LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error occured in the call library function node in Trace32_PracticeCmd.Vi

Hi ,

 

I am trying to intergrate lauterbach (trace32) ; (Debugger) with labview . I have been provided the .dll and some functions that I can use by the manufacturer. 

 

I am trying to "load" a file into my hardware . There is a sub vi that the manufacturer (Lauterbach) has made availabe to me , it is called "Trace32_PracticeCMD.vi" .Please find the Vi attached. 

This Vi should allow a user to enter a command to perform for eg ."DO" and then subsequent Vi would allow me pass a path of the file with the filename and that is how I can load my file into my hardware .

 

This VI keeps throwing me an error . Please see the error attached. 

 

I have read a lot of posts on the similar  error and have tried out all the suggestions that were listed but they are not helping me solve this . 

 

I am also attaching the .dll file . Find attached 

 

Please feel free to ask for more information.

 

Please suggest.

 

 

Download All
0 Kudos
Message 1 of 4
(2,747 Views)

Sounds to me like this is clearly Lauterbach's problem to fix. The error message indicates that there is either a problem in the DLL (which they wrote) or the VI calling the DLL (which they also wrote).

 

Are you sure the DLL is compatable with the version of Windows and/or LV you are using?

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 4
(2,727 Views)

Mike , 

 

 Thank you .

 

I know the dll is comptabile with the labview 2011 , that I am using. Since , I have the VI and the dll attached can we not try to debug the cause ? 

 

I have contacted the manufacturer too.

 

Help appreciated !

0 Kudos
Message 3 of 4
(2,715 Views)

With this error a common solution is to check how the dll is called. Here are a few articles that address calling a dll. Definitely try changing the calling convention. I hope this helps with the first steps in debuging. It is good to hear you have contacted the maufacturer. They will most likely have a solution or example for you to work from. 

http://digital.ni.com/public.nsf/allkb/7253D2F0D91F68058625752F005AB672

http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33

Good Luck,

ConnorM

0 Kudos
Message 4 of 4
(2,677 Views)