Automotive Ethernet supplies a physical link and frame delivery. Vehicle links can use single-pair variants such as 100BASE-T1. IP and diagnostic protocols sit above Ethernet.
Reading the network or diagnostic trace
An internal Ethernet link and the workshop connector can use different physical interfaces. Determine where the tester connects and whether the vehicle gateway routes the requested diagnostic traffic.
See Diagnostics over IP and the vehicle diagnostics protocol guide.
Sources: ACTIA IME overview.
Detailed reference
Automotive Ethernet is a twisted pair inside the car, running at 100 Mbit/s or more, with ordinary Internet Protocol above the physical layer. Diagnostics over IP, DoIP, is the workshop transport that carries diagnostic services over IP. On the socket specified for it, the physical layer is a different Ethernet: 100BASE-TX, the four-wire Fast Ethernet a tester uses, not the single pair in the harness. The services themselves remain the ones on the diagnostic communication protocols page. The fibre rings this pair is often compared with are on the fibre-optic networks page.
The pair in the harness
IEEE 802.3bw, 100BASE-T1, is the 100 Mbit/s physical layer that came out of BroadR-Reach. Texas Instruments' account of it specifies one unshielded twisted pair, full duplex, so transmit and receive share the pair, over at least 15 m. The encoding is a 4-bit to 3-bit step, then a 3-bit to two ternary symbols, then three-level pulse amplitude modulation. The point of that encoding is the emissions limit: the paper cites CISPR 25 Class 5 and the OPEN Alliance TC8 tests. The media-independent interface above the physical layer is unchanged, which is why a switch and an ordinary Ethernet stack sit on top of a cable that looks nothing like office Ethernet.
Siemens' automotive Ethernet note separates the rates by the job. 100BASE-T1 and 1000BASE-T1 are switched networks on one pair, shielded or not as the installation needs. 1000BASE-T1 is 1 Gbit/s. 10BASE-T1S is 10 Mbit/s and is a multidrop bus, closer in shape to CAN, aimed at the places that do not need a switch. The layers above stay IP, so a car can mix the rates without a gateway translating every message. That is the practical difference from a MOST ring, where a unit that does not understand the generation of the bus cannot sit on it.

DoIP on the workshop socket
ISO 13400 is the DoIP series. Vector's training note on it makes the split that matters in the workshop: DoIP defines how diagnostic packets are carried, and the diagnostic services inside those packets remain KWP or UDS. UDP carries status and configuration. TCP carries the diagnostic packets, on a connection, and segments the large ones. Both the tester and every DoIP node, including a gateway at the edge of the vehicle network, implement UDP and TCP. The same note says the transport does not care which physical layer delivered the IP packets. The header, discovery, routing activation and payload types are on the Diagnostics over IP page.
The wired vehicle interface does care. ISO 13400-3:2016 specifies that interface on IEEE 802.3 100BASE-TX, including how the vehicle Ethernet is discovered and how it is switched on and off. ISO 13400-4:2016 puts that Ethernet onto the diagnostic connector of ISO 15031-3 and defines two pin assignments. Option 1 matches cars already on the market and avoids a clash with manufacturer use of pins 1 and 9. Option 2 avoids a clash with pins 3 and 11. The activation line that enables the interface is specified in part 3. The pin options already drawn for this connector are on the diagnostic ports page. Siemens states the same distinction from the other side: DoIP on the SAE J1962 socket, as many manufacturers wire it, is 100BASE-TX on two pairs, while 100BASE-T1 is the single pair used between control units.
BMW's passive lead from this socket to a laptop RJ45 is the ENET cable. The published wiring uses option 1. That page records which RJ45 pin each contact meets, the activation resistor the cable guides print, and how the lead differs from an ICOM.
ISO 14229-1:2020 names ISO 13400-2 as the transport when the same diagnostic services run over IP. Moving a control unit from CAN to DoIP changes the wire and the time a large upload takes. It does not change the data record the control unit was built to return.
One manufacturer's mix: a 2019 Model 3
Tesla's public Model 3 service index lists separate procedures for the front body controller and for the left and right body controllers, including heat-pump and right-hand-drive variants. That is the workshop evidence that this generation is built around those three modules. It does not publish a network diagram in that index.
A 2024 teardown in Electronic Engineering Album, of a 2019 left-hand-drive high-specification Model 3, is the account of how those modules are tied together. The author presents it as a reconstruction from the car and from published teardowns, and says some of it is still uncertain. Read it as that one car.
In that account the three body controllers are the low-voltage core. The front controller, in a metal case near the front compartment and the low-voltage battery, feeds the left and right controllers and supplies the driver-assistance and cabin computers. It also runs the heating and ventilation. The left controller, ahead of the driver's shins, takes the accelerator, brake and steering signals, and the diagnostic connector lands on it. The right controller takes the ultrasonic sensors and has a private park CAN to the driver-assistance computer. Power distribution uses semiconductor switches in the controllers rather than a central relay box. The left and right electric parking brakes are fed from the controller on that side.
The communication the article describes is CAN first, then Ethernet and LIN. Three CAN trunks are named. Private CAN carries the drive, steering and brake units. Chassis CAN is a second path for steering and brakes. Vehicle CAN is a second path for the drive units and carries the body accessories. Ethernet, in that account, joins the driver-assistance computer, the cabin computer, the diagnostic port and the radio. LIN joins the ultrasonic sensors, the temperature and humidity sensor, the overhead consoles, the front and rear lamp controllers, the wiper and HomeLink. A coaxial link carries the rear-camera picture to the cabin computer. Audio to the rear amplifier is A2B, not Ethernet and not MOST. Nothing in the account is a plastic optical ring.
That is a different shape from the E65, where MOST and byteflight are fibres and CAN is the copper backbone, and from a Mercedes of the D2B years, where the infotainment ring is optical and CAN B is reached through the radio. The Model 3 in this teardown keeps CAN for the vehicle, uses LIN at the edges, and uses Ethernet where the cabin computer and the driver-assistance computer need the bandwidth. It does not follow that every later Tesla, or every other manufacturer's zonal car, uses these three CAN names.
Sources
- 100BASE-T1 Ethernet: the evolution of automotive networking. Texas Instruments, SZZY009. One pair, 100 Mbit/s, at least 15 m, PAM3. Accessed 2026-11-12.
- Automotive Ethernet. Siemens. 100BASE-T1, 1000BASE-T1, 10BASE-T1S, and DoIP on the diagnostic socket as 100BASE-TX. Accessed 2026-11-12.
- ISO 13400-3:2016 and ISO 13400-4:2016. The 100BASE-TX vehicle interface and the two diagnostic-connector pin options. Accessed 2026-11-12.
- DoIP. Vector. UDP and TCP, and DoIP as a transport for the existing diagnostic services. Accessed 2026-11-12.
- Model 3 service manual. Tesla. Procedures for the front, left and right body controllers. Accessed 2026-11-12.
- Tesla E/E architecture analysis. Electronic Engineering Album, 2 September 2024. One 2019 Model 3: three body controllers, three CAN trunks, Ethernet and LIN. Accessed 2026-11-12.