#112

assuming the bus itself is stable yeah you should be able to run all 10. the limitation applies specifically to TXo and TXi modules - you can have up to 8 of each (imagine the kind of things you could do with 32 oscillators or LFOs or envelopes or any combination of that : ) - @bpcmusic did run this kind of setup.

for ansible you can have up to 4 connected. earthsea / ww / mp / orca only one of each iirc. pretty sure i ran at least 10 follower modules at some point.

1 Like
#113

Perfect! Thank you. I was counting the modules on your bus and got to 8 so I was wondering and wanted to be sure. Ultimately I don’t know that I want to move cases again, so I’ll have to cross my fingers that I can snag one more Txbs from @bpcmusic if he makes them again so I can connect 2 cases.

PS I’m so excited to mess use orca when my WW comes!

1 Like
#114

Is this still true with Crow?

#115

Right. That may need an update. But is potentially confusing since crow is configurable

#116

I see that Crow can be a leader or follower, but does that impact its ability to provide power?

^^ crow help: general (connectivity, device q's, ecosystem)
#117

It appears this will depend on how a particular script is configured.

So yes - how the pullups are set will impact this, but Leader/Follower is a different thing from this.

3 Likes
#118

we just dm’d but i’ll ask here to confirm

if i have crow, w/, and jf on a bus network together i guess i need to always keep pullups on the crow high…true/false?

do i also need a powered board for the bus? or does eurorack power supplied to crow have enough juice for the connected modules ii needs?

edit: nevermind…i see you asked basically the same thing in the other crow specific thread

3 Likes
#119

Oof, I guess it didn’t occur to me what was happening when people were discussing turning Crow Pullups on/off.

Since you’re only supposed to have 1 source of power, it’s scary that turning pullups on on Crow could cause damage with a Txb (or any other bus power solution like busboard jr or TT backpack) providing power to the rest of the modules.

Unless I’m misunderstanding.

UPDATE: NO DAMAGE. STOP WORRYING.

#120

No damage will be caused. the bus just might not be as stable as it could be.

#121

GREAT! Thank you. Sorry for any paranoia or fear mongering I may have caused

1 Like
#122

so i wonder, how difficult it would be to make a version of TXb or something similar that would check if rise/fall time is within a good range and indicate it with an LED?

the main reason it’s difficult to give an advice on pullup values is because in setups with so many variables there isn’t some absolute “good” value, especially when you combine multiple pullup resistors. the end goal is to ensure rise/fall time is within a good range (detailed info here). if you have an oscilloscope you could use that to analyze your bus, but if we had an easier way to measure it it could help more people with troubleshooting and deciding on which pullups should be enabled and whether an additional busboard is needed.

6 Likes
#125

quick question
is there a way to connect crow/teletype/justfriends/txi nad have crow talk to JF directly? teletype is going to be master?

#126

Damn, the problem returned… TT read faderbank values correctly and was running fine…
The next day TT froze again… I was wondering what others diy-ed to connect the faderbank jack to the i2c bus… Something is wrong with the chassis I’ve used or should I be looking for problems on the faderbank pcb?

#127

hi everyone. anyone using ER301, Just Friends, Teletype, Ansible and 16n faderbank on the same i2c bus without a dedicated i2c powered busboard? TT as master.

thanks! :slight_smile:

#128

Yes, you can have either crow or Teletype talk to Just Friends and TXi. On crow try ii.jf.help() or ii.txi.help() to see available commands. With all of these modules wired together you can send commands either from crow or from Teletype, though using both at once is likely to cause issues possibly including module crashes. In particular crow will now print a warning if I2C lines are in use and crow didn’t initiate communication.

You can check out all the schematics and board files for bpcmusic’s TXb, seems very straightforward. Any kind of disturbance in the I2C bus definitely has the possibility to freeze Teletype, but if you think it is a very intermittent problem you might want to try the most recent beta firmware for Ansible and Teletype here, which includes a patch that limits the number of retries Teletype will do for I2C operations.

I think probably this is doable with newer Teletypes (black PCB), I’ve used a similar number of devices (though not 16n) with no trouble.

2 Likes
#129

This link is broken
Thanks

#130

found it, will add redirect tomorrow: https://monome.org/docs/modular/iiheader

sorry that these older docs still haven’t been thoroughly vetted — please email all broken links to help@monome.org :revolving_hearts:

2 Likes
#131

Thanks Dan!

I found the broken link looking for info on whether I could usefully connect Crow to Ansible and W/ in addition to it already being usefully connected to JF.

I went ahead and connected them all anyway but never really found the right documentation. Weird…

Also, it seems that the Users Guide to i2c could benefit from adding a bit more detail on Crow…

Thanks!

2 Likes
#134

Dumb question but I don’t want to order the wrong thing: will these work for i2c?

#135

yes! that’s what i use - i don’t even bother heat-shrinking / taping / gluing the ends together, i just tear off a strand of 3 and attach them and it works perfectly : )

2 Likes