ControlLogix 5590 Controller Features

This table lists the system, communication, and programming features available with
ControlLogix®
 5590 controllers.
Features
Description
Communication ports
One USB port, Type C 2.0. This USB port does not support powering external devices.
Two
EtherNet/IP™
 ports: 10 Mbps, 100 Mbps, 1 Gbps link speeds
Communication options
EtherNet/IP™
 is the preferred network.
The controller also supports these networks:
  • ControlNet®
  • DeviceNet®
  • DH+™
  • Universal Remote I/O
  • SynchLink™
  • Third-party process and device networks
Controller tasks
  • 32 tasks
  • Safety-enabled controllers have 31 standard tasks, 1 safety task
  • 1000 programs/task
  • Event tasks: all event triggers
Integrated motion
  • Integrated motion on the
    EtherNet/IP™
     network
  • Sercos interface
  • Analog options:
    • Encoder input
    • Linear displacement transducer (LDT) input
    • Serial Synchronous Input (SSI)
  • For a safety-enabled controller integrated motion is supported in the standard task and integrated safety speed and position monitoring is supported in the safety task.
Programming languages
For standard tasks, the controllers support:
  • Ladder Diagram (LD)
  • Structured Text (ST)
  • Function Block Diagram (FBD)
  • Sequential Function Chart (SFC)
For a Safety-enabled controller, the safety task only supports Ladder Diagram.
Integrated safety
A Safety-enabled controller supports:
  • Integrated safety on the
    EtherNet/IP™
     network (
    Kinetix®
     drives,
    PowerFlex®
     drives, safety components)
  • Distribute and control safety I/O (over
    EtherNet/IP™
     and
    DeviceNet®
     networks only)
  • Produce and consume safety tag data.
Other Features
  • Data access control
  • Firmware Supervisor
  • Secure Digital (
    microSD™
    ) card
  • Safety Connections (Safety-enabled controllers only)
  • Standard Connections

Controller Memory

The controller can use all of the standard memory for the standard program and all of the safety memory for the safety program at the same time, without affecting either capacity for that controller type. For example, a 1756-L915TS controller has 15 MB of standard memory and 12 MB of safety memory. You can use up to 15 MB for the standard program and up to 12 MB for the safety program at the same time.
Controller Memory
Catalog Number
Standard Memory
Safety Memory
1756-L902TS, 1756-L902TSXT
2 MB
2 MB
1756-L905TS, 1756-L905TSXT, 1756-L905TPSXT
5 MB
5 MB
1756-L908TS, 1756-L908TSXT
8 MB
8 MB
1756-L915TS, 1756-L915TSXT, 1756-L915TPSXT
15 MB
12 MB
1756-L925TS, 1756-L925TSXT
25 MB
12 MB
1756-L950TS, 1756-L950TSXT, 1756-L950TPSXT
50 MB
12 MB
1756-L980TS, 1756-L980TSXT, 1756-L980TPSXT
80 MB
12 MB

Controller Capacity

The following table shows the number of
EtherNet/IP™
 and OPC/UA nodes that are supported for each controller.
EtherNet/IP™
and OPC/UA Nodes
Catalog Number
EtherNet/IP™
 Nodes
OPC/UA Nodes
1756-L902TS, 1756-L902TSXT
30
300
1756-L905TS, 1756-L905TSXT, 1756-L905TPSXT
100
1000
1756-L908TS, 1756-L908TSXT
200
2000
1756-L915TS, 1756-L915TSXT, 1756-L915TPSXT
300
5000
1756-L925TS, 1756-L925TSXT
400
20,000
1756-L950TS, 1756-L950TSXT, 1756-L950TPSXT
500
50,000
1756-L980TS, 1756-L980TSXT, 1756-L980TPSXT
Recommended maximum: 600
100,000
IMPORTANT:
CIP Security Consideration
EtherNet/IP™
 Node count may be limited to less than 150 when CIP security is used with safety I/O.
If you use I/O data security (
CIP Security™
) for safety I/O, the maximum number of nodes supported is reduced as follows:
  • Number of non-secure nodes + 2 * (number of secure nodes, integrity only) + 4 * (number of secure nodes, integrity, and confidentiality) <= 150
or
  • Maximum nodes supported by the controller, whichever is less.
If you do not use secure connections, the controller catalog number dictates the maximum number of nodes.

Features Supported via the Safety Task

In Safety-enabled controllers, the Safety task supports a subset of features that are supported in the standard task as listed in the following table.
Feature
Safety Task
Standard Task
Add-on instructions
✔
✔
Instruction-based alarms and events
—
✔
Tag-based alarms
—
✔
Controller logging
✔
✔
Event tasks
(While the safety task cannot be an Event task, standard Event tasks can be triggered with the use of the Event instruction in the safety task.)
—
✔
Integrated motion
✔
Drive Safety Instructions for devices providing safe speed and position feedback.
✔
Analog motion
—
✔
Sercos motion
—
✔
Drive Safety Instructions
✔
—
Language switching
✔
✔
License-based source protection
—
✔
Online import of program components
—
✔
Online export of program components
✔
✔
Ladder Diagram (LD)
✔
✔
Structured Text (ST)
—
✔
Function block diagrams (FBD)
—
✔
Sequential function chart (SFC) routines
—
✔
IMPORTANT:
Safety Consideration
ControlLogix®
 5590 Safety-enabled controllers can produce standard tags as unicast or multicast, but they can only produce safety tags as unicast. The controllers can consume safety tags as either unicast or multicast.
When you configure a produced safety tag, you are only allowed to configure unicast connection options. The Logix Designer application does not allow you to configure multicast connection options.
When you configure a consumed tag, you must consider the capabilities of the producer:
  • If the producer in the I/O tree of this controller is a
    ControlLogix®
     5590 Safety-enabled controller,
    GuardLogix®
     5580 controller, or
    Compact GuardLogix®
     5380 controller, and you are consuming a safety tag, you must configure the consumed tag to use unicast.
  • If the producer in the I/O tree of this controller is a
    GuardLogix®
     5570 or 5560, or a
    Compact GuardLogix®
     5370, the safety consumed tag can be configured as either unicast or multicast.
  • ControlLogix®
     5590 Safety-enabled controllers do not produce safety tags to
    GuardLogix®
     5570 (firmware revision 30 or earlier) controllers in the same chassis, because
    ControlLogix®
     5590 Safety-enabled controllers can only produce safety tags as unicast, and
    GuardLogix®
     5570 (firmware revision 30 or earlier) controllers cannot configure consumed tags as unicast. This restriction does not apply over
    EtherNet/IP™
    , as consumed tags can be configured for unicast.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal