#1632

Hi @BKCP . Yes you have to connect i2C to i2C. I don’t have my system under the eyes but if my memories is good adress is for the jumper for set the Tx1 and Tx2

1 Like
#1633

Thanks @Mad86, Ive tried i2c to i2c and I am unable to communicate to the second txi, ops that refer to TI.PARAM (5-8) or TI.IN (5-8) all return zero. If I only have one txi on my i2c bus it works fine, so I know both txi are working properly, but the minute I put two txi on the same i2c bus (teletype-txb-txo-jf-w/(2x)) the second txi returns all zero’s and the first one starts sending strange values on occasion. So what are the adress jumpers for? do I connect those between the two txi? How do I set each txi to its own address? @bpcmusic any advice?

1 Like
#1634

@BKCP you are welcome :blush:
here all the instructions https://github.com/bpcmusic/telex#addressing-multiple-telex-modules
You should find all you need.
For me I use (for 2txi) TT bus and it’s work perfect.
In past I have made some test and it works also daisy chained.
You have to plug i2C 1 to your TT and from this Txo i2C 2 to the i2C 1 of the other Txo.
I hope to be clear enough.

1 Like
#1635

[SOLVED] I found some old documentation on github, it mentions the jumpers were in a little plastic baggie the module shipped with, placed it over the first row of two address pins and am now able to address the second txi. I mistook the term “jumper” to mean a cable like i used for i2c

Thank you for all the help @Mad86 but unfortunately chaining i2c the way you described was something i tried and I still don’t get the second txi to respond. It was the first thing I had tried because Chaining i2c is how I have other modules linked in my system and they work fine, but two txi on the bus and only one will get recognized. I checked out the git hub you linked and it refers to placing jumpers on specific rows to designate the multiple addresses, but it doesn’t mention what you connect the other end of the jumpers to so Ive tried a lot of combinations to just trial and error this but nothing works, Ive sent @bpcmusic a message and hopefully he could shed some light on it.

2 Likes
#1636

@BKCP Ah ok perfect :ok_hand: it’s work.
I am happy to help.
Have a good fun :wink:

1 Like
#1638

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 …

#1639

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!

#1640

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?

16065819033507087420291761900817
160658190335070874202917619008173000×4000 1.93 MB

#1641

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

#1642

Thought so!

And you’re right – pic bad.

Thanks!

#1643

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
#1644

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

#1645

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

#1646

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.

#1647

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
#1648

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

#1649

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.

#1650

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

#1651

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

#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.