(I’m 0a23cb7af4d242 on rcgroups)
first, congrats to your great fork! I tested it a bit and I’m really tempted to switch over to it for my h8 mini blue boards (great layout, defines for different boards, inclusion of joelucids yaw drift fix, features like torque boost etc. are definitely worth it), the only thing that prevents me from doing it atm is the airmode/idle up/arming/safety-topic, it seems that I can’t configure it the way I am used to. I never used betaflight which probably adds to my confusion.
I’m not sure if you are aware of the AIRMODE_HOLD_SWITCH-feature in silverware? It never made it into the bwhoop-branch, and I feel like I’m the only one who ever used it. As far as I understand, it is the same like your idle-up function, but a) it makes also sure that all motors stop when the configured channel is triggered and b) it is only activated after initial throttle has been given. Maybe it can help you figuring out how to prevent the props spin up when binding, I don’t know. I’m using it on all my silverware quads (H8S/H101, H8 mini green and blue boards) and mapped it to the throttle kill/hold-switch.
In addition, I’m using the “sticky throttle hold” on all my devo modelfiles like described here: https://www.deviationtx.com/forum/how-to/1953-how-to-create-a-sticky-throttle-hold . I think it is basically the same like your arming-function.
Now here is my confusion: when I’m mapping the arm and idle-up function to my hold-switch and toggling it, the props start spinning, regardless of the trottle position. It seems to me that idle-up overrides the arm safety function, also the sticky throttle hold is being ignored.
I really like your high-configurable approach, so I think that it might be even much better than AIRMODE_HOLD_SWITCH, but it seems that I can’t figure out how it is supposed to work. Do i need to map both functions to different channels when I don’t want the props to start immediately, or is there something wrong in my configuration?