ILConC (ITF)¶
INTERFACE ILConC EXTENDS IActionProvider, ILevelControlled, IHasContinuousBehaviour
In order to build a function block with a LConC
behaviour, its action provider has to be decorated with this interface.
This will determine the state machine which then forces the function block to the appropriate LConC
behaviour.
See Decorators for more information about the concept.
A state chart for function blocks with LConC behaviour
- Starting:
⇒
StartAction
is running, untilxComplete
isTRUE
,xBusy
⇒TRUE
- Executing:
⇒
CyclicAction
is running untilxComplete
isTRUE
- Cleaning:
- ⇒
CleanupAction
is running. At its end theExitAction
is probably executed one time.After aReady Condition
as input, only the output stateError
(eErrorID
≠ERROR.NO_ERROR
) is possible.After aError Condition
as input, only the output stateError
(eErrorID
≠ERROR.NO_ERROR
) is possible.After aAbort Condition
as Input, only the output statesResetting
orError
(eErrorID
≠ERROR.NO_ERROR
) are possible.(xBusy
is stillTRUE
!) - Error:
xError
⇒TRUE
,eErrorID
≠ERROR.NO_ERROR
,xBusy
⇒FALSE
- Resetting:
- ⇒
ResetAction
is running, untilxComplete
isTRUE
.After that:- the outputxError
will be set toFALSE
.- The outputeErrorID
will be set toERROR.NO_ERROR
.
Methods:
StartAction, inherited from IStartActionProvider