@modaltb my FlightDeck have a barometer 3D printed cap. But it was not tight, there was a groove in it. Maybe it was planned? By completely closing the barometer, we fixed the problem.

Update: I completely removed docker and voxl-docker from my system. I rebooted, reinstalled docker, and followed these steps to install voxl-docker. Now, I get a different error (same as here) : jared@jared-ubuntu:~/voxl-docker$ voxl-docker -i voxl-emulator -e "/bin/bash" launching image: voxl-emulator with the following command: docker run --rm -it --net=host --privileged -w /home/jared --volume=/dev/bus/usb:/dev/bus/usb -e LOCAL_USER_ID=0 -e LOCAL_USER_NAME=root -e LOCAL_GID=0 -v /home/jared/voxl-docker:/home/root:rw -w /home/root voxl-emulator /bin/bash standard_init_linux.go:228: exec user process caused: exec format error I followed the instructions at the link. The first two commands ran without any issues. I had to modify the last one to fit my architecture: sudo apt-get install qemu binfmt-support qemu-user-static docker run --rm --privileged multiarch/qemu-user-static --reset -p yes jared@jared-ubuntu:~/voxl-docker$ docker run --rm -t amd64/ubuntu uname -m Unable to find image 'amd64/ubuntu:latest' locally latest: Pulling from amd64/ubuntu 7b1a6ab2e44d: Pull complete Digest: sha256:7cc0576c7c0ec2384de5cbf245f41567e922aab1b075f3e8ad565f508032df17 Status: Downloaded newer image for amd64/ubuntu:latest x86_64 That worked. Now the voxl-emulator appears to work too: jared@jared-ubuntu:~/voxl-docker$ voxl-docker -i voxl-emulator -e "/bin/bash" launching image: voxl-emulator with the following command: docker run --rm -it --net=host --privileged -w /home/jared --volume=/dev/bus/usb:/dev/bus/usb -e LOCAL_USER_ID=0 -e LOCAL_USER_NAME=root -e LOCAL_GID=0 -v /home/jared/voxl-docker:/home/root:rw -w /home/root voxl-emulator /bin/bash + USER_ID=0 + USER_NAME=root + GID=0 + getent group 0 root:x:0: + echo 'Starting with UID : 0' Starting with UID : 0 + useradd --shell /bin/bash -u 0 -g 0 -o -c '' -M root useradd: user 'root' already exists + addgroup root users + export HOME=/home/root + HOME=/home/root + ls -ld /home/root drwxrwxr-x 8 james host_group 4096 Nov 1 21:45 /home/root + echo 'root ALL=(ALL) NOPASSWD: ALL' + ls -l /etc/sudoers.d/ total 8 -rw-r--r-- 1 root root 30 Nov 23 2020 james -rw-r--r-- 1 root root 29 Nov 1 22:26 root + cat /etc/sudoers.d/root root ALL=(ALL) NOPASSWD: ALL + chmod 777 /tmp + chmod 711 /usr/bin/sudo + chmod +s /usr/bin/sudo + ls -l /usr/local/bin/su-exec -rwxr-xr-x 1 root root 7660 Aug 14 2018 /usr/local/bin/su-exec + ls -l /bin/bash -rwxrwxrwx 1 root root 959344 Aug 12 2018 /bin/bash + echo 'exec /usr/local/bin/su-exec root /bin/bash' exec /usr/local/bin/su-exec root /bin/bash + exec /usr/local/bin/su-exec root /bin/bash bash-4.3#

We do not have any experience with Python IDEs, sorry. There's no reason any IDE that supports remote debugging with Ubuntu wouldn't work. Check the Docker networking documentation if you run into any issues

Yes that shouldn’t be a problem.

I already had voxl-utils v0.8.2 installed (see earlier post), so I did not update that. I downloaded voxl-tflite-server v0.1.6 from http://voxl-packages.modalai.com/dev/ and adb push'ed it to my voxl. I then installed it (opkg install ipk/voxl-tflite-server_0.1.6_202110292056.ipk) and rebooted my voxl. I saw the same behavior as before until I modified /etc/modalai/voxl-tflite-server.conf. Once I set "input_pipe": "/run/mpa/hires/" and restarted the voxl-tflite-server, it began to work! Thanks, @Matt-Turi, for helping me resolve this issue!

Jonathan, if you have a log(ulog) that exhibits the pause would be great, as it'll show which module is causing the issue. Since you mention local_position, there could be multiple possibilities, especially if you're fusioning GPS and vio data. Based on one's setup, the local position NED calculation may use other sensors and not just vio. To briefly check if vio is the source of the problem, you can look at Odometry topic (directly coupled to voxl vio). If vio has an issue, you'll see the pause, it goto zero or freeze. If not, it's likely a PX4 tuning issue. Nonetheless the ulog will explain what is happening.

Good to know -- thanks, Eric!

@Chad-Sweet I think we are all commenting on the wrong post here. The issue of this post was solved by connecting to the appropriate usb cable. However, @Roman-Rempel I guess you are having similar problem as in this post https://forum.modalai.com/topic/520/voxl-stuck-in-waiting-after-unbricking/3 ?

Thanks for th quick reply. Highly appreciate it.

Thanks a lot Eric this definitely helps, will keep updated on progress.

The flashing from the TOF sensor is normal and should not effect VIO. See the documentation troubleshooting VIO, that should help with debugging https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

That is great to hear. Thanks @Alex-Gardner! I will update. I assumed I was on the latest as I had seen I was on factory bundle 1.0.1 and saw on this page: https://docs.modalai.com/downloads/ That the latest factory bundle was 1.0.1. [image: 1635187077739-32eb6578-ebff-4d43-b1ae-d2dc43d70f7e-image.png] Should I be paying attention to the system-image: ModalAI 3.2.0 When checking whether the system needs an update?

@relevinsky Docker has some pretty good documentation. Have you looked at: https://docs.docker.com/engine/reference/run/#network-settings?

Have you followed the tutorial at https://docs.modalai.com/mavros ?

Hi @Jonathan-Jeff , Theoretically yes but there are limitations. Here's some information that might help in showing some possible options: https://docs.modalai.com/image-sensors/

I didn't know Docker had this feature, so thanks for that tip! Docker built on VOXL is running at version 1.9.0 and from some articles I read it looks like multistage build started in 17.06 (https://docs.docker.com/engine/release-notes/prior-releases/) So I don't believe this is supported.

Thank You for Your responses. Unfortunately Mission Planner doesn't see the device. I also tried via nuttx-shell, but voxl doesn't get any response from stm32, so it's probably a problem with the hardware.

No problem at all, I'll get our docs updated so it's more clear, definitely not a rookie mistake, we should call it out!

@Cool-Karp , Congrats on your success! We are all here to learn so if you have any features you find missing that you found on another development platform please let us know! Thanks