The "normalization of inexplicability" is indeed infuriating. It has always been bad when it comes to computer software, and it's increasingly creeping into other consumer products that depend on embedded software.
I bought a new electric car recently. For the most part I've been quite happy with it. Shortly after I bought it, it started popping up a warning message saying "check EV system" every time I started it. By the time I brought it into the dealership, the warning had gone away, and the technician just told me something to the effect of "eh, I guess it just does that sometimes, let us know if it happens again." Hardware fault? Software bug? Who can say?
Like most modern cars, it has connectivity and Google Maps built into the infotainment system. The vast majority of the time, it works fine. Sometimes it says it has no connectivity (meaning no traffic data and suboptimal routes) for the duration of a drive, even in areas with a strong cell signal where it normally works fine. Sometimes the car says it has connectivity, but Google Maps still thinks it's offline. Sometimes Maps will actually load and display a route, but the "start navigation" button just spins forever as though it's still waiting for something. Are these related issues? Is there a common cause that might be fixable? Who can say?
(Conveniently enough, the warranty specifically does not cover any failures of software or firmware to operate correctly.)
> a warning message saying "check EV system"
These are some of the most annoying messages a piece of software can possibly display, and I hate them with a passion!
It's like this with a lot of commercial software, where designers don't want to scare users with complicated (useful) error messages, so you just get a "whoopsie! Something went wrong".
I'd much rather have an error message that I _don't_ understand over an error message I _can't_ understand.
In the case of cars, it used to be that a generic "Check engine" light showed up on your dash, and you needed an external tool to ask the computer what caused it to light up, but why would that be nessecary in a modern vehicle? You've got a large, high resolution display (or more!) on the CAN bus, why can't it show the full problem so you could take a picture right as it happens and send it to your dealer for instant diagnosis?
>why can't it show the full problem so you could take a picture right as it happens and send it to your dealer for instant diagnosis?
Fault codes are uploaded to the manufacturer on modern cars with telematics. On mine, the app will say you have an engine fault (or need an oil change or recall) and offer to schedule an appropriate appointment. If you call them, they often have it already in their portal under your VIN. The manufacturer also keeps track of these for regulatory purposes (triggering recalls).
A single fault code doesn't mean much. That's like saying I got a segfault, please fix my problem. You need a stack trace, registers, what the user was doing at the time, whether they can reproduce it, etc.
OBD2 stores a _freeze frame_, most of its readings at the time of the fault. You also need to look at other fault codes, pending codes, frequency/history of the fault to make a diagnosis. In any case, you can't just give one code; it's 5 pages of readings.
teraflop · · focus · HN ↗
I bought a new electric car recently. For the most part I've been quite happy with it. Shortly after I bought it, it started popping up a warning message saying "check EV system" every time I started it. By the time I brought it into the dealership, the warning had gone away, and the technician just told me something to the effect of "eh, I guess it just does that sometimes, let us know if it happens again." Hardware fault? Software bug? Who can say?
Like most modern cars, it has connectivity and Google Maps built into the infotainment system. The vast majority of the time, it works fine. Sometimes it says it has no connectivity (meaning no traffic data and suboptimal routes) for the duration of a drive, even in areas with a strong cell signal where it normally works fine. Sometimes the car says it has connectivity, but Google Maps still thinks it's offline. Sometimes Maps will actually load and display a route, but the "start navigation" button just spins forever as though it's still waiting for something. Are these related issues? Is there a common cause that might be fixable? Who can say?
(Conveniently enough, the warranty specifically does not cover any failures of software or firmware to operate correctly.)
yonatan8070 · · focus · HN ↗
These are some of the most annoying messages a piece of software can possibly display, and I hate them with a passion!
It's like this with a lot of commercial software, where designers don't want to scare users with complicated (useful) error messages, so you just get a "whoopsie! Something went wrong".
I'd much rather have an error message that I _don't_ understand over an error message I _can't_ understand.
In the case of cars, it used to be that a generic "Check engine" light showed up on your dash, and you needed an external tool to ask the computer what caused it to light up, but why would that be nessecary in a modern vehicle? You've got a large, high resolution display (or more!) on the CAN bus, why can't it show the full problem so you could take a picture right as it happens and send it to your dealer for instant diagnosis?
sam1714 · · focus · HN ↗
Fault codes are uploaded to the manufacturer on modern cars with telematics. On mine, the app will say you have an engine fault (or need an oil change or recall) and offer to schedule an appropriate appointment. If you call them, they often have it already in their portal under your VIN. The manufacturer also keeps track of these for regulatory purposes (triggering recalls).
A single fault code doesn't mean much. That's like saying I got a segfault, please fix my problem. You need a stack trace, registers, what the user was doing at the time, whether they can reproduce it, etc.
OBD2 stores a _freeze frame_, most of its readings at the time of the fault. You also need to look at other fault codes, pending codes, frequency/history of the fault to make a diagnosis. In any case, you can't just give one code; it's 5 pages of readings.