@mbahrami We are currently investigating an issue with Remote ID on RB5 that we are hoping to fix in the next SDK release (1.0.1)

We do not have A/B per se, but have tried the Android OTA method which is similar in concept. A file of the full system image is downloaded and then programmed on reboot We would need to work offline to enable

@tanguy-sagere nvm was a permission issue, thanks!

@Alex-Kushleyev sounds good. thanks

@Robby-Carff said in No IMU data: I have follo I have the same problem on VOXL2. When I connect the VOXL2 to QGroundControl I see that gyro/accel is missing and no data is coming in. Were you able to find the problem?

@tom sorry for the late reply, I've been distant from work for one week. I'm using m500 drone with the voxl flight deck. Below is the voxl-version output as you requested. I will probably try to follow what @jonathankampia mentioned and see if it works. I will update the thread here accordingly. Thank you guys for your help, appreciate it. -------------------------------------------------------------------------------- system-image: 4.0.0 kernel: #1 SMP PREEMPT Thu Oct 13 17:57:05 UTC 2022 3.18.71-perf -------------------------------------------------------------------------------- hw version: VOXL -------------------------------------------------------------------------------- voxl-suite: 0.9.4 -------------------------------------------------------------------------------- Packages: Repo: http://voxl-packages.modalai.com/dists/apq8096/sdk-0.9/binary-arm64/ Last Updated: 1970-01-01 00:05:23 List: apq8096-dfs-server 0.3.1 apq8096-imu-server 1.0.3 apq8096-libpng 1.6.38-1 apq8096-system-tweaks 0.1.3 apq8096-tflite 2.8.3-1 libapq8096-io 0.6.0 libmodal-cv 0.2.3 libmodal-exposure 0.0.7 libmodal-journal 0.2.1 libmodal-json 0.4.3 libmodal-pipe 2.6.0 libvoxl-cci-direct 0.1.5 libvoxl-cutils 0.1.1 voxl-camera-calibration 0.2.3 voxl-camera-server 1.3.5 voxl-cpu-monitor 0.3.0 voxl-docker-support 1.2.4 voxl-gphoto2-server 0.0.10 voxl-jpeg-turbo 2.1.3-4 voxl-libgphoto2 0.0.4 voxl-libuvc 1.0.7 voxl-logger 0.3.4 voxl-mavlink 0.1.0 voxl-mavlink-server 0.2.0 voxl-modem 0.16.1 voxl-mongoose 7.7.0-1 voxl-mpa-to-ros 0.3.6 voxl-mpa-tools 0.7.6 voxl-opencv 4.5.5-1 voxl-portal 0.4.2 voxl-qvio-server 0.8.2 voxl-streamer 0.4.1 voxl-suite 0.9.4 voxl-system-image 4.0-r0 voxl-tag-detector 0.0.4 voxl-tflite-server 0.3.1 voxl-utils 1.2.2 voxl-uvc-server 0.1.3 voxl-vision-px4 1.4.0 voxl-vpn 0.0.6 --------------------------------------------------------------------------------

@martongonczy There's a few different places to start troubleshooting. To follow the pipeline, first make sure camera data is flowing (voxl-inspect-cam -a). Ensure the streamer is configured to use the correct pipe (systemctl status voxl-streamer), Ensure the computer running QGC can see the drone over the network, can you ping your VOXL's IP address? Then check QGC settings, are you using the correct URI and port (default port is 8900)?

@RykerBarthold Yes, that's our long flex cable and will work. Be sure to pay attention to pin1 locations and please review the software pages on our Technical Docs to help you along with the camera setup.

@tom Hey Tom. So I tried doing it in WSL but I can only get as far as this screen [image: 1689776899965-70ade761-ae41-450c-9670-1b5c8eaec823-image.png] After hitting that last prompt, it just hangs there indefinitely. Obviously since you haven't tried this method I don't expect there to be a solution, but I was wondering if this is a symptom of something you've seen before that may help in debugging further. If I cancel the flash the Voxl does not get bricked and I can use it as normal on the old SDK. There's also no LED indicators that may suggest its getting flash and obviously no visual indicators in the console that it's getting flashed so I don't think its getting very far in the flash process.

for anyone who has the voxl-qvio issue where it says state FAIL, just try centering (using your fingers and wiggling) the voxl board and it will work. I think it just needs to be centered.

@Mastermind USB0 is the interface the VOXL2 + newer Microhard add-on boards use for communication, so eth0 may not show up if you're used to using that from VOXL1

Glad to hear that helped @Ivan!