DJI Mavic, Air and Mini Drones
Friendly, Helpful & Knowledgeable Community
Join Us Now

mavic pro sys warn check app help

seama

Member
Joined
Jun 16, 2021
Messages
8
Reactions
0
Age
79
Location
uk
i purchased mavic pro off someone yesterday and now as i went into flight i get this error message. the app stopped responding so i get the drone back manually luckily it was on site as a return to home did not kick in also even i pressed a button on control it will not do it.
i pressed auto land it will not land it will hover i pressed down on the joystick and it landed.

i got the log files can someone help tell me what to do to fix it.
 

Attachments

  • DJIFlightRecord_2021-06-16_[21-20-18].txt
    1.5 MB · Views: 7
i purchased mavic pro off someone yesterday and now as i went into flight i get this error message.

That sucks (disappointing), why / how do people do this to others ?

I hope you get it resolved, as it's a great little aircraft still, even now nearly 5 years since release.

Seems to be a couple of issues.

RTH didn't work pressing the button on the controller, even though you could manually fly it home ?
Were settings configured in the app ok ? This sets that function on the drone itself, so it SHOULD work if the controller is in signal with the M1P.

The app not responding COULD be a bad cable between device and controller.
Very common thing to happen.
 
That sucks (disappointing), why / how do people do this to others ?

I hope you get it resolved, as it's a great little aircraft still, even now nearly 5 years since release.

Seems to be a couple of issues.

RTH didn't work pressing the button on the controller, even though you could manually fly it home ?
Were settings configured in the app ok ? This sets that function on the drone itself, so it SHOULD work if the controller is in signal with the M1P.

The app not responding COULD be a bad cable between device and controller.
Very common thing to happen.
1:if you look through the second link I posted go through the timeline. i have large numbers of YAW errors.
I will need to calibrate the remote and craft again and fly it low near me till the end of the battery so i know everything works ok.

2: I started flying high. then i flew around and started getting the sys to warn check app. at this time app stopped responding no live camera feed. I restarted the app even disconnected the wire and fit back on nothing. i didn't want to turn the controller power off.
so as off from now app did not respond the return to home did not kick in maybe because the controller was still on.
but when i got the drone near me i pressed land it did not work.

3: now that I did a little calibration on 2nd flight the app worked but am sure the error is not gone yet as i did not calibrate it fully.

I need your assistance on this, want to know the cause of the error and how to fix it according to the log file.

To take off in non-P mode, toggle Flight Mode Switch to another mode and then toggle it back.
so what mode normally should i fly in ?
 
Mmm ... something happens there up on 178m height 607sec into the flight ...

1623927764201.png

At 607sec we see a "Yaw error Large" in the log, half a second later the navhealth drops to zero & after further 1sec the AC goes into ATTI mode with 16 sats still locked in. This state continues to 627sec & at 642 all signs of this event is gone & the navhealth is up on 5 again.

Looking at the velocity differences between the IMU & GPS of course show a huge difference during the ATTI phase ... but the differences are really larger in other places during this flight also which could indicate HW related causes to this..

1623928243213.png

Would be interesting to take a look at the corresponding mobile device .DAT log for this flight ... the .DAT for this flight ends with FLY127.DAT. Read up here on how to retrieve (read under section 3.) --> Mavic Flight Log Retrieval and Analysis Guide attach it then in a new post here.

The unresponsive GO4 app is most probably unrelated to this ... sounds like it crashed & froze, that's why you couldn't use app commands to land. And no failsafe RTH could have been triggered in this case, you didn't lose the connection between the AC-RC.
 
were do i get the log from the mobile device.
s20 ultra.
i will look up google how to and if i can il post it here.
 
i hope this is the one your after sir. if not il look into it more. its from the phone. does logs be in the controller as well?

download
so we investigating for the date yesterday which is 16/6/2021



google earth
import the kml to google earth. attachment kml
 

Attachments

  • Jun-16th-2021-09-20PM-Notifications-Airdata.zip
    137.2 KB · Views: 2
Last edited:
were do i get the log from the mobile device.
If you follow the link that I provided in my post #7 just below the chart ... & there read up under section 3. (how to retrieve...), you have there a chapter that points out where you find the mobile device DAT log in the phone you flew with.

The correct DAT log ends with FLY127.DAT ... it's only that one we can use, it will let us access the raw sensor & motor data from the flight, which aren't included in the .TXT log you provided in your initial post.

i hope this is the one your after sir.
Unfortunately it's not ...
 
  • Like
Reactions: seama
no fly127 i cant find. i got fly128

what about this data are you able to se it. if you scroll down you can se a lot of yaw errors.

what worried me about the flight is bringing it back home without eyes on-screen or cam. luckily it was in my sight.
the remote was on so maybe the return to home did not initiate while app crashed or said sys warn check app while app was disconnected even i removed the wire and connected nothing. so had to manually land it.



Flight timeAltitudeHome Distance
Minor Signal
Errors​
Calculated Signal​
A00m 30s188.3 ft 82 ft
0​
100%​
B01m 00s408.1 ft 80 ft
0​
100%​
C01m 30s407.5 ft 79 ft
0​
100%​
D02m 00s430.1 ft 83 ft
0​
100%​
E02m 30s565.0 ft 362 ft
0​
100%​
F03m 00s579.4 ft 479 ft
0​
100%​
G03m 30s579.4 ft 737 ft
0​
100%​
H04m 00s585.3 ft 743 ft
0​
100%​
I04m 30s585.0 ft 515 ft
0​
100%​
J05m 00s585.6 ft 565 ft
0​
100%​
K05m 30s585.6 ft 541 ft
0​
100%​
L06m 00s585.3 ft 447 ft
0​
100%​
M06m 30s585.0 ft 106 ft
0​
100%​
N07m 00s585.3 ft 303 ft
0​
100%​
O07m 30s585.3 ft 510 ft
0​
100%​
P08m 00s585.6 ft 688 ft
0​
100%​
Q08m 30s585.3 ft 797 ft
0​
100%​
R09m 00s585.3 ft 847 ft
0​
100%​
S09m 30s585.3 ft 559 ft
0​
100%​
T10m 00s585.6 ft 284 ft
0​
100%​
U10m 30s503.6 ft 474 ft
0​
100%​
V11m 00s404.5 ft 271 ft
0​
100%​
W11m 30s205.4 ft 158 ft
0​
100%​
X12m 00s164.7 ft 115 ft
0​
100%​
Y12m 30s164.7 ft 116 ft
0​
100%​
Z13m 00s102.4 ft 75 ft
0​
100%​
a13m 30s18.4 ft 13 ft
0​
100%​
b14m 00s17.4 ft 10 ft
0​
100%​
c14m 30s3.6 ft 7 ft
0​
100%​
d15m 00s19.0 ft 7 ft
0​
100%​
e15m 30s33.8 ft 7 ft
0​
100%​
f16m 00s20.7 ft 7 ft
0​
100%​
g16m 30s5.6 ft 6 ft
0​
100%​
h17m 00s6.2 ft 10 ft
0​
100%​
i17m 30s5.9 ft 7 ft
0​
100%​
j18m 00s0.7 ft 7 ft
0​
100%​


anyways i will fly again i calibrated the controller. i need to calibrate the craft .and repost the data log thanks.
 

Attachments

  • 21-06-17-06-12-41_FLY128.zip
    240.6 KB · Views: 3
Last edited:
no fly127 i cant find. i got fly128
No, what we need is FLY127 ... FLY128 is only a 101sec power on sequence without motors on.

what about this data are you able to se it. if you scroll down you can se a lot of yaw errors.
Yeah ... I saw it already in the mobile device .TXT log you attached & it's seen in the chart I included in post #7 (the colored area is ATTI mode + Yaw error Large) In order to dig into the reasons for ATTI & the yaw error we need access to the raw sensor data from the correct DAT log.

the remote was on so maybe the return to home did not initiate while app crashed
As long as your RC is connected with the AC no failsafe RTH will be triggered ... it's not enough that the app crashes for it to happen.
 
Suggest reinstalling the app and rebooting the phone. If the imu calibration didn’t finish, do it again. Still hoping you can retrieve the dat logs. Good luck on your “new” drone getting to fly safely. Good old bird. Remember RTH only hovers if too close to home. Lands manually.
 
update.
I recalibrated the controller.
imu recalibrated yesterday.
uninstalled DJI go 4 and reinstalled.

I flew the drone till the battery was 30% below and I was flying around my area not too far.
I am going to update this post with new logs of 17/6/21 can you kindly check and test to see if any of the calibrations have fixed anything.

so I need help with checking todays logs after I calibrated and check to see if everything looks ok in-flight or any errors.
 

Attachments

  • logs.zip
    9.1 MB · Views: 5
update.
I recalibrated the controller.
imu recalibrated yesterday.
uninstalled DJI go 4 and reinstalled.

I flew the drone till the battery was 30% below and I was flying around my area not too far.
I am going to update this post with new logs of 17/6/21 can you kindly check and test to see if any of the calibrations have fixed anything.

so I need help with checking todays logs after I calibrated and check to see if everything looks ok in-flight or any errors.
No problems on the flight? If all good, you solved it! Logs should prove that as well. Happy flying.
 
  • Like
Reactions: seama
No problems on the flight? If all good, you solved it! Logs should prove that as well. Happy flying.
can you still double-check the logs to see if am good to go?
some times I get nervous when I see a notification saying something about GPS weak or loss that says using GPS again.
Mavic Pro is able to travel 3miles without obstacles on its path but I was only flying not too far and I sometimes get messages. can you check if everything looks ok?. the last thing i want to do is fly over water and something happens.

my video recording sometimes gets little dark-like brightness. is it the iso I need to tweak?
i also fly in beginners mode. if i put it in another mode will the drone auto-balance itself from wind?
 
FLY026.DAT is the correct .DAT. Don't know why the .txt has the correct .DAT as FLY027.DAT.

Unfortunately, no further insight into the problem can be seen in FLY026.DAT. At least, I'm unable to see anything.
@slup
 
FLY026.DAT is the correct .DAT. Don't know why the .txt has the correct .DAT as FLY027.DAT.
That's strange ... but noted that it actually was some confusing references in other logs that was up here, think it was FLY030.DAT vs. the .TXT that clearly was the correct & corresponding flight, but that .TXT said FLY031.DAT ... if I'm remembering correctly.

Also missed the FLY026.DAT in all confusing uploads by the OP ... didn't have time to in detail go through them all.
 
Lycus Tech Mavic Air 3 Case

DJI Drone Deals

New Threads

Forum statistics

Threads
130,592
Messages
1,554,181
Members
159,596
Latest member
da4o98