Go back to previous topic
Forum nameHandling/Suspension
Topic subjectRE: Problem with AEM 12.5" rotor upgrade
Topic URLhttp://forums.2gnt.com/dcboard.php?az=show_topic&forum=6&topic_id=26438&mesg_id=26803
26803, RE: Problem with AEM 12.5" rotor upgrade
Posted by thedawg, Dec-31-69 06:00 PM
Ok, I just took out my rotors and I see two things you could be having probems with.

1) The bolt holding the caliper bracket to the hub. The AEM? bolts I have are just about 1mm too long if you attempt to mount the hub without using the AEM dogbone. They hit the backside of the rotor, preventing it from seating. Solution here would be to remove everything from the hub, including all brackets to test fit.




Pay REALLY close attention to the dogbone. It can be installed 4 ways, only one works. The nipples should face out, and the larger pair of nipples should face away from the hub. You can also see the 1/8" of grinding I had to do to get the GSX calipers to fit. (bright orange rusted patch)



2) The outside of the hub could be rusted enough to keep the hat from fitting over the hub. (also, it could be rusted on the inside of the hat, where the axle nut goes). But I don't see any ridge on my rotors anywhere, its all rounded to allow for slight rusting of the hub. Solution would be dremeling down the rust buildup on the hub.




The tolerances are very close on the hat, but it fits perfectly on all my FWD cars, from 1995-1999, both turbo and nonturbo, talon and eclipse, both with and without ABS. You two must have a very unique hub, the WRONG AEM PART NUMBER?, or a badly out of tolerance (defective) rotor if it really doesn't just mount up. (My part number is 32-5004, stamped on the front, inside rim of the hat.)



Also, here's how badly the pad hangs off the rotor. You can just barely see a stripe of black at the top center of the pad.



I live 5 minutes from RRE and 15 minutes from AEM headquarters. If you guys would like to ship me your rotors, and I can re-create your problem, I'll take them to both companies and show them exactly what the problem is.
I generated this page in 0.0099809169769287 seconds, executing 6 queries.