New, Compact Model F: Thoughts and Tilting the Keyboard

[Coeus]

Much earlier in the New Model F project, I said that one reason I didn't order one was that they were not available in the, now standard, enhanced layout. They did then become available in that layout, I ordered one and it has now arrived.

They keyboard itself is absolutely excellent. Very helpfully, it came with the ISO enter key and space bar installed, I followed the instruction to fit the remaining keys with the keyboard on edge, space bar uppermost and, contrary to the expectation set in the instructions, all they keys worked first time. The feel is very light and positive and very good to type on, very similar, of course, to an original XT Model F that I also have.

I opted for the compact case. The finish is really good, despite the warning that blemishes are to be expected. What I was not expecting was that the top surface of the case would be flat while the keyboard inside is curved, so the keys at the top and bottom of the keyboard protrude from the case by almost the full height of the key cap whereas the numbers and QWERTY rows are almost flush to the case.

The original XT Model F I have has feet to enable the keyboard to be tilted towards the typist and there are no such feet on this compact case, only four stick-on rubber feet which are all the same height.

Does anyone else prefer the keyboard in the tilted position and, if so, what have you used to achieve that? At the moment, I have the edge furthest from me stood on some CD cases but that is not really a long term solution, especially if it needs to be moved.

[Ellipse]

Much earlier in the New Model F project, I said that one reason I didn't order one was that they were not available in the, now standard, enhanced layout. They did then become available in that layout, I ordered one and it has now arrived.

They keyboard itself is absolutely excellent. Very helpfully, it came with the ISO enter key and space bar installed, I followed the instruction to fit the remaining keys with the keyboard on edge, space bar uppermost and, contrary to the expectation set in the instructions, all they keys worked first time. The feel is very light and positive and very good to type on, very similar, of course, to an original XT Model F that I also have.

I opted for the compact case. The finish is really good, despite the warning that blemishes are to be expected. What I was not expecting was that the top surface of the case would be flat while the keyboard inside is curved, so the keys at the top and bottom of the keyboard protrude from the case by almost the full height of the key cap whereas the numbers and QWERTY rows are almost flush to the case.

The original XT Model F I have has feet to enable the keyboard to be tilted towards the typist and there are no such feet on this compact case, only four stick-on rubber feet which are all the same height.

Does anyone else prefer the keyboard in the tilted position and, if so, what have you used to achieve that? At the moment, I have the edge furthest from me stood on some CD cases but that is not really a long term solution, especially if it needs to be moved.

Thanks for your review and feedback Coeus!

For tilting the keyboards, feel free to check out the store item "bumpers" which allow various angles through the use of bumpers varying from almost no height to bumpers with 1 inch height.

[Green Maned Lion]

I wish to point out that my preference in keyboards is the Model M 122 "Type I" or the Model F 122 (same basic design), with its tilting feet in the most extended position. I am clearly in the minority for this preference, as practically no other keyboard was build with this level of tilt being available. I have ordered Joe's 24-function "122" configuration of beam spring, and the large 1" feet he mentions in the post above. I am hopeful this will be adequate in the regard of keyboard tilt. Actually, I'm nervous about the entire purchase because of the uncertain timeline, the fact I've never touched a beamspring keyboard to my knowledge, and the fact that I've spent over $600 on this purchase (I selected quite a few options).

But that is the nature of buying such a specialised device manufactured in such a small run. I take it overall, you are impressed with your New Model F?

[Coeus]

But that is the nature of buying such a specialised device manufactured in such a small run. I take it overall, you are impressed with your New Model F?

Yes, I have been pleased with it and use as my usual keyboard.

It has, in the last couple of days, started to behave strangely, though.

On Windows, I keep hearing the sound for a USB device being disconnected and then reconnected, and Windows pops up a message saying "The last USB device connected malfunctioned and is not recognised by Windows". Despite that, it actually works -- I am typing on it now.

On Linux, it now doesn't work and I get this in the journal:

Code: Select all

Oct 29 10:43:33 ecrins kernel: usb 1-3: new full-speed USB device number 20 using xhci_hcd
Oct 29 10:43:33 ecrins kernel: usb 1-3: device descriptor read/64, error -71
Oct 29 10:43:33 ecrins kernel: usb 1-3: device descriptor read/64, error -71
Oct 29 10:43:33 ecrins kernel: usb 1-3: new full-speed USB device number 21 using xhci_hcd
Oct 29 10:43:34 ecrins kernel: usb 1-3: device descriptor read/64, error -71
Oct 29 10:43:34 ecrins kernel: usb 1-3: device descriptor read/64, error -71
Oct 29 10:43:34 ecrins kernel: usb usb1-port3: attempt power cycle
Oct 29 10:43:34 ecrins kernel: usb 1-3: new full-speed USB device number 22 using xhci_hcd
Oct 29 10:43:34 ecrins kernel: usb 1-3: Device not responding to setup address.
Oct 29 10:43:34 ecrins kernel: usb 1-3: Device not responding to setup address.
Oct 29 10:43:35 ecrins kernel: usb 1-3: device not accepting address 22, error -71
Oct 29 10:43:35 ecrins kernel: usb 1-3: WARN: invalid context state for evaluate context command.
Oct 29 10:43:35 ecrins kernel: usb 1-3: new full-speed USB device number 23 using xhci_hcd
Oct 29 10:43:35 ecrins kernel: usb 1-3: Device not responding to setup address.
Oct 29 10:43:35 ecrins kernel: usb 1-3: Device not responding to setup address.
Oct 29 10:43:35 ecrins kernel: usb 1-3: device not accepting address 23, error -71
Oct 29 10:43:35 ecrins kernel: usb 1-3: WARN: invalid context state for evaluate context command.
Oct 29 10:43:35 ecrins kernel: usb usb1-port3: unable to enumerate USB device
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: new full-speed USB device number 24 using xhci_hcd
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: New USB device found, idVendor=1209, idProduct=4704, bcdDevice=41.01
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: Product: F104 Keyboard (FW:r5)
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: Manufacturer: Model F Labs LLC
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: SerialNumber: vial:f64c2b3c
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: rejected 1 configuration due to insufficient available bus power
Oct 29 10:43:55 ecrins kernel: usb 1-1.1.2: no configuration chosen from 1 choice
Oct 29 10:43:55 ecrins mtp-probe[6708]: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 10:43:55 ecrins mtp-probe[6708]: bus: 1, device: 24 was not an MTP device
Oct 29 10:43:55 ecrins mtp-probe[6725]: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 10:43:55 ecrins mtp-probe[6725]: bus: 1, device: 24 was not an MTP device
Oct 29 10:44:09 ecrins kernel: usb 1-1.1.2: USB disconnect, device number 24

and so on. I have tried the obvious thing of changing the USB-A to USB-C cable but that seems not have made any difference.

[Ellipse]

Please update to the latest firmware that was released this month: https://github.com/mymakercorner/vial-qmk/releases

Also are you using any of the previously discussed problematic connections: USB hub, KVM switch, extension cable, the USB port on a computer case, third party USB cable, a failing USB port that can no longer provide sufficient power, etc. Try another USB port, a USB 2.0 port, and a port directly on your motherboard.

Does your computer use an intel processor and chipset? Some intel chipset users have reported issues with random USB disconnections. This happened on my own computer with non-xwhatsit, non-leyden jar devices. Replacing the motherboard with one that had a newer intel chipset resolved the issue.

[Coeus]

I did look at the link for the firmware. This is obviously not specific to the New Model F so I also went to read the relevant section of the manual. I may have been a bit tired but it will take a second read, at least, to work out what I am supposed to do.

Using a motherboard mounted USB port is not really practical for either of the PCs I regularly use.

For the work laptop, there is only one USB-A socket and this needs to provide network, an external sound card, keyboard and headset with the USB-C connecting to the monitor. In theory, the monitor should be able to do some of these but it doesn't seem to work.

For the home PC (a mini tower) those ports are round the back and the tower is under a desk. There are also four devices already plugged in there.

The good news is that, even so, the keyboard has started working properly again. All I did was unplug it, put it aside for a few hours, then try it again. I don't think it has got wet - there don't seem to be any other signs. I can only assume that the microcontroller got into a odd state that a quick unplug and plug back in didn't solve but a longer period without power did.

On the question of KVMs, I would like to use this KB connected via the monitor I have, which includes rudimentary KVM functionally. From my experience with a previous converter to allow an original IBM Model F (XT) to work with a modern PC, there can be an issue where the KVM expects to snoop on communication from KB to PC and does not seem to understand the protocol used for full key rollover. Once I configured QMK to stick to the boot protocol, it worked fine.

[Coeus]

Please update to the latest firmware that was released this month: https://github.com/mymakercorner/vial-qmk/releases

Having re-read the section of the manual, it seems updating from Linux should be possible but the link above contains only the firmware, not the tools. The download from the "Flashing Firmware" section of the manual does contain some bash scripts. The one I think I need, "UNIX - f104 r2 iso.sh", invokes flash-util/dfu-programmer but the executable of that name appears to be for a machine running MacOS.