#216

teletype is an i2c leader, and you’re using ansible in the leader mode, so you’ve got 2 leaders sharing the same i2c bus - this configuration is not currently supported, you can only use one leader at a time.

#217

Thanks @scanner_darkly. Yes, I’ve noticed this. So I guess the TXi’s are only useful to control internal parameters of the Teletype, but not, for example, to control the velocity of different voices of the Just Friends module while senquencing it from Ansible via I2C.

#218

there is a workaround - instead of running ansible in the leader mode, change it to the follower mode, use gate outputs from ansible to trigger teletype scripts, and in the scripts read CV values from ansible via i2c and pass them to just friends.

2 Likes
#219

Hello smarter people than I,

I picked up a tesseract sweet sixteen and must admit I can’t figure out what to do with it without a Er301 or Teletype. Can it be linked to an Ansible or JF with IC2? I also have Norns and Crows! Any Ideas or advice would be amazing. So far I have just been using it as a fader bank for CV offset. I have not been able to get the CV to Midi to work so its kind of taking up space. I feel the Sweet Sixteen has great potential but when it comes to IC2 and programing I get a little lost.

Would love to hear about anyone using it in interesting ways that a non programer could do/understand haha!

#220

I don’t think there are direct faderbank interactions for Just Friends or Ansible, but one of the I2C crew might be able to put me right.

Have a look at how people are using desktop 16ns for comparison. A thing I like doing with the CV outs is using them as a kind of macro controller: what are they key interactions in your patch? What would be like if they were all broken out to a single space, a bit like an Ableton Rack’s macro knobs? Just taking controls scattered across a modular rack and locating them in a single place can be very powerful.

There are a few 16n threads on lines, and they come recommended for use-examples.

#221

Just Friends, w/, Crow and Ansible connected to a TXb. Each one is connected to a one of the two groups that repeat down the TXb.

Crow can talk to Just Friends and w/ fine but not Ansible. I am sure this is down to follower/leader but I am a bit stuck on what to change.

I am also trying to get the print the value of a single 16n fader connected to the TXb. With this I seem to be struggling with syntax to print the value and also pull ups and follower/leader.

If someone can suggest how to get this lovely lot working I would be very grateful.

#222

if you want crow to talk to ansible then yes, you have to make sure ansible is in the follower mode.

1 Like
#223

Having read the docs a few times I can’t seem to get to that config page as per the instructions.

Any idea on the 16n too?

#224

the leader/follower ansible config is documented here: https://monome.org/docs/ansible/advanced/
can’t really help with the other questions as they are crow specific - one of crow threads might be a better place to ask!

1 Like
#225

I went to update firmware (even though I think I already did) and after sticking in the USB-A to USB-A my running Crow application just worked and starting pulsing triggers on Ansible. No idea why but that bit is sorted now and I have 16n working too - again slightly randomly.

#226

Still having issues with i2c chain

I have:
Ansible
Crow
Just Friends
W/
DistingEX
Sweet Sixteen

All connected to TxB so each device is attached to a separate group on the TxB

So from top down

connection
blank 3 pins
connection
blank 3 pins

etc

Ansible and W/ refuse to work but everything else seems to play together fine. This happened the same when I was piggybacking - thought the TxB would help so must be something else.

I clearly have the cables connected okay as Crow gives errors if that is the case.

Any ideas?

#227

try enabling/disabling the i2c pullups on the disting, then try removing modules one by one. don’t know if sweet sixteen allows controlling the pullups, try that too. try with txb powered and not. basically, it comes down to experimenting until you find a set up that works reliably.

also worth asking in a crow thread.

1 Like
#228

Tried all combos and no joy. It seems the disting was responding on MIDI mappings so i2c isn’t working on that either. Have crossposted it - thank you

#229

another option is to start with a minimal working configuration, like ansible/just friends, then start adding other devices one by one.

1 Like
#230

I’m trying to wrap my head around how i2c and “powered” bus boards work. My question is really, will this work? I have four connectors on TT but want to connect Crow, TXo, TXi, JF and W/. Is it ok to daisy chain these via the dual connectors in the modules or will I need one of those backpacks for TT?

modulargrid_1386277
modulargrid_1386277800×683 134 KB

1 Like
#231

daisy chaining is actually preferable to a star configuration.

that’s a lot of devices for one i2c bus, you might need to play with pull-up values by installing the latest just friends firmware (which enables the pull-ups on just friends) and turning them on/off on crow.

1 Like
#232

Hi!

I’ve just received Ansible and Just Friends modules. I would like to connect Teletype, Ansible, TxO+ and Just Friends using a daisy chaining configuration, but I’m still a noob regarding i2c.

Here’s a picture:

i2c daisy chaining
i2c daisy chaining4000×2965 2.15 MB

Are those connections correct?

I’ve tried to connect GND to GND, SCL to SCL and SDA to SDA. However, I can’t see these labels on Just Friends PCB board. I especially doubt about this connection but I’m not sure about none of them…

#233

The pin order on Just Friends is the same as teletype, ground marked by the white stripe on the pcb - the pins nearest the top of the module.

2 Likes
Mannequins Just Friends
#234

Thanks, Trent!
Is a correct daisy chain configuration?
I used to use a star configuration with everything connected to Teletype…

#235

I think I got it. Nothing broken, all working as expected :sweat_smile:

Well, I’ve just tested i2c connection between Teletype and Just Friends, but those are the first and last modules in the daisy chaining configuration, so I think Ansible and TXo+ -which are in between- can communicate via i2c with Teletype too.

Now I have homework: Just Type Studies…