Recently I have built a drone using Pixhawk 2.4.8 flight controller.
I have used 920 KV motor and 9450 propeller. There is no GPS module used.
Each time I am trying to take off my drone, it starts taking off for few inches then gets tilted one side and gets crash landed.
Can anyone suggest me to resolve this issue.
Could be lots of reasons. Share a .bin log from the flight, otherwise it’s just guesses.
Have you checked motor direction and motor sequence using the motor-test feature?
And yes, please share the .bin log.
Sure.
I am going through it. Will share any update soon.
Here is one of my log files - https://drive.google.com/file/d/1m-6lYdUbgU4anH9QqcyYNmVikhZ_8wtW/view?usp=sharing
Recently I got to know about logs, I found out there were total 29 .bin files. Some of them are over 1MB in size but when I am trying to analyze the log it is saying that the duration is 00:00.
Does this indicate any fault?
here is one of by analysis:
Log File E:\APM\LOGS\00000028.log
Size (kb) 1445.1953125
No of lines 19710
Duration 0:00:00
Vehicletype ArduCopter
Firmware Version V4.6.3
Firmware Hash 92b0cd78
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (2.12%)
Test: Dupe Log Data = GOOD -
Test: Empty = FAIL - Empty log? Throttle never above 20%
Test: Event/Failsafe = GOOD -
Test: GPS = UNKNOWN - No GPS log data
Test: IMU Mismatch = NA -
Test: Motor Balance = UNKNOWN - ‘QUAD/X’
Test: NaNs = FAIL - Found NaN in CTUN.TAlt
Found NaN in CTUN.DSAlt
Test: OpticalFlow = FAIL - ‘FLOW_FXSCALER’ not found
Test: Parameters = FAIL - ‘MAG_ENABLE’ not found
Test: PM = UNKNOWN - ‘NLoop’
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = UNKNOWN - No CURR log data
Have you armed your copter again after the flipping?
If not, then the highest numbered log file is the one of the flipping.
Take then bin log and open it in “review a log” and also attach it here.
Plot some value and you will be able to see the data
Auto Analysis is worthless. You have to do a proper Log review.
And, that firmware is 7 years old. You can’t advance without updating to the current stable version.
It also looks like this is on default parameters.
Start over with the Methodic Configurator.
Issue Resolved – Thank you, everyone!
I wanted to share the root cause in case it helps someone else in the future.
After spending quite some time troubleshooting and reviewing logs, I finally discovered that the problem was entirely on my end. I was unknowingly trying to fly the drone while it was in ESC Calibration Mode, not in the normal Armed mode.
Because of that:
-The motors responded abnormally.
-The Pixhawk never actually armed.
The dataflash logs showed no “Arming Motors” event and the motor outputs remained at their minimum values, which initially made the diagnosis confusing.
Once I exited ESC calibration mode and armed the vehicle normally, the issue was resolved.
Thank you to everyone who took the time to suggest ideas, analyze the symptoms, and help me troubleshoot. I really appreciate the support from this community—I learned a lot about ArduPilot logging and the arming process along the way.