rangerovers.pub
The only place for a coil spring is up Zebedee's arse
Member
Joined:
Posts: 42

Findings on nanocom when the lights came on were all sensors reading 2.35v except right hand rear which was zero volts. Dmm said 5 volts at all abs sensor plugs. All abs sensors gave a resistance reading of around 1000 ohms iirc (wrote it all down but lost the notes).
So I changed the right hand rear (rhd drivers rear) sensor, £25 island 4x4 one, no difference, nanocom still showed no voltage, lights still on. Next day, fiddling, a new fault popped up on the nano, front left sensor short, resistance reading was still OK so I ordered a cheap sensor off ebay £14 posted, just fitted that and the lights have gone out yay!
Nano shows no faults and , my query, voltage is now present on all 4 sensors?
Why would that be?
Wabco D 2001 diesel .

Member
Joined:
Posts: 123

The NanoCom is confused reading wheel sensor voltages. When reading the voltages the NanoCom to real world vehicle conversion is as follows:

NanoCom Vehicle
FL RL
FR FR
RL RR
RR FL

At least it gets FR correct. Perversely it reads the reports the error texts correctly. You can see why it showed the RR voltage incorrect when it was actually the FL at fault. That is why changing the RR sensor didn’t cure the problem

Black box have been informed and promised to correct the software when an update is released.

The Wabco ECU is very sensitive to resistance of the wheel sensors on power up check - they don’t need to be very far out of nominal to throw the ABS/TC faults yet the voltages at the wheel sensor will still look normal. Ask me how I know all this!!!

Member
Joined:
Posts: 42

Cheers Garvin. I do remember reading somewhere that nano mixed up left and right something, thought it was the blend motors though not the abs sensors. My nano is only about 8 months old so I would have expected it to be updated at blackbox before despatch but, who knows!.

Member
Joined:
Posts: 123

I’m not aware that Blackbox have released an updated software suite yet. I have the conversion on a note stuck to my NanoCom lid/cover.

Member
Joined:
Posts: 443

Out of curiosity, would Nanocom’s wheel location confusion also apply to my Disco 2, or is this specifically an issue for the P38.

Member
Joined:
Posts: 42

Garvin wrote:

I’m not aware that Blackbox have released an updated software suite yet. I have the conversion on a note stuck to my NanoCom lid/cover.

Good idea, I'll do that now.

Member
avatar
Joined:
Posts: 6744

Harv wrote:

Out of curiosity, would Nanocom’s wheel location confusion also apply to my Disco 2, or is this specifically an issue for the P38.

Don't know but an easy way to check would be to unplug one sensor and see if it reports a fault on the correct one.

Nano also doesn't know its left from its right on the blend motors on one screen but is correct on another. I can't remember where it is wrong though.

Member
Joined:
Posts: 443

Ok thanks. I’ll try to keep that in mind when I have an issue.

Member
Joined:
Posts: 1242

I doubt that it will ever be corrected in Nanocom firmware.

I found out about the sensor labels being incorrect years ago and informed BBS of it on their nanocom forums (and possibly the blend motor one) and they said they'd look at it then to update in the next firmware release.

Still hadn't been fixed when I last updated my Nanocom.

Member
Joined:
Posts: 347

Guys, on a similar note, I understand that Nanocom may also confuse ride height settings from side to side or front to back. Does anyone have any information on this or am I mistaken?

Member
Joined:
Posts: 79

Regarding the ABS and TC lights, just had that problem and couldn't find a brake related issue...... turned out to be a wheel bearing, I presume the wheel sensor was affected by that. On the Nanocom front mine didn't seem to be able to connect with any of the ecu's is that a common problem?

Member
avatar
Joined:
Posts: 6744

Blanco wrote:

On the Nanocom front mine didn't seem to be able to connect with any of the ecu's is that a common problem?

Only when the fuse has blown (fuse 33) or you have a water leak and the OBD socket (or the multiway connector behind the RH kick panel) has rotted out. Different ECUs use different pins in the socket which explains why sometimes you get one pin that isn't through so some systems will connect but not others.

Member
Joined:
Posts: 79

Thanks, I'll check out the fuse and the condition of the wiring, I do have an annoying leak, .. there is often damp on the rubber mat by the A-pillar.