[GB] Sentraq S60-X RGB Kit (Closing)

[Arhipio]

Sent you an email concerning a replacement.

[milchek]

OK,

Managed to set up some custom keymapping on the function layer so I thought I'd share (since I answered my own questions).

Firstly, this guide is for OSX. So if you're like me and prefer to do things on command line then this is for you.

1. Install 'dfu-programmer' via homebrew

Code: [Select]

brew install dfu-programmer
2. Install homebrew avr so you can compile firmware (https://github.com/osx-cross/homebrew-avr)

Code: [Select]

brew tap osx-cross/avr
brew install avr-libc

3. Grab the (supposed) latest QMK source for the S60RGB here: https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB

4. Go to this folder https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB/keymaps/default, copy the keymap.c file into another folder in the /keymaps dir called 'custom' for example

5. Make your edits. My particular version was minor, I flipped right CTRL and FN buttons. I added up/left/down/right to WASD, and added audio mute, vol - and vol + to FN+1, FN+2, FN+3. You can use this link https://github.com/tmk/tmk_keyboard/blob/master/tmk_core/doc/keycode.txt to find out what all the keycodes are

6. Now compile your firmware with

Code: [Select]

make custom
7. Next, using dfu-programmer erase the current firmware like so:

Code: [Select]

dfu-programmer atmega32u4 erase(Remember to press the reset button on back before doing this)

8. Now flash your custom firmware

Code: [Select]

dfu-programmer atmega32u4 flash S60RGB_custom.hex
Unplug and replug the board and that should be it. Well, it worked for me.

By the way, I'm a total newb at this, not my first board built, but it is my first proper custom firmware/keymap, so if any of the above can be improved please let me know.

One question I have is how to set more FN 'layers' and how to activate them? What would this look like in a keymap file? I'd also love if vendor would confirm that the above firmware source I linked is in fact the one that the .hex file supplied earlier is made from.

[deductivemonkee]

OK,

Managed to set up some custom keymapping on the function layer so I thought I'd share (since I answered my own questions).

Firstly, this guide is for OSX. So if you're like me and prefer to do things on command line then this is for you.

1. Install 'dfu-programmer' via homebrew

Code: [Select]

brew install dfu-programmer
2. Install homebrew avr so you can compile firmware (https://github.com/osx-cross/homebrew-avr)

Code: [Select]

brew tap osx-cross/avr
brew install avr-libc

3. Grab the (supposed) latest QMK source for the S60RGB here: https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB

4. Go to this folder https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB/keymaps/default, copy the keymap.c file into another folder in the /keymaps dir called 'custom' for example

5. Make your edits. My particular version was minor, I flipped right CTRL and FN buttons. I added up/left/down/right to WASD, and added audio mute, vol - and vol + to FN+1, FN+2, FN+3. You can use this link https://github.com/tmk/tmk_keyboard/blob/master/tmk_core/doc/keycode.txt to find out what all the keycodes are

6. Now compile your firmware with

Code: [Select]

make custom
7. Next, using dfu-programmer erase the current firmware like so:

Code: [Select]

dfu-programmer atmega32u4 erase(Remember to press the reset button on back before doing this)

8. Now flash your custom firmware

Code: [Select]

dfu-programmer atmega32u4 flash S60RGB_custom.hex
Unplug and replug the board and that should be it. Well, it worked for me.

By the way, I'm a total newb at this, not my first board built, but it is my first proper custom firmware/keymap, so if any of the above can be improved please let me know.

One question I have is how to set more FN 'layers' and how to activate them? What would this look like in a keymap file? I'd also love if vendor would confirm that the above firmware source I linked is in fact the one that the .hex file supplied earlier is made from.

Copy paste another keymap. Look at where the function key on the base map, make another of those keys with #define. See if anything else has that name. Pretty simple.

[milchek]

Copy paste another keymap. Look at where the function key on the base map, make another of those keys with #define. See if anything else has that name. Pretty simple.

I figured it might be something like this. So what you're saying is to activate the second FN layer you would hold the first FN (FN0) key, then also hold whatever you map as FN1 on function layer 0?

[deductivemonkee]

Copy paste another keymap. Look at where the function key on the base map, make another of those keys with #define. See if anything else has that name. Pretty simple.

I figured it might be something like this. So what you're saying is to activate the second FN layer you would hold the first FN (FN0) key, then also hold whatever you map as FN1 on function layer 0?

You lost me there. Make another function key, it will lead to your second function layer. Your first function key will still go to your first function layer.

[milchek]

You lost me there. Make another function key, it will lead to your second function layer. Your first function key will still go to your first function layer.

Sorry, new to this. What I meant was, right now there are only 2 layers: Base and Function. To access the function layer you hold the menu (FN) key and then you are on function layer. If I create another function layer, from what I'm understanding in your reply, I need to create another FN button on the base layer, my assumption was that you access any new function layers by traversing through them.

For example the layers would look like:

Base Layer
Function Layer 1 (Hold FN on base layer)
Function Layer 2 (Hold FN on base layer, then ALT on Function Layer 1)
Function Layer 3 (Hold FN on base layer, then ALT on Function Layer 1, then CTRL on Function Layer 2)
... this obviously gets a little silly once you're around 4 layers deep.

What you're saying is that you access all function layers through the base layer though right, you just map more FN keys onto the base layer?

[Arhipio]

So how would I go about changing the code in the keymap file for ISO layouts. I wired my escape key to the left iso shift, but it seems like the github branch you gave us is missing the keymap file for ISO and only has the support for ANSI. Do you have the necessary files that you can push to github?

Also sent my email a while ago and still no response.

[deductivemonkee]

So how would I go about changing the code in the keymap file for ISO layouts. I wired my escape key to the left iso shift, but it seems like the github branch you gave us is missing the keymap file for ISO and only has the support for ANSI. Do you have the necessary files that you can push to github?

Also sent my email a while ago and still no response.

The extra key next to shift on iso is set as KC_NO in the keycaps iirc

[Arhipio]

So how would I go about changing the code in the keymap file for ISO layouts. I wired my escape key to the left iso shift, but it seems like the github branch you gave us is missing the keymap file for ISO and only has the support for ANSI. Do you have the necessary files that you can push to github?

Also sent my email a while ago and still no response.

The extra key next to shift on iso is set as KC_NO in the keycaps iirc

Isn't KC_NO pertaining to the HHKB 1u key. Unless I'm mistaken.

[_BL] = KEYMAP(
  KC_ESC,    KC_1,   KC_2,   KC_3,   KC_4,   KC_5,   KC_6,   KC_7,   KC_8,   KC_9,   KC_0,   KC_MINS,  KC_EQL,   KC_NO, KC_BSPC, \
  KC_TAB,  KC_Q,   KC_W,   KC_E,   KC_R,   KC_T,   KC_Y,   KC_U,   KC_I,   KC_O,   KC_P,   KC_LBRC,  KC_RBRC,  KC_BSLS, \
  MO(_AL),   KC_A,   KC_S,   KC_D,   KC_F,   KC_G,   KC_H,   KC_J,   KC_K,   KC_L,   KC_SCLN,KC_QUOT,            KC_ENT,  \
  KC_LSFT         KC_Z,   KC_X,   KC_C,   KC_V,   KC_B,   KC_N,   KC_M,   KC_COMM,KC_DOT, KC_SLSH,            KC_RSFT,  \
  KC_LCTL, TG(_CL) ,KC_LALT,          KC_SPC,                                        KC_RALT,  KC_RGUI, MO(_FL),  KC_RCTL),

[Arhipio]

I'm not sure if I am understanding this correctly, do I have to go into S60RGB.h change the KC_NO (next to kc30) to kc31.

  k00, k01, k02, k03, k04, k05, k06, k07, k08, k09, k0a, k0b, k0c, k0d, k0e, \
   k10, k11, k12, k13, k14, k15, k16, k17, k18, k19, k1a, k1b, k1c, k1d, \
   k20, k21, k22, k23, k24, k25, k26, k27, k28, k29, k2a, k2b,      k2d, \
   k30, k31, k32, k33, k34, k35, k36, k37, k38, k39, k3a, k3b,           k3d, \
   k40, k41, k42,           k46,                     k4a, k4b, k4c, k4d  \
) \
{ \
   {k00, k01,   k02, k03,   k04,   k05,   k06,   k07,   k08,   k09,   k0a, k0b, k0c,   k0d, k0e}, \
   {k10, k11,   k12, k13,   k14,   k15,   k16,   k17,   k18,   k19,   k1a, k1b, k1c,   k1d, KC_NO}, \
   {k20, k21,   k22, k23,   k24,   k25,   k26,   k27,   k28,   k29,   k2a, k2b, KC_NO, k2d, KC_NO}, \
   {k30, k31, k32, k33,   k34,   k35,   k36,   k37,   k38,   k39,   k3a, k3b, KC_NO, k3d, KC_NO}, \
   {k40, k41,   k42, KC_NO, KC_NO, KC_NO, k46,   KC_NO, KC_NO, KC_NO, k4a, k4b, k4c,   k4d, KC_NO}  \

Like this, and then go into keymap and add an extra key into every fourth row for each KEYMAP ?

Edit: If so I did this and I am receiving errors when running the make command (previously to this I already flashed custom working firmware onto my other PCB).

[gerankle]

OK,

Managed to set up some custom keymapping on the function layer so I thought I'd share (since I answered my own questions).

Firstly, this guide is for OSX. So if you're like me and prefer to do things on command line then this is for you.

1. Install 'dfu-programmer' via homebrew

Code: [Select]

brew install dfu-programmer
2. Install homebrew avr so you can compile firmware (https://github.com/osx-cross/homebrew-avr)

Code: [Select]

brew tap osx-cross/avr
brew install avr-libc

3. Grab the (supposed) latest QMK source for the S60RGB here: https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB

4. Go to this folder https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB/keymaps/default, copy the keymap.c file into another folder in the /keymaps dir called 'custom' for example

5. Make your edits. My particular version was minor, I flipped right CTRL and FN buttons. I added up/left/down/right to WASD, and added audio mute, vol - and vol + to FN+1, FN+2, FN+3. You can use this link https://github.com/tmk/tmk_keyboard/blob/master/tmk_core/doc/keycode.txt to find out what all the keycodes are

6. Now compile your firmware with

Code: [Select]

make custom
7. Next, using dfu-programmer erase the current firmware like so:

Code: [Select]

dfu-programmer atmega32u4 erase(Remember to press the reset button on back before doing this)

8. Now flash your custom firmware

Code: [Select]

dfu-programmer atmega32u4 flash S60RGB_custom.hex
Unplug and replug the board and that should be it. Well, it worked for me.

By the way, I'm a total newb at this, not my first board built, but it is my first proper custom firmware/keymap, so if any of the above can be improved please let me know.

One question I have is how to set more FN 'layers' and how to activate them? What would this look like in a keymap file? I'd also love if vendor would confirm that the above firmware source I linked is in fact the one that the .hex file supplied earlier is made from.

Did all this. Upon using "make custom" in cmd, and in the correct directory of the Makefile, prompt shows "Making S60RGB with keymap custom" and doesn't do anything. No hex file made, nothing.

What am I doing wrong?

[deductivemonkee]

OK,

Managed to set up some custom keymapping on the function layer so I thought I'd share (since I answered my own questions).

Firstly, this guide is for OSX. So if you're like me and prefer to do things on command line then this is for you.

1. Install 'dfu-programmer' via homebrew

Code: [Select]

brew install dfu-programmer
2. Install homebrew avr so you can compile firmware (https://github.com/osx-cross/homebrew-avr)

Code: [Select]

brew tap osx-cross/avr
brew install avr-libc

3. Grab the (supposed) latest QMK source for the S60RGB here: https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB

4. Go to this folder https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB/keymaps/default, copy the keymap.c file into another folder in the /keymaps dir called 'custom' for example

5. Make your edits. My particular version was minor, I flipped right CTRL and FN buttons. I added up/left/down/right to WASD, and added audio mute, vol - and vol + to FN+1, FN+2, FN+3. You can use this link https://github.com/tmk/tmk_keyboard/blob/master/tmk_core/doc/keycode.txt to find out what all the keycodes are

6. Now compile your firmware with

Code: [Select]

make custom
7. Next, using dfu-programmer erase the current firmware like so:

Code: [Select]

dfu-programmer atmega32u4 erase(Remember to press the reset button on back before doing this)

8. Now flash your custom firmware

Code: [Select]

dfu-programmer atmega32u4 flash S60RGB_custom.hex
Unplug and replug the board and that should be it. Well, it worked for me.

By the way, I'm a total newb at this, not my first board built, but it is my first proper custom firmware/keymap, so if any of the above can be improved please let me know.

One question I have is how to set more FN 'layers' and how to activate them? What would this look like in a keymap file? I'd also love if vendor would confirm that the above firmware source I linked is in fact the one that the .hex file supplied earlier is made from.

Did all this. Upon using "make custom" in cmd, and in the correct directory of the Makefile, prompt shows "Making S60RGB with keymap custom" and doesn't do anything. No hex file made, nothing.

What am I doing wrong?

You need to have patience. It takes ~5 mins to compile give or take. It will pop up with other messages shortly after the first one.

[gerankle]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

[deductivemonkee]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Send me your keymap, I can try to compile it. It shouldn't take an hour.

[Arhipio]

I got everything to work, decided to wire the escape key to the unused, HHKB key. Made programming much easier. Just waiting on doodersbrother to respond to my email now. Cheers guys, thanks for all the help.

[kt350]

Hi guys,

I am having an issue with my board and was wondering if any of you guys could help me out.
The problem is similar to scizzorz problem in reply #202 in this thread.

My keyboard will work perfectly for some time, however it always ends up spamming a single column of keys and eventually gets stuck on one of those keys. In my case it always spams the far right column (Backspace, \ , Enter , RShift , and RCtrl).
I have tried a couple different firmwares (the one provided by doodersbrother's and also deductivemonkee's) to see if it was a firmware issue but the issue persisted with different firmwares. I created my own firmware changing the far right column to numbers and again, it would just spam the numbers I assigned to the far right column. At this point it doesn't seem to be a firmware issue.
I tested the keyboard on two different laptops and it caused the same issue on both laptops. I also tried different keyboards and the keyboards built into the laptops and could not reproduce this error. This leaves me thinking that it is an issue with this specific keyboard itself and not Windows or my laptops.
I then looked at the pcb and the soldering looks fine to me. It doesn't look like there is a short anywhere on the board.

So at this point, I am unsure of what exactly the problem is. I am leaning towards it being an issue with the pcb but am unsure of how to confirm that (do not have a multimeter on hand). I have sent an email to info@sentraq.com and am waiting for their response. If you guys had any input on what I should do next, it would be greatly appreciated.

Thanks!

[milchek]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Did you make sure to put the keymap.c into a 'custom' subfolder (next to 'default' subfolder) in the S60RGB sub dir?

[colonel disappointment]

For arrow keys on all of my keyboards I use left-win and wasd. It is so natural that when I use a keyboard that doesn't have it I end up sending a few windows commands until I realize it. If you make a keyboard-layout-editor of exactly what you want I could make it for you.

//edit//

This is my de-facto keymap, and hex file if anyone wants it.

if you could do that it would be awesome. basically. just using menu as function to add delete to backspace and arrow directions to wasd. everything else stay the same. (Attachment Link)

Do you want escape on the FN layer, main layer, or at all? I will do this tomorrow, so lmk by then.

FN layer would be great. sorry i forgot to add that one.

Do you want a FN toggle or a momentary (hold to use layer) FN? I will do this when I get home.

hey man sorry it took so long i just now got this flashed onto my board.

its perfect thank you so much this is exactly what i wanted.

[deductivemonkee]

For arrow keys on all of my keyboards I use left-win and wasd. It is so natural that when I use a keyboard that doesn't have it I end up sending a few windows commands until I realize it. If you make a keyboard-layout-editor of exactly what you want I could make it for you.

//edit//

This is my de-facto keymap, and hex file if anyone wants it.

if you could do that it would be awesome. basically. just using menu as function to add delete to backspace and arrow directions to wasd. everything else stay the same. (Attachment Link)

Do you want escape on the FN layer, main layer, or at all? I will do this tomorrow, so lmk by then.

FN layer would be great. sorry i forgot to add that one.

Do you want a FN toggle or a momentary (hold to use layer) FN? I will do this when I get home.

hey man sorry it took so long i just now got this flashed onto my board.

its perfect thank you so much this is exactly what i wanted.

No problem, happy to help.

[gerankle]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Did you make sure to put the keymap.c into a 'custom' subfolder (next to 'default' subfolder) in the S60RGB sub dir?

Yes. See attached picture.

[deductivemonkee]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Did you make sure to put the keymap.c into a 'custom' subfolder (next to 'default' subfolder) in the S60RGB sub dir?

Yes. See attached picture.

(Attachment Link)

Thanks for the picture. You can't compile with Windows CMD, download mhv avr tools and use that to compile.

[tmurch]

So got my board in earlier this week, got it together and have really enjoyed it: http://imgur.com/a/mE6U3

This is my first build so I was worried it wouldn't go well, but so far so good....until today.  I have had it plugged in and when i went to type on it, the LEDs were on, but it wasn't working so I just unplugged it and then plugged it back in.  Well when I did the LEDs werent coming on and the keyboard wasnt registering at all.  I have tried everything I can think of, different usb cable, port, computer. and nothing is working.  Any ideas?

[gerankle]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Did you make sure to put the keymap.c into a 'custom' subfolder (next to 'default' subfolder) in the S60RGB sub dir?

Yes. See attached picture.

(Attachment Link)

Thanks for the picture. You can't compile with Windows CMD, download mhv avr tools and use that to compile.

Got it! Flashed and it's all working. Appreciate all the help. Was confused on CMD compiling because I think I did it for the Minorca 40%.

[deductivemonkee]

Thanks for all the help on this thread deductivemonkee. Any reason why it may be doing it for longer? It's been over an hour >.<.

May I ask somebody to try to compile my keymap and see if it does it for them?

For my function layer, besides backlight and underglow controls, I have Esc as ~, 1 through 0 being F1-F10, - and = as Volume Down and Up, respectively, Backspace as Delete, Right Shift as Volume Mute, and WASD as arrows. I'll also attach it to post.

I just can't get it to compile =\.

Did you make sure to put the keymap.c into a 'custom' subfolder (next to 'default' subfolder) in the S60RGB sub dir?

Yes. See attached picture.

(Attachment Link)

Thanks for the picture. You can't compile with Windows CMD, download mhv avr tools and use that to compile.

Got it! Flashed and it's all working. Appreciate all the help. Was confused on CMD compiling because I think I did it for the Minorca 40%.

Cool, glad I could help.

[Ozbourn]

I'm having trouble getting the board flashed. I'm using QMK Firmware Flasher on mac, when it asks me to click on reset I can't get it to work. The button doesn't seem to register.

I tried using AMTEL FLIP on my PC, and after rebooting the software wouldn't run, and I cannot uninstall... feeling helplessly stupid.

Edit -

I'd still be interested if anyone knows why FLIP would flip out on my computer, but using the QMK windows package I was able to get it to work!

[deductivemonkee]

I'm having trouble getting the board flashed. I'm using QMK Firmware Flasher on mac, when it asks me to click on reset I can't get it to work. The button doesn't seem to register.

I tried using AMTEL FLIP on my PC, and after rebooting the software wouldn't run, and I cannot uninstall... feeling helplessly stupid.

Check the button doesn't have a broken solder joint?

[Ozbourn]

I'm having trouble getting the board flashed. I'm using QMK Firmware Flasher on mac, when it asks me to click on reset I can't get it to work. The button doesn't seem to register.

I tried using AMTEL FLIP on my PC, and after rebooting the software wouldn't run, and I cannot uninstall... feeling helplessly stupid.

Check the button doesn't have a broken solder joint?

Nope, it was user error. I fixed it with the QMK for windows. Still wondering about FLIP on my Windows 10PC, but whatever...

The wife helped me out and we had a blast putting this thing together, together. Can't wait to do another!

http://imgur.com/a/sG4j7

[deductivemonkee]

I'm having trouble getting the board flashed. I'm using QMK Firmware Flasher on mac, when it asks me to click on reset I can't get it to work. The button doesn't seem to register.

I tried using AMTEL FLIP on my PC, and after rebooting the software wouldn't run, and I cannot uninstall... feeling helplessly stupid.

Check the button doesn't have a broken solder joint?

Nope, it was user error. I fixed it with the QMK for windows. Still wondering about FLIP on my Windows 10PC, but whatever...

The wife helped me out and we had a blast putting this thing together, together. Can't wait to do another!

Show Image

Odd, flip works on my win10 rig.

Also, nice build. Looks like I'm not the only one with an oddly twisted right alt key.

[Ozbourn]

Yeah, I even desoldered it and tried to fix the twist, but there is still a bit there. The top plate just doesn't hold on to the switch properly.

[milchek]

Thought I'd share my S60-X RGB:



More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

[pixelpusher]

Thought I'd share my S60-X RGB:

Show Image

More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

Looks nice!  I quite like the silver screws.  Also, please be careful desoldering those LEDs!!! She's a beauty... You don't want to batter and bruise her with jumper wires all over the back (from having to reroute lifted pads)! 

[deductivemonkee]

Thought I'd share my S60-X RGB:

Show Image

More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

Looks nice!  I quite like the silver screws.  Also, please be careful desoldering those LEDs!!! She's a beauty... You don't want to batter and bruise her with jumper wires all over the back (from having to reroute lifted pads)!

Is this a shot at my jumper for a lifted pad?

[Vadurr]

Thought I'd share my S60-X RGB:

Show Image

More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

Well done! :thumb:

[pixelpusher]

Thought I'd share my S60-X RGB:

Show Image

More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

Looks nice!  I quite like the silver screws.  Also, please be careful desoldering those LEDs!!! She's a beauty... You don't want to batter and bruise her with jumper wires all over the back (from having to reroute lifted pads)!

Is this a shot at my jumper for a lifted pad?

Oh no.   Just speaking from experience.  I've had plenty a need for jumpers because of the fragile led pads in the past year.  I learned my lesson... sips all the way for now on

[deductivemonkee]

Thought I'd share my S60-X RGB:

Show Image

More photos of the build log here: http://imgur.com/a/OMOAz

Future plans:
- Desolder all the white LEDs (what was i thinking), orange ones are on the way, replace all of them
- Get some black M3 screws for the top plate to suit the black keycaps

Looks nice!  I quite like the silver screws.  Also, please be careful desoldering those LEDs!!! She's a beauty... You don't want to batter and bruise her with jumper wires all over the back (from having to reroute lifted pads)!

Is this a shot at my jumper for a lifted pad?

Oh no.   Just speaking from experience.  I've had plenty a need for jumpers because of the fragile led pads in the past year.  I learned my lesson... sips all the way for now on

I feel you. Sips make everything better.

[jisaak]

I have an issue with the qmk firmware, maybe someone can help me. I forked the version from  jbyoung and added a secondary layer:

Code: [Select]

[_FLTWO] = KEYMAP(
  KC_GRV, KC_F1,  KC_F2,  KC_F3,  KC_F4,  KC_F5,  KC_F6,  KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, KC_F12, RESET, KC_DELETE,  \
  KC_TRNS,KC_TRNS,KC_LCTL, KC_LSFT,KC_TRNS,KC_TRNS, KC_TRNS,KC_TRNS,KC_UP, KC_TRNS,  KC_PSCREEN,   KC_TRNS,   KC_TRNS,   KC_TRNS, \
  KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_HOME,KC_LEFT,KC_DOWN, KC_RIGHT, KC_END,    KC_TRNS,  KC_TRNS,     KC_TRNS, \
  KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_AUDIO_MUTE,KC_AUDIO_VOL_DOWN, KC_AUDIO_VOL_UP, KC_TRNS, KC_TRNS,  \
  KC_TRNS,KC_TRNS,KC_TRNS,          KC_MENU,                               KC_TRNS, KC_TRNS, KC_TRNS, KC_TRNS),
};
This enables me to use the arrow keys on CAPS + jikl which works as expected. I realized that I have trouble to reach Shift and Ctrl while holding the CAPSLOCK key so I mapped Shift to CAPS + W and CTRL to CAPS + E. Everything is working as expected except that when I use CAPS + W (Shift) and hit any key from the Layer above (that is not mapped in this Layer) say R, then the keyboard is writing everything in upper case, even when I release the Caps (function) key.
The keymap can be found here:
https://github.com/mjisaak/qmk_firmware/blob/master/keyboards/S60RGB/keymaps/default/keymap.c

Can anyone help me?

[deductivemonkee]

I have an issue with the qmk firmware, maybe someone can help me. I forked the version from  jbyoung and added a secondary layer:

Code: [Select]

[_FLTWO] = KEYMAP(
  KC_GRV, KC_F1,  KC_F2,  KC_F3,  KC_F4,  KC_F5,  KC_F6,  KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, KC_F12, RESET, KC_DELETE,  \
  KC_TRNS,KC_TRNS,KC_LCTL, KC_LSFT,KC_TRNS,KC_TRNS, KC_TRNS,KC_TRNS,KC_UP, KC_TRNS,  KC_PSCREEN,   KC_TRNS,   KC_TRNS,   KC_TRNS, \
  KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_HOME,KC_LEFT,KC_DOWN, KC_RIGHT, KC_END,    KC_TRNS,  KC_TRNS,     KC_TRNS, \
  KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_TRNS,KC_AUDIO_MUTE,KC_AUDIO_VOL_DOWN, KC_AUDIO_VOL_UP, KC_TRNS, KC_TRNS,  \
  KC_TRNS,KC_TRNS,KC_TRNS,          KC_MENU,                               KC_TRNS, KC_TRNS, KC_TRNS, KC_TRNS),
};
This enables me to use the arrow keys on CAPS + jikl which works as expected. I realized that I have trouble to reach Shift and Ctrl while holding the CAPSLOCK key so I mapped Shift to CAPS + W and CTRL to CAPS + E. Everything is working as expected except that when I use CAPS + W (Shift) and hit any key from the Layer above (that is not mapped in this Layer) say R, then the keyboard is writing everything in upper case, even when I release the Caps (function) key.
The keymap can be found here:
https://github.com/mjisaak/qmk_firmware/blob/master/keyboards/S60RGB/keymaps/default/keymap.c

Can anyone help me?

It is getting stuck on shift on the other layer.

[jisaak]

You are right, and I just figured out, that I can fix that using

Code: [Select]

#define PREVENT_STUCK_MODIFIERS in config.h :-D

Now I only have an issue with the leds left (If I use RGB_TOG to turn the leds off,  the left two leds on the bottom and top are chaning to white and keep lighting)

[johntron25]

Finished building my tonight http://imgur.com/a/hKDMJ.
I have a QMK question, for the fn key, is it possible just press it to activate instead of holding?

[The Tetanus Clam]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

[deductivemonkee]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

[pixelpusher]

Got mine finished.  Looks great.  I'm glad I found this thread because I thought mine was messed up since the backspace wasn't working.  Flashed the new firmware and it fixed it.  Even figured out how to compile a customized key map 

I'll explain it all and post pics for others after a while

[The Tetanus Clam]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

[deductivemonkee]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

[The Tetanus Clam]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

Don't even have the case on yet and I was holding it when I was checking it so nothing should be shorting it.

[deductivemonkee]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

Don't even have the case on yet and I was holding it when I was checking it so nothing should be shorting it.

Can you take some pictures of the soldering and PCB?

[The Tetanus Clam]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

Don't even have the case on yet and I was holding it when I was checking it so nothing should be shorting it.

Can you take some pictures of the soldering and PCB?

http://imgur.com/a/HV451
the burn mark like things is just burnt solder and flux that I checked. It peels off so its not the board. I also redid some of the solder in these pictures so they are slightly old.

[deductivemonkee]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

Don't even have the case on yet and I was holding it when I was checking it so nothing should be shorting it.

Can you take some pictures of the soldering and PCB?

http://imgur.com/a/HV451
the burn mark like things is just burnt solder and flux that I checked. It peels off so its not the board. I also redid some of the solder in these pictures so they are slightly old.

I notice in the last picture that two diodes are missing the black cover and look as though they could be damaged. I had this issue on my D key that prevented it from sending whatsoever. Could you check those diodes and if they are ruined replace them? Through-hole diodes can be used interchangeably with SMD, just hard to solder.

Edit, disregard this. It looks as though the flash made it look this way. What are all the keys that are not firing correctly?

[pixelpusher]

So, here's an album of my build in a Tex case:
http://imgur.com/gallery/0AR3D

I did make 1 little mistake that I may fix down the road... I put the capslock switch in the wrong spot   I don't usually use stepped caps, BUT I DO NOW.     I'm currently using capslock as the function key, so it's not ideal, but oh well.  If I get bored some day I'll desolder it and scootch it over to the next hole.

For getting the firmware working and cutomized I used:

• This thread (good info on the 5th and 6th pages) for the specifics of the firmware and
• Another post https://geekhack.org/index.php?topic=82935.0 for info on how to get a compiling environment up and running in Windows.

I used the QMK git deposit for the S60RGB that doodersbrother linked (https://github.com/jbyoung/qmk_firmware/tree/master/keyboards/S60RGB) and added in the #define RGBLIGHT_ANIMATIONS line in the config.h file, as deductivemonkee so cleverly suggested.

Great community support here! 

[doodersbrother]

Hey everyone,
This is my first build and am having some pretty annoying issues with my keys.
1.       It seems that many of my keys aren't working, including but not limited to "3" "e" "d" "x" and "backspace." This is AFTER flashing and re-flashing the firmware with the latest firmware we were linked to. Also, whenever I try and short the connection with a pair of tweezers, it doesn't work. In addition, there are NO burn marks on the PCB (other than small amounts of burned solder that I have checked and flakes right off). I did spring swap my switches, however I don't think that could have caused any issues considering I did it very carefully and made sure every switch was put back together correctly. Lastly, I redid all of the soldering on the broken keys without any luck.

2.       Whenever my keyboard is plugged in, it spams the x key endlessly until I press another key. After talking a look at the PCB I can't find any damage or anything out of place.

I appreciate any help. Just to reiterate, I had all of these issues before AND after flashing and re-flashing the firmware.

Did you test each key by shorting it BEFORE soldering anything?

No that probably would have been a good idea. This is my first build so I didn't think of that. I can't really think of a reason why so many keys wouldn't be working other than a defective PCB right? I know for a fact that I couldn't have burnt the pads because I made an extremely conscious effort to not even so much as touch the PCB with my soldering iron.

Make sure that nothing is shorting on the bottom of the case?

Don't even have the case on yet and I was holding it when I was checking it so nothing should be shorting it.

Can you take some pictures of the soldering and PCB?

http://imgur.com/a/HV451
the burn mark like things is just burnt solder and flux that I checked. It peels off so its not the board. I also redid some of the solder in these pictures so they are slightly old.

I would wipe the board with some alcohol. Some solder joints have a lot of solder on them, especially the right shift. check to make sure it isn't shorting out another switch's pad.