Installation guide

106 Estimating Network Performance
890 USE 100 00
3.21.8 Controlling the Sequencing of MSTR Functions
When you use multiple MSTR functions in a controller, each MSTR
acquires its own Data Master path which is maintained open until its
transaction terminates. The paths are independent of each other. A
transaction can be started on one path, and another transaction can be
started some time later on a second path. Their completions are
determined by other devices on the network.
If your application needs to complete the MSTR functions sequentially,
use logic to monitor the COMPLETE outputs before enabling other
MSTR functions.
3.21.9 Optimizing Node Counts
Consider separating a device application into two or more devices to
avoid queueing. For example, if you expect heavy queueing within one
controller because of a high concentration of traffic from other nodes,
consider employing two nodes instead. Although the additional node
count adds slightly to the token rotation time, the opportunity for
parallel processing without queueing makes data available more
quickly as the token is received in each of the two nodes.
3.21.10 Prioritizing and Compressing Data
Plan the data transactions in your application so that only needed
information is sent. Process the data before transmission, condensing
it into larger messages if possible. Reduce the amount of data
messages to be sent, or reduce the frequency at which they have to be
sent.
Schedule the data to be sent on a timed basis rather than on every scan
of a controller, to reduce the loading on the network. Time the
transmissions to the intervals at which the receiving device needs the
information.