Writing mission with high precision waypoints using mavproxy

**danielh** · September 10, 2019, 7:39am

Hi,
I am not sure if this is an ArduCopter, mavlink or mavproxy issue.
I am using mavproxy to load a mission to ArduCopter (tried 3.6.7 -3.6.10).
My waypoints are of high precision (cm accuracy, so 7 about decimal places). When the waypoints are loaded, the mavlink messages displayed on the console are correct. However, when I read the waypoints using wp list, the waypoints are only correct to the first 4 decimal places.
I would think this is because the mavlink message fields for lat and long are float32 (and I require double precision) yet, when loading the same mission from mission planner, the waypoints are loaded correctly.
Any ideas?

Thanks!

**stephendade** · September 10, 2019, 8:12am

Could you post some screenshots or console output?

**danielh** · September 10, 2019, 9:32am

Sure:
btw, I see was mistaken before - it’s the sixth decmal place that is wrong:
The waypoint file:

wp load:

wp list:

It looks like it must be some float to double conversion that is botched up somehwere, but where?

**danielh** · September 10, 2019, 1:54pm

Mission planner uses mission_item_int. I guess mavproxy does not.

**peterbarker** · September 11, 2019, 1:03am

That’s correct. It’s also going to change

**danielh** · September 11, 2019, 4:01am

Any estimate as to when this will change?