Thanks for the info., it's not too late. We will work the task in the upcoming week. We'll make a few attempts and report back our outcome. Thanks again, -Todd

@shlee853 I found a v3.5.6 on the github. I'll try on this version. https://github.com/mavlink/qgroundcontrol/releases/tag/v3.5.6 Thannks,

The obstacle avoidance on voxl uses the disparity map coming out of voxl-dfs-server (so make sure this is running if you want obstacle avoidance), and passes the obstacle data into the standard px4 bins (thus using the px4 avoidance algorithm)

So i managed to get it to work with the following service file and script file - [Unit] After=docker-autorun.service [Service] Type=simple ExecStart=/bin/bash /home/root/mastervoxl_init.sh [Install] WantedBy=multi-user.target #!/bin/bash echo 'initializing mastervoxl docker container' docker run --restart=always -i mastervoxl /bin/bash

@Thomas-MacNamara Awesome! What a cool application!

After no small amount of playing around and Googling I think I have hit the wall. If I set them as = y then the build won't boot when deployed through fastboot if I set them as =m then they just stay as unset # CONFIG_USB_CONFIGFS is not set # CONFIG_USB_GADGETFS is not set I did check to see if the WIFI was running on the failed boots just incase the change was breaking ADB but it seems the build just does not like those flags. It is so frustrating to know the hardware is there and the implementation is possible (Rasberry-pi HID is pritty dang easy). Especially seeing as the underwater stuff is working. The non USB solution is just to go via ethernet but that is just a lot of things being bolted on to the poor thing. Thanks for the help though.

@Alex-Gardner That was it, the ip address was not inputted correctly. Thanks!

@modaltb Not an issue anymore, thanks. I simply rebuilt the image from the very first step. Best guess is something corrupted the original

@Alex-Gardner Found the solution. Here are the steps to make sure VIO is working properly. Make sure VIO is enabled in the voxl-vision-px4.conf file Make sure PX4 parameters are updated Ensure voxl-camera-server, voxl-qvio-server, and voxl-vision-px4 services are all running in the background If you could add step 2 into the documentation it would help a lot. As is, I had to do a lot of forum searching to figure this out. https://forum.modalai.com/topic/140/vio-indoor-navigation

Unfortunately, we have never tried anything but IPv4, and don't really have much of any experience using IPv6 in general.

The vvpx4 option is the second to last one there: "en_tag_fixed_frame". In order to use tag localization, make sure the voxl-tag-detector service is running. The config file for this is at /etc/modalai/voxl-tag-detector.conf and you can specify the tag locations at /etc/modalai/tag_locations.conf

Great, thank you!

Hi @DarkKnightCH , It's likely something you can setup in your transmitter, or perhaps reset the transmitter to default state. What make and model do you have?

That page needs to be updated. The concepts are good but that xml format is out of date. So, voxl-configure-extrinsics is likely the right approach for changing the values We will try to get that page updated in the next day or two to be more clear

We have never used a Xavier, sorry

Hi @DarkKnightCH , We offer other receivers to be installed on the m500 as well, but roughly: weight and size, indoor flying was a primary first use case, spectrum is good for that. For outdoor it works but the range isn’t great, so you could use another receiver. The satellite receiver 100 percent works as we’ve shipped hundreds in this config, but please choose from the options that fit your need for longer range. If you need BVLOS, consider LTE instead, but you should be savvy to setup a VPN server! No main reciever needed. The satellite receiver is put into binding mode via a button in QGC. We’ve bound hundreds of vehicles this way. After pressing the button, the reciever flashes it’s LED quickly to indicate it’s in binding mode. Please note, there are knock offs “spektrums” in the world that may not work.

Here is a link to my .param file: https://drive.google.com/file/d/14DA0fQ8Q4PowwlFXMUfU_w1wteXpM9rk/view?usp=sharing

We do plan to bring the gimbal version back to life, hopefully by the end of the year. We have other, higher priority, products in the pipeline right now.