So I just randomly saw this thread, downloaded the program, and tried it out with my AccessPort cable. What a cool program! I don't have any real use for it, but its still cool to pull up plots in excel of everything!
If your asking about JDash, then at present only the Tactrix OpenPort cable works. I'm still working on making JDash work with an ELM module. Thats my next big goal.
What serial to usb adapters are compatible? I pan on using the AP cable.
If you don't already have the AP cable, they already make a OBD-II->USB version. It uses the FTDI usb->serial adapter internaly. I am also doing some testing with a friends older OBDCOM cable through a keyspan USB adapter. And so far, so good.
I have the cable... I just dont have a serial port on my laptop... I need to know that brand adapter works best with the data logger and the ap's cable. Someone said the Belkin doesnt work and someone said the Radio Shack adapter works...
Looking at the Tactrix website, there are two cables there, the "OpenPort for WRX and drive-by-wire vehicles" and also the "OpenPort for Subaru Drive-by-wire vehicles". From what I can tell the only difference is the WRX-specific one comes with a reflash connector.
I have an 05 Impreza RS, which was the first year for n/a Impreza's getting drive-by-wire. The OpenPort for Subaru vehicles only lists the turbo models as compatible, but it looks from this thread like other Impreza owners have used this thing without issues, anybody have anything to say about my application before I order one up?
I have the cable... I just dont have a serial port on my laptop... I need to know that brand adapter works best with the data logger and the ap's cable. Someone said the Belkin doesnt work and someone said the Radio Shack adapter works...
Belkin works on my son's XP laptop along with an AP cable connected to a 2002 RS2.5.
Not quite. But almost. As I understand the OBD-II interface, it's not directly compatable with a PCs serial port. The cables on that site seem to provide a way of connecting the standard OBD plug to a standard DB9 plug. But, from there, you still need some hardware to convert the line signals to one a PCs serial port would understand.
I tried searching this thread but couldn't seem to find the answer. The ecuExplorer is giving me a bunch of currrent and historic trouble codes (both lists are the same). However, there is no check engine light on. Should I worry about these trouble codes?
I am using v3.0.25 and saw an old post that there might be issues with trouble code reading...I'm just wondering if I should worry about the 19 trouble codes showing up as current AND historic...thanks
I posted this in its own thread, but thought I'd mention it here for anyone that is subscribing to this thread. I put up a webapp that will do some simple analysis and create graphs from your logfiles. The thread can be found here, and the webapp is located at http://www.waygate.net/plotter
not sure if this has been broughten up yet..but i own a AP v2 with the USB cable not the serial cable..wondering if it would work going from the AP obd plug and connecting the mini usb motorola to and then connecting that to the ole laptop?? hopefullyyyyy
You can but it won't include any realtime maps. Not sure what the point would be if it did include the realtime maps. Cobb = very safe and conservative. Theres lots and I mean lots of power left on the table.
Does ecu explorer use the subaru select monitor protocol? I'm wondering if i can pin out tx, rx signals to the yellow subaru connector. I got legacy 2,5 euro my96. It hasnt obdii connector.
Does ecu explorer use the subaru select monitor protocol? I'm wondering if i can pin out tx, rx signals to the yellow subaru connector. I got legacy 2,5 euro my96. It hasnt obdii connector.
I have the accessport cable and an adapter to plug it into my USB port. However when i plug everything in and turn on the car it still says the ecu is disconnected? What could be wrong? Something having to do with com porte setting i am thinking?