Catalog Numbers

• 1756-EN2F/C, 1756-EN2T/D, 1756-EN2TK/D, 1756-EN2TP/A, 1756-EN2TPK/A,
  1756-EN2TPXT/A, 1756-EN2TR/C, 1756- EN2TRK/C, 1756-EN2TRXT/C,
  1756-EN2TXT/D, 1756-EN3TR/B, 1756-EN3TRK/B

Improved Product Resiliency for Firmware Revision 12.001

Product improvements have been made to increase product resiliency to potentially disruptive activities. These enhancements have been verified not to affect product safety, performance, expected life, configuration, or operation of the product. Rockwell Automation recommends that you follow good Industrial Control System (ICS) security practices that include regular product updates. To maintain authenticity, obtain product updates and new releases directly from Rockwell Automation.

• 1756-EN2F/C, 1756-EN2T/D, 1756-EN2TK/D, 1756-EN2TP/A, 1756-EN2TPK/A, 1756-EN2TPXT/A,
  1756-EN2TR/C, 1756- EN2TRK/C, 1756-EN2TRXT/C, 1756-EN2TXT/D

• The Time Sync Connection setting in the module definition is set for Time Sync and Motion
• Explicit Protected Mode is enabled

In ControlLogix Redundancy No Switchover After Reconnection When a Module has Entered a Lonely State (1355859)

In a Redundant Chassis Pair (RCP) configuration, a switchover does not occur after reconnection when an EtherNet/IP™ communication module has transitioned to a lonely state.

Class 1 Connections Lost when ControlLogix Redundancy Switchover Occurs Immediately After RAP Switchover (1190410)

Considering the following configuration:

•              Controller and 1756-EN2x in Redundant Chassis Pair (RCP)

•              Remote chassis that has a 1756- EN4TR Redundant Adapter Pair (RAP) and I/O modules

•              Controller has Class 1 connections to I/O from a remote chassis through a 1756-EN2x, then 1756-EN4TR RAP

When a Redundant Chassis Pair switchover follows closely after a Redundant Adapter Pair switchover, all Class 1 connections are lost.

Known Anomaly Identified as of:

• Firmware revision 2.007, 1756-EN2T, 1756-EN2TK, 1756-EN2TXT, 1756-EN2F, 1756-EN2FK
• Firmware revision 2.001, 1756-EN2TR, 1756-EN2TRK, 1756-EN2TRXT
• Firmware revision 3.004, 1756-EN3TR, 1756-EN3TRK

When a Cisco switch with IP Device Tracking enabled (Cisco IOS firmware that is released after August 2013) is used within the layer 2 broadcast domain, the following can occur:

• The module goes into a duplicate IP state after a power loss.
• The module goes into a duplicate IP state when the link for the module is reestablished.

For more information, see Tech Note 568750. The Tech Note is available at https://rockwellautomation.custhelp.com/app/answers/detail/a_id/568750. A separate login is required.

By default, Stratix™ Ethernet switches do not exhibit this behavior.

Not Valid Device Error

Known Anomaly Identified as of:

• Firmware revision 10.006, 1756-EN2T/D, 1756-EN2TK/D, 1756-EN2TXT/D
• Firmware revision 10.007, 1756-EN2TR/C, 1756-EN2TRK/C, 1756-EN2TRXT/C, 1756-EN3TR/B, 1756-EN3TRK/B
• Firmware revision 10.009, 1756-EN2F/C, 1756-EN2FK/C

In the Studio 5000 Logix Designer® application, a Not Valid Device error can occur. This error occurs when you change the module type from one of the previously listed modules to any of the other listed modules in the Change Type dialog box.

Rack-optimized Connections Can Cause an Ethernet Module to Assert (1186272, 1186282, 942336)

Five or more rack-optimized connections that are targeted to an Ethernet module cause the module to assert immediately. The module status display shows ‘RackInput.cpp LineXXX’ information in the assert message.

Updating a 1756-EN2T/D Module from Firmware Revision 10.00x to 11.00x can cause an Assert (1699446)

When you update a 1756-EN2T/D from firmware revision 10.00x to 11.00x, with the rotary switches set to 900 or 000, this assert occurs:

“Cycle power to unit: assert in file ../../../../../../../LNX/Platform/BSP/Chip/Ice2/BareMetalBSP_WatchdogIMPL.cpp Line 70”.

To recover from the assert, follow these steps:

1. Set the module rotary switches to 999 and insert into the chassis.
2. Set the module rotary switches to the desired settings and insert into the chassis (do not use switch settings 888, 000, or 900, as these are reserved for module reset and mode changes).

NOTE: Setting the module to out-of-box reset (rotary switches set to 888 and power cycle) does not recover the module from the assert state.

NOTE: With firmware revision 11.001 and later, the rotary switch settings 900 and 000 are reserved only for entering and exiting Protected Mode. For more information, see the ControlLogix EtherNet/IP Network Devices User Manual, publication 1756-UM004.

MNRF/Assert can Occur on a Module After RCP Switchover (1955194)

After a switchover due to a cable break, the redundant system may not recover to a synchronized state. This can lead to the module experiencing a major nonrecoverable fault/assert.

A ReadSocket Service Request of the TCP/IP Socket Object Returns Incorrect Values (3096193)

When a Socket Object instance is used for a TCP connection, the response to a ReadSocket service request returns 0 for the Family, Port, and IP address.

Incorrect Product Type String in EDS files (3297343)

The ProdTypeStr keyword in EDS files had the incorrect value of ‘Communication Module’. The correct value is ‘Communications Module’.

Module does not get IP Address Assigned from a DHCP Server (2188094, 2233611)

This anomaly was due to a change in the Dynamic Host Configuration Protocol (DHCP) standard, RFC 6842. This anomaly results in the module not being able to obtain an IP address through DHCP with some Stratix® switches that follow the updated standard.

For more information, see Knowledgebase Technote Some Ethernet devices do not obtain DHCP lease from Stratix 5800 as DHCP Server.

IP Address is Manually Configurable in DHCP Mode (1665460)

When a module is in DHCP mode, attempts to change the IP address manually are accepted, but the actual address remains the same.

Incorrect Delay Before Sending a Response to a Broadcast ListIdentity Request (1592443)

A module responds immediately to broadcast ListIdentity requests instead of delaying for a random period before responding.

Quick Change from BOOTP to DHCP is not reflected in the Module Settings (1489872)

After changing the module configuration from a Static IP address to BOOTP to DHCP in quick succession, the module uses the IP address obtained from the DHCP server, but the settings show an address obtained from the BOOTP server.

This happens when you:

1. Change from "Manually configure IP settings" to "Obtain IP settings automatically using BOOTP” and select Apply.
2. Then immediately change to “Obtain IP settings automatically using DHCP” and select Apply again.

PTP Announce Messages Have Incorrect PTP_TIMESCALE Value (1428782)

When a module is in the same chassis as the PTP Grandmaster, it sends PTP Announce Messages with an incorrect value for PTP_TIMESCALE.

Invalid IP Subnet Mask Allowed on Module (1418381)

The module does not check the validity of the subnet mask; therefore, an invalid subnet mask can be set on the module.

USB Port Cannot be Disabled Using a CIP Generic MSG Instruction (1356346)

USB port cannot be disabled using a CIP™ Generic MSG Instruction.