#38

Yup, gnd <-> gnd, sda <-> sda, scl <-> scl. So just keep the pins all in order (I think only ER301 uses a different order?) If it gives you trouble on the first go maybe try adding one module at a time.

1 Like
#39

My situation exactly…

1 Like
#40

thank you! alright here we go

#41

i2 SEE you man. 20 characters of pun

1 Like
#42

I guess we’re i2c buddies!

2 Likes
#43

3 posts were merged into an existing topic: ^^ crow help: druid

#46

What kind of I2C header does Crow have ? 2 rows (2 x 3 pins) or only one row ? (trying to plan my setup)

#47

It’s 2 x 3, and the rest of this sentence is to comply with the 20 character minimum :sweat_smile:

4 Likes
#48

Perfect, thanks for your reply :wink:

1 Like
#49

Yes, but it depends on which hardware revision you have. Newer models don’t require any crisscrossing, or any hardware modifications. It’s well documented here:

http://wiki.orthogonaldevices.com/index.php/ER-301/Teletype_Integration

1 Like
#50

Is it possible to have both crow and 16n connected to the ER-301 simultaneously?

#51

It’s possible to connect anything to the bus simultaneously (up to some limits for total cable length etc.) but whether it works well for what you’re trying to do is another issue. Using 16n as a follower and polling it from Crow, then passing values from Crow to ER-301 seems totally doable and I believe is similar to a setup some users are happy with using Teletype instead of Crow. Note that neither of these devices have support on the firmware for the initial batch of Crows. ER-301 support has been written but is in need of testing before it will go in the official firmware, see here.

#52

To connect 16n to Crow via i2c, do you need to keep an opening in your rack for cables to get to the back of Crow?

I have a 16n but so far have only used it with cv outs and midi, neither of which require connecting to the back of a module…

Thanks!

#53

I generally just take out one or two modules when I need to change I2C connections. The end of my rack with all the I2C stuff is kind of a mess back there. Having rear access to the modules would be ideally convenient, but I don’t know that I’ve seen any racks that allow for this other than super minimal open-backed ones like Tiptop Z-Ears/Rails.

1 Like
#54

You could also use a TXb to connect the 16n to your i2c bus :slight_smile:

2 Likes
#55

@dan_derks given that you can’t pull request to github wikis and editing them directly seems to require some type of write permissions on the repo, is this thread the place for wiki contributions? Or should another repo be made to track docs issues or something? If there’s a good method for doing this it could maybe be added to the wiki front page.

Here is a proposed FAQ section coming out of a DM conversation with @eblomquist:

What’s the difference between Crow and Teletype?

Here is a partial table comparing some aspects of these two scriptable Monome modules.

Aspect Crow Teletype
panel hardware 2 CV inputs (1.5 kHz sample rate), 4 CV outputs (48 kHz sample rate), mini USB 8 trigger inputs, 4 trigger outputs, 1 CV input, 4 CV outputs, potentiometer, USB-A port, button, screen
events focused on sending and receiving bits of text from something else, and manipulating and reacting to things happening elsewhere in your setup – CV crossing some threshold, receiving an I2C message focused on running small bits of code in reaction to triggers. These can be any of the 8 trigger inputs patched from elsewhere in your modular, or an internal “metro” (metronome) script that’s triggered at a fixed rate
scripting runs Lua scripts, a general purpose programming language with a higher abstraction level (also used on Norns) runs scripts written in a specialized, stack-based language (sometimes called “TT-script”) designed for Teletype
storage has larger (8kb) user storage space for scripts deliberately has a limited amount of code and data that can be in use at any given time
USB is not a USB host - it does not supply USB power and is not programmed to talk to USB devices. Other devices (a computer, Norns, etc) have to initiate communication with it and supply USB power is a USB host, so it can support USB devices and supply power to them. Currently the supported devices are a keyboard, a USB disk so you can make backups of your work, and a Grid (external power required)
UI requires some other device, typically a computer, to send scripts or instructions to it. This can be really convenient, since you can use whatever editor / other tools you like on your computer, and paste chunks of code or whole scripts to Crow as needed. druid can be used on any computer to interact with Crow over the serial port. Norns, Max, and Max4Live can also send bits of code to Crow. has a screen and directly connects to a keyboard so you can write code right on the module with nothing else
CV output very flexible at producing gates and CV. LFOs and envelopes can be arbitrarily specified using the ASL mini-lanugage can produce both gates and CV. CV can slew on its way to a new value, but can’t loop on its own - a script has to initiate each change
15 Likes
#56

I would be careful about saying that Teletype can supply power to USB devices, as the older ones cannot power a grid.

3 Likes
#57

this is fantastic! thank you so much. for now, i’d love to get Crow & end-user documentation on the doc contribution track, but clearly the wiki approach needs to change. brian, trent and i are gonna hash this all out on a call tomorrow!

4 Likes
#58

Thanks for reassuring me that my Teletype isn’t redundant. :pray:

If that comparison table ends up in the docs or wiki, it might be worth clarifying that Crow is also deliberately limited in its storage capacity, in a different way – TT can store many rather small scripts, while Crow can store only one longish one.

5 Likes
#60

Something isn’t connecting for me with the I2C cables and Just Friends. I bought a bunch of colored Dupont wires (female) and I connected the six on the Crow to the matching six on JF. M4L is seeing the crow fine for everything else, but JF is not responding in poly mode even though I follow all steps. Can someone help me, in as much detail or simplification as possible, connect the Dupont cables properly between crow and JF? Going to attach a picture.

IMG_5085%202
IMG_5085 2.JPG2291×2691 1.36 MB