www.megadrum.info

Is Megadrum Manager supposed to automatically detect which firmware and number of inputs my megadrum has?

Should I be concerned if it doesn't?

I'm connecting via USB. Dmitiri made my module so i'm confident it's soldered properly.

It should be able to detect firmware version but not the number of inputs (yet). If it doesn't there might be a few reasons:
1. Incorrect MIDI ports selected for In/Out.
2. ChainId in the module and in MDM don't match.
3. Software problem/bug.
4. Communication problem in both or one direction. Does MIDI log show anything when you hit pads? Does MegaDrum flash the MIDI LED when you press any of 'Get' buttons?
5. Something else but I cannot think of anything right now

It seems like my MDM was not configured properly.

The Midi out was set to microsoft MIDI mapper instead of MD.

All is okay now. When I click on rescan midi ports in the options window it sets the out to Microsoft MIDI mapper.


Thanks for the problem solving Dmitri

I am having this same problem.

- The Id Chain number is the same on MD and MDM
- I have MIDI activitly that shows in the log, and I can trigger my VSTI's
- The MIDI IN and MIDI OUT is set to the same (MD - named USB in menu)

In short, the MDM receives the MIDI messages correctly for the notes, but there is no other communication between MDM and MD. I cannot see the fireware version (the unit says 20080604) and I cannot send or get any configeration data to or from the unit. HELP!

Also ...

I am a complete newbie at this. I bought the unit used a couple of years ago from someone who had built it himself. I have never used it and I'm just trying to set it up with some trigger I have bought. I have a few general questions:

- How can I find out what MCU and Clock Frequency is used in my unit?
- I think it is 32 input. It has 17 1/4 inch inputs on it. When I scroll through the menu it goes up to Channel 31 (is channel 32 the hi-hat?)
- I cannot change the contrast on the LCD, and holding down the left button when powering up does not enter the firmware update mode. I know the buttons function properly because they work correctly when scrolling through the options.
- Some of the miscellaneuous settings are not there (example: ALTEncoders) I assume this is because the firmware needs to be updated on my unit?
- I read the information on the bootloader webpage about the protected bootloader. Does this mean that I can now only update the firmware to an older version instead of the current one? If this is true can you tell me what is the most recent firmware I can use without buying a new MCU and having it programmed by you?
- If I can get the MDM to work (and the MD to enter the update mode when I power up and hold the left button down), can I update the firmware from the MDM or do I also need to use a "bootloader"?

Thanks, I hope someone can help me with this thing.


rod

rod wrote:I cannot see the fireware version (the unit says 20080604) and I cannot send or get any configeration data to or from the unit. HELP!

MDM requires a latest firmware version. It won't work with anything less than 20101223

- How can I find out what MCU and Clock Frequency is used in my unit?

Open the device and look it up on the MCU and the crystal.

- I think it is 32 input. It has 17 1/4 inch inputs on it. When I scroll through the menu it goes up to Channel 31 (is channel 32 the hi-hat?)

It is 32 inputs.

- I cannot change the contrast on the LCD, and holding down the left button when powering up does not enter the firmware update mode. I know the buttons function properly because they work correctly when scrolling through the options.

You don't have a bootloader in MCU.

- Some of the miscellaneuous settings are not there (example: ALTEncoders) I assume this is because the firmware needs to be updated on my unit?

Correct.

- I read the information on the bootloader webpage about the protected bootloader. Does this mean that I can now only update the firmware to an older version instead of the current one?

Correct.

- If I can get the MDM to work (and the MD to enter the update mode when I power up and hold the left button down), can I update the firmware from the MDM or do I also need to use a "bootloader"?

MCU must have the protected bootloader if you want to be able to load encrypted firmware versions.

hi dmitri,
I am having a similar problem.
Already updated to the newest firmware but that is not shown in MDM. He recognizes the MD at Midi In and Out but still wants me to configure the ports while opening.
The led does not flash when I´m pressing "get all". Midi-log does not work either.
do you have any other ideas?
I´m running on mac.

Hope you can help. Thank you in advance.

Greetings

Dimitrios

lyras wrote:hi dmitri,
I am having a similar problem.
Already updated to the newest firmware but that is not shown in MDM. He recognizes the MD at Midi In and Out but still wants me to configure the ports while opening.
The led does not flash when I´m pressing "get all". Midi-log does not work either.
do you have any other ideas?
I´m running on mac.

Did you read the warning in red in viewtopic.php?f=4&t=1504 ?

hi,
yeah, already tried that. Does not work properly with os x Lion (10.7)...

on the hompage it´s also mentioned:


Works with Java 1.5 and 1.6 on OS X 10.4 to 10.6


seems like I have to wait.

I´m trying to do it now via windows emulation on vmware fusion.

p.s :

there is an update on the homepage, which says:

NOTE for LION Users

Mandolane software is no longer required if you're running Lion and should be uninstalled.


so I don´t need it anyway. The problems remains, however...

Without Mac OS X Lion I cannot do anything to test and troubleshoot it. All I suggest is to make sure you have the latest Java version installed.