A-B 1756-IT6I2 module Rockwell ControlLogix 6-point input control

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.

See the following general steps when configuring I/O modules.

1. Configure all I/O modules for a given controller by using RSLogix 5000 programming

software and download that information to the controller.

2. If the I/O configuration data references a scheduled connection to a module in a 

remote chassis that is connected via the ControlNet network, 

run RSNetWorx for ControlNet software to schedule the network.

3. After running RSNetWorx software, perform an online save of the RSLogix 5000 project

so the configuration information that RSNetWorx software sends to the controller is saved.

RTD Error

Module error on the 1756-IR6I module is defined in ohms and is calculated across 

the entire input range that is selected, not the available range of a sensor used with the module. 

For example, if the 1…487  input range is used, the module error is calculated across 507 (actual range = 0.86…507.86 ).

The error in ohms translates to temperature, but that translation varies because the

relationship is non-linear. The most effective way to check a 1756-IR6I module 

error is to calculate the error in ohms and use that value in a linearization table to check the temperatureerror.

If the module is calibrated at operating temperature and the operating temperature remains relatively stable, 

calibration accuracy is better than 0.1% of the full range for the first year after calibration. 

This 0.1% value is a worst case value. In other words, with the 1…487input range that is selected, 

the worst case module error is 0.507.

Finally, you must check an RTD linearization table to determine the temperature error

to which an error of 0.507translates. For example, if the 1756-IR6I has a 0.1% (or 0.507 ) 

error and is operating at 0 °C (32 °F), the temperature error is -1.25…1.2 °C (-2.25…2.16 °F) 

when the Platinum 385 sensor type is used. However, this same ohms error, 

when calculated in an operating temperature of 200 °C (392 °F), 

translates to a temperature error of -1.4 °C…1.4 °C (-2.52…2.52 °F).

You may also need the following related products：