Yamaha DTXpress/DTXplorer/DTXtreme group photo

Yahoo Groups archive

Yamaha DTXpress/DTXplorer/DTXtreme

Index last updated: 2026-04-28 22:44 UTC

Thread

FYI issue with TP100

FYI issue with TP100

2004-09-04 by oldguydrummer

For anyone who has this pad....

Until we can figure this problem out...I would recommend that you 
only tighten the threaded knob that secures the pad to the hex 
mounting bar the minimum amount for it to hold....DO NOT OVERTIGHTEN.


The issue:

If you look in the photo section of this group you we see the photo I 
took of the insides of the TP100 and the TP65S. 

Looking at the photo "Inside TP65S" you can see a hefty solid 
aluminum mounting bracket that secures the TP65S to the hex rod.

Looking at the photo "TP100 MTG BRKT" you can see a plastic insert 
that has a flat piece of square steel on the back side that the 
threaded knob presses down on. The metal channel piece that is 
sitting next to the pad in the photo sits on top of the hex rod. This 
piece is cast aluminum with open channels on the back, which is not 
visible in the photo. At the bottom groove of the metal channel the 
aluminum is less than 1/32" thick. 

I was tightening this pad back on the rack and heard a pop. When I 
opened the pad up I found this piece of channel cracked into two 
pieces. If I had not been holding the pad, it would have fallen off 
the rack clamp.  

I have passed this on to Yamaha, but being a Holiday weekend I don't 
expect anything back until next week sometime.  

I was a little suprised that the larger/heavier pad had only a 
fraction of support compared to the TP65S pad. I suggested to Yamaha 
that perhaps this piece should have been made of solid aluminum or 
maybe even steel.

OGD

P.S.  Yamaha just posted a response to the triggering problem of 
playing these kits in a high volume environment, thanks to input from 
Tony Verderosa. The response is posted on www.Dtxperience.com.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.