Hey, recently, when I was flying my apm based quadcopter, it suddenly crashed.
I have downloaded the log file … can anyone help me by analysing the log files..
I am attaching it down below.
2026-03-22 17-47-39.bin (41 KB)
2026-03-22 17-48-39.bin (264 KB)
Those logs are not usable. Is it really an APM flight controller, or something using Arducopter 4.7 to match the category you chose?
Yes , it is from an apm fc .I have downloaded it from the mission planner
In my mission planner it is opening.
Then it’s certainly not running 4.7 so you posted in the wrong place. It belongs in Unsupported Hardware. And those logs don’t open for me either. Usually is you can attach a .bin log directly to the post there is something wrong.
Moved the post to unsupported hardware category as suggested.
It would probably open in mission planner from 2015
No. The basic log file format should still work. The attached files are not useful.
I think moderators need to enable settings individually for each category. Up until a couple days ago, the option to “Mark as solved” wasn’t present either.
Yes,
Crash Log.log (73.0 KB)
I was running an old mission planner .
Here are the new log file from the latest mission planner
Yes, we need to enable the solution setting per category. It is not enabled for this category because we don’t really arrive at “solutions” for unsupported hardware.
No, we do not change the attachment file size per category. Dave’s point is that the file size is too small to even be a proper .bin log at all.
OP has now uploaded 3 different files, supposedly all from the same flight. A properly retrieved (or uploaded) .bin log would not differ, regardless of GCS version. It is stored in binary format by the autopilot itself.
As worthless as the others. If you want to waste some time APM Planner will open it with errors.
Ah, I was referring to 4.7 category. I thought it was still in 4.7 and log attachments wasn’t disabled yet
Is there any solution for it?
But in the old firmware i can see the parameters of the log file. But now in the new , I can’t .Can you explain why?
I can only suggest that you replace the Flight Controller with a supported one.
Can you try linking the log files after uploading to a cloud storage?
I’ll give you one piece of advice. With only these fields available in the log, from the Log Bitmask, it’s very limited in what one can determine as cause.
Then is the solution to upgrade the fc to another one?
Yes.
Go for h743 if you can afford but f4 series are still usable if on budget
That was suggested to you 5 yrs ago here on the forum.