ArduPilot
autotest: add ScriptingFlyVelocity autotest
~~This demonstrates a problem with set_target_velocity_NED() where request in m/s are showing up as 100x in the log~~ this is an issue with GCS display, but the test is still a good one as there are no autotests currently for these scripting functions.
I can't fault the code here.
It's logging the demand correctly in cm/s - units are correct, multiplier is correct.
It's working just the same as other things in the same like CTUN.CRt , for example.
I think you might be expecting MissionPlanner to automatically scale into units you like? It's absolutely possible for MissionPlanner to magically scale into units you want (eg. degrees from radians, metres/second from cm/second) - but I don't think it ever did that?
When you graph this in MissionPlanner, does it label the axes incorrectly or something? eg. stating something is in metres when it is clearly logged in cm?
