deskthority

'k. Here's my implementation of having the (host) Num Lock status act as a selector (Fn key) for Layer 1.


I finally installed your latest firmware version... I had to tweak your .sh script to suit Debian's very old dfu-programmer 0.6.1. See my changes in the attached file (many variables to ...

One of the keys on my F77 (H) was misbehaving more and more over time. We don't use it very much in french apparently. It had a lower sounding click. I had re-seated the key and spring many times, and finally removed the spring, which was a bit curved. It's able to roll regularly on a flat surface ...

I am tempted to go for a Classic Style FSSK Model F Keyboard, ISO-DE Mac Layout . I understand how to order extra keys for that, like L/@ and ß/? and Cmd, Opt, Ctrl and F11-F13.

But I want to get some more technical answers/guidance - I cannot find a consolidated up to date documentation as to ...

Off the top of my head, I don't have more than one minor style fix to contribute, but when viewing an image in the shop that fills the width of the monitor, the blue newsletter button on the left side covers the side of the image.


Generally speaking, I'd say that any browser display width other ...

Today the project is featured in TechSpot, ExtremeTech, and Adafruit's blog!


Nice to see so much interest. You reached viral status ;-)


AnnoyedWalrus there are not enough pads in the 16x8 matrix unfortunately. Hopefully that will change in the future with the forthcoming Leyden Jar ...

Arkku wrote: 04 Apr 2023, 11:11 (or some direct communication between the halves).

That mystery split USB-C cable could be the key... Each controller could spy on the other one's USB traffic, or some wires inside the cable could be routed between both halfs.

sedevidi wrote: 02 Apr 2023, 11:41 Maybe it also means that pressing Shift on one will not trigger Shift on the other?

Just tested: apparently, Shift, Ctrl, AltGr all work cross-keyboard.
Fn potential problem remains...

I read that both split keyboards actually have a keyboard controller in each part, ie. you plug two independent keybards.
This probably means that pressing Fn on one half will not trigger the Fn layer on the other half.
Maybe it also means that pressing Shift on one will not trigger Shift on the ...

The forum member behind the new Quebec CSA has just submitted a new key set, option, French AFNOR (BÉPO), and has comments below. I have sent the design to the factory, to be included in an air shipment going out this month or next month. I am ordering a few extra sets in case anyone is interested ...

wolfman wrote: 06 Feb 2023, 02:51 When I was doing a final review I discovered that VIA has been bumped to a new version. I now need to find time to update my version of the QMK firmware for the new version of VIA.

Thank you very warmly much for this work!

I didn't see many AZERTY model Fs, or with the classic num+nav pad.
So here is mine: I'm very happy with it!

Ellipse wrote: 30 Nov 2022, 18:39 Rico's new RP2040-based controller samples arrived today!

Nice rounded PCB traces!

Could you elaborate a bit on the current status of this promising project, please?

The right Ctrl key doesn't work and it doesn't seem to be hardware-related, because when I run the "pandrew QMK utility" it registers just fine, both in the keypress monitor and in the signal level monitor.

However, if I go to the QMK configurator "test keyboard" option, the keypress events don't ...

the Vial version – not sure where this is setup or is it just done by patching one of the others



That one was created by NathanA, who described the process a few months ago in this thread. IIRC, this is quite the same as all the other ones: based on mainstream at that time, patched with ...

If you are also interested in testing my fork with saving of calibration / improved scanning speed / keys pressed while powering up detection/recovery, send me a copy of your JSON configuration file and I can build a firmware for that. (Caveat: the calibration threshold offset may need tweaking ...

So, is there a practical situation where you press a key within 200 ms on power-up but after 10 ms?


That happened once in a few months. I powerup the laptop on its dock, then type my password... The firmware I use is Vial from NathanA.


Meanwhile the discussion about varying USB voltages is ...

I got surprised today, when I began to type my password too quickly after waking the computer up. The first 2 keys where probably discarded during the calibration process, and didn't function at all in the subsequent session I openned using the laptop keyboard.
It was a bit wierd that some "random ...

Anyhow, how is the upstreaming of the qmk firmware going?
I know C, so I could lend some time but I don't know what still needs doing or if other people (pandrew) are still working on it.


There are some info on this very subject a few pages earlier.
ARKKU also developped another firmware, using ...

Wrt. the keyboard not working at startup


I strongly suspect some flipper or spring placement to confuse the calibration process in Takashi's case. Thus the above suggestion to try the xwhatsit or AAKBD firmwares, which calibrate differently.
In my case, the left Ctrl key didn't work reliably ...

Any ideas what I can do? Is there any other way to enter boot loader mode so that I can just do a clean eeprom-flash?


You can always open the keyboard and short the "reset" pads at "the correct time" (during power-up).
Or there can be a utility to switch it to bootloader mode on the fly.

Takashi wrote: 18 Aug 2022, 18:36 Sometimes when I start my computer, the keyboard is not detected.

You should probably define « computer », as there are apparently problems with Macs or USB hubs, and I don't remember anyone having this kind of problems with simple PC setups.

I wonder which is correct and what happens if the spring ends up in the wrong orientation?


As experienced recently: I vaguely remember that boths ends of the spring I removed have the same orientation; what happens is that the key won't register reliably, or only when pressing the key a certain ...

Takashi wrote: 02 Aug 2022, 13:11 Huh? What am I doing wrong?

IIRC, you may have used an initial firmware in which those 2 keys were not assigned, which the firmware identifies as non-existing. You thus cannot assign them later using VIA.
Just use a firmware in which all keys are assigned, say 0-9 numpad.

PRIPARA_PLAYER wrote: 09 Jul 2022, 17:32 IMG_20220709_235403.jpg

Weird color. Weird layout. Weird TMK. Or is it the contrary?

Would you elaborate on these?

For example, I'm trying to use numpad layout 5, where 4 is visually shared with Del, 5 with End, 6 with PgDn, etc. When I press my layer toggle key from an admin account, all keys toggle correctly; however, when I do the same from a non-admin account, Del/4 functions as Left Arrow, PgDn/6 as Right ...

If I believe Vial, the combo had sent the same key code (0x5C00) as the "r" key defined on layer 2. Contrary to the former, the latter does enter bootloader mode, though. Hence I wonder, if combos can be used at all to enter bootloader mode running Vial firmware?


IIRC, there is a bug in the ...

I'm assuming pandrew = purdea.ro? Trying to clone that getting less than 1 kbit/sec.


As an alternative, I use NathanA's Vial build, and I'm very happy with it. He provided all the details to build it yourself a few pages ago. I didn't even build it myself... The plus of Vial is that the open ...

Perplexed about what you mean by "feeling" when you say the board's flaky on them both.


The LeftCtrl is definitely the worst key, thus defines the flaky behaviour. Other keys feel like they do not registrer some times, or registrer a bit late: that's the feeling. Nothing definitive or clearly ...

sedevidi have you tried another USB cable?


I do not own a spare USB-A-to-C cable... I may try with an USB-A-to-microUSB with an USB-C adapter though, if I can somehow manage to use the keyboard while open...

As a recap, I tested on the following ports on my Thinkpad T430 with my Mini Dock Plus ...

The flakiness is coming from inside the house. I mean the keyboard! It’s not the USB side of the controller, it’s the capsense.


Do you mean I should check for something related to sensing (say solder joints between the controller and the capsense PCB?), or is there some design issue on the F77 ...