SET_EP_TICKS block
Short summary
Name |
SET_EP_TICKS |
→POU type |
|
Category |
|
logicals.standard.util.schedule |
|
Graphical interface |
|
Available since |
|
Functionality
This block sets the current, platform-dependent system ticks of the entry point for the current execution cycle of the current program. The system ticks are overwritten in the next execution cycle.
Inputs
|
Identifier |
Description |
|
Inputs: |
TICKS |
ULINT |
current system ticks |
Input EN and output ENO are available when →calling the block. See "Execution control: EN, ENO" for information on input EN and output ENO.
See:
"Blocks for safe logic" whether this block is supported for developing safety-relevant applications.
"Highlighting safe logic in the FBD-editor" for the effects when using the block as a block for safe logic .
Example for usage within ST-editor
In order to correctly use the block, you have to access the namespace of the block (e.g. by a USING namespace directive) – see "Namespaces in ST: usage" for details. The calculated values are evaluated by using the Assert block .
FUNCTION_BLOCK ExampleSetEpTicks
Using logicals.standard.util.schedule;
SET_EP_TICKS(TICKS := GET_TICKS_FROM_TIME(T#1s));
ASSERT(GET_EP_TICKS() = GET_TICKS_FROM_TIME(T#1s));
END_FUNCTION_BLOCK
When creating your application within the ST-editor, enter a call of a block by typing the text as requested by the syntax or use Content Assist.
Restriction for test framework
Do not use this block within a POU under test (see "Testing single POUs by using the test framework") because this block is not supported when a test is executed. Reason: The block is used by the test framework. The system ticks must not be adjusted by other blocks.