Skip to Content

Wiki source code of 01 Execution of the Program

Version 2.2 by Iris on 2026/03/02 11:55
Hide last authors
Wecon 1.1 1 == **Composition of the Scan** ==
2
3 ----
4
5 The scan configuration of the CPU module is as follows.
6
7 (% style="text-align:center" %)
8 [[image:1.png]]
9
10 === **Initialization** ===
11
12 ----
13
14 The initialization based on the status of the CPU module is as follows.
15
16 **√**: execute. **×**: not execute
17
18 |(% rowspan="2" %)**Processing item**|(% colspan="3" %)**Status of the CPU module**
19 |**When the power is ON**|**STOP**|**When STOP RUN**
20 |Initialization of input and output modules|√|×|×
21 |CPU parameter check|√|×|×
22 |Check of system parameters|√|×|×
23 |Device initialization|√|×|√
24 |Error clear|√|×|√
25
26 === **Input and Output Point Refresh** ===
27
28 ----
29
30 Perform the following before starting program calculation.
31
32 Update the actual input point of the PLC to the input relay X.
33
34 The following is executed after the END instruction is executed.
35
36 Update the PLC output relay Y to the actual output point.
37
38 **Key points**
39
40 When performing a constant scan, the I/O refresh is performed after the waiting time of the constant scan.
41
42 === **Operation of the Program** ===
43
44 ----
45
46 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.
47
48 === **END Processing** ===
49
50 ----
51
52 Perform the following processing.
53
54 1. Completion processing of partial instructions
55 1. Watchdog timer reset
56 1. Communication processing
57 1. Setting the value of special relay/special register (when the setting timing is END processing)
58
59 == **Scan Time** ==
60
61 ----
62
63 The CPU module repeats the following processing, and the scan time is the total of the following processing and execution time.
64
65 (% style="text-align:center" %)
66 [[image:2.png]]
67
68 The initial scan time indicates the time including this processing.      
69
70 === **Initial Scan Time** ===
71
72 It is the first scan time of the CPU module in RUN.
73
74 Process as the following way:
75
76 The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
77
78 == **The Flow of Each Procedure** ==
79
80 ----
81
82 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.
83
84 (% style="text-align:center" %)
85 [[image:3.png]]
86
87 **Key points**
88
89 When the execution types of the programs are the same, they are executed in the order set in the execution order.
90
91 (% class="box infomessage" %)
92 (((
93 **✎Note:**
94
95 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.
96 )))
97
98 == **Types of Program Execution** ==
99
100 ----
101
102 === **Scan Execution Program** ===
103
104 ----
105
106 Each scan is executed only once from the next scan of the initial execution type program.
107
108 (% style="text-align:center" %)
109 [[image:5.png]]
110
111 When multiple scan execution type programs are executed, the execution time of the scan execution type program is the time until all scan execution type programs are executed. In addition, before the execution of the scan execution type program is completed, if an interrupt program/event execution type program/subroutine is executed, the execution time will also be included.
112
113 **Creation of multiple scanners**
114
115 "Project Management"→ "Program"→ "Scan"→ Right click to create
116
117 (% style="text-align:center" %)
118 [[image:6.png]]
119
120 1. Scan the program name: the program name requires to match case, and the program name cannot use the same name with device name (the device name does not match case).
121 1. The input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" is not supported. It cannot exceed 64 characters. The default name is MAINx.
122 1. The number of scan programs that can be built is limited to 100.
123 1. The execution sequence runs from top to bottom in the order of creation.
124
125 (% style="text-align:center" %)
126 [[image:7.png]]
127
128 === **Event Execution Program** ===
129
130 It uses the event specified by the user as a condition to trigger the program to start execution.
131
132 (% style="text-align:center" %)
133 [[image:8.png]]
134
135 **Tigger type**
136
137 The trigger of event execution type program is as follows.
138
139 **(1) ON event of bit data (TRUE)**
140
141 1. After the ON event is specified, if the contact that sets the trigger condition in the ON event is turned ON during the scan program, the ON event program will be executed in the scan program page*1 or before the END instruction is executed.
142 1. The ON event program will only be executed once in a single scan cycle.
143 1. After the ON event is executed, you can set whether to clear the current value of the output (Y) and timer (T) used in the program.
144
145 *1: Scan program paging: multiple scan programs are established, and each scan program is called a paging. After scan program A is executed, before scan program B is executed, it will be judged whether an event program needs to be executed.
146
147 (% style="text-align:center" %)
148 [[image:9.png]]
149
150 When it is the turn of the execution sequence of event execution type program C and Y50 is ON, the program is executed.
151
152 The devices that can be specified are as follows.
153
154 (% style="margin-left:auto; margin-right:auto" %)
155 |=(% colspan="2" %)**Project**|=**Content**
156 |(% rowspan="2" %)Device *1|Bit Device|X, Y, M, SM
157 |Bit specification of word device|D.b
158
159 *1 The indexed device cannot be specified.
160
161 **(2) TIME event**
162
Iris 2.2 163 After the program is to RUN state and the specified time has elapsed, event is executed one time when it comes to the execution sequence of the first corresponding program. For the second and subsequent executions, the time is re-measured from the start of the last event execution type program. After the specified time has elapsed, the program is executed repeatedly when it comes to the execution sequence of the first corresponding program. In addition, in the next scan after the corresponding program is executed, the current value of the output (Y) and timer (T) used in the corresponding program can be cleared. It can be used for programs that do not need to respond in a fixed period of time.[[image:1772422285611-760.png]]
Wecon 1.1 164
165 After the specified time has elapsed, when it comes to the first execution sequence, the event execution type program C is executed.
166
167 **Key points**
168
169 When set to clear the current value of output and timer, and the scan time is longer than the set value of elapsed time, the current value of output and timer will not be cleared.
170
171 **Operational steps**
172
173 **(1) New event**
174
175 Project management→ Program→ Event → Right click to create.
176
177 (% style="text-align:center" %)
178 [[image:11.png]]
179
180 Event program name:
181
182 1. The program name requires to match case, and the program name with the same name as the device cannot be used (the device name does not match case).
183 1. The program name does not support /%$@&=~~`^<>?:{}[],;!*.~\~\'" character input.
184 1. The length of the program name cannot exceed 64 characters. The default name is EVENTx.
185
186 A maximum of 100 new event programs could be created.
187
188 **(2) Execution type**
189
190 There are two ways to configure the event execution type:
191
192 1. Configure when creating a new event program, as shown in the figure above.
193 1. Project management→ Program→ Parameter → Program parameter→Configuration
194
195 (% style="text-align:center" %)
196 [[image:12.png||height="427" width="510"]]
197
198 Configuration instructions:
199
200 1) Configuration interface:
201
202 (% style="text-align:center" %)
203 [[image:13.png]]
204
205 2) Parameter content:
206
207 |(% colspan="2" %)**Project**|**Content**|**Setting range**|**Default**
208 |(% colspan="2" %)Execution type|Select event type|Not set/ON event/TIME event|Not set
209 |(% rowspan="2" %)ON event|Contact|The event type can be set when ON event is selected. Set the bit device as the trigger condition.|X/Y/M/SM/D.b|
210 |Whether to clear|When the bit device of the trigger condition set by the ON event is turned OFF, whether to clear the current value of the output (Y) and timer (T) used in the execution program of the ON event in the next cycle.|(((
211 True
212
213 False
214 )))|False
215 |(% rowspan="2" %)TIME event|Time|Set how long to execute the event program once.|1 to 2147483647 (100us unit)|
216 |Whether to clear|When the TIME event is executed, if the event is not executed in the next scan cycle, select whether to clear the output (Y) used in the TIME event execution program and the current value of the timer (T).|(((
217 True
218
219 False
220 )))|False
221
222 **Key points**
223
224 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.
225
226 === **Interrupt Execution Program** ===
227
228 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.
229
230 * When an interrupt cause occurs, the interrupt program corresponding to the interrupt pointer number will be executed. However, the execution needs to be set to the interrupt enabled state by the EI instruction.
231
232 (% style="text-align:center" %)
233 [[image:14.png||height="295" width="700"]]
234
235 * An interrupt name corresponds to an interrupt program, and the interrupt name cannot be repeated. Each interrupt has its own trigger condition and execution program, and each interrupt program ends with END.
236 * Interrupt has the characteristic of interrupting the original execution program and executing the interrupt first, but it cannot interrupt the interrupt program being executed.
237 * The interrupt program has the concept of priority. The smaller the priority value, the more priority the response. The priority setting range is 0 to 2.
238
239 The actions when an interruption cause occurs are as follows:
240
Iris 2.2 241 1) Interrupt prohibition (DI) When an interruption cause occurs.
Wecon 1.1 242
243 If the interrupt execution condition is triggered in a program that is forbidden by DI, the interrupt will not be executed. Even if the subsequent program uses the EI instruction to allow interruption, the previously shielded interrupt program will not be executed. Only the interrupt execution condition is triggered again. The interrupt program will be executed.
244
245 2) When multiple interrupt causes occur simultaneously in the interrupt enabled state.
246
247 The interrupt program with higher priority will be executed sequentially. In addition, when multiple interrupts with the same priority occur at the same time, the actions are executed in the order of interrupt priority.
248
249 If three interrupt programs I0, I10, I16 are created, the priority of I0 is 1, the priority of I10 is 0, and the priority of I16 is 1. The execution logic is shown in the figure below: I10 has the smallest priority and is executed first; I0 and I16 have the same priority and are executed in the order of program establishment.
250
251 (% style="text-align:center" %)
252 [[image:15.png]]
253
254 3) When an interrupt occurs during the waiting time when performing constant scan.
255
256 Execute the interrupt program for this interrupt.
257
258 4) When other interrupts occur during the execution of the interrupt program.
259
260 In the interrupt program (including the specification when the interrupt occurs in the event execution program), when other interrupts occur, the original interrupt execution program will not be interrupted. After the original interrupt execution program is completed, the new interrupt program is executed. After the execution is completed Then return to the scanning procedure.
261
262 5) During the execution of the interrupt program, when an interrupt cause with a low priority or the same priority occurs.
263
264 The interruption cause that occurred is stored, and after the interrupt program in execution ends, the interrupt program corresponding to the stored interruption cause is executed. Even if the same interruption cause occurs multiple times, the interruption cause is stored only once.
265
266 (% style="text-align:center" %)
267 [[image:16.png]]
268
269 6) When the same interruption cause occurs during the execution of the interrupt program;
270
271 The interruption cause that occurred is stored, and after the interrupt program in execution ends, the interrupt program corresponding to the stored interruption cause is executed. Even if the same interruption cause occurs multiple times, the interruption cause is stored only once.
272
273 **Interrupt trigger condition classification**
274
275 **(1) External input (X) interrupt**
276
277 1) Description of external input interrupt
278
279 * The external input interrupt is triggered by the rising or falling edge of the fixed X point input.
280 * Supports the rising and falling edge interrupts of a total of 8 input points of X0 to X7, and supports a total of 16 external input interrupts.
281 * The same interrupt trigger condition cannot create multiple interrupt programs.
282 * External input interrupt and high-speed counter cannot use the same X point.
283 * You must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
284
285 2) External input interrupt steps.
286
287 Project management→ Program→ Interrupt→ right click to create
288
289 (% style="text-align:center" %)
290 [[image:17.png]]
291
292 * The interrupt program name requires to match case, and the program name with the same name as the device cannot be used (the device name does not match case),
293 * The interrupt program name does not support the input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" characters,
294 * The length of the interrupt program name cannot exceed 64 characters and cannot be typed. The default name is INTx.
Iris 2.2 295 * Click Configure, and select external interrupt for execution type, as shown in the figure below (it can also be configured in "Program parameters" in "Parameter" in project management):
Wecon 1.1 296
297 (% style="text-align:center" %)
298 [[image:18.png]]
299
300 (% style="margin-left:auto; margin-right:auto" %)
301 |=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
302 |(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set
303 |(% rowspan="4" %)External input interrupt|channel|Select the channel for external input interrupt|X0 to X7|X0
304 |Trigger edge type|Choose to trigger on rising edge or falling edge|Rising edge; Falling edge|Rising edge
305 |priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
306 |Filter time (0.01us)|(((
307 Set the filter time of X point, the unit is 0.01us.
308
309 Note: X rising edge interrupt and X falling edge interrupt use the same X filter, so after the filter setting is changed in the X rising edge configuration, the X falling edge will also change. If the filter time is set to 1000, you must ensure that the high level and low level of the input signal are maintained for more than 10 us before the interrupt can be triggered.
310 )))|0 to 1700|1
311
312 3) Write interrupt execution program
313
314 (% style="text-align:center" %)
315 [[image:19.png]]
316
317 Double-click the newly created interrupt program in the project management to start writing the interrupt execution program. As shown in the figure above, a newly created interrupt program is INT_X0_UP, and the trigger condition is configured to execute the interrupt program when the X0 rising edge is configured. If the EI instruction is used in the main program to allow interrupts, all programs in INT_X0_UP will be executed whenever X0 changes from OFF to ON, That is, D0 will increment once.
318
319 (% style="text-align:center" %)
320 [[image:20.png||height="138" width="317"]]
321
322 (2)Timer interrupt
323
324 1) Timer interrupt description
325
326 * Timer interrupt is based on the set time, execute the interrupt program every time, the minimum time interval can reach 100us.
327 * Up to 100 timer interrupt execution programs can be created.
328 * Each timer interrupt program is independent of each other and does not affect each other.
329 * Each timer interrupt program should be configured with priority. When triggered at the same time, it is executed in the order of priority, but when the priority is the same, it is executed in the order of the established program.
330 * The interrupt execution program is executed only after EI is used in the scanner to allow the interrupt
331
332 2) Timer interrupt step
333
334 Project managementðProgramðInterruptðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure and select Timer Interrupt as the execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management).
335
336 (% style="text-align:center" %)
337 [[image:21.png]]
338
339 (% style="margin-left:auto; margin-right:auto" %)
340 |=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
341 |(% colspan="2" %)Execution type|Select the type of interrupt|Not set/External input interrupt/Timer event/high-speed counter interrupt|Not set
342 |(% rowspan="2" %)Timer interrupt|Time|Set the interval time for interrupt triggering|1 to 2147483647 (100us unit)|
Iris 2.2 343 |Priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
Wecon 1.1 344
345 3) Write interrupt execution program
346
347 (% style="text-align:center" %)
348 [[image:22.png]]
349
350 Double-click the newly created timer interrupt program in the project management to start writing the interrupt execution program. As shown in the figure above, a newly created timer interrupt program is INT0, and the trigger condition is configured to execute the interrupt program every 10ms. If the main program uses EI to enable interrupts, all instruction programs in INT0 will be executed every 10ms, namely D0 It will add 1 to 10ms.
351
352 (% style="text-align:center" %)
353 [[image:23.png||height="190" width="558"]]
354
355 **(3)High-speed counter interrupt**
356
357 1) Description of high-speed counter interrupt
358
359 * The high-speed counter interrupt triggers an interrupt condition after the set value of the high-speed counter HSC0 to HSC7 provided by the PLC and executes the interrupt program.
360 * It can support up to 100 high-speed counter interrupt programs, but the number that can be supported by each channel does not need to be fixed.
361 * When using the high-speed counter interrupt, project must configure the high-speed counter and use the OUT HSC instruction to enable the corresponding counting channel to count before it can be used (see the high-speed counter description section for the specific configuration method).
362 * Each high-speed counter interrupt program should be configured with priority. When triggered at the same time, it will be executed in the order of priority. When the priority is the same, it will be executed in the order of channels HSC0-HSC7. When the channel is also the same, it is executed in order according to the creation promise.
363 * Project must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
364
365 {{info}}
366 **✎Note: **Both the HSC channel and the external input interrupt channel must use the PLC input point X. It should be noted that it cannot be reused during configuration. For details, please refer to the configuration chapter of the high-speed counter.
367 {{/info}}
368
369 2) high-speed counter interrupt steps
370
Iris 2.2 371 “Project management”ð“Programð“Interrupt”ðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure, select high-speed interrupt for execution type, as shown in the figure below (it can also be configured in "Program parameters" in "Parameters" in project management).
Wecon 1.1 372
373 (% style="text-align:center" %)
374 [[image:24.png]]
375
376 |=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
377 |(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set
378 |(% rowspan="5" %)High count interrupt|Mode|(((
379 Select the type of high-speed counter interrupt:
380
381 (1) High-speed comparison interrupt: The interrupt program is executed after the trigger condition is reached.
382
383 (2) High-speed comparison setting: After reaching the trigger condition, the set contact is set.
384
385 (3) High-speed comparison reset: reset the set contact after reaching the trigger condition.
386 )))|(((
387 High-speed compare interrupt
388
389 High-speed comparison set
390
391 High-speed comparison reset
392
393 Not set
394 )))|High-speed compare interrupt
395 |Channel|Select the high-speed counter channel used|HSC0 to HSC7|HSC0
396 |Comparison value|Set the comparison value of the high-speed counter. When the high-speed counter value of the set channel passes this value, the trigger condition is reached.|-2147483648 to 2147483647|
397 |Priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
398 |Contact|It is available when selecting high-speed comparison set and high-speed comparison reset. The contact is set or reset immediately after the trigger condition is reached.|Y/M/D.b|
399
400 3) Description of triggering rules
401
402 |=**Mode**|=**Configuration**|=**The current value**|=**Action**
403 |(% rowspan="2" %)High-speed compare interrupt (INT0)|(% rowspan="2" %)Comparison value: 10000|9999 → 10000|Execute all programs in interrupt INT0
404 |10001 → 10000|Execute all programs in interrupt INT0
405 |(% rowspan="2" %)High-speed comparison set (INT1)|(% rowspan="2" %)(((
406 Comparison value: -50,000
407
408 Contact: Y10
409 )))|-50001 → -50000|(((
410 Y10 is immediately set and mapped to the actual output (not affected by the scan period)
411
412 The program in INT1 will not be executed
413 )))
414 |-49999 → -50000|(((
415 Y10 is immediately set and mapped to the actual output (not affected by the scan period)
416
417 The program in INT1 will not be executed
418 )))
419 |(% rowspan="2" %)High-speed comparison reset (INT2)|(% rowspan="2" %)(((
420 Comparison value: 400000
421
422 Contact: Y10
423 )))|399999 → 400000|(((
424 Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
425
426 The program in INT2 will not be executed
427 )))
428 |400001 → 400000|(((
429 Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
430
431 The program in INT2 will not be executed
432 )))
433
434 {{info}}
435 **✎Note: **Both HSC channel and external input interrupt channel need to use the INPUT point X, so it should be noted that it cannot be reused in configuration. For details, please refer to the configuration section of high-speed counter.
436 {{/info}}
437
438 4) Write interrupt execution program
439
440 ① New interrupt program
441
442 Create three new interrupt programs under the interrupt of project management, namely HSC0_20000, HSC0_30000, HSC0_40000. Configure the interrupt program in the "program parameters", as shown in the figure below.
443
444 (% style="text-align:center" %)
445 [[image:25.png]]
446
447 ② High-speed counter configuration
448
449 Configure HSC0 for use in the high-speed counter configuration. After selecting the working mode, click the "Check” button. After the correct configuration box pops up, click Enter.
450
451 (% style="text-align:center" %)
452 [[image:26.png]]
453
454 Call the high-speed counter in the main program and enable interrupts:
455
456 (% style="text-align:center" %)
457 [[image:27.png]]
458
459 Program operation:
460
461 Assuming that the High-speed counter channel 0 has been receiving pulses:
462
463 When the count value of HSC0 accumulates from 0 to 20000, all procedures of HSC0_20000 are executed.
464
465 When the count value of HSC0 is accumulated from 20000 to 30000, all procedures of HSC0_30000 are executed.
466
467 When the count value of HSC0 is accumulated from 30000 to 40000, all procedures of HSC0_40000 are executed.
468
469 **Mask interrupt**
470
471 **(1) Mask through application instructions**
472
473 The PLC interrupt is in the shielded state by default when it is powered on, and can only be used after the interrupt is allowed through the EI instruction.
474
475 The interrupt mask instruction DI masks all interrupts without parameters, and masks some priority interrupts with parameters (refer to the program flow instruction DI/EI for details).
476
477 **(2) Mask through special registers SM an d SD**
478
479 1) External input interrupt mask register
480
481 (% style="margin-left:auto; margin-right:auto" %)
482 |=(% colspan="4" %)**External input interrupt mask register**
483 |**Special register number**|**Type of interrupt**|**Instruction**|**Defaults**
484 |SM352|X0 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
485 |SM353|X0 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
486 |SM354|X1 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
487 |SM355|X1 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
488 |SM356|X2 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
489 |SM357|X2 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
490 |SM358|X3 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
491 |SM359|X3 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
492 |SM360|X4 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
493 |SM361|X4 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
494 |SM362|X5 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
495 |SM363|X5 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
496 |SM364|X6 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
497 |SM365|X6 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
498 |SM366|X7 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
499 |SM367|X7 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
500
501 2) Timer interrupt mask register
502
503 (% style="margin-left:auto; margin-right:auto" %)
504 |=(% colspan="4" %)**Timer interrupt mask register**
505 |**Special register number**|**Type of interrupt**|**Instruction**|**Default**
506 |SD350|1st to 16th timer interrupt|(((
507 Each bit can control the mask of an interrupt.
508
509 ON: shield interrupts; OFF: interrupt allowed
510 )))|0
511 |SD351|17th to 32th timer interrupt|(((
512 Each bit can control the mask of an interrupt.
513
514 ON: shield interrupts; OFF: interrupt allowed
515 )))|0
516 |SD352|33th to 48th timer interrupt|(((
517 Each bit can control the mask of an interrupt.
518
519 ON: shield interrupts; OFF: interrupt allowed
520 )))|0
521 |SD353|49th to 64th timer interrupt|(((
522 Each bit can control the mask of an interrupt.
523
524 ON: shield interrupts; OFF: interrupt allowed
525 )))|0
526 |SD354|65th to 80th timer interrupt|(((
527 Each bit can control the mask of an interrupt.
528
529 ON: shield interrupts; OFF: interrupt allowed
530 )))|0
531 |SD355|81st to 96th timer interrupt|(((
532 Each bit can control the mask of an interrupt.
533
534 ON: shield interrupts; OFF: interrupt allowed
535 )))|0
536 |SD356|97th to 100th timer interrupt|(((
537 Each bit can control the mask of an interrupt.
538
539 ON: shield interrupts; OFF: interrupt allowed
540 )))|0
541
542 3） High-speed counter interrupt mask register
543
544 |(% colspan="4" %)**High-speed counter interrupt mask register**
545 |**Special register number**|**Type of interrupt**|**Instruction**|**Default**
546 |SD382|1st to 16th high-speed counter interrupt|(((
547 Each bit can control the mask of an interrupt.
548
549 ON: shield interrupts; OFF: interrupt allowed
550 )))|0
551 |SD383|17th to 32nd high-speed counter interrupt|(((
552 Each bit can control the mask of an interrupt.
553
554 ON: shield interrupts; OFF: interrupt allowed
555 )))|0
556 |SD384|33th to 48th high-speed counter interrupt|(((
557 Each bit can control the mask of an interrupt.
558
559 ON: shield interrupts; OFF: interrupt allowed
560 )))|0
561 |SD385|49th to 64th high-speed counter interrupt|(((
562 Each bit can control the mask of an interrupt.
563
564 ON: shield interrupts; OFF: interrupt allowed
565 )))|0
566 |SD386|65th to 80th high-speed counter interrupt|(((
567 Each bit can control the mask of an interrupt.
568
569 ON: shield interrupts; OFF: interrupt allowed
570 )))|0
571 |SD387|81st to 96th high-speed counter interrupt|(((
572 Each bit can control the mask of an interrupt.
573
574 ON: shield interrupts; OFF: interrupt allowed
575 )))|0
576 |SD388|97th to 100th high-speed counter interrupt|(((
577 Each bit can control the mask of an interrupt.
578
579 ON: shield interrupts; OFF: interrupt allowed
580 )))|(((
581 0
582 )))
583
584 === **Subroutine** ===
585
586 ----
587
588 During the execution of the scan program, the executed program can be called by the CALL instruction. You can create up to 100 new subprograms.
589
590 A subroutine is to split a certain module in the main program for the main program to call, which is conducive to the modularization of the program. Such as other high-level language functions, but this function has no parameters and no return value.
591
592 (% style="text-align:center" %)
593 [[image:28.png]]
594
595 (1) Instruction for calling subroutines
596
597 After a new subroutine is created, the content of the program is not executed. It is executed only when the CALL(P) instruction is used to call the subroutine in the scan, event, and interrupt programs, and the call is executed once. Three new subroutines SUB0, SUB1, SUB2 are created as shown in the figure below. In the main program MAIN, the subprogram can be called by using the CALL(P) subprogram program name.
598
599 Through this programming method, the use of the same logic program for different conditions can reduce the number of ladder diagram steps and improve the readability of the ladder diagram.
600
601 (% style="text-align:center" %)
602 [[image:29.png]]
603
604 {{info}}
605 ✎Note:
606
607 1) When using the timer (OUT T), note that the output will not be reset when the subroutine is not called, and a specific subroutine register must be used.
608
609 2) It is not allowed to call recursively between subprograms, that is, call SUB1 in SUB0, and then call SUB0 in SUB1. This is not allowed.
610
611 3) The subroutine can be nested up to 32 levels. If the level exceeds 32 levels, a serious error will be reported and the ladder diagram operation will be forcibly stopped.
612 {{/info}}
613
614 === **Positioning instructions** ===
615
616 ----
617
618 (1) Event
619
620 1) ON event
621
622 If the high-speed pulse instruction is turned on during the ON event, the high-speed pulse instruction will be sent as normal. If the ON contact of the trigger event in the scan period is turned OFF during the pulse sending, select whether to continue sending the pulse or stop the pulse according to the unscanned processing sign bit.
623
624 (% style="margin-left:auto; margin-right:auto" %)
625 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
626 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
627
628 When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. At this time, it should be noted that if the trigger event OFF contact turns ON after the pulse is sent, the pulse will be sent again.
629
630 When the sign bit is 1 (stop sending pulses), if the trigger event ON contact turns OFF in a certain scan period, it will decelerate and stop.
631
632 2) TIME event
633
634 If the high-speed pulse instruction is turned on in the TIME event, the high-speed pulse instruction will be sent as normal. If the instruction is not scanned in a certain scan period during the pulse transmission, select whether to continue sending the pulse or stop the pulse according to the non-scanned sign bit.
635
636 (% style="margin-left:auto; margin-right:auto" %)
637 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
638 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
639
640 When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. In the TIME event, it is impossible to ensure that the instruction is scanned in every scan cycle, so you should avoid using high-speed pulse instructions in the TIME time, otherwise the pulse will be sent again after the pulse is sent.
641
642 When the sign bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the sign bit is set to 1 (stop sending pulses), there will be no pulse sending.
643
644 (2) Subroutine
645
646 If the high-speed pulse instruction is turned on in the subroutine, the high-speed pulse instruction will be sent as normal. If the scanning period is closed during pulse sending, select whether to continue sending or stop the pulse according to the non-scanned sign bit.
647
648 (% style="margin-left:auto; margin-right:auto" %)
649 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
650 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
651
652 When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. At this time, it should be noted that if the subroutine is called again after the pulse is sent, the pulse will be sent again.
653
654 When the sign bit is 1 (stop sending pulses), if the subroutine is closed during high-speed pulse sending, the speed will decelerate and stop. If the subroutine is closed before sending the pulse, then no pulse is sent.
655
656 **（3） Interrupt**
657
658 1） External interrupt
659
660 If the high-speed pulse instruction is enabled in the external interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the non-scanned sign bit.
661
662 (% style="margin-left:auto; margin-right:auto" %)
663 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
664 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
665
666 When the sign bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
667
668 When the sign bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
669
670 2) Timer interrupt
671
672 If the high-speed pulse instruction is turned on in the timer interruption, the high-speed pulse instruction is sent as normal. If the instruction is not scanned in a certain scan period in the pulse transmission, the pulse continues to be sent or the pulse stops is selected according to the non-scanned sign bit.
673
674 (% style="margin-left:auto; margin-right:auto" %)
675 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
676 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
677
678 When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. In the timer interrupt, it is impossible to ensure that the instruction is scanned in every scan cycle, so it is necessary to avoid using high-speed pulse instructions in the T timer interrupt. Otherwise, after the pulse transmission is completed, the pulse will be sent again.
679
680 When the sign bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the sign bit is set to 1 (stop sending pulses), there will be no pulse sending.
681
682 3) HIgh-speed comparison interrupt
683
684 If the high-speed pulse instruction is enabled in the high-speed comparison interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the non-scanned sign bit.
685
686 (% style="margin-left:auto; margin-right:auto" %)
687 |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
688 |=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
689
690 When the sign bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
691
692 When the sign bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
693
694
695
696
697
698
699
700
701