Bus-capable blocks can accept bus signals as input, produce bus signals as output, or both. Some bus-capable blocks work with nonvirtual buses, but not with virtual buses. Some bus-capable blocks have additional requirements for bus signals; see the block documentation for details.
|All virtual blocks|
Constant (nonvirtual buses)
Data Store Memory (nonvirtual buses)
|Has no input port, can store bus signals|
Data Store Read (nonvirtual buses)
Data Store Write (nonvirtual buses)
|(special requirements)||(special requirements)|
From File (nonvirtual buses)
From Workspace (nonvirtual buses)
To File (nonvirtual buses)
To Workspace (nonvirtual buses)
Vector Concatenate(nonvirtual buses)
These modeling patterns support the use of buses. See the documentation for those features for any special considerations relating to the use of buses. Subsystems, models, and S-functions support the use of buses.
MATLAB Function blocks
MATLAB System blocks
Buses that contain signals of enumerated data types do not pass through a block that requires a nonzero scalar initial value (such as a Unit Delay block). Use a structure value to initialize signals with enumerated types.
Root level bus outputs are not logged when you select the Configuration Parameters > Data Import/Export > Output parameter. Use standard signal logging instead, as described in Export Signal Data Using Signal Logging.
Do not use signal logging for bus or array of buses signals directly from within a For Each subsystem. Either use a Bus Selector block to select the bus element signals to log or add an Outport block outside of the subsystem and then log that signal. For details, see Log Signals in For Each Subsystems.