How much programmability do you want out of your keyboards?

[Kamen Rider Blade]

Some people want fully programmable where they can rebind each key

Some people only care about a few dedicated macro keys being programmable

Some people don't like programmable keyboards and would rather just have a simple keyboard.


Where do you folks fall on this spectrum?

[demik]

D) All of the above

[FoxWolf1]

Needs a "more" option.

I wouldn't consider just binding keys to different inputs/macros to be much power by way of "programmability". You start getting a lot more potential when you unlock both sides of the keypress gotten : keypress sent equation, not just the right side.

[StylinGreymon]

Full layout programmability is very much desired.
I wish the Poker II had a way to move the Fn switch to Caps Lock, so I could get something like this:

[hasu]

Need only decent C compiler tool chain and flash tool!

[gh_pp]

fully programmable include macro keys placement

i want a hardware key that can send { } without pressing shift

[daerid]

Full. Firmware hackable and open source.

[Macsmasher]

Fully programmable.

In addition to being Colemak, I currently have AutoHotkey scripts running to swap certain keys. All that works great at the office. It's when I'm remote that everything becomes a pain in the butt. I want a board that has all keyboard snob crap configured at the hardware level in the keyboard.

[HPE1000]

Fully programmable, why not. With a program that lets you reprogram it at a hardware level, no stupid software like razer synapse.

[Grendel]

Need only decent C compiler tool chain and flash tool!

^^ This !

[tbc]

2 primary layers with a rather ridiculous layer switcher (like 10-key combo even)

each layer has an fn layer

the location of the fn button is customizable

each key can be configured to run a macro


why?  I want two layers because I want one as 'normal mode' to use on my workstation where i will have software remapping to convert non-programmable keyboards to my preferred layout.

the second layout is set to my preferred layout to use on OTHER people's machines so I can use my preferred layout without any software help.

that's really all I need personally.

[Hull]

I will be perfectly honest and say:

There can not be enough options. It is not a good thing to forbid any option. However, the most beautiful end result with the fewest options are often the best ones, yet not necessarily the most sought after.

I would like a keyboard that is fully modular but still seamless, for every keycap, material, special properties and color. If I wanted to build a 15 programmable, edible jello key, LED backlit, keyboard in the shape of a pink elephant with blue dots that also floats on water and cures cancer, it should be possible to do so. That said, the harder the options are to obtain and combine, the more we are willing to pay for the end result.

So yes, full programmability as an option, but not a necessary one.

[Kamen Rider Blade]

Needs a "more" option.

I wouldn't consider just binding keys to different inputs/macros to be much power by way of "programmability". You start getting a lot more potential when you unlock both sides of the keypress gotten : keypress sent equation, not just the right side.

I was thinking along the same lines, Key down, <arbitrary time delay>, Key up level of programmability, add mouse inputs, move mouse cursor to predefined position.

What level of programmability are you thinking about.

One button launch program?

I'm curious as to what level of detail you're going for?

[kod]

Yeah, I want completely arbitrary programmability, not just remaps or macros.

[IvanIvanovich]

Mostly the biggest problem I see against offering 100% programability is having an easy to use utility to use for that. Of the few commercially available fully programmable keyboard the utility supplied is terrible, annoying to use and 99% of the time won't even work on 64bit OS. If it is going to be programmable, it might as well be 100% user programmable. I don't see much point in only allow a few keys to be user assignable. It also must be stored in the keyboard always. None of that shonky OS side cloud profile bull****.

[Kamen Rider Blade]

Mostly the biggest problem I see against offering 100% programability is having an easy to use utility to use for that. Of the few commercially available fully programmable keyboard the utility supplied is terrible, annoying to use and 99% of the time won't even work on 64bit OS. If it is going to be programmable, it might as well be 100% user programmable. I don't see much point in only allow a few keys to be user assignable. It also must be stored in the keyboard always. None of that shonky OS side cloud profile bull****.

I don't get why Razer needs Cloud drivers, the only thing I can think of is they're profitting off the information for marketing purposes.
As for OS level drivers, that's usually not too bad if done correctly.

The recent Logitech Gaming Software is pretty decent for that purpose.

They're far from perfect, but a step in the right direction.

[tricheboars]

teensy 2.0 ftw

[Findecanor]

As for OS level drivers, that's usually not too bad if done correctly.

That is not as usable if you swap your keyboards, or move them around between different machines.

A problem with the Teensy 2.0 and the AVR µ-controller in it is that it has such little RAM and user-accessible EEPROM that could be used for remapping and macros, only 2.5 and 1 kilobyte respectively.
It does have a lot more program memory, where the keymap is usually stored, but the normal procedure is to reflash that all at once.

[mooswa]

Fully programmable for me.  For now, I am happy with AVR but in the future I hope to have a keyboard with a slot for Intel's Edison or something like it.

[Kamen Rider Blade]

https://www.pjrc.com/teensy/

Teensy 3.1

Seems like a huge step up compared to 2.0

[Snarfangel]

Take a guess:

 )

[tuxsavvy]

Needs more options,

For people to add even more functionality to their average keyboard. Imagine those who have always loved a specific keyboard but wished it were wireless? An open and customisable firmware basically defines the sky as the limit. Besides one will end up with a totally tailor made keyboard at the end of it all.

The standard keyboard controllers can only do nothing more than capture keycodes and pass them onto the machine, these days gaming mechanical keyboards boasting programmability as well as NKRO function have (rather insane) specifications on the controller. Something like ARM Cortex chipsets. Those ARM Cortex chipsets are known to be popular in the handheld arena such as smartphones. Imagine those beasts powering just a keyboard.

Last but not least, this seems to be a feature that I somewhat desire (a pipe dream really) is the idea of a keyboard with soemthing like how MX RGB works but is programmed to remind one of the layout one is using. Optimus maximus (and now Optimus has those polaris series) are really expensive keyboards with OLED on each and every key. The idea is nice albeit expensive but can be used to serve those whom needs legends on their keys to remind them what the key's own functionality is. So on a cheap man's alternative without saving to go for an Optimus keyboard is to have something like MX RGB backlit keyboards that shine different LED and to also remind one of the layout specific to that LED colour. Think of µTron with a LED that either lits up or not if you are in Tron mode which is essentially Dvorak as opposed to QWERTY. Something like that with MX RGB backlighting that can be tailored to light up a certain colour to remind one instead the layout that it is in without having to see the little LED on top right for instance.

[Pacifist]

https://www.pjrc.com/teensy/

Teensy 3.1

Seems like a huge step up compared to 2.0

iirc teensy 3 uses different firmware than 2.0 which is why no one here has used it much

[Kamen Rider Blade]

https://www.pjrc.com/teensy/

Teensy 3.1

Seems like a huge step up compared to 2.0

iirc teensy 3 uses different firmware than 2.0 which is why no one here has used it much

Somebody has to start at some point, the specs on that controller is beastly compared to Teensy 2.0

[Kamen Rider Blade]

Take a guess:
(Attachment Link)
 )

What the heck is that beastly keyboard?

[Snarfangel]

Take a guess:
(Attachment Link)
 )

What the heck is that beastly keyboard?

It's a Cherry G86-63400 SPOS keyboard. I'm going to use it to play around with key configurations. Rubber dome, sadly, but cheap enough, and supposedly built for spills and harsh environments. Here's a link (though I got a beige one off of Ebay): http://www.cherrycorp.com/english/keyboards/pos/SPOS_Rows_Columns/index.htm

[Fullcream]

Completely content without any programmability. I'm strange

[jacobolus]

Some people want [...]
   fully programmable where they can rebind each key [...]
   a few dedicated macro keys being programmable [...]
   just [to] have a simple keyboard.

All of these are insufficient. I want:

(1) Fully programmable keyboard + some kind of mouse/trackpad/trackball input fed into the same controller.
(2) Based on some kind of state machine w/ mostly declarative syntax to define the behavior, and state transitions on key down / key up
(3) ... This then allows arbitrary chording to be linked to arbitrary actions
(4) Some macro recording capability so that new macros can be created on the fly at run-time.
(5) Some software support from the computer side to add things like a "Leap" key, and ideally some better ways to navigate computer menus, etc.

[Kamen Rider Blade]

Some people want [...]
   fully programmable where they can rebind each key [...]
   a few dedicated macro keys being programmable [...]
   just [to] have a simple keyboard.

All of these are insufficient. I want:

(1) Fully programmable keyboard + some kind of mouse/trackpad/trackball input fed into the same controller.
(2) Based on some kind of state machine w/ mostly declarative syntax to define the behavior, and state transitions on key down / key up
(3) ... This then allows arbitrary chording to be linked to arbitrary actions
(4) Some macro recording capability so that new macros can be created on the fly at run-time.
(5) Some software support from the computer side to add things like a "Leap" key, and ideally some better ways to navigate computer menus, etc.

What is a "Leap Key"?

[steve.v]

The more I can do with a keyboard, the better I guess. I would like to be able to remap certain keys; especially being a colemak user I like having the capslock key act as the delete key. Speaking of which, is the LED version of the POKER II fully programmable? I'm thinking of buying one.

This is the site http://mechanicalkeyboards.com/shop/index.php?l=product_detail&p=656

[StylinGreymon]

In terms of software, I think Linux compatibility is a must.
I hate not being able to use my Logitech g500 to its full capabilities because of their lack of Linux support.

[jacobolus]

What is a "Leap Key"?

There’s a brief description at https://en.wikipedia.org/wiki/Archy#Leaping

But I recommend reading Jef Raskin’s book *The Humane Interface* to really get an idea where he’s coming from.

[spiceBar]

Some people want fully programmable where they can rebind each key

Some people only care about a few dedicated macro keys being programmable

Some people don't like programmable keyboards and would rather just have a simple keyboard.


Where do you folks fall on this spectrum?

On a TKL or full size keyboard, I find that I don't need much programmability.

On a 60% (or around that size), full programability is really needed: many keys are missing and so their functions must be accessible thru some kind of "Fn key" and "Fn layers". There is absolutely no consensus on this, which means everyone would like to do it his own way.

The keyboard must be fully programmable so nothing needs to be installed on the computer.

By fully programmable I mean something like what Hasu's firmware offers. You can do almost anything with it. No offense intended to other available firmware like Soarer's, which I have not tried yet: they may be suitable as well.

The required Atmega controller is cheap, Hasu's firmware is open source and has been proven time and time again.

I understand a manufacturer may be reluctant to allow their users to reflash their keyboards (it's not a fool proof operation), so at this time they just allow limited remapping, like on the Poker II. It's a step in the right direction, but it's not enough.

With some efforts, they could provide a set of preprogrammed layouts for Hasu's firmware, with an editor allowing for simple changes in the layout. This could be OK for the average user. Just select your base layout, adapt it a little bit and reflash your keyboard. They need to provide a reflash tool for Windows, Mac and Linux. It may not be really straightforward, but I believe open source utilities exist for all these platforms, so it could be done without the manufacturer having to pay license fees.

The advanced user could, at his own risk, use Hasu's source code and make any change, implementing very advanced layouts. For me that would be the perfect solution.

The extreme and simplest solution would be this, and it can be done now:
- The manufacturer creates a keyboard based on the Atmega controller (one that is supported by Hasu's firmware).
- The keyboard is sold with a fixed layout. This does not even require that it has Hasu's firmware.
- The manufacturer releases the technical data needed to create a variant of Hasu's firmware for it.
- The user can, out of warranty, reflash the keyboard with Hasu's firmware and do whatever he wants.

That's what Tex should do with their new "Yoda" keyboard, instead of releasing it with a broken layout. Aha, too late, they have already designed a PCB that includes a non-programmable controller. What a waste!

[spiceBar]

The more I can do with a keyboard, the better I guess. I would like to be able to remap certain keys; especially being a colemak user I like having the capslock key act as the delete key. Speaking of which, is the LED version of the POKER II fully programmable? I'm thinking of buying one.

This is the site http://mechanicalkeyboards.com/shop/index.php?l=product_detail&p=656

It is programmable, but you cannot do anything.

BTW, the backlit and non-backlit versions are identical in this regard.

Yes, you can remap CapsLock to to Delete. Something you cannot do is remap CapsLock to something and Shift+CapsLock to something else for example. If you remap CapsLock to Delete, Shift+CapsLock will simply do Shift+Delete.

However you can remap a key to something, and Fn+this key to something else.

So the Poker II is programmable and offers some flexibility, but beware that you cannot do anything. You may run into annoying cases. Or it may simply work for you.

[StylinGreymon]

The extreme and simplest solution would be this, and it can be done now:
- The manufacturer creates a keyboard based on the Atmega controller (one that is supported by Hasu's firmware).
- The keyboard is sold with a fixed layout. This does not even require that it has Hasu's firmware.
- The manufacturer releases the technical data needed to create a variant of Hasu's firmware for it.
- The user can, out of warranty, reflash the keyboard with Hasu's firmware and do whatever he wants.

That's what Tex should do with their new "Yoda" keyboard, instead of releasing it with a broken layout. Aha, too late, they have already designed a PCB that includes a non-programmable controller. What a waste!

Yeah, I can't understand the reasoning behind a 60% with no programmability.
It reeks of "we know better than our users".

[StylinGreymon]

So the Poker II is programmable and offers a some flexibility, but beware that you cannot do anything. You may run into annoying cases. Or it may simply work for you.

Tell me about it.
Why can't I make my Caps Lock an additional Fn key?
Why is Caps Lock even a dedicated key on a 60% keyboard?

[spiceBar]

So the Poker II is programmable and offers a some flexibility, but beware that you cannot do anything. You may run into annoying cases. Or it may simply work for you.

Tell me about it.
Why can't I make my Caps Lock an additional Fn key?
Why is Caps Lock even a dedicated key on a 60% keyboard?

You can. This involves soldering wires on the PCB.

I'm half joking here. I have soldered wires on my Poker X PCB in order to remap the Fn key to a key I could intercept in software.

But obviously, the real solution is a keyboard that would accept a firmware like Hasu's.

[StylinGreymon]

I'm half joking here. I have soldered wires on my Poker X PCB in order to remap the Fn key to a key I could intercept in software.

I can't even begin to imagine how to do that. 

[angelic_sedition]

I want everything currently possible with software and everything that people have yet  to think up.
Give me total control over every key, at least 30 layers, builtin key chaining/ use of prefix keys to infinite depth (built in modality), assignment of macros of (nearly) unlimited length,  and the ability for every key to serve as both a modifier and a normal key (normal output on release, use as modifier for chording after held down for a certain period of time to prevent accidental chords). Until then I shall not be satiated.

To the best of my knowledge, most of this isn't currently possible.

By fully programmable I mean something like what Hasu's firmware offers. You can do almost anything with it. No offense intended to other available firmware like Soarer's, which I have not tried yet: they may be suitable as well.

Can Hasu's firmware do this?

What is a "Leap Key"?

There’s a brief description at https://en.wikipedia.org/wiki/Archy#Leaping

But I recommend reading Jef Raskin’s book *The Humane Interface* to really get an idea where he’s coming from.

Poor man's vim? A cool idea, but unless I'm missing something, this doesn't seem all that useful.

[spiceBar]

I want everything currently possible with software and everything that people have yet  to think up.
Give me total control over every key, at least 30 layers, builtin key chaining/ use of prefix keys to infinite depth (built in modality), assignment of macros of (nearly) unlimited length,  and the ability for every key to serve as both a modifier and a normal key (normal output on release, use as modifier for chording after held down for a certain period of time to prevent accidental chords). Until then I shall not be satiated.

To the best of my knowledge, most of this isn't currently possible.

By fully programmable I mean something like what Hasu's firmware offers. You can do almost anything with it. No offense intended to other available firmware like Soarer's, which I have not tried yet: they may be suitable as well.

Can Hasu's firmware do this?

I'm not to totally sure about it because I'm not sure I understand all that you want. Also I'm not sure Hasu has already implemented the things that people have yet to think of, because he is good but maybe not that good.

But Hasu's firmware does allow all of what I understand you want, like dual modifier keys, a large number of layers (I don't remember if it's 16 or 32 because the number just seemed more than enough for me), Fn keys embedded in Fn layers, and so on…

I would say that if Hasu's firmware is not enough for your needs, I would be interested to learn what you need that could be really useful and that Hasu has not yet implemented.

You have a crude list of features here:
  https://github.com/tmk/tmk_keyboard/blob/master/README.md

[angelic_sedition]

I'm not to totally sure about it because I'm not sure I understand all that you want. Also I'm not sure Hasu has already implemented the things that people have yet to think of, because he is good but maybe not that good.

But Hasu's firmware does allow all of what I understand you want, like dual modifier keys, a large number of layers (I don't remember if it's 16 or 32 because the number just seemed more than enough for me), Fn keys embedded in Fn layers, and so on…

I would say that if Hasu's firmware is not enough for your needs, I would be interested to learn what you need that could be really useful and that Hasu has not yet implemented.

You have a crude list of features here:
  https://github.com/tmk/tmk_keyboard/blob/master/README.md

Very cool. Much better  than the other things that I have seen. Reading over the documentation it would seem that a lot of this would be possible. I would need to test it though. So now I need to get another keyboard.. Are you using this? If so, with what?

Have you used this and tried it with the dual role function and does it work with normal letters? That's essential for me. If the timing is right, this makes letter chording/ using normal letters as modifiers possible without interfering with normal typing.

As for what I was talking with keychaining, it seems that this might work. Basically what I mean is hitting a key to jump to and lock another layer from any layer. This would be like, for example, setting up tapping Capslock to set the keyboard into layer 20. All keys pressed would result in their layer 20 bindings. From there a key could be pressed to enter layer 21. A key could also be pressed to return back to layer 20 or 0. This seems possible from the documentation. I do a lot of weird things with chaining. It basically allows a modal keyboard interface (like with vim). What really makes chaining great, is when it is used in conjunction with prefix keys and macros. I use this, for example, to setup modal bindings with non-modal programs (for example, I have vim bindings and modes for certain programs).

However, it does not seem like there is prefix key capability. This is like a dead key. You can press a key that will, for example, enter layer 20 for the next (# chosen.. usually one) number of keypresses.

I'd have to test the macros to see how robust the feature is. Ideally, I would be able to send sequences of key presses with all modifiers available to alter those sequences. Sleeping would be useful too. For example if I wanted to sed f12 sleep 4 seconds send f14 sleep a few seconds send C-x

[angelic_sedition]

Sorry. I can't stop hitting quote instead of modify. I looked over the list of keyboard and Hasu's post on how he set this up with the hhkb. Software remapping is such a pain and so limited (I have to use over 6-10 programs in conjunction right now), so even if this doesn't have all the features I want, it would be massively useful. Will modding be required or is there anything that already comes with a teensy or whatever is necessary?

[angelic_sedition]

Sorry. I can't stop hitting quote instead of modify. I looked over the list of keyboard and Hasu's post on how he set this up with the hhkb. Software remapping is such a pain and so limited (I have to use over 6-10 programs in conjunction right now), so even if this doesn't have all the features I want, it would be massively useful. Will modding be required or is there anything that already comes with a teensy or whatever is necessary?

I'm so sorry; I did it again. I really wish there was an option  to delete posts.

[spiceBar]

I'm not to totally sure about it because I'm not sure I understand all that you want. Also I'm not sure Hasu has already implemented the things that people have yet to think of, because he is good but maybe not that good.

But Hasu's firmware does allow all of what I understand you want, like dual modifier keys, a large number of layers (I don't remember if it's 16 or 32 because the number just seemed more than enough for me), Fn keys embedded in Fn layers, and so on…

I would say that if Hasu's firmware is not enough for your needs, I would be interested to learn what you need that could be really useful and that Hasu has not yet implemented.

You have a crude list of features here:
  https://github.com/tmk/tmk_keyboard/blob/master/README.md

Very cool. Much better  than the other things that I have seen. Reading over the documentation it would seem that a lot of this would be possible. I would need to test it though. So now I need to get another keyboard.. Are you using this? If so, with what?

Have you used this and tried it with the dual role function and does it work with normal letters? That's essential for me. If the timing is right, this makes letter chording/ using normal letters as modifiers possible without interfering with normal typing.

As for what I was talking with keychaining, it seems that this might work. Basically what I mean is hitting a key to jump to and lock another layer from any layer. This would be like, for example, setting up tapping Capslock to set the keyboard into layer 20. All keys pressed would result in their layer 20 bindings. From there a key could be pressed to enter layer 21. A key could also be pressed to return back to layer 20 or 0. This seems possible from the documentation.

However, it does not seem like there is prefix key capability. This is like a dead key. You can press a key that will, for example, enter layer 20 for the next (# chosen.. usually one) number of keypresses.

I'd have to test the macros to see how robust the feature is.

I am indeed using using Hasu's firmware on several keyboards.

I have a GH60 with it, a modded HHKB (the controller has been replaced by Hasu's specific HHKB controller), and I also have several converters that turn a standard keyboard into a programmable one.

All this hardware uses Hasu's firmware.

Turning any key (including a letter or even space) into a dual-role modifier works very well. The firmware implements smart strategies to differentiate between the key being used as a modifier and the key being used alone to generate a character. The algorithm is not based on a timing alone, it's smarter than that.

This ability has allowed me to design and suggest the SpaceFN layout, that I have tested for long enough to say that it works for me (even if it would not work for everyone):
  http://geekhack.org/index.php?topic=51069.msg1121957#msg1121957

Hasu himself uses dual-role modifiers in the letters/symbols area (I think he uses "/" and other keys) to simulate mouse movements.

[angelic_sedition]

Did you make the converter? That seems like it would be the cheapest way. I'm hooked now.

Interesting. I'm currently using the spacebar for window management and hotkeys, though the software isn't that great, so I occasionally get accidental output. I prefer small spacebars and more thumb keys though. If the dual role works as well as you say it does, this is a must have for me.

[spiceBar]

Sorry. I can't stop hitting quote instead of modify. I looked over the list of keyboard and Hasu's post on how he set this up with the hhkb. Software remapping is such a pain (I have to use over 6-10 programs in conjunction right now), so even if this doesn't have all the features I want, it would be massively useful. Will modding be required or is there anything that already comes with a teensy or whatever is necessary?

It is massively useful!

The simplest and most versatile way to use Hasu's firmware is by using his converter.

The converter will only work with a keyboard that is compatible with PS/2 (that will work if you connect it to the PS/2 plug of a computer, even if you have to use a passive adapter). So if your keyboard ends with a PS/2 plug or has a USB plug but can be used in a PS/2 port, this will work.

The converter has a PS/2 female plug at one end (there you plus the keyboard, using a passive adapter if needed), and a USB connector on the other end (that you plug into the computer thru a cable).

The converter converts the key codes it receives from the keyboard to whatever you want.

The converter has an Atmega controller onboard and a few other passive components. It's very small. It also has a pushbutton that you press when you want to install a new firmware.

In order to adapt the firmware to your needs, you have to modify a few files written in C. Generally you need to change only one file, in which you are going to modify or add one or more tables for the layers, and an additional array that will hold the sequences or layer changes generated by special keys. The SpaceFN layout for example, is done with just one file which has two tables (one for the standard default layout, and another one that is activated by holding space). The third table contains a mix of constants that tell the firmware that space is a special key, and what this key does.

Where can you get this converter? I have got mine from Hasu himself. I don't know where else you can get them.

The GH60 also has a controller that is programmable with Hasu's firmware. But it's a group buy, so it can take a lot of time before you can get one.

[angelic_sedition]

Thanks so much for the help. Did you buy the converter from Hasu then, and is he actually selling them? I've no experience with hardware modification, so I probably wouldn't want to try to do anything like that myself. Is there a thread on it?

The GH60 looks nice, but I hate standard layouts. I don't think I can go back to big spacebars now... too much wasted space.

Also, would you say that the configuration is logical and easy? I've had to deal with some pretty messed up stuff.

[spiceBar]

Thanks so much for the help. Did you buy the converter from Hasu then, and is he actually selling them? I've no experience with hardware modification, so I probably wouldn't want to try to do anything like that myself. Is there a thread on it?

The GH60 looks nice, but I hate standard layouts. I don't think I can go back to big spacebars now... too much wasted space.

Also, would you say that the configuration is logical and easy? I've had to deal with some pretty messed up stuff.

Hasu's firmware can take advantage of the JP layout additional keys (I believe that's what you are using). Hasu is from a place where those keyboards are all around!

I've got my converters directly from him. I do not know if he wants/can to sell more of them. I cannot speak for him, you should contact him directly by PM as he is a member of this forum.

The configuration is not super easy because, as I said, you need to edit a C file. You've got a text file with a table, and you fill this table with key names. Generally you start from an existing layout that you start to modify, so you use the original layout as an example. You look at how it's done and you start by moving keys around. Generally there will already be a second layout in the original file, so you will just have to adapt it as well. Then you can create additional layouts yourself.

What I did not mention is that you then need to compile the firmware (which is a single command in a terminal box) and then reflash the converter (another command). You can do that with Windows, Mac or Linux (I used Linux). Oh and before you can do all of that you need to install a few utilities (the compiler and the flash utility). Almost everything is documented, but not perfectly. Under Linux I had a little bit of guesswork to do (I had to find the name of the packages to install).

All of this may not be a problem for you, it depends on your skills.

Also, I think you can get help from this forum. I believe there are a number of people here who have dealt with this already.

Even if it's difficult at first (which it may not be actually), the pleasure of being able to totally reprogram any keyboard is worth it!

Oh and if you can you should get two converters: one for your usual computer/keyboard and another one that you put in your bag so you can use it on the move.

[StylinGreymon]

Can you put one of these converters on a Poker?

[spiceBar]

Can you put one of these converters on a Poker?

On the Poker X (the first Poker), yes, because it is PS/2 compatible. I have used my Poker X for a while with Hasu's converter. However you cannot reprogram the Fn key, because it does not send any scancode. All the other keys are useable for anything you want. I was using the SpaceFN layout on the Poker X, now I'm experimenting with another layout.

I have modded my Poker X and rewired the Fn key so it does the same as the Menu key, because the Fn key is located at a place I really wanted to use. To do that I had to solder 3 short wires on the PCB and cut 2 existing tracks. It's not difficult to do. Now Fn and Menu send the same code, and I intercept this code with Hasu's firmware to do something with it.

On the Poker II you cannot use Hasu's converter because the keyboard is USB only. This is unfortunate, but the Poker II being programmable the damage is more limited. However, it excludes the Poker II from the list of keyboards you can use with Hasu's converters.

Unfortunately, the HHKB cannot be used with Hasu's external converter either, as the HHKB is USB only (because it behaves as a USB hub). For the HHKB, Hasu has designed and built a special PCB that replaces the HHKB's internal PCB. With the new PCB, you lose the USB hub (which is almost useless because of its electrical current limits) but you gain full programmability.

The Realforce keyboards are not compatible with Hasu's converter. They are USB only.

The Filcos work with the converter.