m500 vio

[sesem738]

[6:33 PM] Wenxi Liu

Hello, team Modal AI

When using your company’s product M500, I encountered the following problems. I hope you can help me with it. Thank you!

Before explaining the problem, I confirmed through voxl-vision-services that voxl-qvio-server is Enabled and Running. But when moving in to the next step, I encountered the following problems.

1. The voxl-qvio-client command cannot be used in guide m500 VIO.

2. The obtained T_imu_wrt_vio drone coordinates cannot be transmitted to the MAVLink inspector ODOMETRY.

3. Follow the website guide to PX4 Parameters (https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master), How do I identify what is causing the coordinates to fail to transmit and, when we find the problem causing it, where and what command should we put in, in order to change the setting?

Appreciate!

[Chad Sweet]

Thanks for pointing out the outdated docs, it has been fixed

Have you looked at the Troubleshooting VIO page?

[José Quintanilla]

@Chad-Sweet Hi Chad, I think I am into a trouble similar to Wenxi LiU.

It appears to me that qvio server is enable and running but, when trying to check odometry in QGC or even with voxl-inspect-qvio, all the T_imu_wrt_vio(m) data is in 0 even when moving the drone. In QGC it appears the XY coordinates are in absolute 0 and Z with an offset os 10 meter, it appears to be a -10.9 coordinate while it hasn't moved at all. I tried to open the link you attached to the answer but the page is down. Is it another page or someone that could help me to troubleshoot this problem?

Regards,