are you able to test with something else connected to teletype via i2c?

1 Like

turns out I was connecting the i2c cable to the wrong header, specifically the one with 6 pins, which I assumed was the correct one to plug it since the i2c cable has 6 pins. connected the cable to one of the 3pin headers and working like a charm!

couldn’t find anything in docs anywhere about this, so perhaps it should be added for 100% clarity’s sake :nerd_face:

1 Like

Sounds like you didn’t get one of the manuals with the module from Control. You can find the latest full manual here:

Lots of helpful stuff in there.

@rikrak and @scanner_darkly - thanks for stepping in to help!! :slight_smile:

@n-So - hope you enjoy your TXo. For others who are interested, the production run is getting ever closer. Unit QA, Teensy prep, and boxing left to go… :slight_smile:

9 Likes

Also … don’t forget the TELEX section of the full Teletype manual. Command reference with some examples and helpful hints there too:

TXo:

https://monome.org/docs/modular/teletype/manual/#telexo-teletype-output-expander

TXi:

https://monome.org/docs/modular/teletype/manual/#telexi-teletype-input-expander

7 Likes

Is there any timeline for the telexi-modules’ restock? Thanks!

2 Likes

Soon. Soon. Soon.

Doing QA and prepping boxes. Making i2c cables. Stuffing screws into little baggies. Also, waiting on a final Teensy order.

I’ll announce the date and time things will go on sale here a few days before. You can also sign up for automatic notifications at my store.

Really sorry to take so long. This build has been gargantuan beyond my expectations. Believe me - no one wants it done more than me. :slight_smile: :slight_smile: :slight_smile:

16 Likes

Absolutely no worries - I haven’t even kept track until now, so sounds great to me :slight_smile:

1 Like

I’ve really been enjoying the TXo. Still learning the many things it adds to Teletype. Here’s a little generative two voice jam with the TXo providing clocks via its independent metronomes, envelopes, and oscillators. Oscillator wave forms are randomized per voice and note. Great fun!

12 Likes

I have a question about i2c and the time it takes to communicate. I had some issues with the communication between Teletype and Just Friends, where commands were sometimes being dropped if I rapidly sent commands (e.g. in a loop).

I currently have two TXos and no such issues. However, I’m thinking about picking up at least two more with the next run and I’m wondering if there could be similar issues as I had with Just Friends and, more generally, what ballpark the latency would be in when looping over all outputs of 4 or 5 TXos and setting them to new values. Does anyone know an estimate of how long it takes for teletype to send an i2c command to a TXo?

My main application is a rather complex step sequencer (with lots of outputs) and so tight timing is sort of important. I have no issues so far with two TXos, just want to make sure that there’s nothing to worry about with twice as many :slight_smile:

it should be very small. i have 4 txos so i’ll measure it and report back (traveling now so won’t be able to get to it until monday though)

1 Like

Thanks and no worries, it’s not urgent at all.

I’m all torn up in production mode, so I don’t have any stats handy either. I remember there being a discussion about this in the past on the forum, but I have been unable to search and find the relevant posts.

My experience is that communication is quite swift. I only was able to perceive a flam when I had 8 TXo connected and was sending a number of commands to each one at the same moment. I was torturing it on purpose. :slight_smile:

Something like:

M
L 1 32: TO.TR.P I
L 1 32: TO.OSC.WAVE I RAND 45
L 1 32: TO.OSC.N I P RAND 32
L 1 32: TO.ENV.ATT I RAND 30
L 1 32: TO.ENV.DEC I RAND 250
L 1 32: TO.ENV.ACT I

In the example, there are a lot of commands between the PULSE and the ENV.ACT commands, which could put a delay between them. It all comes down to how many sensitive commands you are trying to send at any given moment.

I’ve been able to solidify the timing by using the DEL operator to better fix the timing of the things that produce the sounds and then do the setup in the intervening window. For example:

8
L 1 32: TO.TR.P I
L 1 32: TO.ENV.ACT I

M
DEL 15: SCRIPT 8
L 1 32: TO.OSC.WAVE I RAND 45
L 1 32: TO.ENV.ATT I RAND 30
L 1 32: TO.ENV.DEC I RAND 250
L 1 32: TO.OSC.N I P RAND 32

This gives the setup the time to take the time it takes and the ā€œsound activatingā€ commands are sent as closely in succession as possible. (The length of the delay depends on what you have going on. I just picked 15ms for this example.) Think of it as the breath that wind players take before the note sounds.

1 Like

tested with 4 txos. with nothing else running doing L 1 16: TO.TR.P I the last (16th) trigger output was 2.5ms behind the 1st. in similar test with CVs it was 3.5ms.

didn’t run the test multiple times, so this is just from a single measurement, but should give an idea.

6 Likes

That’s in line with some other measurements I’ve made.

2 Likes

Thanks for your efforts everyone!

1 Like

Hi, I’ve finished building two TXO with Teensy 3.6, Europower Helper and 110p caps instead of 180p.
I’m testing them on my work bench before installing them in the main case and connecting them to the Teletype. The voltages are correct but the modules don’t show a sign of life yet but maybe that’s normal (?) Are the LEDs supposed to light up or something ? There’s no LED on the Teensy either. Thanks.

There is no ā€œblink onā€ behavior for the module - so you wouldn’t necessarily see anything unless you sent it a command.

[EDIT]
On closer read - it is clear that you built the Europower helper. I’ve removed my notes about that.
[/EDIT]

So…have you connected it to a Teletype and sent it commands? Knowing more about what you have tried would make it easier to troubleshoot. :slight_smile:

1 Like

Thanks for your reply ! Yes, the euro power helpers are in place. I was imagining a LED routine on boot, that’s why I was in doubt but now I guess I just have to test it with the Teletype :slight_smile:

No it’s not connected to the Teletype, I wanted to be sure the module works before plugging it in the main Eurorack case, but I’ll try tomorrow (I need to make DuPont cables) and I’ll post with details if anything goes wrong. Thanks again :wink:

1 Like

Yeah - i had it in there once, but the Teletype starts so quickly that it just didn’t make sense to do anything but be ready to accept commands (especially the init commands). That is why you need to ā€œhackā€ your Teensyduino installation to reduce the start time if you compile the firmware yourself (as mentioned up on the GitHub Repo).

1 Like