Kingcarr Posted November 29, 2013 Share Posted November 29, 2013 Hi Guys, Been battling this error 34 for a while now... the specs of the Car: Blitz Access ECUCT9b @ 1 BarFMICStraight Through ExhaustFront air intakeRRFPR @ 2.6barTMD Fuel PumpPLX Wideband AFR - getting around 10 on the guage on full boost and around 15 when idling. What ive tried to fix the issue: New vac linesReplace with known working sensorECU Reset - disconnect battery overnight, removed efi fuses and unplugged ECUTried different stock ECU Im tempted to run fresh cables from the MAP/BPS sensor to the ECU as that's the only thing that hasn't been tried that I can think of?!? Please help! Nathan Quote Link to post Share on other sites
micky boy Posted November 29, 2013 Share Posted November 29, 2013 (edited) If you turn the boost down to say 0.6bar of boost what happens? Edited November 29, 2013 by micky boy Quote Link to post Share on other sites
H_D Posted November 29, 2013 Share Posted November 29, 2013 (edited) check the vacuum pipe on the map sensor the tiniest tear or hole can cause this fault.Does the code only come up when your at full boost or does it come up when you are boosting below 1bar? by the way why are you using a rrfpr with a blitz ECU this is not reccommended. Edited November 29, 2013 by H_D Quote Link to post Share on other sites
Kingcarr Posted November 29, 2013 Author Share Posted November 29, 2013 the error comes on as soon as I pull away, so not even on boost. and It was there when the car was running stock pressure on the standard actuator, even on low boost. as mentioned above, I have replaced the hose on it, ive even tried a straight hose bypassing the filter too to see if that would help! Ive also tried a T piece on it and ran it to my boost guage to check there was boost and vac getting through ok. I wasn't aware that the RRFPR wasn't recommended when running a Blitz, I purchased and fitted it before I got the blitz as I was planning on running a FCD, but then the plans changed and I was told its no good running a FCD! I cant see it causing much harm being set 0.3 above stock pressure? the guys at my local RR said it was fine when I had it dyno'd and my wideband checked. Quote Link to post Share on other sites
H_D Posted November 29, 2013 Share Posted November 29, 2013 when you reset the ecu did you do a diagnostic check to make sure the code was cleared on the ECU,If the code does not clear after the reset then your ecu is duff. The blitz ecu is supposed to be ran with the stock fpr therefore it will constatly keep having to adjust and trim itself when using a rrfpr Quote Link to post Share on other sites
Kingcarr Posted November 29, 2013 Author Share Posted November 29, 2013 The morning after disconnecting the battery, I checked the error code after it had got to temp on idle, and the engine management light flashed loads of times fast, then as soon as I pulled off, it came back on with the same error. It's happened on my standard ecu and my blitz, on both the new sensor and the old one! I'll put the standard pressure reg back on then! But error 34 came before fuelling anyway :/ Quote Link to post Share on other sites
Kingcarr Posted November 29, 2013 Author Share Posted November 29, 2013 Just done another test and it's putting out 52 now, not 34 :/ it was deffo 34 last night! So 52 is knock sensor, any basic checks to resolve this before purchasing another sensor? Quote Link to post Share on other sites
H_D Posted November 30, 2013 Share Posted November 30, 2013 Check the knock sensor wiring. Does code 52 come up on idle or only between 2500-2900 rpm.Iirc the ecu starts scanning for knock somewhere between 2500-2900RPM. Quote Link to post Share on other sites
Kingcarr Posted November 30, 2013 Author Share Posted November 30, 2013 Yup, after I pull off, so I guess as soon as I'm into that rev range! I'll try check the wiring tomorrow, any idea what pin it is ecu side? Quote Link to post Share on other sites
Glanza1996 Posted September 21, 2016 Share Posted September 21, 2016 Sorry bringing up an old thread but I got the same issues did you ever find out the problem? But I got error code 34 & error code 52 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.