AccessPORT cable supported in ecuExplorer!!

[bander]

We've added primitive support for the new AccessPORT USB-OBDII cable in ecuExplorer that will allow you to log parameters to your PC using the cable supplied with your AccessPORT.

http://www.accessecu.com/support/oth...cuExplorer.zip
http://www.accessecu.com/support/oth...llAPDongle.exe

Run the installAPDongle.exe file and note which directory it installs to, as you will need to extract the ecuExplorer.exe file into the same directory. After this is done, you should be able to run the extracted ecuExplorer.exe file with the dongle plugged into the PC and your vehicle.

KNOWN ISSUES:
This wouldn't run on our Vista machine
The cable must be plugged in prior to running ecuExplorer

Please do not call Tech Support with issues as they have not been informed on how to support ecuExplorer. Post problems here and we will try to address them.

For those interested (and in the name of truly open-source software), here's the source:

http://www.accessecu.com/support/oth...plorer-src.zip

[jsnuff1]

Awsome, I have been working on this for use with enginuity but looks like you beat me too it.

Few questions, this is for the AP v2 cable correct? Does Ecuexplorer still only support only 05 and before USDM sti models? I remeber that it dosent support drive by wire systems in 06 and 07. Thanks!

[bander]

Correct, AP v2 cable.

I don't know what ECUs ecuExplorer supports, though it would make sense that recent vehicles aren't supported as I don't think improvements have been made to ecuExplorer for a while.

I just tested it on an 07 STI and it connected and displays parameters, though it doesn't show what type of ecu it is connected to.

[BCwrx]

Awsome, I have been working on this for use with enginuity but looks like you beat me too it.

Few questions, this is for the AP v2 cable correct? Does Ecuexplorer still only support only 05 and before USDM sti models? I remeber that it dosent support drive by wire systems in 06 and 07. Thanks!

So i take it i shouldn't even try this with my 07 WRX?

[Charlie]

So i take it i shouldn't even try this with my 07 WRX?

Maybe try it???.....

"I just tested it on an 07 STI and it connected and displays parameters, though it doesn't show what type of ecu it is connected to."

[jsnuff1]

hmm tried this out and no luck. In your intructions you say to just run the driver installer, but all that does is extract the driver files. When I plugged in my cable the driver install wizard still poped up. I just told it to find the driver from the exracted driver files from your utility, and it said the device was installed but it wouldnt even connect in ecuexplorer.

Since you guys are already working on this why not just make a stand alone driver for the ap v2 cable that will work with all the open source datalogging options, like enginuity.

[MBasile]

awesome timing since I need to datalog some stuff. Any word on working in parallels on a mac?

[bander]

hmm tried this out and no luck. In your intructions you say to just run the driver installer, but all that does is extract the driver files. When I plugged in my cable the driver install wizard still poped up. I just told it to find the driver from the exracted driver files from your utility, and it said the device was installed but it wouldnt even connect in ecuexplorer.

Since you guys are already working on this why not just make a stand alone driver for the ap v2 cable that will work with all the open source datalogging options, like enginuity.

This has been a side project in my own time as there are so many other things in the development pipeline here at COBB. I looked at adding driver support to enginuity and it was significantly more complicated than hacking in the support to ecuExplorer. The COBBdriver.dll is essentially a standalone driver; someone with more knowledge of enginuity and the time can port it to work with enginuity. (Hint: COBBcommSerial.cpp and cobb_comms_interface.h)

The driver installer is supposed to pre-install the driver for the cable but it seems that it isn't quite working properly. I have gotten it to work with two or three different AP v2 cables and 3 or 4 different cars, though I will try to spend some time today figuring out why it hasn't worked for some people.

[BCwrx]

I've never worked with ECUExplorer but i got the driver installed and the software in the same directory as the driver. I ran the program and then plugged in the usb cord to my compupter. The 'ECU' node in the treeview still says disconnected. Is there a way to say 'try to connect to ecu' ? or anything like that. Or basically if your plugged in to the ecu and it says that you are still disconnected means it wont work?
'07 WRX TR

[MBasile]

I've never worked with ECUExplorer but i got the driver installed and the software in the same directory as the driver. I ran the program and then plugged in the usb cord to my compupter. The 'ECU' node in the treeview still says disconnected. Is there a way to say 'try to connect to ecu' ? or anything like that. Or basically if your plugged in to the ecu and it says that you are still disconnected means it wont work?
'07 WRX TR

I think it said somewhere in the instructions that you have to connect the AP cable before opening ECUExplorer