Skip to Content

Changes for page 04 Program flow

Last modified by Devin Chen on 2024/01/28 11:38
From version 4.1
edited by Stone Wu
on 2022/06/15 11:27
Change comment: There is no comment for this version
To version 9.1
edited by Devin Chen
on 2024/01/28 11:38
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.DevinChen
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  
... ... @@ -238,6 +238,8 @@
238 238  (% style="text-align:center" %)
239 239  [[image:4_html_29c8e378dfb34066.png||class="img-thumbnail"]]
240 240  
244 +(% class="box infomessage" %)
245 +(((
241 241  **✎Note: **
242 242  
243 243  • Multiple CALL(P) instructions can call the same subprogram, but subprograms with the same program name are not allowed.
... ... @@ -247,6 +247,7 @@
247 247  • 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.
248 248  
249 249  • 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 +)))
250 250  
251 251  **Error code**
252 252  
... ... @@ -258,7 +258,7 @@
258 258  
259 259  **(1) New subroutine**
260 260  
261 -Project management→Subroutine→ Scan→Right click to create
267 +Project management→Subroutine→Right click to create
262 262  
263 263  (% style="text-align:center" %)
264 264  [[image:4_html_3d0d21476f0bb476.png||class="img-thumbnail"]]
... ... @@ -323,7 +323,7 @@
323 323  • 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.
324 324  
325 325  (% class="table-bordered" %)
326 -|SD151|(% style="width:273px" %)Currently disabled interrupt priority|(% style="width:595px" %)(((
332 +|SD151|(% style="width:297px" %)Currently disabled interrupt priority|(% style="width:571px" %)(((
327 327  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.
328 328  
329 329  0: All priority interrupts are disabled (default);