Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Diagnostics
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Diagnostics over IP, shortened to DoIP, is the name ISO 13400 gives to diagnostic communication over Internet Protocol. It is the transport: how a tester and a vehicle find each other, and how a diagnostic packet is carried on TCP and UDP. The services inside the packet remain the ones on the diagnostic communication protocols page. Vector's training note is explicit that DoIP does not replace those services. Keyword Protocol 2000 and Unified Diagnostic Services still name the request. DoIP defines how that request is carried.

The single-pair Ethernet inside the harness is a different physical layer from the workshop socket. That split, and one manufacturer's mix of CAN, LIN and Ethernet, is on the Automotive Ethernet and DoIP page. The 16-pin shell the workshop pairs are added to is on the diagnostic ports page. The CAN transport a large transfer uses when the path is still CAN is ISO-TP.

What the series is for

ISO 13400-1:2011, now withdrawn, stated the job. The interface should stay stable on the outside while the networks inside the car change. It should serve legislated diagnostics and the manufacturer's own uses, including calibration and software updates. It should be able to sit on a later physical layer, wired or wireless, because the diagnostic transport is defined on IP rather than on one bus. And a tester outside the car and a tester inside the car should both be able to speak it. The same edition names two application layers the descriptions cover: enhanced diagnostics, meaning system diagnostics beyond the legislated emissions functions, and World-Wide Harmonized On-Board Diagnostics as specified in ISO 27145-2 and ISO 27145-3. The protocol is also required to support the service-primitive interface of ISO 14229-2.

The areas named there are engineering, manufacturing, service in a franchised workshop or an independent repair shop, and legislated inspection. The specification says it covers the communication needed for those jobs, and that it does not set the data contents, the update rate or whether a signal is available. Three clusters follow. Inspection and repair asks for the data to be transferred reliably and in the order requested, and for a vehicle to stay identifiable after a DoIP entity has been replaced even if the new one is not fully configured. The cluster summary says that data can be retrieved without requiring connection establishment and/or security negotiations. Reprogramming is the large transfer. Its cluster summary says the vehicle requires a connection and security negotiations, while the detailed brief in the same edition says the security negotiations are optional. Both sentences are in the 2011 text. The goal of that use case also asks the protocol to allow an efficient gateway, including splitting and reassembling the data. Assembly-line inspection is the same shape as repair, limited to production, with several parallel diagnostic sessions, and with the vehicle still identifiable when not every DoIP entity has been installed. A note on the cluster table says a vehicle may reject a use case because of its state, the example given being while driving, and that wireless communication in particular can require extra security. The same edition notes that the physical link can also carry communication that is not diagnostic, and that ISO 13400 does not specify that other communication.

The connection pictures are a direct cable, a network with one vehicle and one tester, several vehicles on one tester's network, and one vehicle with several testers or several test applications. On a direct cable no other tester or vehicle is on the link, and the addresses may be a predefined set or an automatic configuration. Each vehicle may contain more than one DoIP entity. The edition was withdrawn on 30 January 2019. ISO's record of it shows no replacement part. The use cases are the historical statement of intent. The requirements that are still maintained are in parts 2, 3 and 4.

The 2025 edition of part 2 repeats the same intent and draws the stack above and below the transport. Above it, the diagnostic communication framework is ISO 14229-1, the DoIP payload-type detection in ISO 13400-2, ISO 14229-2, and ISO 14229-5. ISO 14229-5:2022 is the implementation profile for Unified Diagnostic Services on IP. A presentation layer beside that can be a manufacturer's own description or ODX, ISO 22901. Below it, the wired vehicle interface is ISO 13400-3 and the connector is ISO 13400-4. The introduction's examples of networks that need a gateway, rather than a direct tester socket, are FlexRay and MOST. The fibre-optic networks page is that history.

The four parts, and the one that stopped

All four published parts were written in ISO/TC 22. Part 1 was finished under subcommittee SC 3. Parts 2, 3 and 4 are under SC 31, data communication. The 2011 foreword of part 1 listed a part 5, a conformance-test specification, as under preparation. No part 5 appears among the ISO pages for this series checked on 13 November 2026.

PartWhat it decidesStatus checked in November 2026
ISO 13400-1:2011Use cases and communication scenarios. Enhanced diagnostics and WWH-OBD.Published 18 October 2011. Withdrawn 30 January 2019. 15 pages. No replacement listed.
ISO 13400-2:2012First edition of the transport and network-layer services.Withdrawn. Replaced by the 2019 edition.
ISO 13400-2:2019Second edition. The abstract already includes secured and unsecured communication. TLS is listed as optional, with entity-status monitoring and a DoIP entity firewall.Published 13 December 2019. 78 pages. Withdrawn 13 June 2025, when the third edition replaced it. Amendment 1, published 24 July 2023, was withdrawn on 13 June 2025 and is incorporated into the 2025 text.
ISO 13400-2:2025Current transport. Protocol version 4. The public foreword lists a revised timing table, a diagnostic-message negative acknowledgement of 09 hexadecimal, a check of payload types on UDP, and a rule that a DoIP server supports one protocol version.Third edition, published 13 June 2025. 79 pages. On 14 October 2026 ISO marked it to be revised. A committee draft, ISO/CD 13400-2, is the successor named on that record.
ISO 13400-3:2016Wired vehicle interface on IEEE 802.3 100BASE-TX. Discovery of that interface, and switching it on and off. The second edition added identification of two Ethernet pin assignments.Published 9 November 2016. 14 pages. Confirmed on review in 2022. Replaces the 2011 edition.
ISO 13400-4:2016The diagnostic Ethernet connector, based on the ISO 15031-3 shell. Two pin assignments. The activation line itself is specified in part 3.Published 29 March 2016. 11 pages. Confirmed again on 20 October 2026.

Part 2 separates mandatory behaviour from optional behaviour. Mandatory in the 2019 and 2025 abstracts: IP address assignment, vehicle announcement and discovery, basic status such as the diagnostic power mode, connection establishment including concurrent attempts, connection maintenance, gateway control, routing to and from the vehicle's sub-components, and error handling such as a physical disconnect. Optional: DoIP entity status, TLS, and firewall capabilities of a DoIP entity. The 2025 contents also distinguish an unsecured session from a TLS session, a direct connection from a networked connection, and an internal tester, which that outline marks optional. Vector describes the same two tester places in workshop language: an external tester in the repair shop, and an on-board tester in the vehicle.

Layers

The German Wikipedia article, and the longer EverybodyWiki page that presents itself as a copy of a Wikipedia draft, both draw DoIP on the seven-layer model. They do not draw the same physical layer. The standards split the question.

LayerWhat carries the diagnostics
ApplicationISO 14229-1, profiled for IP by ISO 14229-5:2022. ISO 13400-1 also names WWH-OBD, ISO 27145-2 and ISO 27145-3. Vector still includes Keyword Protocol 2000 as a service list the transport can carry.
PresentationThe 2025 introduction gives ODX, ISO 22901, or a manufacturer's own description, as the example of how the services are written down for a tool. That description is not the DoIP header.
The DoIP messageISO 13400-2. An 8-byte header, then a payload. This is the layer a dissector calls DoIP. It sits on TCP or UDP. It is not Ethernet, and it is not the UDS service byte.
TransportTCP for the diagnostic connection. UDP for discovery, announcement and status. IANA registers TCP 13400 as doip-data and UDP 13400 as doip-disc, both on 26 January 2011, assignee Joerg Schneider.
NetworkIP. The 2025 contents include DHCP and address assignment, IPv4 address resolution, and IPv6 neighbour discovery. A vehicle integration has to obtain an address. The doipclient primer warns that a given control unit may still expect the tester to choose an address by hand, and that ICMP echo is not something to assume.
Data link and physical, workshopISO 13400-3: IEEE 802.3 100BASE-TX. Two pairs. The connector is the 16-pin ISO 15031-3 shell in part 4, not an RJ-45 on the car.
Data link and physical, in the harnessOften 100BASE-T1, one pair, full duplex. The Ethernet page is that pair. A tester PC does not speak 100BASE-T1 on its ordinary port. The doipclient primer says a media converter is the usual way onto that pair, and that the activation line belongs to the diagnostic socket, not to the pair between control units.

Vector's training note says the transport does not care which physical layer delivered the IP packets, and gives WLAN and UMTS as conceivable examples. That matches the 2025 introduction, which says later wired and wireless layers can be added by adaptation. It does not make the workshop socket into a radio. On the cars part 3 and part 4 are written for, the tester's wired interface is 100BASE-TX. English Wikipedia's vehicle-to-everything page lists remote vehicle diagnostics, with DoIP in brackets, as a vehicle-to-cloud example. That is one page's example of a remote session. A workshop session on the 16-pin socket is a local link.

The German article currently says the physical layer in automotive electronics is OABR, and its citation for that sentence is IEEE 802.3bp-2016. IEEE 802.3bp is 1000BASE-T1, 1 Gbit/s on one pair. OABR, OPEN Alliance BroadR-Reach, is the earlier name of the 100 Mbit/s single-pair layer that became IEEE 802.3bw, 100BASE-T1. Neither of those is the workshop interface in ISO 13400-3. EverybodyWiki says the physical medium is 100BASE-TX twisted pair with an RJ-45 connector. The signalling matches part 3. The connector on the vehicle, in part 4, is the legislated diagnostic shell.

EverybodyWiki also lists SAE J1939-73 as a protocol that can sit on DoIP, and places it on the presentation layer. The ISO 13400-1 abstract does not name J1939-73. Nothing checked for this page confirms that combination. The application layers the withdrawn part 1 does name are enhanced diagnostics and WWH-OBD.

Finding the vehicle

Discovery is UDP, on port 13400. AUTOSAR Classic Platform, release R20-11, document 418, requires a DoIP entity to ignore a vehicle-identification request that arrives on TCP. Three requests are defined there.

Payload typeRequestPayload
0001 hexadecimalVehicle identificationEmpty. The length field is 0.
0002 hexadecimalVehicle identification by entity identification6 bytes, the EID.
0003 hexadecimalVehicle identification by VIN17 bytes, the VIN.

On a vehicle-identification request, AUTOSAR also accepts protocol version FF hexadecimal followed by inverse 00 hexadecimal, as a default pattern, in addition to the version the entity itself speaks. A matching entity answers with payload type 0004 hexadecimal, the vehicle announcement, which is also the identification response. An entity can send that announcement on its own when its socket comes up. AUTOSAR repeats it a configured number of times. The response layout in that specification is:

FieldLengthWhat it is
VIN17 bytesThe vehicle identification number. If the entity cannot read one, AUTOSAR fills the field from a configured invalidity pattern.
Logical address2 bytesThe DoIP entity's own logical address, not an IP address.
EID6 bytesEntity identification. AUTOSAR allows this to be the Ethernet MAC address of the interface, or a configured value.
GID6 bytesGroup identification, so several entities in one vehicle can announce as one group. It may be set equal to the EID, configured, or supplied by a callback. The 2025 contents include synchronising a vehicle's GID.
Further action1 byte00 hexadecimal when nothing further is required. In AUTOSAR, 10 hexadecimal means a central-security routing activation, type E0 hexadecimal, is configured and has not yet succeeded. Wireshark's name for 10 hexadecimal is the same action: routing activation required to initiate central security.
VIN/GID status1 byte, optionalPresent when the entity is configured to send it. 00 hexadecimal means synchronised. 10 hexadecimal means the VIN and GID are not synchronised. Wireshark uses those two names.

The VIN is how a tester tells two vehicles apart when both answer on one workshop network. That is the multiple-vehicle case in the 2025 contents. A broadcast identification request is answered by every entity that hears it. The VIN and EID requests are how a tester asks for one of them.

Two further UDP questions are status, not discovery. Diagnostic power mode, request 4003 hexadecimal and response 4004 hexadecimal, is the example the ISO abstract gives of basic status, and basic status is mandatory. Wireshark names the response values 00 hexadecimal not ready, 01 hexadecimal ready, and 02 hexadecimal not supported. Entity status, request 4001 hexadecimal and response 4002 hexadecimal, is the optional monitoring feature. AUTOSAR's response is a node type, the maximum number of concurrent tester sockets, the number currently open, and, when the entity includes it, a four-byte maximum data size. Node type 00 hexadecimal is a gateway. Node type 01 hexadecimal is a node.

Opening the connection

The diagnostic conversation is TCP, again on port 13400 for the unsecured session. UDP discovery does not authorise a source address. AUTOSAR discards a routing-activation request that arrives on UDP, and it discards a diagnostic message that arrives on UDP. The tester opens TCP, then sends payload type 0005 hexadecimal.

AUTOSAR's routing-activation request is a 2-byte source address, a 1-byte activation type, 4 bytes reserved for ISO, and an optional 4 bytes of manufacturer data. The payload length is 7 without those last 4 bytes, and 11 with them. The reserved field in that layout is zero. Wireshark still carries an older layout, used with the 2010 version byte, in which the activation type occupies 2 bytes. A capture has to be read against the version byte in the header.

Activation types named by the Wireshark dissector are 00 hexadecimal default, 01 hexadecimal WWH-OBD, and E0 hexadecimal central security. The response, payload type 0006 hexadecimal, returns the tester's logical address, the entity's logical address, a 1-byte code, 4 reserved bytes, and 4 optional manufacturer bytes. The codes in that dissector are:

CodeWireshark's text
00 hexadecimalDenied. Unknown source address.
01 hexadecimalDenied. Every concurrently supported TCP data socket is already registered and active.
02 hexadecimalDenied. A different source address was received on a TCP socket that was already activated.
03 hexadecimalDenied. That source address is already active on a different TCP socket.
04 hexadecimalDenied. Missing authentication.
05 hexadecimalDenied. Rejected confirmation.
06 hexadecimalDenied. Unsupported activation type.
07 hexadecimalDenied because an encrypted TLS connection was requested. The Eclipse openSOVD Classic Diagnostic Adapter treats this code as the cue to open the TLS session instead.
10 hexadecimalRouting successfully activated.
11 hexadecimalRouting will be activated. Confirmation is still required.

Until the code says the routing is active, the entity has not accepted the tester's source address. AUTOSAR's socket handling shows why a busy gateway sends an alive-check request, payload type 0007 hexadecimal, and waits for 0008 hexadecimal. If every registered tester answers, a newcomer is refused with code 01 hexadecimal. If one of them has gone quiet, that socket can be dropped and the new tester can continue. Code 01 hexadecimal is a full gateway, not a fault in the cable.

TLS is optional in the 2019 abstract and remains optional in the 2025 abstract. The 2025 contents give it a section of its own: accepted TLS versions, cipher suites and extensions are specified there, and the public preview stops at the heading. Wireshark dissects DoIP inside TLS on TCP port 3496. IANA's registration for 3496 is seclayer-tls, "securitylayer over tls", not a DoIP service. The ports IANA lists under the DoIP names are 13400. A tool that assumes every vehicle speaks TLS on 3496 is ahead of the registry, and a vehicle that answers code 07 hexadecimal has refused the unsecured activation. Diadrom's June 2026 note states that 3496 is the port added with the 2019 edition. Treat the port as that implementation convention, and read the car's own specification before treating it as universal.

The header

Every DoIP message starts with the same 8 bytes. AUTOSAR R20-11 quotes the layout from ISO 13400-2 and states it as:

BytesField
0Protocol version. AUTOSAR's worked example is 02 hexadecimal.
1The inverse of byte 0. AUTOSAR's example, for version 02 hexadecimal, is FD hexadecimal.
2 and 3Payload type.
4 to 7Payload length, in bytes, not counting the header. A length of 2 means 10 bytes on the wire.
8 onwardThe payload the type names.

Wireshark's names for the version byte, which are the dissector's labels rather than a fresh reading of the 2025 text, are:

VersionDissector label
00 hexadecimalReserved.
01 hexadecimalISO/DIS 13400-2:2010.
02 hexadecimalISO 13400-2:2012.
03 hexadecimalISO 13400-2:2019.
04 hexadecimalISO 13400-2:2019 amendment 1, marked experimental in the dissector. The 2025 foreword says that edition specifies protocol version 4 and incorporates the amendment. A byte of 4 can be either document. The foreword also says a DoIP server supports one protocol version, so one entity does not answer in two of these at once.
FF hexadecimalDefault value for vehicle identification requests, paired with inverse 00 hexadecimal.

A header the receiver will not accept is answered, on UDP or TCP, with payload type 0000 hexadecimal and a one-byte code. Wireshark names 00 hexadecimal incorrect pattern format, 01 hexadecimal unknown payload type, 02 hexadecimal message too large, 03 hexadecimal out of memory, and 04 hexadecimal invalid payload length. AUTOSAR sends 04 hexadecimal when the length is not valid for that payload type, and then closes the socket. An entity that receives a generic negative acknowledgement discards it.

The payload types AUTOSAR R20-11 requires, which are the same numbers Wireshark decodes, are:

TypeNameTransport in AUTOSAR
0000 hexadecimalGeneric header negative acknowledgementUDP or TCP
0001 hexadecimalVehicle identification requestUDP
0002 hexadecimalVehicle identification request with EIDUDP
0003 hexadecimalVehicle identification request with VINUDP
0004 hexadecimalVehicle announcement, or identification responseUDP
0005 hexadecimalRouting activation requestTCP
0006 hexadecimalRouting activation responseTCP
0007 hexadecimalAlive check requestTCP
0008 hexadecimalAlive check responseTCP
4001 hexadecimalEntity status requestUDP
4002 hexadecimalEntity status responseUDP
4003 hexadecimalDiagnostic power mode requestUDP
4004 hexadecimalDiagnostic power mode responseUDP
8001 hexadecimalDiagnostic messageTCP
8002 hexadecimalDiagnostic message acknowledgementTCP
8003 hexadecimalDiagnostic message negative acknowledgementTCP

The 2025 foreword adds a diagnostic-message negative-acknowledgement code of 09 hexadecimal and a further payload-type status. The preview does not define that new code. A dissector built to the table above will show the type and leave the new code unnamed.

The diagnostic message

Payload type 8001 hexadecimal is the one that carries a service. AUTOSAR requires it on TCP, with a payload of at least 5 bytes:

BytesField
0 and 1Source logical address.
2 and 3Target logical address.
4 onwardThe diagnostic user data. For Unified Diagnostic Services this begins with the service identifier, the same first byte a CAN session would carry. ISO 14229-5 is the profile that says how those services are implemented on IP.

The acknowledgement is a separate DoIP message, and it is not the control unit's answer. AUTOSAR describes it as early feedback that the diagnostic message was received and accepted for the internal control unit, or sent onward to the target network. Payload type 8002 hexadecimal, code 00 hexadecimal in the Wireshark list, means that acceptance. The service response comes later, inside another 8001 hexadecimal message, and it still begins with the response service identifier from the protocols page. A positive acknowledgement followed by a negative UDS response means the gateway routed the request and the server refused the service.

Payload type 8003 hexadecimal refuses the message before that. Wireshark names the codes as 02 hexadecimal invalid source address, 03 hexadecimal unknown target address, 04 hexadecimal diagnostic message too large, 05 hexadecimal out of memory, 06 hexadecimal target unreachable, 07 hexadecimal unknown network, and 08 hexadecimal transport protocol error. Codes 00 and 01 hexadecimal are reserved in that list. The 2025 foreword's additional code, 09 hexadecimal, is not in the dissector list. AUTOSAR closes the socket on an invalid source address. An unknown target address means this tester was not given a route to that logical address when routing was activated. It does not mean the control unit reported a fault.

The edge node

A DoIP entity is either a node, which is itself the server, or a gateway at the edge of the vehicle network. Vector's account of the gateway is the workshop case. The tester sends one request, containing the service and the logical address of the control unit it wants. The gateway takes the diagnostic packet out and puts it on the bus that control unit actually lives on. Vector's example for CAN is an identifier such as 600 hexadecimal for the request and 700 hexadecimal for the response. Those two numbers are the example in the note. They are not a map of every car. When the response comes back, the gateway returns it with that control unit's logical address, so the tester can match it. The note says this lets the tester have requests outstanding for several control units, on different buses, without waiting for each one in turn.

The German article's second advantage over ISO-TP is this point, stated as a property of TCP: separate diagnostic streams do not have to share one flow-control conversation. TCP gives each tester socket an ordered, reliable byte stream, and the alive-check rules above are what happen when the gateway runs out of sockets. The logical address is what keeps two control units apart inside one stream. ISO-TP, on the ISO-TP page, does the equivalent job with CAN identifiers and a flow-control frame, and it does it on a bus whose legislated on-board-diagnostic rate is given as 500 kbit/s in the Sofia summary cited on the protocols page.

The edge node is why a DoIP session can still be slow. The hop from the tester to the gateway is 100BASE-TX, 100 Mbit/s. The hop from the gateway to a body controller can still be CAN, CAN FD, LIN or FlexRay. Vector's note is that the gateway has to know both the logical address and the message identifiers on that inner bus. A large programming download goes quickly only for the part of the path that is actually Ethernet. A control unit behind a 500 kbit/s CAN segment still receives its bytes at that segment's pace.

The workshop socket

ISO 13400-4 puts the Ethernet on the connector of ISO 15031-3, the same 16-pin shell as emissions diagnosis. There are two assignments. The standard's own summary says option 1 matches cars already on the market and avoids a clash with manufacturer use of pins 1 and 9, and option 2 avoids a clash with pins 3 and 11. Obdtester publishes the pairs as follows. The doipclient primer uses the same two options and adds pin 8 as the activation line on both.

PinOption 1Option 2
1Receive, positive
3Receive, positive
8Activation, in the doipclient primerActivation, in the doipclient primer
9Receive, negative
11Receive, negative
12Transmit, positiveTransmit, positive
13Transmit, negativeTransmit, negative

A car uses one option. The primer's detection method is to sense the resistance between pin 8 and pin 5, signal ground, and then apply 5 V to pin 8 to ask the edge node to enable the Ethernet. ISO 13400-3 is the document that specifies activation and deactivation. The resistance values and the timing are in that standard. They are not copied here. Obdtester's DoIP columns do not list pin 8 at all, which is why the ports page says pin 8 has no entry in those columns. The activation function is the primer's reading of part 3, not a third data pair.

The emissions pins can still be populated on the same shell. Pins 6 and 14 remain the place ISO 15765-4 puts CAN, and pins 4, 5 and 16 remain ground and battery, on the ports page. A contact in pin 1, 3, 11, 12 or 13 on a car of this generation may be the Ethernet pair. It may also be an older manufacturer signal. The two published options say which pair is which once the car is known to be using that option. They do not identify a contact on a car that has not been identified.

The primer gives BMW's ENET cable as an apparent example of option 1. That is the primer's observation, not a BMW wiring diagram. The same page says that, away from the legislated diagnostic connection, a manufacturer may deviate, including with its own encryption, and that a production control unit may ignore a tester whose MAC address is not one it expects. A PC Ethernet port still needs an adapter that lands the two pairs and the activation line on this shell. EverybodyWiki's claim that the hardware vehicle-communication interface disappears, and that any RJ-45 will do, describes the case where that adapter is only a cable and the PC speaks 100BASE-TX itself. Workshop interfaces on this wiki that still sit between the computer and the socket, and that name DoIP, include the Bosch KTS 560, the Scanmatik 3, and the Mercedes-Benz pages for XENTRY and the STAR and XENTRY multiplexers. The PassThru directory is the wider list of interfaces. A fitting plug does not say which of the two pin options, or which logical addresses, that car implements.

The rate, and what it does not change

The German article's comparison with ISO-TP is a higher gross data rate, and greater robustness between parallel diagnostic streams because the transport is TCP. EverybodyWiki states the rate as 200 times higher, and states the gross figure as 100 Mbit/s. The 100 Mbit/s is the line rate of 100BASE-TX, which is what part 3 specifies. The factor of 200 is the arithmetic of that line rate against 500 kbit/s. The 500 kbit/s figure is the legislated CAN on-board-diagnostic rate in the Sofia summary already used on the protocols page, not a property written down in ISO 13400. Classic CAN also runs at 1 Mbit/s on other networks, which would make the same comparison a factor of 100, and CAN FD is faster again. Framing takes a share of both line rates. The useful comparison Vector actually draws is programming time: Ethernet has been attractive for flashing because the cycle is shorter in the factory and in the workshop. That saving applies to the Ethernet hop.

Moving the same service from CAN to DoIP changes the wire and the time a large transfer takes. ISO 14229-1:2020 names ISO 13400-2 as the transport when those services run over IP, and it does not change the data record the server was built to return. A preparation log still has to name the service and the identifier. A faster link does not raise the rate at which the control unit calculates the value. The protocols page is that distinction, and it is unchanged by the socket being Ethernet.

What the public articles currently say

Checked on 13 November 2026, English Wikipedia has no article at the title DoIP, and no article at Diagnostics over Internet Protocol. A draft URL of that title also returned nothing. The English Unified Diagnostic Services article lists Ethernet, cited as ISO 13400, among the links UDS can use, alongside CAN, LIN, FlexRay and K-line, and it says that in practice UDS is most often Diagnostic over CAN, ISO 15765. The English vehicle-to-everything article uses DoIP as the example of remote diagnostics under vehicle-to-cloud.

The dedicated Wikipedia article is the German one. It is short. It identifies DoIP as ISO 13400-2, places UDS on the application layer and TCP, UDP, IP and Ethernet under it, and gives the two advantages over ISO-TP summarised above. Its physical-layer sentence is the OABR citation discussed in the layers section. The German vehicle-diagnosis article has a table of hardware, transport and service. One row is Ethernet, DoIP as ISO 13400, UDS as ISO 14229, with BMW named in the manufacturer column. The article says the table is incomplete and still needs other manufacturers. A single named cell is not a statement that other manufacturers do not use the transport.

The Spanish Unified Diagnostic Services article says UDS usually runs on ISO-TP when the medium is CAN, and on DoIP, ISO 13400, when it runs on Ethernet. Searches of the French, Japanese and Russian Wikipedias in this pass returned Unified Diagnostic Services, Keyword Protocol 2000 and ODX articles, not a DoIP article.

EverybodyWiki's page is the longest of the encyclopaedia texts. It says it was copied from a Wikipedia draft. It places DoIP across the first four layers, adds SAE J1939-73 to the list of upper protocols, states the 200-times figure and the RJ-45 connector, and says a hardware vehicle-communication interface is no longer required. Those claims are recorded here against the ISO abstracts, the IANA registry and the connector standard. Where they disagree, the ISO text is the one this page follows.

Sources

  • ISO 13400-1:2011. General information and use cases. Withdrawn 30 January 2019. Enhanced diagnostics, WWH-OBD, and the service primitives of ISO 14229-2. Accessed 2026-11-13.
  • ISO 13400-1:2011 sample. The foreword's list of parts, including a part 5 then under preparation, and the contents headings for the three use cases and the connection scenarios. Accessed 2026-11-13.
  • ISO 13400-2:2025. Third edition, 13 June 2025. Mandatory and optional features, and the note that a revision has since been opened. Accessed 2026-11-13.
  • ISO 13400-2:2025 preview. ANSI. Protocol version 4, the incorporation of amendment 1 of 2023, the layer diagram, and the contents headings for DHCP, TLS, the internal tester and the sessions. Accessed 2026-11-13.
  • ISO 13400-2:2019. Second edition. TLS already optional. Withdrawn 13 June 2025. Accessed 2026-11-13.
  • ISO 13400-2:2019/Amd 1:2023. Published 24 July 2023. Withdrawn into the 2025 edition. Accessed 2026-11-13.
  • ISO 13400-3:2016. 100BASE-TX vehicle interface, discovery, activation and deactivation, two pin assignments. Accessed 2026-11-13.
  • ISO 13400-4:2016. Connector based on ISO 15031-3. Option 1 and the clash with pins 1 and 9. Option 2 and the clash with pins 3 and 11. Accessed 2026-11-13.
  • ISO 14229-5:2022. Unified diagnostic services on IP. Accessed 2026-11-13.
  • Specification of Diagnostic over IP. AUTOSAR Classic Platform R20-11, document 418. Header, payload types, announcement, routing activation, alive check and diagnostic message. The worked version byte is 02 hexadecimal. Accessed 2026-11-13.
  • packet-doip.c. Wireshark. Version labels, payload names, activation codes, power mode, acknowledgement codes, and TCP 3496 as the TLS port the dissector registers. Accessed 2026-11-13.
  • Service name and port number registry. IANA. doip-data on TCP 13400 and doip-disc on UDP 13400, registered 26 January 2011. Accessed 2026-11-13.
  • DoIP. Vector Certification, Ethernet learning module, last modified 7 October 2021. Transport rather than a diagnostic protocol, UDP and TCP, gateway, logical address, and the CAN identifier example. Accessed 2026-11-13.
  • OBD2 connector. Obdtester / SECONS. The two DoIP pin columns. Pin 8 is not in those columns. Accessed 2026-11-13.
  • Automotive Ethernet primer. python-doipclient. Pin 8 activation at 5 V, resistance sensing against pin 5, the BMW ENET observation, DHCP, and 100BASE-T1 between control units. Accessed 2026-11-13.
  • DoIP communication. Eclipse openSOVD Classic Diagnostic Adapter. Routing-activation handling, including code 07 hexadecimal as the TLS fallback. Accessed 2026-11-13.
  • DoIP and ISO 13400. Diadrom, Jonas Hellberg, 28 June 2026. States TCP 3496 as the TLS port from the 2019 edition. Accessed 2026-11-13.
  • DoIP. German Wikipedia. The short article: UDS over TCP/IP, the OABR physical-layer sentence, and the comparison with ISO-TP. Accessed 2026-11-13.
  • Fahrzeugdiagnose. German Wikipedia. The communication table, with Ethernet, DoIP and UDS, and BMW in that row. The article says the table is incomplete. Accessed 2026-11-13.
  • Unified Diagnostic Services. English Wikipedia. Ethernet, ISO 13400, as one of the links UDS can use. Accessed 2026-11-13.
  • Vehicle-to-everything. English Wikipedia. Remote vehicle diagnostics (DoIP) as a vehicle-to-cloud example. Accessed 2026-11-13.
  • Unified Diagnostic Services. Spanish Wikipedia. UDS on ISO-TP for CAN and on DoIP for Ethernet. Accessed 2026-11-13.
  • Diagnostics over IP (DoIP). EverybodyWiki. The draft-style page: four OSI layers, the 200-times claim, RJ-45, and the claim that a vehicle-communication interface is unnecessary. Accessed 2026-11-13.