Bus Receiver Object
Bus receiver objects act as the entry points in a node for packets received on bus links. They can contain multiple channel objects, each of which is capable of communicating with transmitter channels in remote nodes via the bus link.
Receivers have multiple output streams, each one corresponding to a separate channel of the bus link, and each connected to a separate packet stream. The packet streams are directed towards other modules in the node. There is a direct correspondence between output stream indices and channel indices. In other words, a packet that is received on channel j of the bus link is forwarded on output stream j of the bus receiver module. Bus receivers are considered as data sources from the perspective of other modules within the node, so they may not have incoming packet streams.
Graphical Representation
In the Node Editor, the default representation of a bus receiver is a square box with a circle that represents the node, an arrow pointing into the node that represents the tap, and a vertical bar that represents the bus. The name of the receiver appears below the object, as shown in the following figure.
Figure 3: Bus Receiver

Bus receiver objects are the interface between a node and a bus link. Many of the parameters controlling the modeling of packet transmission across a bus link are attributes of the bus link object in the network domain and are not visible on the receiver object. These are attributes such as bit error rate and propagation delay, and also stages of the bus link transceiver pipeline. For more information about the transceiver pipeline, see Chapter 9 "Communication Mechanisms" on page 331.
Bus Receiver Object Attributes
The following table lists the built-in attributes of the bus receiver object.
Table 3: Bus Receiver Object Built-In Attributes
| Name | Data Type |
|---|---|
| channel | compound |
| ecc threshold | double |
| icon name | icon |
| name | string |