How to diagnose each type of vehicle

Where: Remote sessions › Diagnosis › Service functions › Channel “v2 procedures (beta)” › “One-click full diagnosis”

If you do not know which procedure to choose, use “One-click full diagnosis”. You choose the type of vehicle and the tool runs the right steps one after another: detect the protocol, scan the control units, the health report, the fault codes with their description and the key data. At the end it gives you a single report for the customer. Everything is read only: it does not clear fault codes or change anything in the vehicle.

1. Connect the device to the diagnostic connector and switch the ignition on. On a boat, switch on the NMEA 2000 network.
2. Press “One-click full diagnosis” and choose the type of vehicle (“Car or van”, “Motorcycle”, “Truck or bus”, “Tractor or farm machine” or “Boat”) and the device.
3. Enter the vehicle details. Under “What it will do” you see each step and, if one cannot be done with your device or your catalog, the reason.
4. Press “Start the full diagnosis”. If a step asks for something (for example, switching the ignition on), answer on the screen. “Stop after this step” ends when the current step finishes.
5. At the end you see the “Diagnosis report”: the overall result, the fault codes with their description and what the control unit indicates, the checks and the key data. “Print or save as PDF” saves it for the customer; “See the details” opens each step.

Only for cars and vans there is an optional checkbox, unticked: “Add “Safety and accident””. It confirms that the owner consents or that there is an official order. At the end it adds a read-only reading of the identification, the vehicle number, who programmed each control unit last and when, and how many faults it stores. It does not deploy, erase or write, and it reads no secret codes or keys. The airbag and the crash recorder are read afterwards, one by one, with the “Forensic reading” procedures (their names start with “Faults with their status”, “Full identification” or “Programming trace”).

Save and compare: “Save result” keeps the report in the organization's history as the control units sent it. To find the same vehicle later, first choose the organization's vehicle or type the VIN and press “Fill in from the VIN”: make, model and year come from the vehicle sheet or the VIN, you see where each value comes from and you can change them. The full VIN is not stored. “History and comparison” compares the result with the previous one of the same vehicle: faults no longer listed (only if their control unit answered), new ones and those that remain. A fault that is gone does not prove the repair. After the protocol is detected, if the make has its scan of every control unit, “Full scan for the make” appears. A saved result can be attached to a work order and appears in its signed report.

1. What it does on each type of vehicle

2. How to read the fault codes of the report

• Description: for generic codes (P0, P2, P34 to P39, B0, C0, U0 and U3) it is the one of the SAE J2012-DA library; on trucks, tractors and boats (SPN and FMI), the one of SAE J1939-DA. It is shown in your language. The manufacturer's own codes (P1, B1, C1, U1…) have no generic description.
• Library severity: it is a guide, to order the work in the workshop.
• “What the control unit indicates”: what the control unit itself sent with the fault code. “Asks to stop and check now” is the red stop lamp or “check immediately”; “Requests a warning light: check soon”, the malfunction indicator lamp, the amber or protect lamp, or “check at the next stop”; then come “Confirmed or pending: check” and “Only stored in memory”. Classic OBD fault codes only give the code: you will see “The control unit gives no more data”.
• The report does not add causes or repairs that do not come from a source: for that, check the manufacturer's manual.

3. If you prefer to choose the procedure yourself

• Car: “Detect the vehicle's OBD protocol” says which variant answered. If it is OBD on UDS, use the procedures that start with “OBDonUDS”, such as “OBDonUDS: full pre-inspection (lamp, monitors, trouble codes and recent clear)”.
• Real-world consumption: “real-world fuel and energy consumption (OBFCM)” reads the real consumption counters the EU requires on new cars and vans; on plug-in hybrids, also the energy charged from the grid.
• CAN network: “CAN network check (pins 6/14)” is for when the control units do not answer or there are U0 fault codes: it listens to the network without transmitting, finds the speed and counts frames and errors.
• Euro 5 motorcycles: “Euro 5 motorcycle: quick check (warning lamp, monitors, faults and VIN)” reads it in one short pass. The variants that end in “(K-Line, …)” are for motorcycles without CAN.
• Trucks and buses: start with “Scan all truck ECUs (J1939): who is who and their trouble codes” and continue with “Truck and bus HD OBD inspection (J1939-84, read)”.
• Tractors and machines: “Machine health: every ECU and implement with codes, lamps and hours, with a verdict” gives a verdict for each control unit and implement.
• Boats: “Boat health (NMEA 2000): all engines, power and alarms” listens for about 32 seconds without transmitting, after you confirm the safety conditions.

This one-click diagnosis only reads: it is what can run unattended. To repair or adapt (reset soot or ash, forced regeneration, adapt after replacing a part) use the service functions one by one: that is diagnosis mode. If a forensic case file is open for the unit, forensic mode (read only) applies until you close it or register an intervention. More in “Forensic mode and diagnosis mode”.

Important: The procedures are still being tested: always compare the result with the manufacturer's manual. Diaglana has no J1850 (some older Ford and GM vehicles) and vehicles with another connector (motorcycle, truck with a 9-pin connector, ISOBUS or NMEA 2000) need an adapter cable.

Open the platform See it in the help centre