dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorDrive application programming (IEC 61131-3)dl-breadcrumb-item__separatorPractical examples and tips
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Practical examples and tipsdl-permalink__symbolPermalink

Solving communication problems

Follow the instructions below when the scan network does not find any drives.

  1. Check the communication settings.

  2. In Windows “Computer Management  Device Manager”, check that the communication port is correctly installed.

  3. If the USB Serial Port (COMX) is not displayed under Device Manager, check that the corresponding USB/communication port driver is installed.

  4. Select Ctrl + shift + esc → “Processes ” to check that the OPC server (DriveDA.exe) has started in “Windows Task Manager”.

  5. Check that the Drive Composer pro (Drive OPC) finds the connection to the drive.

    You must allow Automation Builder to share communication with Drive Composer pro.

For details on how to allow Automation Builder to share communication with Drive Composer pro search in the help.

⮫ Drive Composer pro integration

Follow the instructions below when the communication fails between Automation Builder/Drive Composer pro and drive.

  • Check that the control panel has the latest firmware version

  • Check the driver data

The next panel driver version is not known. For version details, refer the corresponding ACS880 drive software release notes or contact your ABB representative.

Solving other problems

How to prevent unauthorized access to an application that is running in the drive?

A compiled project as well as the downloaded source code can be password protected. You can make a backup copy of the protected application. The backup copy is encrypted and you need a password for downloading or executing the copied application. The IEC function libraries and projects can be protected as well by means of Automation Builder.

  • What to do when stack overflow fault 6487 occurs?

    • If the stack overflow fault 6487 occurs, then the number of the local variables inside a function is too large. Unfortunately, the limit of the local variables are relatively small. The stack usage is high especially if there are, for example, division operands inside the EXPT function.

    • Also if the division function divider is zero (an exceptional case), the stack usage is high.

Do not make large functions. Try to make a compact function with a limited number of variables (40 REAL). If the function is too large, change some of the local variables to global variables (use, for example, multiple global variable lists GVL to group variables by functions). Consider to use function blocks or program modules instead of functions.

How to optimize the memory usage of the drive application? The code memory of the application is running out. How to optimize the program?

The drive application programming environment has relatively limited memory and execution capacity. There are a couple of tips to minimize the program code:

  • Use functions as much as possible.

If there are many variables inside the function, the risk of stack overflow increases.

  • Try to design the application so that you do not need to create many instances of large function blocks. Instead of function blocks use programs or functions.

  • Use “DriveInterface” to access drive parameters instead of the parameter read/write functions.

How to solve the problem causing error message “Creating boot application failed: Adding Application Parameters & Groups to UFF generator: XmlDeserializationFailed”?

The problem is related to “Application” parameters and events module.

  • Check that all “Value pointer”- , “Bit pointer”- and “Plain value list” type of parameters have the correct “Selection Lists”.

  • Check that the Bit list (16 bit) parameters do not have same Bit names (English) multiple times (for example, text Bit_Handle_0 occurs twice).

  • Check the tool message box for details.