@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.

@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

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

Am I going to have to add those IMU settings to the voxl-vision-px4.conf like "R_imu_to_body" and "T_imu_wrt_body"? I believe that I'm using the IMU1 but I'm also no sure how to check and see which one is in use currently.

@vmassague Awesome!

Got it. Thanks.

@shlee853 Great! I resolved this problem as you mentioned. yocto:/$ rm /data/network/files/local-kv.db yocto:/$ voxl-configure-docker-support.sh Stopping original docker service Enabling our own services docker-start & docker-prepare starting docker-start.service loading hello-world docker image successfully loaded hello-world starting docker-prepare service Created symlink from /etc/systemd/system/default.target.wants/docker-autorun.service to /etc/systemd/system/docker-autorun.service. done configuring voxl-docker-support

The kernel build is posted at https://gitlab.com/voxl-public/system-image-build/voxl-build

@DillonAllen Without WiFi, the only way you'll be able to debug VOXL related things is via. ADB so I would follow this guide: https://docs.modalai.com/setup-adb/ in order to setup ADB on your host computer.

Sorry for the late response, I've been doing some testing. so I've narrowed it down to the error lying in the stereo cameras, I connected each sensor one at a time, reconfigured, and ran the voxl-streamer and was able to get footage for the hires and tracking, but when it came to the stereo it would not work. When I would reboot the system and inspect the services I would see that the voxl-camera-server is running, but once I tried to voxl-streamer -c stereo it would get stuck at the same place and the voxl-camera-server would stop running. I've confirmed that both of my extension cables are working by testing them with the hires camera. I checked the physcial connections on the stereo cameras and there are no creases in them, they look just as they were folded with the original setup, and I believe that if any of the connections were inverted then the VOXL wouldn't even start up.

@Aldo-Castro-Freire thanks for the feedback, do you mind sharing the openVPN Client and Server versions you ended up using that worked? We've tested using server v2.4.8, voxl-vpn (v2.1.3 inside that), and OpenVPN Connect ver 3.2.2 on Adroid.

I reran the calibration outdoors with gps signal and far from any metal. I also raised the drone to be ~3-4' from the metal turntable below it. This improved the calibration quite a bit and the drone is not drifting as much as before. However, there still seems to be more drift in the VIO than there was when I first received the drone. I still don't have the PWM_MIN parameter that the docs say I should check for the assure the PX4 parameters loaded properly. I see that this parameter is in the custom2.params file, but the note in the document says it turns off the gps. Can you please explain the steps you go through during your calibration process? Should I also be loading this custom2.params file? If so, does that mean that gps is not used when in VIO (no sensor fusion etc)?

Solution: sometimes when just binding the RC controller, the inputs aren't shown. Make sure to restart drone after rebinding. Additionally, I've found different controllers have different lever/switch inputs, so its good to use QGC to look for the responsive switches and assign the ones you want accordingly

Sounds good, thanks!

Yes, after adding some foam, The UAV now are stable than a bit. Do you think the battery should be problem? Our 3S battery are quite old.

@Eric-Katzfey Thanks for the explanation, I was not starting the voxl-camera-server before. When I started the voxl-camera-server, I had my camera configuration include the tracking camera which stopped the voxl-camera-server from starting correctly. Once I changed my camera configuration with voxl-configure-cameras to "hires only" I was able to start the camera server and then start the voxl-streamer as well.

WOW! Thanks @Lynn-Koudsi for the help, when we setup the forum this is the kind of interaction we were hoping for, just awesome!! Sorry for the setup and 'wonkyness' right now, we've been somewhat caught with getting pre-release software out there without all the setup/docs lined up.... so we're doing a little catchup it seems. @Liping there until we have our docs updated, if this is working, I'd say this is a good approach! Thank you both for the details, we'll relay this through the team.

@manzur Interesting, thank you for the information! Perhaps I was wrong about the default Network ID, I will take a note of that.