How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?

[kmcdevitt]

Truthfully Ravens Fan, are you employed by NI to always pretend that all is well with NI and LabVIEW, and deny, no matter what, that nothing is ever wrong with LabVIEW?

Message Edited by kmcdevitt on 08-04-2009 03:49 PM

[kmcdevitt]

Truthfully Coq Rouge, are you employed by NI to always pretend that all is well with NI and LabVIEW, and deny, no matter what, that nothing is ever wrong with LabVIEW?

Message Edited by kmcdevitt on 08-04-2009 03:50 PM

[kmcdevitt]

Truthfully dixy normous, let me know your address, and I willship you a 1.5TB drive.  Just letme know where you want it shipped and I will mark it to your attention.  Oh, PATA or SATA?  If 2.5” SATA, then the best I can do is512G, or 320G for or 2.5” PATA.

[kmcdevitt]

Truthfully Dennis Knutson, are you employed by NI to always pretend that all is well with NI and LabVIEW, and deny, no matter what, that nothing is ever wrong with LabVIEW?

Message Edited by kmcdevitt on 08-04-2009 03:50 PM

[kmcdevitt]

Truthfully James R, are you employed by NI to always pretend that all is well with NI and LabVIEW, and deny, no matter what, that nothing is ever wrong with LabVIEW?

Message Edited by kmcdevitt on 08-04-2009 03:51 PM

[RavensFan]

Where have you been for a month and a half to suddenly wake up and start yelling at everyone in BOLD, LARGE text?

No, I don't work for NI.  What I and everyone else here has been saying it that expecting a 1.5TB drive to work on a real-time operating system is a lot to expect.  I really don't want NI to spend a lot of time trying to make a 1.5TB drive work with the RTOS.  There are other things I would rather have them work on.  If I had such a requirement, I would work within the constraints and come up with a different architecture for my system.

If you feel that a 1.5TB working with an RTOS is so critical, why don't you contact your local NI sales person and yell at them instead of flaming everyone on the forums here.  Maybe if you yell loud enough to them, they will market a new RTOS that will work for you.  If you know of an RTOS that will do that, perhaps you can get yourself hired by NI and work on the project team to develop it and bring it to the market.

[billko]

It's one thing to be ignorant; it's quite another to be ignorant at the top of your lungs.  I read the document that you pointed everyone to and it says:

Phar Lap ETS, the real-time operating system used by the LabVIEW and LabWindows/CVI Real-Time Modules on RT Desktop PC targets, can cause disk corruption when accessing disk sectors beyond the first 128 GiB¹ of a drive.

Loosely translated, it means that LabVIEW R/T is running on top of the Phar Lap ETS operating system that (presumably) they licensed from Phar Lap (now IntervalZero).  It most plainly states that it is a limitation of the operating system, which is the case most of the time you run into limitations like this.  It's like blaming a car manufacturer for not equipping your minivan with VR-rated tires that are safe up to speeds of 150 mph, only it's not so simple to fix as buying a new set of tires.

As far as I can see, Phar Lap ETS was developed to have as small a footprint as possible, probably so it can fit onto something like a ROM.  Since real time operating systems are meant to "work in small places," I doubt you'll ever see an upgrade to include support for bigger hard drives.  It's amazing it supports hard drives as big as 126 GB, since most likely it would be R/W from a flash card or something.

references:

http://www.intervalzero.com/ets.htm

http://en.wikipedia.org/wiki/Real-time_operating_system

Bill

[Coq_Rouge]

Ravens Fan You should not bother. For me the comments from kmcdevitt is like a X in a Karnaugh map. It also funny that that  the spell checker suggested kmcdevitt replaced with checkmated. Accidental circumstance, nope I do not think so. Meanwhile on my workplace we have a bet going on. How large fonts will kmcdevitt use next time. Pleace do not let me down kmcdevitt

[TMC-NI]

Kevin,

Your local field rep here, Tolga.  From the Pharlap/ETS website:  http://www.pharlap.com/ETSPatches.htm

"Monitor 1-14 Dated 1/29/2009:  Previously, when the ETS software attempted to boot from a single-partition FAT 32 disk larger than 127 GB, the attempt failed. This update resolves this problem and can boot from single-partition FAT 32 disks up to 2 Terrabytes in size."

Pharlap fixed the issue in January 29th, 2009.  LabVIEW Real-Time 8.6.1 was released in beginning of January 2009, therefore NI was not able to acquire the ETS 14.0 Update in time.

The issue should now be resolved with the release of LabVIEW RT 2009.  However, I will confirm that this is the case and let you know.

Regards,

Tolga Cengiz

Field Sales Engineer - Northern California

National Instruments

[kmcdevitt]

---

Ravens Fan wrote:

Where have you been for a month and a half to suddenly wake up and start yelling at everyone in BOLD, LARGE text?

---

First things first, a blended thankyou and apology:  Thanks for educating me on font sizes, I apologize for being ignorant about what that implies.  I was just using a font size that was legible on my 30 inch monitor.  I did not intend to yell, and I am sorry if I gave you that impression.

Sorry to be away for a month and a half.  I have been busy doing a bunch a upgrades, sys admin, software development, been to the ER, deployed some software, finished some tests at some of our facilities, had the exterior of my house painted, had a new roof put on my house, cleaned the garage after the roofers finished, had relatives from Ireland visit and stay at our home for about a week, had a water pipe burst and flood through the wall into the garage, had a flat tire.  Seriously, all true, during this time, but necessarily in the stated order.

---

Ravens Fan wrote:

No, I don't work for NI.  What I and everyone else here has been saying it that expecting a 1.5TB drive to work on a real-time operating system is a lot to expect.  I really don't want NI to spend a lot of time trying to make a 1.5TB drive work with the RTOS.  There are other things I would rather have them work on.  If I had such a requirement, I would work within the constraints and come up with a different architecture for my system.

---

The 126GB limit is indeed, I suspect, a limitation of the OS.  However, it is both the OS and LabVIEW that are sold together by National Instruments.  NI makes LabVIEW and chooses the OS to market with it.  Writing to a disk should not corrupt your data you are writing, or for that matter other files on the drive, or worse, crash the drive. Simply choosing a 140GB drive instead of a 120GB drive should not destroy your world.  My frustrations in the replies in this forum is the same frustration that I typically get with support from NI.  When there is a issue, their standard response is to question why would you want to do that, and then deny that there is a problem.  Things have been getting way better since Tolga arrived.

---

Ravens Fan wrote:

If you feel that a 1.5TB working with an RTOS is so critical, why don't you contact your local NI sales person and yell at them instead of flaming everyone on the forums here.  Maybe if you yell loud enough to them, they will market a new RTOS that will work for you.  If you know of an RTOS that will do that, perhaps you can get yourself hired by NI and work on the project team to develop it and bring it to the market.

---

Again my applogies for font size and/or boldness.  I meant not to appear to yell, and the only flame that I was aware of was the not as red as it used to be hair on my head.  Meanwhile, even the world of Real Time Operating Systems will still need to mature, progress, advance, etc.... to meet the needs of its users.  This is like a 6 or 7 year issue that was not unforeseen.  The RTOS has to right to stagnate, otherwise, some day, Microsoft WIndows version 17 will yield more determinism (only thought another 15 years of Moore's Law, of course.)