LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

windows XP embedded

I have been working on a VI to run on Windows XP Embedded.  The software is done and (written on a Windows XP machine) I installed the Labview Runtime Library and the VISA runtime library on the Windows XP Embedded.  My software works and runs fine however, after several hours, the program crashes and I get one of two error messages.

 

  1. Illegal Instruction: an attempt was made to execute an illegal instruction (0xC000001D) occurred in the application at 0x3034C9A2
  2. Instruction at 0x30325C42 referenced memory at 0x2FF0F388.  The memory could not be read.

 

What I would like to know about is, is there anything that I can do about these problems.  To see where the problem lies, I have run the software on 3 different computers.

 

  1. My development machine (Windows XP).  Here the code ran for days without an issue.
  2. A laptop with the Labview Runtime libraries installed.  Here I have not witnessed an issue but I have not run the code as much.
  3. The embedded computer where after anywhere from a couple minutes to a couple hours I will get one of the above listed errors.
0 Kudos
Message 1 of 9
(8,212 Views)

Hi Randy,

Officially, Windows XP Embedded isn't tested or supported for LabVIEW. Therefore, we have very few resources on Windows XPe. However, you might be encountering a problem because many times full Windows functionality isn't supported or present in Windows XPe. This Developer Zone talked about LabVIEW on Windows XPe. I also had a customer state that they monitored registry changes from installing LabVIEW Run Time on the computer and used that information to modify the XPe installation to account for those changes.

Regards,

Hillary E
National Instruments
0 Kudos
Message 2 of 9
(8,190 Views)
Any further information about XPe, or any follow up to this inquiry?
0 Kudos
Message 3 of 9
(7,900 Views)

"Officially, Windows XP Embedded isn't tested or supported for LabVIEW."

 

Now has one year pass, did XPE supprted for Labview now?

0 Kudos
Message 4 of 9
(7,392 Views)

Running LabVIEW on XPe is still not officially supported because of the many different setup combinations of an XPe operating system.   However an XPe installation with all of the options enabled is essentially a Windows XP system and LabVIEW will work on it.  The Developer zone article referenced above has been updated in the past few months and explains what you need to do to get LabVIEW working on an XPe installation. 

 

0 Kudos
Message 5 of 9
(7,374 Views)

To build windows embedded device drive is not sample and quick job.

 

 

 

Hoping NI continues more support as DAQmx does (special in their hardwares support):

NI-DAQmx Run-Time Engine 8.7.1 - Windows Embedded

0 Kudos
Message 6 of 9
(7,101 Views)

Just as a different option for you ....

 

I have run into this sort of thing many times using the PDA module.  Almost every time it turned out to be a memory leak.  To check for this, run the program on the platform that crashes and watch the memory usage to see if it continues to increase as the program runs.  If it does, watch it to see if it is almost completely full when the system crashes.  You may have more then one problems aswell.  Sometimes this is something inadvertantly programmed in by programmers or it is something in Labview that doesn't handle memory the way it should.  I would at least check that, if for nothing else, to eliminate that as a cause of your issues.

 

Greycat

0 Kudos
Message 7 of 9
(7,097 Views)

Hello,

 

I develop some applications in LV 8.6 for mobile targets (as PDA in PocketPC2003 or Mobile 6) and CE targets (CE 4.X & 5.0), and during my development I encountered similar problems with memory management.

 

I agree Greycat to check memory usage (you have some VI to do that  ) to be sure that you have a memory leakage.

After check that you have no "bad function " in your code : as "initialize array" done periodically.

 

Another option, I know that you can modified a key in LabVIEW.ini file  to avoid memory leakage possibility. You may contact NI support to have more information for this.

 

Regards

Cordialement,

Mathieu O.
Certified LabVIEW Architect - CLA (2013)
0 Kudos
Message 8 of 9
(6,998 Views)
Dear Randy

forget the things the other ppl said.
I have done XP Embedded systems since some years now and they have to work 24h a day and 365 day a year.
If you have a good running system you can depend on it and LV will run propperly too.

Make sure your EWF manager works fine.

Most of the problems come from bad hardware.
I suggest to try prime95 on your XP Embedded system at least for 24 hours.
If it doesn't crash that your system ist stable.

The problem you have described may come from a bad RAM device. I have seen failures like this several times.

Another problem might be a memory leakage in your software.
Try to user the LabVIEW Desktop Execution Trace toolkit to find memory leakage.
If you use queues you have to check the usage of optain queue.
This may case a slow down of your programm because os a reference leak of this function.
You will see this using the LabVIEW Desktop Execution Trace toolkit too.

Mostly the problem is caused by bad hardware, high temperatur or a failure between the ears of the programmer.

Hope this may help you a little bit.

Yours with 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 9 of 9
(6,982 Views)