#1652

Finally got to play with the TXo and TXi I’ve had packed away.

I LOVE the TXo! I’ve had lots of fun so far jamming with just two outputs oscillating. I have yet to understand what’s up with the wave tables - I don’t have a scope. Anyone else notice there are sizeable portions of the some odd 16 thousand values of WAVE that are just silent or close to it? I guess one could take advantage of it and use these portions of the wavetable like a pseudo VCA.

I’ve developed a small plan to contain the Teletype, TXo, and TXi my small Doepfer desktop skiff, along with some mixers, lfos, a quad vca, 2 filters, an STS, a DLD, and a Dervish fx unit.

Falling in line with my switch to “building instruments” with my modules this is unit going to be for ambient stuff.

#1653

I was wondering if it‘s possible to send a txo osc or envelope over i2c?!

e.g. can I send a lfo to the er-301 via i2c?

1 Like
#1654

I don’t believe so. I’m not sure, but I doubt the I2C protocol is designed for real time or near real time data. Have you already used up your CV inputs?

#1655

No, hadn’t the case that all inputs were used… till now…
I was just curious!!

#1656

I’m wondering out loud here but I feel like TXo and TXi could be improved with some command aliases.

Eg.
TI.PARAM -> TO.P
TO.OSC -> TO.O
TO.ENV -> TO.E
TO.ENV.TRIG -> TO.E.T

I know folks are big on readbility however, given that TT has very few characters available I see Aliases as being essential and helpful. Do Ultra short Aliases go against some TT design ideas? There are just so many “shortenable” commands within the TXo TXi command base that it could have some great benefits, mainly that scripts would be faster to type, especially in a live coding situation, and scripting space could be better utilized especially for anyone with more than one expansion unit.

Come to think of it there are quite a few 5 letter commands that could be shortened in the base TT feature set, too.

1 Like
#1657

Is there any place i can see how the Telexi works with crow?
Are there special commands in crow or do i need to get the knob and jack states through a metro function? (as is with something like just friends)

#1658

Apologies if this has been answered in this thread. I’ve been scrolling through a few and looking at the github page for the expanders and have a couple of questions.

I managed to snag a TXi and TXo and they should be here next week. I’ve got a Teletype I purchased new from monome in the last few months, so I’m assuming it has the most recent firmware. My question is this: Should I just be able to connect the TXi and TXo to the Teletype and expect them to work? No idea what to expect and I realize that I may not be providing nearly enough details, so let me know if that’s the case and I can return with more info later.

(EDIT: TT Firmware is 3.1.0–just booted it up)

Second question: I don’t have the Telex units on-hand, but I’m curious if I can daisy chain them as I’m connecting my JF to Teletype with one of the i2c ports.

Thanks!

#1659

daisy chaining is recommended, and there are double sets of headers on telex modules for that. should likely be fine to run txi + txo + if, especially using the latest jf firmware. if i2c connection isn’t reliable then consider using an i2c backpack.

1 Like
#1660

I don’t think the i2c backpack is necessary with the latest Teletype.

#1661

Hello.

I am not able to have the exact voltage with the inputs of my Txi.
For exemple, with nothing plug, when I type TI.IN 1 it return -5 (not 0), I have done the calibration procedure but nothing change…
If someone have an idea, it’s welcome
@bpcmusic , thanks

#1662

Slowly navigating my way around TT and the TxO. Loving what a powerful pair they make! :dizzy:

https://www.instagram.com/p/CLAj5gOhgdt/?igshid=qpl8inpuzn4k

#1663

I’ve been wondering myself. I’ve got two TXo to build and would love to have them sound nicer and run the TXo+ firmware. Is the 4.0 a direct swap out for a 3.2? it’s the same form factor. Could I use it without buying the teensy power helper board that was required for the 3.6?

#1664

No you can’t … the software package is too big for a 3.2

#1665

Hey everybody, just installed my TXo. The command list makes reference to the “full description” (for scales, etc), can someone point me in that direction? Can’t seem to find it.

#1666

@onlyruin All is here :blush:

#1667

Beautiful. Thank you!

1 Like
#1668

Which part are you replying to?

Are you saying that the size of the txo+ software doesn’t fit the 3.2? That makes sense.

I’m more curious if the 4.0 can be used in place of a 3.6 without the additional power board.

Some investigating of my own shows the 3.2 is 5v tolerant while the 3.6 and 4.0 require 3.3V (3.2? One of em). I suspect the power helper board is for 3.3V specifically. If anyone can back up this notion that would be helpful.

#1669

No it will not work because 4.0 uses another software architecture than 3.6 so the whole has to be rewritten…

1 Like
#1670

Ah sure that makes some sense.

My figurings about the teensy europower helper were wrong - all it does is delay the teensy a bit while power is sorted. I’ve ordered two teensy europower helpers to go on my 3.6 boards when they arrive.

#1671

TLDR: PSU bad. txo+ with Teensy 3.6 not OK. Teensy 3.2 OK.

Hello!

I’ve built two txo+ modules that I’m connecting to a Teletype via I2C just using regular dupont cables. I can address the trig outs and cv outs of the txo+ modules, but it seems like they reset after a short while, maybe 2-4 seconds. Both modules exhibit the same behaviour. Can this be a problem with the I2C bus?

The teensies (3.6) have been programmed with the TELEXoPlus v021B firmware.

I used another type of resettable fuse than in the BOM initially, but tried switching to 4.7r resistors. It seems to take about 15 seconds or so now before it resets again, but that might not even be related to the fuse switch.

UPDATE: Tried using a Teensy 3.2 instead of 3.6, and now it doesn’t reset anymore. But I would like to use the 3.6 to run the txo+ firmware (and understand the source of the problem).

Using an version 0.18 on the Teensy 3.6 didn’t fix the problem.

TODO: I will try the modules with another power supply.

RESULT: My power supply seems to be the culprit here (Pittsburgh Modular Cell 90). I measured +14.6V on the positive rail. OK! Case closed (hopefully).

1 Like