@Chad-Sweet @Adrian-Hidalgo @James-Strawson Everything is working now! THANK YOU so much for all your help!!!

@Eric-Katzfey Got it working about 50% of the time. It seems like most of the time it is just the uvc server trying to connect. I am going to see if I can create a service file around it. Maybe restarting on fail will get it to work with a bit of delay in between. A bandaid for the issue, but at least it will work

@tom thanks

Just to add to this post: I had similar problems with platform image 3.8 (clean install + wipe). Deleting the /data/network/files didn't help. I noticed in the systemctl status docker-daemon that there is were various network related errors, probably in the absense of a valid internet connection (VOXL was configured as AP). For example: Error getting v2 registry: Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid" and "HTTP Error" err="No such image: hello-world:latest" statusCode=404. After connecting the VOXL to a Wifi router with internet access and rebooting, it seems like the daemon is able to run on boot without issues. Is this how its supposed to work? Can't a new VOXL install be successful without internet connection ? Thanks

@wilkinsaf No, took out usb0 entry and it still didnt set the correct ip

@Matt-Turi Ok nice i've send an email to you

@Djalma-Ribeiro You can create a systemd service file and enable it to run on boot and have it execute the OpenVPN connection command. Here is an example on how we have used it in the past on a VOXL: [Unit] After=voxl-time-sync.service Requires=voxl-time-sync.service [Service] Type=forking ExecStartPre=/bin/sleep 2 ExecStart=/usr/sbin/openvpn --script-security 2 --daemon --config /etc/openvpn/KEY_FILE [Install] WantedBy=default.target Won't be exactly the same as above but that's the general idea.

Hi @dlee Can you please double check SW2. From that photo you posted, it seems as if it may stay be in the "ON" position, which would keep it in "EDL" mode and show up as "QUSB_BULK..." instead of an ADB debug device. Please be sure to follow this step carefully when performing QDL updates: https://docs.modalai.com/voxl2-qdl/ We do not have many HW failures on Voxl2 in the field from routine use, so to have one so soon is surprising. However, if you are confident you are following all instructions and still wish to RMA it, we'll test it again to check for all basic functionality and debug the root cause of the failure, if any, and prompt you for further actions. Thanks!

@Aaron-Bottke Yes, that's seems like it would be a nice addition to voxl-gphoto2. We'll put it on our to-do list.

@Anton-Gereles If you have a specific question that we can help you with please open a new forum post and we'd be more that happy to help get you going.

Hi @stevet Late to reply, and thanks so much for your instruction! It's great news for M1 developers like me I will have a try if it works well, and let you know then.

I encountered this problem a while ago and its just a matter of a usb device on your virtual machine You can also download adb for windows to verify that the drone is detected by the computer. If it's not detected by your computer at all (on host OS), then it won't be detected by your VM.

@Chad-Sweet Hey, I updated my voxl to the newest system image and after doing so my docker is using docker-start.service while before it was using docker-daemon.service. Not sure why this has changed, but I have updated the above instructions and wanted to let you know so you could change this in the documentation. Is there a reason why this would have changed after flashing a new system image onto the device? Both times I configured my docker by using voxl-configure-docker-support.sh

So I have Android studio installed now

I found the QGC EKF2_AID_MASK parameter settings above (configuring to 280: Vision position fusion, vision yaw fusion, vision velocity fusion) to allow the seeker to enter position and off-board modes. Prior to configuring, QGC was receiving VIO but was still unable to enter position mode as referenced here To make the forum search engine happy: seeker position mode rejected

@tom I have also noticed that when I updated my platform to 0.9 the streamer.conf has changed. Now our Arducam IMX335 is not even working (it had no problems streaming before). 0.9 streamer.conf { "input-pipe": "hires", "bitrate": 1000000, "decimator": 2, "port": 8900, "rotation": 0 } 3.8.0-0.7 streamer.conf { "conf-version":"1.3", "configuration": "hires", "uvc-generic": { "input": { "interface": "mpa", "mpa-camera": "uvc" }, "output": { "stream": { "rotation": 0, "width": 640, "height": 480, "decimator": 1, "bitrate": 1000000 } } }, "uvc-flir-boson": { "input": { "interface": "mpa", "mpa-camera": "uvc" }, "output": { "stream": { "rotation": 0, "width": 640, "height": 512, "decimator": 2, "bitrate": 1000000 } } }, "uvc-flir-lepton": { "input": { "interface": "mpa", "mpa-camera": "uvc" }, "output": { "stream": { "rotation": 0, "width": 160, "height": 120, "bitrate": 500000 } } }, "hires": { "input": { "interface": "mpa", "mpa-camera": "hires" }, "output": { "stream": { "rotation": 0, "width": 640, "height": 480, "decimator": 2, "bitrate": 1000000 } } }, "hires-logo": { "input": { "interface": "mpa", "mpa-camera": "hires" }, "output": { "stream": { "rotation": 0, "width": 640, "height": 480, "decimator": 2, "bitrate": 1000000 } }, "overlay": { "location": "/etc/modalai/modalai.png", "offset_x": -1, "offset_y": -1 } }, "stereo": { "input": { "interface": "mpa", "mpa-camera": "stereo" }, "output": { "stream": { "width": 640, "height": 960, "decimator": 2, "bitrate": 1000000 } } }, "tracking": { "input": { "interface": "mpa", "mpa-camera": "tracking" }, "output": { "stream": { "width": 640, "height": 480, "decimator": 2, "bitrate": 1000000 } } }, "dfs-disparity": { "input": { "interface": "mpa", "mpa-camera": "dfs_disparity" }, "output": { "stream": { "width": 640, "height": 480, "decimator": 2, "bitrate": 1000000 } } }, "qvio-overlay": { "input": { "interface": "mpa", "mpa-camera": "qvio_overlay" }, "output": { "stream": { "width": 640, "height": 544, "decimator": 2, "bitrate": 1000000 } } }, "tflite-overlay": { "input": { "interface": "mpa", "mpa-camera": "tflite" }, "output": { "stream": { "width": 640, "height": 480, "decimator": 2, "bitrate": 1000000 } } }, "hdmi-mpa": { "input": { "interface": "mpa", "mpa-camera": "v4l2" }, "output": { "stream": { "width": 640, "height": 360, "decimator": 2, "bitrate": 1000000 } } }, "gphoto2-mpa": { "input": { "interface": "mpa", "mpa-camera": "gphoto2" }, "output": { "stream": { "width": 640, "height": 360, "decimator": 2, "bitrate": 1000000 } } }, "video-test": { "input": { "interface": "test", "frame": { "width": 640, "height": 480, "format": "yuv420" } }, "output": { "stream": { "rotation": 0, "width": 640, "height": 480, "rate": 30, "bitrate": 1000000 } } }, "uvc-video": { "input": { "interface": "uvc", "device": "/dev/video0" }, "output": { "stream": { "rotation": 0, "width": 640, "height": 360, "rate": 15, "bitrate": 1000000 } } } }

Hi @gauravshukla914 , Thanks for the help with this. We've released a new beta version of the voxl-hal3-tof-cam-ros that supports auto detection of ToF and defaults the persist.camera.modalai.tof setting properly. It will be in out next voxl-suite release, but is available from our dev channel here if you are interested in using this link The updated readme is here. Thanks!

Hi @Riley-Dove , Want to try to do a screen share tomorrow AM? I'll send an email to what's registered on this account. Some of the errors looked like config file parsing, but the first one was truncated a bit. If the device is in the failed currently, and you don't mind, you can throw the output of systemctl status voxl-vision-px4 -l here in preps. Thanks, we'll figure out what's going on!

Do you have a GPS/Mag plugged in? If not please try plugging in a GPS/Mag and set the PX4 parameter SYS_HAS_MAG to 1. There is a PX4 bug that prevents VIO-only operation if a magnetometer is missing, even if the magnetometer is not in use. We've been trying to get the bugfix approved and merged into PX4 master for over a year now but it seems to be a lost cause. For now our own branch of PX4 has the bugfix along with some custom tools for our ESCs. If your system starts working again with the magnetometer then we know somehow a standard PX4 image got onto your flight core instead of one of our own. Regards, James

On my setup yes that was all I needed to do, but we are still going to do a "full proper tune" on our S500 based frame (Sentinel dev drone) and I will confirm with you that we are getting performance as expected after this and share a video. Our flight test team will be doing that this week, thanks for the patience!!!