M3P, Signal loss, RTH had to manually be activated
Mini 3 Pro
Samsung S20FE Android 13
4.8.3 (280) Kernel 4.8.1
Searching previous posts, nothing current popped up as to what I experienced so hopefully this is unique to this build? Mission planned with RTH as action when completed. Early during mission today signal was lost and drone came to a hover and switched to manual flight mode. It hovered for a few minutes while I double checked settings and I had to manually select RTH. What did I miss?
Edit: RTH for signal loss was selected in DJIFLY.
https://youtu.be/4Mk-GkNNFHo?si=wZwZlqt-F4xaTirF
Comments
9 comments
Sounds as though you've got it set to hover in case of signal loss, check what's set in the DJI app, this setting is stored in the drone
I failed to mention in my original post that RTH was and has been selected for signal loss in the DJI app.
Connection fail-safe is a DJI firmware feature that Dronelink has no control over (if it doesn’t work).
Jim, After reading your comment, I returned to the same location, confirmed ( but did not change) that the DJI FLY app had RTH for signal loss and flew the same DL mission profile, manually with the DJI FLY app. At the expected location/altitude, it experienced RC signal lost and initiated RTH within 10 seconds. After landing at the take off point, I force stopped the DJI FLY app and started the previous mission with DL. Within 15 seconds of arriving at the same signal loss location, DL initiated RTH. I'll update this thread if DL again fails to initiate RTH with signal lost.
A few things.
First. You might be confusing signal loss (which will initiate RTH if set) with low signal, which can cause the mission to pause. You don't show the message that pops up when it stopped so we can't tell what happened, but since to do still have signal that is my assumption.
Second, I would not have APAS turned on. That can also cause problems. Change it to stop instead of avoid.
Best of luck.
Thanks Barry. I was seeing both weak signal and occasionally flashed to RC signal lost, but mostly weak signal was displayed, probably why it didn't RTH until I did it manually. I'll also try APAS to stop instead of bypass and see if that helps.
Also when it disconnects due to signal loss it may be intermittent. So if it disconnects then the DL mission cannot not continue because it needs constant clear connection at all times and it will pause and hover which is normal behavior. At this point It will not initiate the RTH until it has been about 10 seconds of complete signal loss. So if it disconnects and connects back and forth over and over it won’t return. Sounds like you were just at a distance where it was in and out. I’d suggest if it’s that important to launch closer than just under a half of a mile away. Also even if the signal bar has a couple bars that doesn’t mean it has a clear signal. There can be interference within the signal even if it indicates there are signal bars showing.
I think Barry Houldsworth and Mike (Arizona Wyldwest), just about have you covered, to see the exact message that came on the screen when the mission paused, go on to the web app, click on the little clock symbol, then select the mission where you had the problem and you'll see a message similar to this one on the right hand side that is a duplicate ofwhat would have been on the app when the mission paused
I’d suggest using Airdata for the drones logs as it will give you a ton of information which can be easily read. Speed, altitude, coordinates, pitch, satellite amount & strength, distance, disconnection and much more. I think it is obvious why it reacted as it did but having access to more info is a good way to see at what was happening during the flight. There are other ways to check the flight logs but Airdata is so much easier.
Please sign in to leave a comment.