Open brucecrevensten opened 10 years ago
To be a bit more clear about this, there's two places where we've seen jank. One is more serious than the other.
Possibility in the case of (1): sending so many consecutive messages to the platform may be confusing the autopilot (or even overwhelming it). As a part of trying to fix this issue we could try changing the alt control so it's just "enter a number" -- just for a hack, that's terrible ux, but completely removes possible problems due to the rate of messages getting sent.
(2) Could just be the nature of the beast. To test, we'd need to do some comparisons to using Guided mode on Mission Planner and see if it's an APM issue or what.
A likely gaggle of references, with this one being dead on:
https://github.com/diydrones/ardupilot/issues/879 https://github.com/diydrones/ardupilot/issues/1092
29Oct14 Test Flight
Expected Results:
Actual Results:
Notice the yaw jank. Red is destination yaw, green is actual yaw. Notice the destination yaw is set to some value, and then immediately changed to another value that is slightly off.
The same happens in pitch, but it also has noticeable lag
Roll, however, is not showing the same jank, but it is lagging quite a bit.
i'm wondering if the autopilot is amending the yaw command. since our gcs is not explicitly sending yaw commands, only destination x,y coords, i hypothesis it is occurring within the autopilot.
the lag displayed here can be attributed to physical system lag, in that yaw is more responsive naturally than pitch or roll.
We need to also look at any implementation of "follow-me" mode in other ground stations to see if we're not sending optimal messages. The other thing to follow up on here is to generate the same graphs after switching to ArduCopter V3.2+ to see if there's jank and/or same behavior.
Finally ready to test this on 3.2.1 in flight! We'll keep eyes open but expect it to be OK. Close after test flights.
Possibility when changing altitude: it's giving it very slightly different x/y so it wants to "spin" around or something. Maybe that's also the problem with guided waypoints.