Changes for page 01 Program execution

Last modified by Leo Wei on 2024/12/24 22:42

From 9.1 to 8.4

From version 8.4

edited by Leo Wei
on 2022/07/28 15:57

Change comment: Update document after refactoring.

To version 1.1

edited by Leo Wei
on 2022/06/08 12:57

Change comment: Imported from XAR

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--01 Program execution
++01  Execution of the program

Parent

@@ -1,1 +1,1 @@
--PLC Editor2.WebHome
++PLC Editor2.1 User manual.2\.1 LX5V user manual.WebHome

Content

@@ -1,11 +1,11 @@
--= Scan structure =
++= **The composition of the scan** =
  The scan configuration of the CPU module is as follows.
  (% style="text-align:center" %)
--[[image:1-1.png||height="455" width="700" class="img-thumbnail"]]
++[[image:1-1.png||class="img-thumbnail" height="455" width="700"]]
--== Initialization ==
++== **Initialization** ==
  The initialization based on the status of the CPU module is as follows.
@@ -20,7 +20,7 @@
  |Device initialization|√|×|√
  |Error clear|√|×|√
--== Input and output point refresh ==
++== **Input and output point refresh** ==
  Perform the following before starting program calculation.
@@ -34,11 +34,11 @@
  When performing a constant scan, the I/O refresh is performed after the waiting time of the constant scan.
--== Operation of the program ==
++== **Operation of the program** ==
  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.
--== END processing ==
++== **END processing** ==
  Perform the following processing.
@@ -47,16 +47,16 @@
  * Communication processing
  * Setting the value of special relay/special register (when the setting timing is END processing)
--= Scan time =
++= **Scan time** =
  The CPU module repeats the following processing, and the scan time is the total of the following processing and execution time.
  (% style="text-align:center" %)
--[[image:1-2.png||height="349" width="400" class="img-thumbnail"]]
++[[image:1-2.png||class="img-thumbnail" height="349" width="400"]]
  The initial scan time indicates the time including this processing.
--== Initial scan time ==
++== **Initial scan time** ==
  It is the first scan time of the CPU module in RUN.
@@ -64,12 +64,12 @@
  The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
--= The flow of each procedure =
++= **The flow of each procedure** =
  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.
  (% style="text-align:center" %)
--[[image:1652241271896-263.png||height="344" width="500" class="img-thumbnail"]]
++[[image:1652241271896-263.png||class="img-thumbnail" height="344" width="500"]]
  **Key points**
@@ -79,14 +79,14 @@
  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.
--= Types of program execution =
++= **Types of program execution** =
--== Scan execution program ==
++== **Scan execution program** ==
  Each scan is executed only once from the next scan of the initial execution type program.
  (% style="text-align:center" %)
--[[image:1-4.png||height="325" width="700" class="img-thumbnail"]]
++[[image:1-4.png||class="img-thumbnail" height="325" width="700"]]
  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.
@@ -95,7 +95,7 @@
  "Project Management"→ "Program"→ "Scan"→ Right click to create
  (% style="text-align:center" %)
--[[image:1-5.png||height="372" width="300" class="img-thumbnail"]]
++[[image:1-5.png||class="img-thumbnail" height="372" width="300"]]
  * 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).
  * The input of /%$@&=to`^<>?:{}[],;!*.~\~\'" is not supported. It cannot exceed 64 characters. The default name is MAINx.
@@ -106,7 +106,7 @@
  (% style="text-align:center" %)
  [[image:1-6.png||class="img-thumbnail"]]
--== Event execution program ==
++== **Event execution program** ==
  It uses the event specified by the user as a condition to trigger the program to start execution.
@@ -177,7 +177,7 @@
 . Project management→ Program→ Parameter → Program parameter→Configuration
  (% style="text-align:center" %)
--[[image:1-11.png||height="419" width="500" class="img-thumbnail"]]
++[[image:1-11.png||class="img-thumbnail" height="419" width="500"]]
  Configuration instructions:
@@ -184,7 +184,7 @@
 ) Configuration interface
  (% style="text-align:center" %)
--[[image:1-12.png||height="372" width="300" class="img-thumbnail"]]
++[[image:1-12.png||class="img-thumbnail" height="372" width="300"]]
 ) Parameter content:
@@ -208,7 +208,7 @@
  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.
--== Interrupt execution program ==
++== **Interrupt execution program** ==
  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.
@@ -311,7 +311,7 @@
  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.
  (% style="text-align:center" %)
--[[image:1652250056160-117.png||height="215" width="500" class="img-thumbnail"]]
++[[image:1652250056160-117.png||class="img-thumbnail" height="215" width="500"]]
  **~      2.Timer interrupt**
@@ -577,7 +577,7 @@
  ON: Mask interrupt OFF: Enable interrupt
  )))|0
--== Subroutine ==
++== **Subroutine** ==
  During the execution of the scan program, the executed program can be called by the CALL instruction.
@@ -602,7 +602,7 @@
 . The subroutine can be nested up to 32 levels. If the level exceeds 32 levels, a serious error will be reported and the Circuit program operation will be forcibly stopped.
 . Unlike the LX3V series mainframe, the subroutine in the LX5V series mainframe ends with the END instruction instead of SRET.
--== Positioning instructions ==
++== **Positioning instructions** ==
        ~1. Event

Changes for page 01 Program execution

Summary

Details

Navigation

Table of Contents