The new version of the software brings new features and fixes for many b

Improvements:

• The Motion Axis Output Cam (MAOC) instruction now supports additional devices for scheduling. Up to 16 scheduled outputs are now supported.
• The controller supports the use of an Event task with its embedded input points. You can configure embedded input-point terminals to trigger an Event task if a change of state (COS) occurs.
• You can use Extended Properties to define additional information about a tag or the structure of tags.
• The Logix Designer application, version 21 or later, provides the option to specify Engineering Units and Min/Max Values for numeric tags, Engineering Units, and state information for Boolean tags.

Resolved Issues:

• When using the Automatic Device Configuration (ADC) feature, the Logix controller ‘owns’ the configuration in the drive.
• Your controller might experience a major nonrecoverable fault if it uses an RSLogix 5000 project that requires most of the controller’s available memory and power is cycled to the controller.
• When using a 1747-AENTR SLC™ 500 EtherNet/IP Adapter and more than five modules in a remote SLC chassis connected to your CompactLogix 5370 controller, the second download of a project to your controller causes the controller to lose communication with the remote SLC chassis.
• Changes made to the Buffer Timeout value for FactoryTalk Alarms and Events subscribers do not take effect until the existing buffer is deleted.

Open Issues:

• Under some rare occurrences, if a Motion Axis Move (MAM) instruction with Merge Enabled is activated during the deceleration segment of an active MAM instruction, then the new MAM instruction may overshoot its programmed endpoint.
• If a Motion Group Shutdown Reset (MGSR) instruction is executed while a Motion Group Shutdown (MGSD) is still executing, motion error #7, that is Shutdown State Error, results.
• With any coordinated move in a system that uses two or more Integrated Motion on the EtherNet/IP network axes, if one axis is disabled using a Motion Servo Off (MSF) instruction, any remaining Integrated Motion on the EtherNet/IP network axes will generate an Excessive Velocity Error, that is, Drive Error S55.
• Every time there is a Motion Servo Off (MSF) instruction/Motion Servo On (MSO) instruction cycle, the Position Trim value is added to the axis position. This change in axis position causes the axis to move unexpectedly by a distance equal to the Position Trim value.
• When you create a new Integrated Motion on the EtherNet/IP network axis, the default value for Mechanical Brake Delay = 0. If you are using a motor with a brake on this axis and do not change the Mechanical Brake Delay value, the motor will not work properly when you attempt to execute motion.