holidaychicken
Well-Known Member
Once a king always a king but once a knight is enough
I also have this same problem, left headlight exploded, dash light effects on instrument panel, replaced bulb, and it worked fine for a year, except that I was unable to communicate with my Allcomms or Faultmate, but my cheap OBDII tester works. Now, after sitting for months, the battery went dead (fully charged now), and it turns over but won't start (no spark or fuel, but fuel pump runs when I bypass it), as I believe the immobilizer needs to be synced.
Did anyone figure out how to fix or troubleshoot this issue? I'm disconnecting ECUs but nothing working yet.
Thanks!
Did anyone figure out how to fix or troubleshoot this issue? I'm disconnecting ECUs but nothing working yet.
Thanks!
holidaychicken
Well-Known Member
Have you read Saint's posts on the previous page to this one regarding headlamp levelling ECU?
Yes, I did. Disconnected these as well, but still no communication. Will keep disconnecting ECUs this weekend, but was hoping to find a better way to find which was bringing down the system.
Thanks!
Thanks!
Aahhh Saint.V8 I so envy you that you can use that diagnostics again. I tried disconnecting everything that I thought may be faulty and is reachable, tried it with lights off, lights disconnected, but still no communication.
I read again this thread, but there's one thing that I am not sure about. Do you now have old or new IP and LCM installed?
That PDF you attached uses some BMW diag tool that seem to help with bus problem diagnostics. Is there any chance that this would work with L322?
I read again this thread, but there's one thing that I am not sure about. Do you now have old or new IP and LCM installed?
That PDF you attached uses some BMW diag tool that seem to help with bus problem diagnostics. Is there any chance that this would work with L322?
I tried it with the replacement IP and LCM and it was still the same, so I put the originals back and it still wouldn't connect....
Then it all of sudden a good while later it just all of a sudden just worked....and I have absolutely no clue why it cleared itself and I have no idea what caused it....
The BMW Diagnostics tool is called DIS/GT1 and I am not sure if it would work with the L322 or not, I have both the BMW INPA and also DIS, I can get INPA to connect to my 7'er and DIS will work to a fashion, but I can't get INPA to connect to the L322 as I don't have the required profile files I think for the Range Rover, I have heard of others who have got INPA to connect....but I am continuously looking to see how to get it to talk to the L322....as for DIS, this I have big doubts on if it will connect to the L322 at all.....and it is DIS that has the databus diagnostics function.
Thank you so much for your info. So, I won't buy new IP and LCM at the moment.
I wonder if it would be possible to remove as much from equation as possible by just disconnecting wire from IP to CAN bus (C0234-8) or K/I bus (C0233-7, C0233-8) and replacing it with terminal resistor. I would hope that this would remove all possible ECUs from that bus and AllComms should still be able to communicate with IP. Or am I wrong? When I would get communication with IP then I would know what bus have problem. Also, I wonder where could I find junction point X18836 - multiple wires from different ECUs seem to be connected there and I thought maybe this would be good place to divide bus and verify it per partes.
I got some quick chance to connect my car to LR dealer's diagnostics. I believe it is was T4 but I am not really sure. There were multiple suggestions to fix communication issue. Maybe it will help someone sometime (italics are my comments):
I wonder if it would be possible to remove as much from equation as possible by just disconnecting wire from IP to CAN bus (C0234-8) or K/I bus (C0233-7, C0233-8) and replacing it with terminal resistor. I would hope that this would remove all possible ECUs from that bus and AllComms should still be able to communicate with IP. Or am I wrong? When I would get communication with IP then I would know what bus have problem. Also, I wonder where could I find junction point X18836 - multiple wires from different ECUs seem to be connected there and I thought maybe this would be good place to divide bus and verify it per partes.
I got some quick chance to connect my car to LR dealer's diagnostics. I believe it is was T4 but I am not really sure. There were multiple suggestions to fix communication issue. Maybe it will help someone sometime (italics are my comments):
- Passenger fusebox fuse 15
- No supply at C0586/26 (hm, I'm not native speaker, does this mean no +12V? )
- Open circuit C0040/5 or C0040/6 - Ground (NB) (C0040 seem to be OBDII diagnostic port 5 and 6 must be grounded, somewhere else I read that 4 and 5 is ground...)
- Open circuit C0586/26 (RUY) - C0040/16 (RUY) (pin 16 should be +12V, so this connection should bring +12V there from C0586/26, so if I see +12V on C0040/16 also #2 should be ok?)
- Open circuit in diagnostic lead from C0040/7 (WPY)
- Open circuit in daignostic lead from C0040/8 (WP)
- Short circuit C0040/7 (WPY) - Ground or battery (data line for engine and gearbox, this works fine in my case)
- Short circuit C0040/8 (WP) - Ground or battery (data line that seem to have problem)
- Connectors C0040, C0586
- Fault in Diagnostic tester or diagnostic cables (not our case, I think)
I wonder if the voltage spike melted the insulation off a wire and grounded the loom somewhere. That has now jigged loose but if it touches the bodywork again it'll stop working again?
What a slur, sir! How are the leaky half-shaft seals?
holidaychicken
Well-Known Member
td4helllllllllppppppppp
New Member
Did anyone ever figure this one out I have a just replaced a suspension bag and now my suspension is needing adjusting with diagnostics, all I can get into is the engine and gearbox through kline with a cheap scanner, all my other tools completely thrown out by the Can Bus, I started by disconnecting the headlamp adjuster ecu, bought replacement dash and lcm, now individually unplugged every ecu on the car from top to bottom door cards off sunroof whole dash stripped out can find no faulty wiring anywhere, 2 auto electricians been out to the car, Land rover specialist been out with Autologic, must have spent 3 days messing with this, steering wheel left to right no longer resets the suspension because of hard fault, and i know the system is working because when you unplug anything it tells you on the dash, what a silly system which works but does not want to tell you the issue by the means it was designed to do, this was the whole point.
Now just been out and set my supension by plugging it into a td6 setting my suspension up on the wrong car clearing faults and putting the suspension ecu back onto my car this is obviously easy way to get running but less than ideal.
Anyone know a good tech around Yorkshire?
Now just been out and set my supension by plugging it into a td6 setting my suspension up on the wrong car clearing faults and putting the suspension ecu back onto my car this is obviously easy way to get running but less than ideal.
Anyone know a good tech around Yorkshire?
Air Suspension (and other ECUS) are only able to be communicated with Land Rover specific Diagnostics....Snap On, Faultmate, All Comms, Hawkeye, Lynx, iCarsoft, Testbook et al.....
A generic code reader will only read engine and gearbox.
Replacing a strut should not necessarily need re-calibration.....
Surprised Autologic won't connect!!!!
A generic code reader will only read engine and gearbox.
Replacing a strut should not necessarily need re-calibration.....
Surprised Autologic won't connect!!!!
td4helllllllllppppppppp
New Member
yes understand the generic code readers only get into that but my point was they are working on the kline, its the canbus that seems to have gone down, one of the auto electricians had the new snap on, I have x431, delphi, ids, also bmw commander which get's into all these early rr's but not every system, there not connecting because of the canbus failure, but looks like no one ever seems to get to the bottom of it absolute nightmare of a job hours spent it's going into the dealers if I do find out I will let people know for future reference.
Thanks
Thanks
Hi, Having exactly the same issues.
Left HID has exploded, and now no communication with any ECUs using Auto Logic. My OBD readers both read Engine, AT ECUs...
Has anyone found a resolution to this yet?
Initial thoughts after reading this thread, are has anyone tried unplugging all ECUs and plugging in one at a time? Since I guess it is totally feasible that more than one has been fried? Also, has anyone tried swapping ECUs to other L322s? Are there any ECUs that shouldn't just be swapped to try other than the IP and Light Module?
Thanks
Mike
(Oh, my OBD was used two days before HID failed and all ECUs were working fine except an error in EAS ECU wouldn't clear - something along the lines of ECU Fault - but the other codes stored on that one cleared, and communications were possible).
Left HID has exploded, and now no communication with any ECUs using Auto Logic. My OBD readers both read Engine, AT ECUs...
Has anyone found a resolution to this yet?
Initial thoughts after reading this thread, are has anyone tried unplugging all ECUs and plugging in one at a time? Since I guess it is totally feasible that more than one has been fried? Also, has anyone tried swapping ECUs to other L322s? Are there any ECUs that shouldn't just be swapped to try other than the IP and Light Module?
Thanks
Mike
(Oh, my OBD was used two days before HID failed and all ECUs were working fine except an error in EAS ECU wouldn't clear - something along the lines of ECU Fault - but the other codes stored on that one cleared, and communications were possible).
