ECMTuning - wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<h1>Connection Diagnostics</h1> <div class="level1"> </div> <h1>IO failed: Port currently owned</h1> <div class="level1"> <p> First, verify that you have the correct COM port selected in the <code>Edit→Options</code> 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 <em>Palm HotSync</em> 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. </p> </div> <h1>IO failed: Command timed out</h1> <div class="level1"> <p> 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 <u>lot</u> of things between those two endpoints that might be causing the issue. </p> <p> 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. </p> </div> <h2>Which COM port</h2> <div class="level2"> <p> First you have to figure out for sure which COM port to use. In general, you should be able to pull up the Windows Device Manager for this. Right click on <code>My Computer</code>, select <code>Properties</code>, go to the <code>Hardware</code> tab and click on <code>Device Manager</code>. Now, expand the <code>Ports (COM & LPT)</code> tree node and you should see something like this image: </p> <p> <a href="/wiki/lib/exe/fetch.php?tok=38c2d3&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Fkeyspanhwport.gif" class="media" title="http://www.dsmlink.com/images/forums/keyspanhwport.gif"><img src="/wiki/lib/exe/fetch.php?tok=38c2d3&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Fkeyspanhwport.gif" class="media" alt="" /></a> </p> <p> 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 (<code>Edit→Options→Config</code>) 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. </p> <p> 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 <code>Communications Port (COM1)</code> 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. </p> </div> <h2>2G notes</h2> <div class="level2"> </div> <h3>DB9 cable checkout</h3> <div class="level3"> <p> 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. </p> <p> 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. </p> </div> <h3>Diagnostic port wiring</h3> <div class="level3"> <p> If you get desperate and need to confirm that the basic wiring in the car is correct, use the following information to buzz out the connections between the OBDII adapter and the ECU. Note that the image below is of the connector in the car, not the DSMLink adapter. </p> <p> <a href="/wiki/lib/exe/fetch.php?tok=e478bf&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Fobdiiconnector.gif" class="media" title="http://www.dsmlink.com/images/forums/obdiiconnector.gif"><img src="/wiki/lib/exe/fetch.php?tok=e478bf&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Fobdiiconnector.gif" class="media" alt="" /></a> </p> <span class='np_break'> </span> <div class="table"><table class="inline"> <tr class="row0"> <td class="col0" colspan="2">Pin 1</td><td class="col2" colspan="2">Diagnostic line to ECU (connector B-55, pin 56, yellow)</td> </tr> <tr class="row1"> <td class="col0" colspan="2">Pin 5</td><td class="col2" colspan="2">Ground</td> </tr> <tr class="row2"> <td class="col0" colspan="2">Pin 7</td><td class="col2" colspan="2">Data line to ECU (connector B-55, pin 62, pink)</td> </tr> <tr class="row3"> <td class="col0" colspan="2">Pin 16</td><td class="col2" colspan="2">+12v unswitched power</td> </tr> </table> <span class='np_break'> </span> </div> <p> Pin 16 can be pulled from ECU pin 80 (connector B-56, Red-Blue) if needed. Pin 5 seems to just be a chassis ground point. You can get information on ECU connector pin locations from the <a href="/wiki/doku.php?id=ecuwiringinformation" class="wikilink1" title="ecuwiringinformation">ECUWiringInformation</a> page. If pin 16 does not show power (it should have 12v at all times when measured against pin 5), the fuse powering this pin may be blow. The same fuse power the key illumination ring, the lights in the rear view mirror, the foot light under the dash and even provides battery backup power to the ECU. It's labeled in the shop manual as dedicated fuse #11. You can locate this under the hood in the main fuse box. Looking down at the fuse box standing in front of the car, fuse #11 and #12 are grouped together in a yellow clip located in the lower left hand corner of the fuse box. </p> <p> You can also do a basic check against the diag pin (pin 1) of the OBD-II connector. Check the voltage on the car's OBD-II pin 1 without the DSMLink adapter attached. It should be something like 5V or higher. If not, something is grounding it. That can make the ECU behave oddly, prevent DSMLink communications, and may mess with your locks. </p> <p> Please use care when checking the diagnostic port pins. If you jam the typical multimeter probes into the pins, you can stretch the pins to the point that they may not make proper contact with the DSMLink connector. </p> </div> <h3>Laptop timing</h3> <div class="level3"> <p> It's rare, but sometimes the timing of laptop can make a difference on 2G connections. To test this, try adding the following to your <code>dsmlink.prefs</code> file (located in <code>C:\Program Files\DSMLink</code>) </p> <pre class="code">interByteDelayMillis=40 interCommandDelayMillis=40 cmdReplyTimeoutMillis=1000 </pre><p> </p> <p> After you add those things, bring up the DSMLink application again (it must be down when you make those additions to the <code>dsmlink.prefs</code> file) and try to connect. </p> </div> <h2>1G notes</h2> <div class="level2"> </div> <h3>USB adapter</h3> <div class="level3"> <p> The goofy 1G ECU baud rate makes this platform very sensitive to which USB/DB9 adapter you can use. Our users have reported only a few that actually work properly. You can get more details from the <a href="/wiki/doku.php?id=usbtoserialadapterinfo" class="wikilink1" title="usbtoserialadapterinfo">USBToSerialAdapterInfo</a> page. </p> </div> <h3>Red power wire</h3> <div class="level3"> <p> Some early 1G cables had a separate red power wire. Please confirm that this wire is plugged into a powered fuse box port. The cable does require that this wire be connected to a 12v power source as listed in the install instructions or else it simply will not work. </p> </div> <h3>Diagnostic port wiring</h3> <div class="level3"> <p> 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. </p> </div> <h3>Pins in the diagnostic port</h3> <div class="level3"> <p> This one's pretty rare, but it does happen. If one (or more) of the pins in the car's diagnostic connector is loose, then all your checks with the multimeter will still work fine. But when you plug in the DSMLink cable, that pin (or pins) can actually just "push in", away from the cable, and simply not making contact with the cable. Check to see if that might be happening. Try grabbing the pins in the car's diagnostic port one at a time with a pair of long nose pliers and seeing if there's any movement as you push in/pull out on them. </p> </div> <h2>General</h2> <div class="level2"> <p> It can be <u>immensely</u> helpful if you can find someone in your area that has a known working setup and start swapping parts or just trying your laptop with their setup to try to isolate where the problem most likely is. </p> </div>