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 [2008/12/23 06:38] twdorris |
connectionproblem [2009/02/26 13:38] twdorris |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Connection Diagnostics ====== | ====== Connection Diagnostics ====== | ||
| - | ====== IO failed: Port currently owned ====== | + | |
| + | ====== Port currently owned ====== | ||
| First, verify that you have the correct COM port selected in the ''Edit->Options'' menu as described below in the "Which COM port" section. The "port currently owned" message means that some other application has that COM port opened. Often this is a //Palm HotSync// manager or something like that running in the background. Most of those applications have a way to disconnect themselves from or disable their use of the COM port. | First, verify that you have the correct COM port selected in the ''Edit->Options'' menu as described below in the "Which COM port" section. The "port currently owned" message means that some other application has that COM port opened. Often this is a //Palm HotSync// manager or something like that running in the background. Most of those applications have a way to disconnect themselves from or disable their use of the COM port. | ||
| - | ====== IO failed: Command timed out ====== | ||
| - | Basically, if you're getting the timeout message, then it means the application has located a valid COM port, sent a command to the ECU, but did not get a reply back. Something between the application and the ECU is not working properly. Unfortunately, there are a __lot__ of things between those two endpoints that might be causing the issue. | + | ====== Scan failed to find a working connection ====== |
| + | |||
| + | Basically, if you're getting this message, then it means the application has located a valid COM port, sent a command to the ECU, but did not get a reply back. Something between the application and the ECU is not working properly. Unfortunately, there are a __lot__ of things between those two endpoints that might be causing the issue. | ||
| 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. | ||
| Line 19: | Line 21: | ||
| 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 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. | ||
| - | 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. |
| ===== 2G notes ===== | ===== 2G notes ===== | ||
| - | |||
| - | ==== DB9 cable checkout ==== | ||
| - | One of the easiest things you can do yourself is to verify that the DB9 cable is good. We have had a few people send their entire kits back in here for a check out only to realize that it was just the DB9 cable that was bad and they could have picked one up themselves and saved a lot of time and shipping expense. | ||
| - | |||
| - | The cable is a straight through cable. That means each male pin should buzz out to the corresponding female pin. If any do not, then that's probably why there's no communication with the ECU. Replace this cable with another straight through DB9 cable you can find at any reasonable computer store (Radio Shack, Best Buy, etc.) and you'll probably be back in business. | ||
| - | |||
| ==== Diagnostic port wiring ==== | ==== Diagnostic port wiring ==== | ||
| Line 45: | Line 41: | ||
| Please use care when checking the diagnostic port pins. If you jam the typical multimeter probes into the pins, you can stretch the pins enough that they may not make proper contact with the DSMLink connector. | Please use care when checking the diagnostic port pins. If you jam the typical multimeter probes into the pins, you can stretch the pins enough that they may not make proper contact with the DSMLink connector. | ||
| + | ==== DB9 cable checkout (V2 ONLY) ==== | ||
| + | One of the easiest things you can do yourself is to verify that the DB9 cable is good. We have had a few people send their entire kits back in here for a check out only to realize that it was just the DB9 cable that was bad and they could have picked one up themselves and saved a lot of time and shipping expense. | ||
| + | The cable is a straight through cable. That means each male pin should buzz out to the corresponding female pin. If any do not, then that's probably why there's no communication with the ECU. Replace this cable with another straight through DB9 cable you can find at any reasonable computer store (Radio Shack, Best Buy, etc.) and you'll probably be back in business. | ||
| ==== Laptop timing (V2 ONLY) ==== | ==== Laptop timing (V2 ONLY) ==== | ||
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
