Has anybody tried to use the TXi alone without TELETYPE to send I2C messages to, let’s say, an ER301? I’m looking for a slim CV generator or I2C controller, just to control other devices, specially the ER301. I just need a device in 4hp format with 2-4 pots that can create voltages, and the TXi looks perfect for this. I guess the firmware needs to be changed to work in standalone mode … Just guessing …

You would need crow for this, the expanders can’t be I2C leaders as far as I’m aware. But with crow you can code the behavior of TXi, it’s super neat!

Looking for confirmation on a fix I have the impression is pretty common. TxI not working. Zip ties did the trick for a minute, but no longer.

I just need to solder that one connection up, is that right?

Hard to tell from your pic but if that joint is busted then it indeed needs to be soldered.

Thought so!

And you’re right – pic bad.

Thanks!

you would still need something to provide pull-ups and power to the i2c bus (another device connected to the bus that can provide them, like 16n or txb or disting ex or crow), if you do then you can take advantage of the alternative firmware i did for telexi that does exactly what you’re asking for: Telexi er-301 control

1 Like

Thanks @scanner_darkly! Would Ansible be able to provide pull-ups and power to the TXi?

no, unfortunately. if you have just friends, you could try with that using the latest jf firmware.

When used as an extra 4 triggers/4 cv outputs via i2c, what is the difference between Ansible and TXo? TXo seems to offer more possibilities, but I can’t find what exactly. Thanks.

TXo CVs can output LFOs and envelopes and can be quantized to scales. TXo triggers can be set to clock rates.

Ansible outputs function identically to Teletype outputs.

2 Likes

hello I’m having difficulty getting my txo to oscillate
it used to work,
now it does not
should I try to reinstall firmware?
thanks

Probably not firmware if everything else is working properly. Are you setting a CV value first? This example from the Teletype manual causes an audio-rate note (A440) to oscillate between +5V and -5V.

TO.CV 1 V 5
TO.OSC 1 N 69

Without a CV value, It won’t emit a signal. Also, if you are playing around with envelopes in this context, know that they dampen the CV signal until they are triggered.

Yes I am assigning a cv value
Cv works and gates work but it will not oscillate
Or do lfo
It used to work fine
I was messing with the envelopes a while back do they store/set themselves after shut down
Maybe that’s the problem ?
Thanks

Try triggering the envelopes manually by typing this in:
TO.ENV.TRIG <1-4>

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.

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

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?

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

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

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)