Problem:Memory Corrupted in LabVIEW?

[splitsecond]

During a voltage measurement,suddenly I got the following message and vi stopped:

"LabVIEW:An exception occured within the external code called by a Call Library Node. This may have corrupted LabVIEW´s memory. Save any work to a new location and restart LabVIEW.

VI "Meas Ipr 14 & Risetime_AD .vi" was stopped at node 0xA10 of subVI "DAQmx Create AI Channel(sub).vi"

Why it happened?

I tried to restart LabVIEW and my computer,but it still happened sometimes.How can I fix this problem?

Attach my vi.Thanks.

[rolfk]

---

@splitsecond wrote:

During a voltage measurement,suddenly I got the following message and vi stopped:

"LabVIEW:An exception occured within the external code called by a Call Library Node. This may have corrupted LabVIEW´s memory. Save any work to a new location and restart LabVIEW.

VI "Meas Ipr 14 & Risetime_AD .vi" was stopped at node 0xA10 of subVI "DAQmx Create AI Channel(sub).vi"

Why it happened?

I tried to restart LabVIEW and my computer,but it still happened sometimes.How can I fix this problem?

Attach my vi.Thanks.

---

The first course with this kind of error is to make sure the newest release of the driver software involved is installed. In this case go and check what NO-DAQmx software you have and what is available on the NI site and if you haven't the latest and greatest download it or order the DAQmx driver kit from your local NI office since it is a rather large download.

Rolf Kalbermatter

[splitsecond]

---

rolfk 写:

The first course with this kind of error is to make sure the newest release of the driver software involved is installed. In this case go and check what NO-DAQmx software you have and what is available on the NI site and if you haven't the latest and greatest download it or order the DAQmx driver kit from your local NI office since it is a rather large download.

Rolf Kalbermatter

---

Thanks.But in fact the device driver is the newest release:(That was the first time I met the error since I have installed it two months ago.I will check it again as your advice.  

[sarmin]

hi,

i have the same problem. it occurred only when running the executable version. it was running fine when running under labview platform (7.1).

wondering if 'splitseco..' has found the solution the memory corruption matter.

many thanks.

[sarmin]

hi labviewans,

i m using a DAQ card NI USB-6008. when running under labview 7.1 platform or environment, the written labview software was running fine. it can be started and stopped and restarted and so on without any problems.

when the executable version is created, the labview software runs unreliably. for example, it runs first time then stopped or exited deliberately. the second run could be fine could be not. the error message is about corrupted labview memory just like this discussion thread.

please help..

[napview]

Same old same old..an executable program will not run exactly 100% like the original code in labview. A colleague of mine had this same issue regarding to remote controlling a latest Agilent test box with window-based application sw based on .dll calling. There are strange things randomly? happened working with .dll or external code call. The .dll files are written in C/C++ or VB then get called from labview which works well until the code is converted to executable which may have something incompatible or missing in window environment. What exactly I am saying is: too many layers of transition or conversion or compilation from one environment to another and bugs can be overlooked or untested completely until they popped up. 

Sorry can't help you on this because of not working with that card but same idea.

[napview]

attached

[rolfk]

---

@napview wrote:

Same old same old..an executable program will not run exactly 100% like the original code in labview. A colleague of mine had this same issue regarding to remote controlling a latest Agilent test box with window-based application sw based on .dll calling. There are strange things randomly? happened working with .dll or external code call. The .dll files are written in C/C++ or VB then get called from labview which works well until the code is converted to executable which may have something incompatible or missing in window environment. What exactly I am saying is: too many layers of transition or conversion or compilation from one environment to another and bugs can be overlooked or untested completely until they popped up. 

Sorry can't help you on this because of not working with that card but same idea.

---

If you get this error with DLL nodes you created yourself, you have made an error somehow in setting up that DLL node. LabVIEW can't detect what the DLL is doing, just see the effects of it. If you setup a parameter differently than what the DLL requires there is going to be a mismatch between what LabVIEW has done and what the DLL did to that parameter. This can result in an immediate crash if very vital data is corrupted or can cause problems later on at a later call. In the worst case you get some very strange results such as LabVIEW crashing when you want to exit.

When calling DLLs with the call library node it is always important to match the setup in LabVIEW exactly with what the DLL expects. This includes not only datatype and calling convention but also allocating string and array buffers in the LabVIEW diagram (with Initialize Array for instance) to the size the DLL expects to be able to write into. One single byte smaller than what the DLL will write to and you get a crash sooner or later.

A good understanding of C programming is tremendously helpful and for anything but the most simple DLL functions almost mandatory.

Rolf Kalbermatter

[sarmin]

hi rolfk,

back to the problem with the unreliably running executable version of labview software.

where do u think the problem is? it was running fine under labview environment. however when running the executable version after computer reset, it always work the first time and maybe the second time maybe the third time as well but the fourth time will result in error message saying labview memory corrupted on 'DAQmx Create Virtual Channel'.

please help.

[sarmin]

hi,

just to follow on this discussion thread, after a few fiddling about i found that even when running under labview7.1 platform the software will also fail with the same reason (labview memory corrupted on 'DAQmx Create Virtual Channel'). however, it is very unpredictable when it is going to fail. it is for sure less frequent than the executable one.

many thanks.