@stevedan As a side note, I would recommend upgrading to the official SDK 1.0 as opposed to beta4 as there are many bug fixes between the two

@M-al-khatib Video quality is going to be largely dependent on the cellular coverage in your area. For your second question, can you give me more details on the setup you're trying? Are you connecting a standalone modem to your PC?

@esaldiran @Chad-Sweet @Moderator The same issue was occurring for me, I am now running the dfs server on SDK 0.9.5 perfectly. [image: 1693414627297-stereo_dfs_s2.png]

@Paul-Carff WiFi is primarily for local debugging, it will not work well at range. It is heavily dependent on typical wireless interference issues and channel sharing as well as the modem at the ground station.

@Paul-Carff OK I guess 4th time is a charm. I completed successfully on the 4th try.

@Eric-Katzfey Thank you

@Paul-Carff Thanks for sharing your findings! It's super helpful for future users

@M-al-khatib Great, glad to hear it is working now!

@Jgaucin I reflashed the system image for an unrelated reason and now the drone autoconnects to QGC with these settings in voxl-mavlink-server.conf file in /etc/modalai. "x.x.x.x" is the IP of the host PC running QGC. { "primary_static_gcs_ip": "192.168.8.10", "secondary_static_gcs_ip": "x.x.x.x", "onboard_port_to_autopilot": 14556, "onboard_port_from_autopilot": 14557, "gcs_port_to_autopilot": 14558, "gcs_port_from_autopilot": 14559, "en_external_uart_ap": false, "autopilot_uart_bus": 1, "autopilot_uart_baudrate": 921600, "en_external_ap_timesync": 1, "en_external_ap_heartbeat": 1, "udp_mtu": 512, "gcs_timeout_s": 4.5 }

@tom ubuntu 22.04

@tom Here is the output of these commands: [image: 1689356694914-3e07e160-442a-40be-ae73-57ba29ae9950-image.png] [image: 1689356818948-f8d2007c-d9d2-460c-9ae0-67104798f960-image.png] [image: 1689356880764-6e99702d-9fca-48bf-b69a-ee649933411d-image.png] [image: 1689356919104-0a85071d-b6eb-46b4-bf3e-3ab3d99a5674-image.png]

@Eric-Katzfey we are connected to the gpio pin but don't activate it during this reset. We also have a privileged access from the docker so we can change the gpio pin state to on and off from software. We use the pin 1153. The node on this docker runs our autonomy stack but does not interact with the hardware besides the gpio. i also tried removing the privileged access to the docker but still got the problem. We have 2 more dockers that gives us the ros2 mavros messages. Those one never gets resets and works fine.

@stevedan No, we have not encountered that. But can you open this up in a new thread so that it has an appropriate title? Thanks!