Hello everyone. Yesterday, for the first time, we encountered this pre-arm error: “PreArm: CrashDump data detected”. We have the same configuration on more than 30 aircraft and identified this problem yesterday for the first time.
Our setup:
Cube Orange+
Kore Carrier Board
Dual Here4
25kg TOW
Autopilot FW: 4.5.7
Could you please help me identify what caused this?
Thank you guys
crash_dump.bin (138.0 KB)
This is a user induced race condition.
You have a non zero BRD_BOOT_DELAY value and the board was processing the delay when the GCS sent in a command to change mode to BRAKE - which the autopilot responded to.
The mode change attempted to use the position controller - but the autopilot was not far enough in the boot process to have allocated and created the position controller.
The resolution is to shorten or eliminate the BOOT_DELAY and re-flash the board to remove the crash dump data.
This is a boot race condition not a flight risk.
Sorry, I didn’t quite understand what happened.
In this case, since this is the first time this problem has occurred and we have over 40,000 flights, do you think we need to change this parameter?
So, was it a brake command sent to the AP right at startup that caused this ?
Yes. Sent before the autopilot was fully ready to receive it.
Thank you Craig
Do you have any idea why that brake command was sent? any Script ?