Introduction

An action section can be created for every action. This is a section which contains the logic of the action and it is automatically linked with the action.

Name of the Action Section

The name of the action section is always identical to the assigned action.

Programming Languages

FBD, LD, IL and ST are possible as programming languages for action sections.

Properties of Action Sections

Action sections have the following properties:

  • Action sections can have any amount of outputs.

  • Subroutine calls are only possible in action sections when Multitoken operation is enabled.

    Note: The called subroutines are not affected by the controller of the sequence string, i.e.

    • the qualifier assigned to the called action section does not affect the subroutine

    • the subroutine also remains active when the called step is deactivated

  • No diagnosis functions, diagnosis function blocks or diagnosis procedures may be used in action sections.

  • Action sections can have any amount of networks.

  • Action sections belong to the SFC section in which they were defined and can be assigned any number of actions within this SFC section (including all of their macro sections).

  • Action sections which are assigned an qualifier with duration, can only be activated one time.

  • Action sections belong to the SFC section that they were defined in. If the respective SFC section is deleted then all action sections of this SFC section are also deleted automatically.

  • Action sections can be called exclusively from actions.

SFCACTION_STATE Variable

When final scan logic is activated, every action section is implicitly allocated a variable of data type SFCACTION_STATE. This variable has the name of the allocated action section. The elements for this data structure are read only.

You can see the SFCACTION_STATE variables in the Data Editor . The Comment for a SFCACTION_STATE variable is the comment entered as a property of the action section itself. For details, refer to chapter Assigning actions to a step.

The data structure cannot be used in variable declarations. Therefore, accessing the entire data structure (for example, as FFB parameter) is not possible.

NOTE: Usage of a SFCACTION_STATE variable in parallel branches is limited to once.

The scope of this variable to which it belongs, is the same as the SFC section where the action section has been created.

Structure of the DDT:

Element Name

Data type

Description

ActionName.t

TIME

Time elapsed since the action section was made active

ActionName.q

BOOL

1: Action section active

0: Action section inactive