Changes for page 04 Program flow

Last modified by Devin Chen on 2024/01/28 11:38

From version 2.1
edited by Stone Wu
on 2022/06/15 11:26
Change comment: There is no comment for this version
To version 8.1
edited by Mora Zhou
on 2023/11/22 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -04 Program flow instructions
1 +04 Program flow
Parent
... ... @@ -1,1 +1,1 @@
1 -PLC Editor2.1 User manual.2\.1 LX5V user manual.WebHome
1 +PLC Editor2.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Stone
1 +XWiki.Mora
Content
... ... @@ -38,6 +38,8 @@
38 38  1. Each scan is executed.
39 39  1. One scan is executed.
40 40  
41 +(% class="box infomessage" %)
42 +(((
41 41  **✎Note: **
42 42  
43 43  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.
... ... @@ -45,6 +45,7 @@
45 45  When the OUT instruction is jumped by the CJ(P) instruction, the scan time will be shorter.
46 46  
47 47  When the CJ(P) instruction is used to jump backward, the scan time will be longer.
50 +)))
48 48  
49 49  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.
50 50  
... ... @@ -213,15 +213,13 @@
213 213  (% class="table-bordered" %)
214 214  |(% rowspan="2" %)**Instruction**|(% rowspan="2" %)**Parameter**|(((
215 215  **Offset modification**
216 -)))|(((
219 +)))|(% style="width:211px" %)(((
217 217  **Pulse extension**
218 -)))|**other**
219 -|**[D]**|**XXP**|(((
220 -**Subroutine**
221 -
222 -**name**
221 +)))|(% style="width:214px" %)**other**
222 +|**[D]**|(% style="width:211px" %)**XXP**|(% style="width:214px" %)(((
223 +**Subroutine name**
223 223  )))
224 -|CALL|Parameter 1| |●|●
225 +|CALL|Parameter 1| |(% style="width:211px" %)●|(% style="width:214px" %)
225 225  
226 226  Parameter 1 can only use the subroutine name.
227 227  
... ... @@ -240,6 +240,8 @@
240 240  (% style="text-align:center" %)
241 241  [[image:4_html_29c8e378dfb34066.png||class="img-thumbnail"]]
242 242  
244 +(% class="box infomessage" %)
245 +(((
243 243  **✎Note: **
244 244  
245 245  • Multiple CALL(P) instructions can call the same subprogram, but subprograms with the same program name are not allowed.
... ... @@ -249,6 +249,7 @@
249 249  • 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.
250 250  
251 251  • 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.
255 +)))
252 252  
253 253  **Error code**
254 254  
... ... @@ -325,7 +325,7 @@
325 325  • 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.
326 326  
327 327  (% class="table-bordered" %)
328 -|SD151|Currently disabled interrupt priority|(((
332 +|SD151|(% style="width:297px" %)Currently disabled interrupt priority|(% style="width:571px" %)(((
329 329  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.
330 330  
331 331  0: All priority interrupts are disabled (default);
... ... @@ -335,7 +335,7 @@
335 335  2: Priority 2 interrupt is prohibited;
336 336  
337 337  3: All priority interrupts are allowed
338 -)))|R(read only)
342 +)))|(% style="width:148px" %)R(read only)
339 339  
340 340  A: Sequence control program
341 341