Hi All,

I have replaced my PAM with a 2nd hand unit from a 2010 L322 as the original one was full of water.. unfortunately the new unit gives the following error on IID -

U3002-81 - Vehicle identification number - Bus signal/message failure - invalid serial data received (2E)

When activated (by putting reverse) it gives a continuous beep for around 5 seconds and the LED on the switch flashes 6 times - it obviously doesn't work

In IID I can see the module and live values for the sensors, switch, etc and all seems fine however under 'ECU info' the PAM module displays a different VIN to the cars VIN.

I was under the impression that replacing the PAM module was a simple swap that didn't require any coding but this error suggest otherwise?

Anyone any idea what could be going on here?

Many thanks for your help

Matt

2012 TDV8 4.4 Autobiography

I went through this issue. You can't fit an already coded module (and I couldn't find a way of making the ECU 'virgin' again with IID)

I ended up buying an uncoded one, worked straight away and took on the vehicle's VIN number.

Thanks for the reply, that is the unfortunate conclusion I am coming to.. strange as I've read lots of posts on various sites from ppl happily replacing the PAM with 2nd user units with no issue..

Did you get a blank one direct from Landrover? any idea how much it was?

Thanks again!

Matt

A lucky Ebay find..

Thanks again - looks like I'm part hunting again..

Amusingly, it didn't fix the problem straight away. Well, in combination with replacing corroded connector pins, it did.

I had no idea they were locked to the car VIN. If you have had water damage once you will get it again......
https://www.fullfatrr.com/forum/topic64459.html?highlight=pam 2012 TDV8 Vogue (L322)

Nor did I..

the water damage is most interesting - no sign of water anywhere else in the area, all other units have a lovely coating of dry dust.. I;ll get the parking module sorted then do some further investigation..

Don't discount capillary action up the harness, especially if there's no other sign of ingress and you had a corroded connector - possibly on the pin(s) that supply power or ground via a splice in the harness.

This is very odd - I bought a salvaged module from eBay and plugged it straight in no problems at all.

I can't believe it had been "reset" by the breakers yard before they sold it on eBay? Bish.

2005 110 TD5 CSW
2011 TDV8 Vogue SE (gone)

It is certainly very odd - I asked IID and they can't reset it so I'm very doubtful breakers are...

It'll work fine (providing that it was the cause of the issue) but may set a DTC for incorrect VIN. The reason being is that, if it has already been replaced by a dealer during it's warranty period and wasn't tied to the vehicle as they're essentially plug & go, then that would give you a PAM that is VIN-free, the PAM functionality isn't at all restricted by not having any or the incorrect VIN but it will make those who like to spend their time searching for errant DTC's twitch...

The point of the post is it doesn't work fine though - if it was just throwing an error code I wouldn't care (plenty of those from other systems without issue).

Well it's probably not the PAM then.

ETA - it does sound like the PAM is working fine, it's detecting an external issue and telling you about it (with the continuous tone and flashing LED), IMO you need to be checking for water ingress to harness connectors, chafing rear PDC harness or corroded splices.

what makes you say that when when I can successfully query all live values (sensors, switches etc) and the only error being reported is the VIN mismatch one? Another user has also confirmed they had the exact same issue and had to purchase a 'virgin' unit.

If it couldn't talk on the CAN bus then IID wouldn't be able to talk to it and retrieve all the values and if it had an internal issue I would expect more errors. For instance if I disconnect the sensors from the module, but leave the power / data plug connected then IID reports errors with all sensors - plug them back in and the only remaining error is the VIN mismatch.

To be clear I'm not discounting an issue with the module, but I can see no evidence to support that.