Easy AVR USB Keyboard Firmware and Keymapper

[metalliqaz]

Is F13-F24 still supported? I've tried using stable and beta builds with no luck.

It should be sending the scancodes for F13-F24.  They may not be supported by the operating system.

[burli]

I build two keyboards



Both have a splitted layout and currently I connected them with flat cables.



But I want to use an IO expander like the MCP23018 on the ErgoDox. How can I use this with this software?

[suicidal_orange]

I want to use an IO expander like the MCP23018 on the ErgoDox. How can I use this with this software?

None of the boards supported by this firmware use IO expanders so there is no way you're going to make it work unless metalliqaz makes a new binary.  He's currently doing a code tidy up before releasing the source so I don't think he'll be adding any new features anytime soon - your best bet would be to wire it up the same as the middle part of an ergodox and use TMK.

[dhoepp]

I read through a lot of the thread but I cannot find if anyone said the GH60/KC60 was tested and proved supported. Also, I need help on configuring the boot key. What do you guys normally do with the boot key. Also, can I use tkg-toolkit instead of teensy to load the .hex file? I am using a Mac.

[suicidal_orange]

Which GH60 do you have?  I have the final rev C from the group buy and it does not work with EasyAVR as the diodes are the wrong way round, so if that's what you have you're out of luck.  Previous versions surely worked else the option wouldn't be included so if you have an unknown Chinese "GH60" you might get lucky.

I've never used the boot key as I've always had a button on the Teensy/PCB which does the same job, but you're supposed to put it somewhere you won't hit by mistake, usually on a layer.

The output is a hex file so you can use whatever program you like to flash - I've used avrdude for an Arduino Micro and dfu-programmer for the GH60 and both work fine.

[metalliqaz]

Friggin GH60, I can't keep up with them.  Need to finish open source

[RavenII]

I read through a lot of the thread but I cannot find if anyone said the GH60/KC60 was tested and proved supported. Also, I need help on configuring the boot key. What do you guys normally do with the boot key. Also, can I use tkg-toolkit instead of teensy to load the .hex file? I am using a Mac.

KC60 isn't yet...diodes are reversed.

[ika]

Does anyone know if this works well on the Orion v2? I see that the original Orion has been well-tested but I'm not sure what is necessary to ensure that it works on the v2. I don't want to brick my keyboard or anything and I'm woefully inadequate when it comes to firmware-related things.

[metalliqaz]

Does anyone know if this works well on the Orion v2? I see that the original Orion has been well-tested but I'm not sure what is necessary to ensure that it works on the v2. I don't want to brick my keyboard or anything and I'm woefully inadequate when it comes to firmware-related things.

I think it is likely that it will work, except for the new LEDs.  However, if you aren't comfortable with the whole reprogramming thing, you may want to let someone else test it.

[metalliqaz]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

[regack]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

You're the best!

[suicidal_orange]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

No compiling?  I guess the only reason to look at the source will be if we think we can write more efficient code than you did so we can squeeze in another couple of macros )

Will be great to be able any "will this work?" with a yes though

[MOZ]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

Nice!

[whiskytango]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

Sounds awesome. Will we be able to use it for a hand wired board that uses something other than the phantom's 6x17 matrix? I want to handwire one with 105 keys and 3 lock leds.

[metalliqaz]

Yes

[MOZ]

Oh and support for the MCP23008 on Ergodox?

[metalliqaz]

It will be open source. You can try adding support if you want. Won't be easy

[fuszy]

ok so im pretty stumped got the easy keymap thing going got it coded, pins lined up but i cant get it to work for crap.....

Code: [Select]

[MATRIX]
ROW0=D7
ROW1=B4
ROW2=B4
ROW3=B6
COL1=F7
COL2=B0
COL3=B1
COL4=B2
COL5=B3
COL6=B7
COL7=D0
COL8=D1
COL9=D2
COL10=D3
COL11=C6
COL12=C7
LED0=D6
LED1=E6



i think its correct no clue about the LED pins

Code: [Select]

[Example]
# The example will be a 40% layout
# 40% uses only 12 columns of the 17, so get rid of leftmost and 4 rightmost
MAKE_SPACER(0, 0, 0)
MAKE_SPACER(1, 0, 0)
MAKE_SPACER(2, 0, 0)
MAKE_SPACER(3, 0, 0)
MAKE_SPACER(4, 0, 0)
MAKE_SPACER(5, 0, 0)
MAKE_SPACER(0, 13, 0)
MAKE_SPACER(1, 13, 0)
MAKE_SPACER(2, 13, 0)
MAKE_SPACER(3, 13, 0)
MAKE_SPACER(4, 13, 0)
MAKE_SPACER(5, 13, 0)
MAKE_SPACER(0, 14, 0)
MAKE_SPACER(1, 14, 0)
MAKE_SPACER(2, 14, 0)
MAKE_SPACER(3, 14, 0)
MAKE_SPACER(4, 14, 0)
MAKE_SPACER(5, 14, 0)
MAKE_SPACER(0, 15, 0)
MAKE_SPACER(1, 15, 0)
MAKE_SPACER(2, 15, 0)
MAKE_SPACER(3, 15, 0)
MAKE_SPACER(4, 15, 0)
MAKE_SPACER(5, 15, 0)
MAKE_SPACER(0, 16, 0)
MAKE_SPACER(1, 16, 0)
MAKE_SPACER(2, 16, 0)
MAKE_SPACER(3, 16, 0)
MAKE_SPACER(4, 16, 0)
MAKE_SPACER(5, 16, 0)
# 40% uses only 4 columns of the 6, so get rid of the last 2 rows
MAKE_SPACER(5, 1, 0)
MAKE_SPACER(5, 2, 0)
MAKE_SPACER(5, 3, 0)
MAKE_SPACER(5, 4, 0)
MAKE_SPACER(5, 5, 0)
MAKE_SPACER(5, 6, 0)
MAKE_SPACER(5, 7, 0)
MAKE_SPACER(5, 8, 0)
MAKE_SPACER(5, 9, 0)
MAKE_SPACER(5, 10, 0)
MAKE_SPACER(5, 11, 0)
MAKE_SPACER(5, 12, 0)
MAKE_SPACER(5, 13, 0)
MAKE_SPACER(5, 14, 0)
MAKE_SPACER(4, 1, 0)
MAKE_SPACER(4, 2, 0)
MAKE_SPACER(4, 3, 0)
MAKE_SPACER(4, 4, 0)
MAKE_SPACER(4, 5, 0)
MAKE_SPACER(4, 6, 0)
MAKE_SPACER(4, 7, 0)
MAKE_SPACER(4, 8, 0)
MAKE_SPACER(4, 9, 0)
MAKE_SPACER(4, 10, 0)
MAKE_SPACER(4, 11, 0)
MAKE_SPACER(4, 12, 0)
MAKE_SPACER(4, 13, 0)
MAKE_SPACER(4, 14, 0)

# make 2nd row
MAKE_KEY(1, 1, 5, 4)
MAKE_SPACER(1, 11, 0)
MAKE_KEY(1, 12, 7, 4)
# make 3rd row
MAKE_KEY(2, 1, 7, 4)
MAKE_SPACER(2, 2, 0)
MAKE_KEY(2, 11, 5, 4)
# make bottom row
MAKE_KEY(3, 1, 5, 4)
MAKE_SPACER(3, 3, 0)
MAKE_SPACER(3, 5, 0)
MAKE_SPACER(3, 6, 0)
MAKE_KEY(3, 7, 25, 4)
MAKE_SPACER(3, 8, 0)
MAKE_SPACER(3, 9, 0)
MAKE_SPACER(3, 10, 0)
MAKE_KEY(3, 11, 5, 4)
MAKE_KEY(3, 12, 5, 4)
someone halp?

i checked most of the connections for shorts and stuff but nothing...or it spams all the buttons or just the bottom row when not touching anything.....now i cant get it NOT to be pressing buttons even though i tested all the soldering and wiring....

[suicidal_orange]

ok so im pretty stumped got the easy keymap thing going got it coded, pins lined up but i cant get it to work for crap.....

Code: [Select]

[MATRIX]
ROW0=D7
ROW1=B4
ROW2=B4
ROW3=B6
COL1=F7
COL2=B0
COL3=B1
COL4=B2
COL5=B3
COL6=B7
COL7=D0
COL8=D1
COL9=D2
COL10=D3
COL11=C6
COL12=C7
LED0=D6
LED1=E6



i think its correct no clue about the LED pins

Code: [Select]

[Example]
# The example will be a 40% layout
# 40% uses only 12 columns of the 17, so get rid of leftmost and 4 rightmost
MAKE_SPACER(0, 0, 0)
MAKE_SPACER(1, 0, 0)
MAKE_SPACER(2, 0, 0)
MAKE_SPACER(3, 0, 0)
MAKE_SPACER(4, 0, 0)
MAKE_SPACER(5, 0, 0)
MAKE_SPACER(0, 13, 0)
MAKE_SPACER(1, 13, 0)
MAKE_SPACER(2, 13, 0)
MAKE_SPACER(3, 13, 0)
MAKE_SPACER(4, 13, 0)
MAKE_SPACER(5, 13, 0)
MAKE_SPACER(0, 14, 0)
MAKE_SPACER(1, 14, 0)
MAKE_SPACER(2, 14, 0)
MAKE_SPACER(3, 14, 0)
MAKE_SPACER(4, 14, 0)
MAKE_SPACER(5, 14, 0)
MAKE_SPACER(0, 15, 0)
MAKE_SPACER(1, 15, 0)
MAKE_SPACER(2, 15, 0)
MAKE_SPACER(3, 15, 0)
MAKE_SPACER(4, 15, 0)
MAKE_SPACER(5, 15, 0)
MAKE_SPACER(0, 16, 0)
MAKE_SPACER(1, 16, 0)
MAKE_SPACER(2, 16, 0)
MAKE_SPACER(3, 16, 0)
MAKE_SPACER(4, 16, 0)
MAKE_SPACER(5, 16, 0)
# 40% uses only 4 columns of the 6, so get rid of the last 2 rows
MAKE_SPACER(5, 1, 0)
MAKE_SPACER(5, 2, 0)
MAKE_SPACER(5, 3, 0)
MAKE_SPACER(5, 4, 0)
MAKE_SPACER(5, 5, 0)
MAKE_SPACER(5, 6, 0)
MAKE_SPACER(5, 7, 0)
MAKE_SPACER(5, 8, 0)
MAKE_SPACER(5, 9, 0)
MAKE_SPACER(5, 10, 0)
MAKE_SPACER(5, 11, 0)
MAKE_SPACER(5, 12, 0)
MAKE_SPACER(5, 13, 0)
MAKE_SPACER(5, 14, 0)
MAKE_SPACER(4, 1, 0)
MAKE_SPACER(4, 2, 0)
MAKE_SPACER(4, 3, 0)
MAKE_SPACER(4, 4, 0)
MAKE_SPACER(4, 5, 0)
MAKE_SPACER(4, 6, 0)
MAKE_SPACER(4, 7, 0)
MAKE_SPACER(4, 8, 0)
MAKE_SPACER(4, 9, 0)
MAKE_SPACER(4, 10, 0)
MAKE_SPACER(4, 11, 0)
MAKE_SPACER(4, 12, 0)
MAKE_SPACER(4, 13, 0)
MAKE_SPACER(4, 14, 0)

# make 2nd row
MAKE_KEY(1, 1, 5, 4)
MAKE_SPACER(1, 11, 0)
MAKE_KEY(1, 12, 7, 4)
# make 3rd row
MAKE_KEY(2, 1, 7, 4)
MAKE_SPACER(2, 2, 0)
MAKE_KEY(2, 11, 5, 4)
# make bottom row
MAKE_KEY(3, 1, 5, 4)
MAKE_SPACER(3, 3, 0)
MAKE_SPACER(3, 5, 0)
MAKE_SPACER(3, 6, 0)
MAKE_KEY(3, 7, 25, 4)
MAKE_SPACER(3, 8, 0)
MAKE_SPACER(3, 9, 0)
MAKE_SPACER(3, 10, 0)
MAKE_KEY(3, 11, 5, 4)
MAKE_KEY(3, 12, 5, 4)
someone halp?

i checked most of the connections for shorts and stuff but nothing...or it spams all the buttons or just the bottom row when not touching anything.....now i cant get it NOT to be pressing buttons even though i tested all the soldering and wiring....

If the pins are right and your diodes are the right way round it will work, so one of these must be wrong.  Without pics it's impossible for anyone to say which though, so - pics please

Also are you using the beta version or the "latest version"?  It's been a while so I don't remember what changed, but the beta is better for handwire so try that if you haven't already.

[metalliqaz]

Sounds like diodes wrong direction. Wait for eaosp

[fuszy]

http://imgur.com/NB86ujl  i think they are all backwards so im starting to work on editing the gh60 from TMK

[metalliqaz]

By the way, the open source project is coming along.  I have made several of the planned changes and I keep making progress.  If my plans pan out, then the resulting code will be totally general purpose and all your keyboards will be supported.  Adding new boards will only require changing python code and/or config files (i.e. no compiling!)

This is a lofty goal but I think I've cracked it.  I've gone through many redesigns and I've made a lot of progress.  My CompactTKL is working, now I have to debug other boards and then upgrade the keymapper to work with the new firmware.  That will take a while.  I can finally see the finish line, though.

[MOZ]

That is great news!

[FletchINKy]

Great to hear. Will the CompactTKL add support for the newer ergodox builds?

I'm finding myself hardpressed to get the macro and mouse features Easy AVR adds so easily to the supported chips vs the other TKL types, which add layers of keys and not much else.

Also, the first posts included ergodox layouts, which seem to be gone from the current release (unless I'm missing the default layout somewhere in the list). Did this support end? If not, is there a chip selection of ergodox that will support all the features I enjoy with your software on a frosty flake?

Sorry if this information is available somewhere, I couldn't find much googling around the usual forums.

[metalliqaz]

The software does not currently support the Ergodox because it doesn't support the MCP23008 that drives the half-to-half connection.  The primary reason I haven't supported Ergodox is because I don't own one.  Without being able to debug, I have no hope of getting it working.

I am currently working on an overhaul of the EasyAVR code leading up to open-sourcing the project.  Once I'm done, a talented programmer could take up the cause and work with me to contribute Ergodox support.  I can't predict if that will happen or not.

[metalliqaz]

Oh, forgot to mention: the newest "ergodox", the Infinity, uses an ARM processor.  The AVR code will never work on it.

[FletchINKy]

If the MCP23018 communication is the issue, couldn't I use a MCP23017 to de-I2C the remote side to regular GPIO to a teensy on a hand wired layout?

The graphical layout would look a little funky to maintain the matrix, but wouldn't that make the teensy ergodox work?

[metalliqaz]

I think this will finally be uploaded to Github this weekend or maybe next week.  The firmware is so much better now; I can't believe I waited this long to make these changes.

The way it works is you first pick a build to use, from 3 parameters:
Device (ATmega32U4, etc.)
Speed (16MHz or 8MHz)
Size (Costar, TKL, 60%, Pad, Card)
The smaller sizes leave more room in memory for other features.

So if you wanted to add support for your handwired board, you'd select ATmega32U4-16MHz-TKL

Then you have to capture the physical characteristics of your board in a Python config file.  It's a bunch of declarations that specify the IO pins to use for the matrix, what order to use them, what pins to use for LEDs, and especially the layout of the keys.  It's a lot to capture and it takes a while, but once it's done it's done and you don't have to do any programming.

Then you just run the tool as usual.

I need to test it on the boards I own and port the rest of the other boards.  That will take a while.  I'm almost there though.  Looking forward to showing off the code.  There's still some crumby, embarrassing code in there but it was put in for pragmatic reasons, so whatever.

[regack]

I think this will finally be uploaded to Github this weekend or maybe next week.  The firmware is so much better now; I can't believe I waited this long to make these changes.

...

Fantastic, I'm excited to try this out on all of my oddball one-off stuff. 

[FletchINKy]

Awesome! Can't wait to start digging into it!

[metalliqaz]

Yeah it's pretty cool.  For example, it no longer matters which direction you put in your diodes.  You just have to set two parameters:

The first tells the firmware to either strobe rows/sense columns or strobe columns/sense rows.
The second tells the firmware to sense low for key=pressed or high for key=pressed

[metalliqaz]

Well it's working now on all my boards.  I have re-licensed all of it as GPLv2 and put it on Github.

I still have to make a package for users to download and I have lots of developer documentation to write, but finally made it.  *whew*

[suicidal_orange]

Awesome!  I shall download it as soon as I find the link...

[metalliqaz]

Awesome!  I shall download it as soon as I find the link...

Link is in OP.

https://github.com/dhowland/EasyAVR

Python 3.3 or later is now REQUIRED.  Just get Python 3.5.

[iss]

Looks amazing- thanks so much for this, metalliqaz.

[suicidal_orange]

Awesome!  I shall download it as soon as I find the link...

Link is in OP.

https://github.com/dhowland/EasyAVR

Python 3.3 or later is now REQUIRED.  Just get Python 3.5.

That's far too clever, found it on the previous page

Lots of interesting source to look through some other time, but for today I just wanted to have a play with the keymapper. 


It didn't want to load if there isn't a layout in the configs so I made blanks then reinstalled and all good - these should get Linux users going, just complete the path and change python 3.4 to your version

Code: [Select]

cd /PATH/TO/EasyAVR-master/keymapper/easykeymap/configs
touch smallfry.cfg octagon.cfg tau.cfg epsilon.cfg techcard.cfg zeta.cfg atreus.cfg SIGMA.cfg
cd ../..
sudo python3.4 setup.py install
This installs easykeymap which looks very familiar!


Thanks metalliqaz, I'll try and get my GH60revC working tomorrow then work out how to add it officially

[metalliqaz]

the .cfg files weren't included?  That's strange... they're in the repository

[metalliqaz]

the .cfg files weren't included?  That's strange... they're in the repository

Oh wait, those don't have configs.  Man, they shouldn't be needed.  Probably growing pains related to setuptools.  I don't have that problem over here, though

[suicidal_orange]

the .cfg files weren't included?  That's strange... they're in the repository

Oh wait, those don't have configs.  Man, they shouldn't be needed.  Probably growing pains related to setuptools.  I don't have that problem over here, though

Setuptools ran fine without them but I couldn't start easykeymap as it errored mentioning a seemingly random .cfg each time, so it was run, create .cfg, reinstall [repeat until it stopped complaining] then it worked fine.

If you need system info let me know, it could be a new feature in python 3.5?  Doesn't sound likely though...

[metalliqaz]

Ok got it I'll fix.  It's because you installed it. Packaging isn't finished yet.

[regack]

Is there a way to vertically stagger columns?  I see I can put 1-3+ space between one row and another, but not offset just a single column.  Looking at the Atreus, I see that layout is lined up without the stagger, so I assume you don't have that in as a feature, but I thought I would check anyway.  It's obviously not necessary, just trying to see how close to the physical layout I can actually make it appear.  The outer two columns in my pad here would be vertically offset by '2'. 


Either way, I just wanted to say thank you for releasing this.  I'm stuck inside with 20 inches of snow outside, so this is a great time to play around

[metalliqaz]

Yes, you can.  The formatting of the layout grew organically as I added support for more boards, so it is insane and hard to figure out.  But you can.  Check the ISO layouts of things like the Phantom.

Edit: actually, that depends on what you mean by staggering.  You can make long vertical keys, but I didn't add anything for offsetting a whole column.  This is due to the windowing kit.  It likes to layout things in a grid.

Sorry for no documentation, I will hopefully get it done at some point in the future.

[metalliqaz]

the .cfg files weren't included?  That's strange... they're in the repository

Oh wait, those don't have configs.  Man, they shouldn't be needed.  Probably growing pains related to setuptools.  I don't have that problem over here, though

Setuptools ran fine without them but I couldn't start easykeymap as it errored mentioning a seemingly random .cfg each time, so it was run, create .cfg, reinstall [repeat until it stopped complaining] then it worked fine.

If you need system info let me know, it could be a new feature in python 3.5?  Doesn't sound likely though...

By the way, the reason I haven't finished packaging yet is because of updating.  Say you want to add a new target for the GH60revc, right?

So first you take your code, copy the boards/gh60.py to boards/gh60c.py, and add it to the boards/__init__.py file.  Then you update the parameters just the way it's needed, and get it to work.  Great.

But if you don't issue a pull request to get it into the master, then on the next release you will erase all your work if you do an update.  (update = uninstall, install)

I haven't put any system in for user add-ins.  For the time being, I've still be running it directly from a source download without installing.  That is why I don't get the errors.

Any suggestions are welcome.

[suicidal_orange]

Any suggestions are welcome.

From a user perspective it would be nice to have an overlay directory (userboards?) with a second __init__.py listing custom boards which are stored in that folder.  Looking in the main one in it's just storing an array so this sounds easy enough?  Though if the update wipes the root of EasyAVR it will probably take this folder down with it.

Perhaps you could add a second list of boards which came with the download and before doing the update it moves any .py's not in that list elsewhere, updates everything else, then puts them back?

Apparently I can't get Python 3.3+ on my netbook without some serious updating, so I'm trying to kick that off before grabbing some food...

[metalliqaz]

What I'd like to do is to have a directory in the user's home directory that overlays the installation, so there would be a ~/easyavr/boards and ~/easyavr/configs, etc.  Then use importlib to load them at run time.  We'll see

[suicidal_orange]

That sounds perfect

Time to see how "Easy" this new version is!

Edit - tried to build the GH60 "all keys" variant as it shipped to confirm it compiles before I mess with it but got this error message.  It's the same whether if I use the installed version or the one in the source(ish) folder

Can't build binary:
Error: 'int' object is not iterable

Any thoughts?

[regack]

Yes, you can.  The formatting of the layout grew organically as I added support for more boards, so it is insane and hard to figure out.  But you can.  Check the ISO layouts of things like the Phantom.

Edit: actually, that depends on what you mean by staggering.  You can make long vertical keys, but I didn't add anything for offsetting a whole column.  This is due to the windowing kit.  It likes to layout things in a grid.

Sorry for no documentation, I will hopefully get it done at some point in the future.

Documentation is the hardest part of anything, don't worry about it.  It just took some tinkering to figure out what changed what.   Anyway, thanks for the hints, I was wondering if it was partially in tcl/tk... that's what seemed to be complaining when I tried using non-integers, 0, and negative values .  Anyway, I played around with it some more, and since the layout is actually tied to functionality I'll just leave it be.  It's purely cosmetic anyway.  I did make some crazy looking things though, when playing around with it.  If you're curious, I was trying to do something like this:

[metalliqaz]

That sounds perfect

Time to see how "Easy" this new version is!

Edit - tried to build the GH60 "all keys" variant as it shipped to confirm it compiles before I mess with it but got this error message.  It's the same whether if I use the installed version or the one in the source(ish) folder

Can't build binary:
Error: 'int' object is not iterable

Any thoughts?

Ah, yes.  GH60 is unique in that it only has 1 LED.  bl_modes is supposed to be a list of tuples.  Python won't make a tuple unless there is a comma somewhere between the parens.  Should be like this.

bl_modes = [
    ( 0, ),
    ( 1, )
]

My bad.

[suicidal_orange]

That sounds perfect

Time to see how "Easy" this new version is!

Edit - tried to build the GH60 "all keys" variant as it shipped to confirm it compiles before I mess with it but got this error message.  It's the same whether if I use the installed version or the one in the source(ish) folder

Can't build binary:
Error: 'int' object is not iterable

Any thoughts?

Ah, yes.  GH60 is unique in that it only has 1 LED.  bl_modes is supposed to be a list of tuples.  Python won't make a tuple unless there is a comma somewhere between the parens.  Should be like this.

bl_modes = [
    ( 0, ),
    ( 1, )
]

My bad.

I see!  Well the  rev C has 4 pins for LEDs so I guess I should start tweaking and see how it goes.

The JD40 on the other hand does only have one LED, and that currently gives the same error.

[_skeletontoucher]

Getting into modding my Planck. I've got a couple questions:

- Should I use the R_Shift or LED_Dimmer for adjusting the backlight intensity? The reason I ask is because the stock settings on my Planck have the LED key modifying the intensity, but also allowing shift functions.

- Is there a way to split the shift functions of the keys? I want to make my lower layer top row the shift+num symbols (!,@,#,$...) and my raised layer top row just the numbers. Currently, I can only see that you can add them both as they would normally appear, combined with shift modifying for symbols. Same goes for brackets and a few other keys.

- Is layer 2 the same as Fn2? The radial buttons at the top start with Fn1 and then go forward with Layer 2, 3 and so on. I just want to make sure I'm not missing something.

Thanks for any help!