MCT - SEND doesn't work?!

[gabriel1712]

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?

I'm reading 5v both with and without Oldmodule to MD MIDI IN. Should I do the other readings you suggested?

[gabriel1712]

...
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.

ad 2) check
ad 3) check
ad 4) how do I check for shorts? I get continuity between pin 17 and USB switch(vcc) but that can't be the proper way of checking...

[dmitri]

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?

I'm reading 5v both with and without Oldmodule to MD MIDI IN. Should I do the other readings you suggested?

I can only suspect that the old module sends MIDI data periodically which messes up firmware update.

[dmitri]

...
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.

ad 2) check
ad 3) check
ad 4) how do I check for shorts? I get continuity between pin 17 and USB switch(vcc) but that can't be the proper way of checking...

There should be no less than a few kOhm resistance between pin 17 of PIC18F2550 and either Vcc or the ground. Of course you must measure the resistance only when the board is disconnected from power/USB. What does your meter show?

[gabriel1712]

...
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.

ad 2) check
ad 3) check
ad 4) how do I check for shorts? I get continuity between pin 17 and USB switch(vcc) but that can't be the proper way of checking...

There should be no less than a few kOhm resistance between pin 17 of PIC18F2550 and either Vcc or the ground. Of course you must measure the resistance only when the board is disconnected from power/USB. What does your meter show?

5.9k

[dmitri]

There should be no less than a few kOhm resistance between pin 17 of PIC18F2550 and either Vcc or the ground. Of course you must measure the resistance only when the board is disconnected from power/USB. What does your meter show?

5.9k

That's ok. I believe you will have to update firmware/configure MegaDrum with MCT only when the old module is disconnected.

[gabriel1712]

Aye, I can live with that.

I have a jam coming up, so I have to divide my time between practice and MCT. I just move back and forth the pads and cymbals that I haven't yet configured perfectly in MD. Once it's done, ol' Mod is gone.

[thramul]

I have almost the same problem: I can recieve any data from the module, but cannot send anything. I have checked everything as descriped in post#2, but its all correct, no shorts or breaks, and I got the correct resistor values everywhere. When I klick send in MCT, it somehow freezes. I waited a few minutes, but nothing happened. I can only correct the freezing when I disconnect Megadrum from the computer. MCT will immedatly continue working upon pulling the usb connector.
I build synthex kit 3 with atmega 32 and 16mhz clock. Apart from this and the other thread dealing about the "AutoLoadConfig", I did not experienced any problems.
thanks!
greetings,
Matthias