Dronekit issue w/onboard computer & solo controller

[Dustin]

I am testing out a situation where I want to run a Python dronekit program on the Solo onboard computer before the 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. Will cross post to Dronekit forums but figured someone here might have some experience.

 

[carpy]

It helps to think of the controller as a wifi hotspot. The only way you could get to the Solo directly is by cable or if you added a telemetry radio to the pixhawk.
https://dev.3dr.com/concept-architecture.html

 

[h8id]

Is there any reasonthe sololink can't be reconfigured as a wds (wireless distribution system) type arrangement so both the Solo and artoo could be AP stations? Then any wifi camera could be on the sololink network with access to settings,etc.