P3 Firmware Bad experience downgrading firmware Phantom 3 Standard

Joined
Jun 7, 2019
Messages
11
Reaction score
6
Age
65
Hi,

I was trying to get better range on my Phantom 3 Standard, as I was getting fed up with RTH issues just as I was in the middle of filming. I have fitted the external antennae on the receiver and have put external Aomway "rubber duckies" on the bird. I also had the Magic mod to increase db on the 2.4 from the bird. I read that better range could be achieved with downgrading the firmware to version 1.5.70, so decided to try it. Using the SD card method, I successfully installed it, and DJI Go reported that update required and the version number as 1.5.70+.

I force closed DJI Go, and opened Litchi, which is my app i use to fly. I started the bird without props, and tested that the sticks did the right moves, and closed the bird down after powering off the motors by pulling down the left stick. Went to try a flight, and chose a deserted area, to be safe. Did a compass calibration (The IMU reported calibration not required) and started the motors. Lifted off, and immediately, the bird climbed a bit and crabbed, shooting off at full throttle and then full pitch! moving the sticks did nothing, although I had all green on the controller, and the sticks had worked fine when I checked without props. Tried to change to ATTI mode and back to try to regain control, but it was out of sight, and the video feed looked scary. Not wishing to panic, i waggled the S2 switch to try to bring it home, and the beeping confirmed, together with the message that it was RETURNING TO HOME. I could see spinning on the video, and after what appeared to be enough time to worry about battery, it showed up, but shot right past, at about 80 feet altitude ( I set 200 feet as RTH!) Still had no control of sticks. Tried another waggle of S2, and with pulling down on left stick and timing it right, managed to land it. The props however, would not shut down. I tried switching off and on the receiver and this made no difference, the props were spinning at a high speed, and it was higher than idle. I managed to gingerly reach right under the craft and pick it up by the legs, and continued to hold the left stick at the bottom indent, which should shut down the motors. Eventually, it did! The area was a field, no concrete, metal or other issues, and the compass cal was successful. I brought it home, and have now upgraded to the latest firmware via the DJI Go app, and it was successful. Later today, I hope to fly to confirm all is okay. Again IMU reported it does not require calibration. Will post to let you know how it goes. I guess in 2019, downgrading does not work favourably. Sorry this is so long, but had to warn in case others have same issues.
 
Last edited:

ianzone

LV34
Premium Pilot
Joined
May 22, 2016
Messages
5,629
Reaction score
3,175
Age
50
Location
EARTH.NZ
Hi,

I was trying to get better range on my Phantom 3 Standard, as I was getting fed up with RTH issues just as I was in the middle of filming. I have fitted the external antennae on the receiver and have put external Aomway "rubber duckies" on the bird. I also had the Magic mod to increase db on the 2.4 from the bird. I read that better range could be achieved with downgrading the firmware to version 1.5.70, so decided to try it. Using the SD card method, I successfully installed it, and DJ Go reported that update required and the version number as 1.5.70+.

I force closed DJI Go, and opened Litchi, which is my app i use to fly. I started the bird without props, and tested that the sticks did the right moves, and closed the bird down after powering off the motors by pulling down the left stick. Went to try a flight, and chose a deserted area, to be safe. Did a compass calibration (The IMU reported calibration not required) and started the motors. Lifted off, and immediately, the bird climbed a bit and crabbed, shooting off at full throttle and then full pitch! moving the sticks did nothing, although I had all green on the controller, and the sticks had worked fine when I checked without props. Tried to change to ATTI mode and back to try to regain control, but it was out of sight, and the video feed looked scary. Not wishing to panic, i waggled the S2 switch to try to bring it home, and the beeping confirmed, together with the message that it was RETURNING TO HOME. I could see spinning on the video, and after what appeared to be enough time to worry about battery, it showed up, but shot right past, at about 80 feet altitude ( I set 200 feet as RTH!) Still had no control of sticks. Tried another waggle of S2, and with pulling down on left stick and timing it right, managed to land it. The props however, would not shut down. I tried switching off and on the receiver and this made no difference, the props were spinning at a high speed, and it was higher than idle. I managed to gingerly reach right under the craft and pick it up by the legs, and continued to hold the left stick at the bottom indent, which should shut down the motors. Eventually, it did! The area was a fiend, no concrete, metal or other issues, and the compass cal was successful. I brought it home, and have now upgraded to the latest firmware via the DJI Go4 app, and it was successful. Later today, I hope to fly to confirm all is okay. Again IMU reported it does not require calibration. Will post to let you know how it goes. I guess in 2019, downgrading does not work favourably. Sorry this is so long, but had to warn in case others have same issues.
Your post bit confusing,,your flying p3s but you mention you upgrade firmware from djigo4
 

ianzone

LV34
Premium Pilot
Joined
May 22, 2016
Messages
5,629
Reaction score
3,175
Age
50
Location
EARTH.NZ
Yes not sure on firmware upgrades and downgrades so unsure on that part but sounds bit scary,,even though it not want in calibration I would do it along with stick and gimble calibration in case something not right,you would have to upload your flight so others can see what happen,,take care on that next flight;)
 
  • Like
Reactions: Ty Williams (Wales)
Joined
Jun 7, 2019
Messages
11
Reaction score
6
Age
65
Your post bit confusing,,your flying p3s but you mention you upgrade firmware from djigo4
Sorry, meant DJI Go, not 4. it's a typo. edited it now... The firmware is now v1.9.20. Hoping all works well....
 
Last edited:
Joined
Jun 7, 2019
Messages
11
Reaction score
6
Age
65
Hi,

I was trying to get better range on my Phantom 3 Standard, as I was getting fed up with RTH issues just as I was in the middle of filming. I have fitted the external antennae on the receiver and have put external Aomway "rubber duckies" on the bird. I also had the Magic mod to increase db on the 2.4 from the bird. I read that better range could be achieved with downgrading the firmware to version 1.5.70, so decided to try it. Using the SD card method, I successfully installed it, and DJ Go reported that update required and the version number as 1.5.70+.

I force closed DJI Go, and opened Litchi, which is my app i use to fly. I started the bird without props, and tested that the sticks did the right moves, and closed the bird down after powering off the motors by pulling down the left stick. Went to try a flight, and chose a deserted area, to be safe. Did a compass calibration (The IMU reported calibration not required) and started the motors. Lifted off, and immediately, the bird climbed a bit and crabbed, shooting off at full throttle and then full pitch! moving the sticks did nothing, although I had all green on the controller, and the sticks had worked fine when I checked without props. Tried to change to ATTI mode and back to try to regain control, but it was out of sight, and the video feed looked scary. Not wishing to panic, i waggled the S2 switch to try to bring it home, and the beeping confirmed, together with the message that it was RETURNING TO HOME. I could see spinning on the video, and after what appeared to be enough time to worry about battery, it showed up, but shot right past, at about 80 feet altitude ( I set 200 feet as RTH!) Still had no control of sticks. Tried another waggle of S2, and with pulling down on left stick and timing it right, managed to land it. The props however, would not shut down. I tried switching off and on the receiver and this made no difference, the props were spinning at a high speed, and it was higher than idle. I managed to gingerly reach right under the craft and pick it up by the legs, and continued to hold the left stick at the bottom indent, which should shut down the motors. Eventually, it did! The area was a fiend, no concrete, metal or other issues, and the compass cal was successful. I brought it home, and have now upgraded to the latest firmware via the DJI Go app, and it was successful. Later today, I hope to fly to confirm all is okay. Again IMU reported it does not require calibration. Will post to let you know how it goes. I guess in 2019, downgrading does not work favourably. Sorry this is so long, but had to warn in case others have same issues.
 
Joined
Jun 7, 2019
Messages
11
Reaction score
6
Age
65
Tried to upload the flight log, but it's too large. Using the log viewer, it looks like this:


Latitude​
(Deg),​
Longitude​
(Deg),​
GPS​
Altitude​
(m),​
N​
Velocity(m/s),​
E​
Velocity(m/s),​
D​
Velocity(m/s),​
Velocity(m/s),​
Ground​
Speed(m/s),​
AccelerometerX(g),​
AccelerometerY(g),​
AccelerometerZ(g),​
GyroX(rad/s),​
GyroY(rad/s),​
GyroZ(rad/s),​
Barometric​
Alt(m),​
QuaternionX,​
QuaternionY,​
QuaternionZ,​
0,​
0,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
1.018007969817198e-38,​
8.31200026712918e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
90,​
0,​
90,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
0,​
64945,​
0,​
0,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
1.018007969817198e-38,​
8.31200026712918e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
90,​
0,​
90,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
0,​
64948,​
0,​
0,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
1.018007969817198e-38,​
8.31200026712918e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
90,​
0,​
90,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
0,​
64951,​
0,​
0,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
1.018007969817198e-38,​
8.31200026712918e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
90,​
0,​
90,​
5.877471754111438e-39,​
5.877471754111438e-39,​
5.877471754111438e-39,​
0,​
64954,​
There appeared to be no GPS lock, but Litchi reported 8 satellites. In any event, I should have been able to control via ATTI mode (albeit a bit lary, if there was a breeze) but it appears the update screwed a lot. When I fly, I will check with DJI Go first, then land and close down DJI Go, force close it, and try with Litchi. I am currently calibrating the IMU, and will do the controller next (if it will let me)...will keep you posted.
 
Joined
Jun 7, 2019
Messages
11
Reaction score
6
Age
65
Hi,

I was trying to get better range on my Phantom 3 Standard, as I was getting fed up with RTH issues just as I was in the middle of filming. I have fitted the external antennae on the receiver and have put external Aomway "rubber duckies" on the bird. I also had the Magic mod to increase db on the 2.4 from the bird. I read that better range could be achieved with downgrading the firmware to version 1.5.70, so decided to try it. Using the SD card method, I successfully installed it, and DJI Go reported that update required and the version number as 1.5.70+.

I force closed DJI Go, and opened Litchi, which is my app i use to fly. I started the bird without props, and tested that the sticks did the right moves, and closed the bird down after powering off the motors by pulling down the left stick. Went to try a flight, and chose a deserted area, to be safe. Did a compass calibration (The IMU reported calibration not required) and started the motors. Lifted off, and immediately, the bird climbed a bit and crabbed, shooting off at full throttle and then full pitch! moving the sticks did nothing, although I had all green on the controller, and the sticks had worked fine when I checked without props. Tried to change to ATTI mode and back to try to regain control, but it was out of sight, and the video feed looked scary. Not wishing to panic, i waggled the S2 switch to try to bring it home, and the beeping confirmed, together with the message that it was RETURNING TO HOME. I could see spinning on the video, and after what appeared to be enough time to worry about battery, it showed up, but shot right past, at about 80 feet altitude ( I set 200 feet as RTH!) Still had no control of sticks. Tried another waggle of S2, and with pulling down on left stick and timing it right, managed to land it. The props however, would not shut down. I tried switching off and on the receiver and this made no difference, the props were spinning at a high speed, and it was higher than idle. I managed to gingerly reach right under the craft and pick it up by the legs, and continued to hold the left stick at the bottom indent, which should shut down the motors. Eventually, it did! The area was a field, no concrete, metal or other issues, and the compass cal was successful. I brought it home, and have now upgraded to the latest firmware via the DJI Go app, and it was successful. Later today, I hope to fly to confirm all is okay. Again IMU reported it does not require calibration. Will post to let you know how it goes. I guess in 2019, downgrading does not work favourably. Sorry this is so long, but had to warn in case others have same issues.
UPDATE: Yesterday, I had reflashed the correct latest firmware (1.9.2.0) via the DJI Go app and it was successful. Re-linked the controller, Calibrated the IMU, controller and gimbal. Spun up without props, and DJI Go said the video signal was low. Checking in the 2.4 area (clicking on the icon took me there) I noticed that channel was set to 13 on auto, and I could not alter any of it. No signal showing in the graph (which I assume should show bars of specific channels.) Now used to not panicking(!) I shut down the aircraft and removed the micro SD card. Started up the craft and all was good. Switched it off and then reinserted the card and restarted, and all was fine! I then reformatted the card, to be safe. Took a flight later, and after checking it hovered correctly, took it to altitude and flew...all good, thank goodness. Hope this helps someone in some way, and than you for suggesting I recalibrate even though it said it did not need it; I am sure that cleared the possibility of any stray bugs in the memory. Still getting RTH before I would like, but will persevere. :) Unsure if I am allowed to link the Flickr or YouTube video of the scary flight, so will not unless requested. Thanks, Tyrone (Ty).
 
Joined
Jul 30, 2017
Messages
40
Reaction score
9
Age
67
Any time you have a + sign, you have a problem with the Upgrade, and it needs to be Debugged...
So that is why it went ape on you.... There is a conflict between the different moduals ...
 
Joined
Oct 14, 2016
Messages
4,075
Reaction score
1,834
Age
63
Location
UK Brit living Latvia
Sorry to say this - but you have fallen foul of the 'I want to downgrade' gremlins ...

FW does NOT determine range ... and there is no reason older FW will give you greater range. Its a myth.

My P3S was flown on many different FW's in its life till I was over-ambitious and ran out of battery after a 6000m run ...

There are real ways to improve range :

1. To modify the RF signal strength by ICARUS or Magic Power. You can alter it to 27db to get max signal.
2. Improve antenna by using ARGTEK or ITELITE etc.
3. Install antenna boosters.

A combination of 1 + 2 gave me over 2000m reliable range with ALL FW ....

The 6000m was with antenna boosters which was then replaced with dual parabolic reflectors on the ARGTEK antenna's.
 
Phantom Drones from EALLRC.com

New Threads

Forum statistics

Threads
136,398
Messages
1,410,575
Members
99,209
Latest member
knightsraven