I am testing out a situation where I want to run a Python dronekit program on the Solo onboard computer before the solo controller connects. But the Mavlink address 0.0.0.0:14550 which works fine when the controller is connected is not available. Or at least the Dronekit command connect() errors out. Not sure why it would matter that the controller is or isn't connected since the mavlink commands are to the solo not the controller. I tried changing dest address to the loopback address (127.0.0.1) onboard but the MAVlink listener process does not seem to be setup to listen on that network interface. If I could figure which process forwards mavlink commands to/from the serial port that is connected to the Pixhawk perhaps I could find the config file and reset it to list on all network interfaces. Any thoughts?