UPDATE2 - NB Mazda MX-5 Timing Belt Failure

Discussion in 'Technical' started by ging, Jul 28, 2012.

  1. UPDATE - NB Mazda MX-5 Timing Belt Failure

    Is the "pain-in-the-ass" check engine light on?
     
  2. UPDATE - NB Mazda MX-5 Timing Belt Failure

    I'm going to throw my random choice in and say a sensor of some kind.
     
  3. UPDATE - NB Mazda MX-5 Timing Belt Failure

    No lights
     
  4. UPDATE - NB Mazda MX-5 Timing Belt Failure

    Could be. When i heard the thud when driving it sounded like something might have fallen off in the engine. Maybe the mechanic didnt do something up tight enough
     
  5. UPDATE - NB Mazda MX-5 Timing Belt Failure

    Could you tell what area of the car the thud came from?
     
  6. UPDATE - NB Mazda MX-5 Timing Belt Failure

    sounded like quite far back in the engine bay
     
  7. UPDATE - NB Mazda MX-5 Timing Belt Failure

    is it a gradual process, or does it hit a certain temp and then just to crappy like a light switch?
     
  8. UPDATE - NB Mazda MX-5 Timing Belt Failure

    No idea cos the garage has the car. Im just going off what they said
     
  9. UPDATE - NB Mazda MX-5 Timing Belt Failure

    It's your head gasket
     
  10. UPDATE - NB Mazda MX-5 Timing Belt Failure

    Drift damage
     
  11. UPDATE - NB Mazda MX-5 Timing Belt Failure

    possibly the crank or cam sensor.
     
  12. UPDATE - NB Mazda MX-5 Timing Belt Failure

    bingo! (also 1/2 a point can go to James)

    They just rang me and told me it was the cam sensor, they hadn't put it back in properly and it fell out during acceleration, so I guess the thud i heard was it falling out. They did a big road test and said it's fine now. Thank god for that.

     
  13. UPDATE - NB Mazda MX-5 Timing Belt Failure

    that they didn't put it in properly is more than enough reason to take it somewhere not shit next time.
     
  14. yeah you're right. Lesson learned.
     
  15. But the "check engine" light would have turned on and/or flash, no?
     
  16. Hmm well maybe it didnt because the sensor itself was still fine, but had fallen to some point in the engine bay and was still reading something random (as its a magnetic sensor) and so telling the ecu to inject fuel at the incorrect times.

    Im not sure if thats correct but thats my logic
     
  17. it wouldn't put on a code until it wasn't working. it was probably picking up on the cam and just running incorrectly.
     

Share This Page