LED Problems on RS96

[Steezus]

I should start off saying that this is my first attempt at building a keyboard. I am in the process of building a RS96 and after soldering all the switches(except for 2 because of shortage) I ended up with only 1 LED working. I put sip sockets in each switch with white LEDs. I swapped some LEDs around, put in ones with longer stems, etc. and nothing worked. A decent amount of the sip sockets had the stems sticking past the pcb as well.

Imgur Album: http://imgur.com/a/yXxof

[flabbergast]

Which one? I mean - is the caps lock or num lock led, or just a random one in the middle of the keyboard?
AFAIK there are 3 independent led "sub-circuits" in RS III: caps lock, num lock, and backlight (i.e. all the other leds together).

[Steezus]

Which one? I mean - is the caps lock or num lock led, or just a random one in the middle of the keyboard?
AFAIK there are 3 independent led "sub-circuits" in RS III: caps lock, num lock, and backlight (i.e. all the other leds together).

Out of the 98 keys that are soldered in, only 1 key that is in the num lock position has a working LED.

[flabbergast]

There are just 2 MCU pins that control all the other LEDs, namely one for caps lock, and one for everything else.

Well then it could be firmware problem (have you tried TMK?), i.e. the firmware is not actually turning the LEDs on.

Or it could be a hardware problem (the signal from the MCU does not arrive to the LEDs). This is harder to diagnose, but if you have a multimeter you can check the connections (the caps lock led should be on PC7, the backlight on PB7, see this pic to see which physical pins are those). Maybe check the soldering of the chip visually, with a loupe - sometimes the chip pins are not soldered properly.

[Steezus]

There are just 2 MCU pins that control all the other LEDs, namely one for caps lock, and one for everything else.

Well then it could be firmware problem (have you tried TMK?), i.e. the firmware is not actually turning the LEDs on.

Or it could be a hardware problem (the signal from the MCU does not arrive to the LEDs). This is harder to diagnose, but if you have a multimeter you can check the connections (the caps lock led should be on PC7, the backlight on PB7, see this pic to see which physical pins are those). Maybe check the soldering of the chip visually, with a loupe - sometimes the chip pins are not soldered properly.

I checked the MCU and it seems to look fine, I'm attempting to go thru the firmware now but am struggling a bit since it is my first time. How would I go about attempting to fix the LED issue with the firmware if that is the problem?

[Steezus]

I put some keycaps on my board and plugged it in, it feels great but the LEDs are pissing me off. The numlock's led at the moment is currently activated when nums lock is on and de-activated when num lock is turned off.

[flabbergast]

Which TMK for are you using? I would probably try this one - he's got Red Scarf III directly in the repo; I've used this one with Red Scarf II (but I didn't put the LEDs in, so no confirmation there...).

If you want I can write a small firmware that will do nothing else that blink the LEDs - so that you can test if it's a firmware or hardware problem.

[Steezus]

Which TMK for are you using? I would probably try this one - he's got Red Scarf III directly in the repo; I've used this one with Red Scarf II (but I didn't put the LEDs in, so no confirmation there...).

If you want I can write a small firmware that will do nothing else that blink the LEDs - so that you can test if it's a firmware or hardware problem.

I was using https://github.com/tmk/tmk_keyboard, if you could write a small script to flash the LEDs than that would be perfect. I have absolutely no clue what I'm doing so for the most part I've been researching on what to do rather than messing with tmk. I made my layer on http://www.keyboard-layout-editor.com/ as instructed in the RedScarf III Manual thread but I don't know how to flash it to my keyboard nor do I know how to make my LEDs, MX lock switch for caps lock, or anything really other than making the keys output their appropriate letter or function.

[flabbergast]

I'm attaching a hex file. It should turn on Caps Lock, then Num Lock, then backlight, then turn them off in the same order; with 2 seconds between every change.

Note that it does not have any USB/keyboard function, so with this firmware the keyboard *will not* enumerate as a keyboard. For reverting back to a keyboard firmware, you'll need to enter the bootloader manually (make sure you know how to do that *before* you flash this firmware - normally there's a button on the bottom side of the keyboard; although in your photos it looks like it's missing on your PCB. In that case, you should be able to "emulate" pressing that button by just shorting a pair of the pads where the button is supposed to be by something conductive, like a pin).

Also note that I don't have a schematic of that board, nor do I have that board, so I'm just using the pins that are described as for caps, num, backlight in the firmware supposedly for Red Scarf III that I linked above.

[Steezus]

I'm attaching a hex file. It should turn on Caps Lock, then Num Lock, then backlight, then turn them off in the same order; with 2 seconds between every change.

Note that it does not have any USB/keyboard function, so with this firmware the keyboard *will not* enumerate as a keyboard. For reverting back to a keyboard firmware, you'll need to enter the bootloader manually (make sure you know how to do that *before* you flash this firmware - normally there's a button on the bottom side of the keyboard; although in your photos it looks like it's missing on your PCB. In that case, you should be able to "emulate" pressing that button by just shorting a pair of the pads where the button is supposed to be by something conductive, like a pin).

Also note that I don't have a schematic of that board, nor do I have that board, so I'm just using the pins that are described as for caps, num, backlight in the firmware supposedly for Red Scarf III that I linked above.

Thanks but I will not be able to do for a few days. I was shorted 2 leds and 2 sip sockets so I had to order more before I solder the last two switches in which happen the be the Esc and Tilde keys. In order to enter bootloader manually I need to access the esc key. Sorry I am very unexperienced and I do not know what exactly to do with the hex file, do I flash it on my keyboard and then reflash the layout afterwards?

[flabbergast]

In principle yes, you can flash this "blink" firmware, observe the keyboard (it will *not* be acting as a keyboard, just blinking the leds (hopefully)), and then flash the whole firmware back to turn it back into a keyboard.

BEWARE! If you flash the "blink", you'll not be able to get into the bootloader by holding esc (or however it works now), because that depends on the firmware, and the "blink" firmware does not implement this. That's why I say you should try to get into bootloader using the reset button on the back of the PCB.

I would really recommend trying out the TMK firmware I linked above.

[Steezus]

So it seems that firmware is not the issue, I attempted to flash a new layout, everything correct and I followed the step by step instructions but niw my keyboard does not function at all. The only LED that has ever flashed is the num lock and even the simpliest thing like loading bootloader should flash the caps lock too. I posted in the RedScarf III manual thread and nobody is helping. Kind of sucks that I'm left with a $400 keyboard that doesn't work.

[flabbergast]

Hey! Do not despair yet! It might take a while, but generally things can get resolved. You might need to learn a little about electronics along the way though

First - can you still enter the bootloader?

To test the connections on the PCB - do you have a multimeter?

[Steezus]

Hey! Do not despair yet! It might take a while, but generally things can get resolved. You might need to learn a little about electronics along the way though

First - can you still enter the bootloader?

To test the connections on the PCB - do you have a multimeter?

Thank you very much for the help and support, I truly appreciate it.

That I know I'm pretty sure I can still enter bootloader but I can't be 100% since the LEDs are the indicator. I am also up at college so I do not have a multimeter on me, I just ordered a cheap one on Amazon with prime shipping so it should come Friday.

[Steezus]

I managed to get everything working today, I didn't alter my TKG layers at all but tried to flash the keyboard again and for some reason it surprisingly worked. Now that my keyboard was functioning I then tried to turn on the LEDs that finally work as well, the only problem I'm having now is that I put a MX Lock switch for my stepped caps lock and I need to make so that caps is turned on only when it is pressed in(active) and I for some reason can't get the LED to work on it but it isn't that big of a deal.

[flabbergast]

Great to hear! 

(Sorry I wasn't much of a help.)
I don't know if you can get the MX Lock working with the "official" firmware. (I'm sure you can if you compile TMK yourself.)

[Steezus]

Great to hear! 

(Sorry I wasn't much of a help.)
I don't know if you can get the MX Lock working with the "official" firmware. (I'm sure you can if you compile TMK yourself.)

You helped me more than anybody else and I truly appreciate, a lot of people never even responded to my PMs. I see http://www.keyboard-layout-editor.com/ that you can set each cap to have certain switches so I switched the caps lock to a mx lock, I believe this could fix the issue but TMK is currently down at the moment so I will try whenever I get a chance.

[Ryu]

I'm sorry that I didn't come geekhack so often. And I'm glad to hear your problem is solved.
If you are still finding a solution for your caps lock with MX Lock switch, I think I can help you.
Just to simply change the label of "Caps Lock" to "Locking Caps Lock" like follows should make it work.

["Esc\n\n\n\nfn4","F1\n\n\n\nfn5","F2\n\n\n\nfn6","F3\n\n\n\nfn7","F4\n\n\n\nfn8","F5","F6","F7","F8","F9","F10","F11","F12","PrtSc","Pause\nBreak","Ins","Del","PgUp","PgDn"],
["~\n`\n\n\nFn9","!\n1\n\n\nFn10","@\n2\n\n\nFn11","#\n3\n\n\nFn12","$\n4\n\n\nFn13","%\n5\n\n\nFn14","^\n6\n\n\nFn15","&\n7\n\n\nFn16","*\n8\n\n\nFn17","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace","Num Lock","/","*","-"],
[{w:1.5},"Tab","Q","W","E","R","T","Y\n\n\n\nCalc","U","I\n\n\n\nIns","O","P","{\n[","}\n]",{w:1.5},"|\n\\","7\nHome","8\n↑","9\nPgUp",{h:2},"+"],
[{w:1.75},"Locking Caps Lock","A","S","D","F","G","H","J","K","L",":\n;","\"\n'",{w:2.25},"Enter","4\n←","5","6\n→"],
[{w:2.25},"Shift","Z","X","C\n\n\n\nfn3","V\n\n\n\nfn1","B\n\n\n\nfn2","N\n\n\n\nVolDn","M\n\n\n\nVolUp","<\n,\n\n\nMute",">\n.","?\n/",{w:2.75},"RShift","1\nEnd","2\n↓","3\nPgDn",{h:2},"PEnter"],
[{w:1.25},"Ctrl",{w:1.25},"Win",{w:1.25},"Alt",{w:6.25},"Space",{w:1.25},"RAlt",{w:1.25},"RWin",{w:1.25},"Fn",{w:1.25},"RCtrl",{w:2},"0\nIns",".\nDel"]

[Steezus]

I'm sorry that I didn't come geekhack so often. And I'm glad to hear your problem is solved.
If you are still finding a solution for your caps lock with MX Lock switch, I think I can help you.
Just to simply change the label of "Caps Lock" to "Locking Caps Lock" like follows should make it work.

["Esc\n\n\n\nfn4","F1\n\n\n\nfn5","F2\n\n\n\nfn6","F3\n\n\n\nfn7","F4\n\n\n\nfn8","F5","F6","F7","F8","F9","F10","F11","F12","PrtSc","Pause\nBreak","Ins","Del","PgUp","PgDn"],
["~\n`\n\n\nFn9","!\n1\n\n\nFn10","@\n2\n\n\nFn11","#\n3\n\n\nFn12","$\n4\n\n\nFn13","%\n5\n\n\nFn14","^\n6\n\n\nFn15","&\n7\n\n\nFn16","*\n8\n\n\nFn17","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace","Num Lock","/","*","-"],
[{w:1.5},"Tab","Q","W","E","R","T","Y\n\n\n\nCalc","U","I\n\n\n\nIns","O","P","{\n[","}\n]",{w:1.5},"|\n\\","7\nHome","8\n↑","9\nPgUp",{h:2},"+"],
[{w:1.75},"Locking Caps Lock","A","S","D","F","G","H","J","K","L",":\n;","\"\n'",{w:2.25},"Enter","4\n←","5","6\n→"],
[{w:2.25},"Shift","Z","X","C\n\n\n\nfn3","V\n\n\n\nfn1","B\n\n\n\nfn2","N\n\n\n\nVolDn","M\n\n\n\nVolUp","<\n,\n\n\nMute",">\n.","?\n/",{w:2.75},"RShift","1\nEnd","2\n↓","3\nPgDn",{h:2},"PEnter"],
[{w:1.25},"Ctrl",{w:1.25},"Win",{w:1.25},"Alt",{w:6.25},"Space",{w:1.25},"RAlt",{w:1.25},"RWin",{w:1.25},"Fn",{w:1.25},"RCtrl",{w:2},"0\nIns",".\nDel"]

Thanks, I ended up finding the fix later. Everything has been working smoothly for the past month and there isn't a single complaint to be had.