The issue of Mavlink/APM’s use of floats instead of scaled integers (link1) has been brought up before here but never resolved. There is already a framework to fix this by using COMMAND_INT and/or MISSION_ITEM_INT. (see links below) There also seems to be some progress on the 3DR Solo that might also be applicable to APM 3.4. Solo COMMAND_INT / Solo MISSION_ITEM_INT
MISSION_ITEM_INT receiving was added to MissionPlanner a few days ago.
Any help or advice toward an accurate APM would be greatly appreciated.
Increase accuracy of co-ordinates (Replace COMMAND_LONG with COMMAND_INT in general with a translation layer) · Issue #1907 · ArduPilot/ardupilot · GitHub
Adds velocity control to ROI points. by njoubert · Pull Request #2367 · ArduPilot/ardupilot · GitHub
Clarify how to arm/disarm with the common messageset · Issue #426 · mavlink/mavlink · GitHub
How to use COMMAND_INT · Issue #1152 · ArduPilot/MissionPlanner · GitHub
Redirecting to Google Groups
Redirecting to Google Groups