Writing mission with high precision waypoints using mavproxy

ArduCopter
, ,
1

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!

2

Could you post some screenshots or console output?

3

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

waypointFile
waypointFile.PNG958×90 2.07 KB

wp load:

wpLoad
wpLoad.PNG1314×348 54.7 KB

wp list:

wpList
wpList.PNG1316×352 50.8 KB

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

4

Mission planner uses mission_item_int. I guess mavproxy does not.

5

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

6

Any estimate as to when this will change?

7

Any update on this? Just just discovered this issue myself. We have no chance of achieving the accuracy we after with this issue affecting waypoint upload. The error can be in the order of half a meter or so. We will have to look at implementung some alternative upload mechanism…

8

master mavproxy should be fixed.