QGC Cant See Seaker but SSH Works

[nekolny]

Hello,

I have recntly in attempt to get Seeker drone flying indoors, proceeded with default paramters on Seeker drone running VOXL 0.9.5 and PX4 version 11.X. Previously the drone connected well to the QGC with the ip on the drone set to the IP of the computer 192.168.1.138 and the QGC set to look for connection at the IP of the drone whivh ends with 134 and the port 14550 as set by default, however the QGC does nto connect to the drone or seem to receive any MAV messages. I can SSH into the drone without any issues, and after checking all services are running.

I have tried to both reinstall the Ground control PC as well as donwload different versions of QGC witrh no difference in result. I will keep trying to fix this but wanted to ask if anyone has encoutnered this before, or where in the chain of connection could be the issue. I have also on drone when checking communication to PX4 through UART It sometimes marks as disconnected, but I have nto touched any cabled or connections to the PX4.

I will provide anything requested.

Connection Setup:
Seeker -> Wifi Wouter -> Grount Control PC (Ubuntu 24, and QGC)

Thank you for your time an docnsideration.

[Alex Kushleyev]

@nekolny , you are using a very old SDK (2+ years old), please consider upgrading. https://docs.modalai.com/voxl-suite/

Also, please check the following page : https://docs.modalai.com/qgc-wifi/

Alex

[nekolny]

@Alex-Kushleyev said in QGC Cant See Seaker but SSH Works:

https://docs.modalai.com/qgc-wifi/

Thank you very much, I was curious if there are other steps necessary for VOXL 1 board, as I have oone drone updated to 1.2.0 which is the latest VOXl 1 supports, but it does not have any PX4 services. My other drone, which previously worked with flight is the one on 0.9.5, which I plan to also update to 1.2.0. The video provided is helpful but with the commands inspecting mavlink messages, they are absent from the VOXL 1 version, services which I have on the 1.2.0 are.

docker-autorun
docker-deamon
modallink-relink
voxl-camera-server
voxl-cpu-monitor
voxl-dfs-server
voxl-imu-server
voxl-lepton-server
voxl-mavcam-manager
voxl-mavlink-server
voxl-modem
voxl-portal
voxl-qvio-server
voxl-rangefinder-server
voxl-remote-id
voxl-streamer
voxl-trag-detector
voxl-tflight-server
voxl-time-sync
voxl-uvc-server
voxl-vision-hub
voxl-wait-for-fs

there are no px4 files within /etc/modalai

[Eric Katzfey]

@nekolny You should be able to use voxl-mavlink-server --help to see the various debug options available. You can stop voxl-mavlink-server from running as a service and then start it manually from the command line with the desired debug options to see which messages it is getting from the autopilot and what it is sending to QGC (and vice-versa). Then you can also use tcpdump to look at the IP traffic on both VOXL 1 and the QGC computer to see which messages are being sent.