MAVLink Odometry X Y value 0

[Kris]

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

Here are the default Seeker parameters for PX4 1.11

Here are the helper parameters for Seeker indoor VIO flight

[Kris]

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

[Adrian Hidalgo]

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

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

[Kris]

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

[Kris]

@Adrian-Hidalgo
Unfortunatly that didnt work either

[Kris]

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

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

[Kris]

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

[Kris]

This post is deleted!

[Adrian Hidalgo]

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

[Adrian Hidalgo]

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

[Kris]

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

[Adrian Hidalgo]

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

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

@Kris in the page, scroll to the bottom

[Adrian Hidalgo]

@Kris wouldn't hurt to update QGC with the latest

[Kris]

@Adrian-Hidalgo Oh, ok sorry.

[Adrian Hidalgo]

@Kris yeah, that's an older version of QGC. Would recommend updating, could be a mismatch of settings.
After updating, check again local_position_ned
If that doesn't work, try loading platform 1.12 seeker parameters
If that doesn't work, try I'd shift to system_image 3.3.0 to see if that would change it. Be sure to save the data partition when asks to wipe.