Drum roll… after many months and much code, we present the final version of Teletype firmware 2.0!
Firstly I’d like to say thanks to all the people that tested and offered feedback in the beta thread. In particular:
(Profuse apologies to anyone I’ve forgotten, I think I started working on the code for 2.0 at the end of last year and things are getting a bit hazy… even more so with recent developments…)
Anyway, here is the release, please heed the warnings. Firmware update instructions are here.
Teletype firmware 2.0.0: 18th July 2017 (
teletype-2.0.0.zip (444.5 KB)
Flashing it will erase all your presets!
Please backup any
ttXXs.txtfiles on your USB stick, they will be overwritten.
You will need to power cycle your Teletype after flashing for the keyboard to work again. Wait until the normal Teletype prompt appears before rebooting (nothing bad will happen if you forget though).
(Also available on the official release page.)
Changes since 1.4
Here are the major user visible changes since version 1.4:
- Sub commands
PNversions of every
- Telex ops
(breaking) removing the
II MP.PRESET 1will become just
MUTE x y
(breaking): remove unused Meadowphysics ops:
(breaking): rename Ansible Meadowphysics ops to start with
- Using the
F10keys to trigger scripts. Also
alt+Fkeyto jump to editing the relevant script
NUM LOCKto jump to the pattern editor
PRINT SCREENto jump to live mode
- No more leading space before
- Emacs/Unix style keyboard short cuts (
ctrl-A, etc), delete forward with
- Limited script recursion (max recursion depth is 8) including self recursion.
- Using a USB stick at any time (not just boot up)
- Metro scripts limited to 25ms, but new
M!op to set it as low as 2ms (at your own risk)
Plus so very many under the hood changes. (And probably even more that I’ve forgotten as well.)
Changes sinces 2.0rc2
The only change since 2.0rc2 is the change of the version number on the startup screen. All previous beta releases are still available on the beta thread.
The zip file also contains documentation for all the OPs as well as some of the new features. It’s not yet comprehensive, it’s lacking the introduction that the current documentation has. Contributions welcome!
(As an aside, the documentation is capable of being generated as an HTML file too, and it would be an interesting project for someone to take that and improve upon my (bad) CSS and add some navigation so that we may place it online.)