Jump to content
SAU Community

R33 S2 Gts-T Engine Dies Randomly, Won't Start, Cas Replaced Issue Continues


Recommended Posts

Afternoon all,

Quick background:

- 1998 R33 S2 GTS-T with minor mods - brant security alarm fitted.

- 120,000 kms

Summary:

- Engine was losing power (would hesitate then pick up) at 1,500 - 2,000 RPM and then died suddenly after having been doing this for a few weeks.

- Electrical's continue to work and immobiliser not kicking in (engine light on), engine will turn over but not start immediately after.

- Starts again after 20 - 30 minutes and runs for maybe 5 minutes at most before dying again

- Fuel pump flowing ok and primes when power turned on, mechanic checked and fuel flow ok.

- Checked diagnostics and returned 11 CAS code (need to check again now it's died again)

- Replaced with second hand R34 NEO GTT CAS from JustJap, mechanic says car ran fine for "30 minutes"

- Picked it up and same issue occurred within 200m where engine died and wouldn't start.

Note:

- Coil packs / spark plugs were replaced approx. 10k ago

Looking to get some assistance in understanding what the issue may be and how best to isolate.

Consideration:

- AFM

- ECU

- Wiring issue

- Earthing issue

- Immobiliser

- ?

Links

Afternoon,

Idle prior to stalling was fine, no lumpiness or change in tone.

Quick update:

- have disconnected AFM to see if it would start in limp mode, engineer turns over but no starting.

- checked CAS is connected ok and rotated to see if any difference. No change.

- won't start at all now.

Next steps:

- purchase consult cable so we can see what the sensors are showing

- going to replace field filter and check fuel pressure to make sure issue isn't a blockage.

- will also look at testing CAS again and then start to check electricals and also lines to make sure no leaks etc

Update:

- Fuel Filter replaced, no issue with fuel as pushing out when pump priming

- ECU is now showing 55 (no error) and the engine still won't start.

- Next step is to check the wiring and see if there is anything other things broken

Does it just crank, and not even sound like its trying to fire?

I'll just throw these out there:

1) second hand CAS could be faulty

2) disable alarm if possible to eliminate 100% (seen faulty alarms still allow reds depending on set-up)

3) spark issue?
4) timing issue (could've jumped a tooth or stripped ribs on the belt? Worth having a look to see if the cams gears /belt spin while cranking.

Sorry to Hi-jack the post Links haha :whistling:

But I'm currently having the same sort of problem with my S2 33!

Car will die when it gets warm (bit under half temp on gauge) have tried two cas's and a different afm. When car dies it will crank but wont fire but if you leave the car to cool down it starts first turn and will run until it dies again..

seriously ditch the brant alarm.. biggest pos... they came factory in my sti... extremely annoying when they are on their way out.

i have the same prob... car is fine when cold.. when its hot it wont start... this is the alarm/immobiliser failing...

there has been some stories of the brant alarm immobilising the engine whilst freeway driving..

Edited by defari

seriously ditch the brant alarm.. biggest pos... they came factory in my sti... extremely annoying when they are on their way out.

i have the same prob... car is fine when cold.. when its hot it wont start... this is the alarm/immobiliser failing...

there has been some stories of the brant alarm immobilising the engine whilst freeway driving..

Do you think this could be my problem also? I have a Mongoose M80

Edited by Brady_033

Afternoon all,

Thanks for the feedback.

Update:

- Have ordered ECUTalk to be able to look at what is being read from the sensors.

- Based on the ECU returning 55 (all is ok) I am planning to look at disabling or removing the Brant alarm so that we can rule that out.

Given the behavior and everything seems to be ok in general, i'll give the alarm the next focus and see where we go to from there.

The coolant temp sensor can do what your describing, i had to replace mine in my s2r33 as well... It showed an error on the pfc hand controller as well so consult should pick it up

Morning all,

Update in the last couple of days. Received consult cable hooked it up, ecu is showing 55 so no errors being reported.

Turned the car over and it started first go - left it to idle for a while and then have taken it up / down the road while monitoring. Everything was working ok which means I now need to consider heading out for a few longer drives.

Brant alarm keypad isn't lighting up so my thoughts are that there is still an issue and it's the alarm however i'll deal with it shortly.

Thanks everyone for your feedback. Still not confirmed what the root cause was however will see how it goes.

Links

  • 3 weeks later...

Morning all,

Thanks for the prompt as always good to close out a post.

  • After plugging in a consult cable and tracking the data when the car died the ignition was stopping. I called a Brant alarm technician to come and have a look.
  • Keypad immobiliser module had a faulty relay which was triggering when it over heated - this was causing the relay to trigger and cut the ignition.
  • Crank angle sensor was also replaced which has addressed the loss of power issue so all back on the road.

Links

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

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • 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.
×
×
  • Create New...