Diagnostics over IP (DoIP)
Diagnostics over Internet Protocol (DoIP) requires diagnostic communications to use IP, TCP, and UDP protocols on an ethernet network. A vehicle with DoIP typically has one "edge node" ECU to transfer all diagnostic messages between a test tool on ethernet and other ECUs on other networks like CAN, LIN, FlexRay, etc. Requirements for DoIP are defined in ISO 13400. Use Vehicle Spy's Diagnostics over IP (DoIP) to discover and connect to an edge node ECU, which then allows Diagnostics to be sent to other ECUs on the vehicle. The DoIP connection can be setup to run manually or automatically after each time Vehicle Spy goes online with hardware. DoIP is opened from the Spy Networks menu.
Making a DoIP Connection Has 2 Phases - Discover then Connect
Follow these steps to make a Vehicle Spy DoIP connection to a vehicle:
Connect DoIP capable ICS hardware (like FIRE2) to the vehicle data link connector and PC USB.
Verify Tools > Options > Spy Networks tab has "Use PC Ethernet interface" = ON.
In TCP/IP view, set the MAC address = Inherit from device and IP address = Inherit from OS.
In DoIP, verify the Assert activation line at start checkbox is enabled.
Take VSpy online with the ICS hardware from step 1.
In DoIP, click Refresh vehicles. A vehicle should appear in the response table with status "Disconnected".
Click on the vehicle then Connect to selected vehicle -> Connect -> Default diagnostics. The vehicle status should change to "Connected".
Diagnostics can now be used to send DoIP jobs to specific ECUs.
Details of Settings
0E00 - 0E7F Legislated diagnostic test tools that run emissions tests.
0E80 - 0EFF Aftermarket test tools. VSpy usually belongs in this range.
0F80 - 0FFF Prolonged data loggers, like those used by insurance companies.
Auto Connect
First available vehicle - the first vehicle that responds.
By IP - the edge node ECU that has this IP address.
By VIN - the vehicle that has this Vehicle Identification Number.
By EID - the edge node ECU that has this Entity Identification (i.e. MAC) address.
Enable reconnect on error will make Vehicle Spy retry the DoIP connection if an error occurs during the linking process. Routing type supports the following authentication/confirmation methods for the DoIP linking process:
Default diagnostics - default method per ISO 13400.
WWH-OBD - World Wide Harmonized On-Board Diagnostics method per ISO 27145.
Central security - secured linking method as defined by each OEM.
DoIP Status Table
Table 1: DoIP Status Table
Table Column | Description |
---|---|
IP Address | IP address of the edge node ECU. |
VIN | Vehicle Identification Number of the vehicle. |
Logical Address | Logical address of the edge node ECU. |
Entity Identification | MAC address of the edge node ECU. |
Group Identification | An identifier used in place of the VIN if the VIN is not programmed yet. |
Action Required? | If yes, then central security is required. |
VIN/GID synced? | If yes, then the edge node ECU is reporting all ECUs it sees are synchronized to the same VIN or Group ID. |
Status | Vehicle Spy's current status of the DoIP connection with the vehicle. |