connectionproblem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
connectionproblem [2012/12/14 10:31] twdorris |
connectionproblem [2024/03/15 11:16] (current) |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| 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 ''My Computer'', select ''Properties'', go to the ''Hardware'' tab and click on ''Device Manager''. Now, expand the ''Ports (COM & LPT)'' tree node and you should see something like this image: | 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 ''My Computer'', select ''Properties'', go to the ''Hardware'' tab and click on ''Device Manager''. Now, expand the ''Ports (COM & LPT)'' tree node and you should see something like this image: | ||
| - | {{http://www.dsmlink.com/images/forums/keyspanhwport.gif}} | + | {{https://www.ecmtuning.com/images/forums/keyspanhwport.gif}} |
| 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. | 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. | ||
| Line 29: | Line 29: | ||
| ==== Diagnostic port wiring ==== | ==== Diagnostic port wiring ==== | ||
| - | 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. | ||
| - | {{http://www.dsmlink.com/images/forums/obdiiconnector.gif}} | ||
| - | ||Pin 1||Diagnostic line to ECU (connector B-55, pin 56, yellow)|| | + | 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 ECMLink adapter. |
| - | ||Pin 5||Ground|| | + | |
| - | ||Pin 7||Data line to ECU (connector B-55, pin 62, pink)|| | + | |
| - | ||Pin 16||+12v unswitched power|| | + | {{https://www.ecmtuning.com/images/forums/obdiiconnector.gif?nolink&207x72}} |
| + | |||
| + | |||
| + | |Pin 1 ||Diagnostic line to ECU (connector B-55, pin 56, yellow) || | ||
| + | |Pin 5 ||Ground || | ||
| + | |Pin 7 ||Data line to ECU (connector B-55, pin 62, pink) || | ||
| + | |Pin 16 ||+12v unswitched power || | ||
| Pin 16 can be connected to ECU pin 80 (connector B-56, Red-Blue) if needed. | Pin 16 can be connected to ECU pin 80 (connector B-56, Red-Blue) if needed. | ||
| + | |||
| Pin 5 can use a chassis ground point. | Pin 5 can use a chassis ground point. | ||
| - | You can get information on ECU connector pin locations from the [[ECUWiringInformation]] 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 blown. The same fuse powers the key illumination ring, the lights in the rear view mirror, the foot light under the dash, and also provides battery backup power to the ECU. It's labeled in the shop manual as dedicated fuse #11. It is located under the hood in the main fuse box. Looking down at the fuse box standing in front of the car, fuses #11 and #12 are grouped together in a yellow clip located in the lower left hand corner of the fuse box. The lid of the fuse box labels fuse #11 as Room Lamp. | + | You can get information on ECU connector pin locations from the [[:ecuwiringinformation|ECUWiringInformation]] page. |
| - | You can also do a basic check against the diag pin (pin 1) of the OBD-II connector. Check the voltage on the cars' OBD-II pin 1 without the DSMLink adapter attached. It should be ~5V or higher. If not, something is grounding it. This can make the ECU behave oddly, prevent DSMLink communication, and may cause problems with your locks. | ||
| - | 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. | + | 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 blown. The same fuse powers the key illumination ring, the lights in the rear view mirror, the foot light under the dash, and also provides battery backup power to the ECU. It's labeled in the shop manual as dedicated fuse #11. It is located under the hood in the main fuse box. Looking down at the fuse box standing in front of the car, fuses #11 and #12 are grouped together in a yellow clip located in the lower left hand corner of the fuse box. The lid of the fuse box labels fuse #11 as Room Lamp. |
| - | ==== 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. | + | You can also do a basic check against the diag pin (pin 1) of the OBD-II connector. Check the voltage on the cars' OBD-II pin 1 without the ECMLink adapter attached. It should be ~5V or higher. If not, something is grounding it. This can make the ECU behave oddly, prevent ECMLink communication, and may cause problems with your locks. |
| - | ==== Laptop timing (V2 ONLY) ==== | ||
| - | 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 ''dsmlink.prefs'' file (located in ''C:\Program Files\DSMLink'') with the dsmlink application closed. | ||
| - | interByteDelayMillis=40 | + | 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 ECMLink connector. |
| - | interCommandDelayMillis=40 | + | |
| - | cmdReplyTimeoutMillis=1000 | + | |
| - | After you add those items, open the DSMLink application again (remember: it must be closed/not running when you make those additions to the ''dsmlink.prefs'' file) and try to connect. | + | |
| + | \\ | ||
| + | |||
| + | ==== 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. | ||
| ===== 1G notes ===== | ===== 1G notes ===== | ||
| Line 90: | Line 94: | ||
| ===== General ===== | ===== General ===== | ||
| It can be __immensely__ 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. | It can be __immensely__ 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. | ||
| + | |||
connectionproblem.1355499070.txt.gz · Last modified: 2012/12/14 10:31 by twdorris
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
