So this is how it went the other night. wanted to do some more night flying now that I can living in a draconian no fly zone and not having to drive 10 miles to get out of the no fly zone and then the added more miles to get someplace..took hours just to fly..THANK YOU DJI. So i lifted off and went 1,000 feet or so, there were wind gusts I was aware of. Not to bad on the ground up in the air a bit I am guessing worse. Got the message about strong wind, so I headed back. all was ok till I was 200 feet from landing, then the Mini4 pro started acting strange, took 15 minutes to land, was NOT from the wind. started drifting and stick input would take it on a course sometimes on an opposit or a 45° angle off of what it was supposed to go. here is what it did, this is only about 70%


This was at a park, only a few cars, all the cars were empty and the people were playing tennis or B-ball, this truck came in parked near me , turned off it's lights and no one got out... a few moments before I took off.

Interference doesn't cause drones to act up as you described.
Your recorded flight data might help solve the mystery.

Go to: https://www.phantomhelp.com/LogViewer/Upload/
... where you'll find instructions.
That will give a report you can post a link for the report here.

Or if you use Airdata, post a link to the Airdata report for the flight.

Or just post the .txt file.

If you used the RC controller, you'll find your files here:
Android\data\dji.go.v5\files\FlightRecord

Labroides Posted at 3-13 12:35
Interference doesn't cause drones to act up as you described.
Your recorded flight data might help solve the mystery.

thanks, will do that, was sort of like flying atti mode, but worse, went back and replayed the rc2 footage was connect to 27 satellites

Labroides Posted at 3-13 12:35
Interference doesn't cause drones to act up as you described.
Your recorded flight data might help solve the mystery.

    Labroides   here is a link to the flight log https://www.phantomhelp.com/logviewer/2025031406ZZFODCVITP9TNXGEG3I8IR2B3IRMCL
I tried attaching the txt file , system reported could notupload txt files, tried changing the extension to jpg and it said was not a good file. you can download the txt file from the log viewer

here is the crazy path the drone took

Labroides Posted at 3-13 12:35
Interference doesn't cause drones to act up as you described.
Your recorded flight data might help solve the mystery.

what other logs are there? what I would really be interested in is wireless connection between the drone and the controller showing the ID of the controller and signal strength. also a  GPS LOG of where the drone was as compared to where the drone thought it was.

Frunobulax Posted at 3-14 08:17
Labroides   here is a link to the flight log https://www.phantomhelp.com/logviewer/2025031406ZZFODCVITP9TNXGEG3I8IR2B3IRMCL
I tried attaching the txt file , system reported could notupload txt files, tried changing the extension to jpg and it said was not a good file. you can download the txt file from the log viewer

This flight doesn't match your description. In particular, the maximum height is 237.8 feet and the flight duration is 329 secs.

Hi there. We have replied to your other post addressing this issue. Please check it and get back to us for further assistance. Thank you!

BudWalker Posted at 3-15 08:00
This flight doesn't match your description. In particular, the maximum height is 237.8 feet and the flight duration is 329 secs.

why does it not match?  In the air at altitude i got the strong wind warning and turned back, this probably was a third to half of the flight time. no GPS info in the log

Frunobulax Posted at 3-16 06:16
why does it not match?  In the air at altitude i got the strong wind warning and turned back, this probably was a third to half of the flight time. no GPS info in the log

I suspect you’re looking at the wrong log. But, if this is the correct log I don’t see a problem. No indication that “ was 200 feet from landing, then the Mini4 pro started acting strange” .

  

At 282 secs the Mini 4 was 213 ft from the HP. Over the next 44 secs the Mini 4 responded correctly to the control inputs to land it about 68 ft from the HP. A bit unusual in that the Mini 4 was facing 150° but the eventual landing site was about 240°. This required using mostly CW aileron to guide the Mini 4 to the landing site.

  

  

Just guessing here. Is it possible that darkness led to some disorientation, in particular some misperception about the Mini 4’s heading? That could cause “stick input would take it on a course sometimes on an opposit or a 45° angle off of what it was supposed to go. “

BudWalker Posted at 3-16 07:47
I suspect you’re looking at the wrong log. But, if this is the correct log I don’t see a problem. No indication that “ was 200 feet from landing, then the Mini4 pro started acting strange” .   At 282 secs the Mini 4 was 213 ft from the HP. Over the next 44 secs the Mini 4 responded correctly to the control inputs to land it about 68 ft from the HP. A bit unusual in that the Mini 4 was facing 150° but the eventual landing site was about 240°. This required using mostly CW aileron to guide the Mini 4 to the landing site.     Just guessing here. Is it possible that darkness led to some disorientation, in particular some misperception about the Mini 4’s heading? That could cause “stick input would take it on a course sometimes on an opposit or a 45° angle off of what it was supposed to go. “

i just noticed that the VPS altitude is N/A most of the flight except for take off and landing
go here https://www.phantomhelp.com/logv ... TNXGEG3I8IR2B3IRMCL  move the little slider bar along between the picture and the data

I would think the mini4 pro can fly in absolute darkness b/c it uses GPS, light is only for obstacle avoibdance

Frunobulax Posted at 3-16 07:55
i just noticed that the VPS altitude is N/A most of the flight except for take off and landing
go here https://www.phantomhelp.com/logv ... TNXGEG3I8IR2B3IRMCL  move the little slider bar along between the picture and the data

That’s to be expected. VPS will be N/A when the Mini 4 is above the range of the VPS. I assure you; I know how to use the PhantomHelp viewer.

  

  

I’m suggesting that you were disoriented, not the Mini 4. Here is the landing phase starting at 283 secs. The red trace is the aileron.

BudWalker Posted at 3-16 08:15
That’s to be expected. VPS will be N/A when the Mini 4 is above the range of the VPS. I assure you; I know how to use the PhantomHelp viewer.     I’m suggesting that you were disoriented, not the Mini 4. Here is the landing phase starting at 283 secs. The red trace is the aileron.

How could I have been disorientated? i had visual of the drone. There is lighting all around plus I had the landing light on. I also was recording in night mode so I could also see myself ( physically)  and the head up display of the Home point. I  replayed my flight log on Phantom help.  If you watch my stick movement they are perfect for where my drone went. which in reality did not happen, the drone was going the opposite direction of my stick movement. sometimes I was able to move the drone towards me. It was like trying to land a Marlin on a fishing boat where you have to give a a little take a little, give a little take a bit more etc. I still am standing  by that it was electronic interference AND someone had control of my drone.
read this,  i have to read it again slower, but it looks like u can get drone Hijack software on Github
  https://www.sstic.org/media/SSTI ... viet-triem-tong.pdf

Frunobulax Posted at 3-16 18:03
How could I have been disorientated? i had visual of the drone. There is lighting all around plus I had the landing light on. I also was recording in night mode so I could also see myself ( physically)  and the head up display of the Home point. I  replayed my flight log on Phantom help.  If you watch my stick movement they are perfect for where my drone went. which in reality did not happen, the drone was going the opposite direction of my stick movement. sometimes I was able to move the drone towards me. It was like trying to land a Marlin on a fishing boat where you have to give a a little take a little, give a little take a bit more etc. I still am standing  by that it was electronic interference AND someone had control of my drone.
read this,  i have to read it again slower, but it looks like u can get drone Hijack software on Github
  https://www.sstic.org/media/SSTI ... viet-triem-tong.pdf

“stick movement they are perfect for where my drone went. which in reality did not happen, the drone was going the opposite direction of my stick movement.”

  

I’m confused. This statement seems to say that both 1) stick inputs were consistent with drone movements, and 2) stick inputs were not consistent with drone movements. Which is it? I, and others, have reviewed the submitted log and can find no inconsistency.  If you think there was an inconsistency perhaps you can provide a time interval where this occurred.

  

  

Can you reconcile your claims that 1) it took 15 minutes to land the Mini 4 yet the recorded flight is 329 secs, and 2) “lifted off and went 1,000 feet or so” yet the recorded max height is 237.8 feet?

  

  

“I still am standing  by that it was electronic interference AND someone had control of my drone.” There are no indications in the submitted .txt that support this.

BudWalker Posted at 3-17 06:33
“stick movement they are perfect for where my drone went. which in reality did not happen, the drone was going the opposite direction of my stick movement.”  I’m confused. This statement seems to say that both 1) stick inputs were consistent with drone movements, and 2) stick inputs were not consistent with drone movements. Which is it? I, and others, have reviewed the submitted log and can find no inconsistency.  If you think there was an inconsistency perhaps you can provide a time interval where this occurred.     Can you reconcile your claims that 1) it took 15 minutes to land the Mini 4 yet the recorded flight is 329 secs, and 2) “lifted off and went 1,000 feet or so” yet the recorded max height is 237.8 feet?     “I still am standing  by that it was electronic interference AND someone had control of my drone.” There are no indications in the submitted .txt that support this.

I’m confused. This statement seems to say that both 1) stick inputs were consistent with drone movements, and 2) stick inputs were not consistent with drone movements. Which is it? I, and others, have reviewed the submitted log and can find no inconsistency.  If you think there was an inconsistency perhaps you can provide a time interval where this occurred. Someone had taken control of my drone and the stick movements was their input, not what i was doing...most of the time. I finally got the drone to a point where it was acceptitcle to land and i landed the mini4 pro. I had to run about 20 feet before to keep up with the drone before this. It sure felt like 15 minutes, as we both have seen in the flight logs it was not.   what else would cause that erratic flight path? u can see i was heading back in a straight line, then the drone viers off
did u look at the pdf link i provided i found on GIT HUB?

Frunobulax Posted at 3-17 09:33
I’m confused. This statement seems to say that both 1) stick inputs were consistent with drone movements, and 2) stick inputs were not consistent with drone movements. Which is it? I, and others, have reviewed the submitted log and can find no inconsistency.  If you think there was an inconsistency perhaps you can provide a time interval where this occurred. Someone had taken control of my drone and the stick movements was their input, not what i was doing...most of the time. I finally got the drone to a point where it was acceptitcle to land and i landed the mini4 pro. I had to run about 20 feet before to keep up with the drone before this. It sure felt like 15 minutes, as we both have seen in the flight logs it was not.   what else would cause that erratic flight path? u can see i was heading back in a straight line, then the drone viers off
did u look at the pdf link i provided i found on GIT HUB?

Maybe it's best if I take a backseat and let others try to help you. @JJB, @Labroides