Bus access tab¶

The tab Bus access provides access to various buses of control units. The structure of the tab is similar to that of control units. The left part shows the management of bus systems. It allows entering and deleting, as well as shifting between, bus systems. On the right side you can choose the software for bus access together with the corresponding file. The file contains a database comprising all kinds of information processed in a bus network as well as their interrelations.

DBC, ARXML and LDF files are supported. ARXML databases can contain several clusters or channels, so, that when an ARXML file is specified, it is necessary to additionally select the cluster respectively channel to be used. For this purpose, global constants can be used, too. The selection depends on the type of database:

ARXML describing a bus

The cluster can be selected. Information of the different channels of that cluster is merged.

ARXML describing an Ethernet service or a socket adaptor

The cluster and channel can be selected. If necessary, also the protocol.

LDF

No selection needed. The field shows the bus name as specified in the database, given there is one.

DBC

No selection needed.

Each type of database can also be given as zip archive. This archive should only contain a single file with the exception of AUTOSAR XML. In case of AUTOSAR XML zip archives containing multiple files are supported, if their content is compatible and doesn’t collide.

The interface Active node is used for reading signals and messages. Moreover, messages can be sent in an additive (not cyclical) manner. Some bus ports (including the hardware-related bus connections) also support the monitoring of messages (minimum and maximum cycle time, number of messages received, CRC check, etc.) via this interface. For manipulating signals and messages in rest bus simulation it is necessary to indicate a port for the interface manipulation.