fn数据
"0":["ACTION_LAYER_MOMENTARY","1"],"1":["ACTION_BACKLIGHT_DECREASE"],"2":["ACTION_BACKLIGHT_TOGGLE"],"3":["ACTION_BACKLIGHT_INCREASE"],"4":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_E"],"5":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_D"],"6":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_R"],"7":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_F"],"8":["ACTION_LAYER_TOGGLE","2"]
Wow nice, I actually speak Chinese new and have a hopefully working redscarf, so I'll take a look when I get home.
Quotefn数据
"0":["ACTION_LAYER_MOMENTARY","1"],"1":["ACTION_BACKLIGHT_DECREASE"],"2":["ACTION_BACKLIGHT_TOGGLE"],"3":["ACTION_BACKLIGHT_INCREASE"],"4":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_E"],"5":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_D"],"6":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_R"],"7":["ACTION_MODS_KEY","LR_LEFT",["MOD_GUI"],"KC_F"],"8":["ACTION_LAYER_TOGGLE","2"]
This correspond to the action of the label for Fn0 to Fn8 , it seems that Fn8+ are mappable to additional layer.
Fn0: Activate Layer1
Fn1 : backlight decrease
Fn2 : backlight on/off
Fn3 : backlight increase
No idea what the rest is.
Sorry to keep you waiting.No problem man, thanks a lot for this , I'm building mine tomorrow I'll look at it and see if anything is "poorly" translated.
Here is a simple manual for how to reflash RedScarfIII.
And sorry for my poor English.
Hi ryu, any idea how non English characters like ö ä å can be programmed in TKG? How do I use the labels like lang1 or thereint1? Thanks.
Hi azhdar, I tried your link of KLE as it is and got a seemingly working keymap as the attachment.http://www.keyboard-layout-editor.com/#/layouts/35cfe9dd0da60b6b802c49b73efea04a
The keymap you attached seems to have a empty layout. Did you get any error messages (something in red) when you make it?
Oh, I see what's the problem.Damn how did I missed that :confused:
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Then it seems that the firmware is live.keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Offline, I guess it was, It cleared from the printing list.Then it seems that the firmware is live.keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Are you using online reflash or offline reflash? Was the eep file reflashed successfully?
As I wrote in the manual, the task will be cleared from the printing list when successfully completed.
That's so weird.Offline, I guess it was, It cleared from the printing list.Then it seems that the firmware is live.keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Are you using online reflash or offline reflash? Was the eep file reflashed successfully?
As I wrote in the manual, the task will be cleared from the printing list when successfully completed.
Where do I find hid_listen? I'll try that.MoreThat's so weird.Offline, I guess it was, It cleared from the printing list.Then it seems that the firmware is live.keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Are you using online reflash or offline reflash? Was the eep file reflashed successfully?
As I wrote in the manual, the task will be cleared from the printing list when successfully completed.
Are the keys available before reflashing?
Maybe we should launch hid_listen and play with some magic commands (https://github.com/tmk/tmk_keyboard#magic-commands).
Press LShift+RShift+D, LShift+RShift+X, LShift+RShift+K, and then you can get some debug messages when typing keys.
You can find hid_listen on PJRC's website. https://www.pjrc.com/teensy/hid_listen.htmlWhere do I find hid_listen? I'll try that.MoreThat's so weird.Offline, I guess it was, It cleared from the printing list.Then it seems that the firmware is live.keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.I tried the keymap you attached on my bare PCB and I see it works.Oh, I see what's the problem.so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I confirmed your first link with simple mode but not your second and third link.
It seems that the top row (Esc, F1, F2, etc.) is missing in your third link (the layout for fn layer), so the rest keys are all mismatched.
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
It's not necessary to reload Hex file unless you have overwritten the firmware by mistake.
Could you describe your problem in more detail?
For example keyboard cannot be recognized by PC, or can be recognized but nothing happens when typing keys, or key works but keymap is not updated?
Are you using online reflash or offline reflash? Was the eep file reflashed successfully?
As I wrote in the manual, the task will be cleared from the printing list when successfully completed.
Are the keys available before reflashing?
Maybe we should launch hid_listen and play with some magic commands (https://github.com/tmk/tmk_keyboard#magic-commands).
Press LShift+RShift+D, LShift+RShift+X, LShift+RShift+K, and then you can get some debug messages when typing keys.
Yeah I had keymaps before the first reflash. Also before reflash It RGB flashed whenever I plugged it in.
And now no more keymaps, and only light if I play with the remote.
Could you please tell me which controller is used on the redscarfIII pcb? Thank you!Hi xauser, off course.
Hey ryu, using this layout, the 2 keys in red ouput the same thing, which is incorrect. I tried different lang keys or international keys but it doesnt work.
http://www.keyboard-layout-editor.com/#/layouts/da3a2dd7ae786c935e570bfcab5e5179
Side question: one the mapping manual, som output are grey, doest that mean something?
Thanks for the explanation about grey label, that explains why I couldn't get the Keypad enter to be different from the regular enter.Hey ryu, using this layout, the 2 keys in red ouput the same thing, which is incorrect. I tried different lang keys or international keys but it doesnt work.
http://www.keyboard-layout-editor.com/#/layouts/da3a2dd7ae786c935e570bfcab5e5179
Side question: one the mapping manual, som output are grey, doest that mean something?
Good question. I think you may be the first man who try to make an ISO layout with TKG.
As I said earlier, TKG guesses what the key is by recognizing the combinations of the labels.
Inevitably, some keys have the same labels while they are actually different keys. For example left shift and right shift, they have the same label "Shift".
To decide which shift the "Shift" should be, I gave a high priority to left shift, and added explicit labels to both left and right shift.
So when you say "Shift", TKG supposes it's left shift, and only when you specify "RShift", TKG supposes it's right shift.
Every time TKG resolves this type of conflicts, it adds the result to the "Solved conflict" section of the "INFO" of layer. (mouse over the keys to see result)
But for "\ and |" and "Non-US \ and |", I have no idea about what should the explicit label be.
So I just gave the US "\ and |" a high priority, and this cause the "Non-US \ and |" actually can not be assigned by user at present.
To solve this, could you please give me some advises about the explicit label of "Non-US \ and |".
And for your side question, yes, you have noted the gray labels.
They mean the keys have low priorities on the gray labels. In other word, some other keys have high priorities on the same labels and the low-priority keys can not be assigned by the labels.
BTW, you can see a "low priority" tooltip when popmouse over the gray labels.
Thanks for the explanation about grey label, that explains why I couldn't get the Keypad enter to be different from the regular enter.Hey ryu, using this layout, the 2 keys in red ouput the same thing, which is incorrect. I tried different lang keys or international keys but it doesnt work.
http://www.keyboard-layout-editor.com/#/layouts/da3a2dd7ae786c935e570bfcab5e5179
Side question: one the mapping manual, som output are grey, doest that mean something?
Good question. I think you may be the first man who try to make an ISO layout with TKG.
As I said earlier, TKG guesses what the key is by recognizing the combinations of the labels.
Inevitably, some keys have the same labels while they are actually different keys. For example left shift and right shift, they have the same label "Shift".
To decide which shift the "Shift" should be, I gave a high priority to left shift, and added explicit labels to both left and right shift.
So when you say "Shift", TKG supposes it's left shift, and only when you specify "RShift", TKG supposes it's right shift.
Every time TKG resolves this type of conflicts, it adds the result to the "Solved conflict" section of the "INFO" of layer. (mouse over the keys to see result)
But for "\ and |" and "Non-US \ and |", I have no idea about what should the explicit label be.
So I just gave the US "\ and |" a high priority, and this cause the "Non-US \ and |" actually can not be assigned by user at present.
To solve this, could you please give me some advises about the explicit label of "Non-US \ and |".
And for your side question, yes, you have noted the gray labels.
They mean the keys have low priorities on the gray labels. In other word, some other keys have high priorities on the same labels and the low-priority keys can not be assigned by the labels.
BTW, you can see a "low priority" tooltip when popmouse over the gray labels.
In ISO Qwerty (for UK users), "non-US \ and |" is "\ and |" and "non-US ~ and #" is "~and #", the problem is that 2 differents label on TMK output the exact same things which is this key:Show Image(http://i.imgur.com/Ip1vM0m.png)
The 2 labels are the one colored in this link : http://www.keyboard-layout-editor.com/#/layouts/b8de2e29803176a6c89a0929ee244aee
Green is correct key for the output above, but red one is the same that red and shouldn't be.
+----------------+-----------+----------------+
| Keys | US Layout | ISO Layout |
+----------------+----------------------------+
| \ and | | \ and | | Non-US # and ~ |
+----------------+----------------------------|
| Non-US \ and | | N/A | Non-US \ and | |
+----------------+----------------------------+
| Non-US # and ~ | \ and | | Non-US # and ~ |
+----------------+-----------+----------------+
I tried this on Windows, so we can see Windows treat \ and | and Non-US # and ~ as same function and \ and | and Non-US \ and | as different functions.Can you simply name it ISO?Thank you, fixed!
thanks, unknow label for the moment let me know when updated :)Can you simply name it ISO?Thank you, fixed!
Now you can use "iso |\n\\" to assign a key to "Non-US \ and |".
It should have been updated when my previous post.thanks, unknow label for the moment let me know when updated :)Can you simply name it ISO?Thank you, fixed!
Now you can use "iso |\n\\" to assign a key to "Non-US \ and |".
Still unknow label:I tried your layout and it just works well.Show Image(http://i.imgur.com/2PKpYLs.png)
layout:
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf
Still unknow label:I tried your layout and it just works well.Show Image(http://i.imgur.com/2PKpYLs.png)
layout:
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf
I think your browser is using the locally cached file. Please press Ctrl+R until you see the following in the help page.
(Attachment Link)
I already can mapkey success for my RS3 with this layout: http://www.keyboard-layout-editor.com/#/layouts/d804d0f625657bc6bee7a6cb5efbb976
However, there is a problem. Everytime I hit Fn0, seem like my RS3 went to a loop which disable all the key.
This is what I have done:
1. Creat layout by using http://www.keyboard-layout-editor.com/
2. Copy all the raw data to http://www.enjoyclick.org/tkg/# with layout mode: Simple
3. Import Fn from the RS3 guide:
"0":["ACTION_LAYER_MOMENTARY",1],"1":["ACTION_BACKLIGHT_TOGGLE"],"2":["ACTION_BACKLIGHT_DECREASE"],"3":["ACTION_BACKLIGHT_INCREASE"],"4":["ACTION_FUNCTION","2",0],"5":["ACTION_FUNCTION","7",0],"6":["ACTION_FUNCTION","7","1"],"7":["ACTION_FUNCTION","4",0],"8":["ACTION_FUNCTION","3",0],"9":["ACTION_FUNCTION","6","2"],"10":["ACTION_FUNCTION","5","1"],"11":["ACTION_FUNCTION","5","4"],"12":["ACTION_FUNCTION","5","13"],"13":["ACTION_FUNCTION","5","5"],"14":["ACTION_FUNCTION","5","11"],"15":["ACTION_FUNCTION","5","6"],"16":["ACTION_FUNCTION","5","15"],"17":["ACTION_FUNCTION","5",0]
4. Download eep file then flash to the keyboard.
After that, everything worked but after I press Fn0, my RS3 seem get in a loop without get out, so all the key no function anymore. Can you please let me know if I did something wrong with Fn key ?
I fixed the problem. All the keys worked after I press Fn0 by using this layout: http://www.keyboard-layout-editor.com/#/layouts/0409c3a4710f80955aca9b188071de4dI haven't tested the Backlight Features a lot but if I remember correctly it's on Fn2 and Fn3, but when I tested it, It also changed the backlight mode, breathing, full backlight ... So I'm unsure about it.
This is what I have done:
1. Creat layout by using http://www.keyboard-layout-editor.com/
2. Copy all the raw data to http://www.enjoyclick.org/tkg/# with layout mode: All-in-one
3. I don't import Fn from RS3 guide.
4. Download eep file then flash to the keyboard.
But now I have another problem: how to add turn on/increase/decrease the backlight. I don't really understand how the mapkey to control backlight.
Fixed backlight control by change Fn on TMK to :You should refer to this picture: (http://i.imgur.com/3EHUumg.png)
Fn0 - Layout action>Momentary - layer 1
Fn1 - Backlight action> Toggle
Fn2 - Backlight action> Decrease
Fn3 - Backlight action> Increase.
As I remember, the original layout of RS3 can control the backlit without remote by using:
Fn + ESC - backlit on/off
Fn + F1 - backlit red
Fn + F2 - backlit green
...........v............v............
Now how can I control the backlit light without the remote ? With new layout ? Can someone please guide me.
Fixed. I already can control the backlit.
I think the most important thing you need to do is choose a Red Scraft 3 keyboard on http://www.enjoyclick.org/tkg/# before you do anything.
After sleeping on it I figured out that I just didn't have the function keys set up correctly. After importing the ones found in that user manual, I can use the keyboard to adjust the smd leds and the button leds. So the only thing not working now is the remote control. I checked that the battery has juice left with a multimeter. Is there anything else we need to do to get that working?
Really cool keyboard though.
After sleeping on it I figured out that I just didn't have the function keys set up correctly. After importing the ones found in that user manual, I can use the keyboard to adjust the smd leds and the button leds. So the only thing not working now is the remote control. I checked that the battery has juice left with a multimeter. Is there anything else we need to do to get that working?
Really cool keyboard though.
I think I might have to move my question over to the TMK thread...
So the firmware that is linked does not work for me as is (https://github.com/kairyu/tmk_keyboard_custom/tree/master/keyboard/RedScarfIII). It builds just fine, but flashing it results in an "unknown" device. Commenting out KEYMAP_IN_EEPROM_ENABLE in the Makefile results in a hex that allows the keyboard to be identified as a HID keyboard, and even as "RedScarf", but nothing works at all. I'm assuming there's no "keyboard" in there since the keymap wasn't loaded?
Anyway, try not to flash the hex files and stick to just the EEPROM for keymaps for now...
Ryu, You're the best, and thanks for fixing the Hex flashing on the TKG.
You're right that the hex file does appear to big. I figure something must be going wrong for me, but I can't figure out what. I was using WinAVR, so I went over and installed the avr8-gnu-toolchain directly from atmel on my linux computer, cloned the repo, make all and the hex file I get has the last address of 0x75d8. I do get an error in backlight.c -- FADING_LED_SET_DIRECTION isn't passed both the parameters, so I assume you actually want FADING_LED_SET_DIRECTION_ALL. Making that change allows the build to work.
I'm still not sure why it the file is so large for me, but it was clearly the issue. I uncommented NO_ACTION_TAPPING and NO_ACTION_ONESHOT since I wasn't planning on using them, and that gave me a working hex file! The macros I programmed are even working... kind of.
So now... the next issue. Since the keymaps are loaded into eeprom, there should be something in the .eep file, right? I get only an empty file. I think this is messing up my function layers and macros, since it is still reading the memory from the last time I uploaded. So... should the .eep file have output, and any ideas as to why it isn't?
Fn0: Activate Layer1
Fn1 : backlight decrease
Fn2 : backlight on/off
Fn3 : backlight increase
Fixed backlight control by change Fn on TMK to :
Fn0 - Layout action>Momentary - layer 1
Fn1 - Backlight action> Toggle
Fn2 - Backlight action> Decrease
Fn3 - Backlight action> Increase.
As I remember, the original layout of RS3 can control the backlit without remote by using:
Fn + ESC - backlit on/off
Fn + F1 - backlit red
Fn + F2 - backlit green
...........v............v............
Now how can I control the backlit light without the remote ? With new layout ? Can someone please guide me.
I got this strange error when i build my rs84 keyboard. When I press enter key, J key is activated as well and vice versa, similar to "\" and u key, backspace and 7 key, printScrn and F7. Does anyone know to to fix this? Thank you so muchPlease check around the MCU that if the pin 21 and 22 are shorted.Show Image(http://i.imgur.com/Whiyibr.png)
Hey all, wondering if anyone has successfully used dfu-programmer to program a RS96 with a compiled hex file? I am able to build the file from the tmk_software fork but, when I send it to dfu it claims that their is no devise attached. I have tried to get the keyboard into program mode by holding down the esc while plugging in the USB as well as the esc and the f1 key. Any assist would be amazing.RS96 uses a printer class bootloader which is based on LUFA's BootloaderPrinter, so it cannot be programmed by dfu-programmer which only supports Atmel's DFU bootloader. Please read the user's guide again and you will find how to program it.
cat {your.hex} | lpr
Can I use this guide for my RS68 which is an RS II+?
Can I use this guide for my RS68 which is an RS II+?
Yes.
RSII+ has a very similar bootloader to RSIII. The only difference is the key combination for entering HEX mode and EEP mode.
To enter EEP mode, please hold down the top-left key in the typewriter keys (which is usually configured to Esc or `~ key).
To enter HEX mode, please also hold down the key on the right side of the top-left key in the typewriter keys (which is usually configured as 1! key).
Hey guys quick question. I'm currently trying to keymap my RS 78 Red Scarf II+ and I have gotten the main layer and the function layer to work aside from the control of the RGB SMD LEDs on the back. I tried to import the raw data from the Red Scarf III users guide and every time I try to import that Fn using TMK it gets the following error: Error! Please check your data!
I know pasting the raw code helps in troubleshooting so I will do so below
Starting layer
["F1","F2",{x:0.25},"Esc","!\n1","@\n2","#\n3","$\n4","%\n5","^\n6","&\n7","*\n8","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace","Home"],
["F3","F4",{x:0.25,w:1.5},"Tab","Q","W","E","R","T","Y","U","I","O","P","{\n[","}\n]",{w:1.5},"|\n\\","End"],
["F5","F6",{x:0.25,w:1.75},"Caps\n\n\n\n\n\nLock","A","S","D","F","G","H","J","K","L",":\n;",{fa:[1]},"\"\n'",{f:3,w:2.25},"Enter",{f:3},"PgUp"],
[{f:3},"F7",{f:3},"F8",{x:0.25,f:3,w:2.25},"Shift",{f:3},"Z",{f:3},"X",{f:3},"C",{f:3},"V",{f:3},"B",{f:3},"N",{f:3},"M",{f:3},"<\n,",{f:3},">\n.",{f:3},"?\n/",{f:3,w:1.75},"Shift",{f:3},"↑",{f:3},"PgDn"],
[{f:3},"F9",{f:3},"F10",{x:0.25,f:3,w:1.25},"Ctrl",{f:3,w:1.25},"Win",{f:3,w:1.25},"Alt",{f:3,w:6.25},"Space",{f:3,w:1.5},"Alt",{f:3,w:1.5},"Fn0",{f:3},"←",{f:3},"↓",{f:3},"→"]
Fn layer
[{a:7},"","",{x:0.25},"","","","","","","","","","","","","",{a:4,w:2},"Delete",{a:7},""],
["","",{x:0.25,w:1.5},"","","","","","","","","","","","","",{w:1.5},"",""],
["","",{x:0.25,w:1.75},"",{a:4},"Fn4","Fn5","Fn6","Fn7","Fn8","Fn9",{a:7},"","","","","",{w:2.25},"",""],
["","",{x:0.25,w:2.25},"",{a:4},"Fn1","Fn2","Fn3",{a:7},"","","",{a:4},"Mute","VolDn","VolUp",{a:7},"",{w:1.75},"","",""],
["","",{x:0.25,w:1.25},"",{w:1.25},"",{w:1.25},"",{w:6.25},"",{w:1.5},"",{w:1.5},"","","",""]
and that all works just fine until I try to import this Fn for control of the RGB LEDs:
"0":["ACTION_LAYER_MOMENTARY",1],"1":["ACTION_BACKLIGHT_TOGGLE"],"2":["ACTION_BACKLIGHT_DECREASE"],"3":["ACTION_BACKLIGHT_INCREASE"],"4:["ACTION_FUNCTION","2",0],"5":["ACTION_FUNCTION","7",0],"6":["ACTION_FUNCTION","7","1"],"7":["ACTION_FUNCTION","4",0],"8:["ACTION_FUNCTION","3",0],"9":["ACTION_FUNCTION","6","2"],"10":["ACTION_FUNCTION","5","1"],"11":["ACTION_FUNCTION","5","4"],"12:["ACTION_FUNCTION","5","13"],"13":["ACTION_FUNCTION","5","5"],"14":["ACTION_FUNCTION","5","11"],"15:["ACTION_FUNCTION","5","6"],"16":["ACTION_FUNCTION","5","15"],"17":["ACTION_FUNCTION","5",0]
It will not import and I get the above error. Is there something I am missing? Did something change for the RS 78? I just want o be able to control the rear LEDs
Any info would be greatly appreciated :)
Can I use this guide for my RS68 which is an RS II+?
Yes.
RSII+ has a very similar bootloader to RSIII. The only difference is the key combination for entering HEX mode and EEP mode.
To enter EEP mode, please hold down the top-left key in the typewriter keys (which is usually configured to Esc or `~ key).
To enter HEX mode, please also hold down the key on the right side of the top-left key in the typewriter keys (which is usually configured as 1! key).
I'm configuring my keymap in TKG, but its always "position mismatch". how do I solve this? http://i.imgur.com/Tfcbpv4.jpg
Anyone else have any insight on this one? Getting the same issue when trying to flash the board and import the function layer information from the manual.
Hi everyone.Did you hold escape while plugging it in?
I received my RS96 III board yesterday, soldered some switches and tested it. Until here everything's fine. Then I tried to build my own layout, but impossible to make this keyboard recognized as a printer in windows. In either EEP or HEX mode the keyboard is recognized as "RedScarf HID EEPROM".
(Attachment Link)
In normal mode the keyboard is well detected as.. a keyboard.
(Attachment Link)
What should I do to recognize it properly as a printer ?
Thanks
Hi everyone.Did you hold escape while plugging it in?
I received my RS96 III board yesterday, soldered some switches and tested it. Until here everything's fine. Then I tried to build my own layout, but impossible to make this keyboard recognized as a printer in windows. In either EEP or HEX mode the keyboard is recognized as "RedScarf HID EEPROM".
(Attachment Link)
In normal mode the keyboard is well detected as.. a keyboard.
(Attachment Link)
What should I do to recognize it properly as a printer ?
ThanksShow Image(http://uploads.tapatalk-cdn.com/20170402/52371d97a5c2927d30a881a228b0f00a.jpg)
Hi everyone.Did you hold escape while plugging it in?
I received my RS96 III board yesterday, soldered some switches and tested it. Until here everything's fine. Then I tried to build my own layout, but impossible to make this keyboard recognized as a printer in windows. In either EEP or HEX mode the keyboard is recognized as "RedScarf HID EEPROM".
(Attachment Link)
In normal mode the keyboard is well detected as.. a keyboard.
(Attachment Link)
What should I do to recognize it properly as a printer ?
ThanksShow Image(http://uploads.tapatalk-cdn.com/20170402/52371d97a5c2927d30a881a228b0f00a.jpg)
I am having the same problem, holding escape (top left key) while plugging it in only reads as a keyboard.
---===>Device Information<===---
English product name: "RedScarf HID EEPROM"
ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Full (is not SuperSpeed or higher capable)
Device Address: 0x23
Open Pipes: 1
===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0110
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x16C0 = Van Ooijen Technische Informatica
idProduct: 0x0478
bcdDevice: 0x0001
iManufacturer: 0x01
English (United States) "Dean Camera"
iProduct: 0x02
English (United States) "RedScarf HID EEPROM"
iSerialNumber: 0x00
bNumConfigurations: 0x01
---===>Open Pipes<===---
===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0040 = 0x40 bytes
bInterval: 0x05
---===>Full Configuration Descriptor<===---
===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0x32 = 100 mA
===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x00
===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0111
bCountryCode: 0x00
bNumDescriptors: 0x01
bDescriptorType: 0x22 (Report Descriptor)
wDescriptorLength: 0x0015
===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0040 = 0x40 bytes
bInterval: 0x05
$ git clone https://github.com/kairyu/tmk_keyboard_custom.git
enter repository$ cd tmk_keyboard_custom/
update submodules$ git submodule init
$ git submodule update
enter redscarf folder$ cd keyboard/RedScarfIII
#KEYMAP_IN_EEPROM_ENABLE = yes # Read keymap from eeprom
run make inside the RedScarfIII folder$ make -f Makefile
download the teensy loader CLI from $ teensy_loader_cli.exe --mcu=atmega32u4 -w -v RedScarfIII_lufa.hex
hold backspace+spacebar and reconnect keyboard, keep holding keys till you see spaces show up (ie eeprom has been cleared)Hi, I was wondering if you could help me with my red scarf? for some reason, I cannot get the "| \" pads on the pcb to work. when i press the switch nothing happens. I have tried two different positions for the switch, normal ANSI layout and ISO enter layout. I attached some pictures and circled the problem spot of the pcb. Hopefully i do not need a new one :(. http://imgur.com/a/RBvhN also the switch itself is not the problem (tested the switch to be working at other positions). I believe it has to be the pcb or maybe some sort of layout software issue.
also here is my raw data from keyboard layout editor
[{y:0.5},"Esc","Fn1","fn2","fn3","fn4","fn5","fn6","fn7","fn8","Fn9","fn10","fn11","fn12","fn13","fn14","fn15","fn16","fn17","fn18"],
["~\n`","!\n1","@\n2","#\n3","$\n4","%\n5","^\n6","&\n7","*\n8","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace","Num Lock","/","*","-"],
[{w:1.5},"Tab","Q","W","E","R","T","Y","U","I\n\n\n\nup","O","P","{\n[","}\n]",{x:0.25,a:7,w:1.25,h:2,h2:1,x2:-0.25},"enter",{a:4},"7\nHome","8\n↑","9\nPgUp",{h:2},"+"],
[{w:1.75},"fn0","A","S","D","F","G","H","J\n\n\n\nleft","K\n\n\n\ndown","L\n\n\n\nright",":\n;","\"\n'","|\n\\",{x:1.25},"4\n←","5","6\n→"],
[{w:2.25},"Shift","Z","X","C","V","B","N","M","<\n,",">\n.","?\n/",{w:1.75},"Shift","↑","1\nEnd","2\n↓","3\nPgDn",{h:2},"Enter"],
[{w:1.25},"Ctrl",{w:1.25},"Win",{w:1.25},"Alt",{w:6.25},"Space",{w:1.5},"Alt",{w:1.5},"Ctrl","←","↓","→","0\nIns",".\nDel"]
Will reflashing the hex maybe fix this problem for me?
A press of the 'h' key will return 'h' but a press of the r key will return '4rfc', q is '1qa' and 1 is '1qa' as well. I can't tell what Esc does.