@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

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

@Djalma-Ribeiro RB5 is running Ubuntu 18.04, so any installation / updating instructions for Ubuntu 18 should also be applicable to RB5

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

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.

@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

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

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

@vmassague Awesome!

@RichieRich GPS unit is mounted by default (as it comes with RB5 5G drone), mast is locked in vertical postion. Turning EKF2_REQ_SACC to 0,75 provided no errors from GPS. Obstacle avoidance was also disabled, so we managed to fly. But I'm still a bit confused why the obstacle avoidance gives error, since the drone was placed on the ground (concrete pavement), no obstacles within few meters, while the minimum distance was set to only 1 m. But this is current setup that works: Many thanks for your help. We'll try to figure this out and provide info in a few days.

Today I tried using another provider for the SIM and it connected to the internet. Not sure where to start debugging this cause it is getting an IP, but I figure it needs internet access to get the time ?

@Philemon-Benner Our qrb5165 based platforms put 64 bit libraries into /usr/lib. On Voxl the 64 bit libraries go into /usr/lib64. So the 64 bit support is specifically for our qrb5165 based platforms (e.g. RB5 Flight).

@marian This is some really good information, thank you so much for your findings!

@Jae-Park You should ship out the entire drone so that the team can verify that all of the components are functional, fix anything else that you may not have seen, and do a final flight test before sending back.

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

@modalab Hello, can you help me to resolve this problem?

@Eric-Katzfey Ok thanks for the fast answer.