LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Code Interface Node and LV Global Variables in Parameter List

I'm using Labview 6.1 under Windows 2K. I've written a Code Interface Node DLL in C using Visual Studio. The DLL works fine when called with local variables. But when I used a Labview "Global" array instead of a local array as a variable passed as a parameter to the interface, the DLL fails and causes a fault:

"An exception occurred within the external code called by a Call Library Node. This may have corrupted LabView's memory. You should save any work to a new location and restart LabView. VI "name" was stopped at Call Library Function Node "functionName" and Range 0x7308 of sub VI "SubViName.vi".

I haven't found any reference to problems with Global Variables being used as parameters in a CIN DLL. Is there a difference in how local vs global variables are passed? What is a work-around? I'd perfer not having to convert all Globals to Locals, but I can make a local copy of the variable.

D
0 Kudos
Message 1 of 2
(2,450 Views)
This sounds odd. Could you attach a simple example?
0 Kudos
Message 2 of 2
(2,446 Views)