Why cars moved diagnostics to Ethernet
Classic CAN moves at most one megabit a second, eight bytes at a time. That was plenty when a control unit's software was a few hundred kilobytes. It is not when one module's update runs to hundreds of megabytes: at CAN speed that is hours in the bay with a battery charger on the car.
DoIP keeps the diagnostic language the same and changes the road it travels on. The requests are still UDS services such as read data, read fault codes and download. They are wrapped in a small DoIP header and sent over ordinary TCP/IP on 100 megabit Ethernet, which is around two hundred times faster than a 500 kbit/s CAN bus.
How a DoIP session starts
A car does not leave Ethernet live on its diagnostic connector while it drives. The tester has to ask for it, and then find the car on the network, before a single diagnostic request can be sent.
- Activation. The tester raises the activation line on pin 8, and the vehicle switches Ethernet on at the connector.
- Addressing. Both ends take an IP address, from DHCP if a server is present, otherwise a link-local one.
- Discovery. The vehicle announces itself over UDP port 13400, or the tester asks. The answer carries the VIN and the logical address of the vehicle's DoIP entity.
- Routing activation. The tester opens a TCP connection to port 13400 and asks to be routed. Until the vehicle agrees, diagnostic messages go nowhere.
- Diagnostics. UDS requests travel inside DoIP messages that name a source and a target address. The vehicle's gateway passes them on to the control unit they are for.
Which OBD-II pins carry DoIP
ISO 13400-4 puts Ethernet on the same 16-pin connector as everything else and gives makers two layouts. Option 1 uses pins 3 and 11 for one pair and pins 12 and 13 for the other. Option 2 uses pins 1 and 9 with 12 and 13. Both use pin 8 as the activation line.
Pins 3 and 11 are the trap. On some cars those two pins are a second CAN bus. On a DoIP car they are half of an Ethernet link. An interface that assumes one and meets the other hears nothing, or worse, talks onto a bus it does not understand. That is why AirModuleLink listens on those pins before it joins them.
DoIP is not the car on the internet
Because DoIP is TCP/IP, it is tempting to think a DoIP car can simply be routed to a workshop somewhere else. It cannot. The vehicle expects its tester on the same wire, answers discovery only on the local link, and holds every exchange to timeouts written for a cable two metres long.
So remote DoIP needs something at the car that is a real DoIP tester to the vehicle, and that carries the conversation to the technician by a link built for distance. That is the job of the DoIP relay in AirModuleLink.
What AirModuleLink does with it
The box finds a DoIP vehicle, opens routing and relays diagnostic reads and scans to a tester at your shop. The relay carries diagnostics by design. Programming a DoIP car is done with the maker's software through IgniteRemote on a computer at the car.