Release Notes AB 2.8.0
Release Notes AB 2.8.0
0 2024-12-12
Automation Builder
General performance improvements and bug fixes
Cyber security report can be generated for AC500 V3 CPUs
Improved ABB Drive integration, when using Ethernet/IP
Auto-execution of Python scripts
Availability of more OPC UA tags (licensed feature)
Programmable Drives
Support of ABB programmable drives within Automation Builder. The functionality corresponds to the latest Drive Application
Builder 1.3.1 release.
General information
The installation of the ABB Automation Builder software requires administrator rights.
Prior to installation, the Automation Builder, Control Builder Plus, CODESYS software and the CODESYS Gateway Server
must be shut down.
Automation Builder 2.8 installs side-by-side with already installed Automation Builder/Control Builder Plus versions. Projects
created with previous versions can be upgraded to the latest version easily. If upgrading is not desired, projects can be opened
with the matching Automation Builder version.
Automation Builder 2.8 creates a new device repository. Devices which had been installed additionally in previous versions of
Automation Builder/Control Builder Plus can be migrated via menu “Tools” “Migrate third party devices”.
The English documentation contains the latest changes for Automation Builder 2.8. Latest documentation packages can be
found on the ABB website: www.abb.com/plc Download Documentation, and then select your language.
Automation Builder 2.8 includes CODESYS version 3.5 and 2.3. Side-by-side installations of other CODESYS version 2.3
based engineering tools like AC1131 may cause issues or disturb the use of one or both tools. If side-by-side installation
cannot be avoided, please install all other tools BEFORE installing Automation Builder.
Automation Builder 2.8 and embedded AC500 V3 firmware 3.8 are based on CODESYS version 3.5 service pack 20 patch 2.
Windows Server installations: CoDeSys V2.3 Gateway Service Wrapper or server restart required after installation. For
concurrent Gateway access a specific configuration is required, please refer to Automation Builder help for details
1
Welcome to ABB Automation Builder 2.8.0 - System Requirements 2024-12-12
When installing CP600 control panel option the Panel Builder installer may ask for replacing the last installed version of Panel
Builder. This question has to be answered with “no”. In case of accidently choosing “yes”, the installer has to be executed
again, although it has been finished successfully.
AC500 V2: After upgrading projects to latest Automation Builder, please check for having the matching firmware installed
before doing a download from CoDeSys.
Availability of online activation of licenses might be affected by local IT security settings. In case the online activation of
licenses is failing please use the offline activation.
Latest cyber security information is always available on the ABB cyber security alerts and notifications website. We strongly
recommend to subscribe to e-mail notifications!
System Requirements
8 GB RAM
5-18 GB free available hard disk space depending on the selected feature set
Supported operating systems:
– Windows 11 (32/64 Bit) Professional / Enterprise
– Windows 10 (32/64 Bit) Professional / Enterprise
– Windows Server 2019 and 2022
(all devices have to be directly accessible by the server; requires enabled .Net Framework 3.5)
2
Welcome to ABB Automation Builder 2.8.0 - Table of contents 2024-12-12
Table of contents
3
Changes in Automation Builder 2.8.0 - Automation Builder 2024-12-12
Automation Builder
Functional changes / New features Version
Cyber security report can be generated for AC500 V3 CPUs AB 2.8.0
Improved ABB Drive integration, when using Ethernet/IP AB 2.8.0
Auto-execution of Python scripts AB 2.8.0
Improved visibility of PLC and CPU load AB 2.8.0
Availability of more OPC UA tags (licensed feature) AB 2.8.0
Availability of frequently used example libraries by default: ASCII, Http, PCO, Tcp, Websocket AB 2.8.0
Workaround: Set "Always update variables" to “Disabled” or contact our technical support for further workarounds.
Multi download tool: PLCs might reset their IP address after using the multi download tool. FW 3.8.0
Workaround: When planning to update larger installations, please contact our support to discuss potential
workarounds.
Known problems ID
Cyber security report: The section about use of ethernet ports does not yet cover onboard EtherCAT and onboard AB-25837
Profinet configurations.
Drive integration on Ethernet/IP for AC500 V3: Warnings are shown that variables are already used in another task AB-25823
and may be overwritten. These warnings are missleading and can be ignored. Root cause is that for some channels
variables are auto-declared both on byte level and on bit level.
I/O mapping list: Online values of I/O mappings might sometimes not be properly updated AB-25772
Workaround: Either close and reopen the corresponding I/O mapping list editor or use the “I/O Mapping” view of the
same device
Project archives containing device descriptions with specific characters like > or = cannot be opened. An error AB-25720
message "Illegal characters in path" is shown.
Workaround: Exclude the related device descriptions from project archives and install them manually via Tools
Device Repository
Licensing: Number of standard or premium licenses that are purchased 2018 and earlier that can be activated in one n.a.
license container is limited to 4
Workaround: use license dongle if more licenses are required or contact Automation Builder support to update the
licenses
Installation issue on Windows 10: AB-15979
During installation there might be issues with automatically deleted files by Windows in temporary folders which are
required for installation. This automatic temporary file deletion is introduced with Windows 10 feature update (build
17720 and later).
Workaround: if you run into installation issues on Windows 10, please try to disable "Storage Sense":
Windows Open Settings Click on System Click on Storage Turn off the Storage sense toggle switch
Automation Builder installation: n.a.
In case a PC reboot is required/executed during Automation Builder installation the setup might have to be restarted
manually after PC restart.
Workaround: Please start the setup after restart and select the desired options to install. The setup will then continue
the installation where it has been interrupted for reboot
Projects created in Control Builder Plus software versions cannot be upgraded automatically to Automation Builder n.a.
version 2.1.X.
Workaround:
open project with profile "Automation Builder 1.2", perform upgrade, save project
open project with latest profile "Automation Builder 2.0", perform upgrade, use project
4
Changes in Automation Builder 2.8.0 - Automation Builder 2024-12-12
ABB I/O mapping list view for disconnected modules on PROFINET IO devices with Shared Device functionality like AB 2.0.3
AC500 CM589-PNIO-4 (-XC) or 3rd party PROFINET IO devices (drives, I/O modules, encoders, etc.) is temporarily
not supported. As a result, no I/O mapping information is shown for disconnected modules on CM589-PNIO-4 (-XC)
or 3rd party PROFINET IO devices with Shared Device functionality in Automation Builder.
Workaround: Use standard I/O Mapping for disconnected modules on CM589-PNIO-4 (-XC) or 3rd party PROFINET
IO devices with Shared Device functionality
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
5
Changes in Automation Builder 2.8.0 - PLC - AC500 V2 Processor Modules (PM5xy) 2024-12-12
Known problems ID
Safety: SM560-S communication error during login and download: The usage of large arrays with initial values safety CPUFW-8723
application leads to a communication error with automatic logout
Profinet: Only first F-Device error number (per Slot) is sent via PROFINET (CM589-PNIO) CPUFW-8235
IEC60870-5-104: In configurations with a high number of tags and in combination with the general interrogation CPUFW-8955
command, the substation communication might not start. In this case the PLC responds with a negative confirmation
of the general interrogation and the process image is also not sent.
Workaround: Reduce the initial load to the PLC, e.g. by starting one substation after the other in case of multiple
substations.
Profinet: After download of an IEC project containing the POU PNIO_DEV_ALARM sometimes the POU reports the CPUFW-8940
error 0x1005 (4101) which means that the specific driver is not yet ready. The PROFINET communication keeps on
running, but the POU permanently reports this error.
Workaround: Create a boot project and reboot after the download in case this error appears.
System: SystemTime and TimeDate in CurTimeEx show different values when executed simultaneously. CPUFW-8591
Workaround: Select only one single way of getting the time and only use that in the whole application.
Bit wise access of LWORDs is subject to different byte order than other data types. CPUFW-8464
Workaround: The workaround steps are described in detail in the following application note:
http://search.abb.com/library/Download.aspx?DocumentID=3ADR010388&LanguageCode=en&DocumentPartId=&A
ction=Launch
C-Code for AC500 V2: Replacing the C-Code Library is not working when CoDeSys 2.3 is running. AB-22526
Workaround: Use RETAIN, PERSISTENT and/or RETAIN PERSISTENT data only with plugged battery.
Online access: Additional Visu Files at PLC without Onboard Ethernet leads to error during download CPUFW-6929
Workaround: Don't use Additional Visu files in PLCs without Onboard Ethernet
C-Code: PLC crashes on download program running C-Code-lib build with newer revision of FWAPI, e.g. BACnet CPUFW-6916
library created with AB 2.2.0 (FWAPI 2.8.x) used with PLC firmware V2.7.2.
Workaround: Update PLC firmware to same version as FWAPI in C-code lib, e.g. PLC firmware V2.8.1
Online access: Connecting a CP600 Panel via CODESYS protocol serial avoid creating a boot project CPUFW-6885
6
Changes in Automation Builder 2.8.0 - PLC - AC500 V2 Processor Modules (PM5xy) 2024-12-12
Working on CoDeSys 2.3 projects with administrator and non-administrator users might lead to inconsistent data n.a.
Workaround: avoid working in this setup with administrator and non-administrator users
Activating the CANopen sync mode requires to activate the "generic configuration view" (see "Tools->Options- AB-9768
>Device editor")
CM574-RS: If the parameter "Enable debug" is set to "Off" and when the PLC stops the CM574-RS continues to run
causing an E2 failure.
CPUFW-5538
Workaround: Set the parameter "Enable debug" to "On".
When PM5xx-ETH with 4 x CM597-ETH connected on the switch, the IP-Configuration tool shows a wrong
"Configured IP Address" for PM5xx-ETH. When unplugging the cable from all CM597-ETH, the "Configured IP
address" shows the right value." CPUFW-5537
Workaround: Unplug the CM597-ETH from the switch to check the IP address from PM5xx-ETH.
System: DC541: Error message after firmware update also in case of correct update
CPUFW-4659
Workaround: Check FW version of DC541 after update
System: DWORD_TO_LREAL and UDINT_TO_LREAL: DWORD/UDINT value cannot be proper converted to
LREAL if DWORD/UDINT >16#80000000. For PM595-4ETH CODESYS compiler generates warning.
7
Changes in Automation Builder 2.8.0 - PLC - AC500 V2 Processor Modules (PM5xy) 2024-12-12
8
Changes in Automation Builder 2.8.0 - PLC - AC500 V3 Processor Modules (PM5xyz) 2024-12-12
Important Notes:
- For AC500 V3 CPUs, the handling of diagnosis is different from the AC500 V2 CPUs.
- Please check the library placeholder resolution in case libraries are not found after project update. Set the placeholders
back to default or select a matching available library version, e.g. via Project -> Project Environment.
9
Changes in Automation Builder 2.8.0 - PLC - AC500 V3 Processor Modules (PM5xyz) 2024-12-12
PROFINET: Online Change is not working when using iParServer (results in error). FW 3.8.0
Workaround: Crosscheck that a configured option board is plugged into the PLC.
System: The FB PmSramExport will not throw an error when no memory card is plugged or the folder passed as FW 3.8.0
parameter does not exist on the memory card
Workaround: Ensure that a memory card with the required folder structure is plugged.
System: Using "init()" as function name will cause errors FW 3.8.0
Ethernet: The PLC message log may conatain spurious error messages for ETH2 when the CM5640-2ETH is in FW 3.8.0
switch mode (and hence has only one active/visible ethernet port)
Known problems ID
Ethernet: When trying to configure the DNS server from the corresponding Automation Builder editor, the setting will CPUFW-10802
not be taken over by the PLC by clicking on "Send". Programmatically setting DNS (e.g. via POUs) is not affected
and works as expected.
Workaround: Click on "Send" at least twice, and confirm that the configuration has been applied.
The CAA Net Base Services 3.5.20.0 (CAA Technical Workgroup) libraries are replaced by Net Base Services AB-25716
4.0.0.0 (CoDeSys) libraries. Currently both versions of libraries are supported.
Recommendation: Make sure that you use only one of them as both have the same namespace and switch to the
Net Base Services, 4.0.0.0 (CoDeSys) library if possible
Projects with special characters like # might cause errors during download
AB-24976
Workaround: Remove special characters from the project name
In some cases (e.g. after a target change) you receive an error message ‘Device cannot be plugged into this slot’
when plugging an AC500 V3 eCo option board.
AB-24821
Workaround: First do a project update and then plug the deivce.
CM5610-2RS: CM5610-2RS may disturb communication of other devices on the RS485 network during startup.
CPUFW-10293
Workaround: Suspend all communication on RS485 bus during start-up of CM5610-2RS.
System: When upgrading the PLC Firmware from version 3.4.x or earlier with active user management, to version
3.6.x or later, the Administrator account will no longer be able to log in.
CPUFW-10151
Workaround: Do not upgrade from these version when having user management active (deactivate it upfront if you
need to upgrade). If you already did, please contact ABB how to factory reset your PLC in that case.
Ethernet: The FB EthOwnIPInfo will display DHCP setting as "false", even if DHCP is used. CPU_FWLIB-920
CPU_FWLIB-774
CAN: On CM598-CN, CANopen modular devices with a sizes not being multiples of 8 bits are not supported CPUFW-10286
AB-24236
AC500-eCo: Counting of lost interrupts on onboard I/Os does not work CPUFW-10241
CPU_FWLIB-687
"MQTT" library: Characters of MQTT payload may be corrupted in messages exceeding 2048 bytes.
CPUFW-10176
Workaround: Switch to "MQTT Client SL" library
"MQTT" library: Unable to receive MQTT messages after one single message having a size larger than 2148 bytes.
CPU_FWLIB-770
Workaround: Switch to "MQTT Client SL" library
PmLib: Calling AC500_PM.PmVersion() multiple times from a task with high frequency may raise exception CPU_FWLIB-821
CAN onboard: The function block CL2.DriverOpenH may crash the PLC
CPU_FWLIB-872
Workaround: Add either “CANopen manager” or “J1939 Manager” below the CAN onboard object in the Automation
Builder device tree.
Visualization: When being online with Automation Builder, each open page of the visualization in Automation Builder
reduces the number of available connections by one.
CPUFW-9815
Workaround: Consider number of open visualization pages in Automation Builder, if it is mandatory that external
clients can access the web visualization at the same time.
Visualization: When being online with Automation Builder, each open page of the visualization in Automation Builder
reduces the number of available connections by one.
CPUFW-9815
Workaround: Consider number of open visualization pages in Automation Builder, if it is mandatory that external
clients can access the web visualization at the same time.
10
Changes in Automation Builder 2.8.0 - PLC - AC500 V3 Processor Modules (PM5xyz) 2024-12-12
Profinet: In case all Profinet I/O devices are disconnected from the PLC, automatic re-connection of the devices
might not work.
CPUFW-9804
Workaround: Monitor the bus state (via FB CM579PnioGetCntrlState) and re-start the communication in case of this
issue (via FB CM579PnioStartCom)
Security: When upgrading the PLC Firmware from version 3.4.x or earlier to version 3.5.x or later, the ethernet ports
may be in switch mode for a brief period during the update, even when configured as separate ethernet ports.
CPUFW-9793
Workaround: Block ethernet traffic by external measures if this is required for security reasons
AC500-eCo Option Boards: If a TA5142-RS485 is configured in the application, the PLC will also accept if a TA5142-
RS485I is plugged into the respective option module slot. No configuration error will be issued.
CPUFW-8605
Workaround: Manually ensure that the correct variant is used
Pmlib: Tasks that are created by AsyncAdd() are not deleted when the related function block instance is deleted
during online change
CPU_FWLIB-565
Workaround: When using AsyncAdd() make sure that online change is only used, when the related calls are not
removed.
JSON: The character "°" cannot be added to a string. This results in the error JSON_ERR_MEM_ERR. The parsing
of strings containing this character is possible.
CPU_FWLIB-626
Workaround: Set the project-wide compile option "UTF8 encoding for STRING"
CM579-PNIO (-XC) firmware version 3.0.1.21 has a network load issue. Additional network traffic (except own
PROFINET traffic) should be avoided, as this may lead to a loss of the connection between PROFINET IO controller CMNETX-282
and device.
FW update: CM5xx: The firmware update of communication modules via SD card does not work in one step in case
of PLC update firmware version 3.2.1 or earlier.
CPUFW-8814
Workaround: Update the communication module firmware in two steps by using the same SD card:
step 1: update of the PLC update firmware
step 2: update of the communication module firmware
CAN onboard: Calling the POU CL2.DriverOpenH (library CAA CanL2) to open the CAN interface is blocking the task
and takes more than 100 ms to complete.
Workaround: Option 1: Move the call of POU CL2.DriverOpenH to an event task, triggered once in main CAN task. CPUFW-8769
Start CAN communication, when the event task is done.
Option 2: Adapt the watchdog settings (time and sensitivity) accordingly. The I/O bus task must have a higher priority
than the CAN task.
Diagnosis: After an application download the information about a missing battery (if applicable) is not listed in
diagnosis history view. After a reboot missing battery information is available from the diagnosis history again.
CPUFW-8830
Workaround: Either check active diagnosis entries or do a reboot, which will add that diagnosis information to the
diagnosis history.
CAA_File: After closing a file and switching of the PLC by disconnecting from the power supply, the data of the file
might be lost.
CPU_FWLIB-588
Workaround: Always call File.Flush before closing a file.
IP scan: AC500 V3 PLCs running on full CPU load might not respond in time to IP configuration scan requests.
AB-22603
Workaround: Set PLC in stop before executing the scan.
GSDML: Projects with GSDML devices might not be properly upgraded to Automation Builder 2.6 if the GSDML files
are not installed before the upgrade. This issue doesn’t occur in case of upgrading via project archive.
AB-22669
Workaround: Install the missing GSDMLs, execute a “Project update” and then a "Build"
Library placeholder:
Starting with Automation Builder 2.6.0, placeholder redirections that are set inside the pool library manager of a AB-21659
library, will be ignored when the library gets included into an application.
OPC UA server does currently not support the following data types:
LTIME_OF_DAY
AB-20397
LDATE
LDATE_AND_TIME
FW update status on communication modules: The current update status might not be properly shown after the FW
update.
AB-22593
Workaround: Please update the status with reloading the 'Version Information' view by de-selecting and selecting it
again.
FW update including the UpdateFW:
FW updates including the UpdateFW require two times the update process (1st UpdateFW and 2nd SystemFW). FW
updates via SD cards handle these two updates automatically. AB-22126
11
Changes in Automation Builder 2.8.0 - PLC - AC500 V3 Processor Modules (PM5xyz) 2024-12-12
Profinet: The "Compare and commit changes" feature based on a Profinet scan result is only working without errors
or warnings in the following cases:
No slave is configured below the Profinet Controller in the device tree
AB-20790
Only slaves are configured below the Profinet Controller which are not found during the scan
Restriction: all found slaves need to be accepted, to ensure that all required data can be correctly added to the
project
Profinet: In the Profinet Controller 'Diagnostics live list' editor the parameter flag “Assign configuration temporarily”
has no effect on writing a device name into a Profinet device. The device name is always stored permanently.
AB-20609
Workaround: use the IP configuration tool standalone (available via additional tools in Automation Builder setup) if
this is required
User Management: Users might be prompted to login twice after creating the user management on a computer
AB-20703
where Automation Builder was never used before.
Input assistant: The programming input assistant might show not matching initialization values for ERROR_ID
ENUMs
CPUFW-8983
Workaround: Define the initialization of ERROR_ID values directly in the program and not via input assistant
Input assistant: In case the automatically added Ethernet library is removed from the project’s library manager the
use of the programming input assistant might lead to a crash of the Automation Builder.
AB-20877
Workaround: Add the removed Ethernet library again to the project’s library manager
PROFINET: CM579-PNIO: The node state of Profinet I/O devices might be false negative in case of consecutive
errors.
CPUFW-8456
Workaround: Check number of nodes with error state on I/O controller level
Firmware update: Unable to update the system or display firmware, if update firmware (UpdateFW) versions 3.1.2.32
or 3.1.4.82 are installed.
CPUFW-8252
Workaround: First update the update firmware (minimum version: 3.3.2.113) before updating the system or display
firmware in a second step.
EtherCAT: The first breakpoint in the EtherCAT sync task is not processed properly. It is always being ignored if
there is at least a second breakpoint.
CPUFW-8227
Workaround: Always use at least two breakpoints in the EtherCAT sync task considering that the first one will be
ignored.
EtherCAT: POU EcatSync outputs ErrInCnt and ErrOutCnt never start at 0
CPUFW-7983
Workaround: Do not use the first output values of EcatSync function block after setting EtherCAT to operation.
BACnet: If server objects of type "BACNet.BacnetSchedule" or "BACNet.BACnetSchedule" are instantiated in the
PLC application, the PLC will crash when the project is deleted from the device.
CPUFW-7854
Workaround: Only use the BACnet Schedule by adding it below the BACnet Server in the device tree instead of
adding it from the PLC application.
Diagnosis: The PLC node might show a diagnosis indicator "!" in the Automation Builder device tree even if no
diagnosis exists. In this case the root cause is that the device diagnosis is disabled.
CPUFW-7519
Workaround: Activate the device diagnosis in Automation Builder
Ethernet/IP Adapter cannot handle more than one connected scanner (Exclusive Owner). When connecting a 2nd
(Listen Only) Ethernet/IP scanner a connection failure occurs
AB-19326
Workaround: not available
Diagnosis text lists are not updated after new GSDML installation/device object update if the text list was already
present in the project.
AB-16737
Workaround: Delete the diagnosis text lists, save project, restart Automation Builder, and rebuild the project. The
updated text lists are now generated into the project
Diagnosis text lists are not transferred to the AC500 V3 PLC if download/login is done without rebuild.
AB-18007
Workaround: Please check that a visualization is added to the project, the setting 'enable diagnosis for devices is set
and project is rebuilt (clean all rebuild)
Online values of program code are not correctly refreshed in editor if exception handling is included in code AB-18215
Cyclic non-safe data exchange: An initialization of arrays and structures in the non-safe program is not supported by
AB-17989
the safety program in CoDeSys v2.3 and creates corresponding errors "Erroneous initial value".
Compile error will occur after renaming "CAN bus" on AC500 V3 PLCs
AB-17541
Workaround: Please keep default name
Sync-SDOs parameters are not generated when 'Enable Sync Producing' is disabled:
For both communication modules CM578-CAN and CM598-CAN, when the parameter CANopen Master parameter
'Enable Sync Producing' is disable, parameter 'set communication cycle period' and 'Set synchronous windows AB-14071
length' are not generated. When CANopen Master parameter 'window Length' is set to 0, the parameter 'Set
synchronous windows length' is also not generated.
12
Changes in Automation Builder 2.8.0 - PLC - AC500 V3 Processor Modules (PM5xyz) 2024-12-12
Fast counter of DA501/502 does not work if used at a Communication Interface (CI) module on PROFINET,
AB-16614
EtherCAT or CAN
IO mapping: use only mappings available in the IO mapping editor, avoid manual variable declarations using AT %
AB-16521
operations
FW 3.2.0:
Downgrade of AC500 PLCs from firmware 3.2.x version to previous versions via Automation Builder 2.1.X is not
supported.
n.a.
Workaround: Please prepare SD-card with desired firmware versions and execute firmware version update via SD-
card
Sometimes the display firmware is not updated within the first “Update Firmware” process (display shows “bAdFIr”).
AB-17204
Please start the “Update Firmware” process a second time.
The "Scan for devices" functionality does not work when the "Log" Editor of the V3 PLC is opened, After the call of
"Scan for devices" it is also no longer possible to add any object in the device tree (as long as the "Log" Editor is
active). AB-15749
Workaround: select another editor tab and call "Scan for devices" again
Division by zero for REAL and LREAL variables does not raise exceptions in IEC user program.
CPUFW-7429
Workaround: Check results of division in IEC program for "FIN".
Counter: Fast counter word order is wrong for devices on PROFINET and EtherCAT. CPU_FWLIB-279
Note: CM589-PNIO with CODESYS driver not supported with FW 3.2.4 or later
CM579-ETHCAT: In some configurations, the state of the last EtherCAT slave is shown as red circle in AB device CPUFW-6134
tree, even if slave works fine.
13
Changes in Automation Builder 2.8.0 - KNX 2024-12-12
CAA-File: "The files to be accessed from IEC (user) applications go to directories that are not visible for the user (e.g.
/mytemp). The PLC takes the filename specified by the user and appends it to this IecFilePath, and this complete
name has a length <= 255. AB-13406
So, the maximum length of a file name for the CAAFile user is 255 minus the length of the Iec Path." LIB-1176
CPU_FWLIB-9
Workaround: Consider the Iec Path in the IecFilePath.
Modbus TCP: Function code 23 for ETHx_MOD_TCP has different max data length (write 121, read 125) then V2
(write 125, read 125). The values in V3 are according to Modbus specification. LIB-1167
CPU_FWLIB-125
Workaround: Use NOT_EXIST for both use cases
CAA-File: POU FileOpen doesn’t distinguish if the SD card is write-protected or if there is no SD card inserted (in
both cases the error message is NOT_EXIST). LIB-1140
CPU_FWLIB-19
Workaround: Use NOT_EXIST for both use cases
OPC UA server: Property MaxMonitordItemsPerCall has been reduced to 100. If this property is read by OPC UA
clients, it returns no value (null) n.a.
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
KNX
Note: Before using the functional safety configuration and programming tools contained in Automation Builder, you must have read
and understood the AC500-S Safety PLC User Manual (download link). Only qualified personnel are allowed to work with AC500-S
safety PLCs.
Compiling and executing functional safety projects on AC500-S Safety CPUs require the purchase of a license.
SafetyBlocks_PLCopen_AC500_V22.lib V1.0.0 library is further used in Automation Builder projects created with AB
profiles < 2.7.
SafetyBlocks_PLCopen_LV101_AC500_V22.lib is available in the library folder of Automation Builder 2.7 for a possible
update in the project:
- Improvement of function block SF_MutingPar is included.
PLCopen Safety library SafetyBlocks_PLCopenExt_LV200_AC500_V22.lib is available from ABB web site with new
PLCopen FBs only: SF_GuardLocking_2, SF_ResetButton, SF_PSE, SF_EnableSwitch_2, SF_GuardLockingSerial
and SF_Override
Integration of AC500-S SCA (Safety Code Analysis) tool in Automation Builder 2.6.0
New PROFIsafe V2.6 protocol with short and long frames (up to 123 bytes) was added as part of AC500-S safety 2.5.0
CPUs (both F-Host and F-Device, respectively). New PROFIsafe F-Host
SafetyBase_PROFIsafe_LV210_AC500_V22.lib was added.
New features are added in the PROFIsafe, e.g. support of FLOAT32, INT32, UINT32 data types in both PROFIsafe
V2.4 and PROFIsafe V.6.
14
Changes in Automation Builder 2.8.0 - Safety PLC - AC500-S 2024-12-12
Specific functions for user-defined CRC calculation up to SIL3 and PL e were added. Refer to new function blocks in
the new safety library version: SafetyExt2_LV110_AC500_V27.lib.
New PLC browser command „flashstatus“ was added for safety CPUs. It shows the flash programming progress in the
safety CPU when downloading boot code, firmware or a bootproject.
A separate letter of confirmation is available for AC500-S safety engineering as part of Automation Builder. The version 2.3.0
of AC500-S safety engineering and its components can be seen using “About…” option from “Help” menu in
Automation Builder.
SM560-S (-XC) safety CPUs are supported by AC500 V3 CPUs. SM560-S-FD-1 (-XC) and SM560-S-FD-4 (-XC) are
not supported by AC500 V3 CPUs yet.
New cyclic non-safe data exchange editor and related functionality is introduced for SM560-S (-XC) safety CPUs with
AC500 V3 CPU.
Safety Verification Tool (SVT) is added to Automation Builder to verify safety project configuration integrity when safety
CPUs are used with V2 or V3 CPUs.
BYTE data type is used instead of WORD for all variables of DI581-S safety I/O module when used with V3 CPUs.
If data types like Unsigned16, Unsigned32, Integer16, Integer32 or Float32, which require more than one byte, are
used in PROFIsafe data, note the following. The byte order in such data types depends on the used PROFIsafe device
endianness and selected AC500 CPU type. V2 CPU supports big-endian and V3 CPU supports little-endian. Make
sure that the symbolic variables are mapped properly, and the delivered safety data is correctly represented in your
safety application.
Contact ABB technical support when the Automation Builder project shall be migrated from V2 CPU with AC500-S to
V3 CPU with AC500-S.
If non-safety V3 CPU is stopped, the safety CPU will go to DEBUG STOP (non-safety) state and safety I/O modules
will immediately switch to RUN (module passivation with a command) state. Later, if the safety CPU changes to
DEBUG RUN (non-safety) state, e.g., after switching non-safety CPU back to RUN state, the safety I/O modules will
immediately change to RUN (ok) state and deliver valid process values to the safety CPU without the need for
reintegration.
Error acknowledgement on safety CPUs is not directly synchronized with error acknowledgement on V3 CPU. All error
acknowledgement for safety CPUs shall be done on V3 CPUs directly.
The active user login connection to the safety CPU can be interrupted if the new non-safety configuration is loaded to
the V3 CPU in parallel.
Safety CPU firmware V2.1.0 is introduced as part of Automation Builder for SM560-S (-XC), SM560-S-FD-1 (-XC) and
SM560-S-FD-4 (-XC). Firmware V2.1.0 is compatible with previous safety CPU firmware versions V1.0.0, V2.0.0 and,
thus, previously obtained functional safety certifications for machines or processes remain valid, because the boot
project CRC (Cyclic Redundancy Check) does not change. As an example, SM560-S (-XC) modules with firmware
V2.1.0 can be used to replace SM560-S (-XC) modules with firmware V1.0.0 or V2.0.0.
Note:
Firmware V2.1.0 on SM560-S (-XC) safety CPUs can be downgraded to V1.0.0 or V2.0.0 only if the hardware index for
these safety CPUs is below C0, for example, hardware indices A3, B1, etc. In safety CPU modules with the hardware
index C0 and above, the new flash memory is used which is not compatible with safety CPU firmware versions V1.0.0
and V2.0.0. Only firmware V2.1.0 or above can be used on such safety CPUs. Usage of SF_RTS_INFO function in
SM560-S (-XC) boot project allows controlling which firmware version(s) will be accepted by the SM560-S application
program and which is not, if tighter control over firmware version is required from the customer application.
• Firmware V1.0.0 does not run on SM560-S-FD-1 (-XC) and SM560-S-FD-4 (-XC).
• Firmware V1.0.0 and V2.0.0 do not run on safety CPUs with hardware index C0 and above.
15
Changes in Automation Builder 2.8.0 - Modbus TCP – Communication Interface Modules (CI52x-MODTCP) 2024-12-12
Known problems ID
When using one or more variable mappings with type BOOL or STRING in 'Cyclic non safe data exchange' and a mix
of Safety and non-safety IO modules on the IO_Bus the address mapping might not be correctly calculated after adding
IO modules with the first ‘Build / Generate Code' execution. AB-22764
If UINT data type, which requires two bytes (e.g., as it is the case in ABB ACS880 drives with FSO-12 or FSO-21
safety modules, etc.), with individual displayed bits is used in PROFIsafe data in Automation Builder project, note the
following. The values for such PROFIsafe safety variables might be not correct. Thus, these variables shall not be used
in the non-safety V3 CPU program. The correct variable value is only available in the safety CPU project and AC500-S AB-19238
Programming Tool.
Workaround: Use individual bit variables in the safety CPU project and map them using “Cyclic non-safety data
exchange” functionality supported on the non-safety V3 CPU. These variables can be then used in the non-safety V3
CPU project, e.g., for diagnostic purposes, visualization on operator panels, etc.
If safety CPU is set to DEBUG STOP mode when used with V3 CPU, then the safety CPU will not follow state changes,
CPUFW-7743
like, “Run” and “Stop” of V3 CPU anymore.
„Initializations of arrays, structures and enumerations used for cyclic non-safe data exchange within the AC500 V3
variable declaration are currently not supported in AC500-S safety application and create corresponding compile errors
"Erroneous initial value".
AB-17989
Workaround: Please initialize the values of the concerned arrays, structures and enumerations within the non-safety
and safety PLC programs during runtime.”
AC500 V3: Safety output online values of safety IO modules used with an AC500 V3 are not visible in the tab "IO-
Mapping".
AB-20834
Workaround: Use the tab "IO-mapping list" instead.
Known problems ID
Diagnosis only works with CI52x-MODTCP firmware version 3.2.7 and higher. n.a.
Function block CiModCi52x (ABB_Ci52x_AC500 library) only handles Dynamic I/O Mapping, if fixed mapping is used, LIB-3568
module doesn't respond anymore. In the Automation Builder CI52x configuration, select I/O mapping structure as
"Dynamic Mapping" only.
Drive Manager
Remark: Drive Manager is not (yet) supported with Automation Builder 64bit. If required please use Automation Builder 32bit.
Known problems ID
No synchronization between Process data tab and Drive Manager’s FBA data in & data out parameter group with 32-bit AB-7586
parameters.
Workaround: While configuring offline data in FBA data in & data out in drive manager if 32-bit parameter is selected
then leave next parameter as empty
Drive manager loses connection to drive if, user is using Profinet / Profibus DPV1 read/write function blocks in PLC AB-8376
program to read/write parameters of the drive.
Drive Manager is not connecting over Y-link in Profibus connection 104203
Messages are not displaying after exporting the .dsp and .dcparambak file from Drive & Project in online/Offline mode 247760
German language support for ACS530, ACS560 and DCS880 drive parameters are missing.
16
Changes in Automation Builder 2.8.0 - Drive Application Programming 2024-12-12
Supported drives:
ACS880, Versions : AINFX 3.46, AINFX 3.40, AINVX 2.90, AISFX 3.21, APCFX 3.43.4.3, APCVX 2.82,
ATBFX 3.40, YINFB 1.03, YINFB 1.02, YISFB 1.02
DCS880, Version: DCSF1 3.00.3.0, DCSF1 3.0.0.0,
DCT880, Version: DCTF1 3.00.0.0, DCTF1 3.0.3.0
HES880, Version(s): SHVFX 2.57.0.0
ACS860, Version(s): GINKGO QGKFX 2.90
Known problems ID
Scanning of drives is not possible after uninstallation of Drive composer pro as required DriveDA OPC Server gets
uninstalled too.
APEM-Import from Excel is not working
Please refer to the Cyber Security Guideline - Secure Default Settings and Hardening (abb.com) for cyber security related topics on
programmable drives engineering.
Drive Composer
Drive composer pro is compatible with all new common architecture drives such as ACS880. The complete compatibility table is
available in Software Tools web page http://new.abb.com/drives/software-tools/
Drive composer pro version embedded into Automation Builder 2.8.0: V 2.9.0.1
Known problems ID
If a computer has a newer Drive Composer pro and Drive Application Builder installed, installing old version of Drive
Composer pro will fail. Workaround for this problem is to uninstall DriveDAOPCServer from control panel/Programs
and Features. Then install Drive Composer pro. However, there is a small probability that this might cause problem to
Drive Application Builder when communicating with drives
USB connection is occasionally not resumed when unplugging and plugging in USB cable from the drive.
Occasionally, Drive Composer pro does not close properly and will cause No Drive Found failure. The solution to this
problem is to kill Drive Composer and DriveDA processes manually from the Task Manager
Workaround: Please use the “Instantly” or “Delayed” trigger mode for starting a measurement.
SCADA - Zenon
Functional changes / New features Version
No functional changes
Limitation: Zenon AC500 V3 variable synchronization is currently not supported
17
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
Panel Builder 600 version embedded into Automation Builder 2.8.0: V 4.5.0.678
18
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
– Recipes
o Added warning message when restore recipe fails due to not supported chars
– Remote clients
o Added warning message when restore recipe fails due to not supported chars
– Security
o Certificate to sign projects
o Added FTPS secure communication
o Enhanced password hashing method in runtime and PB
o TLS support for PB mailing
o Added project signature functionality to allow only certified project to run
o Added HTTPS secure communication
o Added timeout after wrong password for user login
o Added CSRF (Cross-site request forgery) token as project property for web security
o Updated openSSL library
o Enforced default settings for user management/security
o Added project file encryption
o Add NTP port information in Ports and Firewalls chapter
– Simulator
o Added tool in Simulator to watch and simulate project tags
o Added Online Simulator tool
– SQL
o Added database native connectors
o "Added table data source widget for easier connection with database
o query"
o Added PostgreSQL connector as native DB connector
o Added ODBC connector as native DB connector
o Add Unicode Support for DB Connectors
– Tags
o Possibility to display better view for indexed tags sets in case of long name tags
o Add "replace" button for "Invalid Tag Reference"
o Import/Export/Copy/Paste for Indexed Tag sets
o Tag editor improvement, add double click selection for properties
o Added Client system variable to support remote variable scenarios
o Enhanced scenarios of synchronization with external Tag symbol files: choose to keep datalinks
when Tags is removed externally
o Possibility to choose widget objects from Index Tag parameter in Indexed Tags
o Importer default selection should follow also the combo-box selection of protocols
o "Add tag name info in read block and read datagram error in protocol
o error message"
o Manage tag values with offline simulator
– Trends
o "Added Up and Down button in Trend Data log to reorder Tags to be
o sampled"
o Sampling Time datalink is available only if we have more than one tag to log
o Add Minimum interval Time to 100 ms in trend sample when it used a Trigger Tag
o Trend buffer import/export, clone and autofill
o Add "Attach to" option for FileName properties of DumpTrend
o Add Epoch and ISO8601 standard as available Data Format
– User Interface
o Automatic offsets for retentive variables
o Added System Settings button in Manage Target
o Change Project Type option on right click of Device node in project tree
o "Added possibility to choose project upload folder and quick click to open
o an uploaded project"
o Added Online help
– Widgets
o PB4Web: Table widget sorting support
o New scatter chart widget
o "Added 2D and 3D style to buttons to choose text behavior when button
o is pressed"
o Enhanced combo box widget style capabilities
o Added continuous index option in combo box widget
o Enhanced Web browser widget capabilities
o Add MJPEG Camera URL between the basic properties of IP Camera Widget
o Added Dashboard pages
o Added Tag bar widget
o Added Stack widget to manage layers
o Added new icons in widget gallery
o Added QR code widget
o Web Browser widget: Add save cookie and Accept-Language support
o Provided way to load legacy widget gallery
o Common alignments settings for all text/numeric widgets
19
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
– Alarms 4.5.0.632
o Alarm import file filter not effective when PB runs in French language (AB 2.6.0)
o Live Tag of Multi size array generate an invalid Tag reference
o Corrected behavior of alarms connected to array elements
– Audit Trail:
o Warning message appears at every Logout after Date&Time change
– Behavior
o Corrected behavior of HMI Client application in boot sequence
o Initial change password not working with Client
o Corrected performances issue when loading page with Tables
o Page with dot in them name could not been load
o Corrected behavior of HMI Client on login
o Deleted false error detected by project validator on recipe widget
o Error sending email with attachment in specific SMTP server
o Corrected behavior on property pane which closes after specific sequence
o Wrong page numbering on PB tabs on specific page sequence creation
o Corrected behavior of NFC variables in specific scenario
o Actions defined on hold key pressure are not executed
o Improved tag selection in specific sequence from Tag Editor
o In runtime, all web files are stored in main project folder and not inside web folder
o BACnet scheduler can't read weekly boolean tag and crash with PLCtrend
o Corrected behavior of specific project causing disconnection from HMI client
o Corrected behavior on specific project tun on Simulator
o Corrected PB behavior when cutting some tags in tag editor
o Aligned differences in rendering on the HMI device or in the web using a large amount of data
o Corrected PB behavior in project conversion if project is not saved as but renamed
o Corrected data entry behavior on scaled numeric field linked to recipe selected set
o Opening an external application while holding button causes button to remain pressed
o Corrected false positive error on loading images at project opening
o Corrected unexpected behavior of runtime using specific project
o JavaScript Editor increases the distance between two consecutive rows of code under specific
scenarios
o Corrected hierarchical importers behavior
o Corrected USB update behavior in specific conditions
o Corrected behavior when DBWrite Action are executed and Fast Boot is enabled
o Corrected runtime behavior on print action with specific project
o Fixed behavior while setting protocols with plc network and specific steps
o CODESYS 3.5 SP14 runtime not communicating with protocol on WCE
o Corrected behavior on second project download for specific hardware
o Fixed runtime behavior on loading a specific project
o Action “File > Save Project As” doesn’t show the path of the current opened project
o Corrected disk size value displayed in project wizard for some models
o Add/Remove modules from system variables and other changes
o Certain passwords block the FTP connection to the panel (990/FTPS and normal FTP) and the
project download
o Customer's PB project does not start Offline Simulator (crash simulation)
o HMI does not change page at power-up with Page Request value set
20
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
21
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
o PB4Web: Table's filter is not applied when the number of rows is higher than 500
o PB4Web: Error when we load Home Page after a setLanguage action
o Aligned DbResponse behavior from web and native
o PB4Web: specific project remains on loading and shows an error
o PB4Web: Indexed tags not working when used from dialog pages
o PB4Web: Web pages not loading on a specific project
o PB4Web: Load page is not executed when a non-modal Dialog is opened
o PB4Web: at first loading of Pages and Dialogs, they will refresh twice
o PB4Web: Delay of loading data on Table Page
o PB4Web: Javascript query separator cannot be distinguished from same char inside results
o PB4Web: Corrected Table Filter behavior with specific field value
o PB4Web: corrected behavior when closing dialog causing screen freeze
o PB4Web - Access to different panels web pages trough port forwarding causes alternate
disconnection
o Accessing web page of a project results in stuck visualization
o Grid layout vertical scroll is not working on web pages
o PB4Web: Momentary button stays pressed when web page is used from Mobile device
o Fixed initial password is broken in PB4Web
o Color palette doesn't work on the property background of web pages
o PB4Web: Button Fill color with formula not working in web browser
o PB4Web: fill color property of bargraph does not work on web site
o PB4Web: Integer Tag with HMI datatype float are not converted when they are writing
o PB4Web: Recipe widget shows empty after deleting last recipe in browser
– Protocol
o [MODS] Corrected serial data exchange in WCE targets
o [MODR] Adjusted behavior on node 0 inserting, to be applied only for UDP connections
o [BACN] max segments accepted error if device doesn't handle segments
o [OPCU] Error while importing from Wago PFC200 (message in the header too large)
o [ETIP] Write string data from recipe does not write String LEN value
o [OPCU] Data type imported as null
o [CDS3] Device loses connection with CODESYS Workbench under certain conditions
o [CAND] Import of DBC file does not take care of Mux info start in frame
o [S7ET] Communication failed with CP1542SP Slot 2
o [ABBE] Tag Import erroneously from PLC file with tab/space character in the Tag Name
o [BACN] Communication error with specific BACnet device
o [IR5L] IRC5 Linux protocol not starting in PB 4.5
o [MODR] Server does not answer in TCP mode with Node ID 0
o [ETIP] Communication error when reading multidimensional arrays of structures
o [ABBE] Tag Import erronealy from plc file with tab/space character in the Tag Name
o [MRTU] Reduce protocol communication gap - Case ID: 202200810
o [MODR] Tags defined in Modbus TCP Server has inappropriate ID in Tag URL
o [ETIP] Communication error when reading multidimensional arrays of structures
o [IR5L] IRC5 Linux protocol not starting in PB 4.5
o [MODR] Server does not answer in TCP mode with Node ID 0
o [MODR] HMI runtime crashes with modbus server if malformed packets are sent
o [BACN] Communication error with customer BACnet device
o [BACN] max segments accepted error if device doesn't handle segments
o [CDS3] Device loses connection with CODESYS Workbench under certain conditions
o [ETIP] Write string data from recipe does not write String LEN value
o [ETIP] Tags related with the servo drives are not imported-Int64 types added
o [IR5L] ABB IR5L boolean Tag not working anymore
o [MODR] Tags defined in Modbus TCP Server has inappropriate ID in Tag URL
o [MODR] Runtime crashes when sending request with random long strings(Introduce issue)
o [MODR] Node Override for Modbus TCP Server with possibility to disable node
o [MODS] Different behavior between UN30 and UN31
o [OPCU] Display App Uri Validation not correct
o [ETIP] Long Integer are imported as LINT of int64 but in the protocol configuration they are not
available
o [MIQE] Mitsubishi iQ/Q/L ETH protocol causes crashes on 4.5 when there's a communication
error
o [MIQE] When using PLC network with Mitsubishi IQ ETH, the system will read and write tags
only on the first of the list
o [MODT] String handling in optimization
o [MRTU] Communication issues Modbus RTU protocol
o [MRTU] Request to have better performance on communication with Modbus RTU protocol
o [OPCUA Server] Historical alarm generates events every time a new client (web or PB) will
connect
– Recipes
o Corrected behavior when recipe download is executed on string tags
o Corrected behavior when recipe download is executed on string with special chars
o Recipe Field displays wrong data on screen
o Writing more char in string recipe elements following elements is overwritten
22
Changes in Automation Builder 2.8.0 - Panel Builder 600 2024-12-12
o HMI executes more and redundant write data in plc when a Tag array is used in Recipe
o Restore Recipe for specific Set of specific Recipe will Restore all set of the recipe selected
– Scheduler
o Sunrise and Sunset wrong hour during summer time
– Security
o Login after Change Password in Login Page does keep the Permission of the User Logged
before
o User forced to change initial password after editing another user credentials
o Group home page changed when changing FTP/HTTP settings
o Corrected behavior when accessing to USB and SD via FTP on specific hardware
o Always ask for the encryption password when it is needed
o HMI runtime crashes with modbus server if malformed packets are sent
o CVE-2022-1292
– Simulator
o Simulator is not closing when PB closed
– SQL
o dbReadRecipes action returns Element not found on high size recipes
o Database query with Nchar and Nvarchar will not be returned properly
o Aligned DbResponse behavior from web and native
– Tags
o Scaled array with fixed point does not write value properly
o PB does not save Interfaces tag group selection
o Tag editor Scaling problems when entering scaling factors with decimal point
o Usage of double array resets connection (device offline)
– Trends
o [BACN] Corrected Simulator behavior using BACNetTrends
o Corrected PLC Trend behavior in showing curves
– Widget
o PB4Web: property Sorting for Alarm History Table does not work
o PB4Web: Group column in Alarm History widget is not shown
o Reviewed not working RSS feeds widgets
o TextTableFilter widget apply filter "0" when field is empty
o Trend table duration not working properly when we set 4 weeks / ALL
o Network configuration is not applied when the interface is with an AutoIP
o Improved Pinch event management on Scatter Chart widget
o Browser widget scrollbars does not work
o Corrected behavior when scrolling GridLayout causing performances issues
o Corrected PB behavior on continuous index flag of combobox widget
o ComboBox doesn't show communication error icon and show wrong element with index data
o Fixed behavior of IC Camera widget image polling
o Reviewed minor icon graphic in new widget gallery
o Corrected visualization issues on a custom alarm table
o Boolean BACnet scheduler does not work properly
o Table filter formula does not work at first time
o Web browser widget keyboard is not working with the runtime
o Chart Widget's gesture event shows curves frozen
o Combobox widget with empty data property
o Table widget with filter does not deactivate tags when filter changes
o Web Generation error when we just drag and drop the Tab widget
o Custom Style property is not exposed for "TabBarWgt" by default for style == Custom
o Datalink initialization issue first layer stack widget
o Wgt javascript variables does not work properly inside stack widget in custom widget
o Data read for new chart widget is not stopped when page is changed
o The Chart widget trigger a user.notice pblauncher: QFont::setPixelSize: Pixel size <= 0 (0)
o PB hangs while resize new gallery trend widgets
o PB crashes when User Gallery folder is changed
o Delay while open the PB in pc with new gallery
o Layer widgets are not visible if we insert more than 3 nested stack widget
o Text Editor widget save file without extension and does not recognize them in browse
o Alarm name missing in the alarm report widget
o Boolean bacnet scheduler widget does not show and write propely default value
o Crash of Runtime when we access to HTTPS page from Web Browser widget
o Delay when load the page with Table widget
o History trend widget not updating values after some time of plotting in browser
o Labels on Custom Widget replace special character with "?"
o Messages and label inside nested Custom Widget are completely lost in 4.5
o Setting tahoma font on widget it becomes MS Shell Dlg 2
o Text in Custom Widget Full is replaced when we unlock and lock again the widget
o The PB page is not positioned correctly, when we have an combo widget.
o The runtime crashes when unload project when 2 bacn alarm configured with same notification
class
23
- Servo Drives 2024-12-12
Known problems ID
Export files from Automation Builder have wrong format to be used in Panel Builder 600 protocols.
There is currently no workaround available for importing these files in Panel Builder.
When installing CP600 control panel option including previous version profiles, the Panel Builder installer asks for
replacing the last installed version of Panel Builder. This question has to be answered with “no”. In case of accidently PB600-632
choosing “yes”, the installer has to be executed again, although it has been finished successfully.
ABB Modbus RTU protocol with Model ABB AC31 Series 90 not working.
Missing error message: It is not possible to download a Runtime version lower than V4.5.0.x to a panel with BSP
V1.3.x
Project update: Selecting a new location for updated project will damage project when working with Automation
Builder integration. Workaround: Use option “convert and overwrite”
Servo Drives
Functional changes / New features Version
Integration of latest Mint Workbench version 5.8.74 5.8.74
24
Appendix - Appendix 1: CS31 Library Package 2.4.5 2024-12-12
Appendix
Appendix 1: CS31 Library Package 2.4.5
The software Libraries in HA Library Package are for V2 CPUs only and have been tested with the following versions:
Automation Builder versions AB1.1 to AB2.8.0
CPU and CM574: Firmware versions FW2.4.2 to FW 2.8.6
CI590-CS31-HA: Firmware T3.0.15
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
V1.0.0 HA_CS31_AC500_V13.lib
V2.0.0 HA_CS31_AC500_V20.lib
V2.3.0 HA_CS31_AC500_V23.lib (2013-12-11, library version V2.3.0) HA_CS31_CALLBACK_STOP updated from program to
function
V2.4.0 HA_CS31_AC500_V23.lib (2014-04-29, library version V2.4.0) Support of more than one CS31 bus by using CM574, Bug
fixes.
V2.4.1 HA_CS31_AC500_V23.lib (2014-10-24, library version V2.4.1) Adaptation for compatibility with new FW 2.4.0 (LIB-391,
LIB-394)
V2.4.2 HA_CS31_AC500_V23.lib (2015-03-27, library version V2.4.2) bugs fixes (LIB-347, LIB-419, LIB-347, LIB-418)
V2.4.3 HA_CS31_AC500_V23.lib (2015-03-27, library version V2.4.2) no changes in library, only online help CAA-Merger-9.chm
updated (2016-05-02)
V2.4.4 HA_CS31_AC500_V23.lib (2015-03-27, library version V2.4.2) no changes in library, only example and documentation
updated for CM597 (2018-06-08)
V2.4.5 HA_CS31_AC500_V23.lib (2015-03-27, library version V2.4.2) no changes in library, only example and documentation
upgraded to valid CP600 HMI (LIB-1970)
25
Appendix - Appendix 2: PS553 DRIVES 1.2.8 2024-12-12
AC500 libraries for control and communication to ABB ACS and DCS Drives using ABB Drives Profile.
The software Libraries of this package have been tested with the following versions:
Automation Builder versions AB1.1 to AB2.8.0
Firmware versions FW2.5 to FW 2.8.6
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
V1.2.8: (4.3.2020)
- Examples and documentation updated: set the EN input of Ctrl-block to constant TRUE (LIB-2271, LIB-2273)
V1.2.7: (20.06.2019)
Several improvements and bugfixes in the existing libraries
- ACSDrivesBase_AC500_V20.lib (V1.1.3)
- ACSDrivesComModRTU_AC500_V20.lib (V1.1.4)
- ACSDrivesComModTCP_AC500_V22.lib (V1.0.2)
- ACSDrivesComModTCP_Ext_AC500_V24.lib (V1.0.1)
- ACSDrivesComPB_AC500_V24.lib (V1.0.2)
- ACSDrivesComPN_AC500_V24.lib (V1.0.2)
- DCSDrives_AC500_V24.lib (V1.0.1)
JIRA tickets:
LIB-479: ACS_COM_MOD_RTU_ENHANCED - Output "ONLINE" is not reset after correction of wrong drive settings - PLC
must be reset
LIB-495: Skip Modbus RTU communication to drives that are not online and retry only after e.g. each 20sec
LIB-1128: Comment for DRIVE_DATA input is wrong (this is visible as tooltip)
LIB-1129: Visu ACS_COM_MOD_RTU_GEN_VISU_PH to be added four values
LIB-1269: ACS_DRIVES_CTRL_ENG_VISU_PH color of RESET input should be green instead of yellow if TRUE
LIB-1729: Code related to "DRIVE_DATA.ctrlBlockUsed" is not introduced in "ACS_COM_MOD_TCP" in line with other
communication blocks
LIB-1732: ACS_COM_MOD_TCPx_ENHANCED and interlock missing if not used with control block
LIB-1736: Difference in DCS & ACS drive control behavior: When CW = 0, DCS drive does not go to stop while ACS drive goes
to stop
LIB-1812: Improve the error description for the outputs SPEED_REF and TORQUE_REFLIB-1971: Docu for DRIVES-Lib V2 -
Hint for ACS380 not to use ACS3XX blocks
LIB-1972: add new DRIVE_TYPE for ACS380, ACS480, ACQ580
V1.2.6: (08.06.2018)
- Updated Examples for Modbus TCP with CM597)
V1.2.5: (29.05.2017)
- Updated Examples for Modbus RTU and TCP (workaround for AB-12166)
V1.2.4: (15.03.2017)
- Updated Example documentation: Quickstart Guide B 3ADR025232M0201.pdf (LIB-1247)
- Online help: Added chapter about "ACS / DCS Drives Communication via Modbus TCP EXT" library (AB-11069)
V1.2.3: (22.09.2016)
Added broadcast message functionality to ACS_COM_MOD_RTU_GEN Function block (V1.1.3).
- ACSDrivesComModRTU_AC500_V20
V1.2.2: (24.06.2016)
Improved generation time of DONE output for Profibus and Profinet DPV1 function blocks (V1.0.1)
- ACSDrivesComPB_AC500_V24
- ACSDrivesComPN_AC500_V24
V1.2.1: (17.03.2016)
Update of online help
V1.2.0: (27.10.2015)
Added following new libraries (V1.0.0)
- DCSDrives_AC500_V24.lib
- ACSDrivesComPB_AC500_V24
- ACSDrivesComPN_AC500_V24
- ACSDrivesComModTCP_Ext_AC500_V24
Several improvements in the existing libraries
- ACSDrivesBase_AC500_V20.lib (V1.1.2)
- ACSDrivesComModRTU_AC500_V20.lib (V1.1.2)
- ACSDrivesComModTCP_AC500_V22.lib (V1.0.1)
Update of online help and examples
26
Appendix - Appendix 2: PS553 DRIVES 1.2.8 2024-12-12
V1.1.7: (17.07.2013)
Corrections in PB / PNIO Example documentations - now version E
Added Presentation "PS553 Library Introduction and Exercises V34.pdf" and
ACS Drives - AC500 overview fieldbus connectivity.xls in folder "Examples\PS553-DRIVES"
V1.1.6: (17.05.2013)
Update of folder structure, documents and projects in Examples
V1.1.5: (03.05.2013)
Update of AC500 online help (CAA-Merger11.chm) - Version delivered with Control Builder Plus V2.3.0
V1.1.4: (12.04.2013):
Update of AC500 online help (CAA-Merger11.chm) including German translation.
V1.1.3: (03.04.2013):
Update of example documentations and AC500 online help (CAA-Merger11.chm).
V1.1.1: (16.01.2013):
ACSDrivesBase_AC500_V20.lib:
Bug fixes in existing visualizations for webserver use
ACSDrivesComModRTU_AC500_V20.lib:
Bug fixes in existing visualizations for webserver use
InstallShield:
Bug fix to install (setup) documentation without libraries
V1.1.0: (14.12.2012):
ACSDrivesComModTCP_AC500_V22.lib:
new library for Modbus TCP communication to all ACSxxx drives
ACSDrivesBase_AC500_V20.lib:
New function blocks for fieldbus independent control and scaling
Bug fixes in existing function blocks and visualizations
ACSDrivesComModRTU_AC500_V20.lib:
New function blocks for Modbus RTU communication to all ACSxxx drives
New function blocks for communication to generic slave devices used on same RTU line.
Bug fixes in existing function blocks and visualizations
Documentation:
Update of chm docu in CAA-Merger11.chm
Examples:
New examples for connection with Profibus, ProfiNet
V1.0 (10.12.2010):
Release for AC500-eCo and ACS3XX
Known issues
Drive manager may be disconnected if user is using Profinet / Profibus DPV1 read write function block in PLC. (AB-8376)
Currently user cannot use enumeration from ACS_PB_PN_PRM_TYPE_ENUM. Instead user need to use numerical
values from ACS_PB_PN_PRM_TYPE_ENUM only. (LIB-940)
Modbus reconnection not possible in special cases (LIB-2245):In the following case it might be possible that the
connection to the drive is not reestablished after a connection loss, e.g. due to cable being unplugged or power off of the
drive:
If the “EN” input of the control blocks (ACS_DRIVES_CTRL_STANDARD, ACS_DRIVES_CTRL_ENG) is connected from
the output “ONLINE” of the communication block ( e.g. ACS_COM_MOD_RTU, ACS_COM_MOD_RTU_ENHANCED,
ACS_COM_MOD_TCP, ACS_COM_MOD_TCP_ENHANCED, ACS_COM_MOD_TCPx,
ACS_COM_MOD_TCPx_ENHANCED) it is necessary to switch off/on the PLC.
Workaround: We strongly recommend to set the EN input of the control blocks fix to TRUE.
27
Appendix - Appendix 3: PS566 CMS Signal Processing Package (Technology Preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
Welcome to the AC500 CMS Signal Processing Package, Version 2.1.0, consisting of
SP_AC500_V28_App.lib (and .obj files, since the library contains C-Code)
Example folder with examples, example documentation and library documentation
The software Libraries in this package have been tested with the following versions:
Automation Builder AB1.2 to AB2.8.0
PM592-ETH Firmware FW2.4 to FW 2.8.6 (Version 2.0.0 requires at least FW2.8.0)
FM502 V1.0.0
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
V2.1.0 (AB2.4.1, 2020-05-04)
o New function blocks (Prototype folder)
SP_MAGFFT_OVERLAP_AVG_App (LIB-2563)
SP_FFT_CMPL_POLAR_App, SP_PHASE_OFFSET_FREQ_App, SP_PAHSE_OFFSET_TIME_App,
SP_SPEED_KEYPHASOR_App (LIB-2286)
o Fixed function blocks:
SP_FFT_RMS_App improved (LIB-2560)
SP_STATISTICS_App, MEDIAN now fully working (LIB-2550)
o Example updated: AC500_V2_CMS_SP_Expert_AB240.project , Bug fix for overwrite encoder settings (LIB-
2493, LIB-2391)
o Updated library documentation in example folder ...PS566-CMS\Signal Processing
V2\LibraryDocumentation (LIB-2567)
V2.0.0 (AB 2.2.5, 2020-03-04)
o Library optimized: SP_AC500_V28_App.lib (LIB-2146, LIB-2100, LIB-2235), SP_ENVELOPE_App corrected
(LIB-2199). Upgrade path is described in chapter 4.1 of AC500 V2 CMS SP Library V200 description
3ADR025244M0208.pdf.
o New examples for first steps, gearbox and pumping (LIB-2230, LIB-2168, LIB-1999)
V1.3.0 (AB 2.2.3, 2019-06-03)
o New function block added: SP_READ_WAV_HEAP_App which doesn't needs the program memory but works in
the heap (LIB-2029)
V1.2.3 (AB 2.2.1, 2019-03-01)
o Examples improved (LIB-1965), updated FIR Block: First samples according to filter order number are deleted
(LIB-1953)
V1.2.2 (AB 2.2.0, 2018-10-09)
o Fixed calculation mistake / issue in the SP_FIR_FILTER_APP Function Block (LIB-1733), library enabled for
PM595 (LIB-1721)
V1.2.1 (AB 2.1.2, 2018-06-05)
o New function blocks: SP_FFT_RMS_APP, SP_FIR_FILTER_APP, SP_HARMONICS_APP,
SP_MAGFFT_ENERGY_APP, SP_MATH_APP
V1.1.0 (AB 1.2.3, 2016-07-11)
o New LP and HP filter blocks: SP_HIGH_PASS_FILTER_APP, SP_LOW_PASS_FILTER_APP
V1.0.0 (AB 1.0.0, 2016-01-18)
o First version: SP_AC500_V24_App.lib
Known limitations or bugs
only supported by PM585 or higher due to need of co-processor
Installation and Update
Basic CMS libraries and examples are part of the Automation Builder:
Basic Libraries: \Program Files\Common Files\CAA-Targets\ABB_AC500\AC500_V12\library\CMS_IO_AC500_V24.lib and
WAV_FILE_AC500_V24.lib
Basic Examples: \Users\Public\Documents\AutomationBuilder\Examples\PS566-CMS\Measurements
28
Appendix - Appendix 3: PS566 CMS Signal Processing Package (Technology Preview) 2024-12-12
This package contains additional libraries, examples and documentation for the Condition Monitoring System:
Signal Processing library: \Program Files\Common Files\CAA-
Targets\ABB_AC500\AC500_V12\library\ApplicationLibraries\SP_AC500_V28_App.lib
Signal Processing examples and library help file: \Users\Public\Documents\AutomationBuilder\Examples\PS566-
CMS\Signal Processing V2
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
29
Appendix - Appendix 4: PS565 BACnet-ASC Library Package (license required) 2024-12-12
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
License is obtained via an authorization code as a product, which has to be bought via the normal AC500 sales channels.
LIB-1390: Performance improved with library BACnet_BASC_AC500_V28.lib (V1.0.2), for even faster versions please
contact support
30
Appendix - Appendix 5: PS554 FTP Client Library Package (Technology Preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
31
Appendix - Appendix 6: PS562 Solar Library Package (license required) 2024-12-12
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
SolarNREL_AC500_V22.lib
Solar_AC500_V22.lib
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
License is obtained via an authorization code as a product, which has to be bought via the normal AC500 sales channels.
If you had an authorization code for this major library version already, please contact support for an update license/code.
32
Appendix - Appendix 7: PS5617 Solar Library Package for AC500 V3 (technology preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB
Support hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature
this can be done in the context of a piloting. In this case please contact us to set up a piloting agreement.
Welcome to the PS5617-Solar Library Package, V1.0.0.2, which is the V3 upgrade of the V2 Solar library (PS562-SOLAR)
Example_PM5072_Solar_2Axis_ABxxx.project
AC500_Example_PM5072_Solar2Axis_3ADR011085R1.pdf
(ABB_Solar_AC500.compiled-library is not part of the Automation Builder Installation Package. For the Library, please
contact Technical Support: plc.support@de.abb.com.)
The solar library has been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
This Library Package is part of the Automation Builder. It can be selected as an Option during installation or any time later
using the Automation Builder Installation Manager.
(ABB_Solar_AC500.compiled-library is not part of the Automation Builder Installation Package. For the Library, please
contact Technical Support: plc.support@de.abb.com.)
33
Appendix - Appendix 8: PS563 Water Library Package (license required) 2024-12-12
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
LogData_AC500_V23.lib
PUMP_AC500_V23.lib
HMI example for ACQ Drive (project for pumping functions in ACQ810)
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
License is obtained via an authorization code as a product, which has to be bought via the normal AC500 sales channels.
If you had an authorization code for this major library version already, please contact support for an update license/code.
34
Appendix - Appendix 8: PS563 Water Library Package (license required) 2024-12-12
Pump Station Configuration Tool as Technology Preview: Boost Control Mode added
LogData_AC500_V23.lib: Bugfix direct communication Mode 2
PUMP_AC500_V23.lib - Fixed: Autochange style 3 not working for level control with two pumps [LIB-1637]
Pump Station Configuration Tool removed (discontinued)
LogData_AC500_V23.lib: Bugfix for automatic mode of generic logger: When refresh on historical data in first cycle, a
wrong historical array was stored (LIB-2772)
35
Appendix - Appendix 9: PS564 Temperature Control Library Package (license required) 2024-12-12
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
License is obtained via an authorization code as a product, which has to be bought via the normal AC500 sales channels.
If you had an authorization code for this major library version already, please contact support for an update license/code.
36
Appendix - Appendix 10: AC500 HVAC Library Package (Technology Preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
AC500 Library HVAC_AC500_App_V22.lib (V1.0.2) containing basic Function Blocks, structures and visualizations for
Heating, Ventilation and Air Condition
AC500 Library CTRL_AC500_App_V22.lib (V1.0.1) containing HVAC specific control or signal processing blocks
CTRL_test_example_PM583.project example for the CTRL library, function block CTRL_PI_PULSE_APP
HVAC AC500 Application Library Package Documentation V103.pdf (V1.0.3) documentation for HVAC libraries including
example description
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
V1.0.0 2013-11-07 First release of package, consisting of HVAC_AC500_App_V22.lib (V1.0.0) and CTRL_AC500_App_V22.lib
(V1.0.0)
V1.0.1 2014-05-15 HVAC_AC500_App_V22.lib (V1.0.1): Update of air density and enthalpy FB
V1.0.2 2015-01-19 HVAC_AC500_App_V22.lib (V1.0.2): Add conversion function LREAL_TO_REAL,
CTRL_AC500_App_V22.lib (V1.0.1): CTRL_FILTER_CONTINUOUS_APP optimized
V1.0.3 2015-12-10 Example CTRL_test_example_PM583.project updated for upgrade to PM595
none
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
37
Appendix - Appendix 11: PS571 Pumping Library Package (Technology Preview, license required) 2024-12-12
Appendix 11: PS571 Pumping Library Package (Technology Preview, license required)
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
38
Appendix - Appendix 12: PS552-MC-E Motion Control Library Package (license required) 2024-12-12
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
Initial delta times values for MC_PositionProfile, MC_VelocityProfile and MC_AccelerationProfile must be zero (LIB-550)
ACS355_Drive-based_MotionControl_ProfibusDP.project and ACSM1_Drive-based_MotionControl_ProfibusDP.project:
Compilation error due to new Profibus library. Work around is user should manually delete PROFIBUS_AC500_V10.lib.
(LIB-1311)
Automation Builder crashes when PLC_PTO_PLCopen_example.project is used with MC MoveAbsolute (AB-14638)
Workaround: Login and download the project to the PLC via CoDeSys from 3S (instead of Automation Builder)
MC_SetPosition function block throws error 7 (timeout) as long as Execute=TRUE when used with FM562 PTO module.
(LIB-1139)
When FM562 PTO module is used, Stepper motor will not stop when MC_Power function block is disabled. (LIB 1560)
MC_ReadStatus function block is reads wrong status when the Axis Enable DI0 is powered off on FM562 module
(LIB1561)
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
License is obtained via an authorization code as a product, which has to be bought via the normal AC500 sales channels.
If you had an authorization code for this major library version already, please contact support for an update license/code.
Updated libraries
o CompactMotionControl_AC500_V12.lib: V3.2.4
o MathFunctions_AC500_V23.lib: V3.1.0
39
Appendix - Appendix 12: PS552-MC-E Motion Control Library Package (license required) 2024-12-12
o MC_Base_AC500_V11.lib: V3.2.4
o MC_Blocks_AC500_V11.lib: V3.2.4
o MC_CoBlocks_AC500_V23.lib: V3.2.0
New function blocks
o MCA_CAMINFO
o MCA_PhasingbyMaster (LIB-1032)
Bug fixing
o Using MC_COMBINEAXES results in increasing EtherCAT processing time when used with Modulo axes (LIB-
1219)
o MC_SetPositon reports error 7 (timeout) as long as Execute=TRUE used with PTO (LIB-1139)
o Stepper motor running with MC_Power function block does not stop even if the MC_Power function block is
disabled while running. (LIB-1560)
o MC_ReadStatus function block is reading wrong status when the Axis Enable DI0 is powered off on FM562
module (LIB-1561)
o Move FBs should not start a movement with deceleration=0, because it will then never stop again (LIB-1040)
Examples updated
o ACS355_Drive-based_MotionControl_ProfibusDP_AB240.project
o ACSM1_Drive-based_MotionControl_ProfibusDP_AB240.project
o Ethercat Application Library_Description V03 3ADR023047M0202.pdf (example documentation)
o PTO example docu updated with AB2.5.0 (AB-20253)
40
Appendix - Appendix 12: PS552-MC-E Motion Control Library Package (license required) 2024-12-12
41
Appendix - Appendix 13: PS5602 IEC 61850 Server for AC500 V3 (runtime license required) 2024-12-12
Appendix 13: PS5602 IEC 61850 Server for AC500 V3 (runtime license required)
This package allows the AC500 to act as interface to substation automation systems via IEC 61850:
AC500 V3 CPU acts as an IED with IEC 61850 Server, Edition 1, allowing communication as MMS Server and GOOSE
Publisher and Subscriber
A wide set of Logical Nodes is pre-defined and can be extended.
The implementation of Logical Nodes can be freely programmed in ST code.
Automation Builder is used as IED configuration tool for modelling the IEC 61850 data structures and connecting them to
the PLC applications
Support of SCL – Substation Configuration Language to transfers detailed configuration information between different
IEDs
Version history
V4.0.7.3 (setup 4.0.7.2574, library 4.0.7.8) (Feb 2023)
Improvements
- MMS and GOOSE is possible via new Ethernet coupler CM5640 (AC500_TEST-2659)
- Number of possible datasets increased from 20 to 32 (AB-21005)
- IEC61850 system technology updated in Automation Builder help
Bugs fixed
- GOOSE messages greater than 1500 byte do not lead to exception anymore, runtime error is created now (LIB-2996)
- GOOSE subscriber now also working on ETH2 onboard (LIB-3135)
- MMS Server is only listening on configured Ethernet slot (LIB-3121)
V4.0.7.2 (setup 4.0.7.2257, library 4.0.7.6) (June 2022)
- Updated Logical node definition, which will only take effect after project upgrade and then creating new logical nodes
(AB-21319)
- https://iec61850.tissue-db.com/tissue/219
- updated SBO for all controllable data object types: SPC / DPC / INC / BSC / ISC
- GOOSE Subscriber.xErrorTimeAllowedToLive fixed (LIB-2879)
- GOOSE Subscriber now working on 2nd Ethernet adapter (LIB-2800)
- GOOSE Subscriber stabilized for high number of GOOSE messages (LIB-2980)
- GOOSE Publisher: Increased TAL (Time Allowed to Live), when GOOSE value has changed (LIB-2947)
- GOOSE manager: Improved diagnosis (LIB-2870, LIB-2968)
- Added dummy IP information to exported cid file (AB-21298)
V4.0.7.1 (setup 4.0.7.2170, library 4.0.7.1) (December 2021)
- GOOSE performance improved (AB-20488), more details in AC500_IEC61850_Example_Description_3ADR010262_6_
en_US.pdf, chaper 4.3
- Configuration of GOOSE publisher min repetition time can now be configured (LIB-2761)
- Configuration of IEC61850 Server: Properties "IP, Subnetmask, Gateway" removed , since they were never active.
AC500 IP settings are (and were always) only configured in Communication settings of the PLC
V4.0.7.0 (setup 4.0.7.1991, library 4.0.5.7) (December 2020)
- MAC address for GOOSE publisher/subscriber can be entered offline (FEAT-286)
- GOOSE Master can be disabled (LIB-2412)
- Updated and new examples (D and E)
V4.0.6 (June 2019)
- library AC500_IEC61850Server 4.0.5.5. updated for changed references in AB2.3.0 (LIB-2370)
V4.0.5 (March 2019)
- library placeholder renamed to AC500_IEC61850Server (4.0.5.4), package updated (AB-15610)
- no functional changes
V4.0.4.0 (Release, October 2018)
- Sequence of Coded Enum bits corrected (PUA-206)
- SCL Import error corrected (PUA 204)
- Number of signals increased from 250 to 1000 (PUA-209)
V4.0.3.75 (Technology Preview, Mai 2018)
- Final fixes for certification by TÜV Süd
V4.0.3.60 Update (March 2018) with following improvements
- No “clean all” after update of IEC 61850 server needed any more (PUA-170)
42
Appendix - Appendix 13: PS5602 IEC 61850 Server for AC500 V3 (runtime license required) 2024-12-12
Limits
MMS Reporting: max 5 MMS clients
GOOSE Publish and MMS reporting: Max 32 datasets. Each dataset is limited to 50 entries, which can be data objects or
data attributes.
GOOSE Publish: The GOOSE Ethernet frame length must not exceed 1500 bytes. This can even happen with less than 50
data objects per dataset, if each data object has many data attributes
Example: The maximum number of large data objects of type AnIn (containing 7 data attributes each) is 35 per dataset
only.
Exceeding 1500 bytes will lead to a runtime error at the dagnosis variable eStatus. Workaround: Reduce DO/DAs in
dataset.
GOOSE Subscribe: Max 50 Ethernet frames per cycle. Workaround: Adapt cycle time
GOOSE Publish or Subscribe: Max 3000 Byte per cycle. Workaround: Adapt cycle time
Not possible to have 2 or more IEC61850 server in one AB project. Workaround: Create 2 or more projects (PUA-172)
Only one Logical Device per IEC61850 Server
Only one Report per DataSet (PUA-167)
Known issues
AC500 is configured for sending MMS reports: If an MMS client subscribes to the MMS report and disables the trigger
options “Data change” or “Date quality”, not all data are reported correctly. This will be fixed with next Automation Builder
(AB-24086).
Workaround: Contact PLC support for detailed steps to be followed to correct the auto generated IEC61850 code.
IEC61850 Server: instMag is removed but it still show in the IEDScout report (AB-22437). Workaround: Ignore InstMag
additional tag on the SCADA/Client side.
Exceeding the GOOSE Publish Ethernet frame length above 1500 bytes leads to an exception (LIB-2996)
This can even happen with less than 50 data objects per dataset, if each data object has many data attributes
Example: The maximum number of large data objects of type AnIn (containing 7 data attributes each) is 35 per dataset
only
For GOOSE communication with small cycle times of 1-2 ms, we have observed higher PLC load and longer round-trip
times with AB2.6.0 (AC500_TEST-2752)
43
Appendix -
Appendix 14: PS5605 Drives Library Package for AC500 V3 2024-12-12
This release notes contains important information about the library and it´s installation.
Change history
Package V1.3.0.1 (Dec 2023)
- DrvModbusTcp FB is extended to support Drives communication via CM5640-2ETH coupler (LIB-3586)
- DrvModbusRtu and DrvModbusRtuBroadcast FBs are extended to support Drives communication via CM5610-2RS
coupler (LIB-3585)
Package V1.3.0.0 (Feb 2023)
- Profinet read and write Function blocks updated with input Device replacing input slot. (LIB-2845) -> Upgrade of projects
which were created with previous AB versions requires a rework of all used DrvPnRead and DrvPnWrite function blocks.
See also application note
- Online help updated for Profinet read write FB changes (AB-22090)
- Profinet example project updated based on updated read and write FBs (LIB-2802)
Package V1.2.0.0 (December 2021)
- new function blocks: DrvProfinetRead and DrvProfinetWrite (LIB-1905, LIB-1906)
- updated example and documentation
- Fixed LIB-2625: DrvModbusTcp and DrvModbusRtu: Wrong detection of Write-Value-Changes in specific situation
- Fixed LIB-2626: DrvModbusWrite, DrvModbusTcp and DrvModbusRtu: Write values are not stored at rising edge of
execute, only the pointer
Package V1.1.0.3 (May 2021), containing ABB_Drives_AC500.compiled-library, V1.1.0.17
- Support for V3 eco: COM ports > 1 supported (LIB-2594)
- DrvModbusWrite improved: read values at rising edge of Execute (LIB-2270), except write values (LIB-2626, see know
issues)
- DrvModbusTcp improved (LIB-2275)
Package V1.1.0.2 (March 2020), containing ABB_Drives_AC500.compiled-library, V1.1.0.11
- updated Quickstart guidePackage V1.1.0.1 (November 2019), containing ABB_Drives_AC500.compiled-library,
V1.1.0.11
- function block documentation updated (LIB-2128)
- code styleguide improvements (LIB-2140, LIB-2098)
Package V1.1.0.0 (First product version, June 2019), containing ABB_Drives_AC500.compiled-library, V1.1.0.9
- New function blocks: DrvControlCANCiA402, DrvControlModbusEng, DrvModbusReadWrite23, DrvModbusRtuBroadcast
- Improvements and Enhancements
- Bug fixes
- Example documents and project for all protocols supported.
- Generic modbus blocks (starting with ModRtu...) were moved to generic Modbus RTU library: AC500_ModbusRtu
Package V1.0.0.2 (Technology Preview, March 2019), containing ABB_Drives_AC500.compiled-library, V1.0.0.19
- New examples for EtherCAT, Profinet and ModbusRTU
- New function block ModRtuReadWrite23 (LIB-1904)
- New function block DrvModbusReadWrite23 (LIB-1945)
- New function block DrvControlModbusEng (LIB-1678)
- New function block DrvControlCANCiA402 (LIB-1907)
- LIB-1895 - ModRtuToken improved
- LIB-1929 - NoConToDrive output in the DrvControlModbusEng added
- LIB-1840 - DrvModbusRtu improved
- LIB-1820 - DrvModbusTcp input validation for 'IpAdrServer'
- LIB-1841 - DrvControlModbusACS and DrvControlModbusDCS improved
- LIB-1819 - Visualization updated
- LIB-1838 - ModRtuRead improved
- LIB-1804 - bug fix for line token halt
44
Appendix -
Appendix 14: PS5605 Drives Library Package for AC500 V3 2024-12-12
- LIB-1928 - bug fix, update in function block description related to Online output in DrvModbusTcp
- LIB-1966 - HA specific functionality inputs
Package V1.0.0.1 (Technology Preview, October 2018) containing ABB_Drives_AC500.compiled-library, V1.0.0.9
- First version
45
Appendix - Appendix 15: PS5601 HA ModbusTCP Library Package for AC500 V2+V3 (runtime license required) 2024-12-12
Appendix 15: PS5601 HA ModbusTCP Library Package for AC500 V2+V3 (runtime license required)
AC500 V2:
HAModbus_AC500_V26.lib, V1.3.0.x
(CI52x_AC500_V26.lib, V1.3.0.x is installed by default for use of CI52x modules without HA)
AC500 V3:
ABB_HaModbus_AC500.compiled-library, V1.4.0.x
(ABB_CI52x_AC500.compiled-library, V1.4.0.x is installed by default for use of CI52x modules without HA)
The software Libraries in this package have been tested with the following versions:
Automation Builder AB2.2.3 to AB2.8.0
V2 CPU: FW2.7.2 to FW2.8.6
V3 CPU: FW3.2.2 to FW3.8.0
CI52x-MODTCP F0, Firmware V3.2.3 to 3.2.13
CM597-ETH (Firmware 1.2.1.20 to 1.2.18.21)
CM5640-2ETH, FW3.7.0.158
Bulk Data Manager tool: Bulk_Data_32bit_1.0.8899.40216.zip / Bulk_Data_64bit_1.0.8899.40458.zip
The package contains further documents, examples and tools: Please start by reading the System technology description
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
This release notes contains important information about the library and it´s installation.
The package is an installation option of Automation Builder and contains the following parts:
V2 libraries are copied to …\Common Files\CAA-Targets\ABB_AC500\AC500_V12\library\PS5601-HA-MTCP
V3 libraries are installed into Library repository
Bulk Data Manager Tool, Library documentation, Example projects and documentation are copied to
C:\Users\Public\Documents\AutomationBuilder 2.8\Examples\PS5601-HA-MTCP
The Library package requires to have a PS5601-MTCP runtime license per each CPU to be entitled to use it . (V3 CPU can even not
go to Run mode without that the license has been locked to the CPU, but will report a notification “PLC License missing”).
PS5601-MTCP is a normal product license which must be bought through normal sales channel. Installation is described in the
system technology, chapter 1.2.2.5
Change history
46
Appendix - Appendix 15: PS5601 HA ModbusTCP Library Package for AC500 V2+V3 (runtime license required) 2024-12-12
47
Appendix - Appendix 15: PS5601 HA ModbusTCP Library Package for AC500 V2+V3 (runtime license required) 2024-12-12
o When an IO module is removed or reconnected during operation an error is shown (RuntimeError.2), but during
the next 60 seconds it comes back after acknowledgement by input ACK (LIB-1752, 1762)
o Runtime error bit 7 is not triggered when CI Module is powered off for all clusters (LIB-2371)
o Network reconfiguration: may lead to signal freeze in CI52x module (duration of 500 ms for V2 CPU, if onboard
Ethernet is used) (LIB-1628, LIB-1690) --> workaround: Use CM597 coupler
o V3
LifeCom2 (on modbus) Error bit is blinking in normal operation when Sync cable is removed from PLC
(LIB-1641)
LifeCom2 (CAN only) cable disconnection sometimes causing PLC switchover (LIB-1645)
Runtime error gets generated in running system after some hours for certain duration (LIB-2490)
Improvements
o 120 CI modules possible with V3 library using new priority scheme "Onboard Ethernet" (CPUFW-8029, CPUFW-
8343, LIB-2401)
o New diagnostic function blocks HaModDiag and CIModDiag (LIB-1880, LIB-2191, LIB-2032, LIB-2189, LIB-
2190)
Examples updated, new examples for HA without CI module
Documentation updated
Notes for customer upgrading current running HA system from package 1.2.0.x to new package 1.3.0.x
For AC500 V2
1. timHaModSyncTimeOut: Added into the library to check lifecom1 sync timeout based on HA task. This timeout should be
set equal to HA Task time. Earlier Sync timeout was internally using timCi52xTimeout (this timeout is related to Modbus
field communication to CI52x. To make the lifecom1/sync timeout independently settable, timHaModSyncTimeOut is
added. If timeouts are not adapted as recommended to the application size, then default values are used which can lead to
runtime errors for sync indicating e.g. unstable system with e.g. frequent exchange of primary status.
For AC500 V3
1. timHaModSyncTimeOut: Added into the library to check lifecom1 sync timeout based on HA task. This timeout should be
set equal to HA Task time. Earlier Sync timeout was internally using timCi52xTimeout (this timeout is related to Modbus
field communication to CI52x. To make the lifecom1sync timeout independently settable, timHaModSyncTimeOut is
added. If timeouts are not adapted as recommended to the application size, then default values are used which can lead to
runtime errors for sync indicating e.g. unstable system with e.g. frequent exchange of primary status.
2. timResponseTimeout: Added into the library to allow CI module timeout to be aligned with system size = number of CI
modules. This timeout should be at least 2 * Modbus cycle time or minimum 50ms (present default value is 32ms and has
to be changed).
3. V3 CPU parameter Communication Schema has to be set as “Onboard Ethernet” (new CPU parameter since AB2.4.1 see
online help).
This setting is mandatory and will increase the PLC and CPU load: Therefore recheck your loads before and after upgrade
and adjust the HA tasks (HA, Modbus, application) settings to slightly higher values if deemed necessary (follow the task
calculation guidelines in HA system technology: pdf in AB/Examples/ directory).
48
Appendix - Appendix 15: PS5601 HA ModbusTCP Library Package for AC500 V2+V3 (runtime license required) 2024-12-12
49
Appendix - Appendix 16: PS573 PCO Library (Technology Preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a preview at upcoming technologies. They are non-final versions of our
product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be changed or removed in newer versions of Automation Builder as
communicated via the release notes. If technology previews are subject to licensing, please contact your ABB sales representative.
The software Libraries in this package have been tested with the following versions:
Please start by reading the System technology description, which can be found in the Automation Builder online help.
A simple example can be found in the example folder: C:\Users\Public\Documents\AutomationBuilder\Examples\PS573-PCO
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
Package V0.9.3.1 (2021-04-29): Updated version (Technology Preview) for AB2.4.1
o Formal changes (LIB-2535)
Package V0.9.3.0 (2020-12-01): Updated version (Technology Preview) for AB2.4.0
o Library prepared for 800xA intelligent uploader (LIB-2201) new Version 0.9.1:
upgrade procedure from 0.9.0 to 0.9.1 is given in AC500_PCO Library Example Documentation
AB223 3ADR010401_r4.pdf
o example docu updated (LIB-2207)
o online help updated (AB-17542)
Package V0.9.2.0 (2019-11-08): Updated version (Technology Preview) for AB2.2.4
o Documentation improved and PCO_MOTCON details added to example folder (LIB-2153, LIB-2169)
Package V0.9.1.0 (2019-06-26): First version (Technology Preview) for AB2.2.3
o library documentation (system technology and function block description) moved from example folder (pdf) to
online help
Package V0.9.0.0 (2019-05-27): First version (Technology Preview for Pilot customers) for AB2.2.x
o First version
Known limitations or bugs
None
Installation and Update
This Library Package is part of the Automation Builder. It can be selected as an Option during installation.
The package contains the following parts:
V2 libraries are copied to …\Common Files\CAA-Targets\ABB_AC500\AC500_V12\library\Application
Example projects and documentation are copied to C:\Users\Public\Documents\AutomationBuilder\Examples\PS573-PCO
50
Appendix - Appendix 17: PS5607 BACnet-BC Library Package for AC500 V3 (runtime license required) 2024-12-12
Appendix 17: PS5607 BACnet-BC Library Package for AC500 V3 (runtime license required)
BACnet is a standardized data communication protocol for Building Automation and Control networks as defined in the
ANSI/ASHRAE Standard 135 and ISO 16484-5. This package enables AC500 to act as a BACnet Building Controller (B-BC profile)
as server and/or client. Supported protocol are BACnet IP and MS/TP.
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
This release notes contains important information about the library and it´s installation.
Version history
If server objects of type "BACNet.BacnetSchedule" is initiated in the PLC application, the PLC will crash when the project
is deleted from the device.
Workaround: Only use the BACnet Schedule by adding it below the BACnet Server in the device tree instead of adding it
from the PLC application. (CPUFW-7854)
AC500 holds UTC time only (LIB-2430). A workaround is described in online help - BACnet system technology
After deleting MSTP datalink from COM port and download, the MSTP datalink is still active (AB-19441)
BACnet MSTP communication is not supported on CM5610-2RS. (LIB-3538)
51
Appendix - Appendix 17: PS5607 BACnet-BC Library Package for AC500 V3 (runtime license required) 2024-12-12
This Library Package is part of the Automation Builder. It can be selected as an Option during installation or any time later using the
Automation Builder Installation Manager.
52
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required)
Welcome to the Motion Control (PS5611) software package which contains the following components and features:
1. Motion Control libraries (V1.4.0.4) based on PLCopen Motion Control standards with documentation and examples.
– listed as package "Motion Library PS5611" - PS5611-MC product license needed for the use.
2. Motion Solution wizard (V280) to configure the motion solution and its axes in an user oriented way, based on PLCopen
Motion Control library.
– listed as package " ABB Motion Solution".
3. CAM Editor (V280) to visually create CAM tables linked to the PLCopen Motion Control library. Named as Generic Solution
Engineering in Packages.
- listed as package "ABB Motion Solution".
The components have been tested with Automation Builder 2.8.0 and CPU Firmware 3.8.0.
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions cannot be guaranteed.
Motion Control libraries are an upgrade and extension of V2 PS552-MC (without coordinated and drive based motion). The Motion
Control library package contains additionally ABB_MotionControlLoad library (Tech Preview *) and ABB_MotionControlExtension
library. The first version Motion Control library package was available with AB2.4.0.
* Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB Support
hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature this can
be done in the context of a piloting. In this case, please contact us to set up a piloting agreement.
AC500_MotionControl library
New Features
Function block MCA_PhasingReset - LIB-3712
CMC_Axis_IO added with new switch options (HardLimitSwitchPos / Neg) - LIB-3729
Function block MCA_AxisManualControl - LIB-3636
Function block MCA_CamAppend LIB-3590
New OffSetMode for Function Block MCA_CamStructureSelect - LIB-3627 / LIB-3602
Improvements
Improved Error handling for MC_CamIn – LIB-3591
Improved MasterStartPosition handling - LIB-3627 / LIB-3796 / LIB-3819
Improved documentation for MC_CamIn – LIB-3681 / LIB-3827
Improved Jerk behaviour - LIB-3763
53
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
Bug fixes
MCA_JogAxis decelerate after MinJogDistance - LIB-3806
MC_SetPosition causes some time axis to jump - LIB-3809
MC_MoveAbsoulte issue multiple movements where it is combined with very larger / small set positions
randomly - LIB-3809
Finite axis gives wrong position when inverted direction - LIB-3863
Fixed Jerk related issues - LIB-3759
Axis type “Finite rotary” and parameter inverter direction issue - LIB-3741
Fixed issues when switching to different CamIn instances with different interpolation types - LIB-3685
Support for CMC_GET_UNITS_FROM_INC with 64-bit Kernel - LIB-3682
Fixed MC_ReadStatus output, if the error on drive is reset not via PLC - LIB-3691
Issue with end velocity & Offset for MC_VelocityProfile and MC_AcclerationProfile - LIB-3662 / LIB-3493
MC_CamOut when axis running in negative direction - LIB-3495
Visualization issue with MCA_CamStructureSelect - LIB-3629
ABB_MotionControlEco library
Improvements
ContinuousMode feature added with MCA_TouchProbeOBIO - LIB-3754
ABB_Ecat_CiA402 library
Improvements
Improved simulated axis when a real drive is connected - LIB-3813
Support for drives which partially supports the CiA402 state machine – LIB-3831
Improved ECAT_CiA402_TouchProbe_App to detect the new touch value in continuous mode- LIB-3755
Bug fixes
ECAT_402ParameterHoming_APP not working when DriveType changes - LIB-3724
ABB_MathFunctions library
No changes
54
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
Cam Functions Blocks from ABB_MotionControlExtension library can only be used with Cam Table ABB (and not the older
Cam Table ABB Basic)
Some of the functionalities from ABB_MotionControlExtension library and Expert structure works, only when used together
with Motion Solution Wizard from AB2.7.0 or higher and the user must select the relevant PDO mappings in the EtherCAT
configuration.
Libraries are only tested with ABB Servo Products.
The Motion Solution wizard helps in efficiently configuring the EtherCAT axis using Automation Builder in a short time. The first version
was available with AB2.5.0.
Detailed documentation explaining how to use the motion solution wizard is available in the Automation Builder example folder “AC500
V3 Motion Controller Guide_3ADR011239.pdf”
3. CAM Editor
The newly introduced Cam editor can create Cam & tappet table using the graphical window of Cam editor. The first version was
available with AB2.5.0.
Detailed documentation explaining how to use the Cam Editor is available in the Automation Builder example folder “AC500 V3
Motion Controller Guide_3ADR011239.pdf”
55
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
Improvements
MC_GearIn/MC_GearInPos/MC_GearInDirect Ratio input type changed from INT to DINT - LIB-3571
MC_GearInPos improvements - LIB-3774 / LIB-3758
Cam behaviour improvements - LIB-3730/ LIB-3731/ LIB-3618/ LIB-3563
Improved handling for high acceleration/deceleration for positioning move- LIB-3748
Improved MCA_DriveBasedHome - LIB-3728
Allow axis to run with larger following error when following error monitoring is deactivated - LIB-3707
Improved InVelocity behavior in MC_MoveVelocity - LIB-3630
MC_ReadStatus with additional output to show any Kernel Error/Warning - LIB-3411
Several documentation improvements
Bug fixes
Fixed Jerk related issues - LIB-3759
Axis type “Finite rotary” and parameter inverter direction issue - LIB-3741
Fixed issues when switching to different CamIn instances with different interpolation types - LIB-3685
Support for CMC_GET_UNITS_FROM_INC with 64-bit Kernel - LIB-3682
Fixed MC_ReadStatus output, if the error on drive is reset not via PLC - LIB-3691
Issue with end velocity & Offset for MC_VelocityProfile and MC_AcclerationProfile - LIB-3662 / LIB-3493
MC_CamOut when axis running in negative direction - LIB-3495
Visualization issue with MCA_CamStructureSelect - LIB-3629
ABB_MotionControlEco library
No changes
ABB_Ecat_CiA402 library
Improvements
Improved ECAT_CiA402_TouchProbe_App to detect the new touch value in continuous mode- LIB-3755
Bug fixes
ECAT_402ParameterHoming_APP not working when DriveType changes - LIB-3724
ABB_MathFunctions library
No changes
56
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
57
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
58
Appendix - Appendix 18: PS5611 Motion Control Package for AC500 V3 (runtime license required) 2024-12-12
3. CAM Editor
V2.7.0.1 released with AB2.7.0.249 ABB Motion Solution update package
Bug fixes
“Cam table ABB” generating wrong number of CamPoints when the segment type is “Line”- AB-24454
Easier debugging when multiple Cam objects are used - AB-24581
V2.7.0 2023-12-04, released with AB2.7.0
New functions:
New Cam table named “Cam table ABB” with supporting function block MCA_CamStructureSelect to use
the many Cam functions from ABB_MotionControlExtension library - AB-23182
V2.6.0 2023-02-15, released with AB2.6.0
No changes
V2.5.2 2022-11-24, released with AB2.5.2
Cam tappet function - AB-21528
V2.5.0 First version released with AB2.5.0 (Tech preview)
59
Appendix - Appendix 19: PS5609 Log Library Package for AC500 V3 (Runtime license required; Multilogger is without license and
technology preview) 2024-12-12
Appendix 19: PS5609 Log Library Package for AC500 V3 (Runtime license required; Multilogger is without license
and technology preview)
Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB
Support hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature
this can be done in the context of a piloting. In this case please contact us to set up a piloting agreement.
The software Libraries in this package have been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
V1.1.0.2 2024-11:
o Datalogger Eco library extended to support PM5092-2ETH (LIB-3700)
V1.1.0.1 2023-12:
o Datalogger Eco library extended to support PM5082-2ETH (LIB-3506)
o Improvement in LogFileReduceFB in Multilogger library (LIB-3276)
V1.1.0.0 2022-09: Update package release (to be used with AB2.5.1 or higher):
o DataLogger and DataLoggerEco: Change from Technology preview to product. Separate runtime license for
DataLoggerEco
o DataLoggerEco library namespace is updated to AC500_Datalogger from AC500_DataloggerEco.
o DataLoggerEco FIFO size is configurable between 0 to 60.
o DataLoggerMulti: Only mode 2 and 3 as technology preview, no license required
V1.0.0.0 2022-01: First version with AB2.5.0
(none)
This Library Package is part of the Automation Builder. It can be selected as an Option during installation or any time later
using the Automation Builder Installation Manager.
60
Appendix - Appendix 20: PS5608 Pump Library Package for AC500 V3 (technology preview) 2024-12-12
Appendix 20: PS5608 Pump Library Package for AC500 V3 (technology preview)
Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB
Support hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature
this can be done in the context of a piloting. In this case please contact us to set up a piloting agreement.
Welcome to the PS5608 - Pump Library Package, V1.0.0.2, which is the V3 upgrade of the V2 Pumping library (PS571)
ABB_Pump_AC500.compiled-library
ABB_PumpEco_AC500.compiled-library
Example_PumpV3_AB2xx.project
AC500_V3_Example_Pumping_Library_3ADR011194(1 en_US).pdf
Example_PumpEcoV3 with ACSDrives_AB2xx.project
Pumping Library_V3_eCo V3 with ACS Drives_ Example description 3ADR0113340 (1 en_US).pdf
The pumping library has been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
External Sleep and external Wakeup mode is not yet implemented (LIB-3196)
This Library Package is part of the Automation Builder. It can be selected as an Option during installation or any time later
using the Automation Builder Installation Manager.
The use of the Library package requires a PS5608 runtime license. Otherwise, the CPU cannot go to Run mode but will
report a notification “PLC License missing”. Please contact your PLC Support if the trial period (10 runtime days) is not
sufficient.
61
Appendix - Appendix 21: PS5620 HVAC Library Package for AC500 V3 (Technology preview) 2024-12-12
Appendix 21: PS5620 HVAC Library Package for AC500 V3 (Technology preview)
Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB
Support hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature
this can be done in the context of a piloting. In this case please contact us to set up a piloting agreement.
Welcome to the PS5620-HVAC Library Package, V1.0.0.1, which is an upgrade of V2 HVAC application library package
ABB_Ctrl_AC500.compiled-library
ABB_Hvac_AC500.compiled-library
Example_HVAC_Control_PM5650_AB2xx.project
AC500 V3 HVAC Control Example Description_3ADR011237.pdf
The HVAC and Control libraries have been tested with the following versions:
Automation Builder AB2.8.0
CPU Firmware 3.8.0
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
V1.0.0.1 2024-11: Library versions updated with AB2.8.0 (Technology Preview)
V1.0.0.0 2023-12: First version with AB2.7.0 (Technology Preview)
none
62
Appendix - Appendix 22: PS5614 DNP3 Outstation for AC500 V3 2024-12-12
Welcome to the PS5614-DNP3-O Package, V1.0.0.1 (setup version 1.0.0.285), which explains the Distributed Network Protocol
(DNP3) Outstation protocol integrated in AC500 V3 which is developed as per the DNP3 organisation standards, also known as
IEEE 1815-2012
This package allows the AC500 to act as interface to DNP3 Master(s) as Outstation. Here are the salient features,
DNP3 Outstation Level 1 to 4 is supported, accordingly relevant object groups and variations can be configured.
Data polling between Master and Outstation is possible with different Classes (0,1,2,3)
Secure Authentication Version 2 and Secure Authentication Version 5 is supported
DNP3 Outstation can be connected upto 8 Master sessions using same or different databases
DNP3 Object configurator.
Bulk Engineering of the datapoints is possible using import and export of data into CSV files at object group and database.
Buffering of data during disconnection and reporting to master after reconnection.
Archiving of data for all sessions and File transfer
Device attributes and advanced link layer settings for Session communication
Basic functionalities of the protocol has been tested for the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
Communication between master and outstation using Serial communication is not supported (LIB-2833)
DNP3 Outstation can be configured on onboard ETH1 and ETH2 ports only, using with CM5640-2ETH is not supported
(AB-24286)
If more than 1200 datapoints are linked with global array variables, Arm cortex error is shown during compilation (AB-
24666)
o Workaround: Use the DNP3 configurator to assign variables instead of mapping to global array variables.
If large set of datapoints is imported across multiple groups it can take longer time. (AB-24677)
o Workaround: Import individual group datapoints separately at each object group
User can map wrong datatype for datapoints and map it in configuration (AB-24702),
o Workaround: Map the correct datatype in variable declaration before mapping.
It may happen that Master closes and reestablish the DNP3 Communication when both Secure Authentication and
Unsolicited messages is enabled. (CPUFW-10747)
Asymmetrical certificate update in Secure authentication is not supported (LIB-3365)
Downloading a project sometimes create Log error entry EventDelete(), This entry has no negative impact on functionality
and can be ignored (CPUFW-10751)
In Binary output object group, 'Operate before select' and 'Local Mode' is not supported. (LIB-3174)
In Analog output, Event mode 'Current' is not supported, ignore the drop down selection (AB-25880)
63
Appendix - Appendix 22: PS5614 DNP3 Outstation for AC500 V3 2024-12-12
Do not drag and drop 'DNP3 Database' from one position to another in device tree (AB-25883)
This package is part of the Automation Builder. It can be selected as an Option during installation or any time later using
the Automation Builder Installation Manager.
User documentation and example projects are available in the typical folder: C:\Users\Public\Documents\Automation
Builder x.x Examples\PS5614-DNP3-O, x.x is Automation builder version
For operation a runtime license is required. Please contact your local sales support to get a runtime license
64
Appendix - Appendix 23: PS5621-Temperature Control (Technology preview) 2024-12-12
Disclaimer: Technology Previews are designed to give you a sneak peek at upcoming technologies. They are non-final versions of
our product and should NOT be taken as a measure of the fit, finish, capability, and overall quality of the final release (including user
documentation). Technology Preview features can be removed without further notice. If you use the preview, you could experience
things that go wrong, data that gets lost, and things to change. While we don't stop you using these versions in projects, we don't
recommend it if you cannot afford data loss and the usual quirks of running preview software. It will not be possible to call ABB
Support hotlines for help with Technology Preview features. If you are interested in getting support for a Technology Preview feature
this can be done in the context of a piloting. In this case please contact us to set up a piloting agreement.
Welcome to the PS5621-Temperature Control Library Package, V1.0.0.0, which is the V3 upgrade of the V2 Temperature control
library (PS564)
ABB_TemperatureControl_AC500.compiled-library
ABB_AdaptiveControl_AC500.compiled-library (internal)
AC500 V3 PS5621-TempCtrl Temperature control library System Technology 3ADR011339 (1 en_US).pdf
TemperatureControl_V3_Example Description 3ADR011338 (1 en_US).pdf
Example_TempControlV3_AB2xx.project
The pumping library has been tested with the following versions:
In no event will ABB or its representatives be liable for loss of data, profits, revenue or consequential, incidental or other damage that
may result from the use of other versions of product / software / firmware versions.
The error-free operation of this library package with other products / software / firmware versions can not be guaranteed.
Version history
When number of zones configured is greater than actual zones, TectRecipe function block generates garbage
value in csv file (LIB-3840). Workaround: Configure input NumberOfZone with correct value matching the actual
zones connected.
V2 functionalities TectLogFile and TectDataFlash are not yet supported.
This Library Package is part of the Automation Builder. It can be selected as an Option during installation or any
time later using the Automation Builder Installation Manager.
The use of the Library package requires a PS5621 runtime license. Otherwise, the CPU cannot go to Run mode
but will report a notification “PLC License missing”. Please contact your PLC Support if the trial period (10
runtime days) is not sufficient.
65