DiagRA® S
The right solution for pure software based diagnostic simulation.
DiagRA® S
DiagRA® S is software that simulates diagnostic communication with vehicle ECUs via the standardized diagnostic communication interfaces. It can be used for manual and automated testing of diagnostic applications as well as for training in vehicle diagnostics. DiagRA® S can either be used in software-only mode or connected to a physical bus via a communication interface and acts like an ECU / several ECUs when receiving diagnostic requests from a tester.
DiagRA® S was developed based on the experience gained in the development of RA diagnostic applications (including DiagRA® D, Silver Scan-Tool™, DiagRA® LE, DiagRA® Embedded and DiagRA® Flash Station) and is continuously updated, optimized and constantly adapted to the latest diagnostic standards.
The right solution for pure software based diagnostic simulation
DiagRA® S offers the option of performing diagnostic communication even without a physical interface, bus connection and also without ECUs. You can use it to test and validate your diagnostic software quickly and cost-effectively.
- Simulation of one or more ECUs
- Physical and functional communication
- Diagnostic communication both via the application layer (e.g. UDS, SAE J1939-73/-84) and via the transport layer (ISO-TP, SAE J1939-21, DoIP)
- Support of multiple simulation models and diagnostic interfaces
- Simulation is also possible without interface and without installation
Learn the basics with our entry-level tutorial on DiagRA® S. The following topics are covered:
- What is DiagRA® S?
- Create a simulation project with DiagRA® S
- Add data for OBD-communication from trace files
- Configure DiagRA® D for OBD-communication with DiagRA® S
- Start simulation of diagnostic communication
Feature Overview
DiagRA® S provides all the functions to simulate diagnostic communication to test and optimize your diagnostic tester.
Log files import
Quickly populate simulation models from imported diagnostic log files.
Editor for simulation files
Editor for simulation files based on configured ODX databases.
Test simulation models
A test tool for the simulation files.
Parallel simulation
Parallel simulation via multiple standardized interfaces.
Monitoring
Monitoring window for the overview of the ongoing communication.
Flexible configuration
Many setting options for communication.
Interfaces
Communication via the supplied D-PDU API, SAE J2534 or RP 1210 interface.
Communication over transport layer
Integrated support for ISO-TP (CAN, CAN FD), SAE J1939-21 (CAN), and DoIP (ISO 13400).
Command line application
Execution of the simulations as command line applications (e.g. for the automated tests).
Hardware simulation
Hardware simulation via an active connection to the physical bus.
Customizable simulation models
Multiple simulation models to define the simulated diagnostic data: from simple to configure to very detailed.
Physical communication
Physical communication via the D-PDU API interface and Ethernet (for DoIP). The enclosed RA® D-PDU API can be used as a bridge for using the interfaces with J2534 and RP 1210 interfaces.
Remaining bus communication
Simulation of the remaining network communication on the CAN bus.
DiagRA® S supports
| Diagnostic standards | ISO-TP (Raw CAN / CAN FD): ISO 15765-2, ISO 11898; UDS: ISO 14229-1, ISO 14229-3, ISO 14229-5, DoIP: ISO 13400, OBD: ISO 15765-4, ISO 15031 / SAE J1979 (OBD), ISO 27145 (WWH-OBD), SAE J1979-2 (OBDonUDS); SAE J1979-3 (ZEVonUDS), ISO 9141-1 (K-LINE), ISO 14230-4 (OBD on K-LINE), ISO 14230-3 (KWP2000 for CAN / K-LINE), SAE J1850 PWM; SAE J1939-21, SAE J1939-73/-84, SAE J1699 (OBD Compliance Test), ASAM MCD-2D (ODX), ISO 22901-1 |
| Diagnostic interfaces | SAE J2534-1 v04.04 (x86 and x64), CANFD according to SAE J2534-2; RP1210 (x86); ISO 22900-2 (D-PDU API) via the wrapper functionality of the included RA D-PDU API (x86 and x64); ISO 13400; Socket CAN |
| File formats | Import of diagnostic communication trace files from DiagRA® D and Silver Scan-Tool™, DiagLogging files (emotive OTX Runtime API), PCAP / PCAPNG files, SR files, CAN trace files from Vector (ASC) and IXXAT (TRA) as well as J1699 log files |
DiagRA® S
the simulation tool for easy diagnostic communication with all diagnostic protocols and diagnostic communication interfaces.
Technical specification
| Standards | ISO-TP (Raw CAN / CAN FD): ISO 15765-2, ISO 11898; UDS: ISO 14229-1, ISO 14229-3, ISO 14229-5, DoIP: ISO 13400, OBD: ISO 15765-4, ISO 15031 / SAE J1979 (OBD), ISO 27145 (WWH-OBD), SAE J1979-2 (OBDonUDS); SAE J1979-3 (ZEVonUDS), ISO 9141-1 (K-LINE), ISO 14230-4 (OBD on K-LINE), ISO 14230-3 (KWP2000 for CAN / K-LINE), SAE J1850 PWM; SAE J1939-21, SAE J1939-73/-84, SAE J1699 (OBD Compliance Test), ASAM MCD-2D (ODX), ISO 22901-1 |
| Diagnostic interfaces | SAE J2534-1 v04.04 (x86 and x64), CANFD according to SAE J2534-2; RP1210 (x86); ISO 22900-2 (D-PDU API) via the wrapper functionality of the included RA® D-PDU API (x86 and x64); ISO 13400; Socket CAN |
| File formats | Import of diagnostic communication trace files from DiagRA® D and Silver Scan-Tool™, DiagLogging files (emotive OTX Runtime API), PCAP / PCAPNG files, SR files, CAN trace files from Vector (ASC) and IXXAT (TRA) as well as J1699 log files. Interpretation of simulation data by means of ASAM ODX 2.0.1, 2.1.0 and 2.2.0 files. |
| Protocols | OBD, UDS, KWP2000, SAE J1939, SAE J1699, WWH-OBD, OBDonUDS, ZEVonUDS |
| Interfaces | SAE J2534 (Pass-Thru), RP1210, D-PDU-API |
| Physical connection | CAN, CAN FD, K-line, Ethernet |
| System Requirements (Minimum): | Processor: 32 and 64bit Hard disk space: 80MB RAM: min 100MB Windows: 7 and higher. Standard graphics card |