2002. P38 4l thor/motronic. ABS, TC lamps

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.
Go to agree with @Datatek , Ideally you are looking for stable battery volts anywhere between 12.4 to 12.7 at the start of all things.
Once your starting point is anything less than 12.4V (a battery in need of charging) the systems will all start playing up.
 
Thanks, and thanks again. Put new battery on. Had to put it on and leave it. Nothing changed. I will check voltages in the morning. Please don't go away. Got another month here. Contemplating knocking it on the head till I get home. (Is that a safe option?) Regards p.
 
New battery on last evening. Bonnet up. 12.26v. tickover and 2000rpm 14.30v all on the same. As far as becm sleeping, I guess it must as I can leave it up to 5 or 6 days And it still fires up. As far as difinitive testing procedures are concerned, I'm in my infancy. I am capable of working to learn. The old battery's been off all night and is showing 12.13v. the nanocom still shows no faults. Anyone fancy a busman's holiday on the med?
 
Can I just add? I ditched all my hawkeye stuff after praises for the nanocom were sung around here. On reflection, I had an incessent problem with my EAS. I could clear faults with hawkeye in the eas ecu but the dash lamp never went out until i went into the becm page and cleared the logged fault there. I've yet to find a similar function on the nanocom. Could I assume that clearing faults in the relevant ecu with nanocom carries out any necessary actions with the becm? I need a magician here. Badly. Regs. P.
 
supapete said:
Can I just add? I ditched all my hawkeye stuff after praises for the nanocom were sung around here. On reflection, I had an incessent problem with my EAS. I could clear faults with hawkeye in the eas ecu but the dash lamp never went out until i went into the becm page and cleared the logged fault there. I've yet to find a similar function on the nanocom. Could I assume that clearing faults in the relevant ecu with nanocom carries out any necessary actions with the becm? I need a magician here. Badly. Regs. P.
Click to expand...

The BECM does not store faults it sets parameters. From what i read on here Hawkeye is a joke.
 
supapete said:
Can I just add? I ditched all my hawkeye stuff after praises for the nanocom were sung around here. On reflection, I had an incessent problem with my EAS. I could clear faults with hawkeye in the eas ecu but the dash lamp never went out until i went into the becm page and cleared the logged fault there. I've yet to find a similar function on the nanocom. Could I assume that clearing faults in the relevant ecu with nanocom carries out any necessary actions with the becm? I need a magician here. Badly. Regs. P.
Click to expand...
The manuals are pretty comprehensive. Take a look.
 

Attachments

  • P-38- Lucas EAS ECU Guide.pdf
    100.6 KB · Views: 194
Downloaded every page and read them. I've also had the relevant pages attached by black box to their technical help line. I was hoping that someone more experienced and expert than me could see something I couldn't. They do exhaustively cover nanocoms functions and capabilities. That's patent. Where I'm stuck is nanocom shows no faults. Hence my desperate posts. Thanks again. P.
 
Have you checked the brake light switch ,it has 2 contacts 1open and1 closed these need to reverse when you touch the brake pedal. if they dont ,you will have abs and tc light on. I know because mine does it occasionally. check with nanocom to see this is happening .if not reset switch.
 
Keep em. coming, please. Yes. New switch, adjusted and readjusted. Nanocom sees them operational. I feel.it in my water someone will switch the light on at the end of the tunnel.
 
Grrrrrr said:
Running out of ideas to be honest. More like delirious thoughts of a man in an idea desert.

Have you managed to get a trace where it faulted? You'd have to stop after it faulted so you knew where on the trace it happened to be sure, or use a stopwatch. If not, maybe a drive is in order? More pleasant than cleaning reluctor teeth!
Click to expand...

It's been a while, but this is the only input I haven't followed up on. I've had to do a "modicum" of homework to be able to carry a meaningful trace out.
CSV files aren't permitted here. The trace shows all input voltages within the spec. Previously I had equi resistance both at the sensor fly leads and ecu on all sensors. I got equi dc volts at all sensor chassis connectors.

Now, according to the traces which I can't upload here the right front wheel goes from 1.7 whatevers to 1.8 whatevers and stays there whilst all others follow exactly the same rotation rate.

I've updated the nanocom firmware and downloaded te latest swish CSV viewer.
Thanks grrrrr.
P.
 
supapete said:
It's been a while, but this is the only input I haven't followed up on. I've had to do a "modicum" of homework to be able to carry a meaningful trace out.
CSV files aren't permitted here. The trace shows all input voltages within the spec. Previously I had equi resistance both at the sensor fly leads and ecu on all sensors. I got equi dc volts at all sensor chassis connectors.

Now, according to the traces which I can't upload here the right front wheel goes from 1.7 whatevers to 1.8 whatevers and stays there whilst all others follow exactly the same rotation rate.

I've updated the nanocom firmware and downloaded te latest swish CSV viewer.
Thanks grrrrr.
P.
Click to expand...

To attach here add to .zip and attach that.
 
supapete said:
voila. & thanks again
Click to expand...

Hi Pete.

I've had a look at the NICO file. I think I need someone with WABCO D to check theirs, if possible. @wammers might have WABCO D?

On my WABCO C the brake switches are mutually exclusive, i.e. when #1 is OPEN then #2 is CLOSED or vice versa. They're never both OPEN or both CLOSED. Yours are. Is that normal for WABCO D?

Also, I reckon your front right sensor isn't following the others. it doesn't change much. Weirdly the rear left sensor voltage doesn't change much but it seems to realise the wheel speed is changing. Not sure what to make of that. Maybe @martyuk might have a better idea as he's played with these ECUs.

Excel spreadsheet I used to play with attached in the zip file.
 

Attachments

  • WABCOD_Inputs_20190425.zip
    32.2 KB · Views: 161
Grrrrrr said:
Hi Pete.

I've had a look at the NICO file. I think I need someone with WABCO D to check theirs, if possible. @wammers might have WABCO D?

On my WABCO C the brake switches are mutually exclusive, i.e. when #1 is OPEN then #2 is CLOSED or vice versa. They're never both OPEN or both CLOSED. Yours are. Is that normal for WABCO D?

Also, I reckon your front right sensor isn't following the others. it doesn't change much. Weirdly the rear left sensor voltage doesn't change much but it seems to realise the wheel speed is changing. Not sure what to make of that. Maybe @martyuk might have a better idea as he's played with these ECUs.

Excel spreadsheet I used to play with attached in the zip file.
Click to expand...

Same sort of pattern on the TUV file with the exception that the brake #1 and brake #2 do have opposite values a few times but strangely this coincides with the ignition supply voltage dropping to 0V. Did the car cut out? Or was that when the car threw a fault? Power supply to ECU pin monitoring ignition voltage shorted out? Where does it get the ignition voltage from? BECM pin on connector?

TUV file in Excel spreadsheet in attached .zip.
 

Attachments

  • WABCOD_Inputs_20190425_TUV.zip
    40.4 KB · Views: 147
I can only thank you for your attention. As you and everyone, I'm sure, knows I'm well out of my depth. I can catch up but it takes a while. A slow depress of the brake shoes brake switches operate momentarily in sequence on the nanocom screen. Today I reversed the feeds to the front sensors to observe the resultant trace. The nanocom refused to record. IllI work on your response and hope as you suggest we get some big guns on board along with you. Thanks again. P.
 
supapete said:
I can only thank you for your attention. As you and everyone, I'm sure, knows I'm well out of my depth. I can catch up but it takes a while. A slow depress of the brake shoes brake switches operate momentarily in sequence on the nanocom screen. Today I reversed the feeds to the front sensors to observe the resultant trace. The nanocom refused to record. IllI work on your response and hope as you suggest we get some big guns on board along with you. Thanks again. P.
Click to expand...

I guess you could always ask on the Blackbox forum?

@pwood999 is good with electrickery. Maybe he has a clue?
 
This is official. Firstly thank you very much to all who have scratched their expert heads on this thread. I've complied with every single input . However, we're upping sticks on Wednesday and hauling our caravan back through Spain, France, England and Wales. Complete with my ol pals abs and TC lamps. If I may, I will resurrect matters late may . I've posted this blurb so no-one thinks I've blanked their work. Now, the uk summer beckons. Regards. P.
 
We encountered the yellow jacket thugs all the way down France from Cherbourg to Perpignan. Got diverted 6 times. When is the bricking up ceremony? Book me in. I'll go on the mixer and hod . Portsmouth to Santander November !!
 
You must log in or register to reply here.

Similar threads

02Disco2
Disco 2 Abs & TC lights but no fault codes
Replies
1
Views
214
sierrafery
sierrafery
O
03 L322 EAS ECU Can bus fault / ABS temp system deactivation
Replies
1
Views
592
oldradiotech
O
Dieselmec 42
Front abs kicking on
Replies
3
Views
466
Mark Piercy
Mark Piercy
Henry.adams
Traction control problems
Replies
9
Views
622
Henry.adams
Henry.adams
V
2 amigos ABS and TC light L314 freelander 1 (not solved) (new)
Replies
10
Views
1K
Veslav
V
Back
Top