National Instruments - NI Automotive Diagnostic Command Set

Diagnostic and transport protocols

Because CAN networks use small 8 B frames for communication, you need higher-level protocols for consistent communication of longer messages and standardization of message definitions for diagnostics. You can use the ISO transport protocol and Volkswagen Transport Protocol 2.0 for underlying communications to ECUs. With a transport protocol established, you need a diagnostic protocol for defining which messages correspond to particular functions.

Flexible interface options

ADCS works with NI USB CAN interfaces to help you implement a variety of portable and in-vehicle diagnostic applications. Applications that benefit from ADCS include ECU firmware flashing tools, DTC reading and logging, ECU diagnostic mode interfaces, and live diagnostic variable monitoring and logging for on-road tests. You can duplicate and deploy applications developed with ADCS and NI CAN hardware throughout an organization for a fraction of the cost of comparable off-the-shelf tools.

LabVIEW real-time support

With LabVIEW real-time support, you can use ADCS for high-performance diagnostic applications requiring integration with other systems such as those found in automotive engine and chassis dyno testing as well as other stationary applications. LabVIEW real-time is an ideal operating system for applications requiring high reliability, longevity, and determinism.

Protocol flexibility

While ADCS is designed to work with standard implementations of KWP2000 and Diagnostics on CAN, you can customize ADCS for nonstandard requirements in both the transport and diagnostic protocol layers. LabVIEW source code is provided for most transport and session functions, so you can modify ADCS for your specific application requirements.