Scribd
Upload
258 views23 pages

Do IP

This document discusses diagnostics over IP (DoIP) as an alternative to diagnostics over CAN (DoCAN) as vehicles transition to using Ethernet networks. It explains that DoIP follows the same diagnostic process as DoCAN but uses TCP/IP and Ethernet instead of CAN. It also introduces socket adaptors that allow diagnostics to target ECUs directly over Ethernet through the use of protocol data units. Vehicle Spy is highlighted as a tool that handles all the complexities and allows performing diagnostics over different network types in the same way.

Uploaded by

khallouli.slim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
258 views23 pages

Do IP

This document discusses diagnostics over IP (DoIP) as an alternative to diagnostics over CAN (DoCAN) as vehicles transition to using Ethernet networks. It explains that DoIP follows the same diagnostic process as DoCAN but uses TCP/IP and Ethernet instead of CAN. It also introduces socket adaptors that allow diagnostics to target ECUs directly over Ethernet through the use of protocol data units. Vehicle Spy is highlighted as a tool that handles all the complexities and allows performing diagnostics over different network types in the same way.

Uploaded by

khallouli.slim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

Diagnostics over IP and

Socket Adaptor Diagnostics


Brought to you by
Intrepid Control Systems, Inc.
A World Without CAN
• Automotive network topologies
are moving away from CAN
• Increasingly, more vehicles are
Ethernet only
– Or, partially Ethernet
• Need a way to do diagnostics
– …But how? I think I’ll miss you most of all,
CAN diagnostics!
Diagnostics Over IP
• Retcon: what we have now is “DoCAN”, i.e. Diagnostics
over CAN
• Diagnostics over IP (DoIP)
– ISO 13400
• DoIP is exactly the same
– Except where it’s different
• Replace ISO 15765-2 and ISO 11898 with TCP/IP and
Ethernet
Stack Comparison
DoCAN DoIP
OSI Standard OSI Standard
Application (Layer 7) ISO 14229-1/5 Application (Layer 7) ISO 14229-1/5
Presentation (Layer OEM specific Presentation (Layer OEM specific
6) (J1939, etc.) 6) (J1939, etc.)
Session (Layer 5) ISO 14229-2 Session (Layer 5) ISO 14229-2
Transport (Layer 4) ISO 15765-2 Transport (Layer 4) ISO 13400-2 (TCP)
Network (Layer 3) ISO 15765-2 Network (Layer 3) ISO 13400-2 (IP)
Data Link (Layer 2) ISO 11898 (CAN) Data Link (Layer 2) ISO 13400-3
(Ethernet)
Physical (Layer 1) ISO 11898 (CAN)
Physical (Layer 1) ISO 13400-3
(100BASE-TX)
Activation and Wiring
• DoIP uses regular 4-wire Ethernet (100BASE-TX)
– Not meant for on the road use (EMC issueS)
– Need a way to disable this when not used
• Uses fifth “activation” line – simple on/off signal
– When not asserted all of the DoIP circuitry should be off
• Once activation line > 5 V, 200 ms to boot up
Activation and Wiring
OBD
DoIP Terminology
• DoIP edge node: Node inside the vehicle where the
activate line terminates; main gateway
• Subnetwork: Internal network not directly connected to
an IP network (i.e. CAN)
• Logical address: Two-byte value that identifies a particular
node
• Test equipment: An external tool like the neoVI
Example DoIP Network
DoIP Discovery
• DoIP has a UDP based discovery protocol
• Remember: multiple vehicles can be on the network!
– Factory setting: access all vehicles off the line from your desk!
• Can do VIN <-> IP address lookup
DoIP Connection
• Once you have discovered 1. Discover vehicle
vehicle, open TCP connection! 2. Open TCP connection to vehicle
• Before we can do diagnostics, on port 13400
need “Routing activation” 3. Send Routing Activation
– Optional, OEM-specific 1. Optional: Authenticate
authentication can go here 4. Begin diagnostics!
• Typical flow —>
Vehicle Spy
• DoIP view in Vehicle Spy will do all this for you!
Diagnostic Messages
• Once connected,
regular ISO 14229
(UDS) diagnostics
performed over
socket
• All the jobs you
know and love ($22,
$27, etc.) are the
same
Socket Adaptor Diagnostics
• What if we’re behind the DoIP edge node?
• Need to do diagnostics to target ECU directly
• Normally we would just use CAN
– But what if this ECU is Ethernet only?

• Socket Adaptor (SoAd) is an AUTOSAR module that turns


TCP/IP sockets into PDU-oriented communication
Socket Adaptor Diagnostics
• PDUs are like CAN Ethernet

messages IPv4 / IPv6


– Encapsulate one “piece”
TCP / UDP
of information
PDU ID PDU Length Data
• SoAd module handles
connections, multiplexing PDU ID PDU Length Data

PDUs across sockets … … …


Socket Adaptor Diagnostics
• Create a special PDU that holds UDS messages
• Then, we can do diagnostics by directly connecting to ECU
– Bypass DoIP module entirely
• Requires OEM support – not directly standardized
Vehicle Spy
• Good news – you don’t need to
know any details in Vehicle Spy
• Simply pick diagnostics layer on
job
– Everything “just works”
• Assuming you have the databases, of
course
• If you’re used to diagnostics in
Vehicle Spy, exactly the same
Vehicle Spy (CAN)
Vehicle Spy (DoIP)
Vehicle Spy (SoAD)
DoIP diag request
CAN diag request
Vehicle Spy
DoIP client CAN diag response
Vehicle Spy
Edge node simulator DoIP diag response

Ethernet

ISO 14229
ECU
USB
CAN + Ethernet
CAN

neoVI FIRE 2
Questions?
Discover more at www.intrepidcs.com
Or contact us at:
Sales:
[email protected]
+1 (586) 731-7950 x 2

Technical Support:

[email protected]
www.intrepidcs.com/support
+1 (586) 731-7950 x 1
Thank
You!

You might also like