I'm deep in the woods... Detection problems and solution

[gabriel1712]

So, I'm done building the module and things are partly working. Being a DIY I'd almost be disappointed if it plugged 'n played with out a fight, heheh.

When I boot the MD, after the welcome-screen shows, the LCD continuosly shows the top left bar at max output (Pedal open). No response from the pedal on the floor. MCT confirms this, Pedal = 127. Doesn't matter if the 32 input flat-cable to the jacks are connected to the board or not, it still shows max, so it must be a board/config problem, not a jack/hi-hat jumper issue, right?

I have methodically checked the board for bad solding and shorts. The resistors are all measured and correctly placed. I don't know how to check the rest of the components with the multimeter, so a push in the right direction there is greatly appreciated.

Also with the 32-cable on,
the Pedal (input 2-4),
kick (input 5),
Crash (input 13-14),
Tom3 (input 19-20),
Aux4 (input 31-32)
and Aux7 (input 37-38)
is not responding at all.
The rest is fine. I could use a qualified guess to what to look for/test. Is it a hardware issue and how to check for fried chips, etc. or is it configurable in MCT (I've played around there, no luck).

I'm running XP sp3, MD is detected in device manager as USB composit device (Location 0 (MegaDrum MIDI USB)) but my Terrasoniq TS22 PCI ASIO soundcard doesn't pick up a signal up and the MIDI Message Indicator in BFD2 consequensly shows nothing. Am I missing something obvious?

[gabriel1712]

I'm running XP sp3, MD is detected in device manager as USB composit device (Location 0 (MegaDrum MIDI USB)) but my Terrasoniq TS22 PCI ASIO soundcard doesn't pick up a signal up and the MIDI Message Indicator in BFD2 consequensly shows nothing. Am I missing something obvious?

Edit:
Got signal throu to BFD2, Yeah!! I can't precisely tell you what I did but it seems my BFD2 needs to be restarted a few times before it hooks on to the MD.

But no luck with the silent pads.
Here's a chart of how pads are connected, what the LCD shows and what MCT see.

Small mistake... the Snare LCD should read 3t/3b, not just 3. This is the only pad correctly displayed on LCD and in MCT.

[dmitri]

Disconnect the inputs cable from the board. With something metallic, e.g. tweezers, touch each input pin (1,2,4,5,12,13,14,15) of each multiplexer and monitor VU meters on the LCD.
Do you notice activity of all corresponding VU meters?

[gabriel1712]

Ah... think I got it. You measuring advice made me see a different pattern.

It matters which of the NYS215 sockets twin leg I sold. Look at the picture and see how I solded the far leg in the two first rows (green spots), but for convinience solded the near legs in the last row (red spot). Those legs are separated from their twin legs when the jack is inserted => Not Connected.


Thank you!

[dmitri]

The pins on the jack on either side are not equal. On one side the pins are used fro tip/ring/sleeve and on another side may be used when nothing is plugged into the jack. In the last case the tip/ring/sleeve pins are connected to pins on opposite side and may be used in audio applications to shorten inputs to the ground. These are so called "switched" jacks.

[gabriel1712]

Yup, just resolded them to the other legs and it's firing on all cylinder. Thank you.

Except...this problem remains

When I boot the MD, after the welcome-screen shows, the LCD continuosly shows the top left bar at max output (Pedal open). No response from the pedal on the floor. MCT confirms this, Pedal = 127.

I noticed you have the same hi-hat controller as I, Dmitri. The one you use as basis for you optical variable build. What jumper setting should I use for the basic HH-ctrl?

[dmitri]

It is explained in http://www.megadrum.info/forums/viewtopic.php?f=3&t=462
Optical HH controller is a low impedance controller

[gabriel1712]

Thanks Dmitri.
It's very exciting. The hardware is all set and done. I'm looking forward to playing around with the parametres in MCT.

One question, thou...
My Aux 2,3,4,5 and 6 are all producing the exact same Midi note (MCT midi log shows 63). The VU-meter is show them as different pads.

On a relateded matter all other pads/cymbals, except for my snare, output the same rim note as head note, eg. Tom1 head/rim 48/48. Again the VU view them correctly as either head or rim.

All are correctly set to dual or three-way in MCT. Could it be hardware related or should I look for a software solution to that?

[dmitri]

Thanks Dmitri.
It's very exciting. The hardware is all set and done. I'm looking forward to playing around with the parametres in MCT.

One question, thou...
My Aux 2,3,4,5 and 6 are all producing the exact same Midi note (MCT midi log shows 63). The VU-meter is show them as different pads.

It's because by default they're assigned the same note.

On a relateded matter all other pads/cymbals, except for my snare, output the same rim note as head note, eg. Tom1 head/rim 48/48. Again the VU view them correctly as either head or rim.

All are correctly set to dual or three-way in MCT. Could it be hardware related or should I look for a software solution to that?

Again, assign to the rims (or any other inputs for that matter) notes you want. And look at the documentation: http://www.megadrum.info/content/megadrum-configuration

[gabriel1712]

I thought MCT was the on-the-fly direct interface of MD, equal to using the MD buttons and LCD. In that understanding, the 'SEND TO MD' seemed pointless, so I never used it!!?! ROFL!!

Ssssoooorrrrry for waisting your time. Sleep deprivation turns your brain into an three-legged ATmega8. To my strong defence... I did wonder why the difference between Gain 0 and Gain 8 was only marginally audible.