Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Technology

Proposed Law To Open Code ... In Cars 398

SEWilco writes: "A Minneapolis Star Tribune story points out that small repair shops say they lose money because they don't have access to car computer codes. These 'codes' are the diagnostic messages used by onboard computers to report problems and perform tests. Older designs only required a jumper wire to make a test light flash code patterns, certain dashboard actions to display codes, or a cheap display terminal from a parts store. Now the interfaces and code meanings are more complex and undocumented, so only auto dealer repair shops can easily find causes of some problems. U.S. Senate S.2617 and House H. R. 2735 would force auto manufacturers to share the codes. Sen. Wellstone says that manufacturers are acting like a cartel, blocking independent shops and car owners. But GM is being helpful."
This discussion has been archived. No new comments can be posted.

Proposed Law To Open Code ... In Cars

Comments Filter:
  • Finally an open source analogy your grandmother can understand
    • Finally an open source analogy your grandmother can understand

      Actually, I prefer to think of this as an analogy my redneck friends can understand. When talking to my grandmother I relate to cooking: secret recipes vs. sharing and modifying recipes with others. Giving people something to relate to is half the battle!
    • by Dwonis ( 52652 ) on Monday June 24, 2002 @10:23PM (#3760543)
      It's not really an open source issue, it's an issue of open protocols, which is far more important than open source.

      Closed source allows some companies to make money directly from the software they produce. If closed-source software producers can do this and still remain competitive, then good for them! BUT, it's only acceptable when they compete fairly in the market and if consumer choice is really there. In order for this to happen, we need open protocols.

      • It's not really an open source issue, it's an issue of open protocols, which is far more important than open source.

        So you're saying this is more akin to the SMB/CIFS issue... in which case I'd have to agree with you. Actually it seems very similar, especially if what some of the previous posters' comments are accurate; Honda only sells the manuals to their dealers/mechanics... but I'll bet you don't have to sign an NDA (yet) or some other restrictive contract limiting your ability to disseminate their proprietary information.
    • Finally an open source analogy your grandmother can understand

      Yeah, despite the fact that it's a ridiculous analogy. Analogies don't prove anything. They just make you more convinced of your beliefs, whether they're right or wrong.

      Don't you think the huge difference in proportion is relevant? When you buy a car, you do so with a 100% guarantee that the car will require service, and that service is a significant portion of the total cost of ownership of the car. The average consumer who buys an off-the-shelf software product (e.g. a game) will probably never need support. In the case of a more major purchase (e.g. an OS/Office suite), you get free updates off the web. The average consumer doesn't pay to have someone customize their OS for them. If they're technically challenged, they might pay someone to install it for them.

      -a
  • Karma Whoring: (Score:2, Informative)

    by bentini ( 161979 )
    CNN article on similar subject is here [cnn.com]. It's pretty good and interesting.

    Basically, they're leveraging their IP. I say good for them, but most people here will probably want to skewer them.

    People rarely think about this kind of thing before purchasing a car. Maybe they should.

    • Re:Karma Whoring: (Score:2, Insightful)

      by jethro200 ( 573288 )
      People rarely think about this kind of thing before purchasing a car. Maybe they should.

      Think about what? What are they supposed to do - buy a car without and onboard computer? or maybe buy a car from all those car companies who willingly make their codes available for anybody? or they could just not get those parts of their car fixed. this is pretty much out of the consumers hands, other than writing their congressperson to get the bill passed.

      • or maybe buy a car from all those car companies who willingly make their codes available for anybody?
        Yeah, buy American! The article mentions that GM is the best, when it comes to sharing the codes. A previous poster said he works as a mechanic and codes from the big 3 (GM, Ford, & Chrysler) were readily available.

        If the 3 of the largest auto makers in the world release the codes, why can't the others? It obviously isn't helping their business grow.
        • I really don't think the car market is based on whether or not the code for the fuel-injection chips is open or not.

          People buy cars for the look, the comfort, the convenience, the capacity, or the performance. When was the last time you heard anyone ask if the diagnostic computer code was available?

          The car market shrinks and grows based on the economy. As the economy thrives, then the big ticket cars become popular. When it shrinks, buyers get frugal and buy lower-priced cars.
  • Or being able to prevent an accident?
    Hmmmmmm...
  • I'm an optimistic (Score:2, Insightful)

    by boa13 ( 548222 )
    Step 1: Wait for this law to be voted and put into effect.
    Step 2: Start pushing for a law that mandates opening code... everywhere. Say that it prevents small independant consultants from repairing Microsoft ware.
    • You're comparing apples to oranges...

      Giving out the source would be like giving out the engine design specs. Ford and GM go through a lot of R&D and don't want to have to give out every piece of info about the cas they build and they shouldn't have to, Microsoft goes through a lot of R&D and also shouldn't have to give out their "engine source."

      Giving out the API would be good though...
  • I own an Acura RSX.. (Score:2, Interesting)

    by windex ( 92715 )
    It has alot of tweakable settings, none of which I can preform myself but if I give the kid who works for the big bad car dealer $10 he'll do whatever I want.

    Next car I buy, I will demand open specifications for, I'm getting tired of paying the kid to do what should have come with the car that I own.

    I'm sure as fuck not signing a EULA when I buy my car not to violate its software.
    • The software that my company puts in its products for the OEM is given to them for "free". I've approached my managers about opening up the source code, but they are fearful that it could give our competitors an advantage over them and open them up for lawsuits if a bug was found.

      Any ideas on how to answer these concerns?

  • by tgd ( 2822 ) on Monday June 24, 2002 @10:06PM (#3760474)
    Its funny, because its sort of related to the Ask Slashdot question about car performance tuning software a week ago. All these computerized systems have left cars incredibly complex to tune, repair, or modify.

    Thankfully for some vehicle types, the enthusiast market has reverse engineered a lot of these protocols and codes. I've driven two different Audi's for the last three years, and spent an ungodly large amount of time and money tweaking and otherwise customizing them. Our enthusiast community has software like VAG-COM [ross-tech.com] which can provide a suprisingly large amount of capability for Volkswagen, Audi's and other VAG-group cars. But now Audi (and presumably Volkswagen) is changing their protocols yet again, keeping things proprietary and secret. Thankfully, I'm sure they'll be reverse engineered yet again.

    Even with the capabilities the software has, we're still faced with having very good documentation for what most "sensor" blocks are, but essentially none for what the "settings" blocks are. I can read anything I want, but without insider VAG knowledge, I can't recode a damn thing.

    Amazingly through trial and error, people have even figured out how to reprogram basic functionality on their cars, like how the automatic transmissions shift.

    I would love to see this law passed, but it doesn't help things much if its just emissions codes that have to be released.
    • VAG-COM, My girl friend got that once. Some Cephlexin cleared it right up.
  • Hack Your Car (Score:4, Informative)

    by Kargan ( 250092 ) on Monday June 24, 2002 @10:10PM (#3760486) Homepage
    This article [pcmag.com] here, even though it seems to be written for the person wanting to do their own maintenance, seems like it would have some handy information for small repair shops, as well.
    It basically points out a few new programs and an physical interface that is designed for use with a laptop that can interpret many diagnostic codes. Just install the software, plug in your car and off you go.
  • It ougghta be a law! (Score:4, Interesting)

    by Nogami_Saeko ( 466595 ) on Monday June 24, 2002 @10:14PM (#3760501)
    It would make car repairs so much easier... Which is exactly WHY the dealerships and manufacturers don't want any part of it. When your car starts breaking down a lot you either bring it to the dealership who has the only tool out to read the diagnostic info (dealership wins), or you buy a new car (SOME manufacturer wins).

    I mean, if the manufacturers wanted to, it would be easy enough to put a text readout in the dashboard that would say "engine airflow sensor failure" or something similar. Even an error code that you could look up in the manual would be decent.

    When I buy a new car, part of my shopping checklist will be to see if I can get a (most likely) 3rd party diagnostic plugin tool.

    If more buyers demand onboard diagnostics to be usable by owners without expensive dealership computers, it might start forcing manufacturers to make the information easily accessible.

    Reminds me of Harry Harrison's "Deathworld" trilogy (part 2). Give the buyers of the vehicles (in that case, steam wagons), the bare minimum of information to make servicing/repairing them impossible. At least the manufacturers aren't sealing the hoods and putting mustard gas inside to prevent repairs (yet).
    • by lrichardson ( 220639 ) on Monday June 24, 2002 @10:33PM (#3760576) Homepage
      "I mean, if the manufacturers wanted to, it would be easy enough to put a text readout in the dashboard that would say "engine airflow sensor failure" or something similar. Even an error code that you could look up in the manual would be decent."

      Actually, some cars have this. Got a Malibu ... turn the key slightly differently on start up, and watch the dashboard lights, then cross reference that with the manual (Chilton's, IIRC, not the manufacturers). Yeah, I'd love to have it display "Ignition coil #3 is f$cked", rather than what amounts to a binary display, but, then again, it keeps casual tinkerers out from under the hood ... and, IMHO, there's a whole lot more stuff now (compared to a decade back) that is not user servicable.

      The other sad thing is that computer diagnostics are replacing brains. Take the alternator ... 99% of the time, it's the diode pack. But garages love to go the long route ... which involves more parts, more time, and thus more money. One car I've looked at was quite clear on the error message (Dead battery and/or bad ground). Well, at least it had the right system (electrical), but it took a pair of 25 cent brushes (in the alternator) to fix it.

      Keeping the error codes secret also hides another problem ... a good percentage of the time, the error message is just plain wrong!

      • I'm not wanting to start a fight, but what exactly on newer cars isn't user serviceable? Other than the computer (buy a new one, don't even bother to repair 75% of the time) etc...?

        Granted, for larger work, I have the work done on my 95 chevy by the dealer. But I assure you, with the right amount of time, I can do anything the certified dealer technicians can.
  • Please note (Score:3, Informative)

    by MisterBlister ( 539957 ) on Monday June 24, 2002 @10:14PM (#3760502) Homepage
    They are talking about what amounts to ERROR CODES here. Not SOURCE CODE. Mechanics want to know what certain error messages mean, they don't want the fucking source code. How many mechanics are going to fix bugs in a RTOS car? And if they had access would you even want to drive your car knowing that "Big Joe" from down at Jiffy Lube reworked some of the brake logic?

    Everyone saying this is some sort of victory for Open Source is an illiterate moron, or didn't read the article.

    • Not an illiterate moron; just hoping that for once the confusion can work *FOR* us. keeping information proprietary is evil, even deception lies and confusion are good and just weapons against any who would withold information from anyone else.
    • Re:Please note (Score:3, Insightful)

      by TheFrood ( 163934 )
      They are talking about what amounts to ERROR CODES here. Not SOURCE CODE. Mechanics want to know what certain error messages mean, they don't want the fucking source code. How many mechanics are going to fix bugs in a RTOS car? And if they had access would you even want to drive your car knowing that "Big Joe" from down at Jiffy Lube reworked some of the brake logic?

      Everyone saying this is some sort of victory for Open Source is an illiterate moron, or didn't read the article.


      It's not a victory for Open Source per se, but it's a similar issue. It's the idea of openness versus closedness. Does the consumer benefit more if the protocols for talking to car computers are kept closed so that only the manufacturer can perform repairs? Or is the consumer better off if his car's computer has open protocols that allow any competent mechanic to diagnose and repair the car?

      There's a very direct parallel to the open-source-vs-proprietary-software debate. If this issue gets a lot of publicity, it'll make more people think about then open-versus-closed issue. That will make it easier to explain the benefits of open source to non-technical people.

      Wasn't it Bob Young who asked "Would you buy a car with the hood welded shut?"

      TheFrood
    • Re:Please note (Score:3, Insightful)

      by tswinzig ( 210999 )
      And if they had access would you even want to drive your car knowing that "Big Joe" from down at Jiffy Lube reworked some of the brake logic?

      That's insulting to smart automotive technicians everywhere, and there are plenty [iatn.net].

      It's like saying all programmers are dumb, just because there are some dumb programmers in the world.
      • Re:Please note (Score:3, Insightful)

        by Paul Komarek ( 794 )
        Not to excuse the other guy, but I expect the real issue is whether you want to drive a car run by source code that hasn't been *thoroughly* tested. I can't be sure that the auto manufacturers *thoroughly* test their code, either. However, the manufacturer has more time between writing the code and releasing it than the mechanic did.

        On the other hand if auto manufacturers were run the same way software manufacturers seem to be, I'd be less confident that any serious testing had been done at all. =-)

        -Paul komarek
        • Not to excuse the other guy, but I expect the real issue is whether you want to drive a car run by source code that hasn't been *thoroughly* tested. I can't be sure that the auto manufacturers *thoroughly* test their code, either. However, the manufacturer has more time between writing the code and releasing it than the mechanic did.

          Every serious car enthusiest that I know already does so, in the guise of performance enhancing EPROM's. They get chips that mod their fuel injection ratios, throttle points, and even automatic transmission settings. While this is not really code, more data tables to feed the code, incorrect values can still have the same effect as broken code.
          • To prevent confusion, by "*thoroughly* test" I would like to mean drive 1,000,000 miles in mixed city/highway conditions and a variety of weather, coupled with synthetic testing for extremes and corner-cases. That said, I probably have to live with something like testing 100 cars for 10,000 miles, at least one or two of which had special testing done. Even then I might be pressing my luck.

            Not to disparage the enthusiast, but it seems very likely they have fewer than 100 cars with the same computer. =-)

            -Paul Komarek
          • A second response: but you have a good point -- if they're using the same mod chips that other enthusiasts are using, then you might have more than 100 cars driving 10,000 miles. That said, you might (or might not =-) lack the systematic synthetic tests like crash tests.

            -Paul Komarek
            • Well for edge cases I can almost guarentee that the enthusiests test them a lot more than the manufacturers. The enthusiest market tends to wring 110% performance out of their cars and if it doesn't break in their use then it is unlikely to break for "normal" people.
      • Would you even want to drive your car knowing that "CowboyNeal" over at VA/Linux had been tinkering with your airbags? He wasn't making the point that "Big Joe" was unintelligent, only that he most likely wasn't qualified to be rewriting code for your car's braking system.
  • ODB-II (Score:4, Informative)

    by thesupraman ( 179040 ) on Monday June 24, 2002 @10:17PM (#3760510)
    Most manufacturers (well, certainly most japanese ones, and I'm 99% certain all US..) have used ODB-II from 1996 onwards to allow a standardised interface to their diagnostic (and often tuning..) information. This is a standardised interface, and does exactly what is being requested here.

    You can buy standard ODB-II scanners, or PC interface boards. You can read and write data values in real time, it is a great system.

    Of course, it is only manditory in some US locations, and manufacturers are free to make non-ODB models for other markets. More pressure for them to all support this would be a good thing.

    The biggest problem is that 90+% of 'normal' mechanics out there seem incapable of interpreting the complexities of modern fuel injection systems (I've helped design some, and even I find them hard to understand at times), more information does not always fix that problem! The number of times 'they' (your normal mechanic) fall back to a mode of just replacing bits at random to 'fix' a problem is high.
    • I think you mean OBD-II. It is an emissions requirement for all 1996 and newer autos and light trucks sold in the US. It largely has to do with ensuring that the emissions controls of the car (O2 sensor, cat, etc) are working properly. Problem is, it is possible for a non-OEM to make a part that, while it doesn't bugger up the emissions, it does bugger up OBD-II stuff, making the car think there is a problem (when it comes to emissions, running better than it should is just as bad as running not as well).
    • It could be ODB-II. I haven't looked that much into car stuff in a while.
    • The biggest problem is that 90+% of 'normal' mechanics out there seem incapable of interpreting the complexities of modern fuel injection systems (I've helped design some, and even I find them hard to understand at times), more information does not always fix that problem! The number of times 'they' (your normal mechanic) fall back to a mode of just replacing bits at random to 'fix' a problem is high.

      Hey I can do that... No, what they do is decide that since they don't know what the error codes mean, it must be a problem with the computer. "Oh, your brakes are pulsing? Hmm, must be the computer, you know that controls the antilock brakes, don't you?" Or, "your headlights don't work? Must be the computer..."

      Ok, I'm exaggerating (how the f* DO you spell that??). But you know what? It doesn't bother me any more. I've got my pimp-ass '79 Caddy Coupe Deville, w/ 7.0L V8. Sure I get ~10mpg, but it'll get up and go. Talk about your sleeper :) Plus, it's pimp, did I mention that???

      Memphis, Making Easy Money Pimpin Hoes In Style :)
    • ODB? [tripod.com] yeah.

      "because Biggie done do some of that shit too"

  • This would be great! (Score:5, Interesting)

    by MsWillow ( 17812 ) on Monday June 24, 2002 @10:21PM (#3760533) Homepage Journal
    Back when I worked for Sun Electric (before they got bought by Snap-On Tools), one of the hardest parts of making diagnostic disks for the newer cars was getting access to the codes. Information about what the codes mean, and how to get them, are "trade secrets" jealously guarded by the big automotive manufacturers, so they can provide *their* repair facilities with the stuff they need to do the work, thus effectively gauranteeing them a captive market.

    We'd eventually get copies of the specs, by having some employee schmooze the people at the auto makers, and they'd conveniently leave the codes on their desks, and step out for a loooooong lunch ... while these "confidential" documents were copied. We ran a few years behind - not that it mattered much to Sun, because nobody takes a new, still-under-warranty car to Joe's Auto Repair & Bait Shop. Our customers got the cars after they went out of warranty, and by then we always had the codes, and hardware to allow them to be read.

    It'd be a whole lot less sleazy, though, if the car makers had to release the codes, and how to get them. I do see, however, that this could cause problems, as many of the datastreams are bi-directional, allowing you to change things while the engine is running, potentially causing a malfunction. I wonder if the lawmakers have considered that?

    • This is interesting, because it points out a difference between engineering and management culture. If the management level knew how much informal cooperation goes on between their engineers and those working for other companies, they'd probably have a fit and issue a stack of policies to limit this.
  • Something Similar... (Score:5, Informative)

    by dmadole ( 528015 ) on Monday June 24, 2002 @10:32PM (#3760573)

    I recently ran into something somewhat similar. I have an older Acura Legend that has had a couple of nagging problems I've been trying to track down. First is a ticking sound from somewhere within the mass of emissions-control components. The other was an occasional failure of the air conditioning to cool.

    Anyway, I was doing some searching on Google [google.com] and Google Groups [google.com], trying to see if someone had been down either of these paths before. I ended up, through an Acura enthusiasts site, at Alldata [alldata.com], a mechanics' and do-it-yourself'ers online technical reference subscription site.

    Alldata had a list of Technical Service Belletins (TSBs) for my car -- these are notices sent from the manufacturer to dealers notifying them of, let's say "anomalies", in their product to be aware of. Sure enough, one was titled "BUZZING FROM EMISSIONS CONTROL BOX" and another was titled "A/C INTERMITTENTLY BLOWS WARM AIR". Jackpot!

    All I had to do now was subscribe to Alldata [alldata.com] for a (relatively) measly $25 a year to read the full text of the TSB. But wait! It turns out that of the world's car companies, Honda (who makes Acuras) and BMW (you know what they make) do not allow their TSBs to be distributed to the owners of their products.

    I called Acura's toll-free number and complained, and sure enough, they said they only provide and authorize distribution of TSBs to dealers. Seems Honda likes to keep secret what they know is wrong with their cars, giving their dealers an advantage and making owners and independent mechanics suffer along rediscovering what's wrong with Honda's shoddy products.

    Anyway, fortunately, I discovered an excellent service, Taylor Automotive Tech-Line [4door.com] which is a kind of a pay-per-incident tech support for mechanics and others. A simple web form and $20 later, and they emailed me TIFFs of the "secret" TSBs. Both of which were exactly what was wrong with my car!

    Turns out the air conditioning problem was caused by a circuit board chock full of cold solder joints that had cracked. Ten minutes with a soldering iron and fresh solder corrected that manufacturing defect. The clicking sound was diagnosed in less than five minutes with the help of the TSB and fixed by replacing a $59 chunk of plastic (a "Constant Vacuum Control Valve").

    Taylor Auto Tech's motto, by the way, is "We Fill In The Cracks On The Information Highway". Thankfully, someone is.

  • Codes (Score:5, Interesting)

    by mrycar ( 578010 ) <mrycar@g[ ]l.com ['mai' in gap]> on Monday June 24, 2002 @10:34PM (#3760578) Homepage Journal
    This is interesting. As a co-owner of a small independant garage that primarily works on GM, Ford, and Chrysler, I never had difficuly in obtaining error codes and how to pull them. Not only do the manufacturers provided manuals, but so do the aftermarket companies. Even getting a quicky codelist from the dealerships have never been difficult.

    Now in the beginning of ECM's, all the sensors had different names, but the SAE has been working hard at even removing these obstacles. Also the auto industry is naturally working at producing standard error codes. Todays mechanics owe no loyatly to a dealership or brand (not a bad thing) Its much easier and cheaper if when another dealership or garage picks up a skilled mechanic they don't need to retrain them on that brands codes.

    The automotive manufacturers know this and are migrating to common codes on their own. No need for the government to come in and add an additional expense to a process that is already happening.

    What is happening is the liability of working on a car is becoming too expensive for small independant garages. This will be the death of mom and pop shops before nonstandard ecm codes are.

    • This is interesting. As a co-owner of a small independant garage that primarily works on GM, Ford, and Chrysler, I never had difficuly in obtaining error codes and how to pull them. Not only do the manufacturers provided manuals, but so do the aftermarket companies.
      The article mentions that European manufacturers aren't as open with their proprietary codes, with the specific example of an air-bag light on a BMW. The owner brought it in to a local garage to get it fixed, but was refered to a dealer as the codes aren't available. He had to drive 70 miles to the nearest BMW dealership.

      My friend had a similar problem: the idiot light (service engine) was on, so he went to a mechanic to have a look at it, who found nothing wrong. He then talked to a dealer that said it automatically comes on at 60,000 miles, and for $60 they would give it a tune-up & the light would go out. Instead, my friend just put black electrical tape over the light & ignored it.
  • Wouldn't the equivalent of forcing them to open the code be to force them to hand over the patents and specifications on their assembly equipment?
    • Um, by definition of Patent, if their assembly equipment is patented, then it is open. (of course the fact that it is patented means that they get to charge other people using that same assembly equipment royalties...)

      -Rusty
  • by cr0sh ( 43134 ) on Monday June 24, 2002 @10:38PM (#3760594) Homepage
    Here [asashop.org] is an article about it.

    And you think it is bad now...

    I have very little doubt that as the technology matures, they will be able to build a car that ONLY runs on "dealer gas", which has certain molecular marker "tags" in the gasoline to identify it, custom sensors (similar to that used for DNA analysis, only MUCH faster) in the fuel lines, etc hooked up to the computer. When I mean "dealer gas", though, it will probably be a "cooperative" agreement between a gas company and the manufacturer - or maybe it will be something where all gas will work, but a "certain" gas will work "best" - literally.
  • Everybody does it (Score:3, Insightful)

    by Goonie ( 8651 ) <robert.merkel@b[ ... g ['ena' in gap]> on Monday June 24, 2002 @10:40PM (#3760602) Homepage
    Virtually everybody that makes big, complex machinery that needs periodic repair tries to obfuscate things so that a) you have to use their spare parts, and b) you have to use their technicians to do it.

    Photocopier makers used to be notorious for this sort of thing (they still are, it's just that all new photocopiers are now laser printers :) ).

  • by Em Emalb ( 452530 ) <ememalb AT gmail DOT com> on Monday June 24, 2002 @10:42PM (#3760607) Homepage Journal
    Apparently all mechanics that work on cars are named Joe.

    In a controversial move today, Slashdot.org opened a new can of worms with their posting of open source the error codes message. Joe's everywhere are in shock at finding out that they indeed missed their calling.

    From Joe C in Paduka, Ky.: "When I found out I was supposed to be working in automotive repairs, I completely was flabergasted. I have always felt like I was missing something in my life, this can explain why. Thanks /.!"

    From Joe E. Muntzenburger in Lake Okeechobee, FL.: "Man, when they told me I was supposed to be "Big Joe" down at my local auto-shop, I was stunned. I mean, being CEO of a large paper mill is great, but it can't compare to sweating underneath the hood of a car I don't understand!"

    Mods: If you don't get it, then you haven't been reading the comments.


  • ...I had a brake problem for years, every couple of days to weeks, the computer would bitch about something wrong with the brakes (brake warning light). All the places I took the truck to basically kept saying, "We can't do anything because we can't read the computer codes." So, I kept having to take the truck to the GM dealer and pay their premium prices to "fix" the truck.

    1 set of pads and disks replaced and cleaned, 2 master cylinders, a brake computer, and a dump valve later, after bitching relentlessly with the dealer about the problem, the light stopped coming on, yet the problems with the brakes continued. The truck liked to drift to the left or right when braking, sometimes hard. I suspected they cut the line to the warning light somewhere.

    After taking the truck in for inspection at another place that is reputed as trustworthy, they replaced my brake lines (the only thing the dealer hadn't) saying that they where old and that the drifting was a sure sign they where wearing out. Problem fixed. Over a thousand dollers to fix a $50 problem thanks to GM.

  • I've got a 1987 Nissan 300ZX Turbo (modified a bit), and before than a 1989 240SX. It is, and has been common for me to diagnose my "sensor" or "maintanance required" by sticking a wire in a couple holes and counting dashboard light flashes. On all of my pre-1990 cars I have ever had, I have taken the ability to do this for granted. It has probably saved me hundreds of dollars over the years.

    Never crossed my mind the the flash codes, or the "stick the wire in the proper holes" reader were tradesecret information, and difficult to access. This almost makes me want to figure out how to read the codes on my 97 Acura to see if they screwed me.

    -Pete
  • by tang ( 179356 ) on Monday June 24, 2002 @10:54PM (#3760636)
    I work as a mechanic full time right now... and I worked as a technician for the past 4 years while I went to school (CS major working as a mechanic, go figure). Anyway, I've never had a problem with this mysterious hidden code problem. It's pretty simple, I use a handheld diagnostic scanner (Genisys scanner, it runs a Lynx realtime linux, has usb ports, pcmcia ports, ethernet, large color screen, pretty sweet)
    it plugs into ALL cars made after 1996 (when the standard for OBDII came out) and most domestic cars with computers made before then. It tells me what code (or codes) have been set, and the data from the time it was set (RPM , engine temp, TPC value etc).
    I then take the code, and usually it will say something along the lines of "PO0047 OXY Sensor Bank 2" (I made that code up, but it is very close to something which would actually occur)
    Now, that tells me its an oxygen sensor in bank 2, no problem.
    It seems to me all these "independent shops" just dont have the proper equipment(sidenote: I work at an independent shop). I have NEVER had a car give me a code that was "secret" and that I didnt have access to. Ofcourse, We have the proper equipment (the scanner was $6,000) and we also have several DVDS which , for each code in the computer give you a flow chart of what to check that could set that code.

    It seems that the backwoods shops that people go to because they are cheap, dont have that equipment. Which is why noone understands that when we scan your computer for codes, we charge $55 just to check what the codes are for, not even to fix them.
    So remember, when you get your car fixed and it costs a lot for something you think must be simple, remember that the mechanic is probably still paying for thousands of dollars in tools he needs for his job.
    That was a long rant,but some of it was ontopic I guess.
    • I personally think I shouldn't have to pay $55 for this... because I think you shouldn't have to pay $6000 for that dumb scanner in the first place (times however many of them you have.) The problem is that mechanics are getting ripped off because this equipment they use is so rare.

      How hard would it be to connect one of these $6000 machines to a PC with some kind of cable connect? You could have the PC generate every possible code sequence, over the line, then watch the results on the scanner and renter the results into the PC. Viola, the database is yours. Now reverse that connector so the PC can detect the codes, and for the price of whatever cable and port you need to hook up, the (hopefully free) cost of a 486, and a little programming for your UI, you've got yourself an equivalent scanner. And then you can start charging me what that service is actually worth (next to nothing) and make bank because people will actually start having the money to fix thier car everytime the mystery "check engine" light comes on.
      • shouldn't have to pay $6000 for that dumb scanner

        We're not talking about a very high demand item here. The high price is probably due more to the lack of demand for a very durable good.

        hard would it be to connect one of these $6000 machines to a PC

        Not very. But how much time do you lose working up that database? Somebody needs to be minding the garage.

        you can start charging me what that service is actually worth

        Well, how much the service is worth to you depends on how badly you need your car. While it may not cost the mechanic much after your "simple" process, YOU'RE still the one with the broken car. Sure, his job is easier, but you're failing to take into account the rest of the job, like labor, wear, insurance, tools, etc.

        None of that stuff is cheap.
      • http://www.obd-2.com/ [obd-2.com] is your answer. About $150 and you can interface with any of the 3 main OBD-II interfacing protocols. Downloadable updates. Error code sets for your manufacturer. Tons of information. And the author has a very impressive resume when it comes to automotive and computer diagnostic design!

        Mix this with a little bit of community-brainstorming on an automotive message board, and most car problems can be solved.Not having the tools to fix something is a whole other issue :) Software has a hard time transforming into a torque wrench!
    • Six grand for a machine that basically justs accepts and displays a short serial transfer of data? What a racket.
  • error codes (Score:2, Informative)

    by Butane Bob ( 517437 )
    Every time I plugged in my 96 Audi A4 Quattro, three or four undocumented codes would come up. One of these was due to a co-worker starting the car while it was in gear ( I was in the back seat, completely intoxicated after a lunchtime margarita fest.) I was lucky enough to know a mechanic who had _some_ of these codes in a database on a nice diagnostic computer. However, many codes were not listed at all, mostly non-critical or not a real error condition, and would not show up again when cleared. (these are the mystery codes) When I was a mechanic a few years ago working on Navistar Diesel truck engines controlled by the MC68HC11 microcontrollers (motorolla 68ks) all codes were documented and the engines could perform real-time checks of all the electronics. The ECU had to be plugged into a hand-held computer that would display all the engine's feedback in realtime on a 5X5 screen. I want one in my car, but that looks like its a few years down the road.
  • by MobyDisk ( 75490 ) on Monday June 24, 2002 @11:01PM (#3760655) Homepage

    This is what makes too many laws. There is already a solution in place, the citizens and representatives just need to use them:

    1. Most of the posts I see say that these codes are easy to obtain. If the codes for some manufacturer are hard to obtain, shops should not work on those cars. Or charge more. So customers will not buy them. That is how capitalism is supposed to work. Consumers and service shops just need to stand up for the good manufacturers.
    2. "Sen. Wellstone says that manufacturers are acting like a cartel, blocking independent shops and car owners." We already have laws against cartels. Use them.
    • Point 2, requires providing reasonable evidence that the manufacturers are acting as a cartel, not simply the accusation.

      I might point out that it requires some very strong evidence, not just the observation that they are behaving publicly as a cartel.

      If public behaviour were sufficent, you could sue the major oil companies. Ever notice how all their unrelated gas stations are adjusting their prices on the same day, always to within a couple of pennies of each other? That is cartel like behaviour. However because the managers of the various gas stations do not talk with each other, and come to an agreement ahead of time, providing each station with a schedule of when to adjust prices, and by how much, they are not defined as a cartel.

      There are other reasons for the price changes happening as they do. Reasons like the amount each station is paying for gasoline delivered. The fact that the manager of one station observes that the manager of another station has dropped that station's prices and drivers are going to that station now.

      Likewise for delership mechanics having "proprietary" information. That "fact" is not sufficient to take a collection of car companies to court for acting as a cartel. However it is very much cartel like behaviour.

      -Rusty
  • Let's count the FUD (Score:4, Interesting)

    by FearUncertaintyDoubt ( 578295 ) on Monday June 24, 2002 @11:04PM (#3760663)
    The dealers are waging a FUD war in order to cast the independent mechanics much in the same light as Microsoft would open-source:

    Fud #1:
    "From a business standpoint, it's diluting our franchise" to make the codes public, he said. "A franchise becomes meaningless."

    I'm not even sure what that means, but it sounds scary. We can't have meaningless franchises! The whole system will break down, and then who'll fix your car, huh?

    Fud #2:
    William Abraham, executive vice president of the Greater Metropolitan Automobile Dealers Association of Minnesota, said that manufacturers "want it to be repaired right the first time. . . . All things being equal, they'd rather have you repair them at a dealership because they know they can get the job done right."

    Translation: independent mechanics are scam artists who will leave your car in worse shape than they found it. We can't have them using our codes, that would be like endorsing them to ruin your car and rip you off. And you don't want that, do you? Never mind, of course, that dealer mechanics work on a pay system where the less time they spend fixing your car, the more money they make, and the least profitable jobs go to the worst mechanics. Now that's a system you can endorse!

    Fud #3:
    Lambert, of the car dealers association, said there is no evidence that independent repair shops are being driven out of business, and he said that consumers enjoy "a wealth of options." He said that no products are more regulated than automobiles, adding that manufacturers must be concerned with safety equipment, recalls and warranties.

    There's two in here. 1) These codes are hurting independents? Prove it! Sure pal, right after I prove global warming when Antartica becomes a beach resort. Stall long enough, and there won't be any independent mechanics around to raise a fuss. 2) We're regulated, so you can be sure the government is making sure the system is fair. Oh, please. See US vs. Microsoft.

    Fud #3:
    They have a right, I think, to restrict who has access to all of that technology," he said. "Otherwise, they're left with people they don't have any relationship with working on vehicles that they're still responsible for."

    Of course the manufacturers don't have a relationship with the independent mechanics -- the manufacturers deliberately refused to establish one to keep you away from them! If they started sharing the codes, then they would have a relationship, now wouldn't they? And you know what? I have a better relationship with my mechanic than with the dealer! But apparently that relationship isn't important (or maybe it is, that's why the dealers are trying to break it).

    Fud #3:
    "The old garage mechanic is gone," he said. "In fact, the term 'mechanic' is gone. They're called technicians now. These people have to be very intelligent people. They're working on computers, and it's a high-tech industry.

    Of course, the guy from the dealer association said that customers have lots of "options", and that there's no evidence the mechanics are in trouble. Now, having assuaged our concern for the little guy, this other dude says that they don't even exist anymore anyhow. Pay no attention to that shop that says "Main St. Auto Repair" down the block. He's just a gorilla in overalls that couldn't possibly understand how to read a number from a screen, and look it up in a book that says, "water pump is failing." That's way too sophistamacated for a dumb schmoe like that. Forget that he has twenty years of experience and the dealer guy is some kid fresh out of a technical school (see Unix admins vs. MSCEs).

    How many times have you heard someone ask, "when your Linux server breaks, who are you gonna call?"

    FUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFU DFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDF UDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUD FUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFUDFU

  • What? What? Huge companies attempting to limit competition so they can collect assured profits perpetually?

    Say it isn't so!
  • So now we have another RIAA/MPAA-like cartel. The dealers are the ones who want the codes kept secret (from everyone else but them). So the next time you buy a car, ask for the codes as part of the deal. If the dealer refuses, let him/her know that they lost a sale - there are plenty of brands to pick from. If possible wait until all the paperwork is prepared, then just before signing on the dotted line, act shocked to discover that essential repair information is being withheld from you (which means you will not really "own" the car, so you are being cheated). That will help drive home the point. Probably more so than returning a copy-protected CD. If enough people do this...

    If you don't see the problem with secret repair codes, would you buy a computer with diagnostic codes that were kept secret in order to force you to return it to the factory for repair at exorbitant rates?

  • It's the classic little vs big guy.

    The auto makers should share the codes for the same reason Microsoft should share the (internal) APIs: openness fosters fairness and competition, which is good for the consumer.

    Hopefully, someone will point this out to the congress-critters, and the analogy might finally turn on the light in their heads about software.
  • Cartels are good (Score:5, Insightful)

    by phriedom ( 561200 ) on Monday June 24, 2002 @11:42PM (#3760778)
    "The old garage mechanic is gone," he said. "In fact, the term 'mechanic' is gone. They're called technicians now. These people have to be very intelligent people. They're working on computers, and it's a high-tech industry. . . . How does the guy that's in a little town of a population of 500 people get educated about the electronics of a $30,000 new automobile?

    Could he be any more condescending?
  • It is interesting (Score:5, Insightful)

    by Edmund Blackadder ( 559735 ) on Monday June 24, 2002 @11:57PM (#3760819)
    It is interesting how senators are willing to help the little auto mechanic, from being locked out by the large manufacturer, but not the little pc software developer from being locked out by the large software developers.

    What is it? Is it because auto mechanics is an easier bussiness to understand? Are they better organized? Or is it because the small automechanic is an old institution.
    • Well, gee, that's simple.

      It's because there are *more* small town auto mechanics than small-town "software developers." More people use their services, and more people even tinker at home with their cars.

      I'd be willing to guess that the percentages of the relative populations (of computer users and car drivers) that do personal or semiprofessional maintenance is at least a few % in the car's favor.

  • Dirty Little Secret (Score:5, Interesting)

    by brad3378 ( 155304 ) on Tuesday June 25, 2002 @12:34AM (#3760895)
    Automakers make money by keeping this stuff secret. Why?

    Dealerships do two types of repairs:
    Customer Pay, and Warranty pay. As a way to protect consumers from questionable hourly billing, shops use a refrence book that tells them about how many hours a job will take. This book is how your estimate is determined (plus or minus whatever the service writer thinks they can get out of you)

    What you're not told is that customer pay jobs
    are often quoted TWICE the time alocated for warranty jobs. Very few mechanics like warranty jobs unless it's something that they have a really good shortcut around (i.e. A faster way to replace an engine than the shop manual shows)

    Since automakers tell the dealerships how much they will pay for warranty jobs, Dealerships tend to make up for it by overcharging for customer pay jobs (via padding the quoted labor times)

    So who gets screwed?
    Not the automakers...
    They sell more replacement parts when they can eliminate independant shops and
    aftermarket parts. Independant shops tend to buy more aftermarket parts than OEM parts.

    Not the Dealerships...
    The dealership mechanics don't like to give up their "gravy" jobs like brakes & transmission services to Independant shops because those gravy jobs are what help them compensate for warranty work. Dearership owners feel the same way. For a given week, if mechanic 1 can replace 10 customer pay transmissions, and mechanic 2 can replace the same number of warranty transmissions, Mechanic 1 just earned the dealership twice as much and without all the BS warranty paperwork.

    Independant shops get screwed.
    Common sense. They can't compete because automakers are trying everything they can to get customers to come to them for all their needs. Independant shops must then rely on oil changes & mufflers to make their money, and there's too much competition there because it doesn't involve as much training. There isn't nearly as much money to be made changing oil as there can be for drivability & electrical stuff. The little shops must do a lot more little tests that the Non-OBD2 codes provide. How can a little shop compete?

    Customers get screwed.
    Mainly because competition is eliminated.
    Don't expect to see any improvement either.
    CNN headline news has been reporting that there will be a shortage of about 200,000 mechanics by the year 2010. Expect to see dealerships take advantage of that and watch labor rates and times skyrocket.
  • EULA (Score:2, Funny)

    by ziegast ( 168305 )
    Perhaps one day our cars won't start until we break the shrink wrap that says we must agree to the End User License Agreement before using the car.

    It brings new meaning to the term "24-month lease".

    -ez
  • by stuffman64 ( 208233 ) <stuffman@[ ]il.com ['gma' in gap]> on Tuesday June 25, 2002 @12:47AM (#3760927)
    The problem here may not be just getting car manufacturers to divulge engine codes, but rather the maker of the ECU itself. For instance, Bosch [bosch.com] produces ECUs or other engine components for virtually every car maker. Last year, Bosch had over $23x10^9 in sales in the automotive sector alone. Since nearly all European manufacturers rely on the Motronic ECU [internetwork-bosch.com] for higher-end engine applications, I'm sure that many Engine Control and Error Codes are similar amongst many different models and manufacturers.

    I'm not entirely sure about whether or not the problem is the manufacturers' reluctance to supply codes. Perhaps they have a contract or something with the supplier of the ECUs to keep things hush-hush. Not only do the manufacturers make out by requiring service at their garage with their advanced tools, but the ECU supplier stays safe from the competition by not having all the details of their system easily divulged.
  • From OBDII.com [obdii.com] regarding the purchase of an OBD scanner:
    Not all scantools are equal. In fact, some aren't even close. As part of the OBDII standard, the US Environmental Protection Agency mandated that a basic set of emissions related readings be supported on all OBDII vehicles. The SAE specification J1979 defines these legislated parameters. Many low-end tools only support these emissions related readings, giving you access to only a dozen or so truly useful parameters. While these give you some basic vehicle information, they are just a small set of the vehicle information available through the OBDII port. When shopping for a scantool,
    be sure to find out if it supports just the legislated parameters or if it also includes the enhanced (sometimes called proprietary) diagnostics.
    It goes to show that auto manufacturers will only cooperate because of laws and regulations. They have no intentions of developing standards with their competitors (or in some cases, even within the divisions of their own company!). Just as some automotive companies made their own "enhanced" OBD-based diagnostics only for their own interest, they do the same with car parts. It's all finding a way for them (or their business partners) to make money. Sadly, these car companies fail to see that when they work together to develop a standard, they all benefit.
  • and I noticed a banner in the window that caught my eye.

    This [autozone.com] pretty much sums it all up. They offer FREE code retrieval.

    Back when I had a Jeep Wrangler, I bought a Haynes service manual that showed me what its codes were. I could easily obtain the error messages through a morse-code system.

    To see what the diagnostic computer felt was wrong, you turned the ignition key so that it went off/on/of/on/of/on. After the third and final "on," the check engine light would flash a certain number of times, which corresponded to a specific problem code.

    flash - flash - flash
    *pause*
    flaah - flash - flash

    ... that would mean 33. 33 stood for Air Conditioning, IIRC. That code would always come back since my Jeep didn't have an A/C unit plugged into the diagnostic box.

    Anyways... the Jeep was a '91. I miss it so much.

    *tear*
  • As always when this subject comes up, major props to Chrysler for making the codes easy to get [allpar.com]. At least, in the past. Looks like it's not so easy on newer models. (Must be the Daimler folks that are influencing it.) Too bad.
  • After reading the many messages regarding this topic. Here is a breakdown of information. There are many trouble codes which can be transmitted by the ALDL unit. Also, which most people did not discuss here is the serial data. This data is streaming information which contains information on fuel mixture, speed, and A/C information. The serial data can be read from the ALDL to your computer. Please visit this site for a simple hardware interface and some information on ALDL timings. http://www.techedge.com.au/vehicle/aldl8192/8192hw . tm There is tons of software out there. http://www.andywhittaker.com/ecu/ecu_software.htm Here is the best site on the ALDL(ECM) protocol. Check this site out........ http://www.ws6transam.org/ALDL.html I have a working interface board for my car computer. GPS, MP3, DVD and realtime (yeah right) automobile information from the ALDL unit. Enjoy..!!!!!!!
  • by juliao ( 219156 ) on Tuesday June 25, 2002 @04:43AM (#3761342) Homepage
    We seem to be missing the point here:

    This is NOT about cars, this is about software and about interchange formats!

    I hope this law makes it: this will be the grounds for asking for a law that forces Microsoft et al. to open their document format.

    Today, independent programmers cannot perform services for their customers because large software makers hide the specifications for document formats. This means that an independent programmer cannot properly access and service the customer's database/spreadsheet/file without specialized tools that he would be required to buy from the software maker. This, in fact, amounts to some degree of cartelization, in so far as only programmers "licensed" by the software maker have access to these tools, in what amounts to a cartel. By effectively preventing independent programmers from obtaining revenue from services, this situation limits choice for consumers and harms many independent programmers, who are sometimes the sole financial support for their family.

    This about it. This may be the way to go.

  • Two stories... (Score:4, Interesting)

    by wowbagger ( 69688 ) on Tuesday June 25, 2002 @08:14AM (#3761650) Homepage Journal
    I have three related stories about the absence of good diagnostic information, both showing WHY the auto manufacturers should open the protocols.

    First story. I was on vacation at the Grand Canyon's South rim, and the plan was to head to the North Rim. While that is only a few miles as the neutrino flies, it's about 150 miles by road. Furthurmore, the South Rim is pretty damn far from anything else. So, I get into my car (a 1997 Grand Marquis that had just had its 100kMile service) and lo and behold, the "Overdrive OFF" indicator starts flashing - a fault has been detected in the automatic transmission. Between having the "Check Engine" light come on or this, I'll pick the "Check Engine" light any day - you can troubleshoot an engine in the field, and generally most engine failures are "limp home" failures. A tranny failure tends to be a "walk home" moment.

    After poking, prodding, and checking, the light goes out. No explaination. So, we head off for the North Rim. 80 miles from anywhere the tranny goes "thump", the light flashes, and I curse. I managed to get to civilization, rent a UHaul truck and car trailer, and tow my car home. The dealership tells me the ATF had started to break down - they flushed it and changed the filter.

    Now, BECAUSE the South Rim is so far from anywhere, and because so many vehicles go there, there is a service shop there. Had the car been able to tell me "Clutch #2 slippage detected - possible fluid breakdown" I could have gone to the shop at the South Rim, had the fluid changed, and gone on without having my plans screwed up. Instead, I paid US$900 to tow my car home, and US$200 for the service.

    Second story: A couple of months later, I was going to work. I turned the key, and the "Check Engine" light stayed on. I checked the oil, listens for strange noises, and said "Emissions problem, not serious, call the dealer." Sure enough, the dealership read the codes, and said "Transient failure to pull a vacuum on the fuel tank vapor recovery - It's not showing now. Keep an eye on it. And damn guy, but according to this you've hit the rev limiter on this thing! How fast were you GOING?" Cost: $150. Had I been able to read the codes, I could have cleared it and kept an eye on it.

    Third story: A few weeks later, I was heading home, pulled out from a stop, and the tranny said "bang" and the "Overdrive OFF" indicator began to blink. It turns out the fluid had gone bad BECAUSE the #2 clutch had failed. US$1300 later, I have a rebuild in place. I took the car to a tranny shop nearby, rather than the dealership. As I was demonstrating the failure to the mechanic (at that point, it was still intermittant) I commented "Yeah, I know how hard it is to troubleshoot intermittant failures - I am a software engineer". His immediate response: "Maybe you could write some software for us that would work on all of these cars!"

    Conclusion: There is a clear harm to the consumer by the practices of the auto manufacturers, who together are acting in an anti-competitive and monopolistic fashion. I hope we CAN make them play nice (imagine a nice GTK front-end for diagnostics....)

On the eighth day, God created FORTRAN.

Working...