Author Topic: [DM10] TEST MODE  (Read 3104 times)

Offline Hellfire

[DM10] TEST MODE
« on: January 02, 2014, 06:29:23 PM »
SUPER SECRET TEST MODE
(This is a diagnostic test mode used by the manufacture)


Description of Operation:

Many companies tend to place special kinds of testing modes within the devices they make. These testing modes are typically used when trying to diagnose a problem form a return (or service ticket) unit. Alesis is no different. The DM10, DM8, and Pearl REDbox all have a special testing mode. Please keep in mind that some of the tests CAN NOT be done by the end user as they require a computer or other testing devices connected to the drum module while test is in progress. Also, these tests will in no way erase or reset any sets or custom kits you may have saved in your module. With that said there are a few of the tests the that the end user can use and could be of great value.


Entering Testing Mode:

Entering the test is very easy. Simply hold down the STOP and REC buttons while powering on your drum module. You know you have successfully entered the test mode when you see this plain looking screen:


Remember, this mode is meant for in-house testing so the screen isn’t going to look pretty. “Diags” stands for Diagnostics. To execute the selected test press the PLAY button. In this case “Serial #” is the current selected diagnostic test (the test always starts here). Should you press PLAY at this point your would see a screen like this:


As you can see I blurred out this DM10’s serial number.

To go back to the diagnostic select screen simply press the STOP button. Once you back at the “Serial #” screen, you can scroll through the different test option by using the CURSOR UP & DOWN buttons located just to the right of the module’s readout screen. Again, not all of the tests are useful to the end user. Here is the list of the different test options:

(NOTE: On some tests you can just press STOP to return to the select menu. There are a few tests that you will not be able to get out of without powering off the drum module do to additional equipment or test software being required. Those exceptions are included in the descriptions below.)

• Serial # - This show the serial number of the drum module.

• RAM -This test takes about 5-7 seconds to complete. Once finished (assuming no issues) is should show PASSED.

• Microcontroller - This test isn’t useful to the end user as it requires additional testing equipment or testing software. Running this test will result in a “CD10 stuck high” message. Pressing the STOP button will show a “Failed” message. This does not mean anything is wrong with your module. It just means that something else is needed for the test to be ran correctly.

• LCD - This will show if the LCD screen has any bad pixels. It does this by causing the screen to go black.

• LED - This lights up all five LEDs on your module. You can activate each LED one at a time by using the  CURSOR up & down button to select each one.

• Switch - This is used to test each button on the module. Pressing any button on the module will show the name of that button on the screen. Note that when pressing the “Preview” the screen will also display a velocity value. The harder you press the “Preview” button, the higher that value should display. Pressing any two or more buttons at the same time will result in a “Failed” message. To exit this test, press the STOP button twice and the screen will read “Abort”. Pressing the STOP button once more will take you back to the test selection menu.

• Jog - This is used to show the actual position the jog wheel is sitting at. Each click of the jog wheel should increase (clockwise) or decrease (counter clockwise) the number on the display by one number at a time.

• Audio - This test will produce an audible tone on all audio outputs of the module. This tone can be loud. Make sure that your amp volumes and headphone volume are set low. When starting the test the word “All” is displayed on the screen. Using the CURSOR up & down buttons let you cycle through each output.

• MIDI - This test isn’t useful to the end user as it requires additional testing equipment or testing software. Running the test will result in a “Failed” message being displayed. This does not mean anything is wrong with your module. It just means that something else is needed for the test to be ran correctly.

• Flash - Running this test take about 10-12 seconds to complete. Once completed (assuming no issue exist in the flash memory) the screen will display a “Passed” message. Press STOP to return to the test menu.

• EEPROM - This test happens almost instantaneously when ran. Once completed (assuming no issue exist in the EEPROM memory) the screen will display a “Passed” message. Press STOP to return to the test menu.

• USB - This test isn’t useful to the end user as it requires additional testing equipment or testing software. Running the test will result in a “Failed” message being displayed. This does not mean anything is wrong with your module. It just means that something else is needed for the test to be ran correctly.

• Faders - This test basically wants you to move each slider all the way up and all the way down. Once each slide is moved to its minimum and maximum position, a “Passed” message is display. Notice as you move the slider, the slider number and value of its position is displayed. NOTE: The sliders are not as accurate as the jog wheel. There for, you will see some variance in its values. The slower you move the sliders, the more accurate the position value tend to be. Lastly, if you do not move a fader within 3-4 seconds of starting the test, a “Failed” message will be displayed. This is normal.

• Triggers - This test only works partially. That’s because the test want to check “Tip”, “Ring”, and “Switch” for each input jack (1-12). No user has a trigger that uses all three of these zones states. In general the “Tip” is the head of a drum trigger and the “Ring” is the rim of a drum trigger. The “Switch” tends to only be used by the choke strip of most cymbal triggers. Hitting the corresponding zone will display a velocity value (except for “Switch”). NOTE: Pressing the STOP button during this test will force the test to the next zone. If you wish to stop the test, you have two options. The first option is to press stop for every zone (which takes awhile). The second option is to power off the module.

• Hi Hat - This test isn’t useful to the end user as it requires additional testing equipment or testing software. Running the test will display “Press S1 on tester”. Pressing the STOP button once will display “Abort”. Press the STOP once more and you are back to the test menu.

• Version - This test will display the current version of the module’s Boot software.

• Trig Debug - This test isn’t useful to the end user as it requires additional testing equipment or testing software. You will need to power off your module to end this test.

• Hihat Debug - This test is used to show the position of the Hi-Hat control pedal. NOTE: The number value displayed will fluctuate constantly to some degree. The displayed value will be at its largest when your foot is off the control pedal. Depressing the control pedal will cause the displayed value to drop. Pressing the STOP button once stops the test. Pressing the STOP button once more takes you back to the test menu.


Additional Thoughts

I can see where some of these tests might be a good thing for the end user. I know that if I were to buy a used DM10, DM8 or Pearl REDbox, I would run some of these tests just to make sure things work the way they should just incase I would need to send it back to the music shop or seller.
« Last Edit: January 30, 2016, 10:48:40 AM by Hellfire »
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads