| Author | Message | ||
     Chopperboy |
I have been trying unsuccessfully for the past several days to get the VDSTS software to connect with my Ulys ECM. I have verified the keyspan port setting, vehicle interface cable specification, ECM selection and all communicate fine. When I try to connect I get I nothing. Could I have a bad cable? Other suggestions? Thanks in advance. | ||
| Stevem123 |
Be sure to select the ecm type "Buell. BC Steve | ||
| Stevem123 |
Oops, I just noticed you said ECM selection. My bad..... Hope you get it figured out! BC Steve | ||
| Al_lighton |
Very good chance it is a bad, or rather, less than optimal, cable. Are you connecting to an XB12 race ECM of recent vintage? Here's the deal: I recently conected every VDSTS cable in stock, about 15 of them, to my older race ECM. One in 15 kept connecting and disconnecting, all the others worked fine. I put the other 14 back up on the shelf. A customer was having difficulty connecting to his recent vintage XB12 ECM. He sent it to me for testing, with his cable. His cable would talk to other ECMs I had in the shop, but not his ECM. I hooked his ECM up to my cable, it could talk. I hooked that ECM up to the cables I had in stock, it wouldn't communicate with any of them. Technoresearch has indicated that a bunch of cables built over the past few months have firmware that has the baud rate set at the hairy edge on the dongle drivers. When combined with the recent race ECMs that appear to be also baud-rate critical, they have communication issues. If you suspect that you have a bad cable, send it back to Technoresearch, they will reprogram the firmware and all will be OK. Pain in the butt, I know. But that's what it will take to get it fixed. | ||
| Chopperboy |
Al, Thanks for the input. I would assume my Uly has a later generation race module as the race kit was installed this past April before I took delivery. I will keep you posted. |
