A-B 1783-HMS8TG8EG4CGN Stratix 5400 Ethernet Managed Switches

When remote analog I/O modules are connected to the owner-controller via a scheduled

ControlNet network, the RPI and RTS intervals still define when the module multicasts data

within its own chassis (as described in the previous section). However, only the value of the

RPI determines how often the owner-controller receives it over the network.

When an RPI value is specified for an input module in a remote chassis that is connected by a

scheduled ControlNet network, the RPI also ‘reserves’ a spot and instructs the module to

multicast data within its own chassis.

Whether the timing of this ‘reserved’ spot coincides with the exact value of the RPI, the control

system helps the owner-controller receive data at least as often as the specified RPI.

This illustration shows that the input data within the remote chassis is multicast at the

configured RPI. The ControlNet bridge module sends input data back to the owner-controller at

least as often as the RPI.

IMPORTANT

You must run RSNetWorx for ControlNet software whenever a new I/O module is added to a scheduled ControlNet chassis. 

When a module is permanently removed from a remote chassis, 

we recommend that you run RSNetWorx for ControlNet software to reschedule 

the network and optimize the allocation of network bandwidth. 

The I/O configuration portion of the RSLogix 5000® programming software generates the

configuration data for each I/O module in the control system, 

whether the module is in a local or remote chassis. 

A remote chassis, also known as networked, contains the I/O module but not the module’s owner-controller.

A remote chassis can be connected to the controller via a scheduled connection

on the ControlNet network or an EtherNet/IP network.

RSLogix 5000 configuration data is transferred to the controller during the program 

download and later transferred to the appropriate I/O modules. 

I/O modules in the local chassis, and modules in a remote chassis connected via the EtherNet/IP network, 

or unscheduled connections on the ControlNet network,

are ready to run as soon as the configuration data has been downloaded. 

However, to enable scheduled connections to I/O modules on the ControlNet network, 

you must schedule the network by using RSNetWorx for ControlNet software.

Running RSNetWorx™ software transfers configuration data to I/O modules on a 

scheduled ControlNet network and establishes a network update time (NUT) for the 

ControlNet network that is compliant with the desired communication options specified for each module during configuration.

Anytime a controller references a scheduled connection to I/O modules on a scheduled

ControlNet network, you must run RSNetWorx software to configure the ControlNet network.