Changes for page 01 Program execution

Last modified by Jiahao Lai on 2025/07/18 17:39

From 13.1 to 12.1 From 13.11 to 13.10

From version 13.10

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

Change comment: There is no comment for this version

To version 13.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -20,11 +20,14 @@
  == Installation ==
--* 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.
++1. 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.
++
++      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:**
@@ -72,11 +72,14 @@
  **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.
--* 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.
++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.
++
  **Attached**
  The programmable controller will continue to work if there is an instantaneous power failure of less than 10ms.
@@ -130,12 +130,11 @@
  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|√|×|×
@@ -146,11 +146,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**
@@ -182,8 +182,10 @@
  It is the first scan time of the CPU module in RUN.
--Process as the following way: The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
++Process as the following way:
++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.
@@ -195,11 +195,10 @@
  When the execution types of the programs are the same, they are executed in the order set in the execution order.
--(% 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.
--)))
++**✎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.
++
  = Types of program execution =
  == Scan execution program ==
@@ -218,11 +218,11 @@
  (% style="text-align:center" %)
  [[image:1-5.png||height="372" width="300" class="img-thumbnail"]]
--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.
++* 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.
  (% style="text-align:center" %)
  [[image:1-6.png||class="img-thumbnail"]]
@@ -238,7 +238,7 @@
  The trigger of event execution type program is as follows.
--**ON event of bit data (TRUE)**
++**(1) 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.
@@ -254,13 +254,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.
--**TIME event**
++**(2) 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.
@@ -285,7 +285,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 /%$@&=~~`^<>?:{}[],;!*.~\~\'" character input.
++* The program name does not support /%$@&=to`^<>?:{}[],;!*.~\~\'" 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.
@@ -300,26 +300,26 @@
  (% style="text-align:center" %)
  [[image:1-11.png||height="419" width="500" class="img-thumbnail"]]
--**Configuration instructions:**
++Configuration instructions:
-- Configuration interface
++ 1) Configuration interface
  (% style="text-align:center" %)
  [[image:1-12.png||height="372" width="300" class="img-thumbnail"]]
--Parameter content:
++2) Parameter content:
  (% class="table-bordered" %)
--|=(% 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" %)(((
++|(% 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.|(((
  True
  False
  )))|False
--|(% 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" %)(((
++|(% 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).|(((
  True
  False
@@ -382,9 +382,9 @@
  **Interrupt trigger condition classification**
--**External input (X) interrupt**
++1. **External input (X) interrupt**
--Description of external input interrupt
++**~      **1. 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.
@@ -392,15 +392,15 @@
 . 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.
++      2. External input interrupt steps.
--Project management→ Program→ Interrupt→ right click to create.
++Project management→ Program→ Interrupt→ right click to create
  (% style="text-align:center" %)
  [[image:1-16.png||class="img-thumbnail"]]
 . 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 /%$@&=~~`^<>?:{}[],;!*.~\~\'" characters,
++1. The interrupt program name does not support the input of /%$@&=to`^<>?:{}[],;!*.~\~\'" characters,
 . 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):
@@ -520,33 +520,33 @@
 . Description of triggering rules
  (% class="table-bordered" %)
--|(% 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" %)(((
++|**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" %)(((
  Comparison value: -50,000
  Contact: Y10
--)))|(% style="width:128px" %)-50001 → -50000|(% style="width:324px" %)(((
++)))|-50001 → -50000|(((
  Y10 is immediately set and mapped to the actual output (not affected by the scan period)
  The program in INT1 will not be executed
  )))
--|(% style="width:128px" %)-49999 → -50000|(% style="width:324px" %)(((
++|-49999 → -50000|(((
  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" style="width:135px" %)High-speed comparison reset (INT2)|(% rowspan="2" style="width:187px" %)(((
++|(% rowspan="2" %)High-speed comparison reset (INT2)|(% rowspan="2" %)(((
  Comparison value: 400000
  Contact: Y10
--)))|(% style="width:128px" %)399999 → 400000|(% style="width:324px" %)(((
++)))|399999 → 400000|(((
  Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
  The program in INT2 will not be executed
  )))
--|(% style="width:128px" %)400001 → 400000|(% style="width:324px" %)(((
++|400001 → 400000|(((
  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