Jump to content
SAU Community

Recommended Posts

Was out for a drive in Tokyo with a fellow member this past weekend when my ABS, TCS and Slip lights came on. We did a test, and yep, no ABS. Scanned the codes and got 17 and 44.

Conveniently this has occured about 500kms after replacing the TCS motor on the throttle body; I've been plagued with a recurring code 17 and TCS motor failure for the past year, although it didnt really phase me until I realised I have shaken coming up in December and codes = failure. 

The TCS motor flap is still moving on startup and I'm hesitant to believe the replacement is causality, after all, it's just a plug and its operation (or lack of) never caused ABS failure before. All fuses are fine - checked visually and with a voltmeter - which then led us to the ABS system. 

As the ABS pumps and relays seem to be one unit and with used variants being two a penny on the auctions, I have taken a punt with a 2,000 yen (with warranty) replacement 47600-AA000. However, after some digging, I've come back with the following headf*ck:

Part Numbers:

47600-AA566

Latest revision of the pump and about 200k from Nissan. This is stated as being compatible with the ER34 RB25DE, RB25DET plus Silvia S15 and Stagea 34.

47600-AA500

Currently fitted to my car, looks as though it has been replaced at somepoint. Historical info is limited although I can confirm it was available for Silvia S15 and Stagea 34.

47600-AA000

Came on the ER34 RB25DE, Silvia S15 and Stagea 34. I can find no reference to it ever being fitted to the ER34 RB25DET, although it did come on the Stagea RB25ET.  

I have three weeks to get this fixed and was really hoping to get a final trackday in for the year before I turn the car back to stock-ish for shaken. So, has anyone had any experience with these ABS actuators and can confirm the interchangeability? Or even better, anyone had issues with the ABS system and managed to fix it by other means? 

We can feel the motor give some kind of response with the car on. It's getting power.

Car is running stock auto ECU. 

Link to comment
https://www.sau.com.au/forums/topic/484180-r34-gtt-er34-abs-failure/
Share on other sites

10 minutes ago, GTSBoy said:

I would Nistune the ECU, override the TCS motor/position code and forget the car ever had it. (in fact, that's exactly what I did, because Neo into R32).

What's code 44 again?

Exactly what @tsuokun said. Nistune isnt possible with the tight timeframe. Plus I'm of the camp that's too pussy to drive with ABS off.

17: ABS-TCS control unit circuit - Throttle control unit detects malfunction in the system. (open throttle sensor, harness, etc.) / TCS/ABS Control unit detects malfunction

44: ABS-TCS communication circuit - Malfunction (open/short circuit, etc) is detected in multiplex communication line between  engine and TCS/ABS

1 hour ago, GTSBoy said:

I would Nistune the ECU, override the TCS motor/position code and forget the car ever had it. (in fact, that's exactly what I did, because Neo into R32).

 

If unable to Nistune in the timeframe look at the ec/tcs/abs diagrams to see what voltage is required so no error appears. May be able to trick it with the right resistor/diode in the circuit as we did that on a mates r34 na +T setup to fake a few signals.

1 hour ago, GoHashiriya said:

44: ABS-TCS communication circuit - Malfunction (open/short circuit, etc) is detected in multiplex communication line between  engine and TCS/ABS

Well, there's your problem. There is a bus wire/wires that connect the ABS and TCS CUs to the ECU. Yoou have a wiring problem there.

2 hours ago, GTSBoy said:

Well, there's your problem. There is a bus wire/wires that connect the ABS and TCS CUs to the ECU. Yoou have a wiring problem there.

Seeing as the system is untouched - bar the TCS motor - I'm wondering whether there is any particular part of it that's prone to failure. Searching in Japanese ive found some examples of people replacing the computer and the motor/pump to rid the ABS/TCS/Slip lights from the dash but they never go into detail. 

The car and loom in question is >20 years old now, been through the hands of several possibly hamfisted dickheads. There are plenty of things that could go wrong, and it always turns out to be something from left field.

You have to go looking for the problem. It won't jump out at you and say "Here I am!".

  • Like 1
17 hours ago, GoHashiriya said:

Exactly what @tsuokun said. Nistune isnt possible with the tight timeframe. Plus I'm of the camp that's too pussy to drive with ABS off.

17: ABS-TCS control unit circuit - Throttle control unit detects malfunction in the system. (open throttle sensor, harness, etc.) / TCS/ABS Control unit detects malfunction

44: ABS-TCS communication circuit - Malfunction (open/short circuit, etc) is detected in multiplex communication line between  engine and TCS/ABS

Sounds like code 17 is just telling you to retrieve actual codes from the TCS/ABS control unit. You can either do it via Consult or by grounding the following pin with the key on but the engine off. Do not touch the brake pedal when pulling codes.

image.thumb.png.800ce004ca86ab6bb2de64cf5609e52a.png

To clear the code after fixing things is going to take the following tap code if you don't have a Consult:

image.thumb.png.95c8822e369ef69334f22b98ad2307fb.png

It sounds like code 44 is referring to a circuit signal integrity issue on pin 16:

image.thumb.png.c1c206dbae20ccc7966a49d703842086.png

image.thumb.png.406443c5db31eee88b88c4dc7a9b567d.png

There's a diagnosis tree but a lot of it calls for checking what kind of signal you get on the Consult. NDS1 does not support reading ABS codes or data unfortunately. I highly recommend getting the R34 Skyline service manual to help figure out what's going on here. It's possible your ABS control unit has given up the ghost and is spewing nonsense over the bus which is causing the ECU to throw codes. Also possible there's a harness failure between the ECU and the ABS C/U. I'm not omniscient so you're going to have to be the one to see whether it's a harness problem or maybe you need to recap your ABS control unit or something else.

image.png

  • Like 1
1 hour ago, joshuaho96 said:

Sounds like code 17 is just telling you to retrieve actual codes from the TCS/ABS control unit. You can either do it via Consult or by grounding the following pin with the key on but the engine off. Do not touch the brake pedal when pulling codes...

I appreciate the level of detail in this, I was unaware NDS1 did not give out the entirety of the codes. We initially scanned it using the NisTune software from @tsuokun. That's where we pulled code 44. Actually, code 44 has since disappeared, and upon running the car this morning there were no warning lamps on the dash - which is of course more annoying.

I found a broken earth from the manifold to the strut tower, although this is likely unrelated.

You've given me a fair bit to go off so I'll review this and see what I can find.

 

20 minutes ago, GoHashiriya said:

I appreciate the level of detail in this, I was unaware NDS1 did not give out the entirety of the codes. We initially scanned it using the NisTune software from @tsuokun. That's where we pulled code 44. Actually, code 44 has since disappeared, and upon running the car this morning there were no warning lamps on the dash - which is of course more annoying.

I found a broken earth from the manifold to the strut tower, although this is likely unrelated.

You've given me a fair bit to go off so I'll review this and see what I can find.

 

I would still try and pull the ABS codes, it's possible they're still in memory but not actively lighting the malfunction lamps. The ECU codes IIRC work similarly, even if the error goes away you can still read them via Consult with a counter indicating how many times the code was triggered. Intermittent issues like that would make me want to pull out the control unit first and foremost to check for dead caps. All of these cars are super old now and electrolytic capacitors all eventually fail on a long enough timeline.

Appreciate the info, first port of call will be digging for these additional codes. I may try to get ahold of a known working ABS computer from a friend and try the easy way of plugging it in to see if that works - I imagine the same could go for the actuator up front. 

Grateful used ABS computers and actuators are pretty cheap still, if I need one.

Thanks for the help @joshuaho96, pulled the codes today and got 36, rear left ABS sensor short. Then found what you see in the pic. 
 

Gonna get it on the lift this afternoon and attempt to sort it out. 
 

Fingers crossed may get next week’s track day in after all. 

74C8B8CF-B2E1-4D3F-8D90-837A6D84181F.jpeg

That's a mechanical problem that has caused an electrical problem. I see the damage on the end of the sensor, so presumably that's your sensor short. But it would appear to have been caused by the tone wheel moving axially out of position. It's supposed to be contained within the shield and aligned with the sensor. It's not.

3 hours ago, GTSBoy said:

That's a mechanical problem that has caused an electrical problem. I see the damage on the end of the sensor, so presumably that's your sensor short. But it would appear to have been caused by the tone wheel moving axially out of position. It's supposed to be contained within the shield and aligned with the sensor. It's not.

Yeah that's the one. Actually, appreciate this as I couldnt wipe the 36 code after and didnt think the signal wheel had made contact with the sensor - it had. I left the car at the shop and will have my mechanic switch it out this week. I know, it's an easy job, but I have zero time at the moment. Shaken is on the 5th. 

On 11/8/2022 at 12:24 PM, joshuaho96 said:

Sounds like code 17 is just telling you to retrieve actual codes from the TCS/ABS control unit. You can either do it via Consult or by grounding the following pin with the key on but the engine off. Do not touch the brake pedal when pulling codes.

image.thumb.png.800ce004ca86ab6bb2de64cf5609e52a.png

Hey, where did you get the service manual in nihongo? My mechanic is asking for it. Searching in Japanese is like dating whilst deaf and blind

16 hours ago, Murray_Calavera said:

I hope there aren't any issues with me posting this here. 

 

16 hours ago, joshuaho96 said:

You're both absolute heros, thank you.

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

    • 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.
    • 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.
×
×
  • Create New...