Behavior of the logical outputs if they are written in different tasks.

Search FAQs

You are currently viewing the content available in Vietnam. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.

Goals and Symptoms

Behavior of the logical outputs if they are written in different tasks.

Causes and Fixes

If local logical outputs are written in different tasks of the LMC (Auxiliary task, Motion task or event task) inconsistencies between the programmed value and the physical value of the output can occur.
- This behavior appears if the same output is written in different tasks but also if 2 different outputs are written in different tasks.
- This behavior is common to all the platforms running with Codesys and is not regarded as misbehavior.
- It cannot be modified
- Solution: use LMC_ExplicitOutput FB if you need to write logical outputs from different tasks of the LMC.

Attachments

(Removed File URL: 198428_B832/Behaviour_of_the_logical_outputs_V1_.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/ef76aab6e13c647cc12575ad005297d5/fl_block_5/0.64E?OpenElement&FieldElemFormat=gif)

Legacy KB System (APS) Data: RESL198428 V1.0, Originally authored by MaPr on 05/05/2009, Last Edited by MaPr on 05/05/2009
Related ranges: Lexium Controller