Jump to content
View in the app

A better way to browse. Learn more.

300ZX Owners Club

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

About 2 weeks ago I found my car was running safety boost and was chucking out code 34.

 

Being the det sensor, I followed the guide and put a 1m-ohm resistor in place at the connector block in the engine bay.

This worked fine for a couple of days (had code 55) and then the car went back into code 34!!!!! :x:

 

Following my previous post earlier this week, I decided to wire directly to the ECU at pin point 23 :eek: , I spliced into the wire and connected the 1m-ohm resistor in line and then grounded the other end to the body of the car!

 

This seemed to work fine and the car is back running properly on 1-bar boost :dance: , but, the car is still throwing out code 34! :headvswal :headvswal

 

Now when I'm driving the ECU check light keeps going on and off at will........... theres no noticible pattern, it just comes on for a few secs then goes off, I can maybe then drive for 2 minutes before it does it again, then it could be a couple of seconds....... the light stays on for different lengths of time each time!

 

I'm really stuck with this one and need help!?

 

(I recently had the car chipped to 1-bar, could this have caused a fault within the ECU?)

Featured Replies

Have you reset the ECU since fitting the resistor? If not it will continue to show for the next 50 starts then self clears.... Are you sure the ECU connector is correctly seated?

sounds like a fooked ecu or chip, code 34 won't make the check light come on.

 

faulty or corrupt chip^^

 

and check connection to ecu as andy has said! if its to tight or not square in the ecu then it will put the engine light on!

can i just say something...

 

code34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34 code34 CODE34 CODe34 code34 code34 CODE34 CODe34 CODe34 code34 code34 CODE34

 

 

:wack:

 

sorry couldnt resist, i have beerage in me and far too much time on my hands!

  • Author

I thought i'd reset the ecu.............tell me if this sounds o.k.?

 

when i wired in the resistor directly to the ecu wiring the battery was completely disconnected, it had been disconnected for about an hour.

 

i have since driven the car and the engine check light didn't come on once :) and the car is running on full boost.........but code 34 is still showing :headvswal

 

i'll take it i haven't properly reset the ecu..........any other ways i can do it?

Leave the battery off overnight to be sure :)

had a quick try of this earlier myself

can anyone tell me where Ive gone wrong???

First of all dissconnected battery, then splice one end of 1meg ohm resister too pin 23 (if your looking down at ecu 3rd pin too the right of the bolt top row dirty white colour??) the other end earthed to body work.

reconnected all up

ignition on an reset ecu with datascan

started engine code 34 :headvswal :headvswal :headvswal :mad:

do I need to leave battery off for longer or will the datascan reset it ok

Dohh didnt drive car to see if was boosting ok :headvswal :headvswal

any help appreciated :bow:

datascan will clear the codes fine. And it sounds like you are splicing into the wires at the ECU, which are allready connected up. Why are you not putting the resistor in the knock sensor plug in the engine bay?

datascan will clear the codes fine. And it sounds like you are splicing into the wires at the ECU, which are allready connected up. Why are you not putting the resistor in the knock sensor plug in the engine bay?

tried that but still get 34 so thinking the wiring might be damaged so tried at ecu :(

does the plug need to be disconnected???

  • Author

Hey man, I did disconnect the plug and from my memory the wire I spliced was yellow! :wack: could easily be different colours on different cars!

 

I completely took my ecu out and double, then triple checked against the pin diagram to make sure I spliced the correct wire!

 

I've now got code 55 and the car is boosting strong :) :dance:

Hey man, I did disconnect the plug and from my memory the wire I spliced was yellow! :wack: could easily be different colours on different cars!

 

I completely took my ecu out and double, then triple checked against the pin diagram to make sure I spliced the correct wire!

 

I've now got code 55 and the car is boosting strong :) :dance:

:dance:

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Terms of Use

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.