Tumbleweed, that's the thing. I'm still at the research phase; trying to determine what Henrik calls velocity sensing.

Next challenge: Velocity sensing, ie a way to detect that the user wants the value to change by a lot and not have to turn the knob 600 turns. Getting that just right seems to be tricky, even the big boys don't always... (I've never tried).

I can flick the rotary encoder at 3.5msec from low-low to high-high, but still need to determine that cut-off speed.

https://www.picbasic.co.uk/forum/sho...000#post156000


And then it hit me as I'm typing this post. I can use the logic probe in real-time to find that sweet spot, instead of writing code to display that on LCD (or xmit via HSEROUT). And that's where things get crazy cause all that extra code and I/O would definitely throw off my readings.

Can't see the forest for the trees...