How to Access to OBD Data with Indigo
In Vector Tools, OBD data are indeed diagnostic parameters that are not described in a network description file (DBC, FIBEX, ARXML) like usual signals but in an internal, standard specific diagnostic description (internal encrypted CDD). In the vehicle network, the OBD data is transmitted, in responses sent by the ECU after the test tool has previously sent a corresponding diagnostic service request.
Vector CANoe supports OBD use cases, namely OBD II (SAE J1979/ISO15031), and an interactive OBD II windows. No CAPL build-in support for OBD is available at the moment.
Indigo is Vector’s versatile diagnostic tester. In addition to CANoe scope for OBD, Indigo supports some more use cases. The comprehensive Indigo support for OBD includes OBD II (SAE J1979 / ISO15031), WWH-OBD (ISO27145) and HD-OBD (SAE J1939-73). Indigo offers a ready to use diagnostic tool box with live data and graphical live data tools that automatically send the OBD Service Requests corresponding to the expected OBD data. The user might choose between one of three possible update rates: Slow, medium and fast.
The measured values can be symbolically logged into CSV-files or MDF-files (from
Indigo 6 on) to be processed later by further tools. They can be combined with signals out of network description files and also with parameters out of OEM specific diagnostics descriptions (ODX/PDX or CDD). The user interface is very flexible and easy to be configured. A remote access to the vehicle is also possible with Indigo Remote. Indigo also supports the recording of scripts and the automated access of the full OBD features (including protocol variations) from .NET snippets.
With Indigo the Communication with the vehicle can be established via CAN (FD), K-Line or DoIP (ISO 13400-2:2012) and a network interface (Vector, PassThru or D-PDU API-based interface).