Fault state data, Device actions, Fault state data -6 device actions -6 – Rockwell Automation 1797-IRT8 FLEX Ex Thermocouple/RTD/mV Input Module User Manual User Manual
Page 44: Communication fault behavior -6, Communication fault behavior

Publication 1797-6.5.2 - February 2001
4-6 Input, Status, Output and Configuration Files for the Thermocouple/RTD/mV Module on the ControlNet Network
Possible causes for an I/O Module Fault are:
•
transmission errors on the FLEX Ex backplane
•
a failed module
•
a module removed from its terminal base
•
incorrect module inserted in a slot position
•
the slot is empty
•
the slot contains a non-discrete module
Fault State Data
The ControlNet Ex adapter provides storage for alternate module
output data during communication faults or processor idle state. This
“fault state data” assures that a known output will be applied to the
output devices during the previously mentioned modes. The
processor or scanner software must include the means to specify this
fault state data for each module. If applicable, this data is sent in the
configuration block, see Image Table Mapping on pages 4-8.
Device Actions
Device actions include:
•
communication fault behavior
•
idle state behavior
•
input data behavior upon module removal
Communication Fault Behavior
You can configure the adapter response to a communication fault for
each I/O module in its system. Upon detection of a communication
fault,
the adapter can:
•
leave the module output data in its last state (hold last state)
•
reset the module output data to zero (reset)
•
apply fault state data to the module output