GM Tech 2 interface
Author
Discussion

DrDoofenshmirtz

Original Poster:

16,952 posts

230 months

Wednesday 10th September 2014
quotequote all
Does anyone know anything about GM's Tech 2 interface?
I own a SAAB, and I'd like to have a look around - I know there is a whole raft of things you can do. For example, I'd like to enable the AUX input option on the stereo etc.
A proper Tech 2 handheld scanner is around £3-400, but on eBay you can get a USB interface for about £25 (not to be confused with the basic ODB2 scanners for about a tenner - I have one of those already).
Do/how do these work, do they offer the same features etc?

anonymous-user

84 months

Wednesday 10th September 2014
quotequote all
The issue with all the "ebay" or other aftermarket OBD toolsets is that the manufacturers are only legally obliged to make their OBD data "standard". All "other" data interface will be unique/propriety to each manufacturer and hence much more difficult to access.

In all cases, the protocols and hardware used is generally standardised (UDS ISO1585, J1939 etc) but the precise commands and routine to access manufacturer specific modules and functions is not generally available in the "open"

Because of this, the generic Scan tools have no issue doing the basic OBD stuff, like reading Diagnostic codes, or returning basic data (all mandated by the OBD legislation) but will generally not work for any of the manufacturer specific stuff like module reprogramming or "coding" etc


DrDoofenshmirtz

Original Poster:

16,952 posts

230 months

Wednesday 10th September 2014
quotequote all
Max_Torque said:
The issue with all the "ebay" or other aftermarket OBD toolsets is that the manufacturers are only legally obliged to make their OBD data "standard". All "other" data interface will be unique/propriety to each manufacturer and hence much more difficult to access.

In all cases, the protocols and hardware used is generally standardised (UDS ISO1585, J1939 etc) but the precise commands and routine to access manufacturer specific modules and functions is not generally available in the "open"

Because of this, the generic Scan tools have no issue doing the basic OBD stuff, like reading Diagnostic codes, or returning basic data (all mandated by the OBD legislation) but will generally not work for any of the manufacturer specific stuff like module reprogramming or "coding" etc
Yeah - that's what I thought.