Eliot,
Thanks for the quick response.
You create your endpoints based on your connected devices. If no devices are connected then you can’t create endpoints for them, or routes to their endpoints.
I apologize but I’ve got a spare Rpi3B on my desk running Ardusub and may have access to our actual vehicle in the coming days (I’m new to the project). Should I expect a /dev/ttyS0 to be functional in this list? I’ve got a UART-to-RS485 converter connected physically.
You may wish to look into transferring your system to BlueOS
I will check in with the other folks on the project, I don’t think there is any known pushback to move to BlueOS given it provides the normal ROV functionality as I’d expect it would. Could you give me a jumpstart in tackling the problem in BlueOS? (a pointer to the correct information / context is all that is needed unless you have specific instructions I could follow).
I see the “Endpoints” section here Advanced Usage | ArduSub
Recap on my setup:
- BlueROV2 running Ardusub (could run BlueOS to my knowledge)
- Normal Fathom-X tether
- New UART RS-485 converter on /dev/ttyS0
** I’d like to pipe vehicle telemetry through /dev/ttyS0 (Via Mavlink router if I understand correctly)
Thank you,
- Brent