Diagnosis over Ethernet (DoIP)
Which vehicles use it, which unit you need and what its notices mean.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Many recent vehicles are diagnosed over Ethernet through the OBD connector (DoIP, ISO 13400). The unit activates the vehicle's Ethernet through pin 8 of the connector, only if that pin is free.
| Unit | DoIP |
|---|---|
| ECO-LITE | Yes, with connector option 1 (pins 3/11 and 12/13), activated through pin 8. Pending tests on vehicles. |
| ECO-LITE TOOL | For PC programs through J2534 (API 05.00); it does not activate pin 8 by itself. |
| ECOPRO Gen4 | Yes, 100BASE-TX Ethernet with activation through pin 8. In development. |
| If you see… | What it means |
|---|---|
| Needs Ethernet (DoIP) | The procedure only works on a unit with diagnostic Ethernet. |
| DoIP was not tried: pin 8 of the connector is in use or not measured. | Pin 8 has another use on that vehicle: the unit does not activate Ethernet so as not to damage anything. |
| The manufacturer's certificates are needed | The vehicle asks for an encrypted connection or authentication: it cannot be used without the manufacturer's credentials. |
Tip: To start, run “Identify the vehicle (VIN, EID and GID)” or “Discover the vehicle and its entities”. They are read-only.
More guides in this section
- How a remote session works
- Tunnel plan: connect a tool to the vehicle remotely
- Accept or withdraw remote access to your vehicle
- Collaborating in a session: messages, prompts and photos
- Unit PassThru mode from the app
- PassThru on Mac, Linux and iOS
- Assistance requests, appointments and work orders
- Legacy vehicle configuration and diagnostics: VAG and other makes
- Modern vehicle coding and programming
- Automatic diagnosis: one tap and it explains
- Reading a vehicle and sharing the report
- CANopen diagnostics for machinery
- Vehicle details: identifying it by the VIN
- Live dashboard, service functions and battery test
- v2 procedures: beta and operational
- Compatibility notices for your tool
- CAN captures
- Pre-purchase report
- Battery health of electric and hybrid cars
- Asking Diaglana for help
- Your first read: understanding the result and what to do
- Diagnosis options: each setting and when to change it
- Workshop settings: requests, orders, network and notices
- Reading: choosing the protocol and understanding the OBD on UDS report
- What a fault code means
- Live data: dashboards, recording and export
- Attaching fault codes to a work order
- Procedures that write, program or authenticate
- ISOBUS: reading and changing an implement's NAME
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates