Automatic diagnosis: one tap and it explains
The tool detects the vehicle and its protocol, identifies it, reads every control unit and tells you in plain words what is wrong and what to do.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Remote sessions › Diagnosis › Automatic diagnosis, and in the app, Vehicles › Diagnose
- Plug the ECO-LITE into the diagnostic connector, switch on the ignition and tap “Diagnose”.
- Detect vehicle: the tool listens to the vehicle and tries, in this order and only with read requests, CAN (500 and 250 kbit/s), K-line, J1850 if your tool has it, J1939 on heavy vehicles and DoIP if there is Ethernet. It takes a few seconds.
- Identify: the VIN fills in the vehicle sheet (make, model, year and engine). Without a VIN you see what could be deduced: protocol, control units and vehicle type.
- Read control units: the tool reads the faults of every control unit, the inspection readiness and the key data. Meanwhile you see live what the tool is doing, with a progress bar: the protocol it found, whether it has the VIN and the control unit it is reading (for example, “Reading control unit 5 of 12: …”).
- Result: a traffic light (all good, some things to check or serious faults) and the list of problems with their severity, what each one means and what to do.
- Motorcycles: for a motorcycle the result adds “Your motorcycle”: the connector and how to wire it to the tool, the protocol and, for reading faults, live data, clearing faults and service, which procedure does it and what is missing. It is chosen from the make, model, year and what the motorcycle answered (Hondas too, over their K-Line). No motorcycle procedure has been tested on a real motorcycle yet.
- If nothing is detected, check the connector and the ignition, choose the vehicle type and tap “Read anyway”.
- If the tool sends no news for a while (poor coverage, for example), the screen says so and keeps waiting: the result still arrives.
- If your tool cannot handle something (J1850, J1708 or DoIP), you are told and the tool that can is recommended.
- From the result you can clear the faults (with confirmation and the second factor), see the full report and sign it, ask a workshop or expert for help and see the recommended procedures for that vehicle.
- Each step stays in the list of reads as an ordinary read. If you prefer to choose the vehicle type yourself, use “Read vehicle”.
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
- 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
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates