ItpIsEStop

Via bEStop, the function block ItpIsEStop provides information as to whether an EStop command was triggered. If bEStop is TRUE, then an EStop was initiated (e.g. ItpEStop). The flag does not provide information as to whether the axes have already stopped or are still on the deceleration ramp.

After the execution of ItpStepOnAfterEStop, ItpIsEStop will once again return FALSE.

	Outdated version The sole purpose of the function block is to ensure compatibility with existing projects. For new projects please use the function block ItpIsEStopEx.

Inputs

VAR_INPUT
    bExecute       : BOOL;
    nGrpId         : UDINT
    tTimeOut       : TIME;
END_VAR

Name	Type	Description
bExecute	BOOL	The command is triggered by a rising edge at this input.
nGrpId	UDINT	Group ID
tTimeOut	TIME	ADS Timeout-Delay

Outputs

VAR_OUTPUT
    bBusy          : BOOL;
    bEStop         : BOOL;
    bErr           : BOOL;
    nErrId         : UDINT;
END_VAR

Name	Type	Description
bBusy	BOOL	This output remains TRUE until the function block has executed a command, but at the longest for the duration supplied to the 'Timeout' input. While Busy = TRUE, no new command will be accepted at the inputs. Please note that it is not the execution of the service but its acceptance whose time is monitored.
bEStop	BOOL	TRUE: EStop command was executed. FALSE: No EStop present.
bErr	BOOL	This output is switched to TRUE as soon as an error occurs during the execution of a command. The command-specific error code is contained in 'nErrId'. Is reset to FALSE by the execution of a command at the inputs.
nErrId	UDINT	Contains the command-specific error code of the most recently executed command. Is reset to 0 by the execution of a command at the inputs. The error numbers in ErrId can be looked up in the ADS error documentation or in the NC error documentation (error codes above 0x4000).

Requirements

Development environment	Target platform	PLC libraries to be linked
TwinCAT v3.1.0	PC or CX (x86 or x64)	Tc2_NCI