www.megadrum.info

Am I the only one experiencing problems with MCT option FROM MD / TO MD. No settings are being transfered, between the MD and MCT when I use them.

MD is connected throu USB and MIDI signal from the MD is correctly showing in MCT's midi log.

As a side question, is there a way to make MIDI-OX show output graphs/bars like MCT? I'd like to use MIDI-OX because it shows aftertouch and more, but I find it slow and inconvinient to look for xtalk, retriggering, variations in velocity etc in scrolling numbers.

gabriel1712 wrote:Am I the only one experiencing problems with MCT option FROM MD / TO MD. No settings are being transfered, between the MD and MCT when I use them.

MD is connected throu USB and MIDI signal from the MD is correctly showing in MCT's midi log.

Seems like MegaDrum doesn't receive any MIDI messages from MCT. My guess is that either MIDI Out in MCT is not set correctly or there is a hardware problem in MegaDrum board which prevents MIDI data to be transmitted from PIC18F2550 to Atmega.
In the last case check for:
shorts/breaks between pin 17 of PIC18F2550 and pin 14 of Atmega
shorts/breaks around 6n138.
correct values of resistors between pin 17 of PIC18F2550 and pin 14 of Atmega and around 6n138

As a side question, is there a way to make MIDI-OX show output graphs/bars like MCT? I'd like to use MIDI-OX because it shows aftertouch and more, but I find it slow and inconvinient to look for xtalk, retriggering, variations in velocity etc in scrolling numbers.

MIDI-OX is a low level general MIDI tool and as such cannot do graphs/bars and etc. Ask elrules to add to MCT features you want.

dmitri wrote:

gabriel1712 wrote:Am I the only one experiencing problems with MCT option FROM MD / TO MD. No settings are being transfered, between the MD and MCT when I use them.

MD is connected throu USB and MIDI signal from the MD is correctly showing in MCT's midi log.

Seems like MegaDrum doesn't receive any MIDI messages from MCT. My guess is that either MIDI Out in MCT is not set correctly or there is a hardware problem in MegaDrum board which prevents MIDI data to be transmitted from PIC18F2550 to Atmega.
In the last case check for:
shorts/breaks between pin 17 of PIC18F2550 and pin 14 of Atmega
shorts/breaks around 6n138.
correct values of resistors between pin 17 of PIC18F2550 and pin 14 of Atmega and around 6n138

Thanks Dmitri. MIDI OUT in MCT is set to MD. I'll check the board once I get home. Oh, btw I have my old module connected to the physical din MIDI IN on the MD to pass MIDI throu. Could that block off MIDI IN from MCT (USB)?

gabriel1712 wrote:Oh, btw I have my old module connected to the physical din MIDI IN on the MD to pass MIDI throu. Could that block off MIDI IN from MCT (USB)?

When you send MIDI from the old module to MIDI IN of MegaDrum and watch data in MCT, do you see any MIDI coming through?

Yup, pieces connect to the old module shows up in MCT's log

gabriel1712 wrote:Yup, pieces connect to the old module shows up in MCT's log

1. Try MCT without anything connected to MIDI IN.
2. Check for continuity between pin 17 of PIC18F2550 and R7.
3. Check for continuity between R7 and pin 14 of Atmega.
4. Make sure there is no shorts between pin 17 of PIC18F2550 and anything else, especially the ground and Vcc.

Looks like the old module to MD MIDI IN is causing the problem. With out it everything's fine.

gabriel1712 wrote:Looks like the old module to MD MIDI IN is causing the problem. With out it everything's fine.

This is strange. Seems like the old module drives a current through a LED inside 6n138 when not sending signals. Check voltage on pin 6 of 6n138 when the old module is disconnected and when you connect it. What is it?

Dang... my own Multimeter is a crappy $5 thing. Can't get a sensible low volt reading from it. I'll have to borrow my neighboors pro gear again and get back to you tonight.

Btw how is the pin counted on the 6n138? I know where 1 is.
4321
5678 ??

or

4321
8765

or

7531
8642

or

Etchy-bitsy-minny-moe?! heheh

It's
4321
5678