01-19-2015 11:02 AM
Hello,
I'm building a robot and plan to interface the cRio 9033 with the sensors & actuators.
The builder of the motors provides Windows and Linux libraries for Labview, that allow driving the motors through a simple USB connexion.
I have successfully tested the motor driving on Windows, by connecting the USB directly on my computer.
The provided library is actually a wrapper around a .dll, with hard-coded library path (inside instr.lib). All the VI's are regrouped inside a .llb file.
When trying to connect the motors to my cRio, I cannot understand how to deploy the library :
- the Windows .dll and Linux .so have different names, though the headers are similar
- as said before, the VI's that are used explicitely call the .dll. I have re-wrapped the library to change .dll to .*, but I am not sure whether I should rename the .so.
In short, I am wondering how to use the same Labview VI including a call library, both on the Windows host machine (testing) and on the Linux target device (deployment).
01-28-2015 04:15 AM
Hello oKermorgant,
have you already seen this document :
https://decibel.ni.com/content/docs/DOC-30430
Have a good day
Eloise
NI France