I get annoyed when you purchase a code reader and it says there's no fault codes! - even though the machine/engine/vehicle is not performing as it should! Then you find that ECU's don't record all faults, only the ones they've been programmed to find!
I bought a new luxury Ford car in mid-1990. It had climate control! - woo-hoo! Dial up the temperature, and the cabin got to that preselected temperature and stayed there. Then, just before the warranty ran out, the climate control/air conditioning stopped working.
Took it into the Ford dealership and the service manager delighted in showing me how if you pressed multiple buttons at the same time on the controls, the CC went into "self-diagnosis" mode and broke up the circuitry into 10 different sections, and then tested them all, and produced the code for the fault!
So I said, "Show me!" - and he pressed all the buttons for the self-test - and it came up with "No fault found" - and he got quite upset that it wouldn't work! So he said, "We'll have to run it through the workshop and go into this in depth!". So he did, and I got the car back - with the CC working - and I said, "So, you found the fault?". "Oh yes", he said, "It was a dirty fuse on the back of the A/C compressor!"
I drove around the rest of the day, and within 2 hrs, the CC had stopped working again. So I took it back again. The workshop set to on it again, and I got the car back, and the CC was working again.
I said to the manager, "So you really did find the fault, this time around?" And he replied, "Yes, it was the microprocessor (the ECU) for the climate control that had failed. The ECU can test the circuitry, but they can't test themselves, once they've failed!"
One of the biggest failings I have noticed with vast levels of electronics in machinery, is an increase in fires caused by electrical faults. When they start to burn with an electrical fault, they're usually a total write-off.