a strange move by the manufactures who adopted this.
wouldnt it be more profitable for them to just work with proprietry systems?
unlike in the choice of buying a computer, where compatibilty with internet and friends computers is a obvious requirement, the average alice and bob wont be put off by buying a car whose systems cant talk to any device other than the manufacturers
do you know how this got started?
The message from "beerismygas" contains these words:
It was forced upon them, initially by US legislation but I think they saw it coming in the EU and got on with it.
Indeed. There's lots of info about it on the 'net.
Some manufacturers tried to be smart and started using OBD here before it was required, only for the EU to come up with the incompatible EOBD II standard.
Chris
Don't forget there's extensions to OBD as well. Any OBD scanner can read the basic, legally-required stuff, but you often need a specific tool (VAG-COM for example) for more advanced settings.
Basically from the US where their anti-competition laws required any garage to be able to carry out emission related checks and repairs. They tend to have a different culture regarding some aspects of car servicing, expecting to have an oil service etc done at any garage rather than a main dealer - even with a new car. So a FMDSH means little there to most.
Oh yes, they tried and would have loved just that.
In USA ODB data is accessed for emissions testing. Ford and GM had different OBD data encoding methods. Instead of defining a standard they incorporated both and everyone else had to use them.
Trouble is that it's now mandatory it prevents true OBD being developed or use of new interfaces like USB.
-- Peter Hill Spamtrap reply domain as per NNTP-Posting-Host in header Can of worms - what every fisherman wants. Can of worms - what every PC owner gets!
The message from Peter Hill contains these words:
Is that really true? Would there be any reason why a firm shouldn't make OBD /and/ USB ports available?
anti-trust laws, surely?
it was an excellent move by the manufactures also there are things going on in the background research & development, using the onboard OBD to test emissions relating to the MOT. as they say watch this space.
true OBD - what is missing from OBD that could be cheaply added?
Given the lack of isolation in a USB port it doesn't seem the obvious thing to use anyway.
OBD = On Board Diagnostics.
Not too bothered by costs, I want a vehicle I can still maintain (this is ukrcm) when all the dealers have lost the "trained" staff and service manuals. Having to buy a remote unit and plug it in is hardly "on board". It should have an on board decoder and direct access to the relevant diagnostic and test pages in the service manual. Given the complexity of some current cars setup screens like the BMW M6 it wouldn't be that hard or cost that much. PDA's that run sat nav software could do it with a simple interface, so all other sat nav including built in ones should be able to as well.
One day when I get a round tuit and fit an in car PC.
OK it wouldn't benefit the average car owner at all.
-- Peter Hill Spamtrap reply domain as per NNTP-Posting-Host in header Can of worms - what every fisherman wants. Can of worms - what every PC owner gets!
Ethernet would seem to be a good match. Maybe even using a BNC connector for ruggedness.
Basically, exporting the value of every switch and sensor in the car, as fast as the ECU normally reads them.
I'd be tempted to mandate a web interface, over ethernet, with a full service manual on DVD/CD in PDF.
Most modern vehicles have a can-bus running to the EOBD socket, so that the manufacturer's own diagnostic kit can get data far faster and quicker than a standard EOBD reader. Out of the 16pins in an EOBD socket, under half are actually required under the EOBD standard, and the rest can be used as the car manufacturer sees fit.
MotorsForum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.