Faderbank Run: See top post for status

[bjlogic]

Hi, I also joined to follow this thread with interest. looking forward to hearing the price, or diy kit price if it will be available.

Thanks!!

[Puscha]

Mmmm been following this for a while but realized I haven’t yet put down my interest in a kit.

Consider this my expression of interest

[marcus_fischer]

I have been using an external 8 fader box w/ an FH-1 in my modular and like not taking up extra HP w/ the faders. It makes it more playable than trying to move tiny faders that are half covered by cables. But that’s just my opinion.
Looking forward to the 16n!

[midst]

this is a great idea. mark me down as interested.

[midst]

a fast DJ style fader bank could be useful.

[LLK]

I’m interested, poor, but interested, so call me optimistic-about-the-future-of-my-bank-account interested.

[bookmil]

have been reading for months, never posted.

count me interested

[seres]

I’d be definitely down!

[mopoco]

And i’m up (on the forum) and down for a faderbank
plus interface panel!

[laborcamp]

OMG
That might just make me look back at some old MIDI items…

[giftculture]

I’m interested for sure

[cosmicsoundexplorer]

Count me in too! This thing looks amazing.

[infovore]

maybe i don’t see the most current eagle files. but on those i do see, there are no breakouts for any GPIO at all even the reset button.

it seems like for something to be “hackable” that’s kinda a necessity. like to have a pin to put in “config” mode or any other kind of “special” mode (you don’t have any buttons to use for a key combo.) don’t you need the reset pin at least to flash firmware with teensyduino? is the idea to take it out of the enclosure to do that? or that any fully enclosed mounting will involve DIY breakouts?

So: the Teensy is flashable without physical access to the reset button. I’ve always managed to flash my 16n without having to reach in and hit that button, for sure.

Also, the whole thing is designed such that the Teensy is hard-soldered to the lower board. I don’t think there’s enough height to plug it into female headers. So it’s always going to be in there, you’re not going to be taking it in and out. Unless, of course, everybody hates that idea.

I had not intended to break out any GPIO pins; I guess I am not using ‘hackable’ in the same extent to which you are. It would be straightforward to offer breakout pads for some of the digital pins - 2-12, as a maximum; the remaining pinouts of the Teensy are pretty heavily used right now:

The plans are the final ‘enclosure’ would only be top and bottom with standoffs; the sides will always be open.

So, I mean, I’m open to suggestions around what’s appropriate re: breakout pins but it feels like there’s only so much I can do. I am trying to keep this project from turning into a lot of work, rather than just a moderate amount. But I am open to suggestions for ‘optional’ pinouts (which I would not even populate with a header, given the open edges; I leave that to the end user).

[zebra]

hey thanks for the response

and sorry, again - not trying to complain or ask for more things, honestly wondered if i’d missed something, and good to know you’ve ever found a need for the reset line.

all i’m trying to do is think through the minimal requirements needed to achieve/allow the maximal number of possible software features without forking the hardware.

in particular, i think its plausible to want to programatically change USB device modes. the user-oriented goal being to offer a way to change the MIDI configuration (or whatever) without installing teensyduino - instead, connecting the teensy as a serial or mass-storage device.

its cortex-m3 right? so there is actually a soft-reset register (0xE000ED0C):
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0337e/Cihcbadd.html

so i think i can do:

1. have a flag in flash memory that is read at boot to determine the device mode
2. have a function to write that flag and then trigger a soft-reset
3. connect the midi System Reset message (or sysex) to this function

not as nice as holding a button but i think it would work

[kieselguhrkid]

I’ll toss in with the lot interested in a either a built unit or DIY kit. The possibilities with the analog outs are just too tantalizing.

[sisyphus69]

still interested here. wonder how these are coming along!

[jonsimon]

i’m more than interested!!! (like sell me one, a txo, txi please)

[jacon]

I’ve been following this thread for ages now, just wanted to say keep up the good work! It looks great! And i’m definitely interested in a diy kit or pcb when they’re available

[infovore]

They are… coming along. In no particular order:

• the firmware is basically done, from what we can see
• we’ve been working on the enclosure/panels; they’ve gone through a redesign: better spacing of standoffs to reduce flexing, bumping standoff size to increase choice of parts, designing countersinks into the panels, and that’s mean the mechanical layout of the PCB (where a bunch of holes are) has changed, and that means we need to do a new run of prototype PCBs to confirm things fits
• we’ve started work on prototyping the panels in aluminium - confirming they work how we’d like, how everything fits together.
• and we all have full-time jobs and other commitments, and also worth noting the cost of BOM for a full prototype (ie panels, faders, all electronics, pcb) is… not pocket change.

It’s going about as fast as I imagined it would, which is probably slower than many of you hoped, and also slower than the number of v1.2 prototypes in the wild might indicate. (We’re currently onto v1.25).

So: once the new layout is finalised and the metalwork is confirmed, we’re then at a point to look into contract manufacture, acquiring parts, working out the final BOM and pricing, and working out what products will be offered.

In a nutshell: onwards.

[marcus_fischer]

Thanks so much for all the work you guys have put into this! It’s going to be awesome!