@James-Strawson just checking, are you interested in this at all?

@Alex-Kushleyev said in Voxl 2 mini overheating and rebooting:

@LucaVertiq , did you try disconnecting EVERYTHING from the board and seeing if it boots? Just bare board with power module.

Alex

Yes, the full boot cycles were observed with just the power module and the voxl. We confirmed the voltage at the voxl was 3.8V and not dropping much below that, so no dead short.

@Vinny said in Voxl 2 mini overheating and rebooting:

Hi @LucaVertiq
To me, it seems as if the board went into a power fail condition. Was this in any sort of crash or was it dropped?
LED D2 coming on, then going Off repeatedly is an indication of a continuous reboot cycle (coinciding with your readings of 0.4A, 0A) but there is likely some hardware fault detected by the system preventing it from booting fully.

I had actually just disassembled the vehicle to connect with ADB as we keep the ADB port inaccessible. I had ADB'd in to do some things, then when I reassembled it this began happening. It's quite possible I knocked something loose, or possibly some ESD event.

I've been too busy flying vehicles to get to test the unbricking procedure, but Monday I will.

@Moderator Thanks! I'll give that a shot. Hopefully we can salvage it.

@Moderator I have a VOXL 2 mini that seems to be constantly rebooting and power cycling based on the LEDs.

When I power it on with only the power module plugged in and powered with 12V D1 lights up, but D2 does not. DS2 flashes at a high rate or alternately stays solid. The power supply shows that the voltage is staying high, but the current cycles between around 0.4A and 0A with the DS2 LED also turning off. We noticed that the silver SOC cover was getting hot so held it in front of a fan and it no longer cycled, just held ~0.4A. We measured the voltage arriving to the VOXL 2 mini from the power module and confirmed that it is 3.8v and doesn't dip when powered on. The USB 5V D2 LED doesn't seem to come on and when plugged into a computer there is no indication that a USB device has been plugged in. Holding the ADB button while booting and then plugging it into the computer also does nothing.

Before this the voxl has worked and nothing has really changed in the setup, but it does seem like something has broken. We are wondering if there is a way for us to fix it somehow. Unfortunately it just has the standard SDK installed, so I don't believe the debug port is enabled so I can't check how far into boot it's getting.

Do you have any ideas on things to check?

Thanks

Hello @Moderator

I've been having issues with voxl-px4 taking up 120-130% "CPU Usage" in inspect services and cpu monitor showing overheat warnings. I thought it may have been related to my changes so I reverted to standard voxl-px4, but it still appears to happen. I'm on suite 1.3.4~beta2 according to the MOTD on login.

Any thoughts?

Here's my voxl-version output:

voxl2-mini:~$ voxl-version
--------------------------------------------------------------------------------
system-image: 1.7.8-M0104-14.1a-perf
kernel:       #1 SMP PREEMPT Sat May 18 03:34:36 UTC 2024 4.19.125
--------------------------------------------------------------------------------
hw platform:  M0104
mach.var:     2.0.0
--------------------------------------------------------------------------------
voxl-suite:   1.3.4~beta2
--------------------------------------------------------------------------------
Packages:
Repo:  http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.3/binary-arm64/
Last Updated: 2024-09-13 17:37:13
List:
kernel-module-voxl-fsync-mod-4.19.125     1.0-r0
kernel-module-voxl-gpio-mod-4.19.125      1.0-r0
kernel-module-voxl-platform-mod-4.19.125  1.0-r0
libfc-sensor                              1.0.7
libmodal-cv                               0.5.9
libmodal-exposure                         0.1.1
libmodal-journal                          0.2.2
libmodal-json                             0.4.3
libmodal-pipe                             2.10.1
libqrb5165-io                             0.4.6
libvoxl-cci-direct                        0.2.3
libvoxl-cutils                            0.1.1
modalai-slpi                              1.1.19
mv-voxl                                   0.1-r0
qrb5165-bind                              0.1-r0
qrb5165-dfs-server                        0.2.0
qrb5165-imu-server                        1.0.1
qrb5165-rangefinder-server                0.1.3
qrb5165-slpi-test-sig                     01-r0
qrb5165-system-tweaks                     0.3.0
qrb5165-tflite                            2.8.0-2
voxl-bind-spektrum                        0.1.1
voxl-camera-calibration                   0.5.7
voxl-camera-server                        2.0.0
voxl-ceres-solver                         2:1.14.0-10
voxl-configurator                         0.8.2
voxl-cpu-monitor                          0.4.8
voxl-docker-support                       1.3.1
voxl-elrs                                 0.2.2
voxl-esc                                  1.4.6
voxl-feature-tracker                      0.3.16
voxl-flow-server                          0.3.6
voxl-fsync-mod                            1.0-r0
voxl-gphoto2-server                       0.0.10
voxl-gpio-mod                             1.0-r0
voxl-jpeg-turbo                           2.1.3-5
voxl-lepton-server                        1.2.2
voxl-lepton-tracker                       0.0.1
voxl-libgphoto2                           0.0.4
voxl-libuvc                               1.0.7
voxl-logger                               0.4.5
voxl-mavcam-manager                       0.5.6
voxl-mavlink                              0.1.1
voxl-mavlink-server                       1.4.2
voxl-modem                                1.1.3
voxl-mongoose                             7.7.0-1
voxl-mpa-to-ros                           0.3.9
voxl-mpa-tools                            1.2.3
voxl-neopixel-manager                     0.0.3
voxl-open-vins                            0.4.14
voxl-open-vins-server                     0.2.66
voxl-opencv                               4.5.5-2
voxl-osd                                  0.0.1
voxl-platform-mod                         1.0-r0
voxl-portal                               0.6.9
voxl-px4                                  1.14.0-2.0.79
voxl-px4-imu-server                       0.1.2
voxl-px4-params                           0.4.8
voxl-qvio-server                          1.0.4
voxl-remote-id                            0.0.9
voxl-reset-slpi                           0.0.1
voxl-state-estimator                      0.0.2
voxl-streamer                             0.7.4
voxl-suite                                1.3.4~beta2
voxl-tag-detector                         0.0.4
voxl-tflite-server                        0.3.4
voxl-utils                                1.4.2
voxl-uvc-server                           0.1.7
voxl-vision-hub                           1.8.6
voxl-vtx                                  1.0.5
voxl2-io                                  0.0.3
voxl2-system-image                        1.7.8-r0
voxl2-wlan                                1.0-r0
--------------------------------------------------------------------------------

@Eric-Katzfey That worked perfectly! Thank you. I put all the dynamic notch stuff on my github. I know James mentioned he wanted to implement it.

@Moderator So I was able to get the notch filter working, but I'm still wondering if there's a way to get the mavlink onboard to publish faster than 10hz.

They dynamic notch filter as really improved the VIO on my vehicle which is very prone to vibrations.

@Moderator bump?

@James-Strawson
Hey James,

We chatted at AUVSI about getting dynamic notch filtering working. Right now I have all the basic stuff implemented, but am running into two issues.

The first issue is that even in a sandbox I'm having trouble creating an appropriate notch filter. I've looked at how PX4 and Ardupilot do it, but I'm not seeing as much attenuation as I'd expect. Seeing as you wrote the filter library, I was wondering if you had any notch filters already written. My filter knowledge is rather lacking.

The second issue is that ESC telemetry is only reported across the 'mavlink_onboard' topic at 10hz. I think I'd rather have it be a bit faster.

I was wondering if you had any insight into either of these. Here's the repo I've been working off of:
https://github.com/vertiq-luca/qrb5165-imu-server/tree/feature/rpm_filter
It's just mavlink rpm data feeding a low pass filter for now until I can get my notch filter to work, but it does appear to be filtering!

Best,

Luca

@Alex-Kushleyev Glad that you were able to get that working. I think I tried updating to SDK 1.2.X and was having issues with getting the camera server working, but I think I may just need to wipe. All of these things would be super useful! I'll be out for the next week, so no rush, but it's very good to know that there's a fix.