New ARM unit. Problem sending configuration.
Posted: Mon Jan 28, 2013 3:46 pmI received a new ARM based 56 input Megadrum module. The unit is now mounted and operational. 
However, I may be having a problem. Megadrum Config Tool sees the MIDI notes and communicates with the unit, however, whenever I send a configuration change, the unit stops responding to triggers and I must power off and on to regain triggering.
Here is what I do:
1) Turn on the unit, plugged in to Macbook Air, OSX 10.7.5
2) Open Megadrum Configuration tool
3) The first screen asked me what unit I have - I chose ATMEGA 644 as there was not a choice for the new ARM unit that I could see. (This may be the source of the problem - what do I choose?
4) Triggers work.
5) Make a minor change in a pad configuration and "Send all settings to Megadrum."
6) Triggers do not work
7) Change it back to original setting.
8) Triggers still do not work.
9) Power off and on
10) Triggers work again.
It is not totally "locked up" because if I send another configuration change after it stops responding to triggers, the LED comes on, just as it does whenever communicating with the software. I cannot regain any triggering until the power has been cycled though. Admittedly, I am brand new with this software and hardware.
Do you have any ideas on what I can check?
However, I may be having a problem. Megadrum Config Tool sees the MIDI notes and communicates with the unit, however, whenever I send a configuration change, the unit stops responding to triggers and I must power off and on to regain triggering.Here is what I do:
1) Turn on the unit, plugged in to Macbook Air, OSX 10.7.5
2) Open Megadrum Configuration tool
3) The first screen asked me what unit I have - I chose ATMEGA 644 as there was not a choice for the new ARM unit that I could see. (This may be the source of the problem - what do I choose?
4) Triggers work.
5) Make a minor change in a pad configuration and "Send all settings to Megadrum."
6) Triggers do not work
7) Change it back to original setting.
8) Triggers still do not work.
9) Power off and on
10) Triggers work again.
It is not totally "locked up" because if I send another configuration change after it stops responding to triggers, the LED comes on, just as it does whenever communicating with the software. I cannot regain any triggering until the power has been cycled though. Admittedly, I am brand new with this software and hardware.
Do you have any ideas on what I can check?