We have a NI-Linux-System NI-PXIe-8840 system to do some 3rd party device integration.
We have a driver for Pharlap LabViewRT systems.
We also support Windows and Linux drivers for that 3rd party device.
For the new linux based LabViewRT OS the idea was that the existing linux driver could be used for the device access instead of some kind of dll using visa calls. To realize that NI advised that the Linux driver could be installed on the NI-PXIe-8840 Linux based system and accessed by LabView.
We were able to install and compile the driver on the NI-PXIe-8840 Linux based system when logging in as admin. Device is available and some sample application could be executed in the linux console.
During installation the following files were created on the LabViewRT Linux system.
/lib/modules/<kernel>/extra/aim_fdx.ko (The PCI kernel module compiled for kernel configuration)
/lib/modules/<kernel>/extra/aimfdxusb.ko (The USB kernel module compiled for kernel configuration)
/usr/local/lib/libaim_fdx.* The API-FDX library
/usr/local/include/aim_fdx* The API-FDX header files
The VIs for device access were using "Call library function" and with Pharlap a DLL was refered. NI advised to replace the dll name by the linux library: libaim_fdx.so.
When starting the LabView Sample on host the resources seem not to be present.
I can imagine of different reasons for that.
1. The device library is not in the correct place. Do I need to put it to a different location as described above? I already tried /c/ with no success.
2. Device access rights wrong for lvuser
In directory /etc/udev/rules.d we generated 99-aim_fdx.rules file to allow lvuser to access that device. Contents of this file are:
ACTION=="add", DRIVERS=="aim_fdx", GROUP="users"
Is this ok for that system?
What do we have to do to access our 3rdParty device from LabView?
