ScanGauge, TurboGauge or UltraGauge on '04?

[stevec5000]

Is anyone here using one of these gauges on their '04 and if so, how is it working? I was looking at getting a ScanGauge but ended up buying a TurboGauge instead that was only $70 on ebay. I think it looks better and has some additional functions like serving as a black box but when I plugged it into the OBDII connector it caused the Trac Off and VSC Trac warning lights to come on! I don't know if that is actually disabling the ABS or not but the vehicle seems to run OK otherwise.
After some searching I found that UltraGauge had the same problem on Toyota Tacoma 2001-2004 models with ABS and their solution was to cut the wires going to pins 6 & 14 of the vehicle's OBDII connector! This issue was corrected by Toyota in 2005 and later years. They don't mention the 4Runner but the solutions seems a bit too drastic. Since the OBDII connector needs to work for emissions testing to get my plates renewed everytime I don't want to do anything to alter it's function.
Does the TurboGauge have the same problem or can it deal with the 4Runner without any problems?

Toyota Tacoma 2001-2004 with ABS

 

[MistrWebmastr]

It's all in what connection that the unit tries to connect to the car with. There's 3 different languages that devices use to connect to the ODB II port. I don't remember what they are off the top of my head but there's one that knocks out the zero-point calabration. That's why TRAC and VSC are off. You'll still have ABS, but A-TRAC and VSC will not function until you reset your zero-point calibration. It happens every few months with my Scan-Guage II, but I keep a set of wires and the instructions in my glove box for whenever that happens.

 

[stevec5000]

I went out and looked at the OBDII connector again and it has a wire in pin 14 but none in pin 6 so I might just remove the one in 14 and tape if off so it don't cause problems.

 

[BlackWorksInc]

That's one solution that seems reasonable. But remember to put it back if you ever have any issues and need to use a scantool so you don't confuse the technician.

 

[stevec5000]

That's one solution that seems reasonable. But remember to put it back if you ever have any issues and need to use a scantool so you don't confuse the technician.

I would never take my vehicle to a shop so I don't think that will be a problem. Not sure about the Arizona emissions test though.

 

[Martinjmpr]

I know Toyota made a lot of changes for the 05 model year, so this may or may not be helpful, but I have been running a SGII on my '07 V6 4x4 since I bought it at the end of June with no issues or problems.

I like the SG because it can be programmed to show the transmission temperature (via the Xgauge feature.)

I've used both the SG and the Ultra Gauge on my '99 SR5 4x4 also. Both worked fine, but I ultimately went with the SG because of the trans temp (a capability that the UG doesn't have.) The UG is actually in my DD Mazda (which has a manual tranny so I don't need a Trans Temp reading.)

My opinion on the SG vs UG is mixed. The SG is higher quality and has features like the X gauge that are nice. It is also easier to flush mount because all the controls are on the front.

OTOH, the UG is half the price, has a better display, shows more information (6 gauges at a time vs the SG's 4) and has a much finer calibration capability. It's not as easy to mount because you need to access the buttons on the back in order to work it. Also the "fill up drill" on the UG takes longer than on the SG.

Don't know anything about a Turbo Gauge so I can't comment on that.

 

[stevec5000]

The TurboGauge is just like the ScanGauge without the X gauge features so it won't measure tranny temp, at least I don't think it will. I finally got it to work in my '04 without causing problems by opening it up and disconnecting the pin from the RJ-45 connector that goes to pin 14 on the OBDII connector. Unfortunately it had already cleared the settings for the VSC that disabled it and caused the warning lights to come on when I plugged it into the OBDII connector so I had to do a zero point reset to turn off all the warning lights and get everything working properly again. I also ordered an UltraGauge to try out but it looks hard to open without breaking it so I don't know if I can disconnect the wire for pin 14 in it or not.

 

[earthrealm]

on the ultrgauge manuaal, there is procedure for thiis problem, pge 41.
Force Protocol
MENU  Vehicle Setup ..  Force Protocol
Forces UltraGauge to use a specific protocol to communicate with the Vehicle’s Electronic Control Module (ECM).
When UltraGauge is attached to the OBDII connector it begins scanning for one of five possible interfaces/protocols. Once it determines
the interface it then discovers the available gauges
During the scanning phase UltraGauge tries each of the electrical interfaces and protocols associated with the OBDII standard.
Depending on the interface, different pins of the OBDII connector are used:
Interface Connector Pins
J1850-VPM 2
Early Ford 2,10
ISO 9141 7,15
CAN 6,14
KWP2000 7,15
Common pins:
Battery 16
Ground 4,5
Vehicle’s OBDII connector pin-out:
The issue is that some manufacturers improperly use pins that they should not. For example, a 1999 Ford would use pins 2,10,16,4 & 5.
If Ford then used any of the other pins defined above, say pin 7 & 15, the stage is set for a potential issue.
During the scanning phase UltraGauge will try each of the interfaces. Returning to our example, while Scanning our 1999 Ford,
UltraGauge will drive pins 7 & 15 in an attempt to determine if the vehicle is ISO 9141. Since the vehicle is a Ford, no communication
will be established and UltraGauge will try the next interface. If however, the manufacturer has used pins 7 & 15 for proprietary uses, the
vehicle may become impaired. For example, on some vehicles the traction control light may become lit, or the speedometer or other
gauges may temporarily stop functioning, or the check engine light may become lit. To avoid these issues, the Protocol & Interface can
be fixed to that used by the vehicle. When the protocol is forced, UltraGauge will only try the set protocol. In the case of our 1999 Ford,
UltraGauge will only drive pins 2 and 10, and will no longer attempt to drive pins 7 & 15.
UltraGauge Automatically remembers the last found protocol and attempts to communicate with the vehicle’s ECM using that protocol.
As long as communication is established, UltraGauge will not attempt other protocols. If communication is not established, then
UltraGauge will cycle though each protocol until communication is established. Forcing the protocol will prevent this and UltraGauge
will repeatedly try only the forced protocol.
Force Protocol Description
Auto Discovery Scans the interface for the protocol. This is the default setting
Force J1850-VPM Early GM vehicles and some Chrysler vehicles
Force 9141 Most early foreign vehicles and most early Chrysler vehicles
Force Ford Exclusively used on early ford vehicles.
Force KWP2000 This rare protocol is used on various vehicles.
Force CAN Used on all 2008 and newer vehicles as well as on many 2004 and newer vehicles.
Force Current Forces the Protocol currently in use, found during the scanning process. Use this if
you can’t remember the protocol found