I tried using a 16-bit number here (0=off, non-0=on, as I’ve done with other custom channels and boolean expressions) and the strategy said “Active” the whole time, even when my custom channel was 0. I also have a Pit Speed Limiter, but there I use the “Pit limiter switch” rather than a custom activation, so I haven’t tested whether custom activation channels are broken there too. I needed a solution ASAP and quickly moved on by using a Variable Target instead (300kph = off), but it is probably worth looking into. Thanks! Using firmware 261.0, client/ui 261.0.1.
I had this issue if raw channel is not 0 ( if you have an offset) you have to assign function to pit limiter switch
What kind of 16-bit channel are you used in the original setup? It’s a Number from Project Tree or a CAN RX Channel or maybe something else?
Sorry didn’t see your response until now. It was probably a CAN RX channel. But I would also like it to work with a number from a project tree if possible.