Anybus Communicator PROFINET IRT User Manual page 39

Anybus Configuration Manager
6.4.5 Produce Transactions (Generic Data Mode)
Fig. 35 Parameters
Parameter
Offline options for fieldbus
Update mode
Update time (10 ms)
Trigger byte address
®
Anybus Communicator ™ PROFINET
Description
The action to take for this transaction if the higher level network goes off-
line. This affects the data that is sent to the subnetwork.
Clear = The data destined for the slave devices is cleared (set to zero)
Freeze = The data destined for the slave device is frozen
NoScanning = The updating of the subnetwork is stopped
Specifies when the transaction shall be sent to the slave.
Cyclically = The transaction is issued cyclically at the interval specified in
the Update time parameter.
On data change = The data area is polled for changes at the time interval
defined by the Update time parameter. A transaction is issued when a
change in data is detected.
Single shot = The transaction is issued once at start up.
Change of state on trigger = The transaction is issued when the trigger
byte value has changed.
This feature enables the control system to notify the gateway when to is-
sue a particular Query. To use this feature correctly, the control system
must first update the data area associated with the Query/transaction,
then increase the trigger byte by 1.
The trigger byte is checked at the interval specified in Update time.
The location of the trigger byte is specified in Trigger byte address.
How often the transaction will be issued in steps of 10 ms.
Relevant only when Update mode is set to Cyclically, On data change or
Change of state on trigger.
The entered value is multiplied by 10. A value of 5 means 50 ms.
The location of the trigger byte in the internal memory buffer. Only relevant
when Update mode is set to Change of state on trigger.
The specified memory location is monitored by the gateway. Whenever
the trigger byte is updated, the gateway will produce the transaction on
the subnetwork. This way, the control system can instruct the gateway to
produce a specific transaction on the subnetwork by updating the corre-
sponding trigger byte.
The trigger byte address must be unique to each transaction. It can not be
shared by multiple transactions.
Valid settings range from 0x200 to 0x3FF and 0x400 to 0xFFF
®
IRT (2.32) User Manual
37 (66)
SCM-1202-033-EN 1.1