Vehicle network engineering & diagnostics
EVdiag works on the vehicles the standard tester struggles with — electric and hybrid drivetrains, zonal architectures and software-defined platforms, where a symptom has to be traced across CAN FD, SENT and automotive Ethernet before anyone touches a spanner.
Capabilities
Diagnostics, network analysis and the small pieces of software that make both repeatable.
Fault-finding on modern platforms where the answer is rarely a single trouble code — reading live data across the busses, tracing a symptom to the ECU or the wiring that actually causes it, and saying plainly which it is.
CAN and CAN FD, LIN, SENT sensor links and automotive Ethernet. Bus loading, timing, termination and physical-layer faults, measured rather than guessed.
Architectures where function has moved off dedicated ECUs into central compute and zone controllers, and where a fault can be configuration rather than hardware.
High-voltage architecture, battery and charging behaviour, and the diagnostic differences that come with a drivetrain that has no gearbox to blame.
When the existing tool does not exist or is a spreadsheet, I build one. Small, focused software that a technician can use on the shop floor without training.
Turning a factory document and a tester screen into a procedure someone else can follow, and a report a customer can understand.
Technology
A modern vehicle is a network before it is a machine. These are the layers a fault actually lives on.
| Technology | Standard | Where it matters |
|---|---|---|
| CAN / CAN FD | ISO 11898 | Classic CAN alongside flexible-data-rate, with the longer payloads and faster data phase that modern platforms rely on. |
| LIN | ISO 17987 | Low-cost single-wire sub-busses for doors, mirrors, seats and comfort actuators. |
| SENT | SAE J2716 | Single-edge nibble transmission — the one-way digital sensor links that replaced analogue signalling on pressure, position and temperature sensors. |
| 10BASE-T1S | IEEE 802.3cg | Multidrop automotive Ethernet on a single pair, sharing one segment between several nodes — the edge of a zonal network. |
| 100/1000BASE-T1 | IEEE 802.3bw / bp | Single-pair Ethernet backbones carrying the traffic that used to be split across a dozen busses. |
| UDS & DoIP | ISO 14229 / 13400 | Unified diagnostic services, over CAN and increasingly over IP — the protocol layer beneath every tester screen. |
| Zonal architecture | — | Zone controllers replacing domain ECUs, with function centralised and the wiring harness shortened. |
| Software-defined vehicles | — | Behaviour that changes with a software release rather than a part number, and the diagnostic questions that follow from it. |
Projects
Each one started as a job that was slower or more error-prone than it needed to be.
Turns the raw clutch figures on a diagnostic tester into a one-page report the customer understands. Six single-clutch automated-manual gearboxes, every wear limit taken from the factory documentation, VIN read from the windscreen plate with the camera. Works entirely offline — nothing is uploaded anywhere.
Finds where a noise or vibration is actually coming from. Three accelerometers, time-difference-of-arrival between them, and the event located rather than guessed at — with the documentation translated into 28 languages.
A receipt scanner and mileage tracker for self-employed people filing Schedule C. Photograph a receipt and the vendor, amount, date and line items are extracted and mapped to the right tax line; drives are logged automatically. Receipt images and location stay on the device.
About
EVdiag is my independent practice: diagnostics and vehicle-network engineering on current and near-future platforms, plus the tooling that comes out of doing that work day to day.
Most of what I build starts as a problem on a workshop floor. The Clutch Wear app began as a spreadsheet a technician had to retype for every car; it is now a free app in both stores that prints the customer's copy. That is the pattern — find the step that wastes an hour or invites a mistake, and remove it.
The interest that pulls the rest along is where vehicles are going: electric drivetrains, zonal wiring, and behaviour defined by software releases rather than part numbers. Diagnosing those well means reading the network, not just the fault memory.
Contact