What We Support & How to Validate
Compatibility is a system outcome: vehicle ECU behavior + protocol support + device firmware + app workflow. This section explains what we support and how to validate correctly.
Catalog Models
OBD-II Protocols
Product Families
IOS + Android
Platform Support
Understanding Compatibility
Before submitting a compatibility question, review these principles that apply to all OBD-II diagnostic hardware.
Protocol support does not guarantee every function on every vehicle
OBD-II protocol coverage means the device can communicate. What data is actually available depends on the vehicle's ECU.
Supported data items vary by ECU implementation and model year
Two vehicles with the same protocol may return different PIDs, live data items, or readiness monitors.
App polling strategy and session management can impact stability
For wireless devices, how your app handles connection timing, polling intervals, and reconnection logic directly affects real-world performance.
Important: Compatibility is Not Binary
A device may communicate successfully on one vehicle but return different data sets on another — even if both use the same OBD-II protocol. Always validate with real vehicles before committing to a production program.
Need a Compatibility Check?
Submit your vehicle and workflow details. We'll recommend the right model and provide an evaluation checklist.
English