Data Link Connection Error
Thread Starter
|
Member
Joined: Jan 2012
Posts: 37
Likes: 3
From: Fresno
Data Link Connection Error
Driving home last night and the old girl's engine started to stumble on the slightest attempt to accelerate. Felt as though a coil had stopped working and misfiring on less then 8 cylinders so I wasn't too worried. (been there done that)
When I got home to investigate, I hooked up the OBDII Scanner and it lights up, goes through its diagnostics as it always does, but then gives a
'cannot connect, data link error' at the end.
As it is going through its series of tests, the dash message info center starts flashing all the warnings, electrical fault, asc/trac inop, transmission failure, limp home mode, etc. After I get the unable to connect, the info center goes to open drivers door only. Check engine light will light when key is turned and goes off when it idles, but doesn't stay on?
I have tried hard reset, battery disconnected and grounded all night. I pulled the ECU and nothing obviously burnt inside, but I'm no expert.
The OBDII is working. It was in the jag a few weeks ago working fine, just tested it on a Land Rover, Ford, and Chrysler and communicates fine with all of them.
I pulled obdii port to find any broken wires as stated in earlier posts and found nothing obvious.
ANY way to get codes without scanner, or any quick fixes or are we looking at an ECU/ECM problem?
When I got home to investigate, I hooked up the OBDII Scanner and it lights up, goes through its diagnostics as it always does, but then gives a
'cannot connect, data link error' at the end.
As it is going through its series of tests, the dash message info center starts flashing all the warnings, electrical fault, asc/trac inop, transmission failure, limp home mode, etc. After I get the unable to connect, the info center goes to open drivers door only. Check engine light will light when key is turned and goes off when it idles, but doesn't stay on?
I have tried hard reset, battery disconnected and grounded all night. I pulled the ECU and nothing obviously burnt inside, but I'm no expert.
The OBDII is working. It was in the jag a few weeks ago working fine, just tested it on a Land Rover, Ford, and Chrysler and communicates fine with all of them.
I pulled obdii port to find any broken wires as stated in earlier posts and found nothing obvious.
ANY way to get codes without scanner, or any quick fixes or are we looking at an ECU/ECM problem?
Joined: Dec 2009
Posts: 13,581
Likes: 9,526
From: Wise County,TX
I would try another OBDII reader. If that one will not communicate either, I would suspect a faulty ECM, INSTPK or network harness.
The Instrument Pack is the gateway to all the other modules on the CAN bus and SCP network and if it fails, the network will probably fail to communicate properly.
I don't know if you are using the Serial Data Link or the CAN bus for communication.
Different diagnostic 'scanners' use different protocols.
I had a customer XKR that would communicate with the WDS through the CAN bus but a generic scanner would NOT communicate with the ECM through the Serial Data Link.
More diagnosis??????
good luck
bob gauff
The Instrument Pack is the gateway to all the other modules on the CAN bus and SCP network and if it fails, the network will probably fail to communicate properly.
I don't know if you are using the Serial Data Link or the CAN bus for communication.
Different diagnostic 'scanners' use different protocols.
I had a customer XKR that would communicate with the WDS through the CAN bus but a generic scanner would NOT communicate with the ECM through the Serial Data Link.
More diagnosis??????
good luck
bob gauff
Thread
Thread Starter
Forum
Replies
Last Post
trosty
XJ XJ6 / XJ8 / XJR ( X350 & X358 )
26
Dec 18, 2022 06:40 PM
scooternva
XJ XJ6 / XJ8 / XJR ( X350 & X358 )
19
Oct 27, 2015 02:14 PM
Foosh
F-Type ( X152 )
3
Sep 11, 2015 03:35 PM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)