LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 8.0 with an XP embedded OS

I have heard that you can use LabView 8.0 with an XP embedded OS but there are some toolkits that do not work properly. What toolkits or functions are not available when using this operating system. The application, I am trying to build is not too detailed - although i am using call library nodes to access the serial data card, and then basic function such as building and indexing arrays, storing data in globals and then transmitting data out over TCP/IP. Would any of these functions be unavailable?

0 Kudos
Message 1 of 13
(4,391 Views)
I imagine that you only want to run a LabVIEW executable on a XP embedded OS and not develop the programm on the XP embedded.

In general, XP embedded systems are customized to include all the modules and components you need. When you build an embedded version you select and include all the components which are necessary for your programm to run. So you just have to be sure you don't miss any of the critical components. There are tools available which help you doing this process.

Running LabVIEW executables also involving Building and Indexing Arrays, using normal Globals and doing TCP/IP Transfers works very well on an XP embedded System. We are using such systems currently with a LabVIEW 7 executable. And they run very reliable.

Rob
Message 2 of 13
(4,379 Views)
Thanks for responding so quickly.  I would still like to know if anyone have any knowledge of the call library function nodes working in this OS.
0 Kudos
Message 3 of 13
(4,363 Views)

No Problems with LV and XPE since 2 years now.

The only problem is the EWF manager in connection with compact flash cards.

Kind regards

     Martin

With kind regards

Martin Kunze

KDI Digital Instrumentation.com
e-mail: martin.kunze@digital-instrumentation.com
Tel: +49 (0)441 9490852
0 Kudos
Message 4 of 13
(4,352 Views)
The call library function nodes also work on XP embedded.

Concerning the EWF manager, this is not a problem but just a feature XP embedded offers, if you want to use solid state memory, such as Compact Flashes to replace the Hard Drive.
Using CF is a very nice solution and works well.
0 Kudos
Message 5 of 13
(4,270 Views)
Thank you very much for the responses.  They were very helpful in giving us a good feeling about going ahead in this project with LabVIEW instead of C.  We have this project working on a LabVIEW Windows2000, but due to size constrants, needed an embedded XP app.
0 Kudos
Message 6 of 13
(4,244 Views)
Which tools do you use to determine all the components used?  A tutorial on how the process is achieved would be appreciated.

TIA, John
0 Kudos
Message 7 of 13
(4,257 Views)
I also have questions along these lines.  We have a system running embedded XP and I would like to run a LV8 exe on it.  It requires one of the DAQCards to function.  I guess I'm just not sure how this will all fit on the system.  Traditional NI-DAQ 7.4.1 is a 386MB zip file.  The LV8 Run-Time install is 85.4MB.  Is there anyway of reducing the size of these installs?  I don't need to support every single card NI makes - just the card for my system.  Any ideas from those that have done this?

Thanks!
0 Kudos
Message 8 of 13
(4,169 Views)
John,
You have to use the "Target Designer" and "Component Designer" to make sure all the components you need are included in the XP Embedded Build. These two Tools come with the XP Embedded Development Version. Unfortunately it's not so straight forward to do it....you need some time to get in to it. If you get a tutorial, book or even a course, it will help you a lot to be faster with generating a build.
0 Kudos
Message 9 of 13
(4,228 Views)
I've got both on my XPe development system.  I've successfully built some of the examples and run them from compact flash on my pc104 target.  My next step is to build a labview .exe and install the hardware drivers, runtime, and app on the target.  The missing pieces are the XPe components for these parts.  This is where NI could help out by supplying the components.  There is another thread where someone did this successfully with 6.1 using a third party tool to identify the needed files and registry keys.  NI could supply this information firsthand.  Does anyone have this info for 8.0, or know of any tools to obtain it?

Thanks,
John
0 Kudos
Message 10 of 13
(4,214 Views)