DM6 USB Tom1 Not working

I currently can't get the Tom1 to register in the module. I bought the unit from Craigslist, and the person told me it was working. Here are steps I've tried to troubleshoot:

No matter which pad I plug the Tom1 cable into, there is no sound triggered on the module.

I have plugged in all the other inputs (cymbal, tom2, tom3 etc) into the tom pads, and all of the tom pads work.

That led me to believe there was a cable issue, however when I just apply some resistance to the cable by touching the 1/4" cable plug with my bare fingers I get the module to register the tom1 sound.

This led me to believe that maybe the other person had programmed some kit or something that didn't work the right way, but I held + and - and turned on the unit and had read this will factory reset the module. There wasn't any sound, or visual cue or anything that there was a factory reset, so I'm assuming it worked, but the problem persists.

It sure seems like a cable issue, but the previous owner swears it worked, and if it was the cable why can I get the sound to register by using my fingers?

I'm very confused, don't know how else to troubleshoot.
1 person has
this problem
+1
Reply
  • Hi Scott,

    Thanks for posting. 
    The cause of "no sound" or from a trigger could be one of three things:

    1. The pad
    2. The cable
    3. The module
    In most cases, "no sound" from a trigger is caused by the pad itself, however, to make a solid determination, follow the steps suggested below:

    1. Begin with all cables connected to all the correct pads. Now, disconnect the cable directly from the pad that is not functioning and connect it directly to a different pad, such as one of the Tom pads.
       
    2. Strike the Tom pad that you just connected to.
    • If you get no sound, the cause is the cable or module.
    • If you get a sound, the cause is the original pad, which will need to be replaced.
    1. Reverse the procedure.  Begin with all cables connected to all the correct pads.  Now disconnect the cable directly from a functioning pad and connect it to the pad that is not working.
       
    2. Strike the pad that was not working.
    • If you get no sound, the cause is the pad and it will need to be replaced.
    • If you get a sound, the cause is the cable or module.
    If the cause is not the pad, in most cases it is the cable snake and not the module.  For further assistance in how to obtain a replacement cable snake, contact Alesis Technical Support.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Thanks for the reply.

    I'm currently not using all the cymbals, rather than replace the cable snake, is there a way for me to just re-program say the crash cymbal cable to produce the tom1 sound?

    Sorry for the noobish question, I have only had the kit for two days and I don't really know how to search for tutorials or reference materials.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Since this is a basic-level kit, it is not possible to have different sounds assigned to the pads. This is only possible on our more intermediate kits, such as the DM10 series, Crimson/Forge Kits, and Strike kits. As this issue does seem to be due to a faulty snake, I would recommend connecting with our Support team for assistance with this. Their contact information is linked above.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned