IETrigATo (ITF)¶
INTERFACE IETrigATo EXTENDS IETrigA, ITimeOutConstraint, ITimingControlled
In order to build a function block with an ETrigATo
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 ETrigATo
behaviour.
See Decorators for more information about the concept.
A state chart for function blocks with ETrigATo behaviour

- Starting:
- ⇒
StartAction
is running, untilxComplete
isTRUE
,xBusy
⇒TRUE
At its beginning theSampleAction
is probably executed one time. - 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 statesDone
(xComplete
isTRUE
) orError
(eErrorID
≠ERROR.NO_ERROR
) are possible.After aError Condition
as input, only the output stateError
(eErrorID
≠ERROR.NO_ERROR
) is possible.After aAbort Condition
as Input, only the output statesAborted
(xAbort
isTRUE
) orError
(eErrorID
≠ERROR.NO_ERROR
) are possible.(xBusy
is stillTRUE
!) - Done:
xDone
⇒TRUE
,xBusy
⇒FALSE
- Error:
xError
⇒TRUE
,eErrorID
≠ERROR.NO_ERROR
,xBusy
⇒FALSE
- Aborted:
xAborted
⇒TRUE
,xBusy
⇒FALSE
- Resetting:
- ⇒
ResetAction
is running, untilxComplete
isTRUE
.After that:- the outputsxDone
,xError
andxAborted
will be set toFALSE
.- The outputeErrorID
will be set toERROR.NO_ERROR
.
Methods:
StartAction, inherited from IStartActionProvider