I only stated this because it was the first error thrown and the other week you said you didn't know yourself why these errors were being thrown from the sonar even at high altitudes, have DJI come up with a reason for this now.
Mine threw same error a few times when I first started flying the P3. Went into Atti the same way, but I was able land each time. I chalked it up to launching on my driveway which undoubtedly has rebar. Haven't had it since launching from the lawn.
Yea i had that problem just the once, but like you i was able to control the craft very easy and it did not go out of control in any way. I was near lots of rebar all so near a sea wall, once i moved away from it GPS came back no problem.
Receiving bad data from rapid temp change. This would makes sense since he took off very fast and then over water. This would be a prime example of rapid temp change.
In the video of the flight record, from :43 to 1:26, he never uses his sticks while the craft is all over the place including a SHARP right turn during a RTH of all things! I guess you could say a bird hit at that hard right turn, but what would explain :43 - 1:26? Everything about this video defies logic. I've seen bird strikes and they're sudden and sharp... and the quad either recovers within a second or two or is flipped and comes STRAIGHT down. This does absolutely nothing like that.
ianwood
Taco Wrangler
I agree the instability started there but we have no idea why. Birds don't cause compass and speed errors unless they're made of iron!
And those errors started at the same time.P.S. What is a "speed" error? Never heard of this before.
He was an atti mode and didn't even give stick input.. This would explain the craft doing odd things. No ones knows the wind or any other conditions over the water.
I know I know... I'm guessing that if it was a bird strike, the failure was gradual. Perhaps part of the propellor came off and the quad was able to stabilize for a while, but the motor/prop which got hit remained weak and gradually got worse - maybe more bits of propellor came off over the next minute, or the motor overheated because the shaft was out of alignment, or something.
The thing is that IMU or compass failure wouldn't really explain the sharp jolt. It is hard to know though, without the raw IMU data from the .DAT file.
I agree the instability started there but we have no idea why. Birds don't cause compass and speed errors unless they're made of iron!
P.S. What is a "speed" error? Never heard of this before.
I don't know what the "speed" error is, but I'm guessing it happens when the quad's internal estimate of its speed differs substantially from what the GPS is reporting. That could happen easily if a prop or motor failed. The compass errors could be caused by that, too. It's even possible an impact damaged the leg with the compass on it.
I find it hard to imagine that IMU or compass failure would cause such a sharp jolt (30 degrees in 100ms), and in any case, if the IMU or compass did fail, then the roll/pitch/yaw values wouldn't agree with the course-over-ground values (lat/lon, HEADING.compass etc.). What I see is that they do agree. The craft flew to the right, and it knew it had rolled to the right. If the IMU or compass had failed, it would fly off but that wouldn't be reflected in the roll/pitch/yaw values, which would show the craft being stable in the air.
Could also have been a cascading failure. Perhaps an initial impact confused the flight controller, which then got gradually more and more confused even though everything was mechanically sound. Or perhaps the impact caused an initial mechanical failure which got progressively worse over the following minute or so, until eventually the props were unable to provide enough lift to keep the quad in the air.
ianwood
Taco Wrangler
I don't think a bird strike is going to end in a gradual crash. Physical damage to props will end quickly. And again birds don't cause compass/speed errors. Something else was going on.
My concern here is twofold. I don't want to lose control of my bird and maybe kill someone, clearly, but I also want to feel safe that DJI's warranty will cover this type of accident. I've heard rumors that if you're ever over water, they won't honor the warranty. Is this true? Can we get some set of ground rules from them as to what they cover? I now record EVERY SINGLE SECOND I'm ever in the air to prove I didn't run into a tree or something just because so many people here want to see that video after a crash - but what other steps do we need to take to protect ourselves? Calibrating every single flight seems ridiculous, but will DJI say "you needed to calibrate, so we aren't covering this". We need a protocol to follow, or what's the point of ever going up if there's this little control? All this technology to make it "easier", but other RC crafts are nowhere near as temperamental.
After I upgraded the P3 to 1.1.9 firmware I got one compass error and alsmost lost my p3 too.
how can I export the data from the iphone and post it here?
how can I export the data from the iphone and post it here?
ianwood
Taco Wrangler
Blade, do you know what a "SPEED_ERROR" is?
The only two sources for speed are going to be GPS and VPS as far as I can guess. An accelerometer could give you an idea of speed but in the wind it's going to be noisy as all get out.
The only two sources for speed are going to be GPS and VPS as far as I can guess. An accelerometer could give you an idea of speed but in the wind it's going to be noisy as all get out.
Is it possible that one of the props was fractured from the prior crash and failed causing the sudden jolt? There was another post on here where somebody didn't notice that they had a failed prop.
So there must be several 1st owner/pilots to not know to calibrate the controller before 1st flight. It's a very basic procedure that takes less then a minute to complete. It is something that someone should not need to told to do it.
Now there is separate processes for 4 calibration procedures in the Pilot App. The IMU, Compass, Controller, and Gimbal.
My personal rule for Compass calibration is if moving around in different parts of your neighborhood, then No Compass Calibration needs to be done unless the app is requesting it.
If you travel outside of the neighborhood, then you Do need to Calibrate the Compass at each location you go to. Don't Forget to Calibrate again once you return back to your home location! Several forget to do this.
Humid - Moist - Wet Conditions.
The ESC's are sensitive to those conditions. It's best to stay clear of those conditions as much as possible. Don't forget about situations that can also cause the mentioned conditions. Such as flying in a snowy climate and somehow getting snow inside. Shut it down and get it dried out before you continue on. Or if it summer time with it much cooler inside and humid outside you bring your equipment out and a film of condensation forms, it can also be conditions you don't want to fly in. Hopefully this will help someone from getting into a bind.
Now there is separate processes for 4 calibration procedures in the Pilot App. The IMU, Compass, Controller, and Gimbal.
My personal rule for Compass calibration is if moving around in different parts of your neighborhood, then No Compass Calibration needs to be done unless the app is requesting it.
If you travel outside of the neighborhood, then you Do need to Calibrate the Compass at each location you go to. Don't Forget to Calibrate again once you return back to your home location! Several forget to do this.
Humid - Moist - Wet Conditions.
The ESC's are sensitive to those conditions. It's best to stay clear of those conditions as much as possible. Don't forget about situations that can also cause the mentioned conditions. Such as flying in a snowy climate and somehow getting snow inside. Shut it down and get it dried out before you continue on. Or if it summer time with it much cooler inside and humid outside you bring your equipment out and a film of condensation forms, it can also be conditions you don't want to fly in. Hopefully this will help someone from getting into a bind.
