I asked my wife if she wanted me to waste my money on fast cars, fast women or fast keyboards, and, after she'd rolled her eyes, she said keyboards. This is my made up excuse for both a Soft/Hruf and a Stenomod arriving in the post the day before yesterday and yesterday.
The keyboard is split (like the StenoBoard), which means it has a really nice ergonomic position. You could unscrew and change the position if you wished, as the Stenomod comes with a longer connecting cable in the box. Having used it for a short while, I wonder if the Planck keyboard might have been too narrow for my tastes.
The Stenomod uses the TXBolt protocol. I've no idea what the benefit of this over the NKRO keyboard protocol.
The Stenomod got a far bigger reaction from my family. It reminds me of the Apple One, which also was partially made out of wood. It's not quite a steampunk look, I guess more of a retro 1970s vibe. I like the diodes and I/O board being on view. I'll probably need to create a lid or find a box if I want to travel with it.
And on OSX you can steno into password fields when using a serial machine. Not so with NKRO
--
You received this message because you are subscribed to the Google Groups "Plover" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ploversteno+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to ploversteno...@googlegroups.com.
I was writing a reply when I saw Glen's response, so I may repeat something!
Setting up Plover for the SOFT/HRUF should be easy. By default, the HRUF acts like a keyboard, and opening Plover and configuring the machine type to "keyboard" should work. Ensure Plover has output: enabled.
This will stop you from using a keyboard while Plover is running though. I'm assuming it would be better for you while learning to use your HRUF next to a functional keyboard. For this, you can emulate a real steno machine. While the HRUF is running, you can press key combos to change the mode. I believe it's the same as the steno board:
Fn1 + PH-PB NKRO Keyboard emulation mode (default)
Fn1 + PH-G Gemini PR protocol mode
Fn1 + PH-B TX Bolt protocol mode
You'd want TX Bolt mode, then you configure Plover to the TX Bolt machine.
Here is a diagram of which keys to hit on the HRUF to get it in TX mode:

I don't own a HRUF so I'm not 100% confident. Someone else will surely correct me if I'm wrong.
To unsubscribe from this group and stop receiving emails from it, send an email to ploversteno+unsubscribe@googlegroups.com.
This would be correct if the keyboard was using StenoFW. However, I abandoned StenoFW due to a keybounce bug that I did not want to figure out how to fix when other options were available. The new softhruf firmware uses this layout:
I’m also using the Stenoboard StenoFW with a homemade keyboard. For my second build I switched to a Teensy LC from a Teensy 2++ and saw much greater amounts of multiple keystrokes. Looking at the debounce code I spotted what appears to be an error in the line: if (debouncingKeys[i][j] == true && micros() – debouncingMicros[i][j])/ 1000 > debounceMillis)
— there need to be parens around the subtraction:
if (debouncingKeys[i][j] == true && (micros() – debouncingMicros[i][j]) / 1000 > debounceMillis)
if this is to make sense. I put them in and all multiple-keypresses went away.
Interestingly, two switches were much more prone to bounce than others — I’m using Matias Quiet Linear switches. I can’t explain why some switches would be more likely to bounce but it does seem to be the case. Once the debounce code was fixed, though, it was no longer an issue so I guess it’s nothing to worry about. Given the per-switch differences it may be that the change from the Teensy 2++ to the LC really had nothing to do with observing the problem and that it is all due to differences between switches in the two builds."
and the same user placed a pull request so StenoFW should be viable again.