P4 v1. Lost connection. Did not RTH.

Joined
Aug 15, 2024
Messages
8
Reaction score
9
Age
39
I had a phantom 4 but havent used it since early 2018 due to my 2 batteries swelling. After playing with my coworkers drone i felt in the mood to fly again. I looked on amazon but most do not ship here. Finally found one. It was a generic battery. The day i recieved the battery I charged it that night and took it off the charger when done. The first of the 2 test flights went fine. There was a "motor or propeller warning" but seemed fine after take off. I went about 3k feet away and returned. Upon landing i did not turn off drone. The next flight started a couple minutes later. About 1.5 minutes into the flight i switched to atti mode. When reviewing the flight record i notcied that the battery level stopped going down (stuck @ 57%) and the red/yellow/green bar time stopped as well (stopped @ 10:49). At around 5300 feet away i recieved notification "the remaining battery is only enough for rth" followed closely by "low power. returning home." I canceled it and started booking it back home. On the return i lost downlink for 31.8s and then restored. Still in atti mode i was making my back and at 2100 feet away i lost connection and never regained. Battery indicator still @ 57% and bar still @ 10:49. The flight from start to loss of connection was just over 5 minutes. I used "find my drone" and last location of connection but did not find it. Not sure where to look. My home lies just inside restricted zone but was able to take off and fly in it. Where the drone last was and home the restricted zone is in between. Did it try to go around? Did it try to go through? Did it land? Did it drift? Any suggestions? I really need to find this guy. Its been several days already
 

Attachments

  • Screenshot_20240814_201456_Chrome.jpg
    Screenshot_20240814_201456_Chrome.jpg
    1.2 MB · Views: 54
Last edited:
  • Like
Reactions: RodPad
When reviewing the flight record i notcied that the battery level stopped going down (stuck @ 57%) and the red/yellow/green bar time stopped as well (stopped @ 10:49)
Please share the flight log here.
 
  • Like
Reactions: RodPad
Atti mode doesn't use gps so might prove difficult to locate but definitely post the logs to find the cause. Hopefully you marked your drone (RTH for dummies), I lost a Phantom in a hurricane (dumb) but got a phone call and it returned home next day. Hope you find it, start by posting the logs
 
Yes need the logs.


If you need help you will get it.

Also, more info than you probably need at this point.

Rod ..
 
Last edited:
  • Like
Reactions: LOVE NZ and Capt KO
Yes need the logs.


If you need help you will get it.

Also, more info than you probably need at this point.

Rod ..
Reasons like this is why I love my Marco Polo tracker. Good luck tracking it down..👍👍
 
[/URL]
This is a tricky one.
The options are:
1. The drone had a sudden power loss and dropped .... or
2. The drone just lost signal and kept flying.

When signal was lost the drone was 2100 ft out and being flown home at 32 mph.
It was about 68 feet above the ground below.
There are no obstacles between that point and home.
Battery cell voltage was >3.6V

If the drone lost power and fell, it would have kept moving forward as it fell.
So it wouldn't have come to rest directly below the last recorded position, but approx 90 feet further in the direction of the home point.

If it lost signal, the drone would have initiated Failsafe RTH and continued toward home at RTH speed.
An approximate calculation based of the available data suggests that the remaining battery should have been more than enough to bring the drone back well before the battery reached critical low voltage level and commenced autolanding.

I'd be searching along a line from where signal was lost towards the homepoint, particularly around 80-100 feet along that line.
 
Last edited:
This is a tricky one.
The options are:
1. The drone had a sudden power loss and dropped .... or
2. The drone just lost signal and kept flying.

When signal was lost the drone was 2100 ft out and being flown home at 32 mph.
It was about 68 feet above the ground below.
There are no obstacles between that point and home.
Battery cell voltage was >3.6V

If the drone lost power and fell, it would have kept moving forward as it fell.
So it wouldn't have come to rest directly below the last recorded position, but approx 90 feet further in the direction of the home point.

If it lost signal, the drone would have initiated Failsafe RTH and continued toward home at RTH speed.
An approximate calculation based of the available data suggests that the remaining battery should have been more than enough to bring the drone back well before the battery reached critical low voltage level and commenced autolanding.

I'd be searching along a line from where signal was lost towards the homepoint, particularly around 80-100 feet along that line.

If there is a restricted area in the way, would it go through or try to go around it?
 
I wonder why I was able to takeoff and fly through it since I am just inside restricted zone? Either way it should have tried to land then. Are there any other possible scenarios if it's not there?
If I understand this correctly, if it is in "A" mode, it will fly through restricted areas with only a warning on the app. The flight logs show it in "A" mode I believe.

In my personal opinion, I think the incorrect battery levels being displayed late in the flight (in the logs) were way off. The drone flew until critical battery level was reached, (the percent level set in the GoApp) and it possibly autolanded. Still curious though why no battery warnings, or autoland warnings were displayed in the final minutes of the flight logs. Only other explanation might be that the battery quit during the RTH flight.
 
  • Like
Reactions: RodPad
WOW,

This changes the focus al least for me.

I recall a P4 long time ago that guy flew from house, never made it back. the concept was he flew it from house and not know he gone around the end of a fly zone. RTH was triggered, headed back in straight line when it got to no fly, and landed, If I recall the flight log showed it was landing. It was over a car lot. He told me he did look it the bed of that pickup, of coarse that wasn't there then.

Rod ..
 
After making a long post @Meta4 would have already spotted the no fly zone. :rolleyes:

Rod ..
 

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,310
Messages
1,469,374
Members
105,274
Latest member
davidwilliams
Want to Remove this Ad? Simply login or create a free account