SpeedyBeeF405WingMini - Custom Firmware Builder

If a firmware has been created using Custom Firmware Builder and is 100%, is this software then save or beta? Is there a way to test this software without flying?

Which module must be activated in the “Custom Firmware Builder” for DISARMID/ARMID to work? Currently ARMID is always active (parameter has no effect).

Mission Planer – DATA – Arm/Disarm
Do jou wish to Force Disarmed? (Yes)
Error: command rejected by MAV

Does anyone have an idea how to get back to DISARMID so that you can calibrate the SpeedyBeeF405WingMini?

If you make this selection in the custom builder, then it is safe:

image

Arm/disarm should always be available.

Thanks for the information.
Regarding DISARMING/ARMIN, I’m still looking (trying).
I still hope that I can find the right cause/description for this.

You always write about …ID. I believe this is some misstyping or did you really mean some “ID”
Several parameters are available to handle the arming behavior. All these parameters start with “ARMING_”. But I believe this is not new to you.
How is your ARMING_REQUIRED parameter set. If 0 allways arm immediately.
Also if ARMING_CHECK = 0 don’t mean “all” as shown in the wiki.