#41

New Teletype owner here. Can’t get a keyboard to work with it. I’ve tried two, both work fine with my Windows boxes. Keyboard 1 likes to stick… keys just reppppppppppppppppeat at random, sometimes don’t work at all. Keyboard 2 - the one that came with the Teletype - works great except for the Enter key, which works not at all. Again, no problems on other computers

Teletype version 3. Clearly from looking at previous messages I am not alone in this. I am inclined to believe this is an inherent design flaw in Teletype. Are there any steps that I can take to get a keyboard to work with this, other than trial and error?

#42

I haven’t had issues with the keyboard that came with Teletype, so I’m not too up to date on the details, but I think there are a couple options. Some fixes have been made in recent firmwares to address dropped/repeated keys, so you might try updating to the latest beta, or waiting for the 3.1 release that the Teletype devs are planning on making soon (likely within a week or two). If you’re up to compiling the firmware yourself (I recommend this Docker image) I think you might also try tweaking the HID polling frequency for your specific keyboard and letting us know what works and for what model of keyboard. I think broadly that the trouble here probably arises from there being lots of behavior variation between different keyboards and the limited hardware resources on Teletype kind of necessitate adopting a simpler approach than full-fledged operating systems are able to use, but I also have basically zero first-hand experience with HID stacks in general or Teletype’s specifically.

#43

e-mail info@monome.org and i can send you another!

#44

Thank you everyone. Given the impending release of 3.1 I will wait on both offers. I could figure out how to do the compile but that is not something I want to spend my limited free time on. @tehn, thank you for the offer on the kbd but again I will wait a bit. Testing with a third keyboard tonight.

#45

And later: the third keyboard works. This is a full-size HP keyboard, brand new (all my keyboards come from the spares pile at work). The two that don’t are the K-1000 mini-keyboard that came with the Teletype, and another mini-keyboard from work.

Looking forward to 3.1. I will report back on these keyboards then; maybe I’ll install the beta this weekend. Very much looking forward to the output calibration as well, that was the next item on my list of things to ask about.

#46

Another happy new Teletype owner here. Well, almost happy. I also got some strange behaviour with the included keyboard:

When typing the letter T in live mode, the command TR gets displayed. Not sure if this is some kind of auto completion mechanism, but it also happens when I for example try typing the second T
in TR.TIME.

Also, when typing the letters I or P (e. g. when entering TR.PULSE or TR.TIME), the module starts switching between the different scripts.

There seems to be some other weird behaviour for different keys, but I’m not very familiar with the TT yet, so it’s a bit hard to describe.

The keyboard from my computer (Logitech K280e) seems to work fine. However, since it has a German QWERTZ-layout, it’s a bit tricky to use (and also does not fit into my little synth-corner, so I have to hold it in my hands all the time…).

So if someone has maybe experienced the same problems and found a solution or workaround I’d be very happy to hear about it!

#47

I would suggest testing the TT keyboard with a computer to see if it is a defect keyboard

if so email help@monome and I can send another!

#48

ongoing issue w/ tt version 3.0 (as others previously mention) - regardless of keyboard (i have tried a few), they all lose connectivity to tt after about an hour of inactivity and/or sporadically cease to type during a session. it’s not a big deal as reconnecting the usb cable eventually solves the issue, but is there a more permanent solution to this?

#49

Hi everyone, sorry if I start with a noob question, but I can’t figure this out and maybe a search on the forum will help, but please forgive me if I’m asking here directly, because I have actually 6 tabs on my browser with different thread open on TT. Really thousands of posts!
The problem I’m experiencing is the one @scanner_darkly reported years ago: at some moment the kb doesn’t respond anymore, it happened 2 times in a week, intense use, so I was a bit worried, because this make my brain hard to trust the module, and my brain want to be free using this lovely stuff.
So, two questions:

  1. is there any way to save the presets without a keyboard?
  2. from your experiences, how can I solve the bug I’m experiencing?
    Thank you so much

EDIT: the plug/unplug way didn’t help…

#50

please provide some information:

  • firmware version
  • teletype hardware version (black/green/diy)
  • keyboard model (if not the standard)

and that’ll help narrow it down!

#51

sure!! sorry again

  • fw v3.2.0 B0A17FE, I think this is the lastest
  • hardware is DIY (not by me) green pcb, black panel, yellow screen
  • non standard kb: TRIXES ZE44
#52

when it happens, does the keyboard stop working completely, or does it recover after some time? are the scripts still running or does teletype freeze also? also, are you running anything intensive, like super fast metro script?

the only way to save the presets without a keyboard would be with a grid, if you have one, using the grid control mode.

are you able to try it with another keyboard?

#53

Thanks for replying.
The kb stops completely to work, but tt wasn’t freezed. I tryed to plug/unplug several times but didn’t help, I tried a lot of random key bindings strokes but the kb did stay as dead, i.e. the leds for caps lock etc didn’t work anymore, it was as the kb itself was freezed.

On tt, nothing really intensive for what I remember, but - you know - I’m a 10 days old babe, I’m experimenting a lot trying to scratch the surface of this overwhelming rabbit hole, so maybe I’ve done something intensive without the intention. So kb was freezed until the next power cycle.

The bright side is this is never happened anymore until now, even with super fast metro, stupid and intricate scripts, and so on.
No grid here, and unfortunately no alternative kb.

But I think maybe it will be nice to have some strategy from onboard to save presets without a kb.
Maybe also a way to power cycle without to have the whole power bus going on / off would be nice, but maybe a little dangerous, I don’t know… Just random thoughts :blush:

EDIT: the 3 leds on kb don’t work at all when plugged on tt, even on normal behaviour, so I don’t know if actually kb was freezed

#54

it’s not always firmware related, unfortunately.

it’s difficult to support a DIY due to not knowing if it’s been built right, but here are some starters:

  • the TPS2021D chip (8soic, near the USB port) may be fried or soldered badly— that’s the chip that controls 5v current to the USB port.
  • the power system may be unstable (hard to make suggestions)
  • if you have other keyboards, test them and see if you can replicate
  • try a different euro power supply