[FEI]

Yeah i clean all those connections on the becm, while you at it do the earth points on the body behind the becm and all the ring lug terminals on it and all the fuses and stuff.

The window not set is just after removing the battery you have to fully open and close all the windows for the becm to recalibrate them

 

[FEI]

For the purpose of this diagnosis which of the settings should I try to discover the ABS-TC fault?
NORMAL
ADRE.APP
ALM.APP
APPMAM.APPAS10.APP
BECM.APP
CANDET.APP
CANINST.APP
ETC.....

Yeah i have no experience with the nanocom, so someone else will have to advise on this

 

[pwood999]

You don't use the apps on Nanocom directly. Use the Menus. (not sure how you're seeing those directly unless something is wrong with it)

 

[Grrrrrr]

No, they do sit in a copper mesh bush. The rubber just sits on top but hasn't stop the sensor bedding down.
In all this searching for the cause of the ABS-TC dash lights being constantly on I want to try and understand the systems that could lead to this happening:
The readout from the dash states: ABS failure, Traction Control failure, lights are on.
The nanocom shows 'no fault' and never has. The systems the nanocom monitors are presumably working correctly, or the nanocom is unable to detect what the vehicle's systems are displaying.
So to focus on the reason why this fault is showing up, do we not have to look more closely at the data the ECU, WABCO D, or other vehicle monitors are reading that is outside the purview of the nanocom?

I do know that Marty has repaired several WABCO D ECUs. A search of his past posts might even reveal what it was he did. He did mention the issue never seemed to occur on Wabco C models.

 

[MontyChambers]

Good morning Grrrrrr
I can’t find Marty?

 

[Rubberknees]

Good morning Grrrrrr
I can’t find Marty?

He's been in New Zealand for quite a while now

 

[MontyChambers]

You don't use the apps on Nanocom directly. Use the Menus. (not sure how you're seeing those directly unless something is wrong with it)

I think it’s in the settings set up, there are many options, I show just a few. They are for something. I leave it on normal until I know what is what!

 

[MontyChambers]

He's been in New Zealand for quite a while now

I'll book a flight ;-)

 

[pwood999]

Do NOT mess with the Nanocom Startup Settings menu.

After power-on, for Wabco faults on your diseasel, select these options in order:
R-ROVER-P38 / EDC / WABCO-D / FAULTS.

Same applies to check INPUTS from sensors, etc. except use the INPUTS menu !!

 

[MontyChambers]

I get no faults on the nanocom, I’ve been informed that this could be that the WABCO D isn’t talking to the BeCM.
To clean the connections on the BeCM I should disconnect the battery first and the clean. But which connector goes to the WABCO D?

 

[Datatek]

I get no faults on the nanocom, I’ve been informed that this could be that the WABCO D isn’t talking to the BeCM.
To clean the connections on the BeCM I should disconnect the battery first and the clean. But which connector goes to the WABCO D?

The Wabco D diagnostic data link goes direct to the OBD connector an nowhere near the BECM.

 

[MontyChambers]

But the ABS and TC dash lights and the ABS, traction control faults do come from the BeCM? So if no faults are shown on the nanocom but are shown on the dash then the faults cannot be updated by the WABCO and BeCM talking to each other?
That’s the reasoning.

 

[Datatek]

But the ABS and TC dash lights and the ABS, traction control faults do come from the BeCM? So if no faults are shown on the nanocom but are shown on the dash then the faults cannot be updated by the WABCO and BeCM talking to each other?
That’s the reasoning.

You are correct in that the ABS ECU signals fault conditions to the BECM and the BECM via a serial data link to the instrument cluster lights the lights and may also show a message.
The problem is that the WABCO D ECU can fail.
I can only see one link from the WABCO ECU to the BECM, if that is correct it must be a serial data link as there is more than one fault condition to be relayed. I do not know what happens if that link is broken in terms of what the BECM might display but it's worth checking that link. Otherwise you may have a problem either with the BECM or the instrument cluster.

 

[kermit_rr]

I think the discrepancy is.. becm doesn't have diagnostic access to the wabco. It can send and receive signals, if that doesn't happen or a signal is implausible/out of range then a light is lit up

I might be wrong, but that's how i understood it

 

[Datatek]

I think the discrepancy is.. becm doesn't have diagnostic access to the wabco. It can send and receive signals, if that doesn't happen or a signal is implausible/out of range then a light is lit up

I might be wrong, but that's how i understood it

I would agree with that.

 

[MontyChambers]

I suppose I could just remove the lights from the dash to do the MOT

 

[kermit_rr]

The mot tester expects to see the abs light come on. If it doesn't then it should fail.
Do you also have a warning in the LCD display?

 

[MontyChambers]

Yes, ABS fault Traction Control Fault

 

[MontyChambers]

I'm running out of ideas here, everything worked fine before the renovations, so I believe the Becm and Wabco D are okay!
Work done so far.
Front end:
New ball joints
New CV boots
New brake callipers
New front ABS sensors
New dust shields
New accumulator bulb
Hevac LED screen fixed
Rear door struts and hangers replaced
New wiper blades
She starts first time every time

 

[Datatek]

It's possible that the Wabco D ECU shows no faults on Nanocom but is still flagging faults to the BECM or sending corrupt data.
One answer would be to try another ECU. Alternatively locate the link from the Wabco to BECM and disconnect it to see what happens. Are you able to drive the car n
and check the sensors live data?