Teletype 3.0


Ah! I didn’t realise that “I” affected the Loop step!

I misunderstood the Manual entry for “I” from which I inferred that the step of the loop overwrites the value of “I”:

get / set the variable I, this variable is
overwritten by L, but can be used freely
outside an L loop


basically, L A B: ... could be expanded to this:

  • set I to A (loop start), this is what’s meant by “this variable is overwritten by L”
  • does I exceed B (loop end)? if so, exit the loop
  • execute the loop command(s) (you are allowed to assign a different value to I here)
  • increment I by 1, go to step 2

for simplicity sake i’m only showing incrementing loop, but you could have a decrementing loop as well (by setting A to be higher than B).


Many thanks for the explanation - it makes sense now.

I will ponder “I” for a while, in order to avoid derailing the thread any further… :smile:


it occurred to me that the “resume screen on boot” feature would be nice to put back in, now that there’s also a grid screen (and because i just got an e-mail asking for start-in-tracker-screen to be reinstated)

i’ll try to get to it in the next week, but if someone else has time to spare you’ll help other new things get released on schedule :wink:


Yes, this would be great, especially for those of use who want to use it sans keyboard in a live performance.


should be an easy fix, i can add it to next beta. on related note, i’d like to also add ops for choosing what screen to show - this will be mainly so that you could control it from a grid without having to replug keyboard, but they could also be used in the init script so then you could have different screens shown by default for different scenes.

could be something simple like SCREEN x where x would be:

0 - live screen
1 - live screen with variables
2 - live screen with grid visualizer
3 - full screen grid visualizer
4 - tracker view

Teletype 3.+ feature requests and discussion
Monome ecosystem firmware development backlog

i’m totally into this!

1 Like
Monome ecosystem firmware development backlog

Yes yes yes in 20 characters.


Is there a description of how to grab the documentation from Github for normal citizens somewhere?


you can see markdown files here:

i don’t have the toolchain for docs set up yet, hopefully somebody who does could generate pdfs and post them here?


If I understand correctly, only additions from 2.2-> 2.3 are the grid ops, eh?


quite a bit more… the top post has all the details!

1 Like

I had a crack at generating the latest docs, but got some errors which I need to fix:

RuntimeError: Pandoc died with exitcode "2" during conversion: b'--latex-engine has been removed. Use --pdf-engine instead.\nTry pandoc --help for more information.\n'

I got the html version of the docs out OK, attached below. (291.4 KB)


Mr. Ether, That is amazing! Thanks so much!


I am on Beta 2.3, 3D2CCB9.

My Teletype is locked up, through multiple power cycles. Unfortunately I don’t have a backup of the scene that’s running. I do know that I was using a lot of i2c commands in the INIT scene. 4 TXi knobs were controlling the wave shape of 4 LFOs on the TXo.

When I power the unit on the screen comes up normally, and I can see that the TXo is outputting the LFOs. They are, however, unaffected by the TXi knobs. I can get to the bootloader, so I’m sure the button is still working. I am guessing that I should just reinstall the firmware, but I wanted to ask for advice here first.

Any ideas? @bpcmusic @scanner_darkly or anyone else :slight_smile:

EDIT: details…
There are 8 connections on my i2c bus. I am using a powered backpack, and the runs are fairly short. Also the TX modules are running the latest firmware.


when it happens, is teletype completely unresponsive? what else is on the i2c bus, do you have er-301 connected by any chance?


When it happens the Teletype is completely unresponsive. I do have an ER-301 on the bus, but was not actively using it. My bus is; 2x Ansible, Txi, Txo, Earthsea, Orca, Just Friends, and the ER-301.


can you try disconnecting er-301 from the bus and see if it still locks? there was an issue with er-301 using the bus during booting up which would cause tt to freeze, especially if you have any i2c commands in your init script.

1 Like

Back in business! Thank you for the assistance. I should really back up my scenes now :smiley:

1 Like

it’s a known issue, @odevices mentioned he was going to fix it a while ago so the fix might already be in the latest version. unfortunately i didn’t have the time to update my er-301 yet, if somebody could confirm whether it was fixed it would be great. @laborcamp have you had a chance to verify this?

1 Like