We are pleased to announce the release of Productivity Suite software, version 4.6.0.37

Improvements:

1. Added new File Operations instructions (Px-622, P1-412/P1-M412 only):

a. Retentive Tag Sync (RTS)

b. File Control (FCX)

c. File Read (FRX)

d. File Write (FWX)

Note: If using File operations with a P1-412/P1-M412 CPU recommend upgrading firmware to 1.0.1.2 or P2-622 to 1.10.4.19.

2. Added the ability to auto-size columns in UDS Definition Editor.

3. Added a warning popup when closing data log window with unapplied changes.

4. Increased viewable field size for the Project Properties -> Project Description field.

5. Added total retentive tag count to the tag database window.

6. Data logger improvements: Added new file-creation options triggered by an event, after a specified number of lines, and after a specified number of bytes.

7. Email (EMAL) instruction: Added an option to attach a saved file created using file operations.

8. Added enhanced software and project security.

Bug Fixes:

1. UDS: UDS Export Window placing file path in the file name field.

2. ASP: Network Address strings are being returned with an appended SPACE character which affects the string length.

3. MQTT: P2-550 as MQTT client starts rapidly sending ping request after runtime transfer.

4. NETW, RX, WX: Inconsistent datatypes allowed for Non-Array option.

5. If array pointer is used in FOR instruction enable logic, it can cause E01005 in older CPUs.

6. Unable to tune a constant in an instruction when in monitor mode.

7. StrideLinx VPN CPU connection - unable to login when 2-factor SMS authentication is enabled.

8. Clicking on project compare generates "web server updated to port 443" pop-up each time.

9. Tag import generates error even if only the UDS comment field is changed.

10. P2-622 with multiple RS groups, heavy ethernet traffic, and with Watchdog Timeout value less than 500ms may result in Watchdog Timeout.

11. Fixed an issue where the OR Out instruction did not execute when placed in a Run When Called task.

12. Fixed an issue where converting a project to a P2-622 and after first transfer will cause Web Server open to fail.

13. P3-622: Fixed an issue where the CPU would not enter RUN when using an AMC that was not configured as hot-swappable.

14. Monitoring a ladder containing UDI instructions may incorrectly trigger a "Maximum capacity has been reached" error.

15. Opening a project created in an earlier version may incorrectly trigger a "Project file is either missing or invalid" error.

16. During discovery, the P1-RX was not detected correctly, resulting in an invalid configuration. 

17. UDI: Addressed issues that could occur when copying a UDI, including duplicate parameters and incomplete parameter copying.

18. UDI: Fixed an issue where an array of EMSG data type did not function correctly when an array element was used in an EMSG instruction.

19. UDI: Fixed an issue where parameter comments are not being retained. 

20. Px-622: Fixed an issue where the reported frequency and current (amps) values were incorrect when reading GS2 or GS3 drives.

21. Monitoring a task that contains UDI instructions may cause the GUI to become unresponsive (lock up).

22. PX-622: CPD instruction could produce unexpected results when Copy Binary was selected and a bit of a word was referenced in a Run When Called task.

23. UDI: EIP device compile errors could occur after copying a UDI and instantiating it in ladder logic.

Known Issues:

1. Due to enhanced project security changes, once a project is downloaded to the CPU with Productivity Suite v4.6 and retentive tags are assigned, transferring the same project with Productivity Suite v4.4 or earlier will erase all retentive tag values. 

To capture retentive tag values when reverting from v4.6 to v4.4 (or earlier):

A. In v4.6, Stop Mode transfer to CPU -> choose Copy Current Values and Continue, then save project.

B. In v4.6, export the Tag Database.

C. In v4.4 or older, open the original project and import the exported Tag Database.

D. In v4.4 or older, Stop Mode transfer to CPU -> select Yes when prompted about no retentive tags.

2. Px-622: Rapid disconnect/reconnect actions when using v4.6.x.x with a CPU running a v4.5.x.x project can result in a lost CPU connection. Connectivity can be restored by power cycling the CPU or removing and reinserting the Ethernet connection.

3. P1‑412: In projects created in version 4.5.x.x that include a P1‑02HSC, the software will generate invalid discrete input (DI) tags. If these tags are referenced in ladder logic, the CPU will crash. Recommended workaround is to delete the invalid tags (DI‑0.1.x.1–16) from the project.

4. Monitoring a project that contains UDI instructions may result in degraded or sluggish performance.

Go here to download the software