Latest MegaDrum firmware version

[keko030]

Do you get any MIDI data from MegaDrum?
If not, then you may have a crystal with incorrect frequency.
If yes, then you may have a connectivity problem on the board from PIC to Atmega, i.e. MIDI data are not passed from PIC to Atmega.

Hello Dimitri, I had the outdated atmega firmware, use the application and update with the firmware atmega644_48_20181218.bin, my megadrum is 32 outputs, and it was updated correctly, I have midi activity, there should be no connection problem between the pic and the Atmega, I think. I still can not connect to the MDM, probe also with midi and ox detects activity, I configure the ports in midi with megadrum usb in input and output rn, open but does not record midi activity in the pc, in megadrum if ... what am I doing wrong ?

[keko030]

I think the pic18f2550 was damaged, I measure the voltages of the USB cable connected to the pc and on the data pins there is no voltage, when I connect it to the MD the pin 16 of the Pic gives me 2.84 voltage, that pin is connected to the pin of USB data, is my reasoning correct? , I do not have another pic18f2550 to try ....

[keko030]

Did someone measure the data pin volumes of the USB connector on the MD board?

[dmitri]

Signal levels should be close to 0V and to +5V (~4.9V).

[keko030]

Did someone measure the data pin volumes of the USB connector on the MD board?

I measured 200 millivolts and 2.84 volts, will it be fine? I could update the firmware of the MD to the 20181218 version, the pic18f2550 should work fine, otherwise I could not update it.
but I still have midi activity in the MD but I do not achieve midi activity in the pc with the midi or ox.
and I get error in the ports of entry and exit of megadrum USB in MDM .. any suggestions?

[keko030]

I was testing things with the MD and found that putting MDG in the megadrum USB input port and in MIDI output port yoke 1 I get sysex ok, I just get an error with the megadrum USB output port .. someone had something wrong A) Yes? Greetings.

[dmitri]

As far as I understand, MIDI from MegaDrum to PC is working but from PC to MegaDrum is not. The only cause I can think of is a communication problem from PIC to Atmega.

[Kabonfaiba]

Thank you for the continued development of MegaDrum Dmitri!

Do you think you could ever develop a hot spot suppression algorithm for MegaDrum?

All the best and be well.

[dmitri]

I'm not aware of a reliable way to deal with pads with "hot spot" issues. Positional sensing is not reliable enough to do that.

[shuey79]

To update MD the first post says:

All firmware files in the archive after version 20110410 have the following naming scheme:
megadrumppp_nn_yyyymmdd.bin
where
ppp - MCU type. STM32a - for STM32F103RBT6, STM32b - for STM32F103RCT6, STM32d - for STM32F205RCT6, STM32e - for STM32F205LITE, 644 - for Atmega644, 1284 - for Atmega1284
nn - Maximum number of inputs for the firmware.
yyyymmdd - date(version) of the firmware.

I have an ARM based 32 input unit bought in 2011 but no clue what "PPP - MCU type" would be on mine. How would I figure this out?
Also, can the firmware still be upgraded using MDMFX?