Embedded Perspectives
Automotive Ethernet
5 articles tagged with Automotive Ethernet.
DoIP Explained: ISO 13400 Diagnostics Over IP, Step by Step
DoIP carries UDS diagnostics over automotive Ethernet, and a session is three exchanges in a fixed order: discovery, routing activation, then diagnostic messages. This walkthrough follows each phase on the wire, using open-source clients and the Wireshark dissector as public references. GSAS Engineering supports India-based diagnostics, HIL and validation teams on bench bring-up in IST hours.
OBD2 vs UDS vs DoIP: vehicle diagnostics protocols explained
Three terms turn up in one job spec or one tool menu, and nobody explains how they relate. This article puts OBD2, UDS and DoIP on a single layering table, shows why a modern vehicle uses all three at once in different roles, and hands each branch to the article that covers it in depth. Written by GSAS engineering, who consult on diagnostic benches over IST hours.
UDS negative response codes: the complete NRC table with causes
A working lookup table for UDS negative response codes, built from the public py-uds and udsoncan code tables rather than from a paywalled standard. Every code carries the causes that actually produce it on a bench, with deep sections on 0x31, 0x33 and 0x78. Written by the GSAS engineering team for validation and integration teams debugging ECUs.
UDS protocol explained: ISO 14229 services, security access
A working engineer's model of Unified Diagnostic Services: the service ID grammar, the four diagnostic sessions, the seed and key exchange, and how the same request rides CAN, CAN FD or automotive Ethernet. Written by the GSAS engineering team, with every value traceable to a source you can open for free.
UDS services list: what every service ID does
One canonical table of UDS service IDs, every row checked against the public udsoncan reference documentation, with what the service does and the session it usually needs. Then byte level detail on the five you will actually type: 0x27, 0x22, 0x2E, 0x19 and 0x31. Written by the GSAS engineering team for engineers working with a diagnostic trace open.
Questions about Automotive Ethernet?
Our application engineers help teams evaluate tools, plan validation, and scope pilots across India.