Rockwell Automation Allen-Bradley DriveLogix 5730, User Manual

Page: 56 / 209

3-8 Placing and Configuring Local I/O
Communication Formats
The communication format determines the data structure the I/O module
uses. Each format supports a different data structure. Presently, the
DriveLogix5730 controller supports two data formats:
•
Input Data – INT (for 1769 input modules)
•
Data – INT (for 1769 output modules)
The communication format determines the tag structure that is created for
the module. Assume that a 1769-IA16 Input module is in slot 1. The
software creates the appropriate tags using the slot number to differentiate
the tags for this example module from any other module.
Hold Last State and User-Defined Safe State Not Supported
If a local I/O module fails such that its communication to the controller is
lost, or if any module is disconnected from the system bus while under
power, the controller will go into the fault mode. All outputs turn off when
the system bus or any module faults.
TIP: The DriveLogix5730 controller must own its local I/O modules. No
other Logix-based controller can own the local Compact I/O.
!
ATTENTION: Risk of injury or equipment damage exists.
When 1769 Compact I/O modules are used as local I/O modules
in a DriveLogix5730 system, the local I/O modules do not
support the Hold Last State or User-Defined Safe State features,
even though you can configure these options in the programming
software. Precautions should be taken to ensure that these
settings do not create a hazard of injury or equipment damage.