LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR

Hi,

   This is sony

I have to interface USB to SPI bridge through Labview, i have imported all .dll files of the product, i can see all the functions related to this product under my library files, am getting the following error

 

Possible reason(s):

LabVIEW: An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.

          Can you please explain me about the error as well as the solution for the above error.

Hope your reply as soon as possible.

'' A professional is someone who can do his best work when he doesn't feel like it''...........
0 Kudos
Message 1 of 6
(2,967 Views)

Well, it seems that the dll is buggy or the call node is configured wrong, and there's not much LabVIEW can do about it.

 

What is the dll? How did you configure (import?)  it? What is your LabVIEW version?

0 Kudos
Message 2 of 6
(2,961 Views)

Thanks for your reply,..

                dll :  SLAB_USB_SPI.dll

Call library function node details :

    Function name : CP213x_GetUsbConfig

    Calling convention : C

I have to detect USB of this product.

'' A professional is someone who can do his best work when he doesn't feel like it''...........
0 Kudos
Message 3 of 6
(2,953 Views)

Do you have a link to the documentation?

0 Kudos
Message 4 of 6
(2,946 Views)

My Lab view Version : 10.0.1 (32-bit).

 Are you asking about the product documentation..?

'' A professional is someone who can do his best work when he doesn't feel like it''...........
0 Kudos
Message 5 of 6
(2,942 Views)

A few thoughts:

1.  Are you absolutely sure about the calling convention?  Choosing the wrong calling convention almost guarantees a crash.

 

2.  Another issue that often leads to a crash has to do with passing parameters incorrectly.  If you have arrays or structures this is likely an issue.  What is the function's signature?

 

3.  Can you access this DLL from another program (like perhaps a demo which came with it?) to make sure the DLL is actually OK?  A crash in the DLL function itself (unconnected to LabVIEW) would give similar results.

 

Batya

0 Kudos
Message 6 of 6
(2,885 Views)