Has anyone fixed this recently?

 

Wont unlock on the fob, have to manually open doors with key, locking works every time.  Have 2 fobs (one brand new) and both have the same behaviour

 

One thing Ive noticed is the boot lock does not open (have to use the key), Ive also checked the drivers door loom connector and its as-new, dry as a bone.  No corrosion at all....

 

If I press the unlock once the cars been unlocked (and the puddle light is on), pressing the unlock does flash the puddle light off and on briefly, so I know the fob is doing something

 

Any ideas folks? 

Have you disconnected the drivers loom at both ends and used a multimeter to check the continuity of the loom while you move it about like it would when the door opens and closes?.

Hello, no only a visual inspection on the door side.  Was wondering whether the boot lock not opening may be a clue?  Wasnt sure whether that would affect the fob unlock though.

 

Where does the door loom end up inside the cabin?  Thanks for the reply

Cable ends up in a connector hidden behind the trim that holds the bonnet release.

 

Boot lock may just be the same type of fault but in the wiring trunking at the tailgate.

 

Have you tried putting votage to the lock and unlock pins on the tailgate solenoid to see if it is actually working?

 

I must admit I would be checking the drivers loom first as that is the central point of lock and unlock instructions for the system.

 

The wiring is getting on in these cars now, so there is no guarantee that just because the loom looks intact, that it hasn't had a break in the inner cable inside the insulation. A quick check with a multimeter is the best way forward really,

 

Hope it helps.

Thanks, it stopped working (intermittently) a few years ago, now its been defunkt for a while and so the quest begins to fix it

 

Just glad the loom connector in the door is trouble free as a starting point.

I could be wrong,but i think i remember having an issue similar to yours (no, not you the 1st time round ) 

And it was an interference from the boot. Try disconnecting that and see what it doesnt do?