Resources
OBD power and vehicle diagnostics: what to check
Separate the connector, device functions, vehicle compatibility and software support
An OBD connector describes a connection point. To establish which functions are available, check the specific device, vehicle and software configuration.
| Check | Question to resolve |
|---|---|
| Connector and power | Can this device fit and receive power at the vehicle connector? |
| Device and configuration | Which specific data and functions does this configuration support? |
| Vehicle | What is the make, model and year of the vehicle being checked? |
| Software | Can the platform receive and display the data needed for the task? |
Swipe horizontally to read the full table
Ask for the data you actually need
If you need a VIN, fault codes, fuel data or CAN-related information, list each requirement. A device name containing OBD does not establish support for every vehicle data item. Confirm the exact scope against the selected device and vehicle.
WYOBD uses the OBD connector for power on compatible vehicles. Confirm access, fitting space and the functions of the selected configuration. If a platform is already in place, provide its protocol requirements too.
A more useful enquiry
Describe the vehicles and the data you want to see in your software. For example: “We plan to use these vehicle models and need these data items in our existing platform. Which device and configuration should we check?” This is an enquiry example, not a compatibility result.