Rockwell Automation 1203-SM1 SLC to SCANport Communication Module - Manual (Page 39)

4–11 Using Enhanced Mode
Publication 1203–5.9 –– October 1996
The G file datalink configuration field is defined as follows:
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Gs.1 Not Used ED
2
EA
3
EA
1
EB
1
EC
3
ED
3
EB
2
EC
2
EA
2
EC
1
ED
1
EB
3
These bits have the following definitions:
This: Represents:
EA1
EA2
EA3
SCANport Channel 1, 2, or 3 Datalink A Enable bit. When set
high (1), datalink A is enabled for the corresponding channel.
Note: The datalink is only active while the channel’s Data
Enable bit is also set.
EB1
EB2
EB3
SCANport Channel 1, 2, or 3 Datalink B Enable bit. When set
high (1), datalink B is enabled for the corresponding channel.
Note: The datalink is only active while the channel’s Data
Enable bit is also set.
EC1
EC2
EC3
SCANport Channel 1, 2, or 3 Datalink C Enable bit. When set
high (1), datalink C is enabled for the corresponding channel.
Note: The datalink is only active while the channel’s Data
Enable bit is also set.
ED1
ED2
ED3
SCANport Channel 1, 2, or 3 Datalink D Enable bit. When set
high (1), datalink D is enabled for the corresponding channel.
Note: The datalink is only active while the channel’s Data
Enable bit is also set.
You may enable datalinks with or without providing safe state data.
You can configure G files that are between 2 and 32 words in length.
!
ATTENTION: Configure your safe state values based
on your knowledge of how the SCANport devices
connected on each channel operate. Refer to the
manual for your SCANport device for additional
information.
To transfer messages between the SLC processor and any of the
SCANport devices connected through the SLC to SCANport
module, you need to use M files. The SLC to SCANport module
uses M0 and M1 files. The M0 file is a module output file
(write–only), while the M1 file is a module input file (read–only).
Messages to the SCANport module from the SLC processor are sent
using the M0 file, while the M1 file contains the responses.
Using M Files