Transmitter Modules
Figure 162: Icons Used for Transmitter Modules

Transmitter modules serve as the outbound interface between packet streams inside a node and communication links outside the node. There are two types of transmitter modules, corresponding to the different types of communication links: point-to-point and bus (in addition, radio transmitters are available in the Wireless functionality). Each of the transmitter module types has essentially the same basic behavior, although there are some differences related to the different communication mechanisms.
Transmitter modules can collect packets from one or more input packet streams and relay them over corresponding channels within the communications link. A packet received on a given input stream is transmitted over the channel with the same index number. Each channel can have its own data rate, which can be used with the size of the packet to determine the transmission time. Packets arriving on an input stream while the corresponding channel is busy with a previous packet are automatically queued in a buffer. This buffer has a default capacity of 1000 packets of any size.
Channels are subordinate objects of transmitter modules. The transmitter contains them within its “channel” attribute, which is a compound attribute. The “channel” attribute’s value is a compound attribute object, which is the parent of all of the contained channels (see “Modeling Framework” on page 80 for more information on compound attributes and subordinate objects). Each channel maintains a set of attributes that control various aspects of packet transmission. Some of these attributes are also used to determine compatibility between transmitters, receivers, and link objects to form viable links in the Project Editor. Specifically the “data rate” and “packet formats” attributes of channels are used to establish consistent links for point-to-point and bus transceiver channels. For more information about link consistency, see “Network Domain” on page 292.
Within a node model, a transmitter module is considered to be a data sink. Therefore, although they may have many input packet streams, transmitter modules do not have output packet streams. From the point of view of the network model, a transmitter module acts as the node’s output port, to which a communication link of the corresponding type may be connected: simplex and duplex links to point-to-point transmitters, and bus links to bus transmitters. These relationships are illustrated in the following figure.
Figure 163: Relationship of Transmitter Modules to Network and Node Models

Several of the parameters controlling transmission of packets from point-to-point and bus transmitter modules are actually specified as attributes of the link (such as error rate and propagation delay).
Transmitter channel objects respond to an “abort” command, which causes them to abort the transmission of the current packet. The op_ima_obj_command() Kernel Procedure is used for this purpose; for more details, see the description of this procedure in “Internal Model Access” on page 1.
Transmitter channel objects calculate a number of statistics which can be usefully monitored by other modules via statistic wires, or collected through use of a statistic probe. For example, the “bit_thruput” and “pk_thruput” statistics may be used to monitor the throughput of a specific transmitter channel, based on the total size or number of data packets, respectively. For more information about the statistics supported by a particular transmitter channel object, see “Node Reference” on page 8.