Changes for page 04 Program flow
Last modified by Devin Chen on 2024/01/28 11:38
From version 9.1
edited by Devin Chen
on 2024/01/28 11:38
on 2024/01/28 11:38
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -04 Program flow 1 +04 Program flow instructions - 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. DevinChen1 +XWiki.Stone - Content
-
... ... @@ -38,8 +38,6 @@ 38 38 1. Each scan is executed. 39 39 1. One scan is executed. 40 40 41 -(% class="box infomessage" %) 42 -((( 43 43 **✎Note: ** 44 44 45 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. ... ... @@ -47,7 +47,6 @@ 47 47 When the OUT instruction is jumped by the CJ(P) instruction, the scan time will be shorter. 48 48 49 49 When the CJ(P) instruction is used to jump backward, the scan time will be longer. 50 -))) 51 51 52 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 53 ... ... @@ -241,8 +241,6 @@ 241 241 (% style="text-align:center" %) 242 242 [[image:4_html_29c8e378dfb34066.png||class="img-thumbnail"]] 243 243 244 -(% class="box infomessage" %) 245 -((( 246 246 **✎Note: ** 247 247 248 248 • Multiple CALL(P) instructions can call the same subprogram, but subprograms with the same program name are not allowed. ... ... @@ -252,7 +252,6 @@ 252 252 • 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. 253 253 254 254 • 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 -))) 256 256 257 257 **Error code** 258 258 ... ... @@ -264,7 +264,7 @@ 264 264 265 265 **(1) New subroutine** 266 266 267 -Project management→Subroutine→Right click to create 261 +Project management→Subroutine→ Scan→Right click to create 268 268 269 269 (% style="text-align:center" %) 270 270 [[image:4_html_3d0d21476f0bb476.png||class="img-thumbnail"]] ... ... @@ -329,7 +329,7 @@ 329 329 • 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. 330 330 331 331 (% class="table-bordered" %) 332 -|SD151| (% style="width:297px" %)Currently disabled interrupt priority|(% style="width:571px" %)(((326 +|SD151|Currently disabled interrupt priority|((( 333 333 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. 334 334 335 335 0: All priority interrupts are disabled (default); ... ... @@ -339,7 +339,7 @@ 339 339 2: Priority 2 interrupt is prohibited; 340 340 341 341 3: All priority interrupts are allowed 342 -)))| (% style="width:148px" %)R(read only)336 +)))|R(read only) 343 343 344 344 A: Sequence control program 345 345