Order before 16:00 on business days? Shipped the same day!

Fast & reliable shipping throughout Europe

Expert customer service with professional advice

Mega Sale: Discounts up to 75%! While supplies last!

View Offers

Guide for OBD diagnostic equipment for professionals

OBD Diagnostic Equipment - Gids voor OBD-diagnostische apparatuur voor professionals

AsTools |

Updated on: 2026-01-01

This article provides a technical, practical guide for workshops and fleet managers who want to work efficiently with modern vehicle diagnostics. You will learn which protocols, functions, and safety aspects play a role, how to systematically approach faults, and how to ensure reporting. Includes a clear step-by-step plan, answers to frequently asked questions, and references to relevant equipment and tools.

Table of contents

  1. Introduction
  2. OBD diagnostic equipment: specifications and application scope
    1. Connectivity and protocols
    2. Coverage and licenses
    3. Data access and functions
    4. Security and data management
  3. Step-by-step plan: from connection to reporting
  4. Frequently Asked Questions (FAQ)
    1. What is the difference between EOBD/OBD-II and manufacturer-specific diagnostics?
    2. Do I need CAN-FD or DoIP for recent vehicles?
    3. Can I code or program with a generic scan tool?
  5. Closing remarks
  6. About the author

Introduction

Vehicles contain dozens of electronic control units that communicate with each other via various network protocols. Without appropriate tooling, troubleshooting is time-consuming and uncertain. With professional OBD diagnostic equipment, you get structured access to system information, fault codes, live data, and function tests. This article covers the technical basis, the functional scope, and a robust approach for reproducible diagnosis.

OBD diagnostic equipment: specifications and application scope

Connectivity and protocols

A modern diagnostic device communicates via the 16-pin DLC in the vehicle. Support for EOBD/OBD-II includes standard protocols such as ISO 15765-4 (CAN), ISO 9141-2, and ISO 14230 (KWP2000), plus legacy SAE J1850 PWM/VPW where relevant. For newer platforms, compatibility with CAN-FD (higher data rates and longer payloads) and DoIP (Diagnostics over Internet Protocol, ISO 13400) is essential. Manufacturer-specific diagnosis often runs on UDS (ISO 14229) on top of CAN or Ethernet. A stable Vehicle Communication Interface (VCI) with USB, Bluetooth, or Wi-Fi, galvanic isolation, and automatic protocol detection increases reliability. For pass-thru work in OEM environments, J2534 compatibility is relevant.

Coverage and licenses

Generic EOBD covers emission-related data from the engine control unit. For transmission, ABS/ESP, airbag, body, ADAS, and comfort modules, brand-specific access is required. That access depends on licenses, updates, and the scan tool's dataset. Check active brand packages, the update policy, and whether functions like service reset, EPB, DPF regeneration, BMS registration, and SAS calibration are available. A multi-brand scan tool like the CRP919X BT combines broad coverage with advanced special functions across many model years and models.

Data access and functions

Standard EOBD functions follow SAE J1979: request DTCs (Mode 03/07/0A), freeze frame (Mode 02), current data (Mode 01 PIDs), and on-board monitor statuses (Mode 06). Manufacturer-specific typically offers more extensive data streams, higher sampling frequencies, component activation, and adaptations. UDS services such as ReadDataByIdentifier (0x22), DiagnosticSessionControl (0x10), and SecurityAccess (0x27) determine the depth. Professional devices log CSV or graphs, can plot multiple PIDs synchronously, and support comparison views. For electrical investigation in circuits, an additional circuit tester like the PowerScan PS100 is useful to verify power, ground, and load without dismantling components.

Security and data management

New vehicles use security gateways (SGW) that authorize access. Authentication can occur via manufacturer portals or tokens. Consider rights models per function, especially for actuator control and configuration. Power supply is crucial: a stabilized battery voltage prevents session interruptions and data corruption during long diagnostics or service functions. Check battery condition beforehand with a suitable battery tester. Document data access according to privacy legislation: store VIN, DTCs, and test reports in secure systems and minimize personal data.

Step-by-step plan: from connection to reporting

  1. Determine the task. Note customer complaint, conditions, and reproducibility. Define involved systems (e.g., powertrain, brakes, comfort, or ADAS) and expected protocols.
  2. Choose the interface. Check if the VCI supports CAN-FD and DoIP if the vehicle is recent. Use a wired connection for firmware activities; wireless suffices for diagnostics and data logging.
  3. Stabilize the power supply. Measure battery voltage and internal resistance. Confirm charging support during long sessions. A short pretest with an battery tester reduces the risk of interruptions.
  4. Connect to the DLC. Inspect the connector and pins. Turn the ignition to the correct position (KOEO or READY for EV/HEV). Verify that the scan tool correctly auto-detects the protocol.
  5. Identify the vehicle. Read VIN (Mode 09 or UDS) and build data. Let the scan tool scan modules and save the vehicle file with mileage and date.
  6. Read DTCs. Separate active and stored codes. Note freeze frame. Record environmental conditions (coolant temperature, engine speed, load) to maintain context.
  7. Analyze live data. Select relevant PIDs. Set sample frequency and graphical display. Compare left and right side signals where applicable (e.g., wheel speeds).
  8. Perform function tests. Activate actuators or subsystems where safe. Use the manufacturer's test sequences. Stop the test at illogical values or voltage drops.
  9. Investigate electrical paths. Confirm power and ground points with a test probe or circuit tester. A logical sequence is: fuses, relays, ground, signal, load. The PowerScan PS100 enables quick voltage drop tests.
  10. Perform service functions in a controlled manner. Think of DPF regeneration, EPB service position, steering angle sensor calibration, injector coding, or battery registration. Ensure stable voltage and follow instructions step by step.
  11. Repair and verify. Repair or replace components. Clear DTCs. Perform a test drive under similar conditions. Scan again and confirm that monitors are ready and faults remain absent.
  12. Report and archive. Generate a clear report with DTCs, graphs, and any photos of measurements. Archive in the workshop management system for repeatability and audits.

Frequently Asked Questions (FAQ)

What is the difference between EOBD/OBD-II and manufacturer-specific diagnostics?

EOBD/OBD-II provides access to emission-related data from the engine ECU via standardized modes and PIDs. Manufacturer-specific diagnostics unlock additional control units (transmission, ABS/ESP, airbag, BCM, ADAS) and functions such as actuators, adaptations, and codings. This requires a dataset that varies per brand and model and is regularly updated.

Do I need CAN-FD or DoIP for recent vehicles?

More and more platforms are switching to CAN-FD for higher bandwidth and to DoIP for diagnostics via Ethernet. For access to new control units, faster data logging, and certain service functions, support for these technologies is desirable. When in doubt, a multi-brand scan tool with CAN-FD and DoIP is more future-proof.

Can I code or program with a generic scan tool?

Coding and adaptations are often possible within manufacturer-specific functions of multi-brand tools. Full software programming (flashing) usually requires J2534 pass-thru and an OEM subscription. Additionally, security gateways may require extra authorization. Check the regulations per brand to avoid interruptions and risks.

Closing remarks

A reproducible diagnostic process starts with the right interface, stable power supply, and clear documentation. Combine generic EOBD tools with brand-specific functions when the fault requires it. By consistently following protocols, data flows, and test sequences, you reduce repeat visits and increase technical certainty. View the current selection in the collection diagnostic tools and choose equipment that matches your vehicle mix and work processes. Finally: work systematically, ensure safety, and archive every result. This keeps your workshop efficient and demonstrably careful.

About the author

AsTools supports workshops and fleet managers with equipment and knowledge around vehicle diagnostics, electrical measurements, and workshop processes. We combine product expertise with practical workflows, so you get to the core faster. Feel free to contact us for substantive questions or tailored advice.

The content in this blog post is intended for general information purposes only. It should not be considered as professional, medical, or legal advice. For specific guidance related to your situation, please consult a qualified professional. The store does not assume responsibility for any decisions made based on this information.