Power, Input, and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b)
of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian
Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following
warnings must be heeded:
A WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR
CLASS I, DIV. 2;
B WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE
REPLACING OR WIRING MODULES
C WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS.
D THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.
All ProLinx® Products
WARNING – EXPLOSION HAZARD – DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.
AVERTISSEMENT – RISQUE D'EXPLOSION – AVANT DE DÉCONNECTER L'EQUIPMENT, COUPER LE
COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DÉSIGNÉ NON DANGEREUX.
Markings
UL/cUL ISA 12.12.01 Class I, Div 2 Groups A, B, C, D
cUL C22.2 No. 213-M1987
243333 183151
CL I Div 2 GPs A, B, C, D
Temp Code T5
II 3 G
Ex nA nL IIC T5 X
0° C <= Ta <= 60° C
II – Equipment intended for above ground use (not for use in mines).
3 – Category 3 equipment, investigated for normal operation only.
G – Equipment protected against explosive gasses.
ProLinx Gateways with Ethernet Ports
Series C ProLinx™ Gateways with Ethernet ports do NOT include the HTML Web Server. The HTML Web Server
must be ordered as an option. This option requires a factory-installed hardware addition. The HTML Web Server now
supports:
8 MB file storage for HTML files and associated graphics files (previously limited to 384K)
32K maximum HTML page size (previously limited to 16K)
To upgrade a previously purchased Series C model:
Contact your ProSoft Technology distributor to order the upgrade and obtain a Returned Mercha ndise Authorization
(RMA) to return the unit to ProSoft Technology.
To Order a ProLinx Plus gateway with the -WEB option:
Add -WEB to the standard ProLinx part number. For example, 5201-MNET-MCM-WEB.
Your Feedback Please
We always want you to feel that you made the right decision to use our products. If you have suggestions, comments,
compliments or complaints about the product, documentation, or support, please write or call us.
Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products
and services of, their respective owners.
®
, ProLinx ®, inRAx ®, ProTalk®, and RadioLinx ® are Registered Trademarks of ProSoft
ProSoft Technology® Product Documentation
In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments.
User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provide d on the enclosed CD-ROM,
and are available at no charge from our web site: www.prosoft-technology.com
Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability.
North America: +1.661.716.5100
Asia Pacific: +603.7724.2080
Europe, Middle East, Africa: +33 (0) 5.3436.87.20
Latin America: +1.281.298.9109
The ProLinx Remote I/O (RIO) Adapter communication interface can be used to
interface Rockwell Automation Remote I/O Scanners (PLC, SLC, ControlLogix)
to other communication networks. The RIO interface, as the other solutions in the
ProLinx family, interface to the other communication networks via the module's
internal data table.
1.1 Remote I/O Port
Blue Shield Clear
Blue Shield Clear
12
12
The RIO interface is an adapter (slave) and is connected to a scanner (master)
that controls the data transfer.
For example, the master/slave relationship can be accomplished using the 460XRIO-XXX module (adapter/slave unit) with the Rockwell Automation PLC5
(scanner/master unit). Ladder logic must be programmed into a PLC to perform
BTR/BTW commands to receive and transmit data between the module and the
PLC. The module also supports limited high speed data transfer via the Input and
Output images.
1.2 Module Internal Database
ACTIVE
ACTIVE
ProSoft Technology, Inc. Page 7 of 39
February 4, 2010
The internal database is central to the functionality of the module. This database
is shared between all the ports on the module and is used as a conduit to pass
information from one device on one network to one or more devices on another
network. This permits data from devices on one communication port to be viewed
and controlled by devices on another port.
In addition to data from the slave and master ports, status and error information
generated by the module can also be mapped into the internal database.
1.2.1 Remote I/O Access to Database
This same internal database is used by the RIO interface to pass information
between the module and the RIO scanner.
A RIO scanner attached to the module can request data from the module’s
database using BTR commands. BTW commands transfer data from the RIO
scanning device to the module’s database. Each data-block is capable of
transferring up to 60-words of data in each block. The module sequentially steps
through the list of read and write blocks configured in the module to transfer the
data between the module and the RIO scanner. The following illustration shows
these relationships:
4601-RIO-MCM Module
Module’s
Internal
Database
Master
Driver
Logic
Slave
Driver
Logic
To Modbus
Slave
Devices
To Modbus
Master
Device
Input Image
Read Data
Write Data
Output Image
Processor
Ladder logic
transfers
data from
module using
BTR commands
Ladder logic
transfers
data to
module using
BTW commands
Input Image
BTR Blocks
RIO Interface
BTW Blocks
Output image
In addition to the block transfer operations, the module reports high-speed data to the RIO scanner
through the input and output image table. The size of this table depends on the rack size selected.
The following table defines the input/output word count for the different rack size selections:
The source for the input word(s) and the destination of the output word(s) in the
internal database is user configured via the CFG file (See [RIO] section in this
manual). Each word is associated with an independent register in the database.
The following illustration shows the relationship between the internal database,
the input map and processor input image:
Input File
Word
0
1
2
3
4
5
6
7
The Input Map acts as a data routing table,
allowing the user to configure the source of data
for the Input Image transferred to the RIO scanner
processor on a high-p ri o r i ty basis.
Input Map
1
100
101
200
201
405
4141
Module Database
0
1
100
101
200
201
405
4141
The same relationship exists for the output image except the data is transferred
from the PLC to the module’s database.
ProSoft Technology, Inc. Page 9 of 39
February 4, 2010