Automotive Electrical Systems Engineering: High-Voltage Architecture, In-Vehicle Networks, and Fault Diagnosis for the Software-Defined Car

The circuit is intact. The function is gone.

A lamp does not light. The bulb is good, the fuse is good, the ground is clean, and the switch closes. Every measurement you take is correct, and the lamp is still dark, because the fault is not in a wire. It is in a message that was never sent, or was sent and not authenticated, or was sent to a controller that had gone to sleep.

Most electrical references on the shelf were written for a car with a fuse box, a wiring tree, and one low-speed data bus. This one was written for the vehicle in your bay now: three voltage domains in one body shell, five network media running alongside each other, and software deciding what the hardware is allowed to do.

What is inside

• The physical layer, in real depth. Conductors, insulation, terminals, connectors, sealing, splices, grounds and the return path, with the arithmetic that tells you a joint is bad rather than the impression that it looks bad.
• Three voltage domains. The 12 volt system and its modern job, 48 volt mild hybrids, and traction architecture from 400 volts through 800 to 900 volts and above.
• Energy storage and conversion. Packs, cells and chemistry, the battery management system, inverters, motors, and AC and DC charging.
• Every network the vehicle actually runs. CAN, CAN FD, CAN XL, LIN, FlexRay and automotive Ethernet, with sensors and signal conditioning ahead of them, and the capture and interpretation of real bus traffic.
• Control and software. The move from dozens of scattered control units to zonal architecture and central compute, the software-defined vehicle, and the load that ADAS sensing imposes.
• Diagnosis that does not rely on luck. Diagnostic protocols, a repeatable method for narrowing an electrical fault nobody anticipated, intermittents, voltage drop, and parasitic draw.
• Safety, access and compliance. High-voltage service safety, the secure gateway and authorisation, and the regulation and functional safety standards that now decide what a technician is permitted to do.

How it is built

32 chapters in six parts, with 374 figures, 183 tables, 128 worked examples, and a checkpoint set closing every chapter.

The diagrams are computed, not drawn to look right. Every value-bearing schematic, waveform and characteristic curve in this book is generated from the data behind it and checked against the text that quotes it. What you read off a curve here agrees with the number in the paragraph beside it.

The worked examples carry their arithmetic through. Given, find, reasoning, answer, and a check that tests the result at the point where an error would be obvious. The method is the thing being taught, not the number.

Time-sensitive claims carry their date in the sentence. Where a market share, a platform or a regulatory deadline is quoted, the year it was true is stated and the standard is named. A reader some years from now knows exactly which paragraphs to verify and which are physics.

Who it is for

Working technicians and diagnosticians who have run out of road with the references they own. Apprentices moving into electric and hybrid work. Engineering students who want the practice behind the theory. And anyone whose reference shelf stops before zonal architecture.

Written to be worked from, not read once.