#161

I have two faderbanks here, I will try this out tomorrow, we’ll see what happens (one in slave mode for TT and the other in master mode for the Er-301) :slight_smile:

1 Like
#162

I’m going to want a method for flipping my 16n that doesn’t require teletype and I’m fine with flashing a different firmware or whatever is necessary to accomplish it. So, if a new teletype op is added or whatever, that’s fine but I hope it isn’t the only available method.

#163

i didn’t consider that MIDI would also need to be flipped, which means it has to be done on faderbank. so having 2 versions of faderbank to support flipping will still be required. what this means is that a teletype op could simply be a way to change it dynamically, in addition to the header setting on faderbank firmware (which would become the default setting).

also i should clarify - just throwing ideas, i2c is not the main 16n feature, adding anything to firmware might not be something the 16n creators want to do (also maybe we should have a separate thread for 16n/i2c specific discussions? don’t want to derail the main thread).

2 Likes
#164

Well… it doesn’t work :smiley: I’ll use the second faderbank for Midi or CV

#165

I was thinking of mainly the nifty quantization OPS like NOTE and SCALE.

#166

FYI - @Nordseele posted a new thread for 16n hacking and hardware build questions, etc. here:

#167

I’m having trouble getting my 16n to talk to my ER-301 in master mode. I had teletype integration working without issues, so I think I got the basic connection right. Just trying to confirm that I’m not missing something stupid:

I’ve downloaded the current firmware from github (post “i2c doesn’t work” update), added in the #define MASTER 1 line in config.h and then flashed it to 16n. Then I connected it to the ER-301, powered on my modular, confirmed that the i2c slave address on the ER-301 was set to 0x31 (and was running the most current firmware 0.4.11) and then added a SC.CV unit to a chain with port set to 1. My assumption was that this was how the data was transmitted and that if I moved the first fader, I should see a corresponding change in value.

Is there something I missed? I’ll triple check all connections again, I guess :frowning:

#168

@x2mirko Have you soldered the 4,7k pull-up resistors on the 16n ? They’re needed in master mode

1 Like
#169

I knew I forgot something! :smiley:

1 Like
#170

It should work once they’re soldered on, but you should avoid connecting this “Master” faderbank directly to the TT or to the same bus.

#171

Quick note: the TXb busboards with the stereo i2c jacks will be hitting my web store on Monday at 2 PM PST. Full details are here:

5 Likes
#173

Test build success!

(gotta get some white/gray “nub” switchcaps)

IMG_1596
IMG_1596.jpg1080×720 231 KB

BTW these are switch caps from Tadya
https://www.taydaelectronics.com/toggle-switch-handle-cap-red.html
https://www.taydaelectronics.com/toggle-switch-handle-cap-black.html
https://www.taydaelectronics.com/toggle-switch-handle-cap-white.html

14 Likes
#174

Late to the address party - but ran into all the address problems tonight :slight_smile:

There’s a list of i2c addresses in the monome ecosystem here:

0x35 is no good because it’s already assigned (TETRAPAD). So additional devices would need to use the 0x40 or 0x50 range perhaps?

I’ve just put my flag down for 0x55 to use for enigma. :grin:

I’m going to send up a issue on github to put the 16n i2c address in config.h

3 Likes
#175

Uploaded the latest firmware. Testing midi on chrome shows all 16 channels being controlled by fader 1. No other faders register. Not being seen by the teletype either. This build is pre-multiplexer. What flag do I need to change?

#176

i think…

config.h
uncomment this:
// #define V125

1 Like
#177

yes, what @okyeron said. If you uncomment the line mentioned in config.h so that V125 is defined, and flash that, your board should work correctly. (I’ve tested the latest build on my own 1.25 hardware and it worked correctly).

1 Like
#178

I’m wary of making the i2c address changeable, mainly because one of the key uses - Teletype - requires it using a fixed address that is baked into the TT firmware.

We could move it into config.h, make the default 0x34, and then leave a sternly-worded comment about only changing this if you know what you’re doing.

1 Like
#179

Agree completely.

FWIW - I’m looking at this from a development perspective - hacking firmware code on other devices that will talk to 16n.

#180

Holy smokes. I got the Txb, but it seemed like the reverse cables sold out immediately. Pretty nutty!

#181

I can probably help with cables. PM me.

1 Like