PCMSCAN + Subaru, which adapter

**benetton** · 07-13-2006, 01:32 PM

I have done many searches but cant find an answer, I want to use the PCMSCAN software, but trying to find out which obd2 adapter would work better on a subaru, PCMSCAN lists,
1- elm 327
2- Mobydic
3- autotap
4- mongoose

I want to know if there are any real difference in the refresh rate between any of these, I want to be able to use the gauges with the least amount of lagging.

I know there is deltadash but abit out of my price range.
and I have also see open port 1.2 but can't find if it will work with the PCMSCAN.

Thanks Brad

**CADILLAC** · 07-13-2006, 01:37 PM

did u try

**benetton** · 07-13-2006, 03:15 PM

yes I did!!, I also check scoobymods and nasioc

**SanRemoRex** · 07-13-2006, 11:16 PM

Not really familiar with PCMSCAN, don't know if it works with a serial interface or what, but I use the cable from my AccessPort (Diagnostic to Serial) with ECUexplorer. Great (and free!) software, has some really cool features built in (like starting/ending a datalog with the defrost button). Unfortunately, the interface is really nothing special. Again I dunno what PCMSCAN has going for it (although I believe it does integrate well into the popular FEs, where I doubt ECUexplorer will), but that might give you a couple things to look into. Also, ECUexplorer uses the Suby-specific SSM profile as well as OBD-II, allowing it to read additional sensors, and at faster rates.

I personally plan to exit RR and use ECUexplorer separately when I'm at races, once I switch over to the Pandora.

**Podaman** · 07-28-2006, 03:08 AM

Originally Posted by TunerTools

PCMSCAN will work with all of the tools you've listed, including the Openport 1.2.

If, on the other hand...... you intend to get into reflashing the program on your ECU, you should probably take a harder look at the OpenPort 1.2 application and visit the folks over at www.OpenECU.org.

Hi TunerTools, question for ya:

I just received the Tactrix OpenPort 1.2 USB interface for my Subaru 2006 WRX. I installed the XP drivers and set the virtual com port to COM 4. I tried TARI Racing Software's free DL1 Subaru diagnostic application as a test and it worked fine. I would drive around and my friend could watch the live data change on his laptop.

However, I used PCMSCAN next and couldn't get it to work. I tried connecting with all of the listed connector types (ELM, T16, Autotap, J2534, mOByDic) and none of them would allow me to connect. Maybe I'm missing a simple configuration step? Which of these PCMSCAN supported connector types are closest to the OpenPort 1.2 since I can't select the exact connector from the list?

One thing I noticed: the Tactrix website says the OpenPort 1.2 is an ISO 9141-2 compatible OBDII interface... while the PCMSCAN website says the supported protocol is ISO-9141... without a -2. I wonder if that makes a difference.

**joeyoravec** · 07-28-2006, 10:44 AM

ISO9141 is the specification for vehicle and the -2 just refers to a particular section of the document. What you're experiencing is a driver problem.

The Tactrix cable is interesting; it is a simple, low-cost voltage converter and implements everything with windows serial driver. Since it doesn't use a standard API, it's only compatible with software written specifically for that cable (ie. the Subaru software you mentioned). It's a proprietary cable and unfortunately you're stuck since PCMScan doesn't support it.

**Podaman** · 07-28-2006, 01:25 PM

Originally Posted by TunerTools

Sorry Podaman, I was wrong and Joey is correct... PCMSCAN does NOT support these Tactrix cables. My mistake

NP TunerTools, I'm just glad there's a place like this I can go to when I'm stuck and have questions.

Originally Posted by TunerTools

Subaru does not yet support the J2534 pass-thru standard and the Mongoose doesn't provide the voltage necessary for reprogramming a Subaru.

It looks like on the Drew Tech website in the "Matrix of Drew Tech Customers and Product Uses" Subaru is listed as a target customer.

Could you confirm, joeyoravec, that Subaru's don't work with the Mongoose via the J2534 pass-thru standard? I'm not too worried about reprogramming the ECU. I have the OpenPort 1.2 for that now

. Will the Mongoose ever support reprogramming Subaru ECUs?

If it's true that Subaru's still don't support J2534 then I guess I'll go with the ElmScan 5 to use with PCMSCAN. I'm curious though... what kind of update intervals do you get monitoring, say, a single parameter, like RPM, over the slower ElmScan 5 serial speed connection? Sub 100ms? I'd imagine the faster Mongoose with it's full-speed USB 2.0 connection can handle thousands of updates a second.

**joeyoravec** · 07-28-2006, 01:53 PM

Originally Posted by Podaman

Could you confirm, joeyoravec, that Subaru's don't work with the Mongoose via the J2534 pass-thru standard? I'm not too worried about reprogramming the ECU. I have the OpenPort 1.2 for that now

. Will the Mongoose ever support reprogramming Subaru ECUs?

I can't confirm it because it's not true. But I'll clarify what I think he meant to say:

Similar to the generic driver that lets all printers work together, the SAE (in document J2534) defines a generic driver that lets laptop-to-vehicle PassThru interface cables work together. In this way the low-cost Mongoose cable works perfectly fine with Subarus. You can read and clear codes, pull live parameters, etc. At a basic OBD-II scantool level things are quite simple, always compatible, and the main difference you'll see between tools is speed.

Lloyd's point is that all automakers are required by law to provide reprogramming software to update the factory calibration, but Subaru is on the "naughty" list for failing to provide this software. Subaru assures me that they're working on software and it should be available soon. The older Subarus require a more complex flash tool because they need an extra voltage to enter programming mode. The newer models got rid of that requirement and the Mongoose could probably flash fine. I'll do the testing as soon as something's available.

**Podaman** · 07-28-2006, 06:02 PM

Originally Posted by joeyoravec

...and the main difference you'll see between tools is speed.

Great info joey, thanks.

I've read countless times how you and TunerTools swear by the increased speed of the Mongoose. I know USB is much faster than serial, there's no question about that, but...

Do you have any real-world update interval numbers to compare the Mongoose with the serially-connected scantool competition? (besides the generic max theoretical full-speed USB 2.0 12 mbps bandwidth statistic)

Or perhaps a visual description of the real-time virtual dashboard performance difference? (If any)

Surely there must be some comparison benchmarks to demonstrate the advantage of the superior USB connected Mongoose besides the marketing phrases "increased speed" and "high performance".

I would just like a little more convincing (warm fuzzy) before I shell out 200 bucks on a 5' connector. I'm sure you can see where I'm coming from

. Maybe this info is already lieing around somewhere and I just missed it somehow... if that's the case, my bad.

Thanks!

**joeyoravec** · 07-28-2006, 06:19 PM

Originally Posted by Podaman

Do you have any real-world update interval numbers to compare the Mongoose with the serially-connected scantool competition? (besides the generic max theoretical full-speed USB 2.0 12 mbps bandwidth statistic)

It all depends on the software. On PCMScan in particular the difference isn't huge because he uses a fairly slow technique for requesting data. Aside from the obvious benefit of having a standard cable, the speed does help. It's possible to sniff the bus and not drop a single packet. Can't say that for other low-cost cables.

I'm working on a plug-in library right now that software vendors can use to get the rapid packet datalogging (typical ford/chevy approx 150-200 frames/sec). And now I'm logging off the forum so I can actually get this programming done and push the library into the marketplace.

Keep in mind that I design this cable at an electronics manufacturer, but this library should help the software vendors catch up with technology. There should be some great stuff available within the next several months.