Rockwell Automation 1757-ABRIO Process Remote I/O (RIO) Communication Interface Module - Manual (Page 54)

52 Publication 1757-UM007D-EN-P - December 2008
Chapter 4 Configuring the ProcessLogix Controller to Access Data on the 1757-ABRIO Module
INACTIVE Mode
The module is in INACTIVE mode when it is not receiving messages
from either a host controller or via OPC/DDE. The module is also in
INACTIVE mode when it has not been put in FORCED ACTIVE mode
by AbRioCfg software.
When the module is in INACTIVE mode, the RIO network is placed in
program mode with input updates but no output updates. The
1757-ABRIO module must be in the INACTIVE mode to accept a
download.
ACTIVE Mode (Run)
The module is in ACTIVE mode when it receives a message from
either a host controller or from an OPC or DDE server. When the
module is in ACTIVE mode, the RIO network is in run mode.
The module is in ACTIVE mode as long as any tag is being updated.
Each tag has an associated time-out. The tag is considered to be
updating until the time-out expires. If all tags have timed out, the
1757-ABRIO module automatically switches to INACTIVE mode.
If you try to download a configuration when the module is in ACTIVE
mode, AbRioCfg software asks if you want to take the module out of
ACTIVE mode. If you click OK, AbRioCfg software changes the mode,
downloads the configuration, then puts the module in INACTIVE
mode.
FORCED ACTIVE Mode
The module is in FORCED ACTIVE mode when you set ACTIVE mode
from the AbRioCfg program. FORCED ACTIVE mode lets you send
and receive data without having to create messages in the module. It
is intended primarily for setting up and testing RIO networks.
If you try to download a configuration when the module is in
FORCED ACTIVE mode, AbRioCfg software asks if you want to take
the module out of ACTIVE mode. If you click OK, AbRioCfg software
changes the mode, downloads the configuration, then puts the
module in INACTIVE mode.
IMPORTANT
When the module is in FORCED ACTIVE mode, the RIO network
is in run mode.