140
Rockwell Automation Publication 1407-UM002B-EN-P - February 2019
Chapter 6
CGCM-DLR Unit Software Interface
CGCM-DLR Unit User Program
Interface
The CGCM-DLR unit and the ControlLogix controller transfer data through
five controller tags that are based on the module-defined data types that are listed
in the
When the CGCM-DLR unit is added into the Logix controller project, the
Logix Designer application creates the six module defined data types. These data
types are the following:
•
AB:1407_CGCM:I:0
•
AB:1407_CGCM:O:1
•
AB:1407_CGCM_Unscheduled_Read3
•
AB:1407_CGCM_Unscheduled_Write3
•
AB:1407_CGCM:C:1
•
AB:1407_CGCM_Configuration_Read
In addition, four controller tags are created by using these data types:
• [Module_Name]:C
, the Configuration tag
• [Module_Name]:C.UnschWrite
, the Unscheduled Write tag
• [Module_Name]:O
, the Output or Scheduled Write tag
• [Module_Name]:I
, the Input or Scheduled Read tag
When the Configuration tag is created, a set of default values are assigned. These
default values do not always reflect the configuration parameters necessary for
operation of your application.
See
for information on how to configure the CGCM-DLR unit with
the Logix Designer application Add-on Profile pages.
The data in the Configuration and Unscheduled Write tags can be accessed by
the Add-on Profile configuration interface and 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-DLR unit.
Similarly, if you wish to read back configuration parameters from the CGCM-
DLR unit, you must create a tag with data type
AB:1407_CGCM_Configuration_Read and create logic in the user program to
initiate unscheduled read messages.
IMPORTANT
The Logix Designer application performs data range checks on configuration
data that is entered into the module configuration pages. The data range check
does not help ensure that data is appropriate for the application. No data range
checks are performed on configuration data that is modified by the user
program. The CGCM-DLR unit does not accept out-of-range configuration data
and a communication error results.