XeCutor wrote:I'll improve my issue report a bit. I've changed from a 2-pos switch to a slider, and if I got to the Aux-tab with the slider in low (1000-1200) it's showing LL as it should. As soon as it goes above 1200 it goes to L, above 1400 to M, above 1600 to H, so far so good. As soon as I go above 1800, HH never lights up, but H stays lit and M lights up too. It's the same thing you can see in the screen shot from my previous post. H then stays lit regardless of where the slider is turned, and M, L and LL are also lit up depending on the slider value. If I go to some other tab and back to aux again, the constantly highlighted H value is gone. It looks as though it's only a display issue, the 5 distinct steps seem to all work.
yes, it'll be a bug in the configurator code I imagine, thanks for testing it and reporting back.
I'm currently still trying to decide how best to tackle aux configuration.
My current thinking is to stop using MSP_SET_BOX and MSP_BOX commands and do something different. Not least because the MSP commands are referring to visual representation of the UI rather than being named after the behavior they should invoke!
I'm thinking of an MSP command allowing you to simply say: When channel N is in range X to Y then activate mode Z.
This would then allow for people to use 5 pos, 6pos, 3pos, sliders, knobs, sticks, whatever. Being locked in to 3/5/6 is a bit pants no matter how you look at it.
Not only would this get rid of the horrible bitmask code that all the GUI and FC software has to deal with, it would enable users to do exactly what they want AND be able to provide meaningful configuration in a text based form rather than an unportable integer representation of a bitmask which means nothing to anyone and cannot be re-used if the list of modes change. This would also simplify sharing of aux configurations between users too.
I worked out the worst case storage scenario of the data for all the modes cleanflight has and it turns out that since most people never tick more than about 20 boxes the current solution is actually very wasteful of flash and ram usage.