Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 114)

7Ć2 AutoMax Programming Executive Version 3.x
Configurator. Local variables are defined only in the tasks that use
them.
Note: Although the following modules themselves can be added to the
rack, registers on these modules cannot be configured in the rack:
M/N 57C405 DCS Drive Analog I/O module
M/N 57C408 DCS Drive Power Module Interface module
M/N 57C440 Ethernet Network Interface module
M/N 61C605 8ĆChannel Thermocouple Input module
M/N 61C613 16ĆChannel Analog Input module
See 7.1.1 for more information on configuring I/O variables and 7.1.2
for configuring common memory variables.
7.1.1 Configuring I/O Variables
When you configure I/O or interface modules (except the Network
Interface) module, the register/point locations are displayed in the
form in numerical order. Assigning the name P_BUTTON@ to bit 2 of
register 0 on a digital input module form, for example, attaches the
name P_BUTTON@ to the value stored in bit 2 of register 0, which is
physically connected to external hardware by way of a connector on
the module faceplate.
For I/O modules with duplicate registers that indicate the same status
but differ only in that the bits on one are chiefly R (readĆonly) and bits
on the other are chiefly R/W (read/write) in the instruction manual,
you may configure only the bits that are read only in the read only
register and the bits that are read/write in the read/write register. An
example is the 5VĆ24V DC Input module (M/N 57C419). For this type
of register arrangement, R/W refers to the ability of the operating
system, not the application task, to write to that register.
Most I/O and interface modules are configured using the basic form
described in 7.2.1. Network Interface modules are configured using a
special form described in 7.2.3.
7.1.2 Configuring Common Memory Variables
The common memory variables in the rack are mapped to the
Common Memory module in slot 0 and Processor modules. These
variables are strictly memory variables and are not connected to
external hardware. There is no relationship between the way the
variables are displayed in the form on the screen and the way in
which they are stored. Common memory variables can be made
nonĆvolatile, i.e., their last value is preserved in the event of a power
outage, if the nonĆvolatile option is selected when they are being
configured. Note that the method by which common memory
variables are stored and the form used to configure them are unique.
See 7.2.2 for more information.