Description
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
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 |