Function Blocks; Program Execution - ABB ACSM1 Firmware Manual

Function blocks

The application program uses three types of function blocks: firmware function
blocks, standard function blocks and technology function blocks.
Firmware function blocks
Most of the firmware functions are represented as function blocks in the DriveSPC
tool. Firmware function blocks are part of the drive control firmware, and used as an
interface between the application and firmware programs. Drive parameters in
groups 10...99 are used as function block inputs and parameters in groups 1...9 as
function block outputs. Firmware function blocks are presented in chapter
Parameters and firmware
Standard function blocks (library)
Standard function blocks (e.g. ADD, AND) are used to create an executable
application program. Blocks are based on the IEC-61131 standard. Standard
function blocks are presented in chapter
Standard function block library is always included in the drive delivery.
Technology function blocks
Several technology function block libraries are available for different types of
applications. One technology library can be used at a time. Technology blocks are
used in a similar way as the standard blocks.

Program execution

The application program is loaded to the permanent memory (non-volatile) of the
memory unit (JMU). The execution of the downloaded program starts after the next
reset of the drive control board. The program is executed in real time on the same
Central Processing Unit (CPU of the drive control board) as the drive firmware. The
program is executed with two cyclical tasks. The time level for these tasks can be
defined by the programmer (> 1ms).
Note: Because the firmware and application programs use the same CPU, the
programmer must ensure that the drive CPU is not overloaded. See parameter
CPU USAGE.
blocks.
Standard function blocks.
Drive programming using PC tools
31
1.21