BehaviourModel.AbortModel (METH) ¶ METHOD AbortModel : ERROR InOut: Scope Name Type Return AbortModel ERROR Input xCommit BOOL
BehaviourModel.ResetModel (METH) ¶ METHOD ResetModel : ERROR InOut: Scope Name Type Return ResetModel ERROR Input xCommit BOOL
IBehaviourModel ¶ GetModelState (Method) ModelTimeOut (Property) ResetModel (Method) StartModel (Method)
ETrigTo._Execute (METH) ¶ METHOD PROTECTED _Execute InOut: Scope Name Type Output eErrorID ERROR
Interfaces ¶ IETrig (Interface) IETrigA (Interface) IETrigATl (Interface) IETrigATlTo (Interface) IETrigATo (Interface) IETrigTl (Interface) IETrigTlTo (Interface) IETrigTo (Interface)
IETrig (ITF) ¶ INTERFACE IETrig EXTENDS IActionProvider , IEdgeTriggered In order to build a function block with an ETrig 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 ETrig behaviour. See Decorators for more information about the concept. A state chart for function blocks with ETrig behaviour Starting : ⇒ StartAction is running, until xComplete is TRUE , xBusy ⇒ TRUE At its beginning the SampleAction is probably executed one time. Executing : ⇒ CyclicAction is running until xComplete is TRUE Cleaning : ⇒ CleanupAction is running. At its end the ExitAction is probably executed one time. After a Ready Condition as input, only the output states Done ( xComplete is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. After a Error Condition as input, only the output state Error ( eErrorID ≠ ERROR.NO_ERROR ) is possible. Done : xDone ⇒ TRUE , xBusy ⇒ FALSE Error : xError ⇒ TRUE , eErrorID ≠ ERROR.NO_ERROR , xBusy ⇒ FALSE Resetting : ⇒ ResetAction is running, until xComplete is TRUE . After that: - the outputs xDone and xError will be set to FALSE . - The output eErrorID will be set to ERROR.NO_ERROR . Methods: StartAction , inherited from IStartActionProvider
IETrigA (ITF) ¶ INTERFACE IETrigA EXTENDS IETrig , IAbortable In order to build a function block with an ETrigA 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 ETrigA behaviour. See Decorators for more information about the concept. A state chart for function blocks with ETrigA behaviour Starting : ⇒ StartAction is running, until xComplete is TRUE , xBusy ⇒ TRUE At its beginning the SampleAction is probably executed one time. Executing : ⇒ CyclicAction is running until xComplete is TRUE Cleaning : ⇒ CleanupAction is running. At its end the ExitAction is probably executed one time. After a Ready Condition as input, only the output states Done ( xComplete is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. After a Error Condition as input, only the output state Error ( eErrorID ≠ ERROR.NO_ERROR ) is possible. After a Abort Condition as Input, only the output states Aborted ( xAbort is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. ( xBusy is still TRUE !) Done : xDone ⇒ TRUE , xBusy ⇒ FALSE Error : xError ⇒ TRUE , eErrorID ≠ ERROR.NO_ERROR , xBusy ⇒ FALSE Aborted : xAborted ⇒ TRUE , xBusy ⇒ FALSE Resetting : ⇒ ResetAction is running, until xComplete is TRUE . After that: - the outputs xDone , xError and xAborted will be set to FALSE . - The output eErrorID will be set to ERROR.NO_ERROR . Methods: StartAction , inherited from IStartActionProvider
IETrigATl (ITF) ¶ INTERFACE IETrigATl EXTENDS IETrigA , ITimeLimited , ITimingControlled In order to build a function block with an ETrigATl 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 ETrigATl behaviour. See Decorators for more information about the concept. A state chart for function blocks with ETrigATl behaviour Starting : ⇒ StartAction is running, until xComplete is TRUE , xBusy ⇒ TRUE At its beginning the SampleAction is probably executed one time. Executing : ⇒ CyclicAction is running until xComplete is TRUE Cleaning : ⇒ CleanupAction is running. At its end the ExitAction is probably executed one time. After a Ready Condition as input, only the output states Done ( xComplete is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. After a Error Condition as input, only the output state Error ( eErrorID ≠ ERROR.NO_ERROR ) is possible. After a Abort Condition as Input, only the output states Aborted ( xAbort is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. ( xBusy is still TRUE !) Done : xDone ⇒ TRUE , xBusy ⇒ FALSE Error : xError ⇒ TRUE , eErrorID ≠ ERROR.NO_ERROR , xBusy ⇒ FALSE Aborted : xAborted ⇒ TRUE , xBusy ⇒ FALSE Resetting : ⇒ ResetAction is running, until xComplete is TRUE . After that: - the outputs xDone , xError and xAborted will be set to FALSE . - The output eErrorID will be set to ERROR.NO_ERROR . Methods: StartAction , inherited from IStartActionProvider
IETrigATlTo (ITF) ¶ INTERFACE IETrigATlTo EXTENDS IETrigATl , ITimeOutConstraint In order to build a function block with an ETrigATlTo 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 ETrigATlTo behaviour. See Decorators for more information about the concept. A state chart for function blocks with ETrigATlTo behaviour Starting : ⇒ StartAction is running, until xComplete is TRUE , xBusy ⇒ TRUE At its beginning the SampleAction is probably executed one time. Executing : ⇒ CyclicAction is running until xComplete is TRUE Cleaning : ⇒ CleanupAction is running. At its end the ExitAction is probably executed one time. After a Ready Condition as input, only the output states Done ( xComplete is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. After a Error Condition as input, only the output state Error ( eErrorID ≠ ERROR.NO_ERROR ) is possible. After a Abort Condition as Input, only the output states Aborted ( xAbort is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. ( xBusy is still TRUE !) Done : xDone ⇒ TRUE , xBusy ⇒ FALSE Error : xError ⇒ TRUE , eErrorID ≠ ERROR.NO_ERROR , xBusy ⇒ FALSE Aborted : xAborted ⇒ TRUE , xBusy ⇒ FALSE Resetting : ⇒ ResetAction is running, until xComplete is TRUE . After that: - the outputs xDone , xError and xAborted will be set to FALSE . - The output eErrorID will be set to ERROR.NO_ERROR . Methods: StartAction , inherited from IStartActionProvider
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, until xComplete is TRUE , xBusy ⇒ TRUE At its beginning the SampleAction is probably executed one time. Executing : ⇒ CyclicAction is running until xComplete is TRUE Cleaning : ⇒ CleanupAction is running. At its end the ExitAction is probably executed one time. After a Ready Condition as input, only the output states Done ( xComplete is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. After a Error Condition as input, only the output state Error ( eErrorID ≠ ERROR.NO_ERROR ) is possible. After a Abort Condition as Input, only the output states Aborted ( xAbort is TRUE ) or Error ( eErrorID ≠ ERROR.NO_ERROR ) are possible. ( xBusy is still TRUE !) Done : xDone ⇒ TRUE , xBusy ⇒ FALSE Error : xError ⇒ TRUE , eErrorID ≠ ERROR.NO_ERROR , xBusy ⇒ FALSE Aborted : xAborted ⇒ TRUE , xBusy ⇒ FALSE Resetting : ⇒ ResetAction is running, until xComplete is TRUE . After that: - the outputs xDone , xError and xAborted will be set to FALSE . - The output eErrorID will be set to ERROR.NO_ERROR . Methods: StartAction , inherited from IStartActionProvider