Rockwell Automation 1407-CGCM Combination Generator Control Module - Manual (Page 127)

Rockwell Automation Publication 1407-UM001G-EN-P - April 2013 127
CGCM Unit Software Interface Chapter 6
In addition to the module configuration interface, the data in the Configuration
and Unscheduled Write tags can be accessed by reading and writing elements of
the tags in the user program.
If you wish to monitor the content of the Unscheduled Read data type in the user
program, you must create a tag with data type
AB:1407_CGCM:Unscheduled_Read and create logic in the user program to
initiate unscheduled read messages to the CGCM unit.
Configuration Messaging
CGCM unit configuration is a two-step process. The first step happens
automatically and the second must be performed by the user program.
Configuration Step 1
Each time you apply power to the CGCM unit all of its data tables are initialized
with all zeroes. This results in a configuration fault that exists until the
configuration is written to the CGCM unit. When a ControlNet network
connection to the CGCM unit is established, the controller automatically
attempts a scheduled write of the Configuration tag to the CGCM unit.
The controller also attempts a scheduled write of the Configuration tag when the
configuration has been changed by using the module configuration dialog boxes
and the Apply or OK button has been clicked.
The CGCM unit does not accept configuration data if excitation is enabled. The
ExcitationOutputEnabled
bit provides this information to the user program.
If excitation is disabled and all configuration parameters are within the acceptable
range, the CGCM sets the ConfigRcvd bit in the Scheduled Read data tag.
Whether or not the configuration write was successful, the CGCM unit clears
the UnschWrRcvd bit when it receives a configuration write attempt. This bit is
used in Step 2.
IMPORTANT
RSLogix 5000 software performs data range checks on configuration data
entered into the module configuration screens. This does not ensure that
data is appropriate for the application. No data range checking is
performed on configuration data that is modified by the user program.
Out-of-range configuration data is not accepted by the CGCM unit and a
communication error results.