Posts made by nekolny

@tom

I managed to get ADB working and have reinstalled the VOXL. I went for 1.1.2 version as wanted to see if previous issues i had with both 1.2.0 and 0.9.5 would be present. As of now I am able to ADB to the drone, as well as ssh, with it using the AP mode however my QGroundControl does not see the drone. I have changed within the voxl-mavlink-server.conf the secondary ip address to the one that PC has when connected to the drone IP, and the following services are running. But QGroundControl does not seem to see the connection.

These are the following commands and their outputs. The one VOXL version which worked the best on the VOXL 1 board was 0.9.5 but after updating and switching both between AP mode and connected to Wifi router, there is no responce to the connection. When checking messages send to QGC the terminal is stopped at the step of the screenshot.

I went through the setup process few times and am unsure what could be the issue or what to try next. The QGC version is v4.4.5
In case I can create new thread for this but been trying to get two Seeker drones operational.

Thank you for your time and assistance.

Sincerely

Adam Nekolny

@tom

Tried both USB-A ports on the Razer Blade 15 2020 Model Laptop, running Ubuntu 22.04.5 and got the4 same output as below. I have also reinstalled the OS clean so the only software on it is adb shell and QGroundControl.

nekolny@uavcontrol: JUAlS adb shell
error: no devices/emulators found
nekolny@uavcontrol:- /UAV$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1532:0268 Razer USA, Ltd Razer Blade
Bus 001 Device 002: ID 04f2:b65a Chicony Electronics Co., Ltd HD Webcam
Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root

Hello everyone,

after considerations I determined that my VOXL version. 1.2.0 on VOXL 1 board is most likely bricked, or has some issues as id does only respond to ssh, the android adb has stopped working, as the system is not being detected, and with alot of other issues that I encountered I wanted to completely reinstall the system, as the andoid adb is not responding, I looked on the website and the only Unbricking process for complete reinstall is through use of expansion boards which I cant buy or at least not sure if they are still available. Therefore I wanted to ask what steps should I follow to completely reinstall the VOXL on the Seeker drone?

At this point I am trying to just make the Seeker drones working in even a basic state, but like to reinstall the onboard OS to start from clean slate and eliminate any potential software issues that resulted with previous attempts.

Thank you for your time and consideration.

Sincerely,

Adam Nekolny

Also this is what I was getting when inspecting the mavlink server.

00:19:39.969721 IP 192.168.1.1. domain > 192.168.1.134. 40850: 5282 Refused 0/0/0 (42)
00:19:39.970315 IP 192.168.1.134.48451 > 192.168.1.1. domain: 5282+ PTR? 1.1.168.192. in-addr
• arpa. (42)
00: 19:39.973637 IP 192.168.1.1. domain > 192.168.1.134.48451: 5282 Refused 0/0/0 (42)
00:19:40. 106351 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
00:19:41. 068099 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
00:19:41.553204 ARP, Request who-has 192.168.1.1 tell 192.168.1.134, length 28
00:19:41.553488 ARP, Request who-has 192.168.1.138 tell 192.168.1.134, length 28
00:19:41.558414 ARP, Reply 192.168.1.1 is-at 80:69:1a:06:84:4e (oui Unknown), length 28
00:19:41.561634 ARP, Reply 192.168.1.138 is-at 34:c9:3d:07:16:8d (oui Unknown), length 28
00:19:42. 065376 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
00:19:43.070712 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, Length 21
00:19:44.075718 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
00:19:45. 064630
IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
00:19:46.062935 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, Length 21
00: 19:47. 107960 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21

Hello everyone following to my previous attempt https://forum.modalai.com/topic/4332/qgc-cant-see-seaker-but-ssh-works/4?_=1745528516727

I have setup a second drone with newest suported version of VOXL for VOXL 1 board, which is 1.2.0.

Once system is setup I setup both the mpa, as well as extrinsics, which all suceeds and reports that the drone is seeker drone with the approrpriate cameras. Now with the QGC connection I am using version 4.4.4 on Ubuntu 24. Within the drone I go to /etc/modalai/ directory and find the voxl-mavlink-server.conf file within which i set the secondary ip to the IP of my pc which in the softap mode is 192.168.8.53 with there being no default prefilled field for UDP port but it is sending the defulat connections on 14550 just that the config filoe does not have the UDP port specified. Compared to the prior version 0.9.5 there are no PX4 config files, as well as services which feels weird but unsure if that is supposed to be or not. On PC i start QGC and go to the connection tab, setup a new link, UDP and enter the IP adress of the drone with the Port number.

Now to the issues:

1. Sometimes the ADB shell does not detect the drone, the ssh config does work but when connected to the specified port on the drone and running adb shell it marks that there are no devices.
2. Connecting to the QGC, when running voxl-inspect-mavlink any of the options it sometimes does report: waiting for the pipe to connect
   2.1 When the above commands to produce outputs it is showing and reporting connection to the ground control program but the QGC does show its disconnected and when looking in the mavlink inspect part of qgc it does not show anything.
3. when running voxl-mavlink-server and then setting to check from MPA or autopilot or GCS i am getting that: init complete entering main loop
   3.1 and some times when the comands do respond i am getting the UDP connection showing packets beign send from drone to the IP, but nothing much sent from QGC.

Now what I have tried. I tried different veersions of QGC 4.4.0 was the oldest i tried so far. And all show that they are disconnected without any indication of connection. I use separate device connected wither to soft IP or the wifi router to monitor the ip adresses, plannign to try track packets being send but at moment all devices do not change ips. Below i am attching the services running on the drone.


I feel that I am lost as the first drone which was mentioned in the post above, seems to be bricked with me not seeing it in adb either, and not being able to flash newer version of VOXL.

If there are any ideas or potential steps or logs I can provide I will, but at this moment I am ta loss.

@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

@Alex-Kushleyev

Thank you for the information. I am currently using VOXL 1 board, with version 1.2.0 for the drone that I am trying to connect the ESC to but as there is no command for voxl-esc. I am wondering how would I apply it on the VOXL 1 board.

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.

Hello I am currently working with modal Ai seeker and I want to utilize the PWM port on the ESC board and control it externally such as using the J3 connector and wire it to Arduino board or external PWM controller for manually turning on the Motors wihout the VOXL interference.

I was curious if it is something that can be applied or was done, as currently working with Arduino setup and trying to get the ESC to respond to the commands, which I am sending with 1-2 ms signal as sepcified https://docs.modalai.com/modal-esc-datasheet/ In this case I do not need the output signal, so based on understanding I can disconnect VOXL board and use the PWM input to control the motors, but so far had no sucess. In this case i am using 5V input instead of the 3.3V.

The optimal setup PC -> Arduino -> PWM Port on ESC with VOXL board disconnected.

Hello everyone,

I am using two seeker drones for flight infoors, and I have encountered issues with setup and autonomous flight. Firstly when i use qgroundcontrol I uploaded the indoor flight parameters for PX4 v11.1. I go through parameters and disable even the arming check for GPS but still cannot get it to work. I trie to update to newer PX4 firmware but had issues with connecting to the drone as did not find much steps for updates. Therefore wanted to ask if anyone encountered this and if there is a potential fix.

Also i setup the qgroundcontrol initially as just monitoring and use mavproxy and python with pymavlink to send commands to the drone, but have encountered alot of the same gps issues as the drone did not want to respond to any commands. I used program from prior students, which worked, but when recreatign their steps it just decided that it does not want to accept any commands.

I will provide as much detail as needed for troubleshooting but here are the steps i tried.

Reset all parameters and recalibrate the drone.
Check voxl services if vio is running.
Check the mavlink config file to see if the IP is defined well, and it is.

Thank you for your time and consideration.