There is a problem with the altitude presentation that I'm looking into. I think the entire flight was at roughly the same altitude, around 25 meters.
Can't see motor speeds yet.
Bummed. New P3A Crashed. Pls Advise
- Thread starter McVenturesRC
- Start date
Can't see motor speeds yet.
- Joined
- Oct 16, 2015
- Messages
- 548
- Reaction score
- 123
- Age
- 58
Thank you Budwalker for providing these tools and for analyzing the data.
Can we download this tool as well?.
Is it possible to calculate the oriontation?
What more information is in the log file?
The motorspeed could shed some more light on the cause of the crash.
Oso
Premium Pilot
Hi Jobe and welcome to the forum. Please don't think that any question is ignorant. Most of us are happy to help.
No, I didn't mean that data power and main power come from different batteries. I meant that they come from different connections on the same battery.
If you look closely at your P3, you will see that there are 4 spring activated power connection points just below the two large power connection points. This was why it was speculated back in the early days of the P3 that some people were losing power but not data when they weren't fully seating their batteries. Someone here even posted pictures of the very small gap between the first click and the second click on batteries that needed two clicks. Like I said, I have three batteries and only one of them needs the second click. I'm not sure how pervasive this is now several months into production.
This was one of the potential causes of this particular crash that I was speculating about when the thread was relatively new. Cheers!
The preflight lasted roughly 133 seconds. During that time a compass calibration was done. This plot shows the MagMOD data during the preflight.
I'll speculate that the increase in MagMod happened when the calibration was finished. I.e., this calibration actually resulted in the magnetometer being further out of calibration. I don't think this was the cause of the crash though.
BTW, I've noticed that MagMod data usually shows a higher value than what is seen while the P3 is on the ground before launch.
I'll speculate that the increase in MagMod happened when the calibration was finished. I.e., this calibration actually resulted in the magnetometer being further out of calibration. I don't think this was the cause of the crash though.
BTW, I've noticed that MagMod data usually shows a higher value than what is seen while the P3 is on the ground before launch.
Oso
Premium Pilot
@JoBe - here is an older thread that I found with a video of what I was talking about regarding the one or two "clicks" of the battery before it is fully seated and securely connected to both data and main power.
Caution - Batteries don't fully insert without force | DJI Phantom Forum
Bud what about the below screenshots of the flight map that show the descent. It seems like it something had power all the way down.
. Also Bud can you post the two .csv files somewhere not file sharing site? I cannot access dropbox or other file sharing sites....really want to see though!
Last edited:
Ya there a prop wrench, 1 reply later there a picture that shows it
Right there before your eyes,
Oso
Premium Pilot
Not saying at all that this is the cause of the crash in this thread. Nobody really knows. We are all just speculating and trying to sift through the data as it becomes available. Its a good learning exercise for everyone.
All I was saying is that my take on the early data was that the P3 was no longer powered for flight, but that it was still recording data all the way down to impact with the ground. My suggestion about the battery fit that scenario based on issues seen with pilots several months ago when the P3 first came out. That doesn't mean its the root cause. We may never know the root cause for sure, and it could even just be some sort of electronic failure not even mentioned in the thread.
Oso
Premium Pilot
No "tightening" wrench. It doesn't say "tightening" is the point I think.
I saw that. I suppose it's possible that the file got truncated either on the upload or when I retrieved it. I'll have to check later. I'll also post those .csv for you. If you had the .DAT you generate them yourself
No.. there isnt. There is a prop wrench. There is never any mention from anyone associated with DJI that ever said it was for "tightening"! It is VERY well documented that the props should be tightened by hand. And the only mention ever of the use of the wrench is to REMOVE a prop that is too tight to remove by hand.
So what is it? Make up your mind.
I only said a prop wrench came with the kit. Never said anything about using it to tighten props, but there is a wrench. And if you say it's to take off over tight props ok.
YOU were the first person to say "prop tightening wrench" on the forum, not just this thread, since EVER! You created a term, which sole purpose is to describe a wrench that tightens. I only replied to what YOU stated. dont get mad at me for pointing it out!
I'm far from mad, I just saw a Prop wrench in the kit. And asked why does DJI include this. To undo a struck prop works for me.
And I guess going with the undo answer makes sense. Like an oil filter
Wrench. Hand tighten, wrench off sometimes.
Dale
Have the same info using Dashware and the Fly013.csv posted . The Datconverter has worked well with all my flights but this is weird.
Altitude difference is not even 1 meter. The amp draw is around 1.2 when a flying P3 is around 13 Amps.
So seems that either csv is not correct or there is a communication error. Interesting that healthy drone indicates 106minutes per battery - maybe flight time too short to calculate?
Here are the two .csvs. I checked and there doesn't seem to be a problem with files getting truncated either on the upload or when I retrieved it. Of course it could be a intermittent problem. Let's think about this some.....
Similar threads
