Skip to Content

Changes for page 01 Program execution

Last modified by Leo Wei on 2024/12/24 22:42
From version 10.1
edited by Stone Wu
on 2022/07/28 16:43
Change comment: Attachment moved from xwiki:PLC Editor2.2\.1 LX5V user manual.WebHome.
To version 6.1
edited by Leo Wei
on 2022/07/13 20:54
Change comment: Renamed from xwiki:PLC Editor2.1 User manual.2\.1 LX5V user manual.01.WebHome

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -01 Program execution
1 +01 Execution of the program
Parent
... ... @@ -1,1 +1,1 @@
1 -PLC Editor2.WebHome
1 +PLC Editor2.1 User manual.2\.1 LX5V user manual.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Stone
1 +XWiki.admin
Content
... ... @@ -1,4 +1,4 @@
1 -= Scan structure =
1 += **Scan structure** =
2 2  
3 3  The scan configuration of the CPU module is as follows.
4 4  
... ... @@ -5,7 +5,7 @@
5 5  (% style="text-align:center" %)
6 6  [[image:1-1.png||height="455" width="700" class="img-thumbnail"]]
7 7  
8 -== Initialization ==
8 +== **Initialization** ==
9 9  
10 10  The initialization based on the status of the CPU module is as follows.
11 11  
... ... @@ -20,7 +20,7 @@
20 20  |Device initialization|√|×|√
21 21  |Error clear|√|×|√
22 22  
23 -== Input and output point refresh ==
23 +== **Input and output point refresh** ==
24 24  
25 25  Perform the following before starting program calculation.      
26 26  
... ... @@ -34,11 +34,11 @@
34 34  
35 35  When performing a constant scan, the I/O refresh is performed after the waiting time of the constant scan.
36 36  
37 -== Operation of the program ==
37 +== **Operation of the program** ==
38 38  
39 39  According to the program setting, the execution starts from step 0 of each program to the END instruction. This program is called the main program.
40 40  
41 -== END processing ==
41 +== **END processing** ==
42 42  
43 43  Perform the following processing.
44 44  
... ... @@ -47,7 +47,7 @@
47 47  * Communication processing
48 48  * Setting the value of special relay/special register (when the setting timing is END processing)
49 49  
50 -= Scan time =
50 += **Scan time** =
51 51  
52 52  The CPU module repeats the following processing, and the scan time is the total of the following processing and execution time.
53 53  
... ... @@ -56,7 +56,7 @@
56 56  
57 57  The initial scan time indicates the time including this processing.      
58 58  
59 -== Initial scan time ==
59 +== **Initial scan time** ==
60 60  
61 61  It is the first scan time of the CPU module in RUN.
62 62  
... ... @@ -64,7 +64,7 @@
64 64  
65 65  The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
66 66  
67 -= The flow of each procedure =
67 += **The flow of each procedure** =
68 68  
69 69  When the CPU module changes to the RUN state, the programs are executed in sequence according to the program execution type and execution sequence settings.
70 70  
... ... @@ -79,9 +79,9 @@
79 79  
80 80  When executing instructions that can be completed with multiple cycles (such as OUT T, RAMP, RS, etc.), they should be programmed in the scan program. If it is used in event execution type programs and mid-stage execution type programs, these instructions may not be executed in multiple scan cycles, causing actual results to be different from the ideal results. Therefore, unless events, interrupts and subroutines can be executed in each scan cycle. It is not recommended to use multi-cycle execution instructions in other situations.
81 81  
82 -= Types of program execution =
82 += **Types of program execution** =
83 83  
84 -== Scan execution program ==
84 +== **Scan execution program** ==
85 85  
86 86  Each scan is executed only once from the next scan of the initial execution type program.
87 87  
... ... @@ -106,7 +106,7 @@
106 106  (% style="text-align:center" %)
107 107  [[image:1-6.png||class="img-thumbnail"]]
108 108  
109 -== Event execution program ==
109 +== **Event execution program** ==
110 110  
111 111  It uses the event specified by the user as a condition to trigger the program to start execution.
112 112  
... ... @@ -208,7 +208,7 @@
208 208  
209 209  When "ON event" or "TIME event" is specified, if "Clear or not" is set to "Clear", the event program will not be executed in one scan cycle, and all the internal outputs (Y) and current value of timer (T) will all be cleared (except for the cumulative type and subroutine type T). If the time set by the TIME event is less than the scan period, it is equivalent to executing the TIME event every scan period. Even if the clear output is set, the output and timer data in the event program will not be cleared.
210 210  
211 -== Interrupt execution program ==
211 +== **Interrupt execution program** ==
212 212  
213 213  In the process of executing the scan program, the program that can interrupt the priority execution of the scan program is called an interrupt execution program.
214 214  
... ... @@ -577,7 +577,7 @@
577 577  ON: Mask interrupt OFF: Enable interrupt
578 578  )))|0
579 579  
580 -== Subroutine ==
580 +== **Subroutine** ==
581 581  
582 582  During the execution of the scan program, the executed program can be called by the CALL instruction.
583 583  
... ... @@ -602,7 +602,7 @@
602 602  1. The subroutine can be nested up to 32 levels. If the level exceeds 32 levels, a serious error will be reported and the Circuit program operation will be forcibly stopped.
603 603  1. Unlike the LX3V series mainframe, the subroutine in the LX5V series mainframe ends with the END instruction instead of SRET.
604 604  
605 -== Positioning instructions ==
605 +== **Positioning instructions** ==
606 606  
607 607   ~1. Event
608 608  
0-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.admin
Size
... ... @@ -1,1 +1,0 @@
1 -40.3 KB
Content
1652145267405-613.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.admin
Size
... ... @@ -1,1 +1,0 @@
1 -4.0 KB
Content