Quote:
Originally Posted by ImmortalZ On the contrary, they do. OBD2 was formulated so that it would be possible to monitor quite a lot more data than OBD1 ... |
True. What could be done in 2001 with a twisted pair of wires was much more than what one could do in 1984 with the same pair of wires. Also, an engine in 2001 had many more parameters that could be read than in 1984.
Quote:
Originally Posted by ImmortalZ car can be more thoroughly tested and calibrated for emissions compliance. |
So I can go to GM, Ford or Tata service center and they can give me an emission certificate just by connecting the diag tool over OBD2, or reduce the emissions coming out of my car?
The motive for making OBD2 mandatory was
a. making emissions related data available on call and
b. preventing an escape route for manufacturers by citing inability to measure or inability to present measurements.
The *reason* for introducing OBD2 was quite simple - faster / higher volume data communications - similar to USB replacing RS232 in computers.
Quote:
Originally Posted by Sprucegoose ... any functional advantages of OBD2 over OBD1. ... |
No functional advantages for an end-user of a car
Quote:
Originally Posted by Sprucegoose ... Or is it just a change of interface? ... |
Yes - faster communications at hardware level (serial comm), more data elements at the application layer
Quote:
Originally Posted by Sprucegoose ... Does it have a better processor? Higher resolution of the fuel map?... |
Not in the context. OBDx is not associated with a 'processor' or 'resolution of fuel map'. OBD is a set of specifications:
1. At the hardware level, it is just the definition of voltages, baud rates and signal duty cycles (there are 5 variants)
2. At the logical level (data content) it specifies what data must be made available by an ECU to a connected diagnostics equipment
OBD is only an interface definition/implementation, like an iPod interface. The processor power used on either side of the OBD2 interface, as well as what is done with the data generated/presented, is left to the interpretation of the manufacturers of the ECU and diagnostics equipment. For example, OBD does not specify/limit whether the data is to be used for closed loop parametric calibration, or for the simple vicarious pleasure of looking at various engine parameters presented on one's OBD-connected carputer (nothing wrong in doing that, right?).