Overview. Allen-Bradley SLC 5/02, 1747 ASB, 1747 SN, Remote I/O Scanner
Below you will find brief information for Remote I/O Scanner 1747 SN, Remote I/O Scanner 1747 ASB. The 1747-SN Remote I/O Scanner is used to connect an SLC 500 processor to remotely located I/O devices, such as the 1746 I/O chassis. This allows you to extend the reach of your control system and access signals from a distance. The scanner transmits data between the processor and the remote I/O devices, enabling you to monitor and control processes in areas where you can't have the processor directly available. It also allows for the use of complementary I/O, where two adapters can share the same image space to increase the number of I/O points supported.
Advertisement
Advertisement
1
System Overview
Chapter
1
Overview
This chapter contains the following information:
• system overview
• how the scanner interacts with the SLC processor
• how the scanner interacts with adapter modules
• scanner I/O image concepts
• extended node capability
• complementary I/O
• scanner features
• compatible network devices
The Remote I/O (RIO) Scanner, Catalog Number 1747-SN, is the remote I/O scanner for the SLC 500. It enables communication between an SLC processor (SLC 5/02 or later) and remotely located
(3,048 meters [10,000 feet] maximum) 1746 I/O chassis and other RIO compatible Allen-Bradley operator interface and control devices. The
1747-SN Scanner communicates with remotely located devices using the Allen-Bradley Remote I/O link. The RIO link consists of a single master (scanner) and multiple slaves (adapters). Communication between devices occurs over twisted pair cable with the devices daisy-chained together. The scanner can reside in any slot of the local
SLC chassis except for slot 0.
The Remote I/O (RIO) Scanner, Catalog Number 1747-SN, is the remote I/O scanner for the SLC 500. It enables communication between an SLC processor (SLC 5/02 or later) and remotely located
(3,048 meters [10,000 feet] maximum) 1746 I/O chassis and other RIO compatible Allen-Bradley operator interface and control devices. The
1747-SN Scanner communicates with remotely located devices using the Allen-Bradley Remote I/O link. The RIO link consists of a single master (scanner) and multiple slaves (adapters). Communication between devices occurs over twisted pair cable with the devices daisy-chained together. The scanner can reside in any slot of the local
SLC chassis except for slot 0.
Publication 1747-UM013B-EN-P - January 2005
1-2 Overview
SLC 5/02 or Later
Processor
RIO Scanner
(Master of the
RIO Link)
Local SLC Chassis
The scanner transfers input and output data between itself and all configured network devices over twisted pair cable. Note that the end-to-end length of the cable can be a maximum of 3,048 meters (10,000 feet).
1747-ASB Module
(Adapter/Slave)
Remote Chassis
Remote Expansion Chassis
Dataliner Message Display
(Adapter/Slave)
PanelView Operator Terminal
(Adapter/Slave)
RediPANEL
(Adapter/Slave)
The scanner can be configured for and transfer a maximum of 4 logical racks of discrete data on the RIO link. The scanner provides discrete I/O and block (Series B or later) transfers. Configurations allowed are any combination of quarter, half, three-quarter, or full logical rack devices.
SLC 5/02 or Later
Processor
RIO
Scanner
The scanner transfers discrete input and output data
Remote adapters consist of 1746 chassis and other
Allen-Bradley operator interface and control devices.
Adapter 1
Half Logical
Rack
Device
Adapter 2
Quarter Logical
Rack
Device
Adapter 3
Half
Logical Rack
Device
Adapter 4
Three-Quarter
Logical Rack
Device
Adapter 5
Full
Logical Rack
Device
Adapter 6
Full
Logical Rack
Device
The SLC processor transfers the scanner’s 4 logical racks (32 input image and 32 output image words) of discrete remote I/O image data into the SLC input and output image files. You can adjust the size of the scanner input and output image file during configuration of your
SLC system so that the scanner only transfers the discrete I/O data
Publication 1747-UM013B-EN-P - January 2005
Overview 1-3 your application program requires. Configuration is done through the confiGuration file (G file). Refer to Chapter 4, Configuration and
Programming, for more information.
IMPORTANT
The SLC 500 processor (SLC 5/02 or later) supports multiple scanners in its local I/O chassis. The maximum number is dependent on the following:
• backplane power requirements (power supply dependent)
• SLC 500 processor I/O data table limit (4,096 I/O)
• processor memory to support the application
(SLC 500 processor dependent)
Scanner I/O Image Division
The scanner allows each adapter to use a fixed amount (user defined) of the scanner’s input and output image. Part of the SLC processor’s image is used by local I/O, the other portion is used by the scanner for remote I/O.
The scanner remote I/O image is divided into logical racks and further divided into logical groups. A full logical rack consists of eight input and eight output image words. A logical group consists of one input and one output word in a logical rack. Each logical group is assigned a number from 0 to 7.
Local I/O
Logical Rack 0
Logical Rack 1
Remote I/O
(Scanner Image)
Processor I/O Image
Logical Rack 2
Logical Group 0
Logical Group 7
Scanner I/O Image Adapter
Image
Publication 1747-UM013B-EN-P - January 2005
1-4 Overview
The scanner image contains the image of each adapter on the RIO link. The adapter is assigned a portion of the scanner image, which is referred to as the adapter image.
How the Scanner Scans
Remote I/O
The scanner communicates with each logical device in a sequential fashion. First, the scanner initiates communication with a device by sending output data to the device. The device then responds by sending its input data back to the scanner, as illustrated below. You refer to this exchange as a discrete I/O transfer. After the scanner completes its discrete I/O transfer with the last configured network device, it begins another discrete I/O transfer with the first device.
It is important to understand that the scanner transfers RIO data on a logical device basis not on an adapter basis. A logical device is a full logical rack or portion of a logical rack assigned to an adapter.
RIO Scanner Scan
The scanner updates its input image file each time it scans a logical device.
Scanner
Input
Image File
Output
Device 3
Input
Device 3
Output
Device 2
Input
Device 1
Output
Device 1
Input
Device 2
Scanner Output
Image File
Publication 1747-UM013B-EN-P - January 2005
SLC and Scanner Asynchronous Operation
The SLC processor scan and RIO scanner scan are independent
(asynchronous) of each other. The SLC processor reads the scanner input image file during its input scan and writes the output image file to the scanner during its output scan. The RIO scanner continues reading inputs and writing outputs to the scanner I/O image file, independent of the SLC processor scan cycle.
Depending on your SLC processor, RIO link configuration, and application program size, the scanner may complete multiple scans before the SLC processor reads the scanner’s input image file. The RIO scanner updates its I/O files on a per logical rack basis.
Overview 1-5
The figure below illustrates the asynchronous operation of the SLC processor and RIO scanner.
SLC Processor Scan Cycle
The SLC processor reads the scanner input image file into the
SLC input image file, processes it, and creates an SLC output image file. The SLC processor transfers its output file to the scanner..
Program
SLC Input
Image File
Scanner
Input
Image File
Output
Image
Device 3
Input
Image
Device 3
Output
Image
Device 2
RIO Scanner Scan Cycle
Input
Image
Device 1
Input
Image
Output
Image
Device 1
Device 2
The scanner updates its input image file each time it scans a logical device.
The scanner may scan all of its configured logical devices several times before the SLC processor reads the scanner's input image file.
SLC Processor
SLC Output
Image File
Scanner Output
Image File
Important: The outputs of the RIO are updated after the end of the first SLC processor scan.
How the Scanner Interacts with Adapters
The scanner’s function is to continuously scan the adapters on the RIO link in a consecutive manner. This scan consists of one or more RIO discrete transfers to each adapter on the RIO link.
RIO discrete transfers consist of the scanner sending output image data and communication commands to the adapter that instruct the adapter on how to control its output. (These include run, adapter reset, and reset decide commands.) The adapter responds by sending input data to the scanner. The scanner performs as many RIO discrete transfers as necessary to update the entire adapter image. If RIO discrete transfers do not occur, data is not exchanged between the scanner and adapter. RIO discrete transfers are asynchronous to the processor scan.
Publication 1747-UM013B-EN-P - January 2005
1-6 Overview
Processor Scanner
SLC Local Chassis
Scanner I/O Image
Concepts
RIO Discrete
Transfers
with Adapter 1
RIO Discrete
Transfers
with Adapter 2
PanelView Operator
Terminal
RIO Discrete
Transfers
with Adapter 3
RIO Discrete
Transfers
with Adapter 4
RediPANEL
The scanner’s I/O image consists of RIO logical racks and I/O groups.
A full RIO logical rack consists of eight input image and eight output image words. (A word consists of 16 bits of data.) Each word within an RIO logical rack is assigned an I/O group number from 0 to 7.
You assign devices on the RIO link a portion of the scanner’s image.
Devices can occupy a quarter logical rack (2 input and output words), half logical rack (4 I/O words), three-quarter logical rack (6 I/O words), or full logical rack. You may configure devices to start at any even I/O group number within an RIO logical rack. More than one physical device’s (adapter) I/O information can reside in a single logical rack. Also, by crossing logical rack boundaries, a device can consist of more than one logical rack.
IMPORTANT
The following illustration shows only the input image configuration of the scanner’s I/O image. The output image configuration is the same.
Publication 1747-UM013B-EN-P - January 2005
Overview 1-7
RIO
Logical
Rack 0
RIO
Logical
Rack 1
RIO
Logical
Rack 2
RIO
Logical
Rack 3
Bit Number (decimal)
Rack 2 Group 3
Rack 2 Group 4
Rack 2 Group 5
Rack 2 Group 6
Rack 2 Group 7
Rack 3 Group 0
Rack 3 Group 1
Rack 3 Group 2
Rack 3 Group 3
Rack 3 Group 4
Rack 3 Group 5
Rack 3 Group 6
Rack 3 Group 7
Rack 0 Group 0
Rack 0 Group 1
Rack 0 Group 2
Rack 0 Group 3
Rack 0 Group 4
Rack 0 Group 5
Rack 0 Group 6
Rack 0 Group 7
Rack 1 Group 0
Rack 1 Group 1
Rack 1 Group 2
Rack 1 Group 3
Rack 1 Group 4
Rack 1 Group 5
Rack 1 Group 6
Rack 1 Group 7
Rack 2 Group 0
Rack 2 Group 1
Rack 2 Group 2
Bit Number (octal)
Word 11
Word 12
Word 13
Word 14
Word 15
Word 16
Word 17
Word 18
Word 19
Word 20
Word 21
Word 22
Word 23
Word 24
Word 25
Word 26
Word 27
Word 28
Word 29
Word 30
Word 31
Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
Word 8
Word 9
Word 10
15 14
17
8
16
8
13
15
8
12 11 10 9
14
8
13
8
12
8
11
8
8
10
8
7
7
8
6
6
8
5
5
8
4
4
8
3
3
8
2 1
2
8
1
8
0
0
8
Quarter Logical
Rack
Not Used In This
Example
Half Logical
Rack
Not Used In This
Example
Three-Quarter
Logical Rack
Not Used In This
Example
Full
Logical
Rack
Example Scanner I/O Image
The illustrations below show a scanner’s input image of 4 RIO link devices.
Publication 1747-UM013B-EN-P - January 2005
1-8 Overview
SLC 5/02 or Later
Processor
RIO
Scanner
Device 1
Full Logical Rack
Device
Begins at Logical
Rack 0, Group 0.
Device 2
Three-Quarter Logical
Rack Device
Begins at Logical
Rack 1, Group 0.
Device 3
Half Logical Rack
Device
Begins at Logical
Rack 2, Group 0.
Device 4
Quarter Logical Rack
Device
Begins at Logical
Rack 2, Group 4.
RIO
Logical
Rack 0
RIO
Logical
Rack 1
RIO
Logical
Rack 2
RIO
Logical
Rack 3
Word 8
Word 9
Word 10
Word 11
Word 12
Word 13
Word 14
Word 15
Word 16
Word 17
Word 18
Word 19
Word 20
Word 21
Word 22
Word 23
Word 24
Word 25
Word 26
Word 27
Word 28
Word 29
Word 30
Word 31
Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
Rack 0 Group 0
Rack 0 Group 1
Rack 0 Group 2
Rack 0 Group 3
Rack 0 Group 4
Rack 0 Group 5
Rack 0 Group 6
Rack 0 Group 7
Rack 1 Group 0
Rack 1 Group 1
Rack 1 Group 2
Rack 1 Group 3
Rack 1 Group 4
Rack 1 Group 5
Rack 1 Group 6
Rack 1 Group 7
Rack 2 Group 0
Rack 2 Group 1
Rack 2 Group 2
Rack 2 Group 3
Rack 2 Group 4
Rack 2 Group 5
Rack 2 Group 6
Rack 2 Group 7
Rack 3 Group 0
Rack 3 Group 1
Rack 3 Group 2
Rack 3 Group 3
Rack 3 Group 4
Rack 3 Group 5
Rack 3 Group 6
Rack 3 Group 7
Important: The illustration below shows only the scanner's input image. The output image looks the same.
Bit Number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Input File
Address
I:e.9
I:e.10
I:e.11
I:e.12
I:e.13
I:e.14
I:e.15
I:e.16
I:e.17
I:e.18
I:e.19
I:e.20
I:e.21
I:e.22
I:e.23
I:e.0
I:e.1
I:e.2
I:e.3
I:e.4
I:e.5
I:e.6
I:e.7
I:e.8
I:e.24
I:e.25
I:e.26
I:e.27
I:e.28
I:e.29
I:e.30
I:e.31
Device 1
Device 2
Not Used
Device 3
Device 4
Not Used
Bit Number (octal) 17
8
16
8
15
8
14
8
13
8
12
8
11
8
10
8
7
8
6
8
5
8
4
8
3
8
2
8
1
8
0
8 e = slot number of the SLC chassis containing the scanner
Publication 1747-UM013B-EN-P - January 2005
Overview 1-9
Transferring Data with RIO Discrete and Block Transfers
Input and output image data and command information are quickly exchanged between a scanner and adapter using RIO discrete transfers. RIO discrete transfers are the simplest and fastest way a scanner and adapter communicate with each other. RIO discrete transfers, which are transparent to the user, consist of the scanner sending the output image data to the adapter, and the adapter transmitting input data to the scanner. Each RIO discrete transfer also contains scanner commands for the adapter.
Through your control program, you command the SLC processor to initiate RIO block transfers, which directs the scanner to exchange large amounts of data to/from an adapter. Block Transfers (BTs) use the basic RIO discrete transfer mechanism of the RIO link. However, the actual transfer of data occurs asynchronous to the discrete transfers. It is possible for several discrete transfers to occur before the scanner processes a block transfer. Refer to Chapter 5, RIO Block
Transfer for more details.
Physical and Logical RIO Link Specifications
The maximum number of adapters with which your scanner can communicate is determined by the scanner’s and adapter’s physical and logical specifications, as described below:
• Physical Specifications are the maximum number of adapters that can be connected to the scanner. For more information, see
Extended Node Capability below.
• Logical Specifications for the scanner are the maximum number of logical racks the scanner can address, how the logical racks can be assigned, and whether the scanner can perform BTs.
Extended Node Capability
Extended node functionality allows you to connect up to 32 physical devices on an RIO link. You must use 82 Ohm RIO link resistors in an extended node configuration. You can only use extended node if all
RIO link devices have extended node capability. (Refer to the
Compatible Devices table at the end of this chapter, or to the specifications of your device.) The 1747-SN Series B Scanner has extended node capability. However, the smallest logical rack division is 1/4 logical rack and the scanner image size is 4 logical racks.
Therefore, the scanner is limited to 16 devices unless complementary
Publication 1747-UM013B-EN-P - January 2005
1-10 Overview
Publication 1747-UM013B-EN-P - January 2005
I/O is used. Refer to the following section for more information on complementary I/O.
Complementary I/O
Complementary I/O is very useful when portions of your input and output images are unused because it allows the images of two adapters to overlap each other in the scanner’s I/O image. To use complementary I/O, the I/O image from one adapter must be the mirror (complement) of the other. This means that there must be an input module in the primary chassis and an output module in the same slot of the complementary chassis. This enables total use of the scanner’s 32 input and 32 output word image for I/O addressing of up to 1024 discrete points.
ATTENTION
Because the primary and complementary chassis images overlap, input and specialty combination I/O modules must never share the same image location.
Inputs received by the scanner may be incorrect and
RIO block transfers will not be serviced properly.
If an output module shares its output image with another output module, both output modules receive the same output information.
If you want to use complementary I/O, two adapters that support this function are required (e.g., 1747-ASB modules). One adapter is configured (via its DIP switches) as a primary chassis, the other as a complementary chassis. If a primary chassis exists, it is scanned first.
Primary and complementary chassis cannot have the same logical rack number. The logical rack numbers must be assigned to the primary and complementary racks as shown below:
0
1
2
3
Primary Chassis Logical
Rack Number
9
10
11
Complementary Chassis Logical Rack Number
Decimal Octal
8 10
11
12
13
Overview 1-11
ATTENTION
If the logical rack numbers are not properly assigned, unpredictable operation of both ASB modules results. No ASB module errors occur. Refer to your ASB module user manual for specific information on setting the address of the complementary chassis. (For example, in the
1771-ASB manual the addresses for the complementary chassis are referred to as complementary chassis 0-3.)
Guidelines for Configuring Complementary I/O
When you configure your remote system for complementary I/O, follow these guidelines:
• You can place an output module in the primary chassis opposite another output module in the complementary chassis; they use the same bits in the output image table. However, we do not recommend this placement of modules for redundant I/O.
• You cannot use complementary I/O with a chassis that uses
32-point I/O modules and 1-slot addressing or 16-point I/O modules with 2-slot addressing.
• Do not place an input module in the primary chassis opposite an input module in the complementary chassis; they will use the same bits in the input image table.
Publication 1747-UM013B-EN-P - January 2005
1-12 Overview
Example 1
Example 2
Complementary I/O: Placing Modules with 2-Slot Addressing
The following figures illustrate a possible module placement to configure complementary I/O using 2-slot addressing.
I
8
I
8
O
8
O
8
I
16
O
16
O
8
1
O
8
BT
I
8
O
8
1
BT O
8
0 1 2 3 4 5
O
8
O
8
I
8
I
8
E
M
P
T
Y
E
M
P
T
Y
O
8
1
O
8
1
E
M
P
T
Y
2
O
8
2
E
M
P
T
Y
2
E
M
P
T
Y
2
I
16
O
16
I
16
O
16
I
16
O
16
I
16
O
16
I
16
O
16
I
16
O
16
0 1 2 3 4 5
Outputs in the complementary chassis would use the same bits in the output image table as the outputs in the primary chassis. You cannot place inputs in the complementary chassis.
1 = Output modules use the same output image table bits. This is not recommended.
2 = Must be empty if corresponding primary slot is a block transfer module.
Important: With 2-slot addressing, if an input module resides in either slot associated with a logical group of the primary chassis, an input module cannot reside in that logical group' s complementary chassis.
Publication 1747-UM013B-EN-P - January 2005
Example 1
Example 2
Overview 1-13
Complementary I/O: Placing Modules with 1-Slot Addressing
The figure below illustrates a possible module placement to configure complementary I/O using 1-slot addressing.
I
16
I
16
O
16
O
16
I
16
O
16
O
16
1
BT I
16
O
16
O
16
I
16
0 1 2 3 4 5 6 7 0 1 2 3
O
16
O
16
I
16
I
16
O
16
I
16
O
16
1
T
Y
E
M
P
2
O
16
I
16
I
16
O
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
I
16
0 1 2 3 4 5 6 7 0 1 2 3
O
16
O
16
O
16
O
16
O
16
O
16
O
16
O
16
O
16
O
16
O
16
O
16
I = Input Module (8- or 16-point) O = Output Module (8- or 16-point)
BT = Block Transfer Module
1 = Output modules use the same output image table bits. This is not recommended.
Publication 1747-UM013B-EN-P - January 2005
1-14 Overview
Example 1
Example 2
Complementary I/O: Placing Modules with 1/2-Slot Addressing
The figure below illustrates a possible module placement to configure complementary I/O using 1-slot addressing.
O
I I O O I O O BT O
1
I
01 23 45 67 01 23 45 67 01 23
O I I O I O
1
T
Y
E
M
P
2
I O
I I I I I I I I I I
01 23 45 67 01 23 45 67 01 23
O O O O O O O O O O
I = Input Module (8-, 16-, or 32-point) O = Output Module (8-, 16-, or 32-point)
BT = Block Transfer Module
1 = Output modules use the same output image table bits. This is not recommended.
Publication 1747-UM013B-EN-P - January 2005
Overview 1-15
Summary for Placing Modules Used In Complementary I/O
Discrete Modules
Addressing Method
2-slot
Types of Modules used
8-point
Placement
Install input modules opposite output modules, and output modules opposite input modules.
(1)
1-slot
1/2-slot
8-point, 16-point
8-point, 16-point, 32-point
(1) If an input module resides in either slot associated with a logical group of the primary chassis, an input module cannot reside in that logical group’s complementary chassis.
Block Transfer Modules
Addressing Method
2-slot
1-slot
1/2-slot
Placement
The right slot of the primary I/O group can be another block transfer module, or an 8-point input or output module.
The left slot of the complementary I/O group must be empty.
In the right slot of the complementary I/O group, you can place an 8-point output module; this slot must be empty if the corresponding slot in the primary I/O group is a block transfer module.
Leave the corresponding I/O group in the complementary chassis empty.
Leave the corresponding I/O group in the complementary chassis empty.
The following example illustrates how I/O modules requiring two words of the input or output image can leave unused image space.
Publication 1747-UM013B-EN-P - January 2005
1-16 Overview
I
O
I
O
I
O
I
O O
I
O
I
O
I
O
I
I = Input Module
O = Output Module
Slot 0 1 2 3 4 5 6 7 8
Slot Pair
1 2 3 4
Primary Chassis
Primary Chassis Configured As:
Logical Rack Number
Logical Group Number
Image Size (logical groups)
Addressing Mode
Primary/Complementary
0
0
16
1/2-slot
Primary
Slot 0 1 2 3 4 5 6 7 8
Slot Pair
1 2 3 4
Complementary Chassis
Complementary Chassis Configured As:
Logical Rack Number 8 (decimal)
Logical Group Number
Image Size (logical groups)
0
16
Addressing Mode
Primary/Complementary
1/2-slot
Complementary
17
15
Primary Chassis I/O Image
Input Image from Primary Chassis
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
10
8
7
7
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
0
0
1
2
3
4
Octal
Decimal
Slot Pair
Output Image from Primary Chassis
17
15
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
10
8
7
7
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
0
0
Octal
Decimal
1
2
3
4
Slot Pair
= unused image space
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Complementary Chassis I/O Image
Input Image from Complementary Chassis
17
15
10
8
7
7
0
0
Octal
Decimal
Output Image from Complementary Chassis
17
15
10
8
7
7
0
0
Octal
Decimal
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
1
2
3
4
Slot Pair
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 7
Slot 8
Slot 8
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
1
2
3
4
Slot Pair
Scanner's I/O Image
Both images are overlapped in the scanner. The overlapped image appears where the primary chassis image is configured to reside.
In this case, the primary chassis image is configured as starting logical rack 0 and starting logical group 0.
Logical
Rack 0
Logical
Rack 1
Input Image
Group 0
Group 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 0
Group 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
17
15
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Slot 7
Slot 8
Slot 8
10
8
7
7
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Slot 7
Slot 8
Slot 8
0
0
1
2
3
4
Octal
Decimal
Slot Pair
Output Image
17
15
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Slot 7
Slot 8
Slot 8
10
8
7
7
Slot 4
Slot 5
Slot 5
Slot 6
Slot 6
Slot 7
Slot 1
Slot 1
Slot 2
Slot 2
Slot 3
Slot 3
Slot 4
Slot 7
Slot 8
Slot 8
0
0
1
2
3
4
Octal
Decimal
Slot Pair
Publication 1747-UM013B-EN-P - January 2005
Logical
Rack 0
Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
Overview 1-17
Complementary I/O Application Considerations
If you configure a complementary device to use more I/O image space than an associated primary device, then block transfers can only be performed to locations in the complementary device that have associated I/O image space in the primary device. For example, if a primary device is 1/2 logical rack and a complementary device is a full logical rack, block transfers can be performed only in the first 1/2 logical rack of the complementary device. Attempting block transfers in the last half of the complementary device will result in a BT error
(error - 11 - device not configured).
1/2 logical rack configured and usable
1/2 logical rack not
Logical
Rack 8 configured
Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7
1/2 logical rack configured, but not configured for the primary device.
configured for the primary device.
Complementary 1771 I/O Module Details
Use the following modules in either primary or complementary I/O chassis opposite any type of module:
• Communication Adapter Module (1771-KA2)
• Communication Controller Module (1771-KE)
• PLC-2 Family/RS-232-C Interface Module (1771-KG)
• Fiber Optics Converter Module (1771-AF)
• DH/DH+ Communication Adapter Module (1785-KA)
• DH+/RS-232C Communications Interface Module (1785-KE)
Use the following modules in either primary or complementary I/O chassis opposite any type of module. However, these modules do not work as stand-alone modules; each one has an associated master module. Use care when placing the master modules in the I/O chassis:
• Analog Input Expander Module (1771-E1, -E2, -E3)
• Analog Output Expander Module (1771-E4)
• Servo (Encoder Feedback) Expander Module (1771-ES)
• Pulse Output Expander Module (1771-OJ)
Publication 1747-UM013B-EN-P - January 2005
1-18 Overview
Hardware Features
Publication 1747-UM013B-EN-P - January 2005
Below are the scanner’s features. You can find LED information in
Chapter 6, Troubleshooting.
SCANNER
COMM FAULT
FRN.: PLUG
2
SW1
O
N
1 2
/
1 2
ON ON
ON
OFF
OFF
ON
OFF OFF
KBAUD
57.6
115.2
230.4
230.4
CONNECT ONE END OF
CABLE SHIELD TO CHASSIS
MOUNTING BOLT. REFER T O
USER'S MANUAL.
LINE 1
SHIELD
LINE 2
B
1747±SN
7
3
4
6
5
1. Status Led
2. Front Label
3. RIO Link Connector
4. Cable Tie Slots
Displays normal communication and fault status
Allows user to record configured baud rate
Allows for connections to RIO link devices
Secures communication wiring from module
5. Self-Locking Tabs Secures module in chassis slot
6. Side Label (Nameplate) Provides module information
7. Baud Rate DIP Switch Allows user to set baud rate
1
Baud Rate DIP Switch
The Baud Rate DIP switch selects the RIO link baud rate. The baud rates are:
• 57.6 Kbaud
• 115.2 Kbaud
• 230.4 Kbaud
IMPORTANT
For proper system operation, the baud rate of all devices on the RIO link must be the same.
Overview 1-19
LEDs
Two LEDs allow you to monitor scanner and communication status.
FAULT LED - allows you to monitor scanner status. This LED is red.
The FAULT LED’s normal state is off; therefore, it is off whenever the scanner is operating properly.
COMM LED - allows you to monitor communication with all configured devices. This LED is green and its normal state is on once the processor has entered Run mode. The LED is red if there is a communication problem. The COMM LED status information is valid only when the FAULT LED is off.
RIO Link Connector
This 3-pin male connector connects the scanner to the RIO link. The
Allen-Bradley repair part number is 1746-RT29.
Compatible Devices
Catalog Number
1785-LT/x
(1) (2)
1785-L30x
1785-L40x
1785-L60x
1771-ASC
1771-ASB
(3) (4)
1771-AM1
1771-AM2
1784-F30D
1771-RIO
Device
PLC- 5/15 (in adapter mode)
PLC- 5/25 (in adapter mode)
PLC- 5/12 (in adapter mode)
PLC- 5/30 (in adapter mode)
PLC- 5/40 (in adapter mode)
PLC- 5/60 (in adapter mode)
Remote I/O Adapter Module
Remote I/O Adapter Module
1-Slot I/O Chassis W/Integral Power Supply and
Adapter
-
2-Slot I/O Chassis W/Integral Power Supply and
Adapter
-
Plant Floor Terminal Remote I/O Expansion
Module
Remote I/O Interface Module -
-
-
-
-
-
-
-
-
Comments
Publication 1747-UM013B-EN-P - January 2005
1-20 Overview
Catalog Number
1771-JAB
1771-DCM
1747-DCM
2705-xxx
2711-xx
Device
Single Point I/O Adapter Module Single Point I/O
Adapter Module
-
Comments
Direct Communication Module
Remote I/O Adapter Module -
-
Direct Communication Module
DL40 Dataliner
RediPANEL
PanelView Terminal
-
-
-
Requires half logical rack configuration if you want to use stored messages.Requires half logical rack configuration if you want to use stored messages.
You can address PanelView Terminals as up to four full logical racks of discrete I/O. You can also assign partial logical racks.You can address PanelView Terminals as up to four full logical racks of discrete I/O. You can also assign partial logical racks.
1336-G2
1395-NA
1791-xxx
1794-ASB
Remote I/O Adapter for 1336 AC Industrial
Drives
Remote I/O Adapter for 1395 DC Industrial
Drives
Block I/O Products
SLC 500 Remote I/O Adapter Module
Flex I/O 24VDC Remote I/O Adapter
(1) Extended node capability
(2) In adapter mode
(3) Series A, B, and C
(4) Extended node capability for Series B and C
(5) Must be Catalog Number 2706-ExxxxxB1
-
-
-
The adapter is built into the block.
Publication 1747-UM013B-EN-P - January 2005

Public link updated
The public link to your chat has been updated.
Advertisement
Key features
- Supports communication with remotely located I/O devices
- Provides discrete I/O and block transfers
- Maximum communication distance of 3,048 meters (10,000 feet)
- Supports complementary I/O
- Extended node capability for up to 32 devices
- Asynchronous operation with the SLC processor
- Supports a maximum of 4 logical racks
- User-configurable G files for flexible configuration
- M0 and M1 status files for device monitoring
- LEDs for easy fault identification