ADC_AutomationControls_PM01 (AutomationDirect) asked a question.

Edited November 29, 2023 at 3:35 PM
Productivity Suite 4.1.0.69 Release

We are pleased to announce the release of Productivity Suite 4.1, broadening the feature set for the P2-622 CPU and bringing new communications flexibility and coordinated motion to Productivity PLCs.

 

https://www.automationdirect.com/support/software-downloads?itemcode=Productivity%20Suite

 

For P2-622, the Remote ethernet port can be configured as a secondary ethernet port for improved networking flexibility. If configured in this way, the port cannot be used for normal Remote I/O (P2-RS, P1-RX, GS Drives, or PS-AMC).

 

Also for P2-622, the new Access System Parameters (ASP) instruction allows ethernet parameters to be modified from ladder.

 

MQTT support is improved by the addition of Secure MQTT (P2-622 only) and the ability to use tags for every field in the client configuration dialog.

 

EtherNet/IP receives the same flexibility upgrade, allowing tags for nearly every field in the client configuration dialog.

 

New Modbus capability arrives for P2-622, allowing greater serial and ethernet communication options (via new MBUS, NETW, and CSI instructions), such as changing target node IDs and IP addresses on the fly, dramatically reducing programming time required.

 

The new Multi-Axis Motion Sequencer (MMSEQ) instruction allows sequences of up to 64 steps, enabling smooth, coordinated motion between axes.

 

Version 4.1 also adds support for the new P1-08ND-TTL and P1-08TD-TTL modules.

 

Other changes include improvements to keyboard navigation, data view, and programming environment consistency.

 

A number of bug fixes also improve the overall user experience.

 

For more details, please see the release notes available at the above download link.

  • 6 answers
  • 691 views
kewakl likes this.

  • kewakl (Customer)

    I don't know about everyone else, but I like improvements 1-4.

    The allow tag as parameter in comms device configurations is a very welcome addition!👍

     

    Thank you.

     

     

  • z28z34man (Customer)

    Is there any chance that the P3 series receives any of this love in the future? I am assuming that hardware advances in the P2-622 enabled it and for the P3 series it would require a new processor.

     

    It seams like the P2 series is getting all the new stuff like being able to use P1-RX for remote IO and the P3 series is falling behind.

    • ADC_AutomationControls_PE03 (AutomationDirect)

      Unfortunately, we cannot comment on any potential future development regarding your question about P3000 series receiving new features like the P2000 series. Productivity1000 and 3000 did receive some new communications features in version 4.1, like on-the-fly adjustable parameters for EtherNet/IP and MQTT, as well as the latest motion functionality. However, you are correct in your assumption that a new processor would be required for the P1000 and P3000 to benefit from all the new features in version 4.1.

      Expand Post

  • HikeOnPast (Customer)

    On upgrading ProSuite to 4.0.1.69, there is a notification that the 4.1.x series will update code developed in prior versions (expected), including file format (expected) and functionality (unexpected). The notification doesn't seem to provide a link for more information.

     

    I'm not finding any more detail around which types of functionality are likely to be impacted unless it's just the "Known Issues" section of the release notes. Is there more detail anywhere that talks about how the functionality of existing code might change with migration to the 4.1.x branch?

    Expand Post

  • ADC_AutomationControls_PE03 (AutomationDirect)

    The notes on the ProSuite software download page (https://www.automationdirect.com/support/software-downloads?itemcode=Productivity%20Suite) indicate the improvements and bug fixes in version 4.1.0.69. All the items listed under improvements and bug fixes are areas of a difference in functionality from the previous version of software.

    The primary reason for the notification is that sometimes users have developed work arounds in their code to deal with a bug in the software which, when the bug is fixed, sometimes breaks the user's work around.

    Expand Post

 

Did this information resolve your issue?