Android 141 beta test - feedback 2 - Drone too far off course
So pretty sure this has nothing todo with the beta test however I want to get a confirmation,
Basically today we are getting 20-24mph wind gust at 300 feet SW-S-SE Direction
I ran two mapping missions to test out and put beta test to the test with a max speed set to 21-22 mph Altitude set to 285 When I ran the first Mission the grid was facing East to West same general vicinity as 2nd mission. I don't think the 1st mission ran into errors because it was catching wind from the side so the drone wasn't really slowing down too bad.
Now to the specifics, During the first mission no errors at all the second mission had the same settings but was facing North to south during this mission I got errors when it was trying to go north the error read as put "Drone Too Far Off Course: D 75 ft" After several times I aborted the mission landed the drone and reset the app and booted everything back up and re-started the mission, and got the same thing.
I then Read up motion tolerance could be too low so I then set the motion tolerance distance to 115. Re-did the mission it then would get the same error "Drone Too Far Off Course: D 116 ft"
So I kept resuming the mission thinking it was a possible bug in the app, however, after it started heading south after the first grid, no errors at all! It then got the same errors heading north again, same result back south no issues.
At this point I am thinking it was the result of the wind even though the drone wasn't really blowing all over I think the drone's speed was too low coming north due to the wind so the drone got behind in the apps eyes because it was 115ft behind then the plan said it should be because of the wind slowing it.
Correct me if I'm wrong but this isn't a bug just the fail-safe doing it's job? If i'm correct, if I set the speed down to what it could achieve even with wind then it wouldn't spew an error OR if you turned motion tolerance way up so it wouldn't get behind in the mission eyes it would just take longer due to fighting the wind? Because the Mission is estimated to take 9m10s it however took 13m19s
Jim McAndrew My explanation may kind of suck but it this the general gist of it?
Thanks so much!
EDIT: I apologize if it is the simple issue I think it is however I am looking for a confirmation so I can plan missions better in less than perfect weather. Thanks!
Comments
6 comments
Yes it is wind. Slow it down.
Thanks for the quick reply, I thought it was and is it because it got further behind then the App thought it should be?
Yes
Jim McAndrew Sorry to bother you with another possible issue however I think this is a web app issue unless I am looking over something.
Same Plan I was working with yesterday - I have the max speed for the mission set to 30mph for the mapping I left blank which automatically selected 30mph of course, however, In the mission preview after the plan starts it says 21mph is the max speed if I set the speed for the mapping component to 18 mph in the preview it only gets to 14mph and if I set 14mph it goes to 11mph and so on, my point is the speed portion seems to be off for some reason? Am I looking over something or is this an issue?
The max speed setting in maps is just that, the max speed it can use. Depending on the camera, overlaps, altitude, and time interval chosen, the algorithm will choose the fastest speed that is less than the max speed and still solves for all the other parameters.
Oh okay that makes sense. Thank you so much I was just confused about that. Thank you!
I am really loving this app I cannot wait to see what comes, keep up the good work it has been working great.
Please sign in to leave a comment.