Bus-Capable Blocks
Buses are not intended to support computation performed directly
on the bus. Therefore, only a small subset of blocks, called bus-capable
blocks, can process buses directly. All virtual blocks
are bus-capable. The following nonvirtual blocks are also bus-capable:
All signals in a nonvirtual bus input to a bus-capable block
must have the same sample time, even if the elements of the associated
bus object specify inherited sample times. You can use a Rate Transition block to change the sample
time of an individual signal, or of all signals in a bus.
Some bus-capable blocks impose other constraints on bus propagation
through them. See the documentation for the specific block in Blocks-Alphabetical
List for more information.
You can sometimes connect a virtual bus to a block that is not
bus-capable without generating an error, but such a connection intermixes
buses and muxes, which The MathWorks discourages. See Avoiding Mux/Bus Mixtures for
details.
 | Nesting Buses | | Using Bus Objects |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
Get this Simulink Kit
Store 
