F104+SSK+122+62+77+50+Ergo orders now open! New Kishsaver+Industrial Model F Keyboards

[Ellipse]

With permission I am posting some nice photos of the FSSK at home with a family of original IBM keyboards, including a Model F Unsaver! I like the placement of the Model F badge on the FSSK. Reminds me of the raised badge on the IBM 4704 promotional prototype photos posted a while back.

FSSK (1).jpg (1.95 MiB) Viewed 2125 times

FSSK (2).jpg (2.05 MiB) Viewed 2125 times

FSSK (3).jpg (4.27 MiB) Viewed 2125 times

[Ellipse]

Here we have a great review over on reddit of the Ultra Compact FSSK!

https://www.reddit.com/r/MechanicalKeyb ... _keyboard/

My comment: Thanks for your thoughtful review alifen! And for sharing a nice custom photo! It creatively addresses adding other color keycaps with the limitations of the pebble ISO color scheme (the stepped ISO Enter key comes from Unicomp, which doesn't offer any other colors that match the colors offered by the new Model F keyboard project).

[Ellipse]

Update on USB keyboards output to PS/2, AT, and XT signal:

I have received a small number of requests on this topic. This open source project (also available for purchase pre-built at the second link below) notes that it converts any modern USB keyboard to work with PS/2 input on a computer, as well as the XT and AT protocols for original IBM computers:

https://github.com/rasteri/HIDman

https://retrohackshack.com/product/hidm ... converter/

[edbods]

Nice. Still eager for that PS/2 daughterboard though.

[Ellipse]

The second container shipment batch F122 keyboards is starting to ship this week! First to ship are the various low serials. Now all F122's are in stock except for the few cut out mod cases that give 5 extra keys above the cursor keys (those are finished and should arrive to me later this year).

The F122's have proven even more popular than the FSSK's, so if you are looking to get one I strongly recommend getting it soon while stock still remains.

After thousands of original project new Model F's have shipped, we are down to the last remaining units of these F62/F77 classic and compact boards, so I also recommend getting one of these soon if you want one, before they are gone.

As always, feel free to add on some extras to your order by placing a new order and picking free/other shipping at checkout, right before clicking Place Order, so that you don't have to pay extra shipping charges (it ships with your keyboard order).

[edbods]

Wowee. Just an FYI for anyone else with an F122. The case and barrel plate screws (the ones that have a hex-head) use 6-32 threads (guessing it's UNC as the thread pitch is larger than an M3 coarse thread screw). Replaced the upper two that have a nut acting as a spacer because I felt that those were just way too short and not actually securing the barrel plate to the case. I got ones that had a 12mm shank length from a local hardware store, but I'm quite confident you can get away with 10mm length screws.
Honestly it's probably unneeded, but at least in case you ever need replacements you know what to get if you don't want to rethread the holes for a different screw.

[Ellipse]

Yes, all of the bolts for this project are 6-32 (classic cases and the two controller ground screws for all keyboards), T8 (compact cases), M3 (2 solenoid screws), and 8-32 thread (medium threaded bumpers). The 6-32 bolts use a T8 size or Philips driver.

[Ellipse]

Bluetooth wireless Model F update:

Is anyone interested in making their Model F wireless?

I recently saw a post on this, for the Model M: viewtopic.php?t=29368

Maybe it can be an update or add-on PCB to Rico's Leyden Jar controller or the xwhatsit controller, or a new controller entirely (less convenient as it would require everyone to desolder their current controller).

The Leyden Jar RP2040-based controller does accept power and signal on its header extension, so something like the Supermini NRF52840 used for the above project may be able to work with a battery. Ideally, if a PCB is needed it could be designed to be manufacturable by JLCPCB. If it is powered off the header extension, it might also be helpful to have an extension header on the add-on PCB for a solenoid driver and solenoid (though the battery won't last as long). The Leyden Jar currently allows one controller to communicate with and power another: https://github.com/mymakercorner/Leyden_Jar

There are other projects not specific to the Model F that may work but are currently not tested with the Model F:

https://handheldsci.com/kb/
https://sterling-key.com/
https://www.youtube.com/watch?v=MEMyae7b74I
https://www.wscome.com/product/wired-ke ... d-diy-kit/
https://www.wscome.com/product/convert- ... 2-wbt2-v4/
https://git.kkozai.com/kenji/pico_ble_hid/
https://www.reddit.com/r/MechanicalKeyb ... turn_your/
https://www.reddit.com/r/olkb/comments/ ... ontroller/


My guess is that the Model F would require a much larger battery to be able to run for several weeks (15000mah?). Maybe one of those Lithium iron phosphate batteries of that size could be used.

[DiscoMike]

I am just waiting for my Beamspring 122 Round 2 Keyboard to ship. My order was placed back in January.

[Ellipse]

For those who have received and started using the new F122 keyboards:

Please email me with feedback on how things are going. As always, make sure you're running the latest firmware (I think 5/19/25 is the latest?) which fixes potential issues with key ghosting, etc.

Is the F122's RP2040-based Leyden Jar controller better able to handle KVM switches, USB hubs, USB extension cables, etc.? I recall that these caused issues for some xwhatsit controller-powered keyboards.

DiscoMike, I just posted an update over on the beam spring project thread.

[Ellipse]

Here's a nice article on the 40th anniversary of the Model M keyboard this year: https://www.pcgamer.com/hardware/gaming ... -on-today/

And here is the latest update from someone who got Bluetooth working with their new Model F keyboard, which uses Rico's RP2040-based Leyden Jar controller:

"I was able to get this https://www.amazon.com/Ruitutedianzi-Bl ... 0DP6WTZY4/ Bluetooth adapter to work on this Leyden Jar board, whereas my xwhatsit based restored IBM F122 does not register any keypresses with it. The Handheld Scientific BT-500 does not work with either controller, but does at least register double keypresses with the Leyden Jar. I don’t have their updated BT-600 to test with. According to my in-line USB meter, the BT adapter and keyboard idles at 26mA (with all LEDs on, each consuming ~1mA). With the solenoid at factory settings, I’ve seen it peak at 189mA – but the ~1s sampling rate makes this a very rough estimate.

Using an average 2000mAh 18650 Li-ion cell, I would guess we’d get ~76 hours (or as little as 10 with the solenoid and constant firing)." In other words, one month of battery life with a 20000mah battery.

[idollar]

Bluetooth wireless Model F update:

Is anyone interested in making their Model F wireless?

I recently saw a post on this, for the Model M: viewtopic.php?t=29368

Maybe it can be an update or add-on PCB to Rico's Leyden Jar controller or the xwhatsit controller, or a new controller entirely (less convenient as it would require everyone to desolder their current controller).

The Leyden Jar RP2040-based controller does accept power and signal on its header extension, so something like the Supermini NRF52840 used for the above project may be able to work with a battery. Ideally, if a PCB is needed it could be designed to be manufacturable by JLCPCB. If it is powered off the header extension, it might also be helpful to have an extension header on the add-on PCB for a solenoid driver and solenoid (though the battery won't last as long). The Leyden Jar currently allows one controller to communicate with and power another: https://github.com/mymakercorner/Leyden_Jar

There are other projects not specific to the Model F that may work but are currently not tested with the Model F:

https://handheldsci.com/kb/
https://sterling-key.com/
https://www.youtube.com/watch?v=MEMyae7b74I
https://www.wscome.com/product/wired-ke ... d-diy-kit/
https://www.wscome.com/product/convert- ... 2-wbt2-v4/
https://git.kkozai.com/kenji/pico_ble_hid/
https://www.reddit.com/r/MechanicalKeyb ... turn_your/
https://www.reddit.com/r/olkb/comments/ ... ontroller/


My guess is that the Model F would require a much larger battery to be able to run for several weeks (15000mah?). Maybe one of those Lithium iron phosphate batteries of that size could be used.

Dear Model M Labs,

I do not fully understand your message.
Could you please elaborate the business model behind your request ?

Are you asking to help in upgrading the LeydenJar to commertialise a new product ?
In case of a positive answer, could you please explain how would you share the expected profit with the contributor ?

Thanks in advance

i$

[Ellipse]

Now that the backlog of F122's is done and we are just waiting on boards with orders in August and Everything After (!) (as well as the Round 2 beam spring boards), I will be proceeding with the pad printed Model F PBT keycap project. Due to poor quality I had to switch factories. Below is the new factory sample. This company is one of the largest keyboard manufacturers in the world.

Based on feedback with a focus on durability instead of authenticity to original standards, these keycaps will be using the highest quality abrasion-resistant inks offered by a major manufacturer, as well as a protective coating on top of each legend, with a slight margin of safety. The original IBM M13 boards were known to wear more quickly as they had no protective coating. While this reduces originality it should greatly increase durability.

Please disregard the lack of alignment for these test prints; the production keys will have normal alignment.

2025-09-15_18-23-58.jpg (2.78 MiB) Viewed 1192 times

Below is a photo from the first batch of combined Apple/Mac Text and Icon keys, which are now in stock and available to order.

2025-09-15_18-24-17.jpg (2.12 MiB) Viewed 1192 times

Apologies that both photos are slightly out of focus for parts of the image.

As always please sign the following interest forms if interested and if you have not done so already:

Pad Printed keys interest form: https://forms.gle/Md7p5oA8zySy6pkG7

2025 Model F Project Interest Form for new designs: https://forms.gle/c9cSCCmsDhZk4ZDR6

ISO Black, Industrial SSK Blue, Dark Gray Key Sets, Big Enter Keys, Code Keys Interest Form: https://forms.gle/cDDypmZii6ihxgDY8

And with permission I am sharing a nice image of the Quebec CSA key set:

Quebec CSA.JPG (3.7 MiB) Viewed 1192 times

[moon]

F122 Firmware building questions

This post is the first real use of my new F122 - very happy.

I want to increase the number of VIAL macros from the default 16 to 25, but my git & make skills are rusty so I've a few questions please.

Stable firmware version
From "A beginner’s guide to full configuration of QMK/Via:" section in the Model F Keyboards manual:

Code: Select all

git clone -b leyden_jar --single-branch https://github.com/mymakercorner/vial-qmk.git

This appears to clone the latest files on the "leyden_jar" branch - is this always stable?
I remember normally cloning a tagged Release (such as Leyden Jar Firmware Release 2025.05.19) to ensure a coherent & tested set of files.

Required source changes
To increase the macro count, I believe I need define:
# define DYNAMIC_KEYMAP_MACRO_COUNT 25

Do I need to do anything other than include the above in qmk_firmware\keyboards\leyden_jar\f122\config.h?

Memory & resources
The VIAL app Macros tab indicates 2195 available memory for the current 16 macros - this will be plenty for the 25 macros I have planned. Will increasing the macro count have any other impact on resources I will need to accomodate?

Many thanks.

[Ellipse]

Major project milestone:

Today the keyboard projects passed $4 million in total orders!

[Falkenroth]

Major project milestone:

Today the keyboard projects passed $4 million in total orders!

Congratulations. A lot of work to get there.

[Ellipse]

With permission I am sharing a custom "all pads" layout with the custom 3x5 cut out mod. These mods were first suggested by this user, who is nicknaming this version the F138; now several others have ordered this mod for their F122 (you don't have to use all pads with the 3x5 cut out mod - you can have a regular ANSI/ISO/split shift layout just with 5 keys added above your cursor keys). I still have some cut out cases but they are only available in certain colors (beige and others, no more black cut out cases). Please email me if interested in ordering one.

With this layout, every available pad is used for a key. Each key can be configured in Vial as there is a working pad for each one.

F138 - Copy.jpg (358.02 KiB) Viewed 885 times

[Green Maned Lion]

I wish I had known that mod was possible before I ordered my beamspring. My biggest issue with the 'F122' model offered is its T-nav layout; I want an F122, but with a cross-nav like on my M122s.

[Ellipse]

The mod was announced some time ago. The 3x5 cut out F122 case can also be ordered alone, in order to upgrade the keyboard for anyone who has already received their F122. Just order the case and 100 units of $1 increments and remind me to include the additional barrels and flippers.

[snoopy]

I‘m a bit confused, why is this still marked as a groupbuy and in the member to member section?
Seems more like a webshop advertising/selling things here? I don’t see any character of a groupbuy.

[Green Maned Lion]

The mod was announced some time ago. The 3x5 cut out F122 case can also be ordered alone, in order to upgrade the keyboard for anyone who has already received their F122. Just order the case and 100 units of $1 increments and remind me to include the additional barrels and flippers.

My wife was very generous in letting buy my B122, and several thousand dollars worth of other keyboard related stuff this year. I'm not even going to ask if I can buy a new F122 until Chanukah. lol.

I'd be even happier, though, with a vintage F122 if I could find a restored one for a sane price. But still waiting until the holidays for that one, even.

[Ellipse]

Has anyone come up with additional Model F 3d printed mods? I have looked around the various 3d parts sites.

I have purchased a 3d printer to help with prototyping as well as to offer 3d printed items to those who do not have their own 3d printer - items like 3d printed solenoid holders and feet.

Maybe even some flip-out feet like the IBM F122 and XT/AT feet that could be attached by bolts to the holes in the bottom of the cases.

Any other ideas for 3d printed parts?

Yes Green Maned Lion, those original F122's are getting harder to find! They are my favorite IBM Model F originals - I am typing on one now! An April 1984 6110344

[Ellipse]

Rico has just published the latest firmware update for all Leyden-Jar based keyboards (currently just the F122 but soon the Round 2 B104 and B122, and eventually all boards):

https://github.com/mymakercorner/vial-q ... 2025_10_24

This firmware fixes a bug where the keyboard needed to be unplugged and plugged back in to work after certain computers resumed from sleep mode. It also fixes an issue where splitting certain keys in the allpads version was not saved after the keyboard is power cycled.

Everyone feel free to test this latest version and let me know if there are any other issues.

[Ellipse]

Everyone please check out GH forum member ploxiln's updated Linux and Mac pandrew utilities as well as other updates here, and let us know your feedback:

"Hi Ellipse, I've been working on building the xwhatsit/wcass firmware an util for all platforms, and my own scripts for building and flashing, etc. It's not really better than NathanA's r5 release build, as far as I know, but the purpose is more to confirm that my scripts can do it all "from scratch". These scripts are in the repo: build_vial_xwhatsit_all.sh, flash-util/*, keyboards/xwhatsit/util/*.sh You can see the resulting builds of all this at https://github.com/ploxiln/vial-qmk/rel ... newfxx_r5c

Something new included there is a Linux AppImage build of pandrew-util. (There's also a Windows exe and macOS app, but built for the newer cpu archs compared to NathanA's builds, see release description). I took the liberty of using your favicon from modelfkeyboards.com and scaling/adapting it "quick and dirty" for pandrew-util, I hope that's OK.

See also the updated repo README starting around here: https://github.com/ploxiln/vial-qmk?tab ... l-firmware

Regarding syncing both the leyden_jar and xwhatsit github repos / branches ... it would probably have been simplest to "fork" from both my repo and rico's repo, but you mentioned you can't do that because both forks are in the "vial-kb/vial-qmk" "network" and you can only have one fork related to that network in your github account. I could theoretically unlink my repo from upstream "vial-kb/vial-qmk" but actually that function is disabled because my repo "already has child forks". Hmm. I think maybe the cleanest thing to do is just fork from the more-upstream "vial-kb/vial-qmk", and then use git locally (or some git gui) to periodically sync the branches from rico and I, if there are changes. If someone else effectively takes over from me (or NathanA comes back), it would be simpler to switch to pulling a branch from them at that point."

[Ellipse]

With permission I am posting a nice new production F122 setup with a CRT monitor. I had one of those old Dell CRT's back in the day! I don't recall the specific model but we got it in 1997 or 1998 I believe.

keyboard_crt.jpg (235.68 KiB) Viewed 502 times

[QuestionAsker2030]

Hello all,

First post, got my first mechanical keyboard (F122) and have put it together. Very interesting setups here, used many photos as inspiration for my own layout, excited to start using it.

I had a question before setting it up as my daily driver, if it's OK to ask:

I live in a high-dust environment, and was wondering how to best protect my new F122 so as not to get dust in all the cracks (and in general just to keep it dust free, when I'm using it during the day.

For my current cheap keyboard, I just throw a T-Shirt over it at the end of the day, and take it off the next morning, and dust off my desk with a microfiber towel.

Would that be the best solution?

I find that somehow a bit of dust seems to still get up in into the keyboard however, in spite of being covered with the T-Shirt.

Wondering what you guys use to protect your keyboards against dust.

[edbods]

Honestly I'd say just blowing it out with an air gun would suffice. The gaps above and below the main key groups/areas are big enough for dust to get out when blasted with an air gun. The drawback to doing this is that it might get dust on the underside of the barrel plate, and you'd need to take the case off to truly clean it. But with the way the keys are held in the barrels, it doesn't seem like dust would be able to get in to the PCB which would probably be the critical part; if you did use an air gun, dust could only really get in if you blasted the dust off with the keys removed.

Beyond that though I can't really say, my F122 sits in my room all day so it's not subjected to the amount of dust as say, an industrial workshop.

[Ellipse]

Leyden Jar firmware update (for F122):

Rico has posted an update for the Leyden Jar firmware. It allows more space to store macros compared to the Vial default and all firmware files can now split and unsplit keys (no need to reflash the allpads firmware).

https://github.com/mymakercorner/vial-qmk/releases

As noted with last month's update, the firmware was fixed last month with issues related to resume from sleep and certain split settings not saving after you make changes to them.

Everyone feel free to test this latest version and let me know if there are any other issues.

[Ellipse]

Major project milestone:

This month the keyboard projects passed 7,000 shipped keyboards! Shipping started in late 2019.

We still have the normal backlog of recent orders as well as the round 2 beam spring keyboards, which are currently in production and expected to go out over the coming months (more details on the beam spring thread).

Orders (with and without keyboards) have gone to 71 countries in total (per ISO 3166):

Argentina
Australia
Austria
Bahrain
Belgium
Brazil
Bulgaria
Canada
Chile
China
Colombia
Croatia
Curaçao
Cyprus
Czechia
Denmark
Estonia
Faroe Islands (the)
Finland
France
Germany
Gibraltar
Greece
Guam
Hong Kong
Hungary
Iceland
India
Indonesia
Ireland
Israel
Italy
Japan
Kazakhstan
Korea (the Republic of)
Lithuania
Luxembourg
Macao
Malaysia
Mauritius
Mexico
Netherlands (the)
New Zealand
Norway
Oman
Peru
Philippines (the)
Poland
Portugal
Puerto Rico
Qatar
Republic of North Macedonia
Romania
Russian Federation (the)
Saudi Arabia
Senegal
Serbia
Singapore
Slovakia
Slovenia
South Africa
Spain
Sweden
Switzerland
Taiwan (Province of China)
Thailand
Turkey
United Arab Emirates (the)
United Kingdom of Great Britain and Northern Ireland (the)
United States of America (the)
Viet Nam

[TRN]

I have been using my F122, but I've found a minor issue I've not been able to work out on my own. Sometimes the solenoid will stick for an indefinite amount of time. I don't know what the core of the solenoid is binding on, but it is randomly binding on something. But it always unsticks itself with a modest thump.

I don't know if Ellipse has a solution to this already, but I'm hesitant to just do something like throwing a bit of instrument and tool oil into it until I have at least asked if the solenoid would be damaged by doing so. I'd rather not screw up my daily driver, especially when I don't know if the solenoid binding occasionally is a known issue, or a defect specific to my unit.

I'm pretty sure it's physically binding, as I can't see any issues on the driver board, but the process of opening the keyboard to look at the solenoid always frees it, and I can't reproduce the issue when I have the case open and am moving the solenoid by hand. Any suggestions on that front are welcome. If Ellipse thinks that it's not a mechanical issue, I can probably figure out tapping an oscilloscope into the solenoid circuit if he wants to look at the electrical side of things.

It's the one and only frustration on what is absolutely the best keyboard I've ever used. It has made writing so much more of a joy, and I'm still looking forward to actually trying it out on a game that actually requires precise and fast key inputs since I've been spending my free time writing instead of playing games.