Not sure if USB is exposed into your VM, or if that is possible? Can you type $ lsusb And share if anything shows up?

@James-Strawson hello there James. I've been dumbfounded by the "IMUs" page in your documentation for quite some time now so I'm very thankful that you took that on.^^ Can you please clarify a few things for me here: 1:What do you mean by 'likely DNI'd' for Fligh Ccore IMU3? Sorry, I actually don't know what that means. 2: For now I'm only using the Flight Core -part of the VOXL-Flight so does that mean PX4 by itself is always only using the 20602 and the 42688p? 3: I've tried using the suggested command "voxl-configure-mpa" in an SSH shell, via ADB and in QGC's nutshell CLI but always get an error "command not found". Where exactly would I use that? Using other "voxl-" related commands usually work no matter where I enter them so could you please maybe point me in the right direction? Here's the output when checking for present IMUs: [image: 1644262881378-px4-voxl_imus.jpg] Thanks a lot for all your guys' work and a nice week to everyone. Cheers.

@SmittyHalibut That page may be outdated. You definitely can set a static IP on eth0, it is required for Microhard usage. For example voxl-modem uses the interfaces file here for setting a static IP: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/config/interfaces It does require pulling down / up the interface on boot: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/scripts/voxl-modem#L516 which may be a solution for @Sem-Andeweg

@Chad-Sweet Hi Chad, I go further and for the accelerometer calibration I have another issue. With Rotation None, the QGC see my aircraft on left side instead of level position, and so on. When I test to arm and take off, it see the vehicle as turn on right side and have failsafe issue. If I put Rotation = Roll 270 is much better, and I can arm and takeoff (just simulate for now). Still, I have two positions that are not right, aka it show the vehicle on: left side instead of noise up right side instead of noise down I would really appreciate your help to indicate me the right value for the Rotation to well calibrate this sensor. Thank you!

Oke, so it worked! The issue was this in the installation script it is described that there must be create a directory not the file in the /usr/local path which is called sbin ... but every time it will create a file instead of creating a directory. I manually created the directory as per script and then the script will easily install and copy its required files and the services will works properly. We have tested the function with Virtualhere, and they work perfectly! Now we encountered one extra problem, but I will go and start a new topic for this.

@amitga The only thing we use over the B2B on our add-on boards is USB 2.0 and some GPIO. If you give us some idea of what you are trying to accomplish we may be able to offer some suggestions.

Understood. Thank you again!

@Chad-Sweet Hi, the utility shows the same CPU usage if I add usr & sys.

For VIO use voxl-inspect-qvio For GPS use voxl-inspect-gps The source code for those is here

Is this a custom setup? If so, my first guess would be that the extrinsic pareters between camera and IMU have not been set Check out the debugging section in this document https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

@Chad-Sweet so we find the problem it was the rubber dumpers that we put to hold the voxlflight , it seems that they were too soft and added vibration to the board . we took them out and the problem solved. do you have recommendation about required suspension/vibration absorber for the board? or there is no need ?

Those services look correct. voxl-vision-px4 is the main service that would be routing MAVLink packets from a network interface into the flight controller

I'm not sure if you can have 2 slaves join the same network. From my understanding these modems only support 1 master and 1 slave

The list of supported camera configurations is here I think you would want to run a second qvio-server and merge the results in vvpx4 You could use one of the stereo sensors for that today and point the tracking sensor in a different direction

It is glued to hold the focus. Turn gently, but forcefully, and the glue will break

So, here is how we solved our issue. Even though EKF2 bitmask was set to only listen to GPS, heading still appeared to take VIO into consideration. After turning off VIO on VOXL we got MUCH better readings. Then, after we realized this, we changed out bitmask to 329 (which is in the instructions for flying outdoors without GPS here: https://docs.modalai.com/flying-without-gps/ So, our problem appears to be resolved right now. We just need to test repeatability for this solution

@Chad-Sweet I could`nt access odometry data via telemtry.