Great to hear 
It should work fine as is, but as mentioned if you want the name to show up nicely in the “Detected Devices” on the web interface then you could also add it to the query_udevadm.py file
Are you controlling the individual thrusters via MAVLink messages then? I’m curious how that’s handled.
In case it’s relevant, it’s technically possible to control individual thrusters in ArduSub as well, just generally not recommended because doing so is somewhat hacky at the moment, and because control generally works best with high frequency sensor data and minimal latency, which is only really possible within the autopilot firmware. That said, not every situation requires precise/minimal-latency control, and if you’re testing custom control algorithms then that can be a bit simpler to do in a higher level language program that then talks to the vehicle.
I’m told ArduSub has ROS support, via the mavlink package.
That seems to be supported in ArduPilot firmwares, although I don’t believe we’ve tried it with ArduSub.
Regardless, thanks for the info
Huh, interesting… Any chance one of your USB cables is power only?
Thanks for the info! I’ve raised an issue for it