@LR Are you able to fly seeker indoor (for which no GPS available) with Position mode? If not, for seeker to use VIO as position estimate you need to use this set of parameter for px4.

@Moderator Alright... What radio would you recommend with the VOXL 2 mini to achieve 3-5km of video communication. [image: 1729875415371-9fe75b9a-4c9c-4273-ab2f-d37f78ab40bd-image.png]

@jonathankampia Edit: managed to fix it by disabling voxl-configure-modem and manually setting the IP of the eth0 interface. I guess 'eth1' is the J11 connector then.

I was able to replicate your issue and also confirmed that the issue goes away if I move the AR0144 camera from the M0084 cable (connected to J7L) to J6L using M0076 interposer. I believe the issue is related to potentially insufficient decoupling capacitance in the IMX214 camera, so running it on the same flex with another camera causes noisy pixels. I hope you can work around the issue by moving the AR0144 camera to another port. Sorry about that! Alex

@Jetson-Nano Thanks for all the help, I really appreciate it.

@itsnav Can I get some help here, team?

@LR Better to get a FrSky transmitter than to try to rework the drone.

@craigphoenix , I think the SDK install is failing somewhere in the middle (but goes unnoticed) and the ESC update and wifi issue is a result of that. We have not see this behavior before, so it is best to send the board back for inspection. Thanks! Alex

@deeplearning361 That is normal, that is how the majority of drone controllers work. You can read through the commando 8 user guide to figure out how to make it self-centering if that is preferred: https://manuals.plus/iflight/commando-8-radio-transmitter-elrs-manual

@itsnav , based on your test, it does appear that the camera itself is not functioning. The camera detection and configuration happens via i2c bus but the image data is being sent via the high speed MIPI bus, so that is why you could have a case where the camera is detected and appears to be running but there is no actual data. It is possible that one of 10 (!) high speed connections is not working (one clock, 4 lanes -- all differential, so x2 number of connections). You should probably RMA this camera unit. I am also curious what dmesg -w will output while you are running the camera server with the non-working camera and trying to inspect the stream. dmesg will output any major issues from the Kernel driver that may relate to the camera not working. Alex

@Alex-Kushleyev Yup, editing kona-perf_defconfig looks to have worked, thanks!

@Rowan-Dempster I think it is safest to just not use data that reads 0,0,0 as the sensor cannot measure that close anyways

@Zachary-Lowell-0 Additionally, when I push the left stick on the controller up or down, it stays in that position after I release it, instead of returning to the center. Is this by design? It behaves differently from the right stick, which returns to the center automatically.

@Sarah-McMahon said in Unable to Generate the Mavsdk Docker on a M500: @Zachary-Lowell-0 I encountered an issue with the threading during the download process, which caused it to take about 9 hours. The main problem arose when running deploy-to-voxl.sh—the drone ran out of storage after pushing the tar file, preventing the image from being loaded into Docker. While attempting to free up space, I mistakenly ran the wrong opkg command and deleted all opkg packages, making it impossible to SSH or ADB into the drone. Do you have any suggestions for a potential fix? I noticed the USB Expander and Debug Add-On Board might be helpful, but I couldn't find it available for purchase on the website. Reply Hi Sarah - I am unsure if I am following - the docker tarball is only a few gig's so I am unsure how you ran out of space. For now I would just reflash your voxl from the downloads page here https://developer.modalai.com/categories (download the most recent voxl1 sdk unzip it and run the install script from the parent computer) - this will reinstall the entire sys image and newest SDK onto the voxl and allow you to adb shell and ssh in again. From there you will need to configure the SKU and mpa and then you can try the docker installation again from the parent computer. Can you let me know how big your image is for the mavsdk docker tarball? And if you run df -h on your voxl can you paste the output I want to see where all your disk space is being utilized. Zach

@Moderator I am aware. I've been using this drone for research purposes and I always make sure to follow safety guidelines. Thanks, I'll follow these instructions.