Posts made by stevedan

We noticed that at random moments, the Wi-Fi dongle does not turn on (the light does not blink at all). When we access the drone via adb shell, we observe that the network interface for Wi-Fi, wlan0, is not up. Attempting to bring it up does not resolve the issue. Additionally, there are times when the drone connects, and wlan0 is up, but I cannot ping the drone's IP from outside as it reports "network not reachable." From inside the drone, pinging 8.8.8.8 also does not work. What we've discovered as a temporary solution is to restart the drone using "sudo reboot now," which sometimes resolves the problem and sometimes does not. More information about the drone is available below.

Just for your information, we also have a static IP set. I suspect it's a hardware issue because when the problem occurs, the Wi-Fi dongle is not blinking.
Sentinel
What version of software are you using? voxl-version is very helpful for determining software version.

                                                    ▂▄▆▆██▛▀▀▀▀▀▀▀▀▜████▆▆▄▂    
 ███╗   ███╗ ██████╗ ██████╗  █████╗ ██╗         ▗▆████▀▔             ▔▔▀▀▀▀▚▄  
 ████╗ ████║██╔═══██╗██╔══██╗██╔══██╗██║       ▗▟████▀     ▗██▖    ▐█   ▝▀▆▄▄▄  
 ██╔████╔██║██║   ██║██║  ██║███████║██║      ▟████▀      ▗█▘▝█▖   ▐█       ▜█▀ 
 ██║╚██╔╝██║██║   ██║██║  ██║██╔══██║██║      █▌ ▐█▌     ▗█▘  ▝█▖  ▐█       ▐▄  
 ██║ ╚═╝ ██║╚██████╔╝██████╔╝██║  ██║███████╗  ▀████    ▗█▘    ▝█▖ ▐█     ▂▄███ 
 ╚═╝     ╚═╝ ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚══════╝    ▀▀██▄▄                ▂▆███▀   
                                                     ▀▀██▄▄ ▀▀▆▄▄▄▄▆██▀▀▀▘      


--------------------------------------------------------------------------------
system-image: 1.6.2-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Fri May 19 22:19:33 UTC 2023 4.19.125
--------------------------------------------------------------------------------
hw version:   M0054
--------------------------------------------------------------------------------
voxl-suite:   1.0.0~beta4
--------------------------------------------------------------------------------
current IP: wlan0: 192.168.1.17
--------------------------------------------------------------------------------

How have you configured the software? What is the output of voxl-inspect-services

voxl2:/$ voxl-inspect-services 
Scanning services...

 Service Name          |  Enabled  |   Running   |  CPU Usage
----------------------------------------------------------------
 docker-autorun        | Disabled  | Not Running |  
 docker-daemon         | Disabled  | Not Running |  
 modallink-relink      | Disabled  | Not Running |  
 voxl-camera-server    |  Enabled  |   Running   |    16.7%
 voxl-cpu-monitor      |  Enabled  |   Running   |     0.5%
 voxl-dfs-server       | Disabled  | Not Running |  
 voxl-feature-tracker  | Disabled  | Not Running |  
 voxl-flow-server      | Disabled  | Not Running |  
 voxl-imu-server       |  Enabled  |   Running   |     4.8%
 voxl-lepton-server    | Disabled  | Not Running |  
 voxl-mavcam-manager   |  Enabled  |   Running   |     0.0%
 voxl-mavlink-server   |  Enabled  |   Running   |     3.4%
 voxl-modem            | Disabled  | Not Running |  
 voxl-portal           |  Enabled  |   Running   |     0.2%
 voxl-px4-imu-server   | Disabled  | Not Running |  
 voxl-px4              |  Enabled  |   Running   |    31.9%
 voxl-qvio-server      |  Enabled  |   Running   |    40.3%
 voxl-remote-id        | Disabled  | Not Running |  
 voxl-softap           | Disabled  | Not Running |  
 voxl-static-ip        |  Enabled  | Not Running |  
 voxl-streamer         |  Enabled  |   Running   |     0.0%
 voxl-tag-detector     | Disabled  | Not Running |  
 voxl-tflite-server    | Disabled  | Not Running |  
 voxl-time-sync        | Disabled  | Not Running |  
 voxl-uvc-server       | Disabled  | Not Running |  
 voxl-vision-hub       |  Enabled  |   Running   |     2.6%
 voxl-wait-for-fs      |  Enabled  |  Completed  |  
voxl2:/$

Do you have any logs? Uploading PX4 logs to https://logs.px4.io can be very helpful. See details on PX4 logs here
Not px4 specific
Can you share pictures of your setup?

@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.

@Eric-Katzfey, for more context, look at this link https://forum.modalai.com/topic/2197/sentinel-flips-during-takeoff/39?_=1688709638550. Basically, We are using the sentinel drone with the new beta image we received(more explanation of this on the previous link). So basically, we run multiple dockers on the sentinel. In this docker, we do reset of multiple nodes, after doing 2 or 3 resets, the whole sentinel shuts down. It blocks access to the drone and it seem the sentinel Ubuntu part shuts down because I loose access to it. This did not happen on the rb5, m500 nor in my pc. Do you know what could possible be the problem to this. I monitored the dockers stats and the cpu usage is 80% of one core and the memory usage is like 1.16%, which is not that high.

@Eric-Katzfey I am having issue with the new image, it seems like when I am running a docker and I reset for exampe a ros node inside the docker, after doing it 2 times, the whole ubuntu shuts down. In order to acces it I have to unplug and plug the drone to the batteries and then it works. Do you know what could possible be the problem to this. I monitored the dockers stats and the cpu usage is 80% of one core and the memory usage is like 1.16%, which is not that high. This only happens on the sentinel.

I have been trying to calibrate the hires camera on the sentinel for more than two hours but I was not able to do so. I am not able to get a reprojection error less than 0.5. This is the CLI I am using

voxl-calibrate-camera  hires_small_color -s 6x8 -l 0.039 -d

The version I am using is

oxl2:~$ voxl-inspect-services --version
 Service Name          |  Version  |  Enabled  |   Running   |  CPU Usage
----------------------------------------------------------------------------
 docker-autorun        |    1.2.5  | Disabled  | Not Running |  
 docker-daemon         |    1.2.5  | Disabled  | Not Running |  
 modallink-relink      |    1.0.4  | Disabled  | Not Running |  
 voxl-camera-server    |    1.6.0  |  Enabled  |   Running   |    21.1
 voxl-cpu-monitor      |    0.4.5  |  Enabled  |   Running   |     0.0
 voxl-dfs-server       |    0.1.0  | Disabled  | Not Running |  
 voxl-feature-tracker  |    0.2.2  | Disabled  | Not Running |  
 voxl-flow-server      |    0.3.1  | Disabled  | Not Running |  
 voxl-imu-server       |    0.6.0  |  Enabled  |   Running   |    10.5
 voxl-lepton-server    |    1.1.0  | Disabled  | Not Running |  
 voxl-mavcam-manager   |    0.3.0  |  Enabled  |   Running   |     0.0
 voxl-mavlink-server   |    1.1.0  |  Enabled  |   Running   |     5.3
 voxl-modem            |    1.0.4  | Disabled  | Not Running |  
 voxl-portal           |    0.5.9  |  Enabled  |   Running   |     0.0
 voxl-px4-imu-server   |    0.1.2  | Disabled  | Not Running |  
 voxl-px4              |   1.14.0  |  Enabled  |   Running   |     0.0
 voxl-qvio-server      |    0.9.2  |  Enabled  |   Running   |    31.6
 voxl-remote-id        |    0.0.8  | Disabled  | Not Running |  
 voxl-softap           |    0.2.0  | Disabled  | Not Running |  
 voxl-static-ip        |    0.2.0  | Disabled  | Not Running |  
 voxl-streamer         |    0.6.1  |  Enabled  |   Running   |     0.0
 voxl-tag-detector     |    0.0.4  | Disabled  | Not Running |  
 voxl-tflite-server    |    0.3.1  | Disabled  | Not Running |  
 voxl-time-sync        |    1.3.0  | Disabled  | Not Running |  
 voxl-uvc-server       |    0.1.4  | Disabled  | Not Running |  
 voxl-vision-hub       |    1.6.6  |  Enabled  |   Running   |     0.0
 voxl-wait-for-fs      |    1.3.0  |  Enabled  |  Completed  |  


~ adb shell

                                                         ▂▂▂▂▂▂▂▂▂▂▂▂▂            
                                                    ▂▄▆▆██▛▀▀▀▀▀▀▀▀▜████▆▆▄▂      
 ███╗   ███╗ ██████╗ ██████╗  █████╗ ██╗         ▗▆████▀▔             ▔▔▀▀▀▀▚▄    
 ████╗ ████║██╔═══██╗██╔══██╗██╔══██╗██║       ▗▟████▀     ▗██▖    ▐█   ▝▀▆▄▄▄    
 ██╔████╔██║██║   ██║██║  ██║███████║██║      ▟████▀      ▗█▘▝█▖   ▐█       ▜█▀█▄ 
 ██║╚██╔╝██║██║   ██║██║  ██║██╔══██║██║      █▌ ▐█▌     ▗█▘  ▝█▖  ▐█       ▐▄ ▄█ 
 ██║ ╚═╝ ██║╚██████╔╝██████╔╝██║  ██║███████╗  ▀████    ▗█▘    ▝█▖ ▐█     ▂▄███▀  
 ╚═╝     ╚═╝ ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚══════╝    ▀▀██▄▄                ▂▆███▀     
                                                     ▀▀██▄▄ ▀▀▆▄▄▄▄▆██▀▀▀▘        


--------------------------------------------------------------------------------
system-image: 1.6.2-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Fri May 19 22:19:33 UTC 2023 4.19.125
--------------------------------------------------------------------------------
hw version:   M0054
--------------------------------------------------------------------------------
voxl-suite:   1.0.0~beta4
--------------------------------------------------------------------------------
current IP: wlan0: 192.168.1.9
--------------------------------------------------------------------------------

@Eric-Katzfey For now, it seems that the problem is solved because during arming the drone spins faster and smother, if anything occur I will let you know. Thanks for the support.

@Eric-Katzfey Thanks, problem solved.

@Eric-Katzfey Does this version work with mavros, is there any specific detting to enable the ise of mavros?

@James-Strawson Is it possible to modify this rates?

@Eric-Katzfey i would love to solve that issue first but it seems that the fact that the telemetry is low was done intentionally. I will stress test the drone on Tuesday when i go back to the office and give feedback. Although with the new code during arming the motors spins way smoother compared to before and doesn't do what happens before. I will stress test and let you know.

@James-Strawson, is this documented somewhere because this change is different from the previous versions and it might seem like a problem when it isn't. I will fly the drone on Tuesday and give update on this.

@Eric-Katzfey i used the software binding for the rc and setup the voxl px4 vision hub as usual.

@Eric-Katzfey with the new code. I just calibrated and followed the steps on the sentinel integration page.

@Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong
da55f918-135a-4636-a2b4-8bfb0f634445-image.png

What is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
waiting for server

dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY |

This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing

@Eric-Katzfey This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing

@Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong

What is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
waiting for server

dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY | ^C

@Eric-Katzfey I can test this release and see if it solves the problem. When would this release be officially out?.

@Eric-Katzfey Is it possible we can set a time that both of us are available to speed up the process given that your timezone is different from mine?. like 6pm spain time?

@Eric-Katzfey

 Service Name         |  Version  |  Enabled  |   Running   |  CPU Usage
---------------------------------------------------------------------------
 docker-autorun       |    1.2.4  | Disabled  | Not Running |  
 docker-daemon        |    1.2.4  | Disabled  | Not Running |  
 modallink-relink     |   0.16.1  | Disabled  | Not Running |  
 voxl-camera-server   |    1.3.5  |  Enabled  |   Running   |   116.7
 voxl-cpu-monitor     |    0.3.0  |  Enabled  |   Running   |     0.0
 voxl-dfs-server      |    0.1.0  | Disabled  | Not Running |  
 voxl-imu-server      |    0.5.0  |  Enabled  |   Running   |     0.0
 voxl-mavlink-server  |    0.3.0  |  Enabled  |   Running   |     0.0
 voxl-modem           |   0.16.1  | Disabled  | Not Running |  
 voxl-portal          |    0.5.0  |  Enabled  |   Running   |     5.6
 voxl-px4-imu-server  |    0.1.2  | Disabled  | Not Running |  
 voxl-px4             |  1.12.31  |  Enabled  |   Running   |     0.0
 voxl-qvio-server     |    0.8.2  |  Enabled  |   Running   |    27.8
 voxl-remote-id       |    0.0.5  | Disabled  | Not Running |  
 voxl-softap          |    0.1.5  | Disabled  | Not Running |  
 voxl-static-ip       |    0.1.5  | Disabled  | Not Running |  
 voxl-streamer        |    0.4.1  |  Enabled  |   Running   |     0.0
 voxl-tag-detector    |    0.0.4  | Disabled  | Not Running |  
 voxl-tflite-server   |    0.3.1  | Disabled  | Not Running |  
 voxl-time-sync       |    1.2.2  | Disabled  | Not Running |  
 voxl-vision-px4      |    1.4.0  |  Enabled  |   Running   |     5.6
 voxl-wait-for-fs     |    1.2.2  |  Enabled  |  Completed  |