Help please, Scangauge II messed up my engine! (2 Viewers)

[Timpanogos Slim]

No. It cannot.

 

[TrickyT]

TrickyT, You are right, and the tech on the phone was wrong, our trucks use J1850 VPW, not ISO. So that cable they sent me was a mistake, and in looking at it, has different pins than the female connector on the truck so I bet it would not even work.



Now that we know our truck are J1850 VPW, I'm going to assume you are asking if we use something other than a "J1850 VPW" cable can mess things up? i have no idea.

You don't need a different cable!!! The one you have will work with your Scan Gauge II and a FZJ-80 just fine. My point in my previous post was your cable is not an "ISO only" cable. That's the benefit/beauty of the OBD-II standard. It's supports all OBD-II "required" protocols. So the cable you have works with J1850 VPW, J1850 PWM, CAN, and K-line/L-line protocols. And the Scan Gauge II works with all of those protocols. It senses which communications protocol the vehicle supports and then uses it. And all OBD-II compliant vehicles must implement one of those protocols. So plug it in and use it. You can't do any damage to your ECU, and the Scan Gauge will display all the standard OBD-II parameter values.

In addition to the standard OBD-II emissions-related protocol/parameter support, the OBD-II connector also supports "Manufacturer Discretion" signals. This is used for additional vehicle-dependent computer signaling, like "report status of SRS airbags" or "unlock all the doors". Things that have nothing to do with emissions. The Scan Gauge II doesn't support Manufacturer Discretion signals and neither does the cable you have.

 

[Timpanogos Slim]

The Scan Gauge II doesn't support Manufacturer Discretion signals and neither does the cable you have.

Point of order. Scangauge doesn't, but that's not the fault of the physical interface. Some ECUs have proprietary PIDs that aren't advertised. Others, like VW/Audi, have extensions to CAN and KKL.

But the interface hardware is pretty much all the same. My $350 VCDS cable for my german cars is just a cheap universal usb obd2 cable with the addition of a serial number for Ross-Tech VCDS encoded somewhere. And i say cheap because it turns out that the interface isn't isolated.

 

[Surfdc]

You don't need a different cable!!! The one you have will work with your Scan Gauge II and a FZJ-80 just fine. My point in my previous post was your cable is not an "ISO only" cable. That's the benefit/beauty of the OBD-II standard. It's supports all OBD-II "required" protocols. So the cable you have works with J1850 VPW, J1850 PWM, CAN, and K-line/L-line protocols. And the Scan Gauge II works with all of those protocols. It senses which communications protocol the vehicle supports and then uses it. And all OBD-II compliant vehicles must implement one of those protocols. So plug it in and use it. You can't do any damage to your ECU, and the Scan Gauge will display all the standard OBD-II parameter values.

In addition to the standard OBD-II emissions-related protocol/parameter support, the OBD-II connector also supports "Manufacturer Discretion" signals. This is used for additional vehicle-dependent computer signaling, like "report status of SRS airbags" or "unlock all the doors". Things that have nothing to do with emissions. The Scan Gauge II doesn't support Manufacturer Discretion signals and neither does the cable you have.

Awesome! Ok good to know. I wasn't sure about the whole different cable theory anyway. Anybody want an "ISO cable only" for one othe their other cars!?
Hey wingman, what did the dealership tell you?

 

[TrickyT]

Point of order. Scangauge doesn't, but that's not the fault of the physical interface. Some ECUs have proprietary PIDs that aren't advertised. Others, like VW/Audi, have extensions to CAN and KKL.

But the interface hardware is pretty much all the same. My $350 VCDS cable for my german cars is just a cheap universal usb obd2 cable with the addition of a serial number for Ross-Tech VCDS encoded somewhere. And i say cheap because it turns out that the interface isn't isolated.

Agreed. Newer Toyota's like my FJ Cruiser use multiple protocols and have proprietary PIDs that are intended for use only by Toyota-trained technicians. My FJ uses the CAN bus for communications between the engine ECU, skid control ECU, yaw rate sensor ECU, and steering sensor ECU. And it uses the BEAN bus (body electronics area network) for communications between the body ECU, door lock ECU, occupant classifier ECU, and airbag ECU. And one of the "manufacturer discretion" signals in the OBD-II connector enables the reflashing of the engine ECU and skid control ECU. It's been at least 20 years since the FZJ-80's OBD-II ECU was designed, and there's been a tremendous revolution in computing over that time period. Now you can't just be a mechanic to work on newer vehicles, you've got to be a computer technician too.