store Vi in flash disk and run on single board computer

[nabhi]

Hello,
    IT seems LVRT needs the hard disk to be present as it is min requirement. This i read in the NI website. That was the confusion i had to use SBC. Now you said that solid state disks are available. So can i install Labview RT in SBCs with solid state disk?
    IEI make SBC boards are available in India. I can try one of them. which is the model of IEI that you used? so that i can choose the model with min of specs that you have used.

Thanks once again.

regards,
Nabhiraj


I forgave....If your application HAS to be reliable, I strongly suggest LV Real-Time.  It strongly depends..... maybe a "clean" XP, for you can be reliable enough.

Have a nice day!

graziano

[Graziano]

Hi!
   A Solid state disk is like a traditional HD, so there should be no problems...  but I've never tried! I used SBC for other purposes without ni software, so I can't grant you with NI products, sorry!

   The IEI computers I evaluated were  small form factor PCs,  with 3.5" motherboards, and centrino (not sure to remember correctly...) processor, but I think this products are not good since there's no PCI. 

   I just told you some SBC and solid state disk vendors, that's all. Im really sorry I cannot provide you more infos, I hope someone else can......

   Have a nice day!

graziano

[LV_Pro]

Actually,

If you are running on a small form factor machine running Windows, you won't need to install LabVIEW on each machine (that would be costly) but can create an executable (it will require you to have the Professional Development version of LabVIEW or buy, if it is still sold seperately, the "Application builder") and only have the executable and the LabVIEW runtime engine installed on your deliverables. As to using National Instruments hardware, it will probably lower your NRE (non-recoverable engineering) costs by making the integration of the hardware with the software easier. Not such a big deal where the resulting software and hardware are going to be replicated an number of times, then the actual cost of the hardware comes into play, but in many of my projects, where we may make only one of an item, it can actually save a substantial amount of money to have the hardware "play nicely" with LabVIEW, which National Instruments products generally do.

[PJS]

I did a very similiar project in 1998.  I used an SBC (gee forgot whom's I used) with computer boards PC104 for (now measurement computing) digital, and analog IO, and an NI PC104 board for GPIB (this was a piece of test gear). At the time, we had no labview RT, and a headless Windows NT system was cost prohibitive (due to small volume). I ended up using windows OSR A (original release) with the LabVIEW 5 RTE.  I used register based calls to all hardware, and had a 128 MB solid state drive (the most expensive part of the system).  By the time I was done stripping windows down, My install footprint was just a shade over 22 MB.  Cold start to measurement time was about 22 seconds.  Hell my phone can not even do that anymore.. LOL.  Granted I was not doing complicated AI or AO, or register based programming might have been a problem..
This all being  said a SSDD will NOT cause you any problems... The OS handles all of the calls.  If you are using a thumb drive for logging, you will need to keep track of which drive letter is assigned to it.  I would recommend have ethernet, you never know when you might want to use it!  espescially if you need to talk to an instrument that may be monitoring the vehicle command bus outside of your application.  I would look around a lot, there are rotary disk drives available for high vibration environments... Engine compartments are NOT like launching spacecraft, and there are diskdrives logging on those!  But in any case, you should have a mirror drive, and monitor the drive health if it is a critical app. 
Good Luck.