Cannot connect to OBD port

If it's coming out of the cap that suggests that accumulator/pump pressure is leaking into the reservoir through the ABS modulator.
There's a lot of wiring but a lot less than there would be normally due to multiplexing.

I have the same issue.

Ever since I replaced my accumulator and revised the ABS modulator the pump runs more often and loses pressure more quickly. It seems to me that it is not the pump itself since I hooked up a pressure gauge to the pump output directly and let it run up to 160bar and left it for a few days without it dropping. When it's all connected up however the oil runs back into reservoir, suggesting to me that whatever "blocks" the pressure inside the modulator is leaking internally causing the excess to run back into the reservoir, it does not seem to be the pump.

Cheers,
-P

Tried holding it down. Keeps the pressure at around 50mm pedal travel. But only when driving after a few minutes pedal drops.
Even read on rovernet about holding pedal depressed overnight and how that releases little air bubbles trapped in the lines.. did that for 3 days..but main issue is
I still can't connect to OBDii port. Tried to clean every connection I could find under both seats behind both kick panels. ABS module thing.
Checked for corrosion or green spots on all connectors.
Sprayed contact cleaner on everything. Tightened the connectors in the OBD port.
Nanocom powers up. Reads the airbag and EAS but error communications the the ECU..
It's not the nanocom as it reads everything with the puma. And it's the correct adaptor lead..
Stumped.!!

I am currently in the progress of completely replacing the BECM, if at all possible, with a homemade installation and for that I had to identify all connections to and from the BECM. I can share whatever info I got from this so perhaps this helps you?

From memory (I can't connect to the GIT repo containing all the data of this project from this PC right now) the data line that communicates with all the individual parts is shared amongst all components, including the BECM itself. The first go would be to clean all the connectors thoroughly which it seems you have done. Second would be to see if there is any data flowing. Do you have a scope at your disposal or one you might borrow? The data protocol can be seen easily with a fairly cheap scope.

I will try and dig into the docs to find the relevant pins. I do suspect however if in the end you can not connect to the ABS/TCS unit (that is one item) the problem might exists there. Although diagnostics communications are not part of the primary function of the unit, it might suggest that that module is defective.

The pinouts are in the RAVE manual if you have one, but I will look the, up this weekend just to be sure :)

Cheers,
-P

I have been going over my documentation and as it turns out, what I am looking for is not in there :(

To put this into context: This project is about replacing the BECM only so we have only documented the connections to and from the BECM itself. I can confirm that the ODBII protocol datalines do not connect to the ABS/TCS unit from the BECM, they must run directly (I think it is some sort of bus where they are all connected to the same pins on the ODB connector). It does occur to me that I do want to communicate with the devices that remain in the vehicle so I need to figure that one out myself as well but unfortunately I can't do that on the fly right now.

Suffice it to say that apart from a splice somewhere maybe cleaning the connectors at the ABS/TCS end and in de ODB connector should give you the desired result. Checking for a proper ground can be beneficial as well since that can cause erratic behaviour. When I get around to digging up the pins myself I'll post it down here, when needed.

-P

ABS computer PIN out and explination | Range Rovers Forum

Here you go :) pins 13,14,27 it seems need to have data going over them that is 13,14 are the diagnostic lines and 27 seems to be ground. The protocol is ISO9141 but suffice it to say that you should be able to see data on those buses with a scope.

Noteworthy is that the ECU will ONLY communicate when idle it seems, once the road speed has exceeded 2kph on any of the wheels it shuts down the diagnostics ports and dedicates all it's CPU power to doing it's actual job so perhaps there is a cause for the problem you have. Maybe the unit thinks it has moved? (incorrectly)

Cheers,
-P

Thanks for that..
I've gone through a lot of the connections and cleaned all the pins. They're all solid and no rust yet it's still not reading.
When I first bought the vehicle the a.c drain rubber grommet was blocked and water backed up and dropped down and over the OBD ii port. But it ran fine for 2 years. I'm thinking I've missed maybe some connectors that are back up inside the dash.??
Maybe that's the next port of call.

The P38 is like a blind man walking through a crowded nudist beach. You just have to feel your way through it.

Great car except for this one hiccup.

Disconnect plug at ECU and check wiring for continuity and shorts between OBD plug and ECU plug. Don’t worry about what lies between unless you find a problem. Assuming you have a multimeter. [emoji106]