Hello,
precision of velocity estimates “vx”, “vy”, “vz” seem to be limited to 2 floating point digits (attached screenshot from Mission Planner below). Is there any way or any parameter I can use to achieve higher precision?
It is important for me, because I use the measurement for custom algorithm, which suffers from signal spikes due to velocity estimate quantization error.
Those are just the digits displayed in MP
The mavlink message has full floating precision
Than you for your reply!
Actually, I was observing two digits precision after receiving MAVLink message. To make it more explicit I was using dronekit to acquire velocity readings. Your replay was valuable and forced me to dig deeper into dronekit code. What I found out is that dronekit uses GLOBAL_POSITION_INT message to receive velocity, which is then divided by 100.0 to get float velocity readings with 2 digits precision.
What I’ve done is I added a dronekit listener on LOCAL_POSITION_NED and now I have full floating point precision readings.
Thank you!