Modern cars have MASSIVE digital displays, loads of computers systems monitoring every subsystem and internal diagnostics running to the OBDII ports.
Why the hell can’t we get diagnostic feeds on our console or infotainment center?
I’m not aware of any car manufacturers selling their own diagnostic ASICs, so it’s not an extra margin to squeeze afaik…
What gives? Any insight into this beyond the usual muh corporate profits conjecture?
They don’t want to maintain the software for it.
Also, they simply don’t want you to know. Especially if the whole setup is already a patchwork of sensors that barely work together in the first place. It might cause unnecessary questions, concerns or even liabilities.
A lot of it is useless anyway as long as the car is not broken, and if it is broken, the sensor might be broken too. It’s meant for diagnostics only.
They don’t want to maintain the software for it.
That’s fine, I just want the error codes displayed on the existing screens. No software necessary for that. Maybe a simple script at worst…
Also, they simply don’t want you to know.
They want it to be known, otherwise there wouldn’t be fail codes output to the OBDII port…
It’s meant for diagnostics only.
Yes. Why don’t they display diagnostics error codes on the existing displays? I’m fine with special display modes and “secret” menu options.
They want it to be known, otherwise there wouldn’t be fail codes output to the OBDII port…
That’s only there because it’s required by law since 1996, and only a small subset of those codes are actually standardized/required. Many of them are specific to vehicle manufacturer and are only known to the public due to leaked documentation.
Auto corporations don’t want you to easily have diagnostic info beyond the most basic things (tire pressure for example), they want you to bring it back to them. They don’t profit off you fixing it yourself.
Who is going to look at that stuff apart from technicians? Most users have no clue how the functionality of their vehicle is achieved and they don’t care.
For argument’s sake, let’s assume there is a userbase for this type of information. It would be possible to show diagnostic information like DTC or run DID routines from the dashboard but this is already possible from any cheap offboard tester, via a phone app or laptop.
The reality is that even if an OEM wanted to provide detailed diagnostic information, they don’t know it either because the information isn’t disclosed by their supply chain. Companies such as Bosch, who supply brake ECU, are extremely tight lipped about their intellectual property. When something goes wrong we use a special development version of the ECU to record the associated software variables during the fault and present that as evidence but we don’t have access to the source code.
Modern products are not designed to be repaired. They want us to continually buy new shit. Basically anything with software in it is an absolute nightmare to maintain. It makes me depressed just thinking about what a clusterfuck this landscape is.
Source: control system engineer for a large OEM.
I mean, I don’t think they’re taking about a full diagnostic. Just the code associated with a CEL.
It’d be nice if you could read the code from the dashboard or infotainment without digging out a code reader.
And it’d be even better if they had human readable descriptions for those codes, especially for OEM specific codes.
For most people, a CEL is all you really need. But sometimes and for some people, just telling them the problem would be super helpful.
For example, a loose gas cap is a CEL. Save people $100 at the mechanic if it was just like “check that your gas cap is tight”
When I’ve queried DTC using a cheap scan tool it’s usually resolved the important (as in emission relevant) DTC information text and most of the non engine stuff. In order to create a DTC there usually is a customer recognisable fault or an implication for emissions performance.
Many of the DTC are spurious and would only serve to confuse the user. As a system integrator, I’m personally responsible for creating tens of thousands of spurious DTC (in a vehicle population of ~100k) and I have to periodically report to management what has been done to reduce that number. The funny bit is when I found the root cause the management completely lost interest in solving the problem because, money 😂
I’m with you though, there’s no such thing as too much information. I want to know how my car is doing and fix the problems. Most people in the business do not care and our users are ignorant and apathetic, that’s why we can’t have nice things.
Hell cars have flash codes. I used to have a Holden commodore bridge out two pins in the obd connector and it would flash codes on the check engine light.
I’m sure cars can still achieve this easily enough.
But again useless information to the masses. I’m a crane technician and used to work for a large OEM and even we we pulled DTC codes down often they were little to no help
Who is going to look at that stuff apart from technicians?
Anyone who owns expensive equipment and is serious about true ownership including all possible maintenance and repairs. Hi, I’m the guy who would be looking at it if it was visible without shitty dongles or 5-figure ASICs.
Tell your employer they could have share prices doing numbers if they did the slightest bit of QOL improvements for anyone remotely like me.
There is a standard connector which existed before big screens landed in cars, the OBD2 connector. Dongles are cheap and you can read the output from your phone or computer. Some dongles support bluetooth. The connector is mandated in some markets and I guess that makes it less interesting to add a redundant interface inside of the car. It’s fun to try if you’re interested. Manufacturers can extend the error codes IIRC.
Tesla has a service mode on the display through which you can scan the car for faults, run a battery test, … It is password protected but the password is publicly available.
This is totally it. Car is already required to support OBDII, adding the ability to display diagnostic info to the screen costs more.
Usually I wouldn’t be that guy, but it’s OBD2, not ODB2.
OBD - On Board Diagnostics
Updated my comment to reflect this. Thanks for clearing out the confusion.
Once it may have been called ALDL instead. My '95 Commodore has one. Assembly Line Diagnostic Link. Same physical connector.
Bingo! You can get a BT adapter for $7 on eBay. Torque is the absolute killer app. I’m stunned something so complete and customizable is free, a few bucks for the full version. I suck at mechanics, but that has saved my butt a time or two.
If you own a car that was made in the last several decades, it has the OBDII connector under the steering wheel and openly accessible. You just plug the adapter in and connect to your phone. The adapter and app are every bit as important to me as a jack, lug wrench and tire pump. No one should be without for a measly $20.
My wife’s car occasionally throws an error that kills the cruise control. She can clear the error code while I’m driving! If you have ever had a mysterious check engine light, you can see exactly what it means.
Torque is ancient and not supported on current versions of Android.
I’ve been using Piston for a long time and I’ve been happy with it
Interesting fact. OBDII is a CARB requirement, so it’s tied to cars that must meet emissions standards. This is why Teslas don’t need to include one (ands it likely other manufacturers will stop including them in their electric models at some point as well). No emissions systems to check means no need for an OBDII port.
What I’ve learned with 15 years in the DIY repair sphere is that (obviously to me) the codes don’t tell you what’s at fault, only what’s not reading correctly and (to my surprise) the general public will just replace what the code says is off. A MAF code doesn’t tell you if it’s the sensor, the wiring, or the PCM.
While I’d certainly appreciate a simple code readout because I’m pretty knowledgeable about which are actually concerning this moment vs this year vs never, diagnosis typically takes more equipment and time. The cost and hassle of the reader is negligible in the repair. I use a Bluetooth dongle and Torque app to read all kinds of stats when diagnosing. An integrated interface would be convenient in some ways, but the portability of a phone/tablet probably has an equal amount of convenience once hard diag is needed
