So It got stuck in a spin twice during the same flight?
RTh looks like the solution for now.
Did anyone have the tracking feature enabled or normal mode?
I too was in sport mode when it happened.
Inspire 2 uncontrollable spin
- Thread starter cvanhoose
- Start date
So It got stuck in a spin twice during the same flight?
RTh looks like the solution for now.
Did anyone have the tracking feature enabled or normal mode?
I too was in sport mode when it happened.
I also had uncontrollable spin but was flying in sport mode over the sea so had no chance to recover before it spun into the water. Recovered Inspire 2 and found it was missing the whole prop, motor and foot but don't know if that happened when it hit the water or if that came off during flight which caused the crash.
DJI haven't acknowledged that it's a manufacturer fault yet. It could be that the epoxy bonding let go off the carbon fibre frame, or the quick-spin during fast flight is too much for the a/c to handle?
I'm surprised and disappointed that DJI aren't more concerned that they might have a problem here
DJI haven't acknowledged that it's a manufacturer fault yet. It could be that the epoxy bonding let go off the carbon fibre frame, or the quick-spin during fast flight is too much for the a/c to handle?
I'm surprised and disappointed that DJI aren't more concerned that they might have a problem here
Thanks for the response. I sent you a PM to a link.
Fingers crossed we can isolate this event.
- Joined
- Oct 12, 2016
- Messages
- 1,090
- Reaction score
- 569
My I2 went into an uncommanded spin yesterday, fortunately, not at great height or distance, and in an open area. It h ad been flying for around 90mins prior to the spin without any problems.
Once I realised it wasn't just the camera spinning or spotlight pro having a fit, I was able to stop the spin by flicking the flight mode switch in to atti mode and back to p-gps. After that, there was no ability to yaw the aircraft unless the gimbal was put into free mode, or the flight mode set back to Atti.
I was able to fly the I2 back and land without further issue. Aircraft shutdown and reboot cleared the issue and it flew again for another 30 mins after without any further problems showing up. All sensors showed ok on the ground, the area was open fields with no metal to cause problems.
After looking at the flight logs last night, the I2 reported a compass error at the point it entered the spin, either the compass error caused the spin, or was caused by the spin... which I couldn't tell you. Quick spin was enabled, but wasn't activated in this case as the gimbal was in follow mode and was locked to the aircraft nose. Iirc, I'm pretty sure Spotlight Pro was in use and was set for composition mode but hadn't been triggered as the subject was just about to enter the tracking box. The I2 had just been repositioned with left/right roll to align it with the path of the object to be tracked, and from the video footage, it had been in a stable hover for a second or so before the spin occurred.
I have had compass errors thrown up in flight before, but they've not put the I2 into a spin, and have cleared when resetting the flight mode through atti and back to p-gps. In this case with the spin occurring, I didn't see the on-screen warning this time as my attention was on the video feed going nuts, and then on the aircraft to see what it was actually doing! I don't recal the compass as the aircraft never moves far enough e-w to need it, so a bad cal isn't the problem in this case!
Overall flight time on the aircraft is around 51hrs 20min, and 319 miles flown.
Healthydrones only shows the compass error message in the log, with everything else showing no problems.
Once I realised it wasn't just the camera spinning or spotlight pro having a fit, I was able to stop the spin by flicking the flight mode switch in to atti mode and back to p-gps. After that, there was no ability to yaw the aircraft unless the gimbal was put into free mode, or the flight mode set back to Atti.
I was able to fly the I2 back and land without further issue. Aircraft shutdown and reboot cleared the issue and it flew again for another 30 mins after without any further problems showing up. All sensors showed ok on the ground, the area was open fields with no metal to cause problems.
After looking at the flight logs last night, the I2 reported a compass error at the point it entered the spin, either the compass error caused the spin, or was caused by the spin... which I couldn't tell you. Quick spin was enabled, but wasn't activated in this case as the gimbal was in follow mode and was locked to the aircraft nose. Iirc, I'm pretty sure Spotlight Pro was in use and was set for composition mode but hadn't been triggered as the subject was just about to enter the tracking box. The I2 had just been repositioned with left/right roll to align it with the path of the object to be tracked, and from the video footage, it had been in a stable hover for a second or so before the spin occurred.
I have had compass errors thrown up in flight before, but they've not put the I2 into a spin, and have cleared when resetting the flight mode through atti and back to p-gps. In this case with the spin occurring, I didn't see the on-screen warning this time as my attention was on the video feed going nuts, and then on the aircraft to see what it was actually doing! I don't recal the compass as the aircraft never moves far enough e-w to need it, so a bad cal isn't the problem in this case!
Overall flight time on the aircraft is around 51hrs 20min, and 319 miles flown.
Healthydrones only shows the compass error message in the log, with everything else showing no problems.
Quick spin and crash for me today also. Later i'll grab the DAT files and post video. I was in a large arena and getting up to speed flying in atti mode. Did about 15 min of flight and as I was bringing it in to land - crazy spin - smash. I'll post logs and video soon. Quick spin was off.
Florida Drone Supply
Approved Vendor
- Joined
- Oct 12, 2016
- Messages
- 1,090
- Reaction score
- 569
I have 110 hours on mine and it has not happened to me. That being said mine is back at DJI for a cinecore issue.
- Joined
- Dec 9, 2015
- Messages
- 756
- Reaction score
- 378
- Joined
- Jul 17, 2015
- Messages
- 164
- Reaction score
- 56
- Age
- 57
- Location
- Austin, TX
- Website
- www.overlookfs.com
- Joined
- Oct 12, 2016
- Messages
- 1,090
- Reaction score
- 569
Mine is latest version .0100 or whatever it is. As far as i can remember, I've had Compass errors show up on all versions of firmware, but this is the first time it's spun. On some occassions after it's chucked the compass error, it's then reported being in a no-fly-zone (nearest was 20 miles away!) and other silly stuff like that, other times it reports the compass error and is totally fine. No rhyme or reason to it for mine. on all occasions it's done it, the imu/compass readings were fine before take-off and after restarting. No metal nearby, no compass recal before the error either.
Happened to me today. Did a scouting mission to check out heights and stuff, no problem. Loaded a Litchi mission. Started mission and flew about 5 minutes into a 15 minute mission and the camera went nuts and the Inspire started spinning out of control. Terminated the mission and the Inspire stopped spinning. Returned home manually and landed safely. Restarted the Inspire with a fresh battery and ran the mission again. The mission completed without a problem. Two other flights after that and no problem. Logs show nothing at all. Video below. Inspire 2 Zenmuse X5S with the Olympus 45mm
I will try to get my video posted today. The difference between nuclearheli's spin and my was that my spin was at least 100 RPM - mad spinning. First time it started less than 3 feet off the ground in atti mode just after I triggered landing mode. The I2 touched down and shattered all the props as I tried to shutdown with both left stick down right/retrun to home button and both sticks down and in. (CSC) Just got new props today and will see if I destroy this thing for good ....
Last edited:
@NickU , @enprod , @nuclearheli The .DAT file for one of these flights could help determine the cause of these incidents. I don't own an I2 and can't provide detailed instructions about retrieving the .DAT. But, look here to see how it's done with the Mavic. Since the .DAT will be large it can't be attached to a post You'll need to Dropbox or GoogleDrive it and post a link.
Last edited:
- Joined
- Mar 15, 2017
- Messages
- 34
- Reaction score
- 8
- Age
- 65
Having searched through this forum. The case seems to started on early June. During that time the firmware version was .0330 which was released on April 12th, Dji Go 4 4.0.7. There was no report since until start of June. Probably the bug is in the app library because this affected Litchi too. Just my guess.
