I have recently purchased a new PixHawk, and have had some exposure to programming flight controllers (Naze32 Acro, Naza etc).
I installed Mission Planner and ran through the wizard from start to finish supposedly successfully (I am using a Taranis Plus with X8R Rx). The only flight modes I programmed in were Stabilise / Auto / RTL on one 3 way switch.
I powered the quad up, and it gave me the flashing green LED to indicate GPS lock, I ascended to around a metre off the ground, where for 30 seconds or so, I was able to move left / right / forwards / backwards with no issues. Suddenly, it started moving backwards (towards me) and failed to respond to any inputs (I did not try the flight mode switch). At that point it ran into a chair. I checked all basic settings, and tried again, and once more, it ascended, then failed to respond to any inputs including completely dropping the throttle.
Can anyone possibly point me in the right direction on what to check? Any help would be greatly appreciated here! Thanks!
I haven’t looked at all your logs just the top one…but you had a battery fail safe…your voltage dropped to 10V, and you have battery fail safe set to return to launch…so it RTL’d as set to.
RTL is great, but you need to understand it…and also be confident your copter can loiter properly before using it, I know you didnlt say you had loiter issues, but many fly aways are due to RTL kicking on a copter that doesn’t loiter properly, often the operator is unaware that loiter is bad and needs sorting but has RTL enabled.
Thanks, I can’t remember which one was the actual log from the flight sorry. I had it out in the backyard a few times, and I know the LVC kicked in once before I actually launched (at which point I swapped LiPo’s).
OK, I had another quick flight tonight in AltHld mode, and again it flew fine for a minute, then the LED started flashing orange, and it suddenly started ascending rapidly. Luckily, I had tied some paracord to the landing gear, which managed to hold it till I dragged it back down.
The flight log shows the following:
Log File C:/Users/Jackson/AppData/Local/Temp/tmp6A9C.tmp.log
Size (kb) 333.1630859375
No of lines 4951
Duration 0:00:22
Vehicletype ArduCopter
Firmware Version V3.2.1
Firmware Hash 36b405fb
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Balance/Twist = GOOD -
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (18.96%)
Max mag field length (626.76) > recommended (550.00)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FS_BATT CRASH
Test: GPS = FAIL - Min satellites: 4, Max HDop: 10.39
Test: IMU Mismatch = GOOD - (Mismatch: 0.24, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = GOOD -
Test: Pitch/Roll = FAIL - Roll (93.97, line 4091) > maximum lean angle (45.00)
Test: Thrust = WARN - Avg climb rate 66.72 cm/s for throttle avg 761
Test: VCC = GOOD -
My understanding of the log reads that it went into RTL once more due to low voltage? Is that correct?
What is a safe low voltage setting for a 3S 2200mah lipo?
2200 mah appears pretty small for a 450 sized craft. If you have multiples of this size you might consider wiring a couple in parallel.
Best practice would suggest not using more that 1760mah on a fully charged lipo and not lower than 10.2 V on a 3S. A cheap battery alarm plugged into the balance port may help keep you out of the FS zone.
[quote=“equinox74”]OK, I had another quick flight tonight in AltHld mode, and again it flew fine for a minute, then the LED started flashing orange, and it suddenly started ascending rapidly. Luckily, I had tied some paracord to the landing gear, which managed to hold it till I dragged it back down.
The flight log shows the following:
Log File C:/Users/Jackson/AppData/Local/Temp/tmp6A9C.tmp.log
Size (kb) 333.1630859375
No of lines 4951
Duration 0:00:22
Vehicletype ArduCopter
Firmware Version V3.2.1
Firmware Hash 36b405fb
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Balance/Twist = GOOD -
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (18.96%)
Max mag field length (626.76) > recommended (550.00)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FS_BATT CRASH
Test: GPS = FAIL - Min satellites: 4, Max HDop: 10.39
Test: IMU Mismatch = GOOD - (Mismatch: 0.24, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = GOOD -
Test: Pitch/Roll = FAIL - Roll (93.97, line 4091) > maximum lean angle (45.00)
Test: Thrust = WARN - Avg climb rate 66.72 cm/s for throttle avg 761
Test: VCC = GOOD -
My understanding of the log reads that it went into RTL once more due to low voltage? Is that correct?
What is a safe low voltage setting for a 3S 2200mah lipo?
