https://github.com/PX4/PX4-Autopilot/pull/19618

This now the only thing I get. So there is no intrinsics or extrinsics files for right/left/stereo & tracking. I will do the camera calibration then. Thanks

Where can I find local_position_ned?

Or is it this?

We have the VOXL CAM version with Hires, Stereo & Tracking.
We have uploaded 3.8.0 image with the 0.7 suite.

But this is now the error that I get after doing the following:
voxl-configure-mpa -p -f seeker -b blue -c 7 --fc yes
reboot
voxl-configure-cameras

We updated our VOXL CAM to a newer system image and suite, during the updating we did a clean wipe, removing everything. Now after this clean flash our position lock does not work anymore.

In VOXL we configured the following:
VOXL-configure-mpa / ...exentrics / ... vision-px4 / ... cameras.
Everything as a standard VOXL CAM v1/ seeker.
But still it doesn't work.

If we look at voxl-inspect-qvio, its says OKAY. And if we walk around it will also work just fine. I notice that over time the values get weird and will reset itself.

If we look at the mavlink message Odometry they are not very normal. They are staying at around 0, x and y are just 0 and doesn't change when walking around. And the others do all kind of crazy things, so I think that is why it also won't go into Pos Lock.
EKF2_Aid_mask is 280, of course!

Is there something we are missing? Do we need to perform some calibrations? The VOXL-inspect-QVIO isn't asking for it.

https://github.com/PX4/PX4-Autopilot/pull/19618

Thanks!!

Where can I buy replacements or just new vibration dampers that are on the VOXL CAM for the Seeker drone?

Thank you for the response! I didn't have time to look into this yet. But there is more going on with the system I think. WIFI also doesn't work anymore. And after trying to solve the WIFI, the ADB of the VOXL stopped working. So we for now we are using a different VOXL.

Something else we are running against is the message Reject position control, with working VOXL CAM systems installed on our drones. When we fly everything is super! When we land, after the drone has bumped into things while flying (drone is collision proof) or when heavy wind was pushing it. We cannot take off after landing, it will display Reject position control. Only when the we connect a laptop to the QGC, we can hear that the VOXL reboots and then the Reject position control is gone, and we can go fly again. But if we use QGC via the PX4 Telemetry port, this doesn't happen, and we need to unplug and replug the battery to be able to get the Reject position control message away again.

We don't really know why this happens and how we can solve this. It would of course be great if the VOXL didn't need to reboot in order the drone can fly again in position mode. But it already would be helpful that the VOXL would reboot without having to have WIFI connection with QGC. Please help!

We have flown the Seeker drone up to 4 hours maybe and everything with the VIO and position hold worked good. I did all the updates (v0.5.0) on the VOXL to get the voxl-mapper to work and it did work. In my thoughts it even worked with the VIO. Sometimes I did have Reject position control on QGC, but than I restarted the Seeker and I could fly in position mode again. But for some reason it keeps giving me the Reject position control, and now I am not able to fly in position mode anymore.

I did quite some troubleshooting -> voxl-configure-excentrics/ camera/ QVIO/ PX4 etc. all of that I did do that make sure the VOXL was correctly set.
I also checked if the FC got any Odometry data, but it did not get any of VOXL. At least I could not see the data with the mavlink inspector. It is weird, because I didn't change anything on the FC itself.

We really need it go back up in the air for some more testing! Any idea???

I want to create a static IP Address on eth0.

Now we have added an custom IP link to the USB 2.0 port of the USB expansion board via an ethernet to USB adapter. This works perfectly following the regular link: https://docs.modalai.com/usb-to-ethernet-with-voxl/

But our custom IP link will only work with IP address 192.168.144.20 to 192.168.144.24

Last Monday I got the eth0 to this IP address via changing /etc/network/interfaces to:
IP: 192.168.144.20/24
Mask: 255.255.255.0
Default gateway: Leave open

And everything worked perfectly and I was happy. Even for a couple of times restarting the system.
But today it doesn't work anymore, it's back again changing the IP address of eth0 to whatever suits the VOXL best. Was this the best method to change the IP address on the eth0? Or is there something wrong? And how can I change this on a better way?