Wiki source code of 04 Program flow

Version 7.1 by Mora Zhou on 2023/11/22 15:47

Show last authors
1 = **Program jump** =
2
3 == {{id name="_Toc102982428"/}}{{id name="_Toc17621"/}}{{id name="_Toc871"/}}{{id name="_Toc23743"/}}**CJ/Conditional jump** ==
4
5 When the jump instruction is ON, the program with the specified pointer number in the same program file is executed.
6
7 -[CJ (P) (P)]
8
9 **Content, range and data type**
10
11 (% class="table-bordered" %)
12 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
13 |(P)|The pointer number of the jump target|P0 to P4095|Device name|POINTER
14
15 **Device used**
16
17 (% class="table-bordered" %)
18 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(((
19 **Offset modification**
20 )))|(((
21 **Pulse extension**
22 )))|**other**
23 |**[D]**|**XXP**|**P**
24 |CJ|Parameter 1| |●|●
25
26 **Features**
27
28 * CJ(P)
29
30 {{id name="OLE_LINK159"/}}When the execution instruction is ON, the program with the specified pointer number is executed.
31
32 When the execution instruction is OFF, execute the next program.
33
34 (% style="text-align:center" %)
35 [[image:4_html_a501306a22b46191.png||class="img-thumbnail"]]
36
37 1. Execute instructions.
38 1. Each scan is executed.
39 1. One scan is executed.
40
41 (% class="box infomessage" %)
42 (((
43 **✎Note: **
44
45 After turning ON the coil of the timer, if the timer whose coil is ON is jumped by the CJ(P) instruction, the measurement will not be performed normally.
46
47 When the OUT instruction is jumped by the CJ(P) instruction, the scan time will be shorter.
48
49 When the CJ(P) instruction is used to jump backward, the scan time will be longer.
50 )))
51
52 For the CJ(P) instruction, you can jump to a step smaller than the step number being executed. However, in order to avoid the time limit of the watchdog timer, a method of jumping out of the loop during this period should be considered.
53
54 (((
55 (% style="text-align:center" %)
56 [[image:4-2.png||class="img-thumbnail"]]
57
58 (1) While X3 is ON, the loop is executed.
59
60 (2) When X7 is set to ON, it jumps out of the loop.
61 )))
62
63 • The device skipped by the CJ(P) instruction does not change.
64
65 (((
66 When X2 is ON, jump to the label of P19.
67
68 Even if X2 and X4 turn ON/OFF during CJ instruction execution, Y4 and Y5 will not change.
69
70 (% style="text-align:center" %)
71 [[image:1652258381961-360.png||class="img-thumbnail"]]
72
73 (1) When X2 is ON, jump to the label of P19.
74
75 (2) Even if X2 and X4 turn ON/OFF during CJ instruction execution, Y4 and Y5 will not change.
76 )))
77
78 • The label (P□) occupies 1 step.
79
80 (% style="text-align:center" %)
81 [[image:4_html_624bb12f51649fa1.gif||class="img-thumbnail"]]
82
83 The jump instruction can only specify the pointer number in the same program file.
84
85 When jumping to the pointer number within the jump range during jump operation, the program after the jump destination pointer number is executed.
86
87 The label procedure is shown below. When creating a loop program, move the cursor to the left of the bus bar of the Circuit program, and enter the label (P) at the beginning of the loop block.
88
89 (% style="text-align:center" %)
90 [[image:4_html_66293951b95227d4.png||class="img-thumbnail"]]
91
92 It is also possible to program the label at the position where the step number is less than the CJ instruction, but if the scan time becomes more than 200ms (default setting), a watchdog timer error will occur, which requires attention.
93
94 (% style="text-align:center" %)
95 [[image:1652258541371-747.png||class="img-thumbnail"]]
96
97 When the pointer number in the operand is the same and the label is one, the operation is as follows.
98
99 (((
100 (% style="text-align:center" %)
101 [[image:1652258590342-123.png||class="img-thumbnail"]]
102
103 (1) When X20 is ON, jump from the CJ instruction of X20 to label P9.
104
105 (2) When X20 is OFF and X21 is ON, jump from the CJ instruction of X21 to label P9.
106 )))
107
108 If the tag number is reused, it will become an error state.
109
110 (% style="text-align:center" %)
111 [[image:4_html_8fb019c9369040bb.gif||class="img-thumbnail"]]
112
113 SM100 is always ON during the operation of the CPU module, so the usage method shown below will jump unconditionally.
114
115 (% style="text-align:center" %)
116 [[image:4_html_595b9dbff9fae7fc.png||class="img-thumbnail"]]
117
118 The pointer number P63 of LX3V represents the jump to the END instruction. The P63 pointer of LX5V no longer provides this function. If you need to use this function, please use the GOEND instruction.
119
120 **Error code**
121
122 No error message
123
124 **Example**
125
126 **(1) The situation to jump after OFF processing**
127
128 After one operation cycle when X023 changes from OFF to ON, the CJ P7 instruction is valid.
129
130 With this method, the output between CJ P7 instruction and mark P7 can be turned off before jumping.
131
132 (% style="text-align:center" %)
133 [[image:4_html_e09161008c47ac30.png||class="img-thumbnail"]]
134
135 **(2) CJ instruction and action of contact coil**
136
137 In the following program example, when X000 is ON, jump from the CJ instruction of the first loop to the mark P8. When X000 is OFF, no jump is performed, but the program is executed in order from step 1, and the CJ instruction in the 11th loop jumps to mark P9. The jumped instruction is not executed.
138
139 (((
140 (% style="text-align:center" %)
141 [[image:4_html_e0d34198cc559166.png||class="img-thumbnail"]]
142
143 Double-coil action of Y001 output:
144
145 When X000=OFF, it will act through X001.
146
147 When X000=ON, it will act through X012.
148
149 Even if the program is distinguished by conditional jump, if the same coil (Y000) is programmed twice or more within or outside the jump, it will be treated as normal double coil processing.
150
151 The action of the subroutine timer (T192 to T199):
152
153 After the coil is driven, the action continues even if it jumps, and the output contact also operates.
154
155 If using the high-speed counter (HSC0 to HSC7) operation
156
157 After the coil is driven, the action continues even if it jumps, and the output contact also operates.
158 )))
159
160 In the above program, if each input changes during the jump, the action of each coil is shown in the following table.
161
162 (% class="table-bordered" %)
163 |(% style="width:235px" %)**Content**|(% style="width:292px" %)**Contact state before jump**|(% style="width:549px" %)**Coil action in jump**
164 |(% rowspan="2" style="width:235px" %)(((
165 Y,M,S (Y1, M1, S1)
166 )))|(% style="width:292px" %)X1, X2, X3 OFF|(% style="width:549px" %)Y1, M1, S1 OFF
167 |(% style="width:292px" %)X1, X2, X3 ON|(% style="width:549px" %)Y1, M1, S1 ON
168 |(% rowspan="2" style="width:235px" %)(((
169 1ms, 10ms, 100ms timer (T0)
170 )))|(% style="width:292px" %)X4 OFF|(% style="width:549px" %)Timer not working
171 |(% style="width:292px" %)X4 ON|(% style="width:549px" %)Timer interrupt (continue after X0 OFF)
172 |(% rowspan="2" style="width:235px" %)(((
173 Program timer (T192)
174 )))|(% style="width:292px" %)X5 OFF, X6 OFF|(% style="width:549px" %)Timer not working, but the timer is reset when X13 is ON
175 |(% style="width:292px" %)X5 OFF, X6 ON|(% style="width:549px" %)Timing continues (contact action after X0 OFF)
176 |(% rowspan="2" style="width:235px" %)(((
177 Counter (C0)
178 )))|(% style="width:292px" %)X7 OFF, X10 OFF|(% style="width:549px" %){{id name="OLE_LINK160"/}}Counting interrupt, but it is reset when X13 is ON
179 |(% style="width:292px" %)X7 OFF, X10 ON|(% style="width:549px" %)Count interruption (continue after X0 OFF)
180 |(% rowspan="2" style="width:235px" %)(((
181 Application instructions
182
183 (MOV)
184 )))|(% style="width:292px" %)X11 OFF|(% rowspan="2" style="width:549px" %)(((
185 Single-cycle application instructions are not executed in the jump
186
187 Multi-cycle application instructions are partially executable (such as high-speed pulse instructions)
188 )))
189 |(% style="width:292px" %)X11 ON
190
191 **(3) The relationship between CJ instruction and MC to MCR jump**
192
193 The relationship between the main control instruction and the jump instruction and the action content are as follows.
194
195 However, since the operation of ②, ④, and ⑤ will become complicated, please avoid using them.
196
197 (% style="text-align:center" %)
198 [[image:4_html_679b6b2848540f73.png||class="img-thumbnail"]]
199
200 = {{id name="_Toc23403"/}}**Subroutine jump** =
201
202 == {{id name="_Toc12697"/}}**{{id name="_Toc7169"/}}{{id name="_Toc17038"/}}{{id name="_Toc102982430"/}}CALL/Subroutine call** ==
203
204 When the jump instruction is ON, the program with the specified pointer number in the same program file is executed.
205
206 -[CALL (P) (P)]
207
208 **Content, range and data type**
209
210 (% class="table-bordered" %)
211 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
212 |(P)|Subroutine name|-|Pointer|POINTER
213
214 **Device used**
215
216 (% class="table-bordered" %)
217 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(((
218 **Offset modification**
219 )))|(% style="width:211px" %)(((
220 **Pulse extension**
221 )))|(% style="width:214px" %)**other**
222 |**[D]**|(% style="width:211px" %)**XXP**|(% style="width:214px" %)(((
223 **Subroutine name**
224 )))
225 |CALL|Parameter 1| |(% style="width:211px" %)●|(% style="width:214px" %)●
226
227 Parameter 1 can only use the subroutine name.
228
229 **Features**
230
231 When the CALL(P) instruction is executed, the subroutine of the pointer (P) will be executed. (P) can only write the name of the newly created subprogram, if the program name does not exist, the Circuit program compilation fails.
232
233 (% style="text-align:center" %)
234 [[image:4_html_8924f686c859efa4.png||class="img-thumbnail"]]
235
236 (% style="text-align:center" %)
237 [[image:4_html_60fa80c6a001beb0.gif||class="img-thumbnail"]]
238
239 CALL(P) instructions can be nested up to 32 levels.
240
241 (% style="text-align:center" %)
242 [[image:4_html_29c8e378dfb34066.png||class="img-thumbnail"]]
243
244 **✎Note: **
245
246 • Multiple CALL(P) instructions can call the same subprogram, but subprograms with the same program name are not allowed.
247
248 • Use program timers in subroutines (the same applies to interrupt programs). This timer counts when the coil instruction or the END instruction is executed. If it reaches the timer setting value, the output contact will act when the coil instruction or END instruction is executed. Generally, the timer only counts when the coil instruction is executed, so if it is used in a subroutine that executes the coil instruction under certain conditions, it will not count.
249
250 • If the 1ms accumulative timer is used in a subroutine (the same in an interrupt program), when it reaches the set value, the output contact will act when the first coil instruction is executed (when the subroutine is executed), so be careful.
251
252 • The devices that are turned on in the subprogram (the same in the interrupt program) will be retained after the program ends. Therefore, these devices should be reset in the main program after the end of the program.
253
254 **Error code**
255
256 (% class="table-bordered" %)
257 |**Error code**|**Content**
258 |4102H|CALL(P) instruction exceeds 32 levels of nesting structure
259
260 **Example**
261
262 **(1) New subroutine**
263
264 Project management→Subroutine→ Scan→Right click to create
265
266 (% style="text-align:center" %)
267 [[image:4_html_3d0d21476f0bb476.png||class="img-thumbnail"]]
268
269 **(2) Subroutine call**
270
271 (% style="text-align:center" %)
272 [[image:4_html_474fbc929fb22b37.png||class="img-thumbnail"]]
273
274 In the scan program, turn on M10 to call the subroutine SUB0, execute the Circuit program in the subroutine SUB0, until the END instruction of the subroutine is executed, return to the scan program MAIN to execute LD M11.
275
276 **(3) Subroutine nesting**
277
278 (% style="text-align:center" %)
279 [[image:4_html_d7bf03e5f06b73a8.png||class="img-thumbnail"]]
280
281 In the above figure, the subroutine SUB0 is called in the scan program, and the subroutine SUB1 is called in SUB0. So when the scan program M10 is turned on, after the CALL instruction is executed, the subroutine SUB0 will be executed first.And after the CALL instruction of SUB0 is executed, SUB1 will be executed first. After executing the END instruction of SUB1, return to SUB0 for execution. After executing the END instruction of SUB0, return to the scan program MAIN. The program has only 2 levels of nesting, and the number of nesting levels cannot be greater than 32.
282
283 = {{id name="_Toc8930"/}}**Interrupt disable, interrupt enable** =
284
285 == {{id name="_Toc102982432"/}}**DI and EI/Interrupt prohibited and allowed** ==
286
287 The CPU module is usually interrupt disabled. This instruction can make the CPU module into the interrupt enabled state (EI instruction), and then become disabled again (DI instruction).
288
289 • DI: It is forbidden to interrupt program execution.
290
291 • EI: Release the interrupt prohibition state.
292
293 -[DI (s)]
294
295 -[EI]
296
297 **Content, range and data type**
298
299 (% class="table-bordered" %)
300 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
301 |(P)|Subroutine name|-|Pointer|POINTER
302
303 (% class="table-bordered" %)
304 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|**Offset modification**|**Pulse extension**
305 |**[D]**|**XXP**
306 |DI|Parameter 1| |●
307
308 **{{id name="OLE_LINK161"/}}Features**
309
310 * DI
311
312 • Even if the execution interrupt condition is triggered in the program, prohibit the interrupt program execution before executing the EI instruction.
313
314 • When the PLC is powered on or after STOP, it will become the state after DI instruction is executed, and the interrupt program cannot be executed.
315
316 • The DI instruction can choose whether to use parameters. When there is no parameter, it means that all interrupt programs are prohibited. With parameters, according to the value in parameter s1, interrupt programs with this priority and lower priority are prohibited.
317
318 • The priority of the interrupt ranges from 0 to 2. The smaller the value, the higher the response priority of the interrupt. That is, the interrupt with priority 0 is the fastest to be responded.
319
320 • If there is no EI instruction before the DI instruction, the DI instruction is invalid.
321
322 * EI
323
324 • Release the interrupt prohibition state when DI instruction is executed, and allow interrupt program to run.
325
326 • When the EI and DI instructions are not enabled, they all maintain the original enabled or forbidden interrupt program execution status. The currently disabled interrupt priority can be viewed in SD151.
327
328 (% class="table-bordered" %)
329 |SD151|(% style="width:297px" %)Currently disabled interrupt priority|(% style="width:571px" %)(((
330 According to the interrupt prohibition instruction (DI instruction), the interrupt prohibition instruction (DI instruction) below the specified priority, and the interrupt enable instruction (EI instruction), the priority of the interrupt prohibition will be stored.
331
332 0: All priority interrupts are disabled (default);
333
334 1: Priority 1 and 2 interrupts are prohibited;
335
336 2: Priority 2 interrupt is prohibited;
337
338 3: All priority interrupts are allowed
339 )))|(% style="width:148px" %)R(read only)
340
341 A: Sequence control program
342
343 * DI, EI nested structure
344
345 (((
346 (1) Interrupt allowable intervals of all priority levels;
347
348 (2) Interrupt forbidden zone below priority 2 (interrupt allowable zone above priority 1);
349
350 (3) Interrupt forbidden interval below priority 1 (interrupt allowable interval above priority 0);
351
352 (4) Interrupt prohibition zone below priority 2 (interrupt enable zone above priority 1);
353
354 (5) Interrupt allowable intervals of all priority levels;
355
356 (6) EI paired with [DI K1];
357
358 (7) EI paired with [DI K2].
359
360 (% style="text-align:center" %)
361 [[image:4_html_a573e3db41c8e5e9.png||class="img-thumbnail"]]
362 )))
363
364 • Interrupts (requests) that occur after the DI instruction are processed after the EI instruction is executed.
365
366 • When the DI instruction is executed multiple times and the priority of the argument is specified to be higher than the priority currently being prohibited, interrupts below the priority of the argument are disabled.
367
368 • When the DI instruction is executed multiple times and the priority of the argument is specified to be lower than the priority currently being disabled, the interrupt disable status will not be changed.
369
370 • The nesting of DI instructions can be up to 16 levels.
371
372 • The interrupt priority of the interrupt pointer can be set by the properties of the interrupt program. Refer to the description of the interrupt program for details.
373
374 • The interrupt prohibition interval when DI instruction and EI instruction are executed is as follows.
375
376 **(1) When the DI instruction is executed multiple times (when the interrupt with priority higher than the currently prohibited interrupt priority is prohibited and specified)**
377
378 (% style="text-align:center" %)
379 [[image:4_html_c7e0f7f383d45a1b.png||class="img-thumbnail"]]
380
381 Scan execution type program
382
383 1. Interrupt allowable intervals of all priority levels;
384 1. Interrupt prohibition interval below priority 2 (interrupt allowable interval above priority 1);
385 1. Interrupt prohibition section below priority 1 (interrupt enable section above priority 0).
386
387 **(2) When the DI instruction is executed multiple times (when the interrupt priority is lower than the currently prohibited interrupt priority is prohibited and specified)**
388
389 (% style="text-align:center" %)
390 [[image:4_html_aad79b3250e8a24b.png||class="img-thumbnail"]]
391
392 Scan execution type program
393
394 1. Interrupt allowable intervals of all priority levels;
395 1. Interrupt prohibited interval below priority 1 (interrupt allowable interval above priority 0);
396 1. The interrupts below priority 1 are already in the disabled state, so the interrupt disable priority will not be changed.
397
398 **(3) When DI instruction is executed through interrupt program**
399
400 (% style="text-align:center" %)
401 [[image:4_html_a6d7521496fdd1f8.png||class="img-thumbnail"]]
402
403 A: Scan execution type program
404
405 B: interrupt program
406
407 1. Interrupt allowable intervals of all priority levels;
408 1. Interrupt prohibited interval below priority 3 (interrupt allowable interval above priority 1);
409 1. Interrupt prohibition section below priority 2 (interrupt enable section above priority 0).
410
411 **(4) When only DI instructions without arguments are executed**
412
413 (% style="text-align:center" %)
414 [[image:4_html_606dbe3d93909e42.png||class="img-thumbnail"]]
415
416 A: Scan execution type program
417
418 1. Interrupt allowable intervals of all priority levels;
419 1. Interrupt prohibition interval below priority 1 (all interrupt prohibition intervals);
420 1. Because the DI instruction with no argument is set to interrupt prohibition, by executing the EI instruction once, all priority interrupts are set to allow.
421
422 **(5) In the case of executing DI instructions with arguments and DI instructions without arguments (when executing in the order of DI instructions with arguments → DI instructions without arguments)**
423
424 (% style="text-align:center" %)
425 [[image:4_html_b9b528491258d0e4.png||class="img-thumbnail"]]
426
427 A: Scan execution type program
428
429 1. Interrupt allowable intervals of all priority levels;
430 1. Interrupt prohibition interval below priority 2 (interrupt allowable interval above priority 1);
431 1. Interrupt prohibition section below priority 1 (all interrupt prohibition sections).
432
433 **(6) In the case of executing DI instructions with arguments and DI instructions without arguments (in the case of execution in the order of DI instructions with no arguments → DI instructions with arguments)**
434
435 (% style="text-align:center" %)
436 [[image:4_html_622cf36b6bdc523.png||class="img-thumbnail"]]
437
438 {{id name="_Toc11636"/}}A: Scan execution type program
439
440 1. Interrupt allowable intervals of all priority levels;
441 1. Interrupt prohibition section below priority 1 (all interrupt prohibition sections).
442
443 **Error code**
444
445 (% class="table-bordered" %)
446 |**Error code**|**Content**
447 |4085H|(S) read address exceeds the device range
448 |4084H|The data set in (S) exceeds 0 to 2
449 |4185H|When the nesting of DI instructions exceeds 16 levels
450
451 **Example**
452
453 (((
454 (% style="text-align:center" %)
455 [[image:4_html_e068a061529263d1.png||class="img-thumbnail"]]
456
457 All interrupt programs can be triggered
458
459 Can trigger interrupt programs of priority 0 and priority 1
460
461 Can trigger interrupts with priority 0
462
463 Cannot trigger any interrupts
464
465 Can trigger an interrupt program with a priority of 0
466
467 Can trigger interrupt programs with priority 0 and priority 1
468 )))
469
470 == {{id name="_Toc2335"/}}**SIMASK/Interrupt mask** ==
471
472 Set interrupt pointer No. specified in (I) to the execution permission state/execution prohibition state according to the value of (s).
473
474 -[SIMASK (I) (s)]
475
476 **Content, range and data type**
477
478 (% class="table-bordered" %)
479 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
480 |(I)|Interrupt program name|-|Program name|POINTER
481 |(s)|Specify the enable/disable of interrupt|0: Allow. 1: Prohibited|Signed BIN 16 bit|ANY16
482
483 **Device used**
484
485 (% class="table-bordered" %)
486 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="12" %)**Devices**|(((
487 **Offset**
488
489 **modification**
490 )))|(((
491 **Pulse**
492
493 **extension**
494 )))
495 |**KnX**|**KnY**|**KnM**|**KnS**|**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**E**|**[D]**|**XXP**
496 |(% rowspan="2" %)SIMASK|Parameter 1|(% colspan="12" %)Only support interrupt program name| |
497 |Parameter 2|●|●|●|●|●|●|●|●|●|●|●|●|●|
498
499 **Features**
500
501 • The interrupt program of the interrupt program name specified in (I) is set to the execution permission state/execution prohibited state according to the data specified in (s).
502
503 • When (s) is 0: Interrupt program execution permission status
504
505 • When (s) is 1, the execution of the interrupt program is prohibited
506
507 • Regarding the interrupt program when the power is turned on or after STOP→RUN, all interrupt programs will be executed.
508
509 • After setting interrupt prohibition, the prohibition state will be saved even if the instruction is disconnected. To restore it, write 0 to (S), turn on the instruction again, or execute STOP→RUN.
510
511 • The interrupted execution permission status/execution prohibition status will be stored in SM or SD, details as following:
512
513 **{{id name="_Toc10728"/}}(1) External interrupt**
514
515 (((
516 (% class="table-bordered" %)
517 |**Register**|**Content**|**Register**|**Content**|**Register**|**Content**|**Register**|**Content**
518 |SM352|X0 rising edge interrupt|SM356|X2 rising edge interrupt|SM360|X4 rising edge interrupt|SM364|X6 rising edge interrupt
519 |SM353|X0 falling edge interrupt|SM357|X2 falling edge interrupt|SM361|X4 falling edge interrupt|SM365|X6 falling edge interrupt
520 |SM354|X1 rising edge interrupt|SM358|X3 rising edge interrupt|SM362|X5 rising edge interrupt|SM366|X7 rising edge interrupt
521 |SM355|X1 falling edge interrupt|SM359|X3 falling edge interrupt|SM363|X5 falling edge interrupt|SM367|X7 falling edge interrupt
522 )))
523
524 **(2) Timer interrupt**
525
526 (% class="table-bordered" %)
527 |**Register**|**Content**
528 |SD350 to SD356|Timer interrupt mask, each bit represents an interrupt, a total of 100
529
530 **(3) High-speed counter interrupt**
531
532 (% class="table-bordered" %)
533 |**Register**|**Content**
534 |SD382 to SD388|high-speed counter interrupt mask, each bit represents an interrupt, a total of 100
535
536 **Error code**
537
538 (% class="table-bordered" %)
539 |**Error code**|**Content**
540 |4084H|Data beyond 0 and 1 is input in the application instruction(s)
541 |4085H|(S) in the read application instruction exceeds the device range
542 |4189H|The SIMASK instruction specifies an interrupt program name that is not set
543
544 **Example**
545
546 (((
547 (% style="text-align:center" %)
548 [[image:4_html_fd3e8efafb82209a.png||class="img-thumbnail"]]
549
550 As shown in the figure: when M10 is turned on, the three interrupt programs of INT10, INT91 and INT70 are prohibited from running.
551 )))
552
553 = {{id name="_Toc15333"/}}**Cycle instructions** =
554
555 == {{id name="_Toc102982435"/}}**FOR to NEXT/Cycle** ==
556
557 When the processing between the FOR to NEXT instruction is executed unconditionally (n) times, the next processing of the NEXT instruction will be performed.
558
559 (% style="text-align:center" %)
560 [[image:4_html_bdecdd2d7f545f5b.gif||class="img-thumbnail"]]
561
562 **Content, range and data type**
563
564 (% class="table-bordered" %)
565 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
566 |(n)|Number of repetitions between FOR to NEXT instructions|1 to 32767|Signed BIN 16 bit|ANY16
567
568 (% class="table-bordered" %)
569 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="12" %)**Devices**|(((
570 **Offset**
571
572 **modification**
573 )))|(((
574 **Pulse**
575
576 **extension**
577 )))
578 |**KnX**|**KnY**|**KnM**|**KnS**|**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**E**|**[D]**|**XXP**
579 |FOR|Parameter 1|●|●|●|●|●|●|●|●|●|●|●|●|●|
580
581 **Features**
582
583 • When the processing between the FOR to NEXT instruction is executed unconditionally (n) times, the next processing of the NEXT instruction will be performed.
584
585 • (n) can be specified in the range of 1 to 32767. When specifying -32768 to 0, the same processing as (n)=1 will be performed.
586
587 • If you do not want to execute the processing between the FOR and NEXT instructions, use the CJ instruction to jump.
588
589 • The FOR instruction can be nested up to 5 levels.
590
591 **✎Note: **
592
593 • In the case of FOR to NEXT instruction programming with nesting between FOR to NEXT instructions, up to 5 levels can be achieved.
594
595 (% style="text-align:center" %)
596 [[image:4_html_df140146b29101ab.png||class="img-thumbnail"]]
597
598 • Do not use IRET, SRET, RET, FEND, END and other instructions to block between FOR to NEXT instructions.
599
600 • If the number of repetitions is too large, the cycle time (operation cycle) becomes longer and the watchdog timer error occurs, you need to change the watchdog timer time or reset the watchdog timer.
601
602 • The following program will become an error.
603
604 (% style="text-align:center" %)
605 [[image:4_html_3646fec26f307e30.gif||class="img-thumbnail"]]
606
607 • If the FOR to NEXT instruction is repeatedly executed and ends midway, use the BREAK instruction.
608
609 **Error code**
610
611 (% class="table-bordered" %)
612 |**Error code**|**Content**
613 |4085H|(s) read address exceeds the device range
614 |4100H|When the nesting of FOR to NEXT instructions exceeds 5 levels or the number of FOR to NEXT does not correspond
615
616 **Example**
617
618 (% style="text-align:center" %)
619 [[image:4_html_cf327fbe235812df.png||class="img-thumbnail"]]
620
621 The program INC D0 will be executed 10 times, and INC D1 will be executed 100 times.
622
623 After execution, D0 will be equal to 10 and D1 will be equal to 100.
624
625 == {{id name="_Toc102982436"/}}**BREAK/Break cycle** ==
626
627 When the processing between the FOR to NEXT instruction is executed unconditionally (n) times, the next processing of the NEXT instruction will be performed.
628
629 -[BREAK]
630
631 **Features**
632
633 • Forcibly end the repeated processing by FOR to NEXT instructions.
634
635 • This instruction can only be between FOR to NEXT, otherwise an operation error will be reported.
636
637 • The BREAK instruction can only jump out of the loop nesting structure where the instruction itself is located.
638
639 • When the contact is connected, the loop structure of the FOR to NEXT instruction where it is located is forced to end, as shown in the figure below.
640
641 (((
642 (% style="text-align:center" %)
643 [[image:4_html_c83826b59b86eb5a.png||class="img-thumbnail"]]
644
645 M0 turns ON, no matter how many cycles are left to execute, jump directly to step 35 to execute the program.
646
647 M4 turns ON, no matter how many loops are left to execute, jump directly to step 50 to execute the program.
648 )))
649
650 **Error code**
651
652 (% class="table-bordered" %)
653 |**Error code**|**Content**
654 |4186H|{{id name="OLE_LINK163"/}}BREAK instruction is not used between FOR to NEXT instructions
655
656 **Example**
657
658 (% style="text-align:center" %)
659 [[image:4_html_300cc2cbd41e93af.png||class="img-thumbnail"]]
660
661 The program INC D0 will be executed 10 times, and INC D1 will be executed 100 times.
662
663 When M0 is OFF, D0 will be equal to 10 and D1 will be equal to 100 after execution.
664
665 When M0 is ON, the BREAK instruction is executed, and the current loop is exited. The INC D1 instruction will not be executed, and the result D1=0.
666
667 = {{id name="_Toc21268"/}}**Master Control Instructions** =
668
669 == {{id name="_Toc102982438"/}}{{id name="_Toc25408"/}}{{id name="_Toc22131"/}}{{id name="_Toc6021"/}}**MC and MCR instructions** ==
670
671 • MC: Start main control.
672
673 • MCR: End the main control.
674
675 (% style="text-align:center" %)
676 [[image:4_html_6f51bb3cb7d2ba4f.png||class="img-thumbnail"]]
677
678 **Content, range and data type**
679
680 (% class="table-bordered" %)
681 |**Parameter**|**Content**|**Range**|**Data type**|**Data type (label)**
682 |(N)|Nested ID N|0 to 7|Signed BIN 16 bit|ANY16
683 |(d)|Device number that is turned ON|-|Bit|ANY_BOOL
684
685 (% class="table-bordered" %)
686 |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(% colspan="12" %)**Devices**|**Offset modification**|**Pulse extension**
687 |**KnX**|**KnY**|**KnM**|**KnS**|**T**|**C**|**D**|**R**|**SD**|**K**|**H**|**E**|**[D]**|**XXP**
688 |(% rowspan="2" %)MC|Parameter1|(% colspan="12" %)Only use N0 to N7| |
689 |Parameter2|●|●|●|●|●|●|●|●|●|●|●|●| |
690 |MCR|Parameter1|(% colspan="12" %)Only use N0 to N7| |
691
692 **Features**
693
694 The main control instruction is used to create an efficient circuit program switching program by opening and closing the common bus of the circuit program.
695
696 The transition of ordinary Circuit program and master control Circuit program is as follows:
697
698 (((
699 (% style="text-align:center" %)
700 [[image:4_html_43089229889e1c0c.png||class="img-thumbnail"]]
701 )))
702
703 MC to MCR internal program, X0 must be open to execute
704
705 ■MC
706
707 • When the execution instruction of the MC instruction is turned on by the start of main control, the operation result from the start of the MC instruction to the MCR instruction is the execution result of the instruction (loop). When the MC execution instruction is OFF, the calculation results from the MC instruction to the MCR instruction are as follows.
708
709 (% class="table-bordered" %)
710 |**Devices**|**Device status**
711 |Timer|The count value becomes 0, and the coil and contact are all turned off.
712 |Counter, cumulative timer|The coil turns off, but the count value and contact remain in the current state.
713 |Devices in the OUT instruction|Forced to be OFF.
714 |(((
715 Devices in SET and RST instruction
716
717 Devices in basic and application instructions
718 )))|Keep the current state
719
720 • For MC instructions, the same nesting (N) number can be used multiple times by changing the device of (d).
721
722 • When the MC instruction is ON, the coil of the device specified in (d) will turn ON. In addition, when the same device is used in an OUT instruction, etc., it becomes a double coil. Therefore, the device specified in (d) must not be used in other instructions.
723
724 **Key points:**
725
726 If there are instructions that do not require contact (such as, FOR to NEXT instructions).If the instruction after MC can not affect the main CPU module, the instruction will execute.
727
728 ■MCR
729
730 • The release instruction of the main control indicates the end of the main control range.
731
732 • Do not add a contact instruction before the MCR instruction.
733
734 • When using, MC instruction and MCR instruction of the same nesting number should be used. However, when the MCR instruction has a nested structure concentrated in one position, all main controls can be terminated by the smallest number (N) number. (Refer to notes)
735
736 ■Nested structure
737
738 The main control instruction can be used through a nested structure. Each main control section is distinguished by nesting (N). N0 to N7 can be used for nesting.
739
740 By using the nested structure, it is possible to create a Circuit program that sequentially restricts the execution conditions of the program. The Circuit program using the nested structure is shown below.
741
742 (Left: Display of engineering tools, Right: Actual action loop)
743
744 (% style="text-align:center" %)
745 [[image:1652259670879-365.png||class="img-thumbnail"]]
746
747 1. Execute when A is ON;
748 1. Execute when A and B are ON;
749 1. Execute when A, B, C are ON;
750 1. It has nothing to do with A, B,
751
752 **✎Note: **
753
754 • If there is no instruction (LD, LDI, etc.) connected to the bus after the MC instruction, a program structure error occurs.
755
756 • MC to MCR instructions cannot be used in FOR to NEXT, STL to RET, subroutines, events, and interrupts. In addition, there cannot be instructions such as IRET, FEND, END, RET (SRET) inside MC to MCR to block.
757
758 • There can be up to 8 nests (N0 to N7). In the case of nesting, the MC instruction is used from the small number of nesting (N), while the MCR instruction is used from the old number. If the order is reversed, it does not become a nested structure, so the CPU module cannot operate normally.
759
760 • When the MCR instruction is a nested structure concentrated in one location, all main control can be ended by the smallest number (N) number.
761
762 **Error code**
763
764 No operation error
765
766 **Example**
767
768 (1) No nested structure
769
770 (((
771 (% style="text-align:center" %)
772 [[image:4_html_4f6cacf53f330135.png||class="img-thumbnail"]]
773
774 Main control program 1
775
776 Main control program 2
777 )))
778
779 The main control program 1 and the main control program 2 do not belong to the nested structure, so you can use N0 programming. There is no limit to the number of times N0 can be used in this case.
780
781 **(2) Nested structure**
782
783 When using the MC instruction, the number of nesting level N increases sequentially.(N0→ N1→ N2→ N3→ N4→ N5→ N6→ N7). When returning, use the MCR instruction to release from the larger nesting level. (N7→ N6→ N5→ N4→ N3→ N2→ N1 → N0).
784
785 For example, when MCR N6 and MCR N7 are not programmed, if MCR N5 is programmed, the nesting level will return to 5 at once.The nesting level can be programmed up to 8 levels (N7).
786
787 (((
788 (% style="text-align:center" %)
789 [[image:1652260093074-914.png||class="img-thumbnail"]]
790 )))
791
792 As shown above:
793
794 87 Walk: Level N0, Y0 will follow X1 state only when X0 is ON.
795
796 95 Walk: Level N1, Y1 will follow X3 state only when X0 and X2 are both ON.
797
798 103 Walk: Level N2, Y2 will follow X5 state only when X0, X2, and X4 are ON at the same time.
799
800 109 Walk: Level N1, use MCR N2 to return to level N1. Y3 will follow the state of X6 only when X0 and X2 are both ON.
801
802 115 walk: level N0, use MCR N1 to return to level N0. Y4 will follow the state of X7 only when X0 is ON.
803
804 121 Walk: Does not belong to the main control structure, has nothing to do with X0, X2, X4, Y5 follows the state change of X10.
805
806 = {{id name="_Toc16744"/}}**Watchdog reset** =
807
808 == {{id name="_Toc15927"/}}**WDT/watchdog timer** ==
809
810 The watchdog timer is reset by the program.
811
812 -[WDT]
813
814 **Features**
815
816 • Reset the watchdog timer through the program.
817
818 • Use when the scan time exceeds the set value of the watchdog timer depending on conditions.
819
820 • For t1 from step 0 to WDT instruction, and from WDT instruction to END instruction, do not exceed the set value of the watchdog timer.
821
822 (% style="text-align:center" %)
823 [[image:4_html_3341a4693ce1250c.png||class="img-thumbnail"]]
824
825 • The WDT instruction can be used more than twice in one scan.
826
827 **✎Note: **
828
829 • The watchdog timeout time can be set in the special register SD122. The default is 200ms.
830
831 • Use the special relay SM122 to control whether to turn on the watchdog timer function. The WDT instruction will be invalid after closing.
832
833 (% style="text-align:center" %)
834 [[image:4_html_21bc20f7ff159189.png||class="img-thumbnail"]]
835
836 (1) The watchdog timer time is set to 300ms;
837
838 (2)  Refresh the watchdog timer.
839
840 **Error code**
841
842 There is no operation error.
843
844 **Example**
845
846 (% style="text-align:center" %)
847 [[image:4_html_ceca3c411d993d90.png||class="img-thumbnail"]]
848
849 The FOR to NXET instruction loop takes a long scan period for many times, which may exceed the set watchdog timer 300ms, causing the PLC to report an error and cannot continue to run. After turning on M0, the WDT instruction will run, and the watchdog timer is updated every cycle , So that it will not report an error to execute the program normally.