Some changes to schematics (original "I screwed up")
Posted: Tue Nov 27, 2007 10:15 am
This topic is now out of date because the correct schematics have been up there for quite a while. So I move it out of the announcements.
I think I've managed to solve the problem:
In MegaDrum32 Digital board: R26 - from 220 to 4k7 (thanks to Synthex for the suggestion)
In MegaDrum8 Digital board: R21 - from 220 to 4k7
In AVR-CDC USB board: R4 - from 470 to 1k
In PIC18F2550 USB board: R4 - from 470 to 1k
After these changes Sysex doesn't cause any problems anymore, at least on my dev board. Both Synthex's MIDI USB and AVR-CDC work fine for me.
Hi,
It appears I screwed up my development Digital board but the weird thing is that estregan , see this thread, might have the same problem as I have.
First of all I should say that the MegaDrum module I use for drumming works fine - it communicates fine with a PC over both standard MIDI and FT232 based USB board, i.e. MegaDrum Controller (Sysex messages) works fine with it.
Now, with my development board I experience a strange issue: whenever I send a Sysex message to this board over USB MIDI(both Synthex's and AVR-CDC) it causes MegaDrum to reset. Sending Sysex over standard MIDI works fine, but the weirdest thing is that if I keep standard MIDI connected to the same PC but send Sysex over USB MIDI it works fine again!
So, until I resolve this issue, I won't be making any firmware updates.
I think I've managed to solve the problem:
In MegaDrum32 Digital board: R26 - from 220 to 4k7 (thanks to Synthex for the suggestion)
In MegaDrum8 Digital board: R21 - from 220 to 4k7
In AVR-CDC USB board: R4 - from 470 to 1k
In PIC18F2550 USB board: R4 - from 470 to 1k
After these changes Sysex doesn't cause any problems anymore, at least on my dev board. Both Synthex's MIDI USB and AVR-CDC work fine for me.