• Home
• Function/Function Block Reference
• PLCnext Controller Function Blocks
• Timer
• TP_R / TP_R_LTIME

TP_R / TP_R_LTIME

Type	Function block
Description	The TP_R / TP_R_LTIME function blocks generate a pulse with a configurable pulse duration. They operate as retain timers, i.e., the elapsed time since start of the timer is retained internally when switching the controller off. After switching the controller on again and executing a warm start, the timer continues counting from the point at which it was stopped. When the IN input switches from FALSE to TRUE, the Q output is set to TRUE and remains set until the delay time specified at the PT input has elapsed. The Q output remains unchanged, if the IN input switches from TRUE to FALSE before the specified delay time has elapsed or if the input becomes TRUE for a second time before the delay time has elapsed. The PT input specifies the time after which Q is switched from TRUE to FALSE. The ET output indicates the already expired time.
Notes	The input IN and the output Q can be negated. Note: The negation of formal parameters is not supported in safety-related code (SNOLD). Function blocks have to be instantiated. The instance name of the function block has to be declared in the 'Variables' table of the POU where the FB is going to be used. The instance name must be unique within the POU.
Parameters	Inputs IN Data type: BOOL Description: If a rising edge is detected, a pulse is generated. PT Data type: TP_R: TIME TP_R_LTIME: LTIME Description: Preset time interval for the pulse. The time value must be positive. Outputs Q Data type: BOOL Description: TRUE if IN = TRUE and ET < PT. FALSE if IN = FALSE and ET >= PT. ET Data type: TIME Description: Elapsed time interval (retentive). The current elapsed time is retained internally when switching the controller off. After switching the controller on again and executing a warm start, the timer continues counting from the point at which it was stopped.
Timing Diagram	Timing diagram 0 The IN input is FALSE. As a result, also Q is set to FALSE. 1 IN switches from FALSE to TRUE. Q is set to TRUE immediately and the measurement of the elapsed time is started. 2 Power is switched off. The timer stops. The elapsed time since start of the timer is retained. 3 Power is switched on again and a warm start is executed. The timer continues counting from the point at which it was stopped. 4 The delay time PT has elapsed (ET = PT), Q is set to FALSE. 5 IN switches from TRUE to FALSE. The timer is reset (ET = 0). Q remains FALSE. 6 IN switches from FALSE to TRUE. Q is set to TRUE immediately and the measurement of the elapsed time is started. Before the delay time PT has elapsed, IN switches repeatedly from TRUE to FALSE and vice versa. Q remains TRUE as the delay time PT has not expired yet. 7 The delay time PT has elapsed (ET = PT), Q is set to FALSE.
Algorithm	Algorithm The algorithm is based on incrementing time distances between two invocations of the function block. The function block is capable to calculate the elapsed time after a warm restart beginning from the last invocation. The time distance is measured by using an internal system tick counter (contains the amount of time in milliseconds). The preset timer value (PT) is limited at 2,147,483,647 milliseconds for the *_R function block (max range of DINT data type) and 9,223,372,036,854,775,807 for the *_R_LTIME function block (max. range of the LINT data type). Problem of lost invocation after warm restart Because the algorithm is based on a non retentive internal system tick counter, it is important to take notice of the problem, which we call 'lost invocation'. The figure below describes the behavior of the function block before and after a warm start is forced. After the parameter IN raised to TRUE, the next invocation detects the raising edge state of IN. At this point, the calculation begins with ET (elapsed time) := 0. After a warm restart, the next invocation detects the changed state and normalizes the internal start value by subtracting the current system counter with the internal retentive elapsed counter. That is why the time distance to the previous invocation is 0. Related to the 'real' elapsed time there is a delay dependent from the duration between successive invocations of the function block. That means, after a warm start the duration of the function block is at worst one invocation distance slower than a function block where no warm restart occurs. Hot start behavior After a hot start is performed , it is important to know that the timer calculates the elapsed time including the duration of the stop state. A hot start is forced, if, for example, the PLC is continued from a breakpoint. During the online debug, it could happen that some timer expire if the PLC halts on breakpoints.