I've reformatted the myRIO back to the standard driver implementation plus all extra NI-VISA (5.4) additional drivers such as the NI-VISA USB Passport. Turns out that after all this debugging, all you need to do to get a Communication Device Class (CDC, ttyACM) module to get recognised within LabVIEW RT is to perform the following:
- Get your LabVIEW RT remote target visible in MAX.
- Connect the USB module you wish to control to the USB host port of your remote target.
- SSH into LabVIEW RT.
- Double check that the device you're using is a CDC. You can do this by typing the command #dmesg,and getting a response that looks something like this:
[ 173.342694] usb 1-1: new full-speed USB device number 2 using xusbps-ehci
[ 173.635010] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 173.652955] usbcore: registered new interface driver cdc_acm
[ 173.652977] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Your actual response my vary slightly. - Execute the command #rmmod cdc-acm. If the command prompt returns does not return with a response, the device driver has been successfully removed.
- Go into NI-MAX on your host machine and refresh the Devices and Interfaces list for your remote target. The hardware should now show up. :smileytongue: