Looks like this post has come back from the abyss! How can we not be trying? Everyday posts were randomly disappearing... Hopefully that's fixed now, as I can see more and more of my posts reappearing.
Holy crap! Are 1 in 4 posts here really mine? Guess I talk too much...
You question me a lot. And it's good. Cos i sprout ideas without double checking.
If I were naming the board as my own project, I would like call it something with my name in it. Hazelboard, Hazboard,HazeLUX.
Sadly this is a group effort. So therefore I will put my vote into:
LUX = p Its elegant, but slightly cheesy. I don't think it needs any more to it. = p
or maybe
Aura
Radient
Dawn
Back on serious topic:
I think allowing for both polling and LED lighting at the same time should work. The debounce(?, its in the code) of 5ms and poll rate of 1kHz(?,im unsure but this is what most keyboards are,ye?) will lead to a LED that won't flicker.This is pretty much exactly the design that Prin has done. I'm considering having the transistor only drive the current/voltage across the LEDs and not both switches and LEDs.It makes for slightly easier analysis/less area to have fault,I think. Row pins are sensitive to voltage and LEDs are sensitive to voltage, but are nicely controlled with current control.
If anyone knows what I'm saying in the following (and I still make sense) then please comment:
I want to use a NMOS for the column and have the source to ground (might need use a resistor to bias current). And at the positive rail use a PMOS and active low with combination of the row select pin to the base.
This is my design. It's like Prins, but the main thing we don't have to worry about is the voltage given to the Row lines for detecting closed switches. Also no extra/unaccounted current flowing through the "switch circuit":
[ Attachment Invalid Or Does Not Exist ] 39801[/ATTACH]