Doip test development practice

DoIP brief introduction

Ethernet was first developed by BMW Into the car , Its application scenario is to brush , Meet similar HMI Map data 、 LCD instrument and other software data update , Interested parties may refer to Thomas Konigseder Of Automotive Ethernet The introduction in the book . Because of its outstanding characteristics , Then get the main OEM And more widely used , Then began international standardization （ The automotive industry has always been “ tricks ”）.

DoIP Full name ：Diagnostic communication over Internet Protocol. seeing the name of a thing one thinks of its function , Vehicle diagnosis is realized through Ethernet , The corresponding international standard is ISO 13400, It is defined. DoIP agreement （ be based on UDS） The flow of diagnosis data interaction between external test equipment and vehicle is described .

The following figure for DoIP And Ethernet based diagnosis in OSI 7 Layer model and in “7 Outside the floor ” Of “ role ” and “ Location ”.

chart 1 DoIP And Ethernet diagnostic specification framework

DoIP Brief description of key points of the agreement

DoIP message
DoIP The position of the message in the Ethernet message is shown in the figure below .

chart 2 DoIP Schematic diagram of the position of the message in the Ethernet message

DoIP Messages are divided into three categories ：

• Node management class

It mainly includes header processing flow 、 Vehicle information acquisition （ Such as EID、GID、VIN etc. ）、 Route activation process （ Including authorization and confirmation functions ）、TCP_DATA socket Processing flow .

chart 3 Node management class DoIP message

• Vehicle information

It mainly includes obtaining DoIP Entity status information 、 Vehicle power mode information .

chart 4 Vehicle information DoIP message

• Diagnostic class

It mainly includes diagnostic message processing flow and UDS Data interaction .

chart 5 Diagnostic class DoIP The message shows

DoIP Conversation flow
DoIP The whole process of conversation can be divided into five steps ： Hardwired activation ( Whether the activation mechanism is adopted and the activation method is different OEM There are differences )-> Vehicle discovery process ->TCP_DATA socket Processing flow -> Diagnostic data interaction -> close TCP_DATA socket.

chart 6 DoIP Conversation flow

picture source ：ISO 13400-2:Road vehicles - Diagnostic communication over Internet Protocol (DoIP)

Differences between edges and internal nodes

About DoIP agreement ,ISO 13400 The specification makes a framework definition , but OEM The details will be customized according to the functional requirements of the whole vehicle , At the same time, it will distinguish between edge nodes and internal Ethernet nodes , Some friends may have questions here ,“ Why should Ethernet nodes distinguish between edge nodes and internal nodes ？ Whether the two can support complete DoIP agreement ？” Next, we discuss the edge nodes and internal nodes in DoIP Differences in message configuration .

Question 1 ： The internal node needs to support the positive response of diagnostic message (0x8002) Well ？

analysis ： When Tester When sending a diagnostic request to an internal node , First, the edge node will move to Tester send out 0x8002 message , If the internal node also supports 0x8002 message , Then, the edge node forwards the message sent by the internal node again 0x8002 Message and diagnostic response message to Tester.
according to DoIP agreement ,Tester Wait after sending the diagnostic message 0x8002 The message starts at the same time P6Client Timer to receive diagnostic response message ( Not for now 0x8003). So if the internal node supports 0x8002 The message does not meet the requirements in terms of system design DoIP agreement , And it will lead to Ethernet system level diagnostic brush test P6Client Parameter timeout .

chart 7 Internal nodes support 0x8002 Example of message interaction process

Question two , I throw a brick ： What strategies should different types of nodes adopt for routing activation messages ？

Interested , You can make an appointment about such technical details , Similarly, this topic can be extended to include DoIP Other messages have different configurations and support schemes for edge and internal nodes , Of course, there are the most obvious differences in the support for hardwired activation features .
All change is the same , Ethernet node DoIP The message configuration shall serve the functions of the whole vehicle , This part should be OEM Design engineers need to design from the perspective of application scenarios . opinion , Wise men see wisdom. , In different topologies 、 The design scheme should also be different under different requirements .

DoIP And Ethernet diagnosis test scheme and practice

DoIP And Ethernet diagnostic test implementation can be introduced hierarchically , Of course, in each layer OEM Will be in ISO Custom development based on standard requirements .

in the light of ISO 13400-2 Test of
The test includes DoIP Message format 、DoIP Process and DoIP Time parameters, etc , Its test script and test project passed CANoe（CAPL） Custom implementation .

chart 8 be based on CANoe Some test items and test scripts developed

chart 9 A controller Alive_Check_Message Test report

in the light of ISO 13400-3 Test of
The test contents include activation enabling line and other related tests , The test script also passes CANoe（CAPL） The development of implementation , The test environment needs the help of Vector Of VT card , Such as VT2004 Realize the simulation of hard wire .

in the light of ISO 14229-1/-5 Test of
Can be based on CANoe Option DiVa Can be realized ,DiVa yes Vector The company has a convenient 、 Efficient diagnostic test case generation tool , Use DiVa Realization UDSonCAN Everyone is familiar with the test , So for Ethernet UDS test DiVa Whether it can also cover ？ The answer is yes .DiVa Can be based on DoIP agreement （ISO 13400） Generate Ethernet UDS Test Engineering , That is, according to the standard DoIP Process and ECU Conduct diagnostic data interaction .

chart 10 be based on DiVa Ethernet UDS Test Engineering

Introduced here, the little friends may have questions , For non-standard DoIP Whether the Ethernet node of the protocol is also available DiVa Cover its test requirements ？ For example, the author once encountered OEM The defined Ethernet node only supports DoIP Specific message in payload type , Or Ethernet nodes only support OEM Self defined diagnostic message, etc .