Slashdot Mirror
Congress May Force Revealing of Car Computer Secrets
marksven writes "The Seattle Post-Intelligencer is reporting that there is a bill with 86 co-sponsors in the House to force automakers to open up their proprietary interfaces to car computers. Small car repair shops are more and more becoming locked out of the repair business because most late model cars can only be fixed by accessing their computers with codes that are secret."
had to take my car to the dealership this weekend because the shop down the block didn't know what the codes meant. Turns out it was a misaligned break caliper, cost me $225 at the dealership, would have been about $130 down the street.
You also handle the point that allowing users to get into the inner workings of their cars is not inherently evil.
I foresee some argument along the lines of "If we do this, <insert terrrorist/criminal organization here> will be able to soup-up the performance of their cars, and escape capture.
People working on their cars at low level resembles people working on Linux From Scratch, with the difference being that a core dump is only embarrassing, whereas an engine becoming several hundred flying sub-engines at the I95/I495 interchange, known with affection as 'the mixing bowl', could have substantial costs...
I hope the safety gestapo doesn't win the argument.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
If all this should have a reason, we would be the last to know.
I had a problem with my '99 cavalier; the engine would drop it's RPMs by several hundred every once in a while; almost, but not quite, enough to stall.
Took it in to the dealer, they said 'is the check engine light on?'
'Nope,' I replied, 'but here's what it's doing...'
'Sorry,' came the reply. 'If the check light's not on, there's no diagnostic codes for us to look up. We can't fix it unless we know what's wrong.'
Vintage computer games and RPG books available. Email me if you're interested.
I've been training as a mechanic and in most of our classes we use computer diagnostic tools as one step in verifying the problem.
First off, while the error codes are usually VERY accurate to what POTENTIAL problems are, they DON'T always tell you exactly what the problem is. Case in point: '96 GMC Yukon, the Service Engine light comes up every few days. Running the computer codes, it spits out a problem with an O2 sensor in the exhaust system, saying there is too much O2 in the exhaust. Now, this could be a number of things wrong...from problems with plugs and whires to bad gaskets, etc. that allow O2 leakage. However, the problem is nothing more than a crack in the weld on the exhaust pipe that leaks air into the exhaust system before the sensor, causing it to go off.
Secondly, last time I checked, I could buy manufacturer-specific computer equipment to diagnose cars from the manufacturers as a mechanic. Yes, the're about $600-700 a pop. (Snapon in turn sells a computer for that price and sells modules for each manufacturer for diagnosis).
Also, these performance maps and such you think aren't necessary...are. Why? because, during diagnosis, one of the things we look at is engine performance to verify that the engine isn't having trouble. The computer calculates and spits out performance data for the technician based on the information in the computer. No, we don't get to see all of the information on the chip directly, but for the sake of diagnosis, our tools have to be able to access it in the event that the car's performance is lagging behind what it should be and we have to diagnose it.
Thank you for our time.