Saturday, May 19th, 2012

EB tresos Busmirror

FlexRay and CAN cluster emulation made easy


Cluster emulation with EB tresos Busmirror allows you to test  your ECU software during the implementation stage.  When you want to start up your ECU while the other ECUs in the network are not yet available, our cluster emulation solution mirrors the behavior of these missing ECUs.

In addition to testing the intended behavior, EB tresos Busmirror also emulates the responses to potential error situations, such as the sporadic absence of individual frames or the incorrect calculation of check sums.

Time critical functions can be carried out on EB interface hardware in real-time.  This allows you to emulate complex functions such as entire environment models or network management directly on the interface hardware, saving resources on your host system. With EB tresos Busmirror you can power up a FlexRay or CAN  network and configure the nodes to be emulated in a matter of minutes.

EB tresos Busmirror

FlexRay and CAN cluster emulation in four steps


  • Import a system configuration in the form of an

    • AUTOSAR system description

    • FIBEX file or

    • CANdb file.


  • Select the network nodes/ECUs to be emulated

  • Modify communication schedule

  • Generate the configuration for the EB interface hardware

OEM specific cluster emulation


Our new extension package for EB tresos Busmirror allows you to emulate ECU clusters according to OEM specific requirements. Learn more about EB tresos Busmirror MAid for OEM.


Main functions at a glance


EB tresos Busmirror Config


  • Easy configuration of the cluster emulation through guided workflow

  • Simulation of large FlexRay networks with several ECUs with only a few clicks

  • Automated cluster emulation generation for FlexRay and CAN

  • Editors (add, delete and change) for signals, frames, frame triggerings, scheduling and network parametersCSV-file export and import

  • Supported system configuration formats:

    • FIBEX 1.1.5a, 1.2.0a, 2.0.0b, 2.0.0d, 2.0.1,

    • FIBEX+

    • CANdb

    • AUTOSAR system description  2.1.2, 2.1.4, 3.0.2, 3.1.0, 3.1.2, 3.1.4


Using EB tresos Busmirror Runtime you can download, control and execute the cluster emulation configuration you created with the EB tresos Busmirror Configuration Tool.

EB tresos Busmirror Runtime


  • All EB tresos Busmirror Runtime functions can be controlled via a Windows graphical user interface (EB tresos Inspector). This user interface is part of the delivery content.

  • Broad interface API with functions for signal (coded and physical), PDU and frame access.

  • Ensured consistent access to signal groups and PDUs

  • Your own functions can be calculated in real-time directly on the EB hardware  by means of target user modules (TUMs).

  • Useful TUM functions are included in the delivery content but can also be programmed by yourself.

  • TUM functions can be executed asynchronous or synchronous execution of functions with respect to the FlexRay schedule.

  • The TUM models can be configured during runtime, via a bidirectional data channel.

  • Emulated nodes can be switched on or off during runtime

  • The following drivers are included in the delivery:


  • Our generic driver can easily be adapted to your a platform of your choice (EB 5100)

  • Driver for the MATLAB/Simulink real-time hardware xPC available upon request

  • Driver support for signal, signal group and frame access

  • Signal access to coded and physical values

  • Consistent access to signal groups

  • Switch emulated frames and FlexRay nodes on and off

  • Support for message based access to CAN data

  • Support of up to 16 digital in- and output signals

  • Independent FlexRay network start-up, when no other ECUs are connected to the network

EB tresos Busmirror - host drivers

Use caseHost driverConnection busLatency host-EB hardwareApplication model execution
EB tresos Busmirror + EB 5100NI LabVIEW and Windows VISA driverPCI/cPCI
very low-Host (PC)
-EB 5100 (target user modules)
National Instruments LabVIEW RT driververy low-NI real-time system CPU
-EB 5100 (target user modules)
LINUX driververy low-LINUX host
-EB 5100 (target user modules)
very low-ETAS LabCar RTPC
-EB 5100 (target user modules)
low-Matlab xPC
-EB 5100 (target user modules)
EB tresos Busmirror + EB 61x0low-Host (PC)
-EB 61x0 (target user modules)
-LINUX host (PC)
-EB 61x0 (target user modules)

EB tresos Busmirror serves the electronic control
unit (ECU) developer during the implementation stage, in which
their own ECU is initially started up, while the other bus users
are not yet available.

EB tresos Busmirror - host drivers

Use caseHost driverConnection busLatency host-EB hardwareApplication model execution
EB tresos Busmirror + EB 5100NI LabVIEW and Windows VISA driverPCI/cPCI
very low-Host (PC)
-EB 5100 (target user modules)
National Instruments LabVIEW RT driververy low-NI real-time system CPU
-EB 5100 (target user modules)
LINUX driververy low-LINUX host
-EB 5100 (target user modules)
very low-ETAS LabCar RTPC
-EB 5100 (target user modules)
low-Matlab xPC
-EB 5100 (target user modules)
EB tresos Busmirror + EB 61x0low-Host (PC)
-EB 61x0 (target user modules)
-LINUX host (PC)
-EB 61x0 (target user modules)

What’s new in EB tresos Busmirror?


Read more about the features integrated in the latest product releases:
EB tresos Busmirror & EB tresos Inspector 3.3.1
EB tresos Busmirror & EB tresos Inspector 3.3