Bus Manager 2025-A

New interface for exchanging data with Simulink^® models and generating container files, selectable import behavior for messages with multiplexed signals from DBC files, new bus configuration features

Bus Manager 2025-A (25.2) now provides the shared data interface (SDI) for bus configurations, which is a completely new interface for exchanging data with Simulink^® models and generating container files. The shared data interface is a central data structure that can be accessed directly by bus configurations and Simulink models, which results in an optimized run-time performance. Moreover, you can generate bus implementation containers (BIC files), which contain the bus communication of exactly one bus configuration. The current state of the shared data interface is a preview version, i.e., it is in an early but completely tested development stage. We provide this preview version so you can explore this new interface as early as possible. Moreover, we would like to collect feedback that we can consider in the further feature development. However, due to the further feature development, incompatible changes between this preview version and the first stable release version of the interface are very likely.
Furthermore, the Bus Manager now lets you select how messages with multiplexed signals are imported from DBC communication matrices into the Bus Manager. You can keep the standard import behavior, which is an AUTOSAR-oriented approach: The messages are imported as multiplexed IPDUs, and the signals are added to static-part IPDUs and dynamic-part IPDUs. Alternatively, you can choose to import such messages as extended multiplexed IPDUs, which results in a DBC-like handling of the messages: Only one extended multiplexed IPDU is generated for each applicable message. All signals of the message are included directly in the generated IPDU. 
The Bus Manager also provides new bus configuration features: The PDU Cyclic Timing Status inspection feature lets you observe the cyclic reception of PDUs, e.g., to detect cycle time errors. The Frame Triggering manipulation feature lets you specify a frame triggering that is used to identify a CAN frame that is to be manipulated by the Bus Manager.