So cool, where do you find these aluminum caps? looking great

1 Like

Cant find a source of any more - its just one i had hanging around that id salvaged off an old radio as a kid

1 Like

Hey @rklem I have same setup as you, but cant make it work.! I thought it was wrong pull up resistors and have soldered new ones in, but still no luck. Do you use pull-up resistors on your 16n at all, when going through TXb? Do you have an old ER-301 with reversed SCL SDA or new one? I appreciate any feedback - I’m completely lost! Thanks :slight_smile:

I didn’t build the 16n myself, @jonnymon kindly did that for me, so I have the sister of his awesome looking 16n. He told me that there are 10k pull ups in my 16n. I didn’t open it yet, but perhaps he could confirm here?

I have a Rev. 7 ER-301, so I had to modify it and needed the reversed i2c connection. If you’re in doubt about your reversed i2c cable: The easist way to make sure that there’s no problem with the connections is to use three separate cables. This way you can clearly see if everything is plugged in the right way.

Apart from that: You have to power your TXb (didn’t work for me without power). Connect the 16n to your TXb, first power on the ER-301, then the 16n. Did you check your USB to MIDI functionality on the website? Does this part work?

Hope you can solve it!

1 Like

Thanks for getting back on this!

I’ve changed from no resistors, then 10k and now 4,7k. Have always been trying with TXb, with and without power. New revision of ER-301, and except for the two resistors, my 16n is build by @MichiganSynthWorks and works fine with midi and CV.

I’m trying to find out where the fault might be, but I’m new to i2c and have nothing else to test on.

How exactly do you go forward from a-z on the ER-301 to register input?

@bpcmusic should i be able to use er-301 without pull-up resistors, when using TXb? and can you confirm if the white line on TXb means ground?

You have to run v 0.4 or later. In Admin mode you go to System Settings, enable “Teletype control” (at the end of the list), make sure “i2c slave address” is 0x31 (default). Then return to User mode.

Now you can insert a sc.cv unit (bottom of the units page). In this unit select port 1 and move the first 16n fader (also try the last one, it might be set to reversed). Do you see the unit responding?

1 Like

Also: Did you make sure the master/leader flag was set when compiling the 16n firmware?

Just to confirm, the unit is populated with 10k pull ups, master mode flag. It will work without or with an i2c connection (with depends on order of powering up)

I have not put the very latest firmware on which apparently makes it possibly more robust - seems fine so happy as is

1 Like

oh my sweet lord i did not know it had to be 0.4 :exploding_head:!! I wonder if it works if I just upgrade and all this work and component sourcing could have been avoided!

I’m still on 0.3 as I have a pretty complicated setup for live performances that I didn’t want to risk because 0.4 wasn’t flagged as stable yet. Will try tomorrow, fingers crossed :smile: thanks!

TXb under power provides the appropriate pull-up. White line is ground.

Let us know how things go!! Good luck! :slight_smile:

2 Likes

Sorry to crash your hopes, but I was wrong: Teletype integration was added in 0.3.06, my bad.

So I’m afraid I’m running out of ideas what could cause your i2c problems. :frowning:

oh no.! :sweat: hm…

if you’re on older er-301 firmware make sure to set the address to 0xB1 (which is equivalent to 0x31), especially if you’re using the latest 16n firmware.

2 Likes

there is 0x31 in stable version of 0.3 - 0x31 would be the right one then, right?

yep, either 0xB1 or 0x31 should work.

are there any other 16n owners in Portland, OR?

I am still having a hard time getting mine working w/ USB midi.
the i2c and CV outs work as expected but midi was spotty (sometimes working sometimes not) but now doesn’t work at all. It shows up as a midi device on norns and on my MacBook but no midi cc’s are detected when I move faders around :sob:
I’d love to find someone local that could help.

have you updated to the most recent 1.33 firmware?

Otherwise - i’ll be not exactly close in Olympia the weekend of May 11th :slight_smile:

I finally made I2C work with my ER-301, after countless of hours testing, troubleshooting and soldering!! Such a relief.! :sweat_smile:

I don’t know what exactly caused the issue in the end unfortunately.

If anyone experiences problems, feel free to write me or in this thread and I’ll do my best to help.!

2 Likes

I think the problem might have been, that leader (16n) has to be turned on after slave (ER-301). I was powering both from same power supply, so they turned on simultaneously. I have to wait until ER-301 is on, before inserting 16n’s usb power or else it won’t send any info to ER-301.

Does this behaviour (hot-plugging usb power) do any damage to the hardware?

interesting… @bpcmusic does this sound right to you? if so, i wonder if some sort of delay can be implemented in the i2c code?