512TR intermittent CEL | FerrariChat

512TR intermittent CEL

Discussion in 'Technical Q&A' started by J. Salmon, Sep 8, 2007.

This site may earn a commission from merchant affiliate links, including eBay, Amazon, Skimlinks, and others.

  1. J. Salmon

    J. Salmon F1 Rookie
    Owner Rossa Subscribed

    Aug 27, 2005
    4,367
    VA
    I have had an intermittent CEL banks 1-6 for the last month or so. It comes and goes without being reset. Car seems to run 100%. I swapped the right and left O2 sensors last week. The light immediately went out, but now is back on and still on the 1-6 bank (not the O2 sensor). I have seen posts about an ECU also. Could that be the issue?

    Tom Jones at Sport Auto looked for vacuum leaks a while back when this first started, but no luck. Any ideas?

    BTW, I am supposed to run the car at VIR on Tuesday, then to a show 2 hours out of town on the following weekend. Other than risking being stranded, should I be concerned?
     
  2. james patterson

    james patterson Formula Junior
    Professional Ferrari Technician

    Dec 8, 2003
    417
    Dallas Texas
    Full Name:
    James Patterson
    Without logging onto the Motronic and doing some diagnostics, at least knowing what error is being set, it is all just guess work as to the cause. But in my experience it never hurts to clean the grounds for the Motronic. They are located on the cylinder heads towards the back, on top, between the intake manifold and the parting line. If you pull the air-flow-meter off you can access easily, one 5mm and one 6mm bolt, 1-6 is on the right head and 7-12 on the left. However, your best bet is to find out what is setting the light
     
  3. WILLIAM H

    WILLIAM H Three Time F1 World Champ

    Nov 1, 2003
    35,532
    Victory Circle
    Full Name:
    HUBBSTER
    twice when I started the engine only half the engine would fire but when I shut it down & restarted it the whole engine would then fire

    Wierd
     
  4. No Doubt

    No Doubt Seven Time F1 World Champ

    May 21, 2005
    72,740
    Vegas+Alabama
    Full Name:
    Mr. Sideways
    I'd consider checking/replacing the relays to each ECU and fuel pump, as well as inspecting/replacing the crank sensors and their connections.

    Your 512TR is running Motronic 2.7? Should be easy to display those error codes on your dash if so.
     
  5. J. Salmon

    J. Salmon F1 Rookie
    Owner Rossa Subscribed

    Aug 27, 2005
    4,367
    VA
    Code is 1212. Sport Auto is helping too, but it is the weekend and I am supposed to head to VIR tomorrow.
     
  6. No Doubt

    No Doubt Seven Time F1 World Champ

    May 21, 2005
    72,740
    Vegas+Alabama
    Full Name:
    Mr. Sideways
    1212 on M2.7 for 348's, 355's, and Mondial T's is a lambda issue (O2 sensor and/or MAF and/or coolant temp sensor). Perhaps this holds true for 512 TR's running M2.7 as well.

    You swapped the O2's from side to side, but the trouble code remained on your 1-6 side, so I'd rule out O2's being the problem because your swap didn't trigger a 7-12 bank 1212 code.

    If 512 TR's have twin MAF's then you could swap them to sort of repeat the same test above, but I'd suspect that what you really have is a coolant temp sensor gone bad (causing you to run too rich which triggers the O2 1212 code) or a fuel pressure regulator gone bad (causing you to be too rich again).

    To test the FPRs, pull off the black vacuum hose (easily comes off by pulling with one hand; simple test) to the FPR, rub your finger on each end, and sniff your finger for the scent of fuel. Fuel smell in a vacuum hose means the FPR has failed.

    Easy to replace.
     
  7. J. Salmon

    J. Salmon F1 Rookie
    Owner Rossa Subscribed

    Aug 27, 2005
    4,367
    VA
    Thanks much, will do.
     
  8. J. Salmon

    J. Salmon F1 Rookie
    Owner Rossa Subscribed

    Aug 27, 2005
    4,367
    VA
    OK, CEL goes out with any steady driving. It was gone within 5 minutes on the highway headed to VIR. It came on briefly the next morning, then went out and never returned during the track event. Back to home no light. So it looks to be something at startup.
     

Share This Page