Just for reference, what is the AUW on a stock p3 with stock battery?
P3P v1 with 960kV
All of a stock battery.
1298g in the air.
Just for reference, what is the AUW on a stock p3 with stock battery?
Pardon the intrusion here. The .DAT can be a little tricky if the flight exceeds about 700 secs. The .DAT will stop being recorded and then recording resumes by creating a new .DAT. This happened to you flight where it created FLY030.DAT and then FLY031.DAT. Looking at the whole flight can be done by concatenating the two .DATs E.g.
cat FLY030.DAT FLY031.DAT > FLY3031.DAT
and then submitting FLY3031.DAT to CsvView.
Here are the esc temps
View attachment 39366
Lolo,
I am a noob with csviewer, can you look at this flight for me and see what it tells you?
drone-share-temp
Looks like your ESC temps are getting up there. The most I've seen is 10x degrees. I've also seen this so you'll want to get some heat dissipation happening on the drivers.. I've also seen this so you'll want to get some heat dissipation happening on the drivers. The rears will work harder in forward flight so ideally you want to concentrate efforts there. I was trying to figure out a good way to draw the heat outside the frame without putting any mechanical stress on the chips.
@BudWalker thanks for posting the temps graph.
Looks like your ESC temps are getting up there. The most I've seen is 10x degrees. I've also seen this so you'll want to get some heat dissipation happening on the drivers.. I've also seen this so you'll want to get some heat dissipation happening on the drivers. The rears will work harder in forward flight so ideally you want to concentrate efforts there. I was trying to figure out a good way to draw the heat outside the frame without putting any mechanical stress on the chips.
@BudWalker thanks for posting the temps graph.
Lolo,
I am a noob with csviewer, can you look at this flight for me and see what it tells you?
drone-share-temp
Pardon the intrusion here. The .DAT can be a little tricky if the flight exceeds about 700 secs. The .DAT will stop being recorded and then recording resumes by creating a new .DAT. This happened to you flight where it created FLY030.DAT and then FLY031.DAT. Looking at the whole flight can be done by concatenating the two .DATs E.g.
cat FLY030.DAT FLY031.DAT > FLY3031.DAT
and then submitting FLY3031.DAT to CsvView.
Here are the esc temps
View attachment 39366
I looked for 100% pwm in beambubba's flight data and i see it happened for a second about 14min into the flight to the right front motor. Keep an eye on that to see if it gets worse with added weight and over time like mine.
View attachment 39379
If the RF motor maxes out, the AC will yaw counterclockwise. I don't have your log in front of me but I'm guessing that's what happenend?Forgive my ignorance on motor technology, but from what I have heard you guys say so far, there is no obvious explanation for the spin at 27 minutes into my last flight??
Actually, @beanbubba 's flight got split into 3 .DATs. I didn't mentioned it because the 3rd one was very short (824 KB) and didn't contain anything useful.Thanks for that! I'm wondering why beanbubba's 27min flight made two 300mb files and my 50min flight made a single 450mb file
Guys please give me a scheme/ wiring to fly 4s lipo without main original smartboard and battery? Thanks!
Actually, @beanbubba 's flight got split into 3 .DATs. I didn't mentioned it because the 3rd one was very short (824 KB) and didn't contain anything useful.
In your flight I'll bet there was another flight following the 450 MB .DAT.
Different FWs record different data in the .DAT resulting in different size .DATs for the same batteryOn duration. I also suspect that birds with a modified mix of FW modules can also cause this.
I don't know why @beanbubba 's .DATs are each 300 MB instead of the usual 450 MB files.
Forgive my ignorance on motor technology, but from what I have heard you guys say so far, there is no obvious explanation for the spin at 27 minutes into my last flight??
Could I have the .DATs for this? I'm thinking it's possible that this may be an artifact caused by how the .DATs were concatenated.I don't know much about stuff but if you look at the chart the right front motor hit 100%pwm in the middle of your flight and it hits it at the end too.
Id like @lolo780 's professional opinion. Look at the left front motor in the second and 3rd (zoomed in) pic the green dot is showing it to be maybe 100% and the readout on the bottom is showing 0%. Maybe means nothing but its odd he had a yaw issue at the end of the flight.
View attachment 39412 View attachment 39414 View attachment 39415
We use essential cookies to make this site work, and optional cookies to enhance your experience.