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

#236

So I just had an idea and would be curious if this would work the way I’d like. From my understanding the Intellijel XY 1U module works as a TRS to i2c converter. Would it be possible to have two different cases with XY modules in each, connect them via TRS cables and effectively link modules between cases i.e. have Teletype in one case, connect i2c to XY, patch a TRS to the other XY in a different case that has an i2c connection to Ansible? I believe there would be a specific order the cases would need to be powered on and they would need to be connected prior to powering on but would that actually work?

#237

Was reading through the documentation for the new Intellijel CVx module and… it talks I2C!

If it’s implemented in the straightforward way (an I2C DAC and some jacks) it could make a simple expander for Teletype etc :thinking:

I couldn’t find any specific spec on resolution, but probably better than 8-bit? Output can be either 0-5V or +/-5V according to the configuration app.

1 Like
#238

hi! hope these questions aren’t too silly—my system contains 1x crow, 2x ansible, and (soon) 1x just friends. looking forward to getting them all i2c’d together…

  • would crow provide enough power to the whole chain, or do i need to put together something like this?
  • i assume each module only has one set of hookups. would i need to buy or create a cable w/ multiple connectors, or again use the above busboard? i only thought to purchase 1:1 cables.

cheers!

edit – woah hold on does every module have dual connectors?? could i just daisy-chain from module to module, using crow as my first link and power source?

#239

yes, crow should provide enough power.

not every module has 2 sets of connectors but you can take advantage of the ones that do, and daisy chaining is actually the recommended way to connect.

1 Like
#240

gotcha! i understand now that all 6 connections are needed, haha. for the above setup (1x crow, 2x ansible, 1x JF) would you recommend i grab a multi-connector 6-pin cable, or do i have enough connectors to go around w/ only 1:1 cables?

#241

i would check your modules - i’m not sure if there are different revisions that would have different number of pins, so don’t want to give incorrect advice.

1 Like
#242

Followup on the new Intellijel CVx module - got a reply from Intellijel with the details:

  • DAC is an LTC2609 quad 16-bit I2C DAC
  • module also contains an EEPROM containing calibration information

Double-checking that part number - I suspect the part is actually the LTC2605 because there would need to be two LTC2609 each with their own address :thinking:

Unfortunately there are some address collisions, based on this list.

#243

Sorry if this is obvious, but I bought 15cm and 30cm jumper cables. Is that “short”?

But if Crow is acting as leader, do I have “enough” power for both a JF and a W/?

#244

If it’s just those 3 modules, you should be fine. Newest versions of W/ and JF also add some pullup current, so they help bus stability as well.

I don’t have empirical numbers of what is good enough, and what’s not, but perhaps we can make a simple spreadsheet to help calculate this?

2 Likes
#245

Hardware revision or firmware version?

1 Like