Closed andrewmoni closed 10 years ago
@andrewmoni which version of DP are you running. The issues with the incorrect messages should have been fixed with the 2.7.4 beta release.
OK - u got me!! Thought I was on the latest - am running 2.7.3 RC1 - will wait for the update to come through to me. Sorry.
On 11 September 2014 07:18, Fredia Huya-Kouadio notifications@github.com wrote:
@andrewmoni https://github.com/andrewmoni which version of DP are you running. The issues with the incorrect messages should have been fixed with the 2.7.4 beta release.
— Reply to this email directly or view it on GitHub https://github.com/DroidPlanner/droidplanner/issues/1060#issuecomment-55217612 .
No problem :) The latest update can also be downloaded from github: https://github.com/DroidPlanner/droidplanner/releases/tag/Droidplanner_v2.7.4_RC1
Just tried 2.7.4.RC1. Although I appeared to have far few of what I called 'false' alerts (cannot recall if I had any) - the waypoint being announced now appeared to be TWO out rather than one - and even ended up going for waypoint 9 when waypoint 8 was RTL - there was no waypoint 9. So 2.7.4 seems to have helped one part and made another part worse.
On 11 September 2014 07:18, Fredia Huya-Kouadio notifications@github.com wrote:
@andrewmoni https://github.com/andrewmoni which version of DP are you running. The issues with the incorrect messages should have been fixed with the 2.7.4 beta release.
— Reply to this email directly or view it on GitHub https://github.com/DroidPlanner/droidplanner/issues/1060#issuecomment-55217612 .
@andrewmoni Do you mind sharring yout mission-file? OR the log via droneshare?
Just loaded the mission from the drone back into MP - and what seems to happen is that DP is oblivious to the change speed, so all waypoints shown in DP are out by 1 anyway. My RTL WAS at waypoint 9. I suspect it may be the spline waypoints that are confusing DP in addition. So, the annunciation of waypoints was POSSIBLY correct according to the mission stored on the drone, but not correct according to the numbering shown within DP (since DP ignored the do_change_speed). I think the do set ROI has also caused a misnumbering of waypoints on the DP screen - but they are correct within the mission.
On 11 September 2014 07:18, Fredia Huya-Kouadio notifications@github.com wrote:
@andrewmoni https://github.com/andrewmoni which version of DP are you running. The issues with the incorrect messages should have been fixed with the 2.7.4 beta release.
— Reply to this email directly or view it on GitHub https://github.com/DroidPlanner/droidplanner/issues/1060#issuecomment-55217612 .
Here is a link to logfiles and the mission plan txt file https://drive.google.com/folderview?id=0By58QJ60bmMRYXA5dGctQTlBQk0&usp=sharing
On 11 September 2014 09:07, Arthur Benemann notifications@github.com wrote:
@andrewmoni https://github.com/andrewmoni Do you mind sharring yout mission-file? OR the log via droneshare?
— Reply to this email directly or view it on GitHub https://github.com/DroidPlanner/droidplanner/issues/1060#issuecomment-55223510 .
Using DP to provide audio alerts for battery and other warnings I got the distinct impression that DP was announcing "going for waypoint 5" when actually it had just started going to waypoint 4. This continued throughout the flight - it appeared to be one out. The mission contained 1 DO CHANGE SPEED and one DO SET ROI - either of which could have been the cause of the incorrect numbering. My suspicion woud be the DO SET ROI as that does not create an actual waypoint per se. Also whilst flying I had continual lost lock, got lock, disarmed, armed messages being spoken to me - the route was flown flawlessly however with no hesitations - so I find it very hard to believe these were genuine lost locks and disarmings (these must have been false as I was flying!!). I was running APM 3.2 but had the same continuous misleading stream of commentary with 3.1.5