compass error mid-flight.. now what??

I don't think so - it looks like it was the RC mode switch. There is no mention of the FC switching:
Which flight? First or second? My post was the first flight, originally posted. Not from the .dat but from the .txt file. This is where the confusion enters, between the two. The second flight has an AC .dat. The first does not.
 
  • Like
Reactions: sar104
@sar104 ...This is what I saw in the original .txt log....

ATTI SWITCHpng.png
 
  • Like
Reactions: sar104
so.. im facin a trouble.. my job is especialising on aerial photography and videography.. and i really dont know what else i can do.. i cannot send it in as techs are on vacations.. so i need to know the faulty component to proceed myself with the replacement
This is not what you want to hear but it's something you should consider.
You say your job is specialising in aerial photography and videography ... but you only have one drone?
And it's an old P3 ... that was made obsolete by the P4 pro two and a half years ago?
 
  • Like
Reactions: RodPad
Which flight? First or second? My post was the first flight, originally posted. Not from the .dat but from the .txt file. This is where the confusion enters, between the two. The second flight has an AC .dat. The first does not.

Good point. I was looking at the second one (DJIFlightRecord_2019-07-19_[15-07-42] and FLY142).
 
i dont think that it has to do sth with the 2 years as it has almost 50 hours of flight time...
how can a manual switch conflict with auto switch?? if i hadnt switched i could have lost it...
fly070.dat isnt available anymore... so.. lets see what can we discover from fly 142.. i gave you everything i could..
and the riddle is getting on.. is that the imu?? if i swap it could that solve this flyaway attitude??
 
how can a manual switch conflict with auto switch?? if i hadnt switched i could have lost it...
I am not saying that it can. Only bringing up the possibility. There was no need for the manual switch because the aircraft was already in ATTI mode. Which means that if the Nav Health recovers, GPS positioning is automatically restored. Not so with a manual switch except for the availability of RTH.
 
  • Like
Reactions: RodPad
if.. thats the keyword.. and yes it recovered for a while.. it went into p-gps mode.. and thats why i pressed autolanding.. but the error showed up again.. thats why i flipped back to atti.. see airdata log.. but either way.. no compass means no rth.. or yaw error.. or whatever it was.. nobody seem to be able to understand what happened.. and thats a good challenge.. and here is my question.. if signal got lost.. drone would be lost as well??
 
if signal got lost.. drone would be lost as well??
In Auto Switch ATTI mode with signal loss, if I am not mistaken, the aircraft will land where it is. If , and I stress if you are in manual ATTI mode and GPS is available, it will Auto RTH.
 
youre right but.. it had yaw error.. how could it come back to me.. one time it was ok and the other wasnt.. how do i supposed to trust this kind of error?? i just want my star to be ok.. i want it to fly again without any problem.. it seem that there is no solution to this.. so.. before i give up im goin to try a compass swap and give it a try.. maybe its the compass witch is conflicting with imu and thats why all this.. maybe not.. if this doesnt work.. i would have lost 10€ .. but if it work.. i would have my little star back in the air in no time..
 
@xrider I am not seeing much in FLY142. However, I am speculating that this is more of a GPS related issue than that of the compass. @sar104 has already described what he was seeing. Maybe @BudWalker we can get another set of eyes on this.
 
whoa.. sar104 said that is imu related.. i said its compass related.. you now say thats gps related.. well.. thats a good trivia for all who like playin with them.. i m tryin now to figure out whats goin on in the .csv by the time the "yaw error large" occured .. from the values between imu and compass its seems that it threw off compass readings as they were sayin that aircraft was upside down and imu not.. so.. regardless of normal mod.. yaw raw isnt correct.. what the heck??!! it was tryin for a recovery witch it did and gps mode was back.. but when i pressed autolanding.. error showed up.. same values.. same thing.. well.. i feel that im missing something here as.. what was the cause of it.. i ve checked the soldering in the compass.. it seems okay.. ive checked several times the drone on the ground to see if that kind of error show up.. nada.. it can sense very well metal things.. its heading its correct.. but when up in the air.. compass readings are in disagreenment with those from imu.. whats the cause?? i like riddles a lot but this is a very tough one.. take off place is interference free.. im always checking about it.. what else could cause such a conflict?? ?
 
sar104 said that is imu related.. i said its compass related.. you now say thats gps related..
They all interact with each other. One or more are not playing nice together in pure basic terms.
 
  • Like
Reactions: RodPad
i know that.. but.. what causes this conflict?? what makes it fly away from me?? what do i do so wrong?? i know 99% of flyaways are pilot related so.. i feel guilty.. even if i dont know why.. ?
 
Over a year ago I nearly lost my P4 when it started to misbehave in flight. After take off I intended to use the course lock function so turned the P4 on to the course heading I wanted but I noticed that the P4 continued to turn slightly after I stopped the stick control and when I turned the bird back onto the desired heading it drifted past again. So although I noted this odd behaviour I didn't fully realise the danger. After I engaged course lock the P4 flew away but was in sight and I managed to fly it back. Luckily I was wearing brown cords. I landed it in a panic and checked over the drone. I did the compass dance and all seemed well so I risked taking off again (yeah, I know!!!) and it flew off out of sight beyond tall trees but I eventually landed 1/4 mile away and recovered it. The first lesson here is to note that you must take heed of any unusual behaviour by the drone and immediately land it to investigate.

I have to put my hand up and admit that this issue was an own goal - totally my fault. After recovering the P4 and while doing the compass dance for the 5th? time I realised that the compass error increased as I approached my P4 back pack. I first moved the pack a few yards to a new position suspecting that there was an object in the ground causing the anomaly and repeated the dance but the compass error persisted. It dawned on me that it was the pack itself that was the problem. I started emptying out the pack until the issue changed. The weather was cold and I had worn a pair of shooting gloves to the take-off site. I had taken these gloves off before flying and put them into the backpack from which I launched the P4. These specialist gloves allow the first finger and thumb to be exposed for operating the trigger/bolt on a gun. These parts of the glove are clipped out of the way by TINY magnets built into the fabric of the gloves. When I found the cause I felt like a complete fool because this silly mistake had nearly cost me my P4.

I thought that it was worth posting this info as a warning to others so that no one else falls in to this trap. I strongly suspect that the same problem has caused many of the reported flyaways. We all need to be aware that tiny neodymium magnets are built in to so many every day items - such as the clips on mobile phone and tablet cases, glasses cases, key fobs etc etc. After this incident I completely emptied out the back pack again at home and focused on a screen shade I had bought, but very rarely used, for the Nexus tablet that I use on the controller. To my horror I realised that the fold-flat screen shade when folded out and mounted on the tablet relied on built in flexi magnetic strips (as used on fridge magnets and shower doors) to hold it in shape. That shade immediately got binned and I made a replacement out of black card.

I then thought back to a non-DJI drone that I owned a year earlier. That drone eventually met its end when it started to fly erratically and uncontrollably. Because it had drifted near to houses and I was not in control so I was forced to initiate a forced motor stop to bring it down. Of course I couldn't remember whether I was wearing the same gloves but it did make me wonder. We live and learn. Fly safe.

All the best, Martin
 

Recent Posts

Members online

Forum statistics

Threads
143,086
Messages
1,467,527
Members
104,965
Latest member
Fimaj