I also have this outpu from voxl-inspect-cpu:

@tom I tried to upgrade to 0.9.5 version (the latest for RB5Flight in the releases page) but I see the voxl-camera-server is same version as the 0.9.4 sdk (version 1.3.5); the drone is still crashing the voxl-camera-server after the upgrade. Is there any other more updated sdk for the RB5 flight (M0052 hardware)? or at least for the voxl-camera-server package that I could try? thanks

Hello, the voxl-camera-server in my RB5 Flight randonmly crashes. I can see when I inspect the services a huge amount of CPU consumption from voxl-camera-server:

The voxl-camera-server can reach cpu consumption up to 170%. Then randomly stops running. When I use the journalctl command I get this output:

The SDK version I am using is this one:

Could this be solved if I flash the rb5 image to the latest SDK version for the rb5?

Thanks!

@Eric-Katzfey okey, tomorrow I will try to set up a local network with a router and I will let you know!

@Eric-Katzfey yes I see the Green bar and then It appears the pop-up

@Eric-Katzfey Could be, I am using this config to connect to the Sentinel (IP is 192.168.1.75)

Also, the QGroundControl version is 4.2.8:

I normally used the qgc_ip param to directly connect the drone to QGC in voxl-vision-px4.conf,when the service was there but now with the new version I do not know if that param is still available somewhere.

Hi again, could it be that QGroundControl still does not support this new version? otherwise I cannot perform a manual flight as I cannot configure the RC parameters

Hi, I just updated one Sentinel to the latest image available (VOXL2 SDK 1.0.0, released in July 12). The flashing was succesful and the Sentinel was assigned with a proper SKU number (MRB-D0006-4-V1-C4).
I tried after to bind the RC (Spektrum Dx6e) using the command qrb5165-bind -s inside the drone terminal; the binding was successful (receiver light goes in constant orange). But when I try to assign the channels to the switches in QGrounControl, this pop-up appears (sometimes with more parameters):

I can see the raw data from mavlink changing values as I move the toggles in the RC, but it seems that even though I assing for example, the Kill Switch into one of the proper channels, the QGroundControl does not notify that the KillSwitch is Engaged or Disengaged. For the previous voxl-version, the platform 0.9.5, I was able to bind the RC and none of this pop-ups where happening. Would appreciate any feedback! Thanks

Hello, I am trying to set up an static IP from an script; I automatically set an static IP once the drone is set to a new WiFi. In few lines, the script what it does is:

• Connect the drone to a new WiFi (with adb shell voxl-wifi station <ssid> <password> command
• reboot the drone with adb reboot to gain a new IP address
• ask the new IP for the network, ask netmask and default gateway, set this new values into the file for the voxl-static-ip service (/usr/bin/voxl-static-ip)
• reboot to see the changes

The thing is that I manage to set an static IP for the drone. Once it reboots , the drone gets this new static IP but I cannot ping the drone from another device until few minutes passes. Once it gets the first ping, the connection never stops but I wonder if you could see why it lasts too many minutes to set the static IP for the new WiFi.
I see, once rebooted, the new static IP in the wlan0 interface (192.168.1.141), but I cannot reach it; instead, I can reach the IP address that appears here when putting 'ip route' into the terminal (192.168.1.198):

from the drone I can ping to 8.8.8.8 and my laptop; Any help would be appreciated.
Thanks!

So another question, is it safe to power it with 4S batteries (without flying)? I am using the drone for development now. I would like to know the power input range of the Sentinel as it is not in any place specified @Adrian-Hidalgo