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

@Chad-Sweet No I have not changed the firmware. The firmware version is 1.11.3. I have also attached the picture of it in my previous comments. We are running out of ideas now. @Cliff-Wong - Thanks for the video. We did set the aid mask explicitly to 280 multiple times and rebooted PX4, but still no luck

@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

@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)?

Sounds good, thanks!

Unfortunately, I'm not aware of any such documentation.

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.

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.

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

Hi Bobby, I did some more testing and it seems i can get the IMX377 camera to produce green-ish shades under some lighting conditions. I believe that this is due to AWB somehow incorrectly detecting the scene / lighting type. Let me play with this, I think the solution can be to force a particular scene type so that AWB does not try to guess. In my tests, I pointed the camera at a light gray wall and depending on the angle, it would show up as gray or sometimes a bit green-ish. I will follow up soon.. Alex

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

@MattO The instructions should be more clear now: https://gitlab.com/voxl-public/other/voxl-python-3.6.9#installing-the-ipk

Hi @Sébastien-de-Pret-Roose-de-Calesberg , I'll get an email going to this address on this account, I'm not clear what's going on and perhaps we need to send it in. Thanks and sorry for the inconvenience, Travis

Yes you can use vi on VOXL

@Arrowtec Okay this all looks normal, have you tested this SIM card in a different device to confirm that it is indeed functional?

@scottesicdrone curious to see if you were you able to get things working?