Hello all,

I’m still having usb midi troubles with my 16n.
It works great w/ i2c and cv but will not send midi over USB.
It shows up as a midi device on my computer and in Norns but sends nothing over USB.
I’ve tried different cables and re-loaded the firmware and I’m getting nothing.
The fucked up part is that it used to work… then only worked sometimes and now doesn’t work at all.
Any help would be greatly appreciated (especially if there are any local PDX friends on here)
Thanks!!

If you don’t get it sorted before then, I’m in PDX end of Sept and would be happy to meet up and help figure it out. (or meet up anyways!)

1 Like

I’m leaving to play some shows in Iceland/UN on sept 10th and was hoping to get it sorted before then but either way we should try and meet up while you are here!

1 Like

I have a trs jack for i2c installed in my case to connect a faderbank to TT via a TT backpack. It’s hooked up and working, but I noticed the I don’t get the full range from 0 to 16383 when I poll a fader value. This is true for faders 1-16. They all top out around 15900. I am using a 3 foot trs cable which is the shortest I have in my possession right now, so I’m not sure how that might affect what I’m seeing. The connection from the jack to the backpack is about 5 inches or so. Should I be using a shorter cable?

P.S. I have the 16n set as a follower, and without the pull-ups installed. I’m also connecting an ER301, white whale, ansible, just friends, TXo and TXi to the backpack.

I2C is a digital signal and therefore cable length is not related to “output level”. More likely issue is the quality of power supply in use for your 16n or the tolerance of components on the voltage dividers.

I remember reading in a few other posts here that I2c reliability drops off as the cable length increases? Maybe I misunderstood aspects of that?

As far as the power supply, I’m pulling from 5v at 1.5 amps from an Intellijel tps80w switching power supply. I’m definitely well under 600ma at full load.

Not too sure about the tolerances of the components though. I’ll have to review my mouser cart, but I used the BOM from github with no substitutions.

Reliability is affected by cable length, for sure. But that’s more about whether the message arrives in a readable form. These messages are digital pulses. If your cable is too long the pulses look less like squares and more like ramps. And the signal:noise ratio gets worse. This affects the timing of your pulses (the ramp crosses the comparator threshold later than a square pulse) and increases chances of missed or spurious pulses.

But the “value” carried by the message is unlikely to change.

Aha, that makes a lot of sense. Thanks for the clarification.

My wonderful family just gave me a lovely 16n for my 60th birthday!

I’m extremely psyched! It’s from Michigan Synth Works, natural aluminum…

However there are no instructions… where do I find documentation?

Also, how do I power it?

Thanks!!!

5 Likes

It’s powered by USB. Here is the main manual (click the link to go to the GitHub page)

1 Like

Thanks!

A USB power supply would include an iphone charger, I assume. What about an iPad charger?

I don’t see anything about a maximum power limit.

I have a 5v iPhone charger and a12v iPad charger…

5v but I don’t know what the amp draw is. Pretty small I’d guess. 500ma has been more than enough to power mine.

I’v got it running with a 5v iPhone charger!!!

Wow, seriously transformative with the Mannequins modules!!!

image

The final pieces arrive

2 Likes

@infovore @okyeron

Hey I just put together a couple more faderbanks and I’m getting some strange problems with the MIDI USB signals. Certain faders when you move them will seem to trigger a bunch of other faders to send out their MIDI value, but then other faders are completely normal. Do you know what would cause this? I can’t seem to find any shorts or inconsistencies in the board at all. I went through the brd file and PCB connection by connection with a multimeter.

For those who haven’t seen this yet:

Tesseract Modular have a eurorack prototype (sweet sixteen), which is running a alt version of the 16n firmware (seen on facebook).

I like the fact that it has CV inputs, which allows you to use it as a CV to MIDI converter or/and CV to I2C (I assume).

7 Likes

I would be interested to see them release their firmware source code, but alas, MIT Licence doesn’t require it. Sounds like some neat alterations. Hardware is licensed as sharealike, though.

Yes, I thought I’d ask him if he would.

Does this mean he must keep the 16n licence and share the hardware?

There should be some period of flexibility to allow development of derivatives before the sharealike requirement kicks in. I have seen it pushed too far (e.g. the Supercell derivative of Clouds) but surely it should be a dialog between the respective creators.

(Paging @M4ngu to the thread to comment)

1 Like

This would require a different license which specifically allows for that flexibility.

(note - it might be a good idea to start a new thread about CC-Licenses and requirements/suggestions for open sourcing projects, etc, rather than fill this “help thread” with that content)

2 Likes