Visualization Of course the parameters can be modified. But: VISU_INPUT_TASK always should be processed before VISU_TASK in order to guarantee a useful interaction of user inputs and update of the visualization. The task calling the main program (e.g. PLC_PRG), should at least be processed as often as VISU_INPUT_TASK, ideally even with a higher priority, but it also could be added directly to VISU_INPUT_TASK Case B: Deactivate task generation is switched off: Use VISU_INPUT_TASK is switched off: Only task VISU_TASK will be generated automatically, but in this case will include the functionality of VISU_INPUT_TASK.
The implicit program POU MAINTARGETVISU_ PAINT_CODE in this case additionally will include the functionality of program MAINTTARGETVISU_INPUT_CODE. This configuration is intended for systems which do not allow multi-tasking. Disadvantageously no differentiated cycle times can be configured for the processing of user inputs and the repainting of the visualization elements, see above. The Target visualization is not controlled by automatically created tasks; The implicitly available POUs MAINTARGETVISU_PAINT_CODE and MAINTTARGETVISU_INPUT_CODE can be called by the application program resp. can be appended to any task: Case C: Deactivate task generation is activated:
Use VISU_INPUT_TASK is activated: Both implicit POUs are available and can be called individually resp. can be appended to any task. (Referring to this regard the hints in (Case A). Example for calls of the Target-Visulization POUs in the application program: PROGRAM visu_control VAR n: INT; END_VAR n:=n+1; IF (n MOD 4) =0 THEN MAINTARGETVISU_PAINT_CODE(); END_IF; MAINTARGETVISU_INPUT_CODE(); Here in program visu_control the POU which processes the user inputs is only called after each fourth call of the repainting POU - thus reducing the danger of getting disturbed the repainting by another user input.
When creating the application program, absolutely pay attention to reduce this danger of incorrect display ! TX1200 327 Version: 1.3