Jump to content
SAU Community

Recommended Posts

My timing was jumping around by big numbers in just few seconds. I figured it was my CAS, so I made a WTB thread and ordered another unit from a SAU member. http://www.skylinesaustralia.com/forums/topic/424325-wtb-rb25det-cas/ The new unit arrived today, although the timing is a bit more stable than with my CAS, its still jumping around.

Do I have my hands on 2 faulty CAS or is could it be something else? I need a definite yes or no answer if this is normal behaviour for a R33 GTST-t Series 1.

I have used the same diagnostic gear on other skylines, but only series 2 rb25s, and they seemed to hold 15 just fine. Anyone have a S1 R33 willing to let me hook up the nissan consult to it?

Edited by sonicz

Does it hunt when it returs to idle? Looks like it is from the timing. It seems to hold 15 pretty well once it settles down

The Revs dont look like its hunting to bad if it is, but the timing seems a bit like it might be. What happens if you rev it and hold it at a certain RPM does the timing stay pretty stable?

Does it hunt when it returs to idle? Looks like it is from the timing. It seems to hold 15 pretty well once it settles down The Revs dont look like its hunting to bad if it is, but the timing seems a bit like it might be. What happens if you rev it and hold it at a certain RPM does the timing stay pretty stable?

No it seems to idle just fine, no more "hunting" than any other RB25 i've seen, even less in fact.

It looked like it holds 15 for those few seconds, but that was just a lucky streak. If I left it for a bit longer it would have been back to its old ways :)

At the higher RPM it seems to hold the timing ok, certainly better down low where the problems are.

I'll try get a friend to record the laptop whilst I actually go for a drive.

I'd be looking for a bad connection in the CAS wiring. That looks like noise more than jitter. You tend to get jitter (caused by dud CAS) at high RPM, not idle.

Its a possibility. But I couldn't "look" for that to save my life. I wouldn't know where to start, and it doesn't sound like a good idea to just take it to an auto electrification who been working on commodores for the past 40 years and pay them by the hour to check something they have no clue about?

Anyone tuner in syd familiar with the car and wiring and these types of "tuning" issues that would have a look at it without wanting an arm and a leg?

With the new CAS i got today, the car definitely has much much more grunt down low. So it has made a difference. But I really want to find another s1, check that the timing is stable, and put that cas in my car to check if it ok. Free pizza, any topings in syd to anyone who lets me do that :D

You guys are reading a gauge, that is giving you the timing BTDC, based on a sensor...

If sensor is physically flogged the timing will move around when you have a timing light on it. The gauge will stay stable though (What you're looking at). The issue is something is making the ECU move the timing around. The CAS only tells the ECU where the engine is physically up to.

Flogged out star drive inside the exhaust cam.

Poor quality sensor

Poor quality wiring

Damaged shielding

We put a scope on the two cam sensor outputs and compare them to known good traces to determine if its a fluctuating signal.

You can determine anything with the ignition timing trace on "consult"

Cant see the vid here at work but is the car up to temp when checking the timing?

Because the car has more grunt doesnt necessarily mean the cas is working better. It could mean you have advanced the timing some when putting in the new one, so you need a timing light to set it back to 15*

Ignitor could be a possible cause also on the S1

Now, that's not entirely true. The ECU calculates the engine speed from the stream of pulses it receives from the CAS. The CAS doesn't calculate rpm and send that number to the ECU, it just sends pulses. So if the ECU is trying to work out the engine position (which of course is what it is supposed to do) but the nice steady stream of rpm pulses is all messed up (which is what happens when the CAS or drive is flogged) then the ECU has a hard time knowing exactly where the engine is. It has a stab at getting the timing right, but the timing point is of course calculated with respect to the rpm and it can all get very untidy.

You guys are reading a gauge, that is giving you the timing BTDC, based on a sensor... If sensor is physically flogged the timing will move around when you have a timing light on it. The gauge will stay stable though (What you're looking at). The issue is something is making the ECU move the timing around. The CAS only tells the ECU where the engine is physically up to.

Flogged out star drive inside the exhaust cam.

Poor quality sensor

Poor quality wiring

Damaged shielding

We put a scope on the two cam sensor outputs and compare them to known good traces to determine if its a fluctuating signal.

You can determine anything with the ignition timing trace on "consult"

1.So a new cam gear? How does a star drive flog out anyway...and how do I check it.

2.Highly possible the 2nd CAS is faulty too. The fact that it performs better than mine tells me it has a lot do with the cas.

3.So New wiring harness?

4.Damaged Shielding to what?

Don dada, yea the car is up to temp. I've got the CAS adjusted roughly the same, and it still has the issues whether its advanced or retarded.

Here is a vid of my orginal CAS again

Notice its a lot more erratic than the new cas.

If there is a fault with one CAS it seems likely another identically manufactured cas of the same age and condition can develop a similar problem.

Edited by sonicz
  • Like 1

So no one is willing to let me hook up their series 1 to consult or better yet try their cas??

I don't want to have to buy another cas, this time a $500 new brand new one.

I may as well buy another r33 at the rate fixing this car is costing me...

Edited by sonicz

seriously?

? Whats wrong with that? Its just a cas.

I've seen people even lend stuff for free to clear defects here on sau.

You can charge me to rent it out if you want, hourly daily, by the minute etc. I only need a few minutes.

Also the nissan consult thing is easy. Its just a plug that dangles from your foot area. I'll read your fault codes for free eh?

Edited by sonicz

Ok , why do you think you actually have a problem? The ecu alters the timing to maintain idle. Unplug the tps and see what happens. Thats what you have to do when timing the car. How did you set tge base timing when you swapped the cas?

No, But I'm not sure when the timing belt was done last time. Could it be loose?

I'll get a flash light and take some pics tomorrow down the hole. I don't even know how a cam gear wears out ffs.

Ill try video the car while driving as well.

It's not the cam gear that is worn out, the cas doesn't connect to the cam gear at all. It passes straight through the middle of it and into the camshaft. It's possibly the drive in the camshaft that is flogged out, not anything to do with the cam gear. Can happen when people don't fit the CAS properly, eg. not putting the spacers in between the CAS and the mount, causing the CAS to sit further in than it should and damaging things.

Your best off giving it to someone to look at for you who knows what causes the issues your having.

30mins and the problem should be located.

5mins pulling the CAS out and physically looking at the drive peg

15mins putting a scope on the two signal wires

5 mins checking the shielding

And 5 mins of fart arsing around tidying up.

It might take more than 30mins to fix the problem but locating it is not hard.

I've got several Sensors at the workshop your welcome to try them but chances are it won't be 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


  • Latest Posts

    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
    • When I said "wiring diagram", I meant the car's wiring diagram. You need to understand how and when 12V appears on certain wires/terminals, when 0V is allowed to appear on certain wires/terminals (which is the difference between supply side switching, and earth side switching), for the way that the car is supposed to work without the immobiliser. Then you start looking for those voltages in the appropriate places at the appropriate times (ie, relay terminals, ECU terminals, fuel pump terminals, at different ignition switch positions, and at times such as "immediately after switching to ON" and "say, 5-10s after switching to ON". You will find that you are not getting what you need when and where you need it, and because you understand what you need and when, from working through the wiring diagram, you can then likely work out why you're not getting it. And that will lead you to the mess that has been made of the associated wires around the immobiliser. But seriously, there is no way that we will be able to find or lead you to the fault from here. You will have to do it at the car, because it will be something f**ked up, and there are a near infinite number of ways for it to be f**ked up. The wiring diagram will give you wire colours and pin numbers and so you can do continuity testing and voltage/time probing and start to work out what is right and what is wrong. I can only close my eyes and imagine a rat's nest of wiring under the dash. You can actually see and touch it.
    • So I found this: https://www.efihardware.com/temperature-sensor-voltage-calculator I didn't know what the pullup resistor is. So I thought if I used my table of known values I could estimate it by putting a value into the pullup resistor, and this should line up with the voltages I had measured. Eventually I got this table out of it by using 210ohms as the pullup resistor. 180C 0.232V - Predicted 175C 0.254V - Predicted 170C 0.278V - Predicted 165C 0.305V - Predicted 160C 0.336V - Predicted 155C 0.369V - Predicted 150C 0.407V - Predicted 145C 0.448V - Predicted 140C 0.494V - Predicted 135C 0.545V - Predicted 130C 0.603V - Predicted 125C 0.668V - Predicted 120C 0.740V - Predicted 115C 0.817V - Predicted 110C 0.914V - Predicted 105C 1.023V - Predicted 100C 1.15V 90C 1.42V - Predicted 85C 1.59V 80C 1.74V 75C 1.94V 70C 2.10V 65C 2.33V 60C 2.56V 58C 2.68V 57C 2.70V 56C 2.74V 55C 2.78V 54C 2.80V 50C 2.98V 49C 3.06V 47C 3.18V 45C 3.23V 43C 3.36V 40C 3.51V 37C 3.67V 35C 3.75V 30C 4.00V As before, the formula in HPTuners is here: https://www.hptuners.com/documentation/files/VCM-Scanner/Content/vcm_scanner/defining_a_transform.htm?Highlight=defining a transform Specifically: In my case I used 50C and 150C, given the sensor is supposedly for that. Input 1 = 2.98V Output 1 = 50C Input 2 = 0.407V Output 2 = 150C (0.407-2.98) / (150-50) -2.573/100 = -0.02573 2.98/-0.02573 + 47.045 = 50 So the corresponding formula should be: (Input / -0.02573) + 47.045 = Output.   If someone can confirm my math it'd be great. Supposedly you can pick any two pairs of the data to make this formula.
×
×
  • Create New...