Hello, despite spending many hours analyzing the flight logs, I still can’t understand what happened. The aircraft was performing a very simple mission (I was trying to improve the rate of descent) and suddenly, all the engines shut down and the control stick became inoperative (I tried to save the aircraft by switching to FBWA mode). Obviously this resulted in a big crash destroying the plane. In the logs there is nothing obvious about voltage drop or any electrical problems. There are also no errors. The log just stop abruptly at the moment I heard the plane cutting everything and starting to fall. So I am very doubtful now about the cause of this crash. I verified all electrical continuity in all wires and nothing seems problematic. I verified the battery and it was near full after the crash, and all cells was also individually ok. So, could it be the Flight Controller ? It is a relatively robust one (Pixhawk 6c mini v1.5) with good power module so I don’t think so. The only thing that remains is the software…but could it be possible that arduplane just cut off without any warning signs in the log ?
If you want to examine it in detail, you should use log analysis tools such as GitHub - ArduPilot/UAVLogViewer: An online viewer for UAV log files Artificial intelligence also provides correct answers about 70-80% of the time when examining log records. At least if you identify where the problem lies, you can conduct a more detailed investigation. Safe flights.
@asikarastallion you are putting too much faith on AI.
AI has not been trained in flight log analysis, it alucinates a lot, the same for configuring and tuning: not explicitly trained = bad answers.
@amilcarlucas I apologize for misrepresenting myself.
I am aware of the risk of hallucinations in flight logs with general-purpose large language models. What I meant was to analyze specific models such as MTCL-UAV, which are trained directly on UAV anomaly detection and time series analysis, and labeled aviation datasets such as the ALFA Dataset, rather than general models. Best regards
That would indicate a catastrophic power loss to the Flight Controller.
Not that it would cause this problem but you have an odd servo outputs configuration. Chan1-8 are set for Dhsot150 which are configured for Flight Control servos. Chan 9-12 are PWM configured for the motors ??
Ok thanks. In the examples you refer to, what was statistically the most prevalent cause? The battery failing ? the power module ? a short circuit somewhere ? the FC itself ?
Well I finaly found the point of failure. And it was….the Battery. Despite looking good at first glance, the third cell has a very strange behavior (at least I never seen that before). I cycled the battery multiple time on bench to monitor it. And what I discovered is that from time to time (looks ramdom) the third cell disconnect itself, cutting the entire battery. I saw previously that this cell has more discharge than the others. This is a common problem showing that the battery has to be replaced but that never affected my flights before. This is the first time I see a cell completely cutting the voltage continuity between its poles.
