Simulation and Analysis
Residual Bus Simulation (RBS)
Functional Simulation based on Matlab/Simulink
Virtualization

With the Ixxat simulation solutions you can simulate the communication behavior of missing components (ECU’s) in your communication network. Communication simulations (RBS) are configured based on network description files with an easy to use tool. There’s no own coding required. Functional simulations can be implemented by scripts, C user code or MATLAB/Simulink models. Standalone or PC based simulation – that’s up to you. You don’t want to waste time – in that case the Ixxat simulation solutions are the right choice for you.


PC-based or standalone approach?

PC-based simulation can be done by using either PC interfaces, FRC-EP170/190 or CANnector. The application itself runs on a PC (as for example CanEasy). This economic approach is flexible and easy to implement, but has – due to several layers in between – limited real time processing capabilities.

Applications with high real time demands – e.g. residual bus simulation – can directly be executed standalone on the FRC-EP 170/190 or CANnector platforms. Direct connection to the buses and powerful local processor performance enables low latency transmission and real time processing. The configuration of the application and devices is done easily via Ixxat ACT.


Application examples


PC-based development

Simple manual signal simulation
using a PC interface for bus access and CanEasy with its build in widgets.

Programmed device simulation
using CanEasy with its integrated programming function to enable simple automated signal simulation.

Expanding CanEasy with Matlab/Simulink and CAPL
to allow complex PC-based system and device simulation.


Standalone testing

Gateway application
between different physical and logical networks running Matlab/Simulink models and/or C User Code directly on the real time capable hardware.

Classical test bench application
Residual bus simulation with checksum and alive counter to keep the DuT (Device under Test) alive plus data exchange or/and stimulation via e.g. EtherCAT master

Cloud connection
Virtualization of bus systems to the cloud or remote management of systems.


Highlights


Stand-alone or PC-based

Powerful hardware platforms enabling either stand-alone or PC-based operation

Versatile operation modes

Easily choose between signal-based, frame-based and mixed operation

Various data formats

Support of DBC, LDF, ARXML, Fibex, ESI, MDF, BLF, ASC, CSV


Data recording

Parallel logging of the transferred data on the interface device itself or on the PC

Programming

C user code with high-level debugger (ADK) Eclipse, Matlab/Simulink based models or Visual-Basic, C#/.net, VB.net

Easy configuration

With drag&drop and automated functions growing with your demand by providing different software variants


Hardware compatibility with the software tools



Requirements and functions for PC-based and realtime standalone simulation

PC-based simulationStandalone simulation
Hardware interfacesCANnector, FRC-EP170, FRC-EP190

Ixxat CAN interfaces

and other vendors (Vector, Peak, Kvaser, NI, Intrepid, MHS,  Melexis)
CANnector, FRC-EP170, FRC-EP190
Software toolsCanEasy
for analysis and simulation
ACT – Advanced Configuration Tool
(only required for configuration)
Required hardwarePCRealtime (standalone) hardware
Embedded hardware
(CANnector & FRC-EP family)
Bus description filesDBC, ARXML, LDFDBC, ARXML, LDF, Fibex
Bus systemsCAN, CAN FD, LIN, Automotive Ethernet, FlexRay*CAN, CAN FD, LIN, FlexRay
Communicative simulation
Communicative cyclic/event-triggered simulation (without checksum and alive-counter)Automatically by using bus description filesAutomatically by using bus description files
Residual bus simulation
Residual bus simulation (RBS) with checksum, alive-counter, etc.PC with coding or CAPL importRealtime, automatically generation
Manipulation / Stimulation / Simulation
Functional simulation by Matlab/SimulinkMatlab/Simulink on PCMatlab/Simulink on realtime hardware*
Functional simulation by codingCoding on PCC user code (integrated development environment with Eclipse) on realtime hardware*
Manual signal stimulation and visualizationSignal panels / User-panelsWebsockets, CanEasy, canAnalyser Mini
Simple signal modulationModulatorMatlab/Simulink, C user code
Signal calculation, logical functionsFormula editor, Visual-Basic, C#/.net, VB.netMatlab/Simulink, C user code
External StimulationCAN, COM (e.g. Matlab/Simulink), Ethernet, RS-232CAN, EtherCAT, FDX, XCP, Generic Ethernet, CAN@net, virtual CANonEthernet, CanEasy
Gateway
Gateway environmentPlug-ins on the PCOn realtime capable hardware*, configuration via drag&drop (signals, frames, PDUs, logical buses)
Data Logging
Data logging targeton PCOn SD-card or USB-device (realtime capable hardware*) or on other systems which are connected to the system
*realtime hardware: CANnector, FRC-EP170/190

Product selection for simulation applications with supported interfaces and order numbers


(A) Input or output per software switchable
(B) only CANnector and FRC-series: 6/8 CAN in total, thereoff max. 2/4 CAN-FD capable
(C) 4/6/8 CAN in total, thereoff max. 1/2 Low-Speed CAN capable
(D) 4 digital inputs/outputs (5 V TTL)
(E) 4 digital inputs (max. 34 V), 4 digital outputs (max. 34 V, 1 ampere)
(F) only CANbridge NT 420 and CAN@net NT 420: max. 4 CAN in total, thereoff max. 2 CAN-FD capable