connectionproblem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
connectionproblem [2009/02/26 13:38] twdorris |
connectionproblem [2009/11/16 08:52] twdorris |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| If you search for "command timeout" on the forums you will see a huge number of possible causes. We've seen everything including OS configuration issues, bad serial ports on the laptop, wiring issues in the car, blown fuses in the fuse/relay box under the hood, problems with the ECU itself, a damaged adapter, etc., etc. It can sometimes be very difficult to track down the source. But there are a few basic things you can try to get started. | If you search for "command timeout" on the forums you will see a huge number of possible causes. We've seen everything including OS configuration issues, bad serial ports on the laptop, wiring issues in the car, blown fuses in the fuse/relay box under the hood, problems with the ECU itself, a damaged adapter, etc., etc. It can sometimes be very difficult to track down the source. But there are a few basic things you can try to get started. | ||
| + | |||
| ===== Which COM port ===== | ===== Which COM port ===== | ||
| Line 19: | Line 20: | ||
| {{http://www.dsmlink.com/images/forums/keyspanhwport.gif}} | {{http://www.dsmlink.com/images/forums/keyspanhwport.gif}} | ||
| - | That should tell you for sure which COM port you should be using in DSMLink. Once you know that, you enter that COM port into DSMLink (''Edit->Options->Config'') and try again. If that's still not working, then at least you know you have the correct COM port selected and there's no need to go swapping around with that. If you don't even see your USB/DB9 adapter listed in device manager as illustrated above, then you'll need to start debugging why your adapter driver isn't properly installing itself. | + | That should tell you for sure which COM port you should be using in ECMLink. Once you know that, you enter that COM port into ECMLink (in the V2 app, that's under ''Edit->Options->Config'') and try again. If that's still not working, then at least you know you have the correct COM port selected and there's no need to go swapping around with that. If you don't even see your USB/DB9 adapter listed in device manager as illustrated above, then you'll need to start debugging why your adapter driver isn't properly installing itself. |
| **V2 ONLY:** If your laptop has a built-in DB9 serial port (i.e., you're not using a USB/DB9 adapter), then the COM port you'll want to use will be something like the plain ''Communications Port (COM1)'' port listed in the diagram above. In that case, you'll also what to check to make sure the select COM port isn't actually a built-in modem or IRDA port or something like that. | **V2 ONLY:** If your laptop has a built-in DB9 serial port (i.e., you're not using a USB/DB9 adapter), then the COM port you'll want to use will be something like the plain ''Communications Port (COM1)'' port listed in the diagram above. In that case, you'll also what to check to make sure the select COM port isn't actually a built-in modem or IRDA port or something like that. | ||
| Line 56: | Line 57: | ||
| ===== 1G notes ===== | ===== 1G notes ===== | ||
| + | |||
| + | |||
| ==== Diagnostic port wiring ==== | ==== Diagnostic port wiring ==== | ||
| - | When all else fails, check the basics. Here's some information posted to our forums related to basic checks you can perform on the 1G diagnostic connector in the car. First, make sure the car's ignition is turned on when you're trying to connect DSMLink. Examine the cable for any broken wires at the car end. With the ignition on, measure the voltage on pin 10 of the car's diagnostic connector (connects to the DSMLink cable's pin that has a white wire) with no cable attached. It should be about 4.5V (3.5V for a 1990 ECU). Measure the voltage on pin 1 of the car's diagnostic connector (connects to the DSMLink cable's pin with the green wire). It should be pulsing, indicating diagnostic info. Check that pin 12 of the car's diagnostic connector (connects to the DSMLink cable's pin with the black wire) has continuity to ground. | + | When all else fails, check the basics. Here's some information posted to our forums related to basic checks you can perform on the 1G diagnostic connector in the car. |
| + | |||
| + | First, make sure the car's ignition is turned on when you're trying to connect ECMLink. | ||
| + | |||
| + | Examine the cable for any broken wires at the car end. With the ignition on, measure the voltage on pin 10 of the car's diagnostic connector (connects to the V2 cable's pin that has a white wire) with no cable attached. It should be about 4.5V (3.5V for a 1990 ECU). Measure the voltage on pin 1 of the car's diagnostic connector (connects to the V2 cable's pin with the green wire). It should be pulsing, indicating diagnostic info. Check that pin 12 of the car's diagnostic connector (connects to the V2 cable's pin with the black wire) has continuity to ground. | ||
| + | |||
| + | For more wiring information related to the 12-pin diagnostic connector found in the 1G DSM and EVO1-3 cars, check the [[diagport-12pin|12-pin Diagnostic Port]] page. | ||
| ==== Pins in the diagnostic port ==== | ==== Pins in the diagnostic port ==== | ||
connectionproblem.txt · Last modified: 2024/03/15 11:16 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
