#49

(or for that matter, in my case I could be compiling development-of-scripts firmware for myself with faster polling so I can type correctly and performance firmware that restores normal polling at the expense of dropped keys. Long live FOSS.

That said really appreciate that you’re taking any time to look at this at all. Thank you!)

2 Likes
#50

Found some time to test this today. 20ms is better for me than the default 47, but I still drop keys. 15 and 10 are both very usable, though I still drop the occasional key. 5 actually seemed worse to me than 10, though my testing wasn’t exactly scientific.

I may just do custom firmware builds for myself of whatever is the current firmware so I can use the keyboard. The mechanical is nice, and since I’ve paid for it I’d like to use it, but being able to use Dvorak with Teletype is a real win for me personally (my keyboard has Dvorak/Colemak modes settable via DIP switch).

1 Like
Teletype firmware discussion
#51

omg typing Colemak on Teletype would be nice, so it doesn’t interfere with my muscle memory… maybe I’ll look into this

1 Like
#52

It’s a bit confusing because right now my Teletype muscle memory is hunt and peck Qwerty and I have to unlearn that now :slight_smile:

1 Like
#53

thanks for testing this! i’ll send you another version to try (with the fix i described above).

1 Like
#54

can you give this version a try? including modified main.c as well so you can see the change.

main.c (28.7 KB)
teletype.hex (549.4 KB)

2 Likes
Teletype - Programming a keyboard to send stored commands
#55

ah this makes sense! It did seem like there were times where if I pressed the keys really fast multiple key strokes would populate the screen at the same time.

In other words, ASDF typed in super quick succession would sometimes populate the screen visually as A…S…DF.

I’m assuming that the buffer is appended to, and processed first-in, first-out, right? Only thing I can think of that I didn’t test very thoroughly is that the keys come in the order they are pressed.

#56

keyboard HID protocol is a bit weird. updates gets sent in frames, iirc for keyboard a frame always consists of 8 bytes, byte 0 is a bitmask for modifiers (alt/shift/ctrl), byte 1 is reserved and the rest is for key presses / releases. for presses you know what key was pressed but for releases it’s just 0, so you have to compare to the previous frame to know which key was released. also i don’t remember if the order within a frame is guaranteed (i imagine it’s maintained though, otherwise it’d be really weird…)

#57

word, sounds good, I can keep a check on it and see if I ever get any out of order-ness or any sort of weird behavior and let you know!

Would it be possible to build this fix and rebase off of 3.0.0 (or is this build basically that and there’s no real reason to)?

1 Like
#58

pretty sure it should have everything from 3.0 but i’ll make a new build tonight just in case and will post it here.

1 Like
#59

from the initial testing by @jlmitch5 and @xenus_dad it appears the latest fix addresses the issue with dropped keystrokes on some vortex keyboards.

here is the fix applied to the latest official 3.0 release (it will show TELETYPE 3.0 KBD FIX when booted):
teletype.zip (165.6 KB)
teletype.hex (561.0 KB)

@desolationjones @jamescigler it’d be great if you could try it as well!

6 Likes
Teletype ergonomics - firmware fix?
#60

Awesome, I will pack up my keyboard when I leave work and get the firmware loaded tonight/tomorrow. Thank you!!

1 Like
#61

It works great!!! I tried my fastest typing and no dropped key strokes!
Thanks so much for this @scanner_darkly , working perfectly with Vortex Race 3.

3 Likes
#62

awesome, thanks for confirming!

#63

now n=2: the new f/w works great with my vortex race 3! is it the same tweak as your modified main.c above?

1 Like
#64

great!

and yeah, it’s the same fix as in the main.c posted above.

#65

IMG_5979
IMG_5979.jpg3839×2879 6.6 MB

I really like using my Unicomp with its buckling spring switches, the only downside is, it doubles the size of gear I need to carry to performances. Yet still, I consider bringing the keyboard alongside with me because I find the loud click-clacking noise of the keyboard as a beautiful accent amidst quiet moments of a performance.

15 Likes
#66

Heyo, I’m looking for recommendations on a compact mechanical keyboard for use with the Teletype. The Happy Hacking boards are some that I like (and I better for how much they cost…) but they lack the function keys which I’m finding to be too handy to go without. The world is flooded with unicorn colored rave baby keyboards now that they’re popular with the gaming crowd and it makes the search for something with a more laid back look rather tedious :slight_smile:

I may just punt on the search and grab a wired apple keyboard, I don’t mind those and they’re nice and small…

#67

Vortex Core is about as compact as you can go. I know a few people use them for Teletype. I have one but don’t have Teletype so may be parting with it soon if you’re interested.

Moving up a size for me would be something like the Vortex Pok3r.

up from there would be the Race 3

or even Tab 90. Technically compact but basically just a full keyboard will all the spaces removed.

Edit: obviously that’s all just one manufacturer, the website I linked allows you to filter by size and what not, so there are more affordable options and crazy more expensive options.

3 Likes
#68

Fantastic website, thanks for sharing! Looks like they have quite a few models and give the option to choose the switches in them which is something I’d appreciate!

1 Like