HELP! analyse the reason behind crash

Pixhawk Crash Analysis

 

Date:19-05-2017

Time: 4 – 7 p.m.

Weather: Calm, sunny day & with no or little wind

Temp: 37-32 C

Plane: Volantex Ranger

Board: 3DR Pixhawk loaded with plane 3.7.1

Battery: DIY 3s pack 20400Mah made from Panasonic ncr18650b

 

After programming the board, today was the first test flight. I took off in manual mode, trimmed the plane and flown it for almost 10 to 15 minutes in manual mode without any problem.

Then I switched to FBWA mode the plane handled the flight very well with the stock parameters and without any tuning at all. Then I switched to FBWB mode and the result was great flight. After that I switched to cruise mode where I faced only one issue: The plane was holding the flight path really well but with some roller coaster motion (something that I know is having to do with tuning). After that I switched to loiter and the plane started performing good circles thought I haven’t calibrated the airspeed yet. Only then and after making sure that the plane can fly itself I switched to RTL mode and the plane came back to me and started loitering at 200m altitude which I had set for RTL altitude.

Now it was the right time to start the auto tuning progress. I went ahead and did the roll tuning, then the pitch tuning and everything was good. After that I checked the tuning page on my mission planner and the parameters were changed to the new set of the auto tuning. Afterwards I started applying rudder inputs to tune the yaw and here the problem started. After few rudder inputs the plane stopped responding and went into a turn towards the ground with the rudder stock in one end. While the plane was going down I switched out of Auto tune and tried all the modes but without getting any response from the plane even in manual mode.

It was at that moment when the plane sat on the green field about 500 meters away from me. When the plane hit the ground the radio announced “RSSI CRITICAL”.

When I reached the plane opened the canopy the led indicator of Pixhawk was indicating failsafe. The plane wasn’t damaged at all and I didn’t notice any damage to the electronics as well. Of course I haven’t checked anything yet.

I had the screen recorder on my laptop recording the screen and now when I came to see the last seconds before the crash I realized few things that I wasn’t aware of as I had the sound muted on my laptop.

            

31’ 20”                    in to the flight                        started the yaw tuning

31’ 27”                    in to the flight                        3 yaw inputs so far

31’ 28”                    in to the flight                        bad AHRS

31’ 29”                    in to the flight                        error caused vert variance   

31’ 36”                    in to the flight                        6 yaw inputs and I realized that something is not OK with plane

31’ 39”                    in to the flight                        warning no data for 10 seconds

31’ 40”                    in to the flight                        changed to other modes

31’ 44”                    in to the flight                        earning no data for 15 seconds

31’ 46”                    in to the flight                        I was sure that the plane is not responding at all

31’ 55”                    in to the flight                        warning no data for 25 seconds

32’ 05”                    in to the flight                        RSSI critical (from Taranis)

32’ 08”                    in to the flight                        Telemetry lost (from Taranis)

32’ 21”                    in to the flight                        Telemetry recovered (from Taranis)

32’ 23”                    in to the flight                        Telemetry lost (from Taranis)

32’ 42”                    in to the flight                        No RC Receiver

                                                                                 Error caused vert variance

                                                                                 Bad AHRS

                                                                                 Error compass variance      

Same errors continued for several minutes till I reached the plane and turned it off.

                                                                                 Telemetry Recovered, RSSI critical, Telemetry Lost, ….

Now when I connect the Pixhawk to the PC I get a solid red light and I cannot get it to connect to mission planner.

I’ll try to go through all the components one by one to see if I can detect any error or issue starting from tonight.

Guys, please give me your thoughts and ideas on what could be the cause

Many Thanks

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies



  • Tom Pittenger said:

    Log shows it as a power failure. Power overload, not a software problem.

    I'll post the Tlog ASAP.

  • The problem that I have now is that I'm unable to get the pixhawk to connect to mission planner. The red solid light is indicating an error. I've tried to flash different firmware but nothing happened. I've tried flashing the px4 pro using QGround Control. It works and the solid red changes to blinking red and it won't go off.

    The BOOT file located on the SD card says:"no px4io board found"

    I've tried flashing the master firmware it works but still the error on the mission planer is:"no px4io board found"

    Any ideas on how can I solve the issue?



  • Tom Pittenger said:

    Log shows it as a power failure. Power overload, not a software problem.

    Well, due to the plane not responding at all it might be true that the problem is a power failure. I think it needs more analysis.



  • Andre K. said:

    here is the link:

    https://github.com/ArduPilot/ardupilot/issues/6300

    Hopefully, something good, will be the result of this crash/very creative use of autotune :)

    I hope so. Maybe this crash could help preventing something bad in the firmware.

  • Developer

    Log shows it as a power failure. Power overload, not a software problem.

  • please post .tlog for that flight (telemetry log, stored by your GCS)

  • here is the link:

    https://github.com/ArduPilot/ardupilot/issues/6300

    Hopefully, something good, will be the result of this crash/very creative use of autotune :)

    Plane: Crash, partial data freeze, during unusual autotune procedure. · Issue #6300 · ArduPilot/ard…
    Forum user posted this log: http://diydrones.com/forum/topics/help-analyse-the-reason-behind-crash?commentId=705844%3AComment%3A2379548&xg_source=msg…
  • That 72 second interval has no log entries; between log index 1527975 and 1527976, TimeUS jumps from 2070 seconds to 2141 seconds. 

    Andre K. said:

    Like Graham already pointed out, there is no yaw tuning, and if you rolled plane enough, using rudder, it could very well get some crazy PIDs - but there's something worse heppening here.

    There are some 72 seconds between the failsafe kicks in, and the crash, where there is no elevator/aileron movement, not even a realistic change in elevation  (GPS & baro) or attitude.  Basically, much of the data and control surfaces are just frozen during the descend.

    I'll create a issue on github for this case. suspecting a nasty bug somewhere.



  • Andre K.

    Well, Maybe there was a problem in my understanding of the manual where it says that the yaw tuning is optional. I might misunderstood the point that yaw tuning is part of the autotune process.

    As for the control surfaces not moving you are absolutely right. After this point of the flight:

    "31’ 36”                    in to the flight               6 yaw inputs and I realized that something is not OK with plane"

    the plane didn't respond to any input not even in manual mode. and I was able to see the rudder is stuck in one direction also.
    it would be great if you could also post the github link here.

    Many thanks for your great efforts guys

  • Like Graham already pointed out, there is no yaw tuning, and if you rolled plane enough, using rudder, it could very well get some crazy PIDs - but there's something worse heppening here.

    There are some 72 seconds between the failsafe kicks in, and the crash, where there is no elevator/aileron movement, not even a realistic change in elevation  (GPS & baro) or attitude.  Basically, much of the data and control surfaces are just frozen during the descend.

    I'll create a issue on github for this case. suspecting a nasty bug somewhere.

    Screenshot from 2017-05-22 14-25-40.png

This reply was deleted.

Activity

Laurie J. Troy liked Jasper Kueppers's profile
Apr 1
Timothy Miller liked Joseph Udofia's profile
Mar 18
Joseph Udofia liked Joseph Udofia's profile
Mar 3
More…