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:39] 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. | ||
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
