Call Library Function Node

[labeau]

When using the NI MyDaq and NI Elvismx- clicking on any of the functions on the toolbar (i.e. DMM, oscilliscope) yields this pop up window:

Labview: an exception occurred within the external code called by a Call library Function  Node. This might have corrupted labview’s memory save any work to a new location and restart labview.  VI”Dmm.vi” was stopped at node “ “ at a call to ELVISmx_subGetDevNames.vi”

Any advice? Thanks!

[labeau]

No ideas...? any suggestions please!!

This error window prevents the Elvis toolbar from working correctly....(i.e. DMM, scope)

[Jim_S]

Hello Labeau,

Could you take a screen shot of the error you are seeing? Also could you give me a better description of what program you were using?

Have you tried to get access to the device in LabVIEW or Measurement and Automation Explorer (MAX)? In MAX, you can try to use the device in Test Panels and see if you can access the device at all. In LabVIEW, you can try to use a DAQ Assistant to create a Voltage task to get access to the DMM.

[labeau]

Jim-

Here's the error window.... I have not tried the other programs, I was specifically using an NI myDAQ A/D device, and the ELVISmx instrument launcher toolbar. When selecting a function such as DMM or other, this window pops up. The function also loads, but I was not able to get them to run. We performed an update on the software as well (labview 2010). The computer also has labview 7.1 installed on it.

Thanks much,

Mike

[labeau]

I tried to access the device through labview measurement and automation explorer (MAX) by right clicking on the device and using the test panels. The test panel came up, I tried a simple audio input, but when I pressed 'run', recieved this error- attached: first jpg is the error, second is the error report. Thanks for any help!

[Jim_S · Accepted solution]

Hello Labeau,

In order to debug this problem, have you been able to use the PCI-6221 that is in you system? Does this work without any issues?

For right now, I think our first step should be to upgrade the DAQmx and Elvismx driver. I would first upgrade the DAQmx driver to 9.2.2 to see if you can access the device normally in MAX. If this works, then I would update the Elvismx driver to 4.2.3 and see if this fixes the other part of the issue.

If you still have problems with this, feel free to post so we can continue to help.

[labeau]

Jim the 9.2.2 driver update seems to be working. The units function now. Thanks for you help.