MAVLink Odometry X Y value 0

Kris · 1 Sept 2022, 17:23

I unplugged the GPS from the Seeker. I am still not able to get position control in MAVLink and my Odometry x y values are still at 0.
Maybe the last option to do is to re-calibrate my cameras...

Chad Sweet · 1 Sept 2022, 17:26

If voxl-inspect-qvio shows functioning VIO data, there is no need to calibrate cameras. VIO is working. PX4 is most likely misconfigured.

If you have a GPS, then you likely have a magnetometer?

Seeker should have arrived pre-configured for VIO flight. No need to change anything. VIO is flight tested for 20 minutes before being shipped.

Kris · 1 Sept 2022, 17:27

@Chad-Sweet

Kris · 1 Sept 2022, 17:33

@Chad-Sweet
Yes, I have this GPS/Magnetometer that is on the back of the Seeker above the battery compartment.

If my PX4 is possibly misconfigured, should I just remove PX4 and start clean?
Or, is there something you might know that could be causing the problem in PX4?

Chad Sweet · 1 Sept 2022, 17:41

Here are the default Seeker parameters for PX4 1.11

Here are the helper parameters for Seeker indoor VIO flight

Kris · 1 Sept 2022, 17:44

@Chad-Sweet Thank you
I will load these into PX4 and test it.

Adrian Hidalgo · 1 Sept 2022, 17:48

@Kris Can you post a pic of QGC under MavLink Inspector, go to the tab that says Local_Position_Ned and see what the X, Y, Z show. I want to verify how those numbers are numerating.
Normally if the X & Y are zeroed out, VIO hasn't started yet or has blown up. A power-cycle can fix this, but I would think you've already attempted that. Looks like you've already attempted resetting voxl-vision-px4 & qvio.
You may want to try reconfiguring mpa:

voxl-configure-mpa -p -f seeker -b blue -c 7 --fc yes

Power-cycle afterwards. You'll have to set your qgc-ip again since mpa will reset it to factory.

Kris · 1 Sept 2022, 17:58

@Adrian-Hidalgo
Ok, I will try that now.
My position is still being rejected after resetting PX4 and loading the new paremeter files.

Kris · 1 Sept 2022, 18:00

@Adrian-Hidalgo
I have actually reconfigured mpa before, but I will try it again after I have loaded these new PX4 parameters.

Kris · 1 Sept 2022, 18:13

@Adrian-Hidalgo
Unfortunatly that didnt work either

Kris · 1 Sept 2022, 19:10

@Adrian-Hidalgo @Chad-Sweet , Is there anything else you would like to look at on my end or something else I can try to resolve this issue?

Adrian Hidalgo · 1 Sept 2022, 19:30

@Kris what version of PX4 are you using?
This forum may have similar issues and it was resolved by updating PX4

Kris · 1 Sept 2022, 19:33

@Adrian-Hidalgo I honestly don't remember which one I installed. Could you please remind me how to check for the version?

Kris · 1 Sept 2022, 19:35

This post is deleted!

Adrian Hidalgo · 1 Sept 2022, 19:36

@Kris select the Q, should say in the menu selection below application settings

Adrian Hidalgo · 1 Sept 2022, 19:38

@Kris you could try loading a previous sys-image & sdk. Did it work before updating?

Kris · 1 Sept 2022, 19:39

@Adrian-Hidalgo I have not had it for very long. I have not gotten it to work before.

Adrian Hidalgo · 1 Sept 2022, 19:47

@Kris all Seekers get test flown before shipping to validate functionality. They are loaded with VOXL Platform 3.3.0-0.5.0, test flown with px4 platform 1.11 seeker & helper files for seeker ekf_2_indoor & spektrum_dx6e_config.
You can try loading the platform 1.12 seeker to see if that helps

Kris · 1 Sept 2022, 19:48

@Adrian-Hidalgo

I dont see where the version is listed.
Also, this message keeps popping up everytime I open QGC, about a newer version.

Adrian Hidalgo · 1 Sept 2022, 19:48

@Kris in the page, scroll to the bottom