ECU Explorer connection quirk issue, any help appreciated
12-01-2005, 06:44 AM
#1
Junior Member
Thread Starter
Join Date: Jul 2000
Posts: 862
Likes: 0
Received 0 Likes
on
0 Posts
ECU Explorer connection quirk issue, any help appreciated
I called APR but their ECUx Engineer is out right now, they are also still out of stock on their cables, here's my issue;
I can check my ecu for DTC's using ecux but when I ask it to log a group file it won't work. I hit start on the logging session and it waits for 15 seconds then a dialog box opens ( ecu acquisition) and it tells me "write to specified main failed" why would checking dtc's work fine but not logging ?
I have worked on this for hours but can't understand it. This same cable works fine with vag-com and lemmiwinks . I am using serial cable ( OBD Tool cable ) with a keyspan serial to usb converter connected to one of my usb ports. Do I need to run some of kind of serial emulator software on my usb port? I have tried using both the keypsan drivers as well as the APR USB drivers. But no go.
Any help is appreciated. I am running a Toshiba A-65 laptop running XP, 2.8Ghx chip with 700MB memory. I connected to the toshiba website and checked for driver updates.
I can check my ecu for DTC's using ecux but when I ask it to log a group file it won't work. I hit start on the logging session and it waits for 15 seconds then a dialog box opens ( ecu acquisition) and it tells me "write to specified main failed" why would checking dtc's work fine but not logging ?
I have worked on this for hours but can't understand it. This same cable works fine with vag-com and lemmiwinks . I am using serial cable ( OBD Tool cable ) with a keyspan serial to usb converter connected to one of my usb ports. Do I need to run some of kind of serial emulator software on my usb port? I have tried using both the keypsan drivers as well as the APR USB drivers. But no go.
Any help is appreciated. I am running a Toshiba A-65 laptop running XP, 2.8Ghx chip with 700MB memory. I connected to the toshiba website and checked for driver updates.
12-01-2005, 07:02 AM
#3
are you using stock ECU or other?
reason I ask is that I had to return ECU Explorer about a year ago because it wouldn't work with my AMS chip....went back and forth with AMS/APR but never got resolution.
12-01-2005, 07:44 AM
#6
Junior Member
Thread Starter
Join Date: Jul 2000
Posts: 862
Likes: 0
Received 0 Likes
on
0 Posts
Yes, I know for sure becuase it tells you at the bottom of the group file window
it says ecu properties associated is vag120.
Here's another twist, I am running M code on a H box. I tried both properties files for M code as well as H but no go. It looks like it is recognizing the ecu ( M code ) and I can check and clear dtc's but the logging won;t work. trying to figure out what the "write on specified main failure" means. Wonder if's go something to do with my ECU ?
Here's another twist, I am running M code on a H box. I tried both properties files for M code as well as H but no go. It looks like it is recognizing the ecu ( M code ) and I can check and clear dtc's but the logging won;t work. trying to figure out what the "write on specified main failure" means. Wonder if's go something to do with my ECU ?
Trending Topics
12-01-2005, 07:56 AM
#9
Junior Member
Thread Starter
Join Date: Jul 2000
Posts: 862
Likes: 0
Received 0 Likes
on
0 Posts
I remember Doc saying he couldn;t get his working and to use a
serial emulator driver or something to that affect on one of his USB ports. Not sure which one he used he never specified as far as I can tell.
12-01-2005, 08:00 AM
#10
Junior Member
Join Date: Mar 2000
Posts: 572
Likes: 0
Received 0 Likes
on
0 Posts
Lower the baud rate way down to 10400
If your cable uses optoisolators, it may have problems at the higher baud rates. Also, always use the property file corresponding to the software that you are running on the ECU (ignore the hardware number.) So if you are running M code, use the M code properties file.
ECUX cables are out of stock and unfortunately probably will be until January. But there is good news. The reason they are out of stock is because there is a new cable design. This cable will be the one that will be designed to work with ECUX V2.0 which should be available sometime in the spring.
edit: the APR USB drivers won't work with the cable you are using. Your setup emulates a standard COM port. Assuming your emulator is setup properly (which it sounds like it is), just select the appropriate port in ECUX settings.
Brett
APR
ECUX cables are out of stock and unfortunately probably will be until January. But there is good news. The reason they are out of stock is because there is a new cable design. This cable will be the one that will be designed to work with ECUX V2.0 which should be available sometime in the spring.
edit: the APR USB drivers won't work with the cable you are using. Your setup emulates a standard COM port. Assuming your emulator is setup properly (which it sounds like it is), just select the appropriate port in ECUX settings.
Brett
APR