br>This will be for people building the 6 hp 12 output teensy based eurorack MIDI module.

Thiis module was built as a "quick and dirty" way to get 12 outputs from MIDI in a small module,

for CV it relies on very fast PWM (over 300khz) when the PWM is only using the 7 bits that MIDI CCs send, and filtering, you can also do triggers, velocity scaled triggers, gates, and velocity scaled gates.

with a bit of coding you could have built in self generated LFOs, envelopes, etc if you wanted say, octatrack style control LFOs and your sequencer does not have that feature,

there is one 12 bit DAC, using the built in teensy DAC output which can be used as a 1v/octave note output, but it is not meant as a high performance midi to 1v/octave midi voice. (probably ok for bass )

it might also be a nice start for learning teensy coding, as the sketches are fairly basic. (though you have a whole teensy to work with so...)

it has been found that you can also use this with usbMIDI, and Steven Noreyko has even gotten MIDI clock to work from USB. (we are updating the code for usbMIDI)
[note, USB MIDI will not pass from master to slave modules, it is using the raw midi pulses from the opto isolator, there might be a fairly easy fix for this though with just one wire kludge][/img]

The DUBLdeca uses 2 complete Dodeca units - this means two sets of everything under the hood (pcb + parts*) - with ONE Dubldeca panel.

This also means you need two euro power connectors. Or you can make a single power cable with two power connectors (pic below).

Not sure if the BOM is updated yet but try to get 5mm wide 47uF electrolytic caps. The early bom had 6.5 or something and they were kinda hard to squeeze in there. I ended up re-ordering and getting some of 667-ECA-1VM470I from Mouser

(*actually you only end up using ONE stereo jack for the MIDI input)

br> br>

br>GaryInHuaHin

br>Could you explicate the wiring of the stereo jack for MIDI In? I think there's only 2 ways to do it, but I'd rather do it right the first time....

Initially having trouble compiling the code. It chokes whenever it hits a line to point to a handler, such as:

MIDI.setHandleNoteOn(HandleNoteOn);

It kicks back
'class MIDI_Class' has no member named 'setHandleNoteOn'

I'm using midi.h from PJRC. Is there something I should know?
Thanks! br> br>

br>nevetsokyeron

br>

GaryInHuaHin wrote:

Could you explicate the wiring of the stereo jack for MIDI In? I think there's only 2 ways to do it, but I'd rather do it right the first time....

The side (ground) pin goes toward the 3rd hole in the pcb. BUT - you don't need to connect the ground pin.

GaryInHuaHin wrote:

Initially having trouble compiling the code. It chokes whenever it hits a line to point to a handler, such as:

MIDI.setHandleNoteOn(HandleNoteOn);

It kicks back
'class MIDI_Class' has no member named 'setHandleNoteOn'

I'm using midi.h from PJRC. Is there something I should know?
Thanks!

Check to see if you have a "MIDI" library folder in the Arduino Libraries folder (in your user directory ~/Arduino->Libraries). If so - take it out. The PJRC/teensyduino stuff is installed deep into the Ardunio application directory. Note - the "MIDI_Library" is OK and should not conflict.

There's some issues with a couple different versions of midi.h installed in different places. br> br>

br>GaryInHuaHin

br>

nevetsokyeron wrote:

GaryInHuaHin wrote:

Could you explicate the wiring of the stereo jack for MIDI In? I think there's only 2 ways to do it, but I'd rather do it right the first time....

The side (ground) pin goes toward the 3rd hole in the pcb. BUT - you don't need to connect the ground pin.

Thanks. Actually, it's the external wiring I'm aftert, ie which pin of a 5-pin MIDI goes to the tip?

This might be standard now, but that hasn't always been the case.

nevetsokyeron wrote:

GaryInHuaHin wrote:

Initially having trouble compiling the code. It chokes whenever it hits a line to point to a handler, such as:

MIDI.setHandleNoteOn(HandleNoteOn);

It kicks back
'class MIDI_Class' has no member named 'setHandleNoteOn'

I'm using midi.h from PJRC. Is there something I should know?
Thanks!

Check to see if you have a "MIDI" library folder in the Arduino Libraries folder (in your user directory ~/Arduino->Libraries). If so - take it out. The PJRC/teensyduino stuff is installed deep into the Ardunio application directory. Note - the "MIDI_Library" is OK and should not conflict.

There's some issues with a couple different versions of midi.h installed in different places.

When I don't have that folder (PJRC's MIDI directory) in ~/Arduino->Libraries, I get ''MIDI' was not declared in this scope' error at MIDI.begin. This was my original problem.

On MacOS, the PJRC stuff is actually buried in the Arduino application bundle at Arduino.app->Contents->Java->hardware->teensy->avr->libraries->MIDI

Still no joy on compilation. Oddly, I've moved from PC to Mac but have a similar result. error log below. The Libraries Manager shows 47Effects midi lib installed (which I assume is the one in Documents>Arduino>Libraries) but is seemingly ignored in favor of the PJRC library.

I've tried removing one library or the other. The error ('MIDI not declared in this scope') remains the same.

Thanks again for help.

/dubldecca_left.ino.cpp.o"
dubldecca_left: In function 'void setup()':
dubldecca_left:66: error: 'MIDI' was not declared in this scope
MIDI.begin(MIDI_CHANNEL_OMNI);
^
dubldecca_left: In function 'void loop()':
dubldecca_left:81: error: 'MIDI' was not declared in this scope
MIDI.read();
^
Multiple libraries were found for "MIDI.h"
Used: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/ MIDI
Not used: /Users/garyhall/Documents/Arduino/libraries/MIDI_Library
Using library MIDI at version 4.3.1 in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/ MIDI
'MIDI' was not declared in this scope br> br>

br>nevetsokyeron

br>Trying to test this on another computer from my existing Arduino install...

I did the following:
1) remove the MIDI folder from ~/Documents/Arduino/libraries/
2) use the Arduino application library manager to install the 47Effects midi library*
3) re-install teensyduino**

* this is at the menu path Sketch->Include Library->Manage Libraries...
and then search for MIDI

EDIT - there may be something going on here with versions of Arduino and Teensyduino. The above worked for me with Arduino 1.8.1 and Teensyduino 1.35

Right out of the box, Arduino 1.8.4 and Teensyduino 1.39 (both the current versions) end up with the compile error you experienced above. Something apparently changed with MIDI in Teensyduino 1.37 and later...

Also - for anyone else playing along in the home game - You must always quit and relaunch the Arduino application when you change anything with Libraries. br> br>

br>GaryInHuaHin

br>Yay! That did it!
Really glad we could recreate it and track it down.

Now to build.... br> br>

br>n82558

br>I'm trying to compile the firmware and having some trouble at the moment. On the Github for the Dodeca project, each the left and right folders have 3 .ino files. Do I need to upload all 3 to each teensy or just dubldecca_left.ino and dubldecca_right.ino?

I've followed the steps in this thread but I'm trying to just upload the dubldecca_left.ino file at the moment but I keep getting the following error message:

/Users/xxxx/Documents/Arduino/left.ino/left.ino.ino: In function 'void setup()':
/Users/xxxx/Documents/Arduino/left.ino/left.ino.ino:67:24: error: 'HandleNoteOn' was not declared in this scope
MIDI.setHandleNoteOn(HandleNoteOn); // Put only the name of the function
^
/Users/xxxx/Documents/Arduino/left.ino/left.ino.ino:68:31: error: 'HandleControlChange' was not declared in this scope
MIDI.setHandleControlChange(HandleControlChange);
^
/Users/xxxx/Documents/Arduino/left.ino/left.ino.ino:69:25: error: 'HandleNoteOff' was not declared in this scope
MIDI.setHandleNoteOff(HandleNoteOff);
^
Error compiling for board Teensy 3.2 / 3.1. br> br>

br>n82558

br>Ok SO that was actually an easy fix, I just had to have all 3 .ino files in the same directory. Both teensy's are programmed now, the startup sequence runs without issue, but the module still doesn't seem to respond to midi at all. Does the ground on the stereo jack really not have to be soldered? Is there a schematic for this anywhere? It would be helpful to figure out what may not be working.

br> br>

br>cannonball swandive

br>Can anyone point me to substitutes for my build as mouser is out of stock

These are the replacements I used for those two parts ( you have the resistor in there twice) br> br>

br>jmsiener

br>

n82558 wrote:

Ok SO that was actually an easy fix, I just had to have all 3 .ino files in the same directory. Both teensy's are programmed now, the startup sequence runs without issue, but the module still doesn't seem to respond to midi at all. Does the ground on the stereo jack really not have to be soldered? Is there a schematic for this anywhere? It would be helpful to figure out what may not be working.

Kind of in the same boat man. I've gotten the usbMIDI stuff working but still no dice on the dinplug. At this point I've checked continuity between every teensy pin and the other side of the boad as well as continuity between the jack and where they connect to the 220R and 1n4148. When looking at the side of the board where diode is I've got the line to the left going with the line that was on the PCB. I've tried the recent IDE and teensyduino 1.41 and now everything is uploading without any CREATE_MIDI_INSTANCE stuff; just the examples are straight uploading. At this point the only thing I feel like I haven't done is flip that diode around. Feeling like captain dumbass right here. br> br>

br>chailight

br>Am about to start on a dubldeca build. Before ordering all the parts, I wanted to check if using a Teensy 3.2 in place of a 3.1 is ok? I know 3.2 is intended as a drop in replacement for a 3.1, but wondered about whether the change in function to pin 1 (analog out instead of reset) makes any difference in this case. br> br>

br>gwpt

br>

chailight wrote:

Am about to start on a dubldeca build. Before ordering all the parts, I wanted to check if using a Teensy 3.2 in place of a 3.1 is ok? I know 3.2 is intended as a drop in replacement for a 3.1, but wondered about whether the change in function to pin 1 (analog out instead of reset) makes any difference in this case.

Did you ever get confirmation of this? I am about to build one too and have the same question... thx br> br>

br>smidirin

br>teensy 3.2 is fine. module is great br> br>

br>jmsiener

br>Forgot got to give a status update here on my build, Facebook group be working way faster. Got everything sorted; had a bat54 and not a bat54s. Got the right diode and everything worked. Got the code sorted on my dodeca for a mono voice, clock out, and 8 drum trigs - my MPC1k and me couldn’t be more pleased. br> br>

br>synthetek

br>There is an error in the build doc it says 7x .01 uf Bypass instead of .1uf (it does say .1uf in the picture). There are also 5 10uf smd Electrolytic Capacitors in the BOM that aren't needed? br> br>