#143

I tried this out on a bus with: crow, W/, Ansible, Teletype (black PCB), TXo, JF and it worked fine, but if I take Teletype off power then JF doesn’t output and crow does not respond / does not connect to druid, however Orca’s Heart is still running. Wild! Pulling too much power off the bus? I seem to recall reading about crow’s pullups being designed to handle a lot of devices. Might need to figure out the UART situation on crow for this one.

2 Likes
#144

This is not very helpful but using a txb on setups of 4 or more modules using i2c has worked 100% of the times for me.

Its like a i2c multiple and you can have a few in the same i2c port, but only one can powered at a time.

Hope you get it sorted :slight_smile:

#145

Sorry for the inexperienced question, but if I have a module that has an i2c expander, would it be somehow possible to connect it to the Teletype and have the two communicate or does this require more than a mere connection?

Telex: Teletype expanders
#146

You’d need documentation of the commands that the expander module will understand at a minimum.

#147

It is possible, but almost certainly not without alteration to the Teletype firmware. As @moogah points out, you need to know the messages to send over the I2C bus, the address prefix of the remote I2C device, and then make modifications to the Teletype firmware to add support for those messages.

Whether that fits within your definition of “possible” is another matter. Technically, probably yes, but practically, possibly not.

#148

might be worth revisiting the idea of having a set of generic ops that would allow interacting with any i2c enabled device without having to modify the firmware (we would still need a mechanism to reserve addresses for specific devices, but that just needs to be documented somewhere).

here is the relevant thread: Generic teletype ops for interacting with other devices?

1 Like
#149

Topic: Backpack with new Teletype Version - aka black PCB.

This passus from the very top of this thread:
" If you have a later revision Teletype (black PCB) you should not need a powered busboard. With this version if you already have the busboad that attaches directly to the Teletype (aka Teletype backpack ) you can still use it separately from Teletype (so that it’s not powered) as a splitter. If you do, make sure unused pins can’t accidentally touch other modules or the powerboard!"
Does this mean that the backpack physically even can`t be attached to the “black Teletype”? Or does this mean that the backpack could be physically attached (as on the “green Teletype” also to the power socket) but it would/could damage the ecosystem in conjuntion with a “black Teletype”? If I understand correct the backpack should only be connected “loose” to the ii-connector, that it is not powered directly from “black Teletypes” power socket?
Thanks for clarifing before I start doing physical attempts :slight_smile:.

#150

it’ll work, but it might put the i2c lines out of spec. you can try it without fear of damage.

1 Like
#151

Just for feedback: I don`t know exactly what you mean by “lines out of spec”. The physical connections are at least as intended (no swap or twist, if you meant this) and the ecosystem with 5 modules seems to work proper. Thank you!

#152

Thanks for this resource!
A question: I should be able to connect crow to Just Friends using just a single 3-wire i2c cable, right? I don’t need a power supply or bus?
I’m trying to get JF to work as a synth in Max4live but It’s not giving me the blinking lights.
Sorry if this very novice question has been answered in the thread above. I searched it and couldn’t find anything that helped me make sense of this particular situation.
Thanks!

#153

@okyeron, can we update the top post still? Ansible should be added in under the Leaders section now that v3.0 is out.

1 Like
#154

No longer edit-able. Not sure how that works.

#155

top post is now a wiki

5 Likes
#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