ArduPilot
uas: In AC4.0.0 or later, automatic flight plan display, update, writing, and reading are not completed.
I used a master containing #1207 to check the automatic flight plan reading from the AC4.0.0 release version. At startup, T YPE is set to an indefinite value for list acquisition and WP acquisition, so it is not displayed.
I was able to show it at startup by making the same fix as #1207.
=== However, when the WP becomes too much, a timeout occurs and the game is finished in the middle. So, by increasing the timeout time and the number of retries, we received all the WPs.
What should I do about this time and frequency value? #define PROTOCOL_TIMEOUT_MS 180000 //2000 ///< maximum time to wait for pending messages until timeout #define PROTOCOL_MAX_RETRIES 90 // 5 ///< maximum number of send retries (after timeout)
I will try to reproduce this issue tomorrow - but I think a timeout of 2 seconds and a retry of 5 should be enough. You are using macOS 10.15.4 aren't you? I am pretty sure this problem relies on the macOS version - 10.15.4 is known to have a lot of network problems. If you have a Mac which has an older macOS version - at least 10.15.3 - it would be cool if you could try to reproduce the problem. If not we should wait until the next macOS release.
I was not able to reproduce this issue with 32 waypoints. Writing and fetching works without any problems. It seems the problem is related to macOS 10.15.4.
@muramura we have a new release candidate for macOS. Perhaps you want to test it :smiley: You can find it here: https://github.com/ArduPilot/apm_planner/releases/tag/2.0.28-rc1
10.15.4 is known to have a lot of network problems
I haven’t experienced any network issues on macOS. Or is this related to Qt 5.9.3?
I work for a company which produces cameras for industrial purpose. Among several special frame grabber interfaces we produce GigE and USB cameras. Since the update to 10.15.4 a lot of customers have heavy issues when using GigE cameras especially with timeout handling and packet loss. We still hope that those issues are fixed with the next update.
Does this problem still exist? Otherwise I will close this issue in the next days