Jump to content
SAU Community

Recommended Posts

Hi, sorry if I posted this in the wrong section, I also used the search button but came up with nothing.

So when my 33 idels at traffic lights or where ever the revs start going crazy, goes down real low to properly around 500 rpm all the way up to properly 3000-3500 rpm, as soon as I take off and drive the car is fine again.

Any ideas?

Link to comment
https://www.sau.com.au/forums/topic/368591-skyline-idelling-hi-and-low/
Share on other sites

2 things,

1: may possibly be the IAC valve. this often causes a fluctuating idle.

2: the ideal location for a BOV is where the stock one is located.

also, was the plumback pipe blocked up? it should also be noted that RB's don't like atmospheric BOVs that much. it usually tends to make them misbehave when you lift off due to the ecu dumping a heap of fuel in. this may be part of your problem. if you have the stock bov then put that back on and block off the aftermarket one. see if that solves the problem.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • I was more thinking so it doesn't flop around as much rather than for rotating it. Once you have the balance right, it should rotate well enough, depending on how much resistance there is on the pivot. I think you said the pivot point was on a bearing though didn't you?
    • You can get them with the worm drive rotator but I was too tight to pay another $250-$300 so manual labour it is! I don't think it will be too hard to rotate though. 
    • Sag as in the windows start to slowly open themselves, or they're just slow to go up/down with engine off?
    • It looks like it needs a big worm gear drive on it to control the rotating, not a few sloppy pins!
    • As Duncan said, first there was OBD, which few cars used, then came OBD2.   Now an interesting point, OBD2 isn't even for what you want to do. OBD2 is for emissions testing. There is some sensor data on OBD2, but it's up to the manufacturer what they're putting on it. Most scan tools operate on UDS, which like OBD2 is a standard built on-top of CAN. UDS specifies how to structure a message, what very limited things mean such as "read memory address" but it does not specify what is stored in which memory address, that is all up to the manufacturer. You either a scan tool compatible with that vehicle, or to know how to reverse engineer all the data, which can take a VERY long time and a lot of vehicles to get it right. Oh and then the manufacturer does a firmware update and changes what's where... Ask me how I know that as fact Oh, and by the time you've got the scan tool that supports all the manufacturers stuff, well, you're back at "But a consult cable and the Nissan software" The main difference being most manufacturers software these days works with the same hardware readers, as the readers are built to support J2534 which is another standard for how the PC communicates with the tool to make it do specific things on the car...
×
×
  • Create New...