ScanGauge II Ultra Compact 3-in-1 Automotive Computer

[processengr]

Anyone familiar with "ScanGauge II Ultra Compact 3-in-1 Automotive Computer with Customizable Real-Time Fuel Economy Digital Gauges" a plug in OBD2 reader that can be left connected for some information displays. Thinking about it for our 97 SVX and our 99SLK

[Green1995SVX]

Originally Posted by processengr

Anyone familiar with "ScanGauge II Ultra Compact 3-in-1 Automotive Computer with Customizable Real-Time Fuel Economy Digital Gauges" a plug in OBD2 reader that can be left connected for some information displays. Thinking about it for our 97 SVX and our 99SLK

I've used that product. It's neat.

I have a product from gopoint technology that is more powerful and simply plugs into your iphone or ipad. This is the best, most powerful OBD2 device i've ever used at this price point.

http://gopointtech.com/

[processengr]

Wow,looks great! Do you have the cable version or the bluetooth? Which Apps are you using? the price on the website is a lot lower than Amazon!

[Green1995SVX]

Originally Posted by processengr

Wow,looks great! Do you have the cable version or the bluetooth? Which Apps are you using? the price on the website is a lot lower than Amazon!

I have the cable one, and I bought it from amazon before I realized how cheap it was elsewhere (oops!). I am using the standard GoPoint free app.

[processengr]

The Scangauge2 info shows it can read autotrans temp. this is useful, does anyone know if the 97 SVX transmits that info over the OBD2?

[DiabloScoobyru]

Check into the Ultragauge as well. Much cheaper, functions just like the SGII, and gives more info while allowing you to set high and low threshold alarms (perfect for watching your tranny temps ) At $79, ya can't go wrong compared to the $165 for the SGII. Not to mention, they pay you for completing the registration process ($9), and it comes with a windshield mount. Can't go wrong there

http://www.ultra-gauge.com/ultragauge/index.htm

http://ultra-gauge.com/ZC/index.php?...ea4sqh6e22t384

[jellybytes2]

The ultragauge web page states that is does not read trans temps,

[DiabloScoobyru]

Originally Posted by jellybytes2

The ultragauge web page states that is does not read trans temps,

I stand corrected

Sorry about that. I looked at the page awhile back and could have sworn it said trans temps were monitor-able. I was looking at it more for the MPG tracking and engine load gauges myself. Trying to hypermile the Leg. OB wagon.

[processengr]

Although the scangauge 2 can be configured to read auto transmission temps in some cars, it cannot read the SVX with OBD2 because the trans sensor reports to the TCU, not the ECU.

[Huskymaniac]

I stumbled on what may, or may not, be a new option for us.

When looking at Phil's website I saw he had a link to EvoScan. I checked it out and they have cables for OBD1 Subarus, OBD2 Subarus from 1996-1998 and newer OBD2 Subarus. The cables provide access to SSM pins and, supposedly, the software provides SSM data. The interesting thing is that Subaru OBD2 cars from 1996-1998 apparently use SSM1 and provide SSM1 pins on the OBD2 connector. Most other companies that have tried this in the past only supported SSM1 on OBD1 cars (pre-1996). Some also picked up SSM2 for 1999 cars forward. This is the first time where a company supposedly has a product that will communicate with 1996-1998 OBD2 cars using SSM1 protocol. I am going to buy it and try it out. They are also working on iphone and Android software.

Cable Selector Page:
http://www.evoscan.com/mitsubishi-su...bd2-can-cables

Cable that will work for either OBD1 or OBD2 SVXs:
http://www.evoscan.com/evoscan-gps-o...lect-monitor-i

And there are cables for 1999-2007 OBD2 cars as well as 2008+ OBD2 cars and there are versions for flashing these newer vehicles as well as versions for just datalogging.

[processengr]

This is great! Waiting to hear your findings!

[Huskymaniac]

Originally Posted by processengr

This is great! Waiting to hear your findings!

I bought cables for both the 1996 OBD2 SVX and the 2006 Tribeca. I have no idea how long they will take to come from NZ.

[Tapani]

Check out freeSSM and ROMRAIDER too. I have both - work real well on both my 2006 Outback and wifes 2007 Forester. They are said to work on all 1999-2009 Subarus, I do not know if they can be used with OBDII SVXs, though. I understand that ALL TCUs are OBD1 in the OBDII SVXs - so maybe they can not be reached.

The ROMRAIDER has nice trending features and does logging to a file too, which is very neat.

http://www.subaruoutback.org/forums/...r-ecm-tcu.html

http://legacygt.com/forums/showthrea...ad-151177.html

I was able to "fix" a glitch in my 5EAT by clearing all it had learned and then forcing to relearn. Needed the FSM for this too, though.

They use the same VAG cable, which can be had at as low as $12 on ebay. This works with the same drivers as SVX interface for the ECUTuner from Mike and all run on Windows 7 too.

All this is so cheap and easy - I think everyone with troubleshooting and diagnostics issues should have them .

Tapani

[Huskymaniac]

I have an update on this as well.

First, thanks to Phil for his help.

I can report that the hybrid OBD1/OBD2 cable does indeed work on our OBD2 SVXs. It enables us to access the ECU through the SSM1 protocol. However, the memory addresses are NOT the same as the ones used on the OBD1 cars. I tried some memory addresses from a 1996 Impreza and most of them worked. I can get access to battery voltage, speed, RPM, coolant temperature, ignition advance, MAF sensor voltage, engine load, TPS voltage, injector pulse width, ISU valve duty cycle, knock correction, atmospheric pressure, and manifold relative pressure. I believe I am also able to get one of the air/fuel correction numbers. I still need to verify that and find the correction for the other bank. I also need to find the signals for all three oxygen sensors. The ECU varies from the Impreza mainly in the fact that each bank is handled seperately and there are three oxygen sensors. For the parameters mentioned above, I have the updated definition file so the evoscan software can communicate with the OBD2 SVXs.

I also managed to get JECScan working with my OBD2 ECU with the same parameters. I have the updated definitions file for this software as well. Evoscan does NOT have the ability to communicate with the TCU but JECScan does. Unfortunately, none of the OBD1 TCU addresses worked on my OBD2 car so that will take a significant amount of investigative work. If we can determine the addresses, however, we will be able to use this cable to talk to both the ECU and TCU through JECScan.

I also tried out FreeSSM and it does not support OBD1. Phil said that an OBD1/SSM1 version was available but I have not contacted the person who wrote the code yet.

Bottom line is that the cables from evoscan work and the free JECScan software works as well. The not free evoscan software has some nice features and may be worth the $20 but it does not communicate with the TCU whereas the JECScan software theoretically does with OBD2 cars and has been proven to work with the OBD1 cars.

[steveherman]

Originally Posted by Huskymaniac

I have an update on this as well.

First, thanks to Phil for his help.

I can report that the hybrid OBD1/OBD2 cable does indeed work on our OBD2 SVXs. It enables us to access the ECU through the SSM1 protocol. However, the memory addresses are NOT the same as the ones used on the OBD1 cars. I tried some memory addresses from a 1996 Impreza and most of them worked. I can get access to battery voltage, speed, RPM, coolant temperature, ignition advance, MAF sensor voltage, engine load, TPS voltage, injector pulse width, ISU valve duty cycle, knock correction, atmospheric pressure, and manifold relative pressure. I believe I am also able to get one of the air/fuel correction numbers. I still need to verify that and find the correction for the other bank. I also need to find the signals for all three oxygen sensors. The ECU varies from the Impreza mainly in the fact that each bank is handled seperately and there are three oxygen sensors. For the parameters mentioned above, I have the updated definition file so the evoscan software can communicate with the OBD2 SVXs.

I also managed to get JECScan working with my OBD2 ECU with the same parameters. I have the updated definitions file for this software as well. Evoscan does NOT have the ability to communicate with the TCU but JECScan does. Unfortunately, none of the OBD1 TCU addresses worked on my OBD2 car so that will take a significant amount of investigative work. If we can determine the addresses, however, we will be able to use this cable to talk to both the ECU and TCU through JECScan.

I also tried out FreeSSM and it does not support OBD1. Phil said that an OBD1/SSM1 version was available but I have not contacted the person who wrote the code yet.

Bottom line is that the cables from evoscan work and the free JECScan software works as well. The not free evoscan software has some nice features and may be worth the $20 but it does not communicate with the TCU whereas the JECScan software theoretically does with OBD2 cars and has been proven to work with the OBD1 cars.

So will the cable work on obd1 cars ecu and tcu?
So will the evoscan software work on obd1?
And so does this mean u want to sell ur cable?