Welcome, Guest. Please login or register.
Did you miss your activation email?
April 23, 2014, 12:30:37 PM
Home Help Search Login Register
News: OBDLink MX officially launched.

ScanTool.net Forum  |  Hardware  |  OBDLink SX  |  Topic: Cannot Connect « previous next »
Pages: [1] Go Down Print
Author Topic: Cannot Connect  (Read 905 times)
Rhapsody5
Newbie
*
Posts: 4


View Profile
« on: December 14, 2011, 05:02:51 PM »

Scan Tool:   OBDLink SX Scan Tool
Connection:   USB
Operating System:   Microsoft Windows XP Professional 32 Bit
      Version: 5.1.2600 Service Pack 3 Build 2600
Vehicle:      1999 Jeep Grand Cherokee (6 cylinder) USA
Engine:      6 cylinder gas, 242 cu. in. (4.0 liters)
Software:   OBDwiz  Version:  2.12.1.292
ScanTool Fault:   Connection of scan tool to vehicle PCM was not successful.  Message says only that there was an error experienced in the attempt to connect.  In response to error correction prompts, we can confirm that:
1.       The scan tool was connected properly.
2.       The vehicle ignition was set to ON.  (The engine will not run.  The starter engages and turns the engine over but there appears to be no fuel and we assume no ignition?)
3.       Connection Settings are correct between tool and laptop and we have successfully connected with a 2004 Chrysler Pacifica previously.

Vehicle Problem:   1999 Jeep Grand Cherokee will not start after normal shutdown.  The instrument cluster is not responsive (i.e.: when in run position the fuel gauge registers nothing - fuel warning light is on [there is gas in tank].   Check instruments light is on.   After the attempt at connecting the scan tool, the check engine light comes on).  Suspect that the PCM has crashed since it will not connect with the scan tool?   

Any suggestions as to how to affect connection with the PCM?  Will direct short in Crank Position Sensor or other input cause complete shutdown of PCM? 

Thanks, Rhapsody5
Logged
Vitaliy
ScanTool.net Staff
Veteran
*
Posts: 2243

Forum Cop


View Profile WWW
« Reply #1 on: December 15, 2011, 02:09:30 AM »

Please post your Raw Data log (Diagnostics->Raw Data).

From your description, it does sound like the ECU may be damaged.
Logged

Need to decode a diagnostic trouble code? Try DTCSearch.com
Rhapsody5
Newbie
*
Posts: 4


View Profile
« Reply #2 on: December 15, 2011, 01:27:49 PM »

Sorry, can not post "The communication logs (Raw Data tab of the Diag page);
nothing saved.  I was unaware that anything at all was being produced that could be recorded if there was no connection whatsoever.  Please advise what, if any, "raw data" will be generated during the CONNECTION process that would be helpful in diagnosing the connection problem. 

Rhap5
Logged
Vitaliy
ScanTool.net Staff
Veteran
*
Posts: 2243

Forum Cop


View Profile WWW
« Reply #3 on: December 15, 2011, 07:27:23 PM »

Sorry, can not post "The communication logs (Raw Data tab of the Diag page);
nothing saved.  I was unaware that anything at all was being produced that could be recorded if there was no connection whatsoever.  Please advise what, if any, "raw data" will be generated during the CONNECTION process that would be helpful in diagnosing the connection problem. 

Rhap5

It would show commands that the computer sends to OBDLink, even if OBDLink is unable to communicate with the ECU.

Vitaliy
Logged

Need to decode a diagnostic trouble code? Try DTCSearch.com
Rhapsody5
Newbie
*
Posts: 4


View Profile
« Reply #4 on: December 19, 2011, 12:43:09 PM »

Attached is the "Raw Data" log. 

Curious to know if anything revealed by the failure indications. 

Thanks, Rap5

* RawDataLog_20111217 161821.txt (1.25 KB - downloaded 61 times.)
Logged
Vitaliy
ScanTool.net Staff
Veteran
*
Posts: 2243

Forum Cop


View Profile WWW
« Reply #5 on: December 19, 2011, 09:18:23 PM »

The voltage reading is 13.4V, which usually indicates that the engine is running. Do you have the battery hooked up to an external charger?

Before replacing the PCM, I would check the connectors & wiring.

Vitaliy
Logged

Need to decode a diagnostic trouble code? Try DTCSearch.com
Rhapsody5
Newbie
*
Posts: 4


View Profile
« Reply #6 on: December 20, 2011, 11:49:17 AM »

Yes, the 13.4 volts was due to jumping the Jeep's battery with another vehicle. 

We will follow up on re-checking all connections and wiring.  We have inspected all relays, fuses and re-seated various grounding wires (to assure good contact) but we have not disconnected and re-installed the connectors between the OBD port and the PCM.  I suspect that some connector has oxidized and is no longer conducting (?). 

Thanks for your comments; we will advise the outcome. 

Rap5   

Logged
Pages: [1] Go Up Print 
ScanTool.net Forum  |  Hardware  |  OBDLink SX  |  Topic: Cannot Connect « previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.8 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!