Can you please assist in figuring out why waypoint upload might have failed multiple times?
From our app it failed, but from flytConsole it worked - and the drone flew the waypoints as expected.
I know link quality again may be an issue - but the flytPi was right next to the remote… In any case, I’m attaching logs, and from one of them I see this error:
e[31m[ERROR] [1524811983.507586202]: WP: upload failed: error #13e[0m
Others are clearly timeouts:
e[33m[ WARN] [1524813678.190336809]: WP: timeout, retries left 1e[0m
We also had another issue where commands were sent twice - this is from our software - is it possible if we send too many commands via REST API that maybe pixhawk is busy and not able to take all of them?
I suspect from flytConsole it worked because there weren’t many commands sent one after another.
Before set waypoints we send: waypoint pause, waypoint clear, only then set waypoints.
If you have idea what error #13 is, please share.
The JSON should be correct, it works with the simulator, no issues.
We are also using REST API for telemetry instead of websocket - every 2-3 seconds we get global location, battery, state, others. Do you think this also overloads the connection / pixhawk?
Logs below (log date is not correct, this was today 4th of May). Thanks for the help.
Also attaching images of the setup (for the last try they were outside- before, the remote, flightPi and laptop were in the trunk, maybe that also doesn’t help). flightPi gets power from the car - via a phone charger that’s rated at 2V 3A - it’s not a power issue this time .