Allen-Bradley 1747-SN: RIO Mapping and Link Fault Checks

The Allen-Bradley 1747-SN is the Remote I/O (RIO) scanner for an SLC 500 controller. Replacing a failed scanner is not simply a matter of installing another module with the same catalog number. The original logical rack allocation, network speed, wiring, and scanner series must still match the running system. A replacement can appear healthy at the backplane while one or more remote I/O groups remain unavailable.

This guide separates the scanner's configuration from the RIO physical layer, so maintenance teams can document the existing system and diagnose faults before replacing hardware. The figures below come from Rockwell Automation's 1747-SN installation instructions and SLC documentation; troubleshooting priorities are PLC ProTech's engineering interpretation.

Understand the scanner and adapter roles

A local SLC 5/02 or later processor communicates with remote chassis through the 1747-SN Remote I/O scanner. The scanner is the RIO master. At a remote 1746 chassis, an 1747-ASB adapter acts as a slave and presents remote I/O data to the scanner. Some legacy operator terminals and other RIO-compatible devices can also operate on the link.

Confusing these roles leads to an avoidable purchasing error: an adapter is not a scanner. The scanner must also agree with the addressing and image allocation configured for the remote devices. The wiring is a daisy-chained twisted-pair network, not an Ethernet star or a DeviceNet trunk.

Four logical racks do not mean four physical chassis

The 1747-SN transfers up to four logical racks of discrete data, a maximum of 32 input and 32 output image words. A logical rack contains eight I/O groups; a group represents one input word and one output word in the scanner image. A remote device can occupy a fraction of a logical rack, depending on its configured image size. Therefore, counting physical enclosures does not tell you how much scanner image space the project uses.

The SLC processor and RIO scanner operate asynchronously: the scanner exchanges data with the adapters, while the processor reads and writes the associated image through its own scan cycle. During maintenance, preserve the distinction between a live RIO connection, an assigned scanner image, and the logic addresses that the program actually uses.

Check the project's scanner G-file settings against the remote devices' logical rack and starting group assignments. Rockwell's 1747-SN user manual explains that the G-file is changed in an offline project and the modified configuration is then downloaded; it is not a setting to alter casually in a running controller. Record the original file and physical addressing before troubleshooting image mismatches.

RIO baud rate, cable length and termination

Every device on the RIO link must operate at the same baud rate. The 1747-SN supports 57.6, 115.2 and 230.4 kbaud, selected through its front-panel DIP switch. Rockwell publishes the following maximum link lengths for Belden 9463 cable:

RIO rate	Maximum total cable length	What to verify
57.6 kbaud	3,048 m (10,000 ft)	All devices share the rate and the configured termination
115.2 kbaud	1,524 m (5,000 ft)	Length, device settings and both physical ends
230.4 kbaud	762 m (2,500 ft)	Shorter length budget and extended-node capability

The link is terminated at both physical ends, not at every adapter. Rockwell's resistor selection depends on baud rate and whether extended-node capability is used. Do not copy a resistor value from another installation without confirming its link configuration. The same manual specifies grounding the cable shield at the scanner end only; for a retrofit, use the installation procedure appropriate to the scanner series.

These are network checks, not instructions to change switch positions on a live, safety-critical system. Follow the site's isolation and change-control procedures before touching hardware or field wiring.

Read FAULT and COMM LEDs before swapping modules

The scanner has separate FAULT and COMM indicators. Rockwell warns that the COMM indication is meaningful only when the FAULT LED is off. Use the indications to narrow the fault domain instead of immediately ordering a replacement.

Observed indication	Rockwell-defined meaning	First engineering check
FAULT flashing red	Scanner configuration error	G-file, configured device addresses, image sizes and downloaded project
FAULT steady red	Major scanner fault	Document hardware series and module state; investigate hardware after confirming supply
FAULT off; COMM green	Active communication with all configured devices	If I/O logic still fails, examine image mapping and application logic
FAULT off; COMM flashing green	At least one configured RIO device is not communicating	Identify the affected adapter, wiring segment and its rack address
FAULT off; COMM flashing red	None of the configured RIO devices is communicating	Check baud rate, cable continuity, both terminations and scanner-end shield ground

A green scanner indication does not verify every downstream sensor, actuator or program interlock. Conversely, flashing COMM does not automatically prove the scanner module is defective.

Series B block transfers need a separate check

Rockwell specifies block-transfer support of up to 64 words per remote device on 1747-SN Series B or later. This is separate from the four-logical-rack discrete image limit. If an operator terminal, drive or other adapter uses block transfers, document the scanner series, destination addresses, application instructions and adapter configuration before replacing the module.

For a worked example involving drive data, see our existing technical guide to 1747-SN block transfers with a PowerFlex 70 via RIO. That configuration should not be assumed to apply unchanged to another remote device.

Practical 1747-SN replacement record

1. Capture identity: Photograph the 1747-SN catalog label, series, firmware markings, slot position and any prior service notes.
2. Capture logic: Save the SLC program, scanner G-file, image allocation and a list of configured adapters, logical rack numbers and starting groups.
3. Capture network settings: Note DIP-switch baud rate, Belden 9463 or installed cable type, total network length and any extended-node configuration.
4. Record the fault: Log FAULT/COMM LED patterns while the system is in its documented operating state. Include which remote adapters are reachable.
5. Confirm power: The 1747-SN requires 600 mA at 5 VDC from the backplane. Verify the 1746 power-supply loading rather than treating the module's presence in a slot as proof of capacity.
6. Inspect the physical link: Check the scanner's 3-pin RIO connector, shield/earth arrangement, daisy-chain wiring and end termination according to the documented system.
7. Validate after replacement: Confirm the scanner can communicate with every configured adapter, that input/output image data maps correctly, and that any block-transfer behavior is restored before releasing the machine to operation.

Do not confuse the 1747-SDN DeviceNet scanner with the 1747-SN RIO scanner. They support different networks and should not be treated as interchangeable just because both are used in SLC 500 systems.

Discontinued hardware versus an engineered migration

Rockwell Automation lists the 1747-SN as discontinued effective March 31, 2024. Its current product page identifies an engineering replacement path, but that is not evidence of a direct slot-for-slot substitute. Migration requires a new review of controller architecture, network interfaces, wiring, application logic and validation. For plants maintaining existing RIO systems, an exact 1747-SN part number and matching configuration remain central procurement checks.

Primary technical sources

• Rockwell Automation, 1747-IN060D-EN-P, Remote I/O Scanner Installation Instructions (November 2002): network rates, wiring, power draw and LED diagnostics.
• Rockwell 1747-SN product page: current lifecycle and engineering replacement classification.
• Rockwell SLC 500 technical literature index: 1747-UM013 user manual and related SLC documentation.

Engineering note: This article describes documented module behavior and maintenance checks, not a substitute for the machine-specific electrical drawings, safety procedures or validated control-system configuration.