geekhack

geekhack Projects => Making Stuff Together! => Topic started by: azhdar on Thu, 26 February 2015, 03:42:19

Title: RedScarfIII Manual (WIP)
Post by: azhdar on Thu, 26 February 2015, 03:42:19
Some people asked about a manual, and I found some informations, so I'll share what I've found so far, so everyone can experiment and report back.

Feizor gave me a manual for a 60% RedScarfIII (.doc attached file), in chinese sadly.

Please note that I have yet to test anything!!! Just sharing informations.

After a quick glance it seems that you simply create your mapping on http://www.keyboard-layout-editor.com
and then import it on this website : http://www.enjoyclick.org/tkg/. by pasting your raw data into the desired layer.

The Avaible labels being here:
http://www.enjoyclick.org/tkg/#help


Here is the exemple showed in the doc of a pokerII layout(only missing the WASD lock on rShift):
http://www.keyboard-layout-editor.com/#/layouts/7d55431c8a8d9f9bf94b6f6af8ce7c12

Looks like you can do the Fn layer by simply putting the labels into the side-print label.

The pokerII layout exemple helped me understand this part of the manual :

Quote
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"]

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.


Will continue once I have more time.



Title: Re: RedScarfIII Manual
Post by: azhdar on Thu, 26 February 2015, 03:42:48

Creating your layout

Keyboard layout editor
The utily tool to create your layouts for your redscarf is pretty simple, you create it on : http://www.keyboard-layout-editor.com/ and then past it on the web tool to get your keymapping file. You obviously need to be sure that your layout is accepted by the PCB you're working on.

Different modes
On the website (I'll get to the website part latter) there's 3 different modes to generate your layout:
Normal, simple and All-In-One.
I adress it before the website part because It changes how you need to prepare your layout.

Normal: you want to make one layout for each layer , for exemple :
Layer0 : http://www.keyboard-layout-editor.com/#/layouts/c69d3d242b7eca4fcfb534d0d4810604
Layer1 : http://www.keyboard-layout-editor.com/#/layouts/3ee6332b881aa263175a1ddf76b2a336

Simple: you only make one layout and it covers 2 layers , Top label & Bottom label for your regular layout, and Side-Printed label for the second layer. I don't know if you can make more that 2 layers on that mode. exemple :
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf

All-in-One: almost similar to Normal mode but you put each of your layer in the same layout just seperate it vertically :
http://www.keyboard-layout-editor.com/#/layouts/254775420a71e52bfb79d6da39000a8e

I achieved the same final layout and layers with the differents links posted above.

Label avaible and priority:
You can find all the usable labels here : http://www.enjoyclick.org/tkg/#help

$INSERT EXPLANATION OF PRIORITY HERE$
(http://i.imgur.com/S0Ksxcm.png)

About Fn layer: the backlight commands are on the fn mapping, Fn3 is Backlight on/off, Fn1 is increase backlit , Fn2 is decrease , more details on this picture:
(http://i.imgur.com/3EHUumg.png)
Fn0 is the label you want to use to do your regular Fn layer (see the layout posted above).

Since Backlit is taking Fn1 to Fn24 , you still have a total of 9 layers possible: Normal, Fn0, Fn25=>Fn31

$ TEST Fn25+ layers and come back with precisisons$

Reflashing the keyboard
To reflash the keyboard we'll go onto this website:
http://www.enjoyclick.org/tkg/

Before attempting anything on the website please read the "Red Scarf III User's Guide - How to Reflash.pdf" that Ryu provided and that you can download in OP

Title: Re: RedScarfIII Manual
Post by: Shanghaied on Thu, 26 February 2015, 09:06:13
Wow nice, I actually speak Chinese new and have a hopefully working redscarf, so I'll take a look when I get home.
Title: Re: RedScarfIII Manual
Post by: azhdar on Thu, 26 February 2015, 09:13:16
Wow nice, I actually speak Chinese new and have a hopefully working redscarf, so I'll take a look when I get home.

Let me know how it goes and report back !
Title: Re: RedScarfIII Manual
Post by: Shanghaied on Thu, 26 February 2015, 11:46:44
Okay, been playing with it for a bit, and azhdar, you appear to be mostly correct. Fn1 - Fn3 are fixed - they control the backlighting. I'm not sure what side labels do, but it might have something to do with the All-in-One and simple modes on the TMK GUI - there all the layers are edited together. In "normal" mode the TMK web GUI lets you edit each layer in the Keyboard Layout Editor - for example picture 3 in the manual shows the Fn0 layer (default), and picture 4 the Fn1 layer (Fn key held down). The URL for each layer is pasted into the respective fields in the GUI, then the GUI will allow you to choose the function of the Fn keys (Fn0-F7), they can either be a momentary modifier for activating layers (e.g. Fn key) or perform other functions, which are listed in the list of labels azhdar posted. Just write past the labels for the desired function into the top label of the key in the Keyboard Layout Editor. After all is done, the border of the input field turns green if everything is correctly edited and you can download the .eep file, otherwise the border remains red.

So far I've not been able to program some Nordic characters ( , etc), because they were not part of the allowable labels, but I'm guessing this can be done with the labels International1 - International9 and LAN1 - LAN9, although I'm sure how yet.

Also I'm still not totally sure how the firmware can be flashed yet. Instruction is provided for GH60: basically, download a package called dfu-reflash.zip; connect the keyboard to the PC and then press the the S1 button on the back of the PCB; wait for the driver to update/install; copy and paste the .eep file into the reflash-gh60_rev_cn.bat file under the dfu-reflash folder; then a window should appear prompting you to press any key to continue; press any key and you are done. Rather ominously, there's a red warning text underneath saying that flashing must been strictly performed as outlined above. Not sure exactly how it will work on RSIII since they are no physical buttons on the back of the PCB that I can see.

Anyway this has been my first programmable keyboard, so anyone with more experience please chime in.




Title: Re: RedScarfIII Manual
Post by: byker on Thu, 26 February 2015, 11:51:00
Thanks for starting to put this together azhdar! I am sure it will be useful when my board finally arrives.  :)
Title: Re: RedScarfIII Manual
Post by: Ryu on Sun, 01 March 2015, 20:18:56
Sorry everyone, it's my fault :(
I'm writing the manual and will complete it soon.

Let me explain about the 3 layer modes first.
Normal mode: Ordinary, one raw data one layer.
Simple mode: One raw data for two layers - top&bottom for layer0 and side for layer1, and automatic set fn0~fn3 to common usage.
All-in-one mode: One raw data for mutiple layers, just put layers one by one vertically, for example http://www.keyboard-layout-editor.com/#/layouts/2794625e34ece7201585646e75be9822 (http://www.keyboard-layout-editor.com/#/layouts/2794625e34ece7201585646e75be9822)

You can find more samples here: http://www.enjoyclick.org/wiki/tkg (http://www.enjoyclick.org/wiki/tkg)

If you have any question in a rush, please feel free to ask me directly.
Title: Re: RedScarfIII Manual
Post by: Ryu on Sun, 01 March 2015, 22:25:03
Quote
Quote
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"]

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.

The rest seems that someone is using left win key as fn key but he also want some win key combinations work as well, so
Fn4: LWin+E
Fn5: LWin+D
Fn6: LWin+R
Fn7: LWin+F
Fn8: Toggle layer2

I guess layer2 maybe a arrow keys overlay on RShift/RAlt/RWin/RCtrl.
Title: Re: RedScarfIII Manual
Post by: Ryu on Mon, 02 March 2015, 10:16:21
Sorry to keep you waiting.
Here is a simple manual for how to reflash RedScarfIII.
And sorry for my poor English.
Title: Re: RedScarfIII Manual
Post by: azhdar on Mon, 02 March 2015, 10:27:25
Sorry to keep you waiting.
Here is a simple manual for how to reflash RedScarfIII.
And sorry for my poor English.
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.
Title: Re: RedScarfIII Manual
Post by: Shanghaied on Mon, 02 March 2015, 11:49:08
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.
Title: Re: RedScarfIII Manual
Post by: Ryu on Tue, 03 March 2015, 03:22:51
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.

I'm not sure what's your goal, so I will try to answer your question with some assuming prerequisite.

First of all, you should know that TKG's mechanism is translating keycap printing to scancode. It attempts to guess what the key is (what the scancode should be) by recognizing the combinations of the labels. So actually a keymap is a cluster of scancodes.

For the first question. As far as I know, how to type non English characters is depended on the keyboard layout setting and IME setting of your host.

If you are using a physical US layout and you want to set your host (I suppose it's a Windows PC) to use US layout too, you can open "Text Services and Input Languages" and add "English > Keyboard > United States-International". Then switch to the new layout added just now, you will get by typing RAlt+p, RAlt+q, RAlt+w respectively.
If your goal is type them by only one key stroking, you can set for example Fn4="Key action > Modified key, modifier=Right Alt, key=p and P", Fn5="Key action > Modified key, modifier=Right Alt, key=q and Q", Fn6="Key action > Modified key, modifier=Right Alt, key=w and W" on TKG. Then you can get by typing fn4, fn5 and fn6.

If you are using a physical Swedish (sorry I'm not familiar with those characters, maybe Swedish?) layout and you want to set your host to use Swedish layout too, you can add the "Swedish > Keyboard > Swedish" layout first (maybe you already have it). And on this condition, actually the scancodes of are same with ;(semi-colon), '(single-quote) and [(square-brackets) of US layout. So putting the US symbols on your keymap is equal to putting the non English characters on it.
Certainly, it's more grace to use the non English characters' self as the label than use the US stand-ins. If you expect this, please help me to collect these characters into a table because I'm really not familiar with them. And then I will add them to available labels, just like how I support ISO layout (you can find them from the number keys).

For the second question, I'm afraid that you may not use lang1 and international1 in that way.

To explain this, here is a specification for reference: Keyboard Scan Code Specification - Microsoft (https://www.google.co.jp/url?sa=t&rct=j&q=&esrc=s&source=web&cd=8&cad=rja&uact=8&ved=0CEAQFjAH&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F1%2F6%2F1%2F161ba512-40e2-4cc9-843a-923143f3456c%2Fscancode.doc&ei=emX1VNDKE9S68gWxtoAY&usg=AFQjCNFpwWwiM0iIlms4bSL-fVCvRK4K2w&sig2=jVlELv9H8-xFH2NV2of9tg&bvm=bv.87269000,d.dGc)

You can find the descriptions of lang1 (Keyboard LANG1) and international1 (Keyboard Kanji1) at the footnotes of Appendix C. They are handled by the host so we can't decide what they stand for on the keyboard side.

Please feel free to ask me any questions.
Title: Re: RedScarfIII Manual
Post by: Shanghaied on Tue, 03 March 2015, 08:43:45
Ah ryu, what you said is actually very useful! Thank you!

Sorry, but yes it is Swedish (also Finnish, they have the same layout), and I'm currently on a physical Swedish layout. I'll have to think this over once I get home, and try a few things out on TKG.

As for character labels, I was getting seven (7) "unknown label" errors when I was putting in a full Swe/Fin layout, which were ; ` (the last two are a bit weird, since they seem to only exist on Scandinavian layouts). I might take you up on your offer of adding non-English character labels. I can certainly make a table for Scandinavian characters since those are the ones I'm most familiar with. Not sure when though, since I'm in the middle of writing a big report, but hopefully I'll have a bit more time next week...

Thanks again!
Title: Re: RedScarfIII Manual
Post by: azhdar on Wed, 04 March 2015, 14:32:23
Hey ryu, I finally tried my hand on this and while trying this layout :
http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
I ended up with the keymap (attached to my post)

I tried both all-in mode and dual layer mode with those layouts:
http://www.keyboard-layout-editor.com/#/layouts/35cfe9dd0da60b6b802c49b73efea04a
http://www.keyboard-layout-editor.com/#/layouts/3ee6332b881aa263175a1ddf76b2a336

Title: Re: RedScarfIII Manual
Post by: Ryu on Thu, 05 March 2015, 01:16:57
Hi azhdar, I tried your link of KLE as it is and got a seemingly working keymap as the attachment.

The keymap you attached seems to have a empty layout. Did you get any error messages (something in red) when you make it?
Title: Re: RedScarfIII Manual
Post by: azhdar on Thu, 05 March 2015, 01:32:45
Hi azhdar, I tried your link of KLE as it is and got a seemingly working keymap as the attachment.

The keymap you attached seems to have a empty layout. Did you get any error messages (something in red) when you make it?
http://www.keyboard-layout-editor.com/#/layouts/35cfe9dd0da60b6b802c49b73efea04a
I got this:
(http://i.imgur.com/wgiUZlk.png)

http://www.keyboard-layout-editor.com/#/layouts/3ee6332b881aa263175a1ddf76b2a336
And for the Fn layer I got this error:
(http://i.imgur.com/mmRsVN8.png)
Title: Re: RedScarfIII Manual
Post by: Ryu on Thu, 05 March 2015, 02:01:21
Oh, I see what's the problem.
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.
Title: Re: RedScarfIII Manual
Post by: azhdar on Thu, 05 March 2015, 02:08:39
Oh, I see what's the problem.
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.
Damn how did I missed that  :confused:
Will try and report back.
Title: Re: RedScarfIII Manual
Post by: azhdar on Thu, 05 March 2015, 06:57:35
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?


Title: Re: RedScarfIII Manual
Post by: Ryu on Thu, 05 March 2015, 21:58:27
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
Title: Re: RedScarfIII Manual
Post by: azhdar on Fri, 06 March 2015, 01:06:10
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Title: Re: RedScarfIII Manual
Post by: Ryu on Fri, 06 March 2015, 01:19:48
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Then it seems that the firmware is live.
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.
Title: Re: RedScarfIII Manual
Post by: azhdar on Fri, 06 March 2015, 01:30:56
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Then it seems that the firmware is live.
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.
Offline, I guess it was, It cleared from the printing list.
Title: Re: RedScarfIII Manual
Post by: Ryu on Fri, 06 March 2015, 02:08:18
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Then it seems that the firmware is live.
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.
Offline, I guess it was, It cleared from the printing list.
That's so weird.
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.
Title: Re: RedScarfIII Manual
Post by: azhdar on Fri, 06 March 2015, 02:18:17
More
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Then it seems that the firmware is live.
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.
Offline, I guess it was, It cleared from the printing list.
That's so weird.
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.
Where do I find hid_listen? I'll try that.
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.
Title: Re: RedScarfIII Manual
Post by: Ryu on Fri, 06 March 2015, 02:28:48
More
Oh, I see what's the problem.
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.
so trying with this layout : http://www.keyboard-layout-editor.com/#/layouts/5202bd017285426aefc56e7342d968f5
Simple mode gave me the keymap that I attached below, still don't work.
Should I reload the Hex file onto the keyboard?
I tried the keymap you attached on my bare PCB and I see it works.
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?
keyboard is recognized , it evens appears as "redscarfIII" but none of the keys works.
Then it seems that the firmware is live.
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.
Offline, I guess it was, It cleared from the printing list.
That's so weird.
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.
Where do I find hid_listen? I'll try that.
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.
You can find hid_listen on PJRC's website. https://www.pjrc.com/teensy/hid_listen.html
Anyway please make sure you have reflashed the proper keymap :)
Title: Re: RedScarfIII Manual
Post by: Bromono on Fri, 06 March 2015, 06:05:49
I want to contribute to this thread.. But mine is stuck in the endless shipping loop :(
Title: Re: RedScarfIII Manual
Post by: xauser on Fri, 06 March 2015, 13:25:29
Could you please tell me which controller is used on the redscarfIII pcb? Thank you!
Title: Re: RedScarfIII Manual
Post by: Ryu on Fri, 06 March 2015, 21:11:22
Could you please tell me which controller is used on the redscarfIII pcb? Thank you!
Hi xauser, off course.
Red Scarf III uses the familiar atmega32u4 as it's main controller.
And the official firmware is based on a customized tmk_keyboard.
You can find the source code here: https://github.com/kairyu/tmk_keyboard_custom/tree/master/keyboard/RedScarfIII
Title: Re: RedScarfIII Manual
Post by: xauser on Sat, 07 March 2015, 05:09:56
Great! Happy to see more tmk based firmwares. Really interesting stuff in there. I'm looking forward to dig into this deeper once my redscarfIII pcb arrives.
Title: Re: RedScarfIII Manual
Post by: azhdar on Sun, 08 March 2015, 17:29:17
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?
Title: Re: RedScarfIII Manual
Post by: Shanghaied on Sun, 08 March 2015, 18:25:42
Ryu mentioned earlier that the lang and int labels are usually defined by the OS for some languages, and can't be programmed by the user.
Title: Re: RedScarfIII Manual
Post by: Ryu on Sun, 08 March 2015, 23:11:50
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.
Title: Re: RedScarfIII Manual
Post by: azhdar on Mon, 09 March 2015, 02:04:23
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.


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:
(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.
Title: Re: RedScarfIII Manual
Post by: Ryu on Mon, 09 March 2015, 02:41:09
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.


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.

Yes, you are right. Please let me explain this by a table.
Code: [Select]
+----------------+-----------+----------------+
| 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.
And at present we have no way to assign a key to Non-US \ and |. This is why you always get only \ and | key lighted on.

Now what should we do is making a explicit label to tell TKG that key is Non-US \ and | but not a US \ and |.
(TKG recognizes keys by key units, it cannot know what the layout actually is.)
I need your suggestion.
Title: Re: RedScarfIII Manual
Post by: azhdar on Mon, 09 March 2015, 02:49:51
Can you simply name it ISO?
Title: Re: RedScarfIII Manual
Post by: Ryu on Mon, 09 March 2015, 03:04:14
Can you simply name it ISO?
Thank you, fixed!
Now you can use "iso |\n\\" to assign a key to "Non-US \ and |".
Title: Re: RedScarfIII Manual
Post by: azhdar on Mon, 09 March 2015, 07:12:02
Can you simply name it ISO?
Thank you, fixed!
Now you can use "iso |\n\\" to assign a key to "Non-US \ and |".
thanks, unknow label for the moment let me know when updated :)
Title: Re: RedScarfIII Manual
Post by: Ryu on Mon, 09 March 2015, 08:00:25
Can you simply name it ISO?
Thank you, fixed!
Now you can use "iso |\n\\" to assign a key to "Non-US \ and |".
thanks, unknow label for the moment let me know when updated :)
It should have been updated when my previous post.
You can find a new "iso |" label at the help page. If not, please try to hit Ctrl+R to reload the webpage.
And please note that the bottom label "\" is still necessary.
Title: Re: RedScarfIII Manual
Post by: azhdar on Mon, 09 March 2015, 12:41:41
Still unknow label:
(http://i.imgur.com/2PKpYLs.png)

layout:
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf
Title: Re: RedScarfIII Manual
Post by: Ryu on Mon, 09 March 2015, 20:10:27
Still unknow label:
Show Image
(http://i.imgur.com/2PKpYLs.png)


layout:
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf
I tried your layout and it just works well.
I think your browser is using the locally cached file. Please press Ctrl+R until you see the following in the help page.
[attachimg=1]
Title: Re: RedScarfIII Manual
Post by: azhdar on Tue, 10 March 2015, 06:02:50
Still unknow label:
Show Image
(http://i.imgur.com/2PKpYLs.png)


layout:
http://www.keyboard-layout-editor.com/#/layouts/1e84476c846afc053faa0be569906adf
I tried your layout and it just works well.
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)

Indeed it was that. Layout is all working know.
Thanks for your help ryu.
Title: Re: RedScarfIII Manual (WIP)
Post by: azhdar on Fri, 13 March 2015, 05:21:12
Managed to work a bit on putting it together (see the second post).
Will continue later.
Title: Re: RedScarfIII Manual (WIP)
Post by: Manchias on Thu, 02 April 2015, 12:22:51
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 ?



Title: Re: RedScarfIII Manual (WIP)
Post by: Manchias on Thu, 02 April 2015, 12:39:54
I fixed the problem. All the keys worked after I press Fn0 by using this layout: http://www.keyboard-layout-editor.com/#/layouts/0409c3a4710f80955aca9b188071de4d

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.
Title: Re: RedScarfIII Manual (WIP)
Post by: Manchias on Thu, 02 April 2015, 12:46:58
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.



Title: Re: RedScarfIII Manual (WIP)
Post by: Manchias on Thu, 02 April 2015, 13:09:21
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.
Title: Re: RedScarfIII Manual (WIP)
Post by: azhdar on Thu, 02 April 2015, 13:35:34
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 ?





On the layout you linked, there's no binding related to the Fn layer, so you probably should have used the normal mode, with only one layer.
I fixed the problem. All the keys worked after I press Fn0 by using this layout: http://www.keyboard-layout-editor.com/#/layouts/0409c3a4710f80955aca9b188071de4d

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.
I 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.


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.




You should refer to this picture: (http://i.imgur.com/3EHUumg.png)

I believe you can use the Fn numbers of the remote to have the remote buttons onto the keyboard, but I have not tested it.
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.

Yeah, I made that mistake at the beggining too :)

If you haven't read it yet, my first and second post are a quick introduction to what I've tested on the keyboard so far.
I'll need to finish the manual on day.
Title: Re: RedScarfIII Manual (WIP)
Post by: poog on Wed, 13 May 2015, 16:49:38
Hello,

I soldered up the switches and tried flashing firmware last night but it looks like I'm having some trouble with the smd leds. I don't have any leds on the keys yet so there were no flashes or anything to confirm certain modes but when I first plugged it in (without pressing anything) the smd leds came on automatically and switched colors over and over.

I unplugged it and held down the upper left button (esc) and replugged it and this time no smd leds came on. The driver installed correctly and I saw the generic/text only printer in my devices. I tried flashing a configuration online (simple mode) but the little box kept spinning so I switched to offline flashing. The print job never left the "what's printing" queue even after a couple minutes but when I unplugged and replugged in normal mode (after waiting in vain for the job to disappear) the configuration I had made was flashed to the keyboard!

However, now I can't figure out how to light up the smd leds. I tried using the remote control (after pulling out that plastic thing on the batterry) and it doesn't seem to be working. I also tried the function keys (fn1, fn2, fn3) but they didn't do anything.

Any ideas on what I could troubleshoot to fix it?

Thanks
Title: Re: RedScarfIII Manual (WIP)
Post by: poog on Wed, 13 May 2015, 21:43:52
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.
Title: Re: RedScarfIII Manual (WIP)
Post by: VesperSAINT on Thu, 14 May 2015, 03:44:10
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 was kind of having the same problem, but I haven't been able to replace the battery that it came with just yet. The thing is though, the remote works sometimes, and most of the time, it doesn't. I guess I won't know for sure if it's the battery or not until I replace it.

Will update when I do.
Title: Re: RedScarfIII Manual (WIP)
Post by: azhdar on Thu, 14 May 2015, 03:49:18
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.

On mine It wasn't delivered with battery so I bought a fresh battery. I don't encounter any issues with it besides the fact that you can tell that the remote is not top quality, you got to aim straight at the keyboard, and sometimes it doesn't register for some reasons. Altough once you've found the correct angle it works great.
Title: Re: RedScarfIII Manual (WIP)
Post by: Glod on Fri, 15 May 2015, 17:39:53
edit: hiding frustrations in programming :)
Title: Re: RedScarfIII Manual (WIP)
Post by: Glod on Fri, 15 May 2015, 17:52:47
all good, all programmed, thanks for the guide
Title: Re: RedScarfIII Manual (WIP)
Post by: Spopepro on Sun, 17 May 2015, 23:53:48
So... um... anyone know how we're supposed to build a hex file from source? 

Mine was working great, and the TMK generator is a really awesome feature.  But I wanted to get crazy with some macros, and those have to be done in firmware.  The only one currently available is a macro for keypad 00.  So I downloaded the source, made my edits (I'm pretty confident they are solid), and followed the instructions for loading a hex file.  No dice.  There are two Makefile scripts, one is .lufa and the other is .pjrc.  Following the instructions for flashing a .hex file neither of them result in a working keyboard. 

So... the bootloader functions still work, but I can't get a keyboard to work with either my custom keymaps or kairyu's source.  Either I'm building it wrong, or the hex files built from source need to be loaded through another method. 

Any ideas?
Title: Re: RedScarfIII Manual (WIP)
Post by: Spopepro on Mon, 18 May 2015, 18:10:01
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...
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Tue, 19 May 2015, 22:11:19
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...

Off course you can ask it here, I think.
Definition macros is what TKG can not do presently, and re-compiling from source code is certainly a supposed way to customize user's own firmware - otherwise there will not be a "Download .c file" feature.

I think maybe the "Unknown Device" issue is caused by a oversize image, please check the size of your .hex file. (The last address inside the hex file should not exceed 0x7000)
This is very probability if you are compiling with WinAVR instead of something like avr8-gnu-toolchain which I'm using.
WinAVR always gives me a bigger .hex file even with the same source code, and to add RGB LED control feature I have used almost all available space. (You can find the last address inside the pre-compiled .hex file is 0x6FC2+0x08)

And after you disabled KEYMAP_IN_EEPROM_ENABLE, the size of your .hex file seems became ok, but maybe you have triggered the Boot Maigc (https://github.com/tmk/tmk_keyboard#boot-magic-configuration---virtual-dip-switch) feature by mistake.
You can try to hold down space and backspace simultaneously and plug in the usb cable to ensure keyboard startup with a clear EEPROM.
Hope this can help you.
Title: Re: RedScarfIII Manual (WIP)
Post by: Spopepro on Thu, 21 May 2015, 14:28:51
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.
Title: Re: RedScarfIII Manual (WIP)
Post by: Spopepro on Thu, 21 May 2015, 17:18:26
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?
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Thu, 21 May 2015, 20:46:16
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.

Oh, you are exactly right. It's caused by a merging of new feature recently. I will fix it soon. Thanks for your feedback.

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?

Sorry to make you confusing. If you compile the .hex file by yourself, I recommend you to disable KEYMAP_IN_EEPROM_ENABLE just like what you did at the very beginning.
Actually the compiler won't generate any helpful .eep file in this case. (It only generate non-empty .eep file when user declaring variable with EEMEM attribute, but we don't use this at all)
KEYMAP_IN_EEPROM_ENABLE is supposed to work with .eep file generated by TKG. So just to disable it to let everything go well, including much smaller .hex file ;)

And also I have to admit that even I have tried to compile with severial combinations on windows, linux and osx, I found avrgcc + avr8-gnu-toolchain on windows always gives me the smallest image :(
Title: Re: RedScarfIII Manual (WIP)
Post by: Bromono on Wed, 19 August 2015, 11:34:14
How do you turn off/fade the in switch LEDs?

Edit: figured it out.
Title: Re: RedScarfIII Manual (WIP)
Post by: azhdar on Wed, 19 August 2015, 11:36:18

Fn0: Activate Layer1
Fn1 : backlight decrease
Fn2 : backlight on/off
Fn3 : backlight increase

Title: Re: RedScarfIII Manual (WIP)
Post by: Bromono on Wed, 19 August 2015, 19:03:06
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 used this but lost all control of the RGB backlighting of the keyboard. I can only control the LEDs
Title: Re: RedScarfIII Manual (WIP)
Post by: Steezus on Sun, 20 September 2015, 13:39:38
I put together my RS96 and only the num lock led is working. My soldering looks fine and so does the MCU. After asking around it seems like the general consensus is either being a firmware issue or that I didn't turn the LEDs on. I can't really seem to find a solution to this problem. Does anybody have an idea?
Title: Re: RedScarfIII Manual (WIP)
Post by: Steezus on Mon, 21 September 2015, 11:48:31
I followed all the steps to reflash my RS96 and now my keyboard does not work at all.

Here is what I set as my first layer, for some reason the hyperlink is longer than the raw data so to save space I'm going to post the raw data instead:
["Esc","F1","F2","F3","F4","F5","F6","F7","F8","F9","F10","F11","F12","Print Screen","Scroll Lock","Delete","Insert","End","PgUp"],
["~\n`","!\n1","@\n2","#\n3","$\n4","%\n5","^\n6","&\n7","*\n8","(\n9",")\n0","_\n-","+\n=",{w:2},"Backspace","Num Lock","/","*","PgDn"],
[{w:1.5},"Tab","Q","W","E","R","T","Y","U","I","O","P","{\n[","}\n]",{w:1.5},"|\n\\","7\nHome","8\n↑","9\nPgUp","-"],
[{w:1.25,w2:1.75,l:true},"Caps Lock",{x:0.5},"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","V","B","N","M","<\n,",">\n.","?\n/",{w:1.75},"Shift","↑","1\nEnd","2\n↓","3\nPgDn",{h:2},"Enter"],
[{c:"#c0c0c0",w:1.25},"Ctrl",{w:1.25},"Win",{w:1.25},"Alt",{a:7,w:6.25},"",{a:4,w:1.5},"Alt",{w:1.5},"Fn0",{c:"#cccccc"},"←","↓","→",{c:"#c0c0c0"},"0\nIns",{c:"#cccccc"},".\nDel"]

Here is what I have for my second layer:
[{a:7},"","","","","","","","","","","","","","","","","","",""],
["","","","","","","","","","","","","",{w:2},"","","","",""],
[{w:1.5},"","","","","","","","","","","","","",{w:1.5},"","","","",""],
[{w:1.25,w2:1.75,l:true},"",{x:0.5},"","","","","","","","","","","",{w:2.25},"","","","",""],
[{w:2.25},"",{a:4},"Fn1","Fn2","Fn3",{a:7},"","","","",{a:4},"VolUp","VolDn","Mute",{a:7,w:1.75},"",{a:4},"PgUp",{a:7},"","","",{h:2},""],
[{c:"#c0c0c0",w:1.25},"",{w:1.25},"",{w:1.25},"",{w:6.25},"",{w:1.5},"",{w:1.5},"",{c:"#cccccc",a:4},"Home","PgDn","End",{c:"#c0c0c0",a:7},"",{c:"#cccccc"},""]

When I put them into http://www.enjoyclick.org/tkg/ (http://www.enjoyclick.org/tkg/) I do not receive any error messages in red, I then add in the Fn code provided in the User's Guide.
I set Fn0 as a mometary action to open layer 1
Fn1: Toggles Backlight
Fn2: Decrease Backlight
Fn3: Increase Backlight

After attempting both online and offline flashes neither seem to work. After flashing, my num lock led flashes(which seems to be the only switch led to work) and then I replug the usb cable in and no lights, even rgb work now and no key outputs anything. Is there anything I'm missing or doing wrong?
Title: Re: RedScarfIII Manual (WIP)
Post by: SuperBo on Sun, 06 December 2015, 06:41:03
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 much

(http://i.imgur.com/Whiyibr.png)
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Mon, 07 December 2015, 04:03:53
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 much

Show Image
(http://i.imgur.com/Whiyibr.png)

Please check around the MCU that if the pin 21 and 22 are shorted.
(http://i.imgur.com/KoQ1Y6r.png)
Title: Re: RedScarfIII Manual (WIP)
Post by: braidn on Thu, 19 May 2016, 08:00:37
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.
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Fri, 20 May 2016, 06:38:37
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.
Title: Re: RedScarfIII Manual (WIP)
Post by: braidn on Fri, 20 May 2016, 14:20:45
RYU, Does this mean that the RS96 is only available to be programmed in a Window's environment? No Mac or Linux environment's allowed?
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Fri, 20 May 2016, 20:33:44
On *nix systems, it's even much easier. Just open terminal and type as follows.
Code: [Select]
cat {your.hex} | lpr
Title: Re: RedScarfIII Manual (WIP)
Post by: braidn on Mon, 23 May 2016, 08:29:11
I have created the Hex through the TMK fork, but once I hold down esc, plug in the keyboard, and after using the lpr command, the keyboard never reboots and the new/changed keymap is never uploaded. I do see that an item is added to the printer queue and it takes a little while (maybe 1 or so minutes to complete) and I see it finished. Any ideas?
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Tue, 24 May 2016, 03:15:21
Unfortunately the keyboard cannot automatically reboot after printing since there was no coding space to implement this feature.

If you want to use the keymap within the hex which you built, please try to clear the EEPROM after programmed the hex file by e.g. bootmagic (Space+Backspace), or just disable KEYMAP_IN_EEPROM_ENABLE in the Makefile when you building the firmware.
Title: Re: RedScarfIII Manual (WIP)
Post by: braidn on Fri, 03 June 2016, 22:14:43
Ryu,

I am doing the following and nothing seems to be working:


Afterwards the printer queue shows that it's printing and stops. However, no matter what, it does not change the layout on the RS96. Kinda lost.
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Tue, 07 June 2016, 22:53:52
braidn,

If the thing you only want to do is customizing some key definitions, I recommend you to try to use TKG.
If you are attempting to customize more things like macros or even some new features for keyboard, you are doing the right way.
But please don't forget to choose any one of the follows which I also mentioned in the previous reply to make your keymap applied .
1. Clear the EEPROM after you programmed the hex file by e.g. bootmagic (hold Space+Backspace keys simultaneously for a long while when plug in the usb).
2. Disable KEYMAP_IN_EEPROM_ENABLE in the Makefile when you building the firmware.
Title: Re: RedScarfIII Manual (WIP)
Post by: Jumie on Wed, 08 June 2016, 00:32:00
Can I use this guide for my RS68 which is an RS II+?
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Wed, 08 June 2016, 01:29:28
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).
Title: Re: RedScarfIII Manual (WIP)
Post by: Jumie on Fri, 10 June 2016, 08:39:00
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
Title: Re: RedScarfIII Manual (WIP)
Post by: joostflux on Tue, 21 June 2016, 22:18:36
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 :)
Title: Re: RedScarfIII Manual (WIP)
Post by: gzprime on Mon, 12 September 2016, 07:48:53
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 :)

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.
Title: Re: RedScarfIII Manual (WIP)
Post by: feralfoo on Mon, 12 September 2016, 09:16:09
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

Hi Jumie,

Your post is a few months old and I haven't seen a response. If you haven't resolved this check out my KLE config here http://www.keyboard-layout-editor.com/#/gists/a622fd495ec3e1a1f402b1572e0d5cf7 (http://www.keyboard-layout-editor.com/#/gists/a622fd495ec3e1a1f402b1572e0d5cf7), you basically need to move all your keys several positions to the right.
Title: Re: RedScarfIII Manual (WIP)
Post by: gzprime on Mon, 12 September 2016, 09:38:20

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.

So I made some progress in that I realized to import the LED functions from the manual, you have to add actual "Fn" buttons to one of your layers. As you add more "Fn" buttons more of the options will show up. If  you're getting errors importing the actual code from the manual, it's probably because there are line breaks in weird places - throw it in a text editor and clean it up. That fixed it for me.

However, I still can't get the main Fn0 function key to temporarily choose the other layer with the light functions.
For example: "Fn0 - Layer action > Momentary - layer 1"

Then all my light functions are on Layer 1. Is the correct approach? Should I be using momentary or another type of action?

Thanks everyone!
Title: Re: RedScarfIII Manual (WIP)
Post by: gzprime on Mon, 12 September 2016, 10:03:28
Got it all fixed up. Just took walking away from it for a few to have that ah-ha moment! If anyone gets stuck feel free to message me on here or Reddit (same usernames) and I'd be happy to help any way I could.
Title: Re: RedScarfIII Manual (WIP)
Post by: Ryu on Mon, 12 September 2016, 21:45:44
Hey guys, if you have issue when importing RGB LED Fns for RSII+, perhaps you are choosing "RedScarfII" instead of the proper one "RedScarfII+" in the keyboard dropdown list.
And if you got "position mismatch" error, it often occurs with RSII+ Ver.C (a.k.a RS68), please try to add 2.25 offset to your keys as feralfoo mentioned.
Title: Re: RedScarfIII Manual (WIP)
Post by: livingspeedbump on Sun, 30 October 2016, 16:31:14
(working with an RS III 96 here)

You can easily get all of the lighting functions on the remote onto the RS by using the built-in-function option on TMK.

This is what it should look like after you are done (I'm using the "simple" layer, fyi)

(http://i.imgur.com/PCWBL4L.jpg)

My actual layout from KLE looks something like this:

(http://i.imgur.com/YdY373i.jpg)
Title: Re: RedScarfIII Manual (WIP)
Post by: ErectedLine on Fri, 13 January 2017, 22:04:25
Wondering if I might be able to get some help here. I got an RS68 II+ from Massdrop right after Christmas. I came home from work today after not using it for 4 days to find that it's broken as hell.

While using this layout
https://gyazo.com/d5f4a0981818a4a626a7b15aa0d93677


The backspace outputs \ and the \ doesn't do anything now
\ szdxfc
The backspace actually does 1 backspace then infinite \
sometimes doing as many as 5-7 at a time.
And most the keys still aren't working either
for example this is the number row
1q2w3e4r5t6y7u8i9o0p

Here's a picture of the backside of the PCB http://imgur.com/a/pc2wF I can't find any jumped pins, burned lanes, lifted pads or anything on it.

I have flashed it multiple times with that layout and no dice and hell I might've messed it up in the process by doing something wrong, but I'm ready to give up on the keyboard at this point. I'm wondering how I might be able to possibly reflash this back to basics so that I don't have to wait on MD to tell me to f*** off.

Any help would be greatly appreciated as I'm pretty upset that this board broke with under two weeks of use on it.

Title: Re: RedScarfIII Manual (WIP)
Post by: dotchoucou on Sun, 12 February 2017, 11:50:00
Hi,

I have a problem with my RS68 II+ rev C.

Both red keys on this layout does the same thing when I press them:
http://www.keyboard-layout-editor.com/#/gists/462f442185cbc90095344fe50ecc9261
i.e. the right one behaves like the left one although the layout as shown here is different.

Can anyone help?

PS: I also posted this question in other topics to have more chances of an answer. Sorry about that.
Title: Re: RedScarfIII Manual (WIP)
Post by: dotchoucou on Sun, 12 February 2017, 12:14:08
I answer to myself thanks to soilheart on another thread.
needed to use "iso |" in the layout.

Working now
Title: Re: RedScarfIII Manual (WIP)
Post by: Shinra on Sun, 02 April 2017, 11:19:36
Hi everyone.

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".
[attachimg=1]
In normal mode the keyboard is well detected as.. a keyboard.
[attachimg=2]
What should I do to recognize it properly as a printer ?

Thanks

Title: Re: RedScarfIII Manual (WIP)
Post by: SpAmRaY on Sun, 02 April 2017, 11:57:46
Hi everyone.

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
Did you hold escape while plugging it in?

(http://uploads.tapatalk-cdn.com/20170402/52371d97a5c2927d30a881a228b0f00a.jpg)
Title: Re: RedScarfIII Manual (WIP)
Post by: Checkfield on Sun, 02 April 2017, 12:13:44
Hi everyone.

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
Did you hold escape while plugging it in?

Show 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.
Title: Re: RedScarfIII Manual (WIP)
Post by: Shinra on Sun, 02 April 2017, 13:53:39
Hi everyone.

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
Did you hold escape while plugging it in?

Show 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.

Yes I hold escape. And then the keyboard is detected as "RedScarf HID EEPROM" instead of a printer. the led under caps lock is on. So the keyboard seems to be in EEP mode. What i don't know is why windows isn't showing me a printer.
When i plugged it in the first time with escape, instead of showing "Installing LUFA Printer Bootloader" it said me "Installing RedScarf HID EEPROM". I tried multiples USB ports but the "wrong" driver is always choosen.
Title: Re: RedScarfIII Manual (WIP)
Post by: twiddle on Tue, 04 April 2017, 19:37:24
Similar issue for me - it doesnt enumerate as a printer.
In fact, as can be seen here, it wont ever enumerate as a printer as it is showing as the wrong Device Class in the USB descriptors (interface class 0x03):
Code: [Select]
---===>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


I'd really like to just get things working using the actual HEX mode, but I can't find any information on how to actually program the device when it's in that mode either (it doesnt seem to be either dfu OR flip OR printer-based, though it occurs to me I should check if theres a HID based LUFA bootloader).


Edit: Right, so I worked out HEX mode. Yes, it does use the LUFA HID bootloader.

Instructions for using HEX mode for altering firmware or for people having trouble using the printer method:
(assuming MSYS2 on windows or equivalent for other OS, with avr-gcc installed on path or built/installed from source)
clone the tmk fork with RedscarfIII support:
Code: [Select]
$ git clone https://github.com/kairyu/tmk_keyboard_custom.gitenter repository
Code: [Select]
$ cd tmk_keyboard_custom/update submodules
Code: [Select]
$ git submodule init
$ git submodule update
enter redscarf folder
Code: [Select]
$ cd keyboard/RedScarfIII
make whatever changes you want to keymap_default.c

comment out KEYMAP_IN_EEPROM_ENABLE in the makefile
Code: [Select]
#KEYMAP_IN_EEPROM_ENABLE = yes # Read keymap from eepromrun make inside the RedScarfIII folder
Code: [Select]
$ make -f Makefiledownload the teensy loader CLI from
https://www.pjrc.com/teensy/loader_cli.html into the same folder

hold esc+f1 and connect the keyboard, then flash the device
Code: [Select]
$ teensy_loader_cli.exe  --mcu=atmega32u4 -w -v RedScarfIII_lufa.hexhold backspace+spacebar and reconnect keyboard, keep holding keys till you see spaces show up (ie eeprom has been cleared)
Enjoy.
Title: Re: RedScarfIII Manual (WIP)
Post by: khahk on Thu, 04 May 2017, 01:20:10
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"]
Title: Re: RedScarfIII Manual (WIP)
Post by: khahk on Thu, 04 May 2017, 01:31:08
Like it would be weird for two pads to not be working in different locations right? even the enter works (both the iso and ansi enter pads work)

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"]
Title: Re: RedScarfIII Manual (WIP)
Post by: SeedyOne on Tue, 06 June 2017, 02:49:29
I know this is an older, rarely updated thread but there's a lot of good information here. Thanks  :thumb:
Title: Re: RedScarfIII Manual (WIP)
Post by: asgeirtj on Tue, 09 January 2018, 03:24:04
I'm unable to control the RGB on my RS96 at all, It's just stuck on green RGB. I know I'm doing everything correctly since I have another RS96 which I can control the RGB on. Will reflashing the hex maybe fix this problem for me?
Title: Re: RedScarfIII Manual (WIP)
Post by: mike-y on Tue, 09 January 2018, 17:38:12
Will reflashing the hex maybe fix this problem for me?

That would be a good place to start.  re-flash the factory hex file and it should reset the keyboard back to that condition.  if that doesn't work, you can try to manually set your Fn key assignments for the RGB's with TMK. 

Title: Re: RedScarfIII Manual (WIP)
Post by: mankeroo on Wed, 07 November 2018, 19:38:58
Hey y'all.

I've had a working RS3 for over a year, but I recently built up some static electricity walking around the office and then shocked the board when my fingers got close. Now the left half of the board is acting weird. 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.

This means I cannot put my board into either REFLASH or EEPROM mode in order to attempt to reset it. Am I totally screwed or is there some other methodology that I can use to reset the firmware?  I'm getting pretty pessimistic :(
Title: Re: RedScarfIII Manual (WIP)
Post by: tinyprawn on Sat, 01 December 2018, 21:15:31
Sounds like your static electicity broke a diode on the PCB.  You may be able to use a multimeter in "diode check" mode to identify which one is bad and solder a replacement in.  They're very cheap, though surface mount stuff can be tricky.  Just check all the little guys in on the underside of the PCB that live in "D#" boxes.

I'd look around D19 through D23 or  D37 through D40ish.

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.