Interior lights work, door latches don't

[Cowinthefog]

2006 L322, 4.2 supercharged. I am having an issue with the door switches. I get the close doors to change height message. I cannot tell where the door ajar switches are in the wire diagram, if I have the correct one. I also can't seem to find how to locate the connectors identified, but that is kind of a separate question. I have taken apart the front doors and everything looks pretty clean, no signs of corrosion, though I did not remove the door latches. I sprayed an electrical cleaner in each latch, including the tail gate upper and lower latches, just to see if that might help. No change. Each door and the tail gate cause the lights to come on and then go off, each within about 15-20 seconds of closing. I cannot tell how to pin down the bad switch or switches. I also could not see a way to check the door latches via SDD-is there a way to check or actuate them remotely? I also have no lights on the dash for any aperture open or closed.

I think I need
1. A proper wiring diagram (what I have is attached)
2. A good suggestion on how to efficiently troubleshoot the system. I'd love to not have to take the car apart, but if that's what it takes...

Josh

 

[Cowinthefog]

I performed a network integrity test and the Body Processor Unit, IPC (instrument cluster?) are not communicating. It does not show anything else labeled for controlling body electronics, is it the same as a BCU, or BECU or BECM? But this is under the passenger seat(see photo). Is there a good way to test this, or is not communicating enough, I have looked at all the wiring I can get to and have found no visible issues, but still need to find the correct pins/points for continuity checks. If the Body Control Unit is dead (regardless of the acronym) does it need reprogramming to match the VIN? Is that something I can do with SDD?

 

[Rover Range]

The door ajar switches are built into each latch. A scan tool that can monitor data pids will indicate which switch is defective.

Modules that are replaced, will need to be programmed. That way they can " talk" to each other.

 

[Cowinthefog]

Thanks for the pointer! I'm still quite new to SDD. Is programming simply running the configure new module function?

 

[Rover Range]

Yes.
But, with the JLR cyber attack. We lost the SDD module programing feature.
Can't even program key fobs.

 

[Cowinthefog]

I guess I'll hope it only needs minor repair then! Any hope for the functionality to return?

 

[Cowinthefog]

I did some SDD checking today, and through the live data capture, having selected all the doors, hood and tailgate, I see that the module is not replying, which sounds consistent with the network integrity test that produced the same result. All the wiring I can get at, including most of the dash, sill plate areas, spare tire and side trunk areas looks sound and chafe-free. Any other checks I can do? Body processor module toast? It is dry.

 

[Cowinthefog]

The solution was my rain sensor connector. It's a strange, folding type of connector that bends in the middle. I don't know if that's the design, or if a little tab or clip is broken, but the result is the wires can back out, which they did. One of those wires is the K-bus wire! I don't know why LR would put such an auxiliary system tied to one that can take down the car, but they did. It's in the same loop as the Generic Electronics Module, which has the same connector numbers and place in the car as the Body Processor Module (hmmmmmmmmmmm.....) and sees whether or not the doors are closed. Soooooo, long story short, wire backs out of rain sensor connector, GEM can't see doors are closed, air suspension module won't turn on and the safety inihibit kicks in to drop the suspension if the vehicle goes over around 28 mph, as well as three other modules in the loop it took down. All from ONE WIRE. C'mon LR! Reseated wires, reset the systems and the world turns again.