#137

Thanks, I built a txb recently for connecting the faderbank properly. Also connected Ansible TXO TXI Crow JF and ER301 to TXB and powered it from the busboard, TT froze. Just connecting TXB (powered) over i2c to t TT, TT froze and wouldn’t boot. The backpack I built previously seems to work more accordingly and as you stated it’s a pretty straightforward build, what could go wrong (TXB is in fact the backpack). The puzzling thing is that things will work for some time but all of a sudden TT will freeze up and I have to power down. Cables are short and connected as they should be, some are daisy chained. I’ve just updated Ansible and TT to the firmware you pointed out, perhaps this will solve the issue. Should you have other advice considering the above, please let me know.

#138

Hey everybody. So, thanks to finishing my TXo and TXi builds this week, I finally got my rack all built out. This is what I ended up with, choosing to have a TT be my initial sequencer, but also having a crow in there for good measure. Everything laid out looks as so:

image
image1121×600 120 KB

I put my i2c ribbon cable together where the first port originates on my (Black PCB) teletype, passing through each of the modules. I was lazy, and didn’t want to do one long ribbon cable, so, i Wired everything as so:

TT; TXi; TXo (this one, I have one set of pins be the final of a daisy chain from the TT and the start of a second daisy chain); crow; teletype; w/

For some reason, it appears as if my TT has some real troupe talking to my JF. Signal begins to falter pretty badly, and often times no signals reach JF at all.

I am curious, with this length ofi2c, would it be best if I had a powered bus board? Was my daisy chain breaking at the TXo the issue and one long ribbon cord would work? Should I love the TXi and TXo to the other side of the TT and have them each going out their own way?

If anybody has some thoughts I’d appreciate it!

#139

This configuration I don’t think should be a problem for a black PCB Teletype, I’ve used this many devices successfully in a larger case. Probably try troubleshooting your connections individually, seeing if you have problems with crow -> JF, etc.

What do you mean by first and second daisy chains? Separate ribbon cables?

1 Like
#140

In regards to testing, the crow worked just fine with JF. After I did that, I stopped my crow script (awake on my norns) and the JF script began working… for a few minutes before the signal clearly died out and the JF went quiet.

But yeah, the daisy chain I’m mentioning is two different ribbon cables, one connecting the TT, TXi and TXo. I then have a different cable going TXo, crow, JF, and w/

I’m guessing this would most likely be prevented with one ribbon cable, but wanted to see if this distance was too much for the i2c before going in there and moving all my 6pin connectors to a new single cable.

#141

Hi All,

I have just hooked up some modules with i2c fo the first time. Here is the chain order:

ansible > ansible > crow > w/ > just friends

I have used crow to connect to just friends over i2c with Norns and it works great but I am having trouble getting any results from Polyearthsea running on the Ansible that is next to crow in the chain. I have made sure the pull up resisters are on on the crow. I have a few questions. Thanks.

Does the chain look okay?

Is having two ansibles connected together okay?

Is there a crow command that will make crow list which modules it sees on the i2c chain?

#142

yeah having two ansibles connected should be fine, and your chain looks fine.

it’s likely related to crow. check this: Polyphonic earthsea for trilogy/ansible and er-301/just friends/txo

if that doesn’t help, see if disconnecting crow fixes it. i haven’t had a chance to look more deeply into why having crow on the same bus interferes with polyES and orca’s heart running as i2c leaders.

1 Like
#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