AUTOSAR and vehicle networks guides
How CAN fits into the rest of the vehicle: LIN, Automotive Ethernet, gateways, and AUTOSAR ECU software, from the layered architecture down to the CAN stack.
7 guides Read them in this order
- Why CAN still matters and where it is better than other vehicle buses CAN is not newer than Automotive Ethernet, but newer does not always mean better. This guide compares CAN with LIN, FlexRay, and Ethernet in the contexts where engineers actually make architecture decisions.
- Automotive Ethernet, ECUs, gateways, and the rest of the vehicle network stack CAN does not live alone. This guide explains how ECUs, gateways, LIN, FlexRay, and Automotive Ethernet coexist inside modern vehicles and why zonal architectures are reshaping the map.
- LIN bus for CAN engineers: where it fits and how to think about it A practical LIN bus guide for engineers who already know CAN, covering master-slave scheduling, LDF files, signals, gateways, diagnostics, and why LIN still appears beside CAN and Ethernet.
- Automotive Ethernet for CAN engineers A practical guide to Automotive Ethernet for engineers coming from CAN and CAN FD, covering 100BASE-T1, 1000BASE-T1, gateways, tcpdump, SOME/IP-style thinking, and why Ethernet does not replace every CAN bus.
- What is AUTOSAR? Classic and Adaptive explained for CAN engineers A plain-language introduction to AUTOSAR. Learn the layered Classic Platform (application, RTE, basic software, MCAL), how the Adaptive Platform differs, what ARXML files hold, and where CAN fits in.
- How CAN works in AUTOSAR: the CAN stack from COM to the CAN driver Follow a CAN signal through the AUTOSAR Classic communication stack. Learn what COM, PduR, CanIf, CanTp, CanSM, CanNm, and the CAN driver each do, how I-PDUs become CAN frames, how ARXML maps to DBC, and where J1939 fits.
- SOME/IP and SOME/IP-SD explained with real packet bytes How SOME/IP messages and SOME/IP Service Discovery work on automotive Ethernet. The 16-byte header field by field, message types, return codes, methods versus events, and the SD entries and options, with byte-level packets and a tested Python encoder and parser.