BMW OBDII codes and connectors

"YKhan" > wrote in message
...
On Apr 11, 3:09 pm, (Scott Dorsey) wrote:
> I believe that the error codes for the other computer subsystems are
> available through the OBD II port, but they are not readable by the
> cheap scanners.

Okay, assume I'm using a PC with OBDII software rather than a
standalone scanner. My assumption is that all codes are of the same
format, whether they are the standard or proprietary codes on OBDII,
so the PC software should be able to at least display the code number
even if it doesn't understand what it's about.

<JS>
The Website for your tool should have all of the possible codes. The
readout -- if it is worth anything at all -- should give the code and a
textual indication of what the code means. If the code is a P1nnn code, the
textual readout should tell you the manufacturer specifics, that is the code
will be displayed, and the textual indication of the code should say FORD
for the Ford meaning, GM for the GM meaning, BMW for the BMW meaning, and so
on. ANY P1,,, code should be follwed up by the mfg, that uses that code for
that meaning. It does no good to give a P1nnn code without the mfg
designation, because the meaning of a code in a Ford platform and the same
code in a BMW platform will be entirely different. The machine will not know
that it is plugged into a Ford or a BMW, so the text that is displayed must
display for all makers. I assume you have to scroll through multiple screen
of data to find the information that affects you.

</JS>



> In addition there are diagnostic modes available on the ports which allow
> you to plug in a scanning device and look at realtime plots of all the
> engine sensor inputs and outputs. This is an absolute lifesaver and a
> whole lot easier than trying to guess what's happening from an error
> message that says a sensor is out of range, but not what direction it's
> out of range, and with no information about the other sensors that aren't
> out of range.

I believe the real-time sensor plots are available on all cars, it's
not just a BMW feature, right? So it would be a standard OBDII
feature, rather than proprietary.

<JS>
If you can plug your PC into your car and get real time data, then you can
get real time data from the BMW. OBD II is a universal convention. Nothing
about it is proprietary, except for some of the specific codes that might
come out.

</JS>



> The problem is that these cars are computer networks on wheels... there is
> an outrageous amount of automation and a huge number of individual
> communicating systems, and when _anything_ fails you will be completely
> at a loss without information from the responsible system. The cheap
> scanning tool isn't a bad thing to have, but it's not enough to diagnose
> the vast majority of problems you'll encounter.
>
> Now... the good news is that if it's a 2000 model, it's not anywhere near
> as crazy as a late model BMW. And if it has a manual transmission, you
> are that much better off because the transmission control system is one
> of the more nightmarish diagnostic headaches. But this is a car that has
> microprocessors controlling the interior lights... It's not like the 2002
> any more, sadly....

Yeah, actually my friend wanted a tool that could even tell him if the
windows were opened or closed. Not that he really needs that, but he
does like to be able to have full capabilities. Will these
proprietary, non-critical codes come through the standard under-dash
port?



<JS>
I seriously doubt that OBD II data will tell you if the windows are open.
Having said that, I had a '95 Ford Bronco, and I bought an OBD I scan tool
for it, and it told me stuff like the current state of the radio and AC
system. I don't recall if it reported the state of the windows, and I had to
remember to turn the radio and AC off so the scanner did not make the light
blink all day reporting those systems being on.


</JS>