#156

i’ve also updated the list of devices.

3 Likes
#157

I went ahead and added Crow in there, as well as corrected some outdated info in the leader/follower questions/answers section. :slight_smile:

2 Likes
#158

good catch!
i’ve also cleaned up the firmware list a bit (don’t think we need to include telexo/er-301 etc there really)

edit: while doing the above accidentally removed ansible 3.0 - sorry - re-added!

2 Likes
#159

Looking to find a cable to connect Teletype -> Ansible (with future I2C devices later) and ran across this:

I believe the 3-pin JST connector on 0.1" spacing used here will interoperate cleanly with the 0.1" headers on Teletype etc and allow for daisy-chaining through the neighboring set of pins.

Anybody tried this kind of connector? I didn’t see any mention of similar ones in the user’s guide to I2C’s cable section but those threads are pretty vintage.

DIY i2c cables
#160

That should do the trick!

1 Like
#161

we keep the thread up to date - and it’s a wiki, meaning community contribution is also welcome. i took a look and even though jumper wires are not mentioned in the topic itself, it links to the DIY cables thread which has a lot of info and suggestions.

#162

Hello, sorry if this is not the right place to post. I am having trouble with my i2c setup attempt. I have 16n, Teletype, Ansible and bpc TXb.

I have connected everything and the builds all seem to work fine. Except for when I try to get the 16n into the Teletype thru TXb

Here are the symptoms. I’m testing for 16n with FB n message … I have the FB connected to the TXb with a stereo minijack cable. I tried different ones.

  1. Ansible and Teletype work fine when connected over i2c

  2. Powered TXb to Teletype with Ansible also connected to Teletype… Ansible doesn’t respond to Teletype messages anymore, but can control Grid over USB. Teletype does not report any FaderBank action with the FB n message.

  3. Powered TXb with jacked FaderBank to Teletype ( no Ansible) . Still no FB response to FB n.

  4. Ansible to powered TXb ( no 16n in the setup) and TXb to Teletype - Ansible doesn’t respond.

My FaderBank is powered over USB and works fine with the Web editor.

Any help appreciated.

I2C questions / discussions
#163

Sounds like there’s a problem with TxB. Sorry i dont have more to offer, but you need to get everything working without 16n first.

#164

sounds like either txb is not connected properly or it does not work. when connecting to txb, make sure GND is connected to GND, SDA to SDA and SCL to SCL. also try ansible to txb and txb to teletype, unpowered, and see if that works.

1 Like
#165

Did some shopping, wrote a followup post: DIY i2c cables

2 Likes
#166

thanks @scanner_darkly.

Just to clarify, does this last test you suggest mean unpowered txb bus or unpowered ansible?

#167

Unpowered txb.

For nr. 3: Is 16n really in follower mode? Check in the web editor.

#168

yeah, unpowered txb. i doubt not powering it will make a difference but worth to try, you never know with i2c.

#169

Fairly new to Teletype and Crow, but wrote now several scripts for each module.
I’d like to have the teletype to control some aspects of the Crow, so I’m looking at Teletype as the ii leader and Crow as a follower. While I have found several Lua based example code to control a Crow via ii, I am not clear how I can approach this using the Teletype as the leader.
Would anyone of you have any example? Has it been implemented in the code base of the Teletype?

#170

It has not yet been implemented. Likely in the next minor update to crow we will add support.

#171

Seeking some guidance from folks with rather dense, multi-leader i2c configurations. In my system, I have Crow, Teletype, TXi, TXo+, Ansible, w/ and Just Friends, all supported by an i2c busboard connected to Teletype (I’ve tried to daisy-chain as much as possible).

Yesterday, as I was experimenting with a crow script for jf, while simultaneously using a couple of voices on TXo+, I kept getting the ii lines are low message in druid. It seems that the TXo+ is typically what tips things over the edge.

I would have figured that the busboard should provide enough support for the network, but perhaps not. Any other ideas?

1 Like
#172

Thanks! That explains. Would you have an estimate when this new update might be available?

#173

Total noob question, so thanks in advance for bearing with me:

Would a TXb be a sufficient solution for powering i2c in an Ansible + JF/ER-301 setup? I don’t have a Teletype (yet), and want to make sure that TXb doesn’t require TT before I order one.

Thank you, and apologies if this has been asked/answered elsewhere already!

#174

yes, that should be sufficient.

1 Like
#175

Glad to hear it. Thanks!