ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Call Library Node Error 1097

Solved!
Go to solution

I do have the solution files (good), but they are for a very old version of visual studio (2008!). Libraries it links to can't be compiled in new versions of visual studio easily because of various strange redefinition errors that I haven't encountered before (C4005).  THis might be fixable with enough effort but I may try a different route first.

 

The vendor's code mainly wraps another dll (netsnmp.dll).  I may just try to move the functionality in the questionable dll into LabVIEW using moveblocks, pointer dereferencing etc.. and only call the underlying library

0 Kudos
Message 11 of 13
(1,334 Views)

I do keep a VS 2005 installation around for that, but don't have 2008. As to calling the low level API directly from LabVIEW, I don't think that is a feasible option. I'm sure it can be made to work with enough effort but the API is heavily pointer based with linked structure it seems, so that would be a major pain in the ass to do.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 12 of 13
(1,329 Views)

After looking a bit more at the data structures I am coming around to your view. 

 

I found a workaround that's probably adequate. There's a command line facility for the stuff that's in the dll.  It's a lot slower because I'll need to call 'system exec', but I only need to use the cmd line for the 'set' commands.  (The 'gets' don't throw the 1097).  The 'sets' are rare enough that the performance penalty probably won't matter.  

 

0 Kudos
Message 13 of 13
(1,323 Views)