01-22-2008 08:07 AM
01-22-2008 08:16 AM
01-22-2008 08:49 AM
01-22-2008 09:45 AM
01-22-2008 03:02 PM
No custom .dlls or hw. Also all front panel controls & indicators are text - no graphics. Vid accelerator is set to full - default. It crashes more frequently when set to 'None'. HW is PFM-540I NEW .
http://www.aaeon.com/PL_Products_List_E062ABE0294D40E1B2_417FE8679547491DBA_TW_utf-8.html
01-23-2008 04:10 AM
01-23-2008 09:29 AM
Thanks Wiebe,
Looks like you're referring to the grapihics issue. I don't think it is hw since it happens on multiple PFM CPU boards. I do have the latest OEM video drivers. It does occur while the LV .exe application is running and I do file browsing on windows explorer of a log file that the app creates. Also no external I/O LAN, internet, etc...
FYI, not interested in reverse engineering anything. Just trying to make a reliable product while using Labview.
01-23-2008 02:59 PM
Hi RAMaston,
I have been looking into the issue and I think that there are few things that could possibly be wrong. First, are you using any global variables in your code? If you are then these global variables could have gotten corrupted. If the global is formed without a label associated to all the controls and indicators on the front panel data, then the error "memory could not be read" can result. There is a great knowledge-base article that discusses this instance and how to fix it, which can be found here.
Also, this error message occurs when something in the LabVIEW memory space has become corrupted and is often caused by a call to a DLL or CIN code. When LabVIEW is performing garbage collection, it will eventually run into the data corruption and crash. To fix this issue, eliminate any calls to DLLs you might have in your LabVIEW code and see if the crash goes away.
This error can also be caused when running a LabVIEW built executable. If the VI calls a WinAPI DLL function and uses the full path to the DLL in the Call Library Function Node, the LabVIEW Application Builder will create a copy of the DLL in the data directory of the executable.To prevent this, remove the DLL path in the Call Library Function Node when calling WinAPI DLLs. There is another great knowledge-base that discusses this error in a bit more detail.
I hope this helps!
01-24-2008 05:40 AM
01-24-2008 07:51 AM