Hi everyone !
I come to you as I wish I could find some answers to what happened with my P3P lately.
Please find flight log over here :
Flight Log
And please look at the video that will 'prove' flight log is just totally wrong (and will show you how "f..." close I was from a "disaster").
Footage
So basically what happened here: I was flying waypoint without troubles. Suddently I got this error message saying that the drone was switching to "atti mode" and that's when the drone went all nuts. First it speened and then became really really hard to control with actions not in adequation with control sticks movements.
I barelly managed to bring it back and roughly landed it.
What's bothering me here is that the flight log is just REALLY FAR to tell what indeed happened.
If you have a look at the "large map" in the general tab it shows that the serie of events happened quite the same point one the map when all these events actually happened while I was far away trying to get control back.
Looking at the flight log, well it says the gps signal stayed strong and good all time. If so, why the flight log doesn't show the real course of the bird ??? (looks like the last location of the drone was well registered before flyaway but once it switch the first time to atti, it disappear from earth, you know, like a drone getting zero gps signal after popping out the gps module cable for example)
The list of notification is also really weird (especially at event N while I was actually landing and it says I reached the maximul altitude flight O__o)
I actually had the same flyaway next day. I made a IMU calibration before in the morning (but not a compass one - might be a mistake ?)
Flight Log
This time I was lucky too but less. Managed to "crash" it from not too high in a field as there was no way to bring it back (stick responses were just too wrong). But it took me quite some time (and luck) to find it as I lost visual with it during flyaway ;-)
To give a little bit of background here, I recently crashed in shallow waters (total pilot stupid mistake). I made it repaired and they changed the motherboard. I only made a clean compass calibration, assuming they did on their side the IMU one (of course now they won't admit if they forgot...)
So I'm somehow wondering if it could be the result of a problem with gps module ? I mean, drone went in waters and if they just said that motherboard needed to be changed, it might also be possible that gps module could have been damaged...
Drone is now in service and they say everything's just fine with it...
They say that as I was flying close to a no fly zone, the compass was affected. Hummm ok but that flight close no fly zone was the second flyaway. How can you explain the first one ?
Anyway I find hard to believe there's nothing wrong with the drone. Does anyone see any valuable information in flight logs that could help spot the problem ?
Thanks very much for any input.
Best
I come to you as I wish I could find some answers to what happened with my P3P lately.
Please find flight log over here :
Flight Log
And please look at the video that will 'prove' flight log is just totally wrong (and will show you how "f..." close I was from a "disaster").
Footage
So basically what happened here: I was flying waypoint without troubles. Suddently I got this error message saying that the drone was switching to "atti mode" and that's when the drone went all nuts. First it speened and then became really really hard to control with actions not in adequation with control sticks movements.
I barelly managed to bring it back and roughly landed it.
What's bothering me here is that the flight log is just REALLY FAR to tell what indeed happened.
If you have a look at the "large map" in the general tab it shows that the serie of events happened quite the same point one the map when all these events actually happened while I was far away trying to get control back.
Looking at the flight log, well it says the gps signal stayed strong and good all time. If so, why the flight log doesn't show the real course of the bird ??? (looks like the last location of the drone was well registered before flyaway but once it switch the first time to atti, it disappear from earth, you know, like a drone getting zero gps signal after popping out the gps module cable for example)
The list of notification is also really weird (especially at event N while I was actually landing and it says I reached the maximul altitude flight O__o)
I actually had the same flyaway next day. I made a IMU calibration before in the morning (but not a compass one - might be a mistake ?)
Flight Log
This time I was lucky too but less. Managed to "crash" it from not too high in a field as there was no way to bring it back (stick responses were just too wrong). But it took me quite some time (and luck) to find it as I lost visual with it during flyaway ;-)
To give a little bit of background here, I recently crashed in shallow waters (total pilot stupid mistake). I made it repaired and they changed the motherboard. I only made a clean compass calibration, assuming they did on their side the IMU one (of course now they won't admit if they forgot...)
So I'm somehow wondering if it could be the result of a problem with gps module ? I mean, drone went in waters and if they just said that motherboard needed to be changed, it might also be possible that gps module could have been damaged...
Drone is now in service and they say everything's just fine with it...
They say that as I was flying close to a no fly zone, the compass was affected. Hummm ok but that flight close no fly zone was the second flyaway. How can you explain the first one ?
Anyway I find hard to believe there's nothing wrong with the drone. Does anyone see any valuable information in flight logs that could help spot the problem ?
Thanks very much for any input.
Best