Hi team, i’d like to test cockpit out, but having trouble connecting to my local SITL simulation which is working fine with QGC etc on tcp port 192.168.1.189:14550 (via mission planner mavlink mirror)
putting in localhost or localhost:14550 or ip address into vehicle network connection (global address) results in restarting cockpit and no subsequent connection, or updates.
Windows firewalls are all off
I cant see any doco for the format of the connection string eg “TCP:// etc” in the “search for vehicles” or what searching for vehicles is looking for eg UDP or open ports on the ip address etc.
Any help appreciated - including confirmation cockpit works with SITL instances. (my mavlink vehicles is not portable, and a few km’s away…)
Cockpit does work with SITL, but currently there are only two ways of connecting to a vehicle:
Connecting to a mavlink2rest websocket endpoint (usually from a BlueOS vehicle)
Connecting to a serial mavlink endpoint
Since you’re using a local SITL instance, you can set it to communicate through a serial port and connect Cockpit to that port.
To do that on Cockpit, go to Menu>Settings>General and put your serial address + port under “mavlink2rest URI”: serial:/path_to_serial_port?baudrate=baudrate_value
If I remember correctly you can run SITL streaming to a serial port using a command similar to the following:
sim_vehicle.py -A “–serial1=uart:/dev/ttyUSB0:115200” --console --map