Changes for page 01 Program execution

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

From 12.1 to 13.1 From 13.11 to 13.12

From version 13.1

edited by Stone Wu
on 2022/07/28 16:50

Change comment: There is no comment for this version

To version 13.11

edited by Stone Wu
on 2022/09/23 16:05

Change comment: (Autosaved)

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -20,14 +20,11 @@
  == Installation ==
--1. Please use it in the general specification environment described in the manual.
++* Please use it in the general specification environment described in the manual.
++** Do not use in the following places: places with dust, oily smoke, conductive dust, corrosive gas, flammable gas; places  exposed to high temperature, condensation, wind and rain; places with vibration or impact. Electric shock, fire, and misoperation can also cause product damage.
++* When processing screw holes and wiring, do not let iron filings or wire ends fall into the ventilation window of the programmable controller. It may cause fire, malfunction, or misoperation.
++* Please insert the connecting cable and display module accurately into the specified sockets. Poor contact may cause misoperation.
--Do not use in the following places: places with dust, oily smoke, conductive dust, corrosive gas, flammable gas; places  exposed to high temperature, condensation, wind and rain; places with vibration or impact. Electric shock, fire, and misoperation can also cause product damage.
--
--      2. When processing screw holes and wiring, do not let iron filings or wire ends fall into the ventilation window of the programmable controller. It may cause fire, malfunction, or misoperation.
--
--      3. Please insert the connecting cable and display module accurately into the specified sockets. Poor contact may cause misoperation.
--
  (% class="box infomessage" %)
  (((
  **✎Note:**
@@ -75,14 +75,11 @@
  **Attention**
  )))|Do not connect the empty terminal to the outside, otherwise the product will be damaged.
--Please connect the AC power supply to the dedicated terminal according to the content in the manual.
++* Please connect the AC power supply to the dedicated terminal according to the content in the manual.
++* If the AC power supply is connected to the DC input/output terminal or the DC power supply terminal, the programmable controller will be burnt out.
++* Please do not supply power to the 24+ terminal of the basic unit from the external power supply, and to the empty terminal    . Do not wire from the outside, otherwise the product will be damaged.
++* Please ground the ground terminal of the basic unit according to the third method. But please do not share the ground with the strong current system.
--If the AC power supply is connected to the DC input/output terminal or the DC power supply terminal, the programmable controller will be burnt out.
--
--Please do not supply power to the 24+ terminal of the basic unit from the external power supply, and to the empty terminal    . Do not wire from the outside, otherwise the product will be damaged.
--
--Please ground the ground terminal of the basic unit according to the third method. But please do not share the ground with the strong current system.
--
  **Attached**
  The programmable controller will continue to work if there is an instantaneous power failure of less than 10ms.
@@ -136,11 +136,12 @@
  The initialization based on the status of the CPU module is as follows.
--**√**: execute. **×**: not execute
++* **√**: execute
++*  **×**: not execute
  (% class="table-bordered" %)
--|(% rowspan="2" %)**Processing item**|(% colspan="3" %)**Status of the CPU module**
--|**When the power is ON**|**STOP**|**When STOP RUN**
++|=(% rowspan="2" %)**Processing item**|=(% colspan="3" %)**Status of the CPU module**
++|=**When the power is ON**|=**STOP**|=**When STOP RUN**
  |Initialization of input and output modules|√|×|×
  |CPU parameter check|√|×|×
  |Check of system parameters|√|×|×
@@ -151,11 +151,11 @@
  Perform the following before starting program calculation.
--Update the actual input point of the PLC to the input relay X.
++* Update the actual input point of the PLC to the input relay X.
  The following is executed after the END instruction is executed.
--Update the PLC output relay Y to the actual output point.
++* Update the PLC output relay Y to the actual output point.
  **Key points**
@@ -187,10 +187,8 @@
  It is the first scan time of the CPU module in RUN.
--Process as the following way:
++Process as the following way: The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
--The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
--
  = 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.
@@ -202,10 +202,11 @@
  When the execution types of the programs are the same, they are executed in the order set in the execution order.
--**✎Note:**
++(% class="box infomessage" %)
++(((
++**✎Note:** 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.
++)))
--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 =
  == Scan execution program ==
@@ -224,11 +224,11 @@
  (% style="text-align:center" %)
  [[image:1-5.png||height="372" width="300" class="img-thumbnail"]]
--* 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.
--* The number of scan programs that can be built is limited to 100.
--* Each scan program has been END ended, but only the last END instruction is completed to calculate a scan cycle.
--* The execution sequence runs from top to bottom in the order of creation.
++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).
++1. The input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" is not supported. It cannot exceed 64 characters. The default name is MAINx.
++1. The number of scan programs that can be built is limited to 100.
++1. Each scan program has been END ended, but only the last END instruction is completed to calculate a scan cycle.
++1. The execution sequence runs from top to bottom in the order of creation.
  (% style="text-align:center" %)
  [[image:1-6.png||class="img-thumbnail"]]
@@ -244,7 +244,7 @@
  The trigger of event execution type program is as follows.
--**(1) ON event of bit data (TRUE)**
++**ON event of bit data (TRUE)**
  * 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.
  * The ON event program will only be executed once in a single scan cycle.
@@ -260,13 +260,13 @@
  The devices that can be specified are as follows.
  (% class="table-bordered" %)
--|(% colspan="2" %)**Project**|**Content**
++|=(% colspan="2" %)**Project**|=**Content**
  |(% rowspan="2" %)Device *1|Bit Device|X, Y, M, SM
  |Bit specification of word device|D.b
  *1 The indexed device cannot be specified.
--**(2) TIME event**
++**TIME event**
  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.
@@ -291,7 +291,7 @@
  Event program name:
  * 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).
--* The program name does not support /%$@&=to`^<>?:{}[],;!*.~\~\'" character input.
++* The program name does not support /%$@&=~~`^<>?:{}[],;!*.~\~\'" character input.
  * The length of the program name cannot exceed 64 characters. The default name is EVENTx.
  A maximum of 100 new event programs could be created.
@@ -306,26 +306,26 @@
  (% style="text-align:center" %)
  [[image:1-11.png||height="419" width="500" class="img-thumbnail"]]
--Configuration instructions:
++**Configuration instructions:**
-- 1) Configuration interface
++ Configuration interface
  (% style="text-align:center" %)
  [[image:1-12.png||height="372" width="300" class="img-thumbnail"]]
--2) Parameter content:
++Parameter content:
  (% class="table-bordered" %)
--|(% colspan="2" %)**Project**|**Content**|**Setting range**|**Default**
--|(% colspan="2" %)Execution type|Select event type|Not set/ON event/TIME event|Not set
--|(% 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|
--|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.|(((
++|=(% colspan="2" %)**Project**|=(% style="width: 654px;" %)**Content**|=(% style="width: 190px;" %)**Setting range**|=**Default**
++|(% colspan="2" %)Execution type|(% style="width:654px" %)Select event type|(% style="width:190px" %)Not set/ON event/TIME event|Not set
++|(% rowspan="2" %)ON event|Contact|(% style="width:654px" %)The event type can be set when ON event is selected. Set the bit device as the trigger condition.|(% style="width:190px" %)X/Y/M/SM/D.b|
++|Whether to clear|(% style="width:654px" %)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.|(% style="width:190px" %)(((
  True
  False
  )))|False
--|(% rowspan="2" %)TIME event|Time|Set how long to execute the event program once.|1 to 2147483647 (100us unit)|
--|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).|(((
++|(% rowspan="2" %)TIME event|Time|(% style="width:654px" %)Set how long to execute the event program once.|(% style="width:190px" %)1 to 2147483647 (100us unit)|
++|Whether to clear|(% style="width:654px" %)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).|(% style="width:190px" %)(((
  True
  False
@@ -339,78 +339,61 @@
  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.
--      ~1. 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.
++* 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.
  (% style="text-align:center" %)
  [[image:1652249587490-678.png||class="img-thumbnail"]]
--      2. 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.
++* 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.
++* Interrupt has the characteristic of interrupting the original execution program and executing the interrupt first, but it cannot interrupt the interrupt program being executed.
++*  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.
--      3. Interrupt has the characteristic of interrupting the original execution program and executing the interrupt first, but it cannot interrupt the interrupt program being executed.
++**The actions when an interruption cause occurs are as follows:**
--      4. 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.
++* Interrupt prohibition (DI) when an interruption cause occurs.
++** 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.
++*  When multiple interrupt causes occur simultaneously in the interrupt enabled state.
++** 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.
++** 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.
--The actions when an interruption cause occurs are as follows:
--
--1. Interrupt prohibition (DI) when an interruption cause occurs.
--
--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.
--
--      2.When multiple interrupt causes occur simultaneously in the interrupt enabled state.
--
--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.
--
--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.
--
  (% style="text-align:center" %)
  [[image:1652249553246-688.png||class="img-thumbnail"]]
--      3. When an interrupt occurs during the waiting time when performing constant scan.
++* When an interrupt occurs during the waiting time when performing constant scan.
++** Execute the interrupt program for this interrupt.
++* When other interrupts occur during the execution of the interrupt program.
++** 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.
++* During the execution of the interrupt program, when an interrupt cause with a low priority or the same priority occurs.
++** 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.
--Execute the interrupt program for this interrupt.
--     4.When other interrupts occur during the execution of the interrupt program.
--
--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.
--
--     5. During the execution of the interrupt program, when an interrupt cause with a low priority or the same priority occurs.
--
--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.
--
--
  (% style="text-align:center" %)
  [[image:1652249673420-476.png||class="img-thumbnail"]]
--     6. When the same interruption cause occurs during the execution of the interrupt program;
++* When the same interruption cause occurs during the execution of the interrupt program;
++** 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.
--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.
--
  **Interrupt trigger condition classification**
--1. **External input (X) interrupt**
++* **External input (X) interrupt**
++** Description of external input interrupt
++*** The external input interrupt is triggered by the rising or falling edge of the fixed X point input.
++*** 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.
++*** The same interrupt trigger condition cannot create multiple interrupt programs.
++*** External input interrupt and high-speed counter cannot use the same X point.
++*** You must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
++* **External input interrupt steps.**
++** Project management→ Program→ Interrupt→ right click to create.
++** 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),
++** The interrupt program name does not support the input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" characters,
++** The length of the interrupt program name cannot exceed 64 characters and cannot be typed. The default name is INTx.
--**~      **1. Description of external input interrupt
--
--1. The external input interrupt is triggered by the rising or falling edge of the fixed X point input.
--1. 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.
--1. The same interrupt trigger condition cannot create multiple interrupt programs.
--1. External input interrupt and high-speed counter cannot use the same X point.
--1. You must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
--
--      2. External input interrupt steps.
--
--Project management→ Program→ Interrupt→ right click to create
--
  (% style="text-align:center" %)
  [[image:1-16.png||class="img-thumbnail"]]
--1. 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),
--1. The interrupt program name does not support the input of /%$@&=to`^<>?:{}[],;!*.~\~\'" characters,
--1. The length of the interrupt program name cannot exceed 64 characters and cannot be typed. The default name is INTx.
++* Click Configure, and select external interrupt for execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management):
--Click Configure, and select external interrupt for execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management):
--
  (% style="text-align:center" %)
  [[image:1-17.png||class="img-thumbnail"]]
@@ -430,7 +430,7 @@
  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.
  )))|0 to 1700|1
--1. Write interrupt execution program
++* Write interrupt execution program
  (% style="text-align:center" %)
  [[image:1-18.png||class="img-thumbnail"]]
@@ -440,7 +440,7 @@
  (% style="text-align:center" %)
  [[image:1652250056160-117.png||height="215" width="500" class="img-thumbnail"]]
--**~      2.Timer interrupt**
++**Timer interrupt**
 . Timer interrupt description
@@ -526,33 +526,33 @@
 . Description of triggering rules
  (% class="table-bordered" %)
--|**Mode**|**Configuration**|**The current value**|**Action**
--|(% rowspan="2" %)High-speed compare interrupt (INT0)|(% rowspan="2" %)Comparison value: 10000|9999 → 10000|Execute all programs in interrupt INT0
--|10001 → 10000|Execute all programs in interrupt INT0
--|(% rowspan="2" %)High-speed comparison set (INT1)|(% rowspan="2" %)(((
++|(% style="width:135px" %)**Mode**|(% style="width:187px" %)**Configuration**|(% style="width:128px" %)**The current value**|(% style="width:324px" %)**Action**
++|(% rowspan="2" style="width:135px" %)High-speed compare interrupt (INT0)|(% rowspan="2" style="width:187px" %)Comparison value: 10000|(% style="width:128px" %)9999 → 10000|(% style="width:324px" %)Execute all programs in interrupt INT0
++|(% style="width:128px" %)10001 → 10000|(% style="width:324px" %)Execute all programs in interrupt INT0
++|(% rowspan="2" style="width:135px" %)High-speed comparison set (INT1)|(% rowspan="2" style="width:187px" %)(((
  Comparison value: -50,000
  Contact: Y10
--)))|-50001 → -50000|(((
++)))|(% style="width:128px" %)-50001 → -50000|(% style="width:324px" %)(((
  Y10 is immediately set and mapped to the actual output (not affected by the scan period)
  The program in INT1 will not be executed
  )))
--|-49999 → -50000|(((
++|(% style="width:128px" %)-49999 → -50000|(% style="width:324px" %)(((
  Y10 is immediately set and mapped to the actual output (not affected by the scan period)
  The program in INT1 will not be executed
  )))
--|(% rowspan="2" %)High-speed comparison reset (INT2)|(% rowspan="2" %)(((
++|(% rowspan="2" style="width:135px" %)High-speed comparison reset (INT2)|(% rowspan="2" style="width:187px" %)(((
  Comparison value: 400000
  Contact: Y10
--)))|399999 → 400000|(((
++)))|(% style="width:128px" %)399999 → 400000|(% style="width:324px" %)(((
  Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
  The program in INT2 will not be executed
  )))
--|400001 → 400000|(((
++|(% style="width:128px" %)400001 → 400000|(% style="width:324px" %)(((
  Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
  The program in INT2 will not be executed

Changes for page 01 Program execution

Summary

Details

Navigation

Table of Contents