Create Remote I-O Adapter and Rack

You use a Remote I/O (RIO) rack entry in the
Controller Organizer I/O Configuration
 module tree to establish a communication path between the controller and a RIO Adapter.
A rack is a data structure that comprises eight I/O Groups of input and output data available via an adapter. A single adapter may present a partial rack, a whole rack, or multiple racks.
I/O group
A group of input and/or output circuits corresponding to a word in the input and output image tables.
In the
ControlLogix
 system, RIO links are accessed through the 1756-DHRIO module. RIO rack entries under a 1756-DHRIO in the module tree each represent a partial or whole rack of data. When an adapter supports multiple racks, multiple rack entries are necessary for the adapter, each representing a separate rack.
As with other module tree entries, RIO rack entries cannot be created while attached to the processor.
To create a remote I/O adapter and rack
  1. Select the desired 1756-DHRIO entry in the
    Controller Organizer I/O Configuration
     module tree.
  2. From the
    File
    menu, choose
    New Component/Module
    .
  3. Choose one of the RIO Adapter module types from the
    Select Module
    dialog module type list.
    RIO Adapter module type entries include "1747-ASB," "1771-ASB," "1794-ASB," and "RIO-ADAPTER." (RIO-ADAPTER is a generic module type that can be used with any RIO adapter. The three specific adapter types provided are for documentation purposes only; there is no difference in behavior between the four RIO Adapter module types. )
  4. Select
    OK
    .
  5. Enter a name.
    name
    A title with 40 characters. It must start with a letter or underscore ("_"), however, all other characters can be letters, numbers, or underscores. Names cannot contain two contiguous underscore characters and cannot end in an underscore.
    TIP:
    The naming conventions are based on the IEC-1131 rules for identifiers.
    The name must be unique among all modules in the module tree.
  6. Enter a description for the new module, if desired.
    description
    A representation that can be a maximum of 128 bytes in length. You can use any printable character; carriage returns, tabs, and spaces are also supported. Standard ASCII characters consume 1 byte per character, allowing for 128 characters. Note that some characters (for instance, those used for Asian languages) take up to three bytes to represent one character, resulting in less than 128 characters maximum.
  7. Choose the Parent Channel.
    The Parent Channel is the channel on the parent 1756-DHRIO to which the target RIO adapter is connected. If only one channel of the parent 1756-DHRIO module is configured for RIO, that RIO channel will be shown as the default value.
  8. Enter the RIO rack number.
  9. Enter the starting group of the target adapter.
    Choices include 0, 2, 4 and 6.
  10. Enter the rack size.
    Choices include ¼ Rack (2 I/O Groups), ½ Rack (4 I/O Groups), ¾ Rack (6 I/O Groups) and Full Rack (8 I/O Groups).
  11. Select
    Next
    .
  12. Enter the Requested Packet Interval.
    requested packet interval (RPI)
    The amount of time (in milliseconds) between updates of data from the remote controller. This value is scaled as a real value from the microseconds stored in the controller. The local controller will receive data at least this fast.
    This value represents the maximum amount of time allowed between packets on the connection between the
    connection
    The link between networks and devices.
    controller and the intervening 1756-DHRIO module.
    controller
    A device that controls machines or processes elements (for example, a programmable controller or relay panel).
  13. Select
    Finish
    .
    Upon creation of the rack entry, tags are created to allow access to the rack data. The rack size and the starting group number for a rack are interdependent. A starting group larger than zero limits the possible rack size. A rack size larger than ¼ limits the possible starting group. The rack size and starting group must not result in an entry that overlaps a second rack entry.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.