That’s a very deterministic tool. There’s no need for LLM or machine learning to get that type of output (which is almost certainly the preferable way to do analysis of this rudimentary sort).
Right. Saying it’s “more useful” doesn’t mean It’s particularly useful. I was drawing a contrast with the present tool that doesn’t look useful at all.
1 Like
Hi @Juergen-Fahlbusch, the drone did undergo a hard landing when this issue occurred.
But after that, I have done around 11 test flights and did not experience any issue.
So the system had an hard crash impact,
afterwards it ssemms to be 11 times ok,
and now you had once or some multiple times or every time this error?
Please give a qualified answer.
For me it looks still that your FC get a crack by the crash, if you don’t changed anything other as the batteries.
1 Like
Yes, the system did have a hard landing earlier. After that, it flew normally for around 11–12 flights without any noticeable issues. The error only started appearing later — sometimes during flight and sometimes even while on the ground. I haven’t made any hardware changes other than swapping batteries. It’s possible there’s an intermittent fault or small crack on the FC as you mentioned
To rule that out, I swapped the flight controller and did a number of flights afterwards and now it is working well.
The flight controller in question I have inspected very closely but I couldn’t find any visible defect in it.
Electronic componants and PCBs can crack internally which is not ssen by normal eyes or a normal magnifying glass. Also a microscope is not always enough to detect these kind of cracks. So you have to x-ray it to get these kind of failures …
…or throw the FC in the trash can
1 Like