Skip to main content

Blocking Predetection

This library was specially developed for shredder applications and ensures reliable prevention of potential drive faults.

TB_BlockingPreDetection

TB_BlockingPreDetection

The function block TB_BlockingPreDetection was specifically designed for shredder applications and ensures reliable prevention of potential drive errors, including overloads due to current or thermal energy (i²t) as well as blockages.

By continuously monitoring current and speed, this module enables proactive detection and prevention of critical operating conditions that could lead to disruptions. This helps minimize potential downtime and ensures smooth and trouble-free operation in shredder applications.

The function block provides four distinct monitoring levels:

Empfohlene Task: Cyclic / Event

Verwendete Bibliotheken: TECH_TOOLS_40bd08 oder höher

Eingänge

Marking:Data type:Data range:Description:
x_EnableBOOL-Release of the function block
x_AcknowledgeBOOL-Resets the *LimitExceeded outputs.
x_AcknowledgeByTorqueDirChangeBOOL-Enables automatic resetting of the *LimitExceeded outputs when the direction of rotation changes.
x_NoDetectionAccBOOL-If this input is set to TRUE, the working or blocking detection is not active in the acceleration phase.
x_NoDetectionDecBOOL-If this input is set to TRUE, the working or blocking detection is not active in the deceleration phase.
x_DriveState_InVelBOOL-Indicates whether the drive is in the speed state.
x_DriveState_InAccBOOL-Indicates whether the drive is in the acceleration state.
x_DriveState_InDecBOOL-Indicates whether the drive is in the deceleration state.
us_MaxNrBlockingsUSINT1 .. 255Maximum number of blockings allowed before a blocking error x_BlockingMaxCntReached = TRUE occurs.
t_BlockingCountDownTimeTIMET > 0sTime after which the blockage counter is counted down, provided that the current motor current is below the limit values.
t_BlockingFreeRunTimeTIMET > 0sTime period that the drive must run freely to reset the output x_BlockingMaxCntReached.
t_WorkingCurrentTimeoutTIME0sTime period after which a working current exceeded is detected.
t_BlockingCurrentTimeoutTIMET > 0sTime period after which a blovking current exceeded is detected.
ui_WorkingCurrentThresholdUINT0%Sets the working current limit in percent of the nominal motor current.
ui_WorkingCurrentHysteresisUINT1%Sets the Hysteresis of the working current limit in percentage.
ui_BlockingCurrentThresholdUINT0% ui_WorkingCurrentThresholdSets the blocking current limit in percent of the nominal motor current
ui_BlockingCurrentHysteresisUINT1Sets the Hysteresis of the blocking current limit in percent.
ui_BlockingVelocityDeviationUINT1%Sets the velocity deviation from the setpoint r_SetpointVelocity in percent at which velocity monitoring is triggered.
r_ActualCurrentREAL-Contains the actual motor current in percent.
r_ActualVelocityREAL-Contains the actual motor speed in percent, related to the nominal motor current.
r_SetpointVelocityREALv >= 1%Contains the setpoint speed of the motor in percent, related to the nominal motor current.
r_SetpointAccelerationREALa >= 1%Contains the setpoint acceleration of the motor in milliseconds.

Ausgänge

Marking:Data type:Description:
x_WorkingLimitExceededBOOLIndicates whether the maximum working current limit has been exceeded.
x_WorkingLimitReachedBOOLIndicates whether the working current limit has been reached and the timer started.
x_BlockingLimitExceededBOOLIndicates whether the maximum blocking current limit has been exceeded.
x_BlockingLimitReachedBOOLIndicates whether the blocking current limit has been reached and the timer started.
x_BlockingMaxCntReachedBOOLIndicates whether the maximum number of blockings has been reached.
us_BlockingCounterUSINTDisplays the number of detected blockages.
x_ActiveBOOLIndicates whether the function block is active.
x_BusyBOOLIndicates whether blockage detection is active, depending on the input configuration and drive status.
x_WarningBOOLIndicates whether a warning has been detected and a valid w_WarningID is available.
w_WarningIDWORDNumber to identify the warning:
1 - MaxNrBlockings must be greater than 0.
2 - BlockingCountDownTime must be greater than 0s
3 - BlockingFreeRunTime must be greater than 0s
4 - WorkingCurrentTimeout must be greater than 0s
5 - BlockingCurrentTimeout must be greater than 0s
6 - WorkingCurrentTimeout must be greater than BlockingCurrentTimeout
7 - WorkingCurrentThreshold must be greater than 0%.
8 - BlockingCurrentThreshold must be greater than 0%.
9 - WorkingCurrentThreshold must be smaller than BlockingCurrentThreshold
10 - BlockingVelocityDeviation must be greater than or equal to 1% and less than or equal to 95%.
11 - WorkingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
12 - BlockingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
13 - SetpointVelocity must be greater than or equal to 1%.
14 - SetpointAcceleration must be greater than or equal to 1%.
15 - BlockingCurrentHysteresis disabled, SetpointVelocity or SetpointAcceleration invalid.
x_ErrorBOOLIndicates whether an error has occurred and w_ErrorID is valid.
w_ErrorIDWORDNumber to identify the error that has occurred:
1 - MaxNrBlockings must be greater than 0.
2 - BlockingCountDownTime must be greater than 0s
3 - BlockingFreeRunTime must be greater than 0s
4 - WorkingCurrentTimeout must be greater than 0s
5 - BlockingCurrentTimeout must be greater than 0s
6 - WorkingCurrentTimeout must be greater than BlockingCurrentTimeout
7 - WorkingCurrentThreshold must be greater than 0%.
8 - BlockingCurrentThreshold must be greater than 0%.
9 - WorkingCurrentThreshold must be smaller than BlockingCurrentThreshold
10 - BlockingVelocityDeviation must be greater than or equal to 1% and less than or equal to 95%.
11 - WorkingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
12 - BlockingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
Representation in FBD

TB_BlockingPreDetection

TB_BlockingPreDetection

The function block TB_BlockingPreDetection was specifically designed for shredder applications and ensures reliable prevention of potential drive errors, including overloads due to current or thermal energy (i²t) as well as blockages.

By continuously monitoring current and speed, this module enables proactive detection and prevention of critical operating conditions that could lead to disruptions. This helps minimize potential downtime and ensures smooth and trouble-free operation in shredder applications.

The function block provides four distinct monitoring levels:

Empfohlene Task: Cyclic / Event

Verwendete Bibliotheken: TECH_TOOLS_40bd08 oder höher

Eingänge

Marking:Data type:Data range:Description:
x_EnableBOOL-Release of the function block
x_AcknowledgeBOOL-Resets the *LimitExceeded outputs.
x_AcknowledgeByTorqueDirChangeBOOL-Enables automatic resetting of the *LimitExceeded outputs when the direction of rotation changes.
x_NoDetectionAccBOOL-If this input is set to TRUE, the working or blocking detection is not active in the acceleration phase.
x_NoDetectionDecBOOL-If this input is set to TRUE, the working or blocking detection is not active in the deceleration phase.
x_DriveState_InVelBOOL-Indicates whether the drive is in the speed state.
x_DriveState_InAccBOOL-Indicates whether the drive is in the acceleration state.
x_DriveState_InDecBOOL-Indicates whether the drive is in the deceleration state.
us_MaxNrBlockingsUSINT1 .. 255Maximum number of blockings allowed before a blocking error x_BlockingMaxCntReached = TRUE occurs.
t_BlockingCountDownTimeTIMET > 0sTime after which the blockage counter is counted down, provided that the current motor current is below the limit values.
t_BlockingFreeRunTimeTIMET > 0sTime period that the drive must run freely to reset the output x_BlockingMaxCntReached.
t_WorkingCurrentTimeoutTIME0sTime period after which a working current exceeded is detected.
t_BlockingCurrentTimeoutTIMET > 0sTime period after which a blovking current exceeded is detected.
ui_WorkingCurrentThresholdUINT0%Sets the working current limit in percent of the nominal motor current.
ui_WorkingCurrentHysteresisUINT1%Sets the Hysteresis of the working current limit in percentage.
ui_BlockingCurrentThresholdUINT0% ui_WorkingCurrentThresholdSets the blocking current limit in percent of the nominal motor current
ui_BlockingCurrentHysteresisUINT1Sets the Hysteresis of the blocking current limit in percent.
ui_BlockingVelocityDeviationUINT1%Sets the velocity deviation from the setpoint r_SetpointVelocity in percent at which velocity monitoring is triggered.
r_ActualCurrentREAL-Contains the actual motor current in percent.
r_ActualVelocityREAL-Contains the actual motor speed in percent, related to the nominal motor current.
r_SetpointVelocityREALv >= 1%Contains the setpoint speed of the motor in percent, related to the nominal motor current.
r_SetpointAccelerationREALa >= 1%Contains the setpoint acceleration of the motor in milliseconds.

Ausgänge

Marking:Data type:Description:
x_WorkingLimitExceededBOOLIndicates whether the maximum working current limit has been exceeded.
x_WorkingLimitReachedBOOLIndicates whether the working current limit has been reached and the timer started.
x_BlockingLimitExceededBOOLIndicates whether the maximum blocking current limit has been exceeded.
x_BlockingLimitReachedBOOLIndicates whether the blocking current limit has been reached and the timer started.
x_BlockingMaxCntReachedBOOLIndicates whether the maximum number of blockings has been reached.
us_BlockingCounterUSINTDisplays the number of detected blockages.
x_ActiveBOOLIndicates whether the function block is active.
x_BusyBOOLIndicates whether blockage detection is active, depending on the input configuration and drive status.
x_WarningBOOLIndicates whether a warning has been detected and a valid w_WarningID is available.
w_WarningIDWORDNumber to identify the warning:
1 - MaxNrBlockings must be greater than 0.
2 - BlockingCountDownTime must be greater than 0s
3 - BlockingFreeRunTime must be greater than 0s
4 - WorkingCurrentTimeout must be greater than 0s
5 - BlockingCurrentTimeout must be greater than 0s
6 - WorkingCurrentTimeout must be greater than BlockingCurrentTimeout
7 - WorkingCurrentThreshold must be greater than 0%.
8 - BlockingCurrentThreshold must be greater than 0%.
9 - WorkingCurrentThreshold must be smaller than BlockingCurrentThreshold
10 - BlockingVelocityDeviation must be greater than or equal to 1% and less than or equal to 95%.
11 - WorkingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
12 - BlockingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
13 - SetpointVelocity must be greater than or equal to 1%.
14 - SetpointAcceleration must be greater than or equal to 1%.
15 - BlockingCurrentHysteresis disabled, SetpointVelocity or SetpointAcceleration invalid.
x_ErrorBOOLIndicates whether an error has occurred and w_ErrorID is valid.
w_ErrorIDWORDNumber to identify the error that has occurred:
1 - MaxNrBlockings must be greater than 0.
2 - BlockingCountDownTime must be greater than 0s
3 - BlockingFreeRunTime must be greater than 0s
4 - WorkingCurrentTimeout must be greater than 0s
5 - BlockingCurrentTimeout must be greater than 0s
6 - WorkingCurrentTimeout must be greater than BlockingCurrentTimeout
7 - WorkingCurrentThreshold must be greater than 0%.
8 - BlockingCurrentThreshold must be greater than 0%.
9 - WorkingCurrentThreshold must be smaller than BlockingCurrentThreshold
10 - BlockingVelocityDeviation must be greater than or equal to 1% and less than or equal to 95%.
11 - WorkingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
12 - BlockingCurrentHysteresis must be greater than or equal to 1% and less than or equal to 10%.
Representation in FBD