Scanning encoder debounce on new scope

[Demon]

... Anyway, since you master the art of software, I think is waste of money to add hardware when you can debounce in software.

Plenty of ways to do that and as you said, going into production, will save you a lot of money and complexity....

I know. But I haven't started coding yet and don't know exactly how burdened my processors will be. I prefer to start with hardware debounce, and then see as I advance. It's a lot easier to take stuff off a PCB, than to add it all later.


...insert drum roll and trumpets here...

I present to you, the Encoder Driver v1: 24 encoders, 1 switch, debounced according to Bourns, inverted via 74HC14 Schmitt triggers, in a 30mm x 160mm vertical package. I have 180° pins on the design, but it'll be 90° pins on the final product.

[Ioannis]

Hmm, too many wires to connect switches and encoders. Have you thought about that? For a production this is very time consuming.

Ioannis

[Demon]

No more wires. It's unrealistic.

I changed to a single main board for all switches. The ADC, MCP (switches and LEDs) and encoder drivers will be placed around the perimeter with headers.

So now I'm down to just soldering the switches, pots and encoders.