#416

Thanks for getting back on this @infovore

I’m not that good at coding yet, so if you’d be up for the task it would be very nice. If not, I’ll try and see if I can make it work somewhere down the line.

#417

No it’s normal, there are no traces connected to the LED pins on this kind of slider. Like Okyeron suggested it might be a possible mod using an additional MUX connected to the teensy then free-wired to the LED pins.

#418

Making the LEDs addressable requires a pile more electronics; you’d need at least another mux, and you’d be spitting PWM through it.

The LED faders have the same pinouts as non-LED faders. If you wanted to, you could bridge either the power or voltage out pins to the led pin via a resistor, and that’d make them work. Wouldn’t look great, but it’d work!

#419

i thought i should share my solution here.
i.e. using through hole resistors soldered to a 2x3 header with jumpers that perfectly fits in between two jacks.

DSC_0064
DSC_0064.JPG5504×3096 5 MB

1 Like
#420

Would anyone by chance have a compiled firmware file that would work with the Teensy loader? I’ve been trying to get the Arduino environment to compile properly with no luck.

50%20PM

1 Like
#421

There’s a compiled one in the official Github releases. You want the first “.hex” file in that list.

#422

Perfect, that’s what I needed. Thanks!

Sidenote: How does one get to that link from the main 16n page here: https://github.com/16n-faderbank/16n ? I don’t see a link, and assume I’m being stupid…

#423

You are not being stupid; you are just falling prey to the overloaded Github UI! In the row above the file browser, “144 commits / 4 branches / 4 releases” - click the ‘releases’ option. It’s a way of marking a specific point in the Github history as an official “version”, and also attaching files such as compiled binaries to it. In this case, I compile hex versions, and attach delivery files for the hardware as well.

2 Likes
#425

Hi there,
as I finally have my 16n running (after messing with my destructing stupidity), I noticed that the faders output a maximum of 126 instead of 127 when using in MIDI.
I’m sure it’s an easy fix for someone with the adequate skills. Would anyone care to take a look ?

#426

You might try to adjust the MINFADER value (line 34 of config.h). I set mine to 200.

But my faderbank is “flipped” so, maybe it’s the MAXFADER value you need to adjust :wink:

#427

Thanks, I completely overlooked that arduino code could have tabs, that’s why I couldn’t find it.
How do I make an .hex file from the arduino editor ?

1 Like
#428

I generally compile and program the teensy direct from the arduino app but

sketch —> export compiled binary

#429

Makes sense. For some reason I thought you had to use the Teensy programmer.
Thanks !

1 Like
#430

I set MINFADER to 1 to fix the problem for me

1 Like
#431

no - the teensy programmer will let you upload a .hex file somebody else has made without having to compile it. If you compile a file in Arduino, it’ll automatically get beamed through Teensy Loader to your 16n. And, as explained elsewhere, “export compiled binary” is how you generate the .hex alone.

1 Like
#432

slick :muscle::+1:…

#433

Has anyone designed a full enclosure for this beautiful piece, by any chance? Was thinking something 3d printable.I am worried about dust issues

1 Like
#434

not that I know of. it’s going to be a lot of material if you print it, btw.

regarding dust: the two biggest vectors for dust on a 16n are jack sockets and faders. dust on the components is largely irrelevant. so: even if you box in the sides, you’re still going to have the main dust vectors on the object exposed, and those are places where dust is meaningful - scratchy faders, ropey audio contacts.

enclosures would protect the sides/innards a bit against things like spillage, however.

3 Likes
#435

plug in all cables
set faders to favorite values
encase in lucite
problem solved

5 Likes
#436

hehehehe. 16n as a MIDI/CV preset card :stuck_out_tongue:

1 Like