Weird behaviour shortly after takeoff...

I have never worked with .DAT files so if i dont have this right just let me know.
Her is my flight from a few days ago.
Dropbox - FLY169.DAT
I think I've figured out the problem. There isn't a motorStart:). Looks like you got the wrong .DAT. The bottom half of the page here has some info about getting the right .DAT. Good luck.
 
@NiallxD that .DAT corresponds to the .txt you provided. But, neither of those correspond to the Go App screen shot in your first post. Is that right? Do the two log files correspond to the HealthyDrones screen shot in the first post?

I'm not real confident on this one but I'm going to guess that the root cause of this problem is the uplink signal strength is low. I noticed you mentioned something about switching back to stock antennas in one of your posts.

Looking at the eventLog stream in the .DAT the P3 lost connection with the RC several times begiining at about 208 secs
208.958 : 225193 : 18557 [LED] changed: rc completely lost
209.958 : 225793 : 18607 [LED] changed: normal led
219.198 : 231337 : 19069 [LED] changed: rc completely lost
222.758 : 233473 : 19247 [Ctrl<8>] REQ_RC_LOST AUTO_LANDING_HOLD ctrl_auto_landing
222.913 : 233566 : 19254 Eeprom write offset:330
226.798 : 235897 : 19449 [LED] changed: normal led
234.498 : 240517 : 19834 [LED] changed: rc completely lost
237.098 : 242077 : 19964 [LED] changed: normal led
240.178 : 243925 : 20118 [LED] changed: rc completely lost
243.978 : 246205 : 20308 [LED] changed: normal led
247.058 : 248053 : 20462 [LED] changed: rc completely lost
252.258 : 251173 : 20722 [LED] changed: normal led
261.498 : 256717 : 21184 [LED] changed: rc completely lost
263.618 : 257989 : 21290 [Ctrl<10>] REQ_RC_GO_HOME AUTO_LANDING_HOLD ctrl_auto_landing

At 222.8 the .txt seems to be saying the same thing as the eventLog stream when the autoLand is commanded because of the lost connection.

The following plot shows what the P3 thinks the RC mode switch is set to.
View attachment 66818
The blue areas are where the P3 thinks the mode switch is in the A position. I don't think it's physically possible for the switch to change positions this fast. There must be some other explanation.

As I mentioned I don't find the foregoing to be very compelling. I suggest that you restore the stock antennas and try the same flight but put some horizontal distance between the RC and launch site. If you still have the same problem I'd ask DJI to look at the log files.

Hey Bud, tried flying with the stock antennas to no avail.

Loosing control at only about 5 feet away and 8 feet up. Any other ideas?



Sent from my iPhone using PhantomPilots
 
Hey Bud, tried flying with the stock antennas to no avail.

Loosing control at only about 5 feet away and 8 feet up. Any other ideas?



Sent from my iPhone using PhantomPilots
Sorry, I don't have any more ideas. Maybe it's time for a trip to DJI repair.
 
  • Like
Reactions: phantomflyer22

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,066
Messages
1,467,352
Members
104,933
Latest member
mactechnic