Can’t think of any cars that run MS Windows, but don’t assume that software can’t crash because it’s ROM-based.
My day job would be a hell of a lot less interesting if embedded devices running their OS from little bootable ROM chips didn’t crash; they do, just less often than fuller-featured operating systems.
On most cars, just look under the dash once you have the scanner and know what the end looks like. Easy to find… on my last two cars, it was located within 12 inches of where my knees would be when I was driving.
I think on one screwball Honda, they mounted the fool thing in the assembly beneath your elbow rest.
There’s a picture on THIS page, after the third paragraph of text:
http://www.nology.com/obd2connector.htm
It is not a stupid question, and is actually a really good idea. I am sure one day cars will head in that direction. The only obstacle I can think of would be the liability of errors.
As far as the software on cars, I would venture to say it could ‘crash’ in some way, if by crash you mean stop working.
Don’t know, but my owner’s manual on my '03 said not to do it because it can cause damage. I’d have to ask one of my mechanics about it.
If your car has a knock sensor (and I suspect that it does since you don’t hear pinging on gas that’s 5 octane points lower than it should be), it’ll tell the engine management computer to enrich the mixture and knock back the timing a bit.
You’ll notice somewhat sluggish acceleration and lower gas mileage, but no permanent damage from the occasional tank of wrong fuel.
Repeatedly doing this could lead to a snowball effect as the overly-rich fuel mixture leaves carbon deposits which increase compresssion and increase octane requirements–leading to more computer compensations to eliminate knock, which leads to more incomplete combustion which leads to more carbon.
:dubious: So out of the three or four hundred possible fault codes that ccould light up the service engine soon light, just how do you know that this one is the result of knock?
As a point of fact, the engine management computer detects knock all the time and is constantly adjusting the timing for the presence or absense of knock. This is a normal function.
Knock does not light the SES light on any car I have ever seen. Misfire yes, knock no.
Common Tater The system you are describing is available on a McLaren F1 IIRC they were a million a pop new. How much do you want to pay for your next Corolla? I beleive that OnStar can read fault codes when you push the button, but the car does not run a data stream to the dealer. Also be careful what you wish for, you just might get it. Here in California they are talking about the next gen of OBD (or the one after I forget) with a system that phones home when there is a problem. The issue is that it phones the State of California who then forces you to get the car fixed. Can you say big brother?
No car runs windows, as the computers on the cars have no graphical interface
OK, I waited until there was half a tank of 87 left and filled it up with 93, ran that out, and filled it up with more premium. Then I reset the check engine light, and it has stayed off since. So that, hopefully, is that! Thanks for the input.
How did you reset the indicator light?
Heh. You can actually run Windows without a GUI if you use the right Windows Embedded kit.
I think no car runs Windows because:
A) it’s not a real-time operating system
B) it has too many lines of code to be trusted in this embedded application
C) Ford doesn’t want to pay Microsoft $50 for the OS on every car they sell.
Unhooked the battery for five or ten minutes.
Why didn’t I think of that!