Has anyone simulated or experienced (within sight) a loss of signal with an M2P/Z?

[Deleted member 103366]

I am interested in knowing whether the 'reverse course' thing literally flows the in bound path and speeds?

 

[Cymru]

Ive tested it by deliberately turning off the RC
Mine did an exact backtrack for 60 seconds before giving up and returning.

 

[Deleted member 103366]

That's course and speed?

 

[Cymru]

Course for sure.
Speed is harder to tell - no controller on to read it.
Would need to test that again by deliberately flying very slowly so you can visually see that.

 

[Deleted member 103366]

Thanks.
A slow 'inbound' flight was my thinking too, possibly a circle etc.. I just didn't want to go experimenting 'completely in the dark' as it takes about 15 secs or so to 're'capture the drone and things could go pear shaped in that time.
I wonder would the DAT capture it 'after the event'........

 

[Cymru]

On my RC data it just has no data for that time period (which makes sense).
The drone doesnt resend non-received telemetry for the period.
To test i took it to my nearest sports fields where my "outbound" track were following the pitch lines so several clear 90 degree turns.
This means i could visually see clearly what its path was without access to the screen or FPV.
(and also if it went wrong theres nothing in the area to crash into!).

 

[NG Wildman]

Three times this has happened. All three times it was the exact route. The second time, it seemed to be the same return speed for about 20 seconds or so (I was on my boat and lost while turning around). The 3rd time, however, I took the MP2 out for a quick spin and on the second quick flight I took off from under a building overhang. On the RTH the drone sat directly above the take-off spot which was now under the roof where it hovered till the battery was shot and then landed on the roof (again directly above the take- off spot). With the RTH height at 120', the drone did what it was supposed to and when it hit the proper coordinates, it met the roof about 25' above the take of altitude and that's why it hovered there until battery exhaustion. I was unable to re-establish contact with the drone the whole time...still don't know why...and I tried restarting the RC and the app. Phone is gone now and I replaced the drone with care refresh.

 

[Deleted member 103366]

Thanks.
One point though. if you are thinking that, in the latter flight, the drone hovered because the 'ground' that it saw was at 'altitude' then I doubt that is correct.
The height at which the drone encounters or sees the ground is, I think, irrelevant to the drone, it will simply descends until the 'ground' comes within VPS ( Vision Positioning System) range then slow its descent but continue descending until the descent is stopped by a stationary object.

I suspect that what happened is that the 'ground'/roof came within ranges of the VPS and that the drone 'analysed' the landing site and rejected it, which means the drone hovers until other instructions are recieved or a low battery RTH is initiated but, since the drone was already over the homepoint, it just hovered until the battery was exhausted then landed or whatever.
I see this "landing site rejected" behaviour quite frequently from either or both my M2P and MM if I intiate any form of automated landing in front of my house.