I had an altitude drop of ~ 100 feet the other day. The winds were calm and I was flying over land. It happened when I came to a stop. All of my firmware is updated to the latest releases. I've seen small drops in the past, but not this much.

I've looked at my flight log, but it doesn't give me any information/time stamps on control stick inputs to the P4. Is there a way to pull this info from the flight log?

Hi, the command input is there when you review the flight log on your DJI Go, click the icon that looks like a controller, when the flight log is in playback.

Try again and see if the issue appear consistently, if so, please send an email to support.us@dji.com and send it in. Thank you.

DJI-H.C Posted at 2016-8-21 07:11
Hi, the command input is there when you review the flight log on your DJI Go, click the icon that lo ...

Thanks for your response DJI H.C    I played back my flight and it showed a stick climb input to 180', then the left stick went to the center position, but my P4 continued to climb to 330' only to drop back to 190' all while the left stick was at center.I was in sport mode traveling 34mph at the time.

The rest of this flight had no problems as did the flight after this one. I'll keep an eye on it for now.

Roadstar1700 Posted at 2016-8-21 23:52
Thanks for your response DJI H.C    I played back my flight and it showed a stick climb input to 1 ...

Still having a problem with the altitude on my P4. It happened again today. I increased altitude to 160', then went to center stick position. It continued to 300', then came back down to 168'. The log replay shows no stick action after I hit 160' but it still increased to 300'. I re-caled the IMU and joysticks this morning before flight.

It doesn't happen every time, but I've noticed this 4 times now. I'm flying in P mode. The altitude is based on GPS, correct? I know there is a barometer sensor(s), but are they only for ATTI mode?

Roadstar1700 Posted at 2016-8-29 08:48
Still having a problem with the altitude on my P4. It happened again today. I increased altitude t ...

To clarify, what firmware version firmware are you currently running on your unit?

DJI-Jamie Posted at 2016-8-28 22:55
To clarify, what firmware version firmware are you currently running on your unit?

Hi Jamie,

2.8.1  Google Nexus 2013

1.6.0  RC

1.2.503  P4

I'd like to post one of my flight logs, but am not sure if I can attach it to a reply. It doesn't happen on every flight. Always at the beginning of the flight and only happens once during the flight. Looking back at most of my flights I've found 5 out of 141 that experienced this problem all within the last month. I've updated firmware, but not sure of the dates or whether it correlates with them.

Roadstar1700 Posted at 2016-8-29 09:36
Hi Jamie,

2.8.1  Google Nexus 2013

The 5 flights I've seen this happen had elevation changes of:

135 to 186 to 144
140 to 175 to 147
150 to 305 to 168
100 to 130 to 100
180 to 330 to 190

I just synced my flights to the DJI cloud service. I understand there is a DAT flie that is extracted with the DJI 2 assistant which I haven't done yet. Just finishing building a new computer with Win 7. Can't run the program on my Win XP currently.

Roadstar1700 Posted at 2016-8-29 14:36
Hi Jamie,

2.8.1  Google Nexus 2013

Try moving to latest firmware on aircraft 1.2.503, that cured an altitude drop problem that I and many others had experienced, but was closer to a 20 foot max' drop.

Roadstar1700 Posted at 2016-8-29 21:36
Hi Jamie,

2.8.1  Google Nexus 2013

Based on the information provided, you should update the firmware on your aircraft to v1.2.503. That would rectify the issue you're experiencing. I would not need the .DAT file to review your flight records remotely, just your DJI email and the date that this started occurring. I would recommend performing the update first. If the issue persists, then you can provide the information requested above and I can take a look at it for you.

Aardvark Posted at 2016-8-29 10:20
Try moving to latest firmware on aircraft 1.2.503, that cured an altitude drop problem that I and  ...

Thanks Aardvark. I forgot that I had updated to the latest aircraft version a few weeks ago. This update may just coincide with the problem I'm currently experiencing. Is there a way to see a time stamp of when I updated to the latest firmware?

DJI-Jamie Posted at 2016-8-29 11:21
Based on the information provided, you should update the firmware on your aircraft to v1.2.503. Th ...

I forgot that I had updated to v 1.2.503 a few weeks ago. I'm also thinking this may be the time I started having this problem. The earliest I can find the problem occurring in my flight logs is 7/29. My first flight was on 5/9. When you say my DJI e-mail are you referring to the my e-mail address I have on file?

The 5 flights I found are:

7/29 - 14 min flight
7/29 - 9 min flight
8/18 - 10 min flight
8/27 - 13 min flight
8/28 - 12 min flight

I'm thinking you should have access to these on the DJI cloud. They all happen during the initial large increase in altitude.

Roadstar1700 Posted at 2016-8-29 16:24
Thanks Aardvark. I forgot that I had updated to the latest aircraft version a few weeks ago. This u ...

Best way is to download and run 'DJI Assistant 2' on a PC.

That shows you the current build, which you can update to latest build, refresh, roll back, or try a factory reset. I would update to latest build, or refresh if already done. Then do a factory reset, then carry out Sensor (from Assistant 2), IMU, Gimbal, RC & Compass calibrations. And see if any change

Oh, and make sure all batteries are up to date.

Roadstar1700 Posted at 2016-8-29 23:48
I forgot that I had updated to v 1.2.503 a few weeks ago. I'm also thinking this may be the time I  ...

The DJI email would be the one you used to register the drone with. You can also try Aardvark's suggestions as well if you have not done so already.

DJI-Jamie Posted at 2016-8-29 12:01
The DJI email would be the one you used to register the drone with. You can also try Aardvark's su ...

My e-mail for DJI is sgussert@charter.net. With this, should you be able to look at one of my flights I've listed above?

I'm going to load Assistant 2 on my new computer and carry out Aardvark's suggestions.

Roadstar1700 Posted at 2016-8-30 00:58
My e-mail for DJI is . With this, should you be able to look at one of my flights I've listed abov ...

There's no reason at all to have a 100ft altitude drop, you don't have a gimbal guard installed do you?
If so, REMOVE IT. It will block the sonar sensor and cause the aircraft to yoyo up and down.

Roadstar1700 Posted at 2016-8-30 00:58
My e-mail for DJI is . With this, should you be able to look at one of my flights I've listed abov ...

It seems that the logs are not appearing. Can you please try to resync them?

DJI-Jamie Posted at 2016-8-29 13:44
It seems that the logs are not appearing. Can you please try to resync them?

I just re synced all of my flights. I don't have a gimbal guard installed. I did a factory reset through Assist 2 and refreshed the 1.2.503 firmware. I also tried to calibrate the vision position sensors many times and recieved a fail at 66% every time. I'm going to do a compass, gimbal and IMU cal next.

Aardvark Posted at 2016-8-29 11:51
Best way is to download and run 'DJI Assistant 2' on a PC.

That shows you the current build, which ...

I refreshed the firmware in the P4, tried to cal the VPS sensors and failed at 66% each time, then did the cals on the all rest. I did the rest of them through the Go app. Will try later today. Thanks Aardvark

Roadstar1700 Posted at 2016-8-29 20:00
I refreshed the firmware in the P4, tried to cal the VPS sensors and failed at 66% each time, then ...

If the VPS calibration was failing try reducing the screen resolution a bit, or perhaps try a bigger monitor if available.

Roadstar1700 Posted at 2016-8-30 02:07
I just re synced all of my flights. I don't have a gimbal guard installed. I did a factory reset t ...

Try to adjust your monitor settings or try a different monitor as Aardvark suggested and see if the calibration issue persists.

DJI-Jamie Posted at 2016-8-29 16:09
Try to adjust your monitor settings or try a different monitor as Aardvark suggested and see if th ...

Back to my original problem with altitude change. I refreshed the current most up-to-date firmware in the aircraft and re-caled all sensors. Just flew it this morning with the same problem. I went up 100' and it continued to travel upward, then the motors sounded like they were laboring trying to hold a position although there was no wind. It then came back down on its own to ~ where I put the left stick back to neutral. I brought it down to physically 10' off the ground and the GO app said I was 40' up. I went back up a ways and it continued to travel upward, then back down again. I brought it back down to 10' and the GO app said I was 58' above the ground.

How does the barometer tie into the flight when you are flying in P mode with GPS sats? Can you monitor the barometer reading on the GO app somewhere? I'm going to go back 1 firmware version on the aircraft, re-cal sensors and try again.

Also, I didn't try to re-cal the VPS yet after it failed to cal multiple times yesterday. This shouldn't have anything to do with my problem though, correct?

Aardvark Posted at 2016-8-29 15:14
If the VPS calibration was failing try reducing the screen resolution a bit, or perhaps try a bigg ...

Thanks for the tip Aardvark. I went from a 20" 1200X1600 res monitor to a 1200X1920 and the VPS calibrated up the first time. Don't know why the 20" didn't work, though. Ran through the rest of the cals and just got back from flying. It flies like a dream now! Didn't realize the bottom cameras were that important when you're high up, but they obviously are.

Roadstar1700 Posted at 2016-8-31 20:21
Thanks for the tip Aardvark. I went from a 20" 1200X1600 res monitor to a 1200X1920 and the VPS ca ...

That's good news, not sure about the monitor thing, could be a refresh/timing issue or perhaps a driver thing.
Have fun.

Roadstar1700 Posted at 2016-9-1 03:21
Thanks for the tip Aardvark. I went from a 20" 1200X1600 res monitor to a 1200X1920 and the VPS ca ...

Good to hear you're up and running.

Aardvark Posted at 2016-9-1 03:58
That's good news, not sure about the monitor thing, could be a refresh/timing issue or perhaps a d ...

Refresh rates and overall resolution are the normally the culprits for sensor calibration errors.  

I have same problem, drop 5-10m! Scary