Changes for page 01 Program execution

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

From 6.1 to 5.1 From 13.12 to 13.11

From version 13.11

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

Change comment: (Autosaved)

To version 6.1

edited by Leo Wei
on 2022/07/13 20:54

Change comment: Renamed from xwiki:PLC Editor2.1 User manual.2\.1 LX5V user manual.01.WebHome

Raw
Rendered

Summary

Page properties (4 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 4 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

Author

@@ -1,1 +1,1 @@
--XWiki.Stone
++XWiki.admin

Content

@@ -1,141 +1,19 @@
--= **Summary** =
++= **Scan structure** =
--This manual has a comprehensive introduction to the basic functions of WECON PLC Editor and the actual use. This book is completely aimed at zero-based readers, is an essential reference book for entry-level readers to quickly and fully grasp WECON PLC and WECON PLC Editor.
--
--This book starts from the basic product of WECON PLC and the basic concept and operation of WECON PLC Editor. It combines with a large number of cases and graphic analysis to comprehensively and deeply explain the use of WECON PLC Editor Software, as well as PLC program.
--
--WECON technology Co., Ltd. All rights reserved.
--
--= Precautions =
--
--Before the installation, operation, maintenance and repair of the micro programmable control, please read this manual and other related manuals to ensure correct use. Please use it after you have mastered the operation method, safety information and all
--
--== Design ==
--
--In the event of an abnormality in the external power supply or failure of the programmable controller, to ensure the safe operation of the entire system, be sure to install a safety circuit outside the programmable controller.
--
--1. Be sure to install an emergency brake circuit, a protection circuit, an interlock circuit for reverse operation, such as an emergency brake circuit, a protection circuit, a forward and reverse circuit, and an interlock circuit for the upper and lower positioning limits to prevent machine damage, in the external circuit of the programmable controller.
--1. When the programmable controller CPU detects abnormal conditions such as WDT errors through self-diagnosis, all outputs are shut off. In addition, when the programmable controller CPU cannot detect abnormalities in the input/output control part, etc., it cannot control the output. At this time, in order to make the machine operate safely, please design the external circuit and mechanism.
--1. Due to the failure of the relay and transistor of the output unit, it is impossible to control the state of the output to ON or OFF. In order to ensure the safe operation of the machine, please design external circuits and mechanisms for output signals related to major accidents.
--
--== 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.
--
--(% class="box infomessage" %)
--(((
--**✎Note:**
--
--* To prevent the temperature from rising, do not install at the bottom, top or vertical direction.Be sure to install it horizontally on the wall as shown on the right.
--* Please leave a space of more than 50mm between the host and other equipment or structures.Try to avoid high-voltage lines, high-voltage equipment, and power equipment.
--)))
--
--== Wiring ==
--
--The signal input and output lines of the programmable controller cannot pass through the same cable.
--
--In addition, signal input lines and output lines cannot pass through the same pipeline with other power lines and output lines, and cannot be bundled together.
--
--If implemented according to the above precautions, even if the input and output wiring is as long as 50 to 100m, there is almost no noise problem. But generally for safety, the wiring length should be within 20m.
--
--(% style="text-align:center" %)
--[[image:PLC Editor2.01 Program execution.WebHome@1652145475206-244.png||height="179" width="200" class="img-thumbnail"]]
--
--(% class="box infomessage" %)
--(((
--**✎Note:**
--
--* The installation and wiring must be performed when the external power supply is cut off. Otherwise, it may cause electric shock or product damage.
--* After installation and wiring, etc., the terminal cover must be installed before power-on operation to avoid electric shock.
--)))
--
--(% class="table-bordered" %)
--|=(% scope="row" %)(((
--
--
--
--[[image:PLC Editor2.01 Program execution.WebHome@1652145267405-613.png||class="img-thumbnail"]]
--
--**Danger**
--)))|(((
--(% style="text-align:center" %)
--[[image:PLC Editor2.01 Program execution.WebHome@0-1.png||height="141" width="400" class="img-thumbnail"]]
--
--It is very dangerous to close the positive and negative contactors at the same time. For loads like this, in addition to the interlock set by the internal program of the programmable controller, the interlock shown above must also be set outside the programmable controller.
--)))
--|=(((
--  [[image:PLC Editor2.01 Program execution.WebHome@1652145275238-798.png||height="45" width="50" class="img-thumbnail"]]
--
--**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.
--
--**Attached**
--
--The programmable controller will continue to work if there is an instantaneous power failure of less than 10ms.
--
--When the power is cut for a long time or the voltage is low, the programmable controller will stop working and the output will turn OFF, but once the power supply is restored, it will automatically restart.
--
--== Startup and maintenance ==
--
--(% class="table-bordered" %)
--(% class="warning" %)|=**Danger**
--|(((
--Please do not touch the terminals when the power is on, otherwise it may cause electric shock or misoperation.
--
--Please clean and disassemble the terminal after the power is turned off. Performing it while the power is on may cause electric shock.
--
--Please read the manual thoroughly and fully confirm the safety before proceeding with program changes, forced output, RUN/STOP, etc. during machine operation.
--
--Operation errors can damage the machine and cause accidents.
--)))
--
--(% class="table-bordered" %)
--(% class="warning" %)|=**Caution**
--|(((
--Please do not disassemble or modify, otherwise it may cause malfunction, malfunction, fire.
--
--※For repair matters, please contact Fuzhou Wecon Electronic Technology Co., Ltd.
--
--After the power is turned off, perform the installation and disassembly of the extension cables and other connecting cables, otherwise it may cause malfunctions and malfunctions.
--)))
--
--== **Maintenance** ==
--
--Regular inspection: Whether the programmable controller is equipped with consumables with a shorter life.
--
--For relay output type, if the output relay works abnormally at a high frequency or drives a large-capacity load, you must pay attention to its impact on the service life.
--
--Check with other equipment, please pay attention to the following points:
--
--* Whether there is an abnormal increase in the temperature inside the machine due to other heating elements or direct sunlight.
--* Whether dust or conductive dust has penetrated into the machine.
--* Whether there are loose wiring and terminals or other abnormalities
--
--= Scan structure =
--
  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"]]
--== Initialization ==
++== **Initialization** ==
  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|√|×|×
@@ -142,25 +142,25 @@
  |Device initialization|√|×|√
  |Error clear|√|×|√
--== Input and output point refresh ==
++== **Input and output point refresh** ==
  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**
  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.
@@ -169,7 +169,7 @@
  * 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.
@@ -178,14 +178,16 @@
  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.
--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 flow of each procedure =
++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.
  (% style="text-align:center" %)
@@ -195,15 +195,14 @@
  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:**
--= Types of program execution =
++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.
--== Scan execution program ==
++= **Types of program execution** =
++== **Scan execution program** ==
++
  Each scan is executed only once from the next scan of the initial execution type program.
  (% style="text-align:center" %)
@@ -218,16 +218,16 @@
  (% 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"]]
--== Event execution program ==
++== **Event execution program** ==
  It uses the event specified by the user as a condition to trigger the program to start execution.
@@ -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
@@ -329,65 +329,82 @@
  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.
--* 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.
++      ~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.
  (% style="text-align:center" %)
  [[image:1652249587490-678.png||class="img-thumbnail"]]
--* 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.
++      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.
--**The actions when an interruption cause occurs are as follows:**
++      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.
--* 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.
++      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.
++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"]]
--* 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.
++      3. When an interrupt occurs during the waiting time when performing constant scan.
++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"]]
--* 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.
++     6. 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.
++
  **Interrupt trigger condition classification**
--* **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. **External input (X) interrupt**
++**~      **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"]]
--* 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):
++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):
++
  (% style="text-align:center" %)
  [[image:1-17.png||class="img-thumbnail"]]
@@ -407,7 +407,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
--* Write interrupt execution program
++1. Write interrupt execution program
  (% style="text-align:center" %)
  [[image:1-18.png||class="img-thumbnail"]]
@@ -417,7 +417,7 @@
  (% style="text-align:center" %)
  [[image:1652250056160-117.png||height="215" width="500" class="img-thumbnail"]]
--**Timer interrupt**
++**~      2.Timer interrupt**
 . Timer interrupt description
@@ -503,33 +503,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
@@ -681,7 +681,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.
@@ -706,7 +706,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

0-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.admin

Size

...	...	@@ -1,1 +1,0 @@
1		-40.3 KB

Content

1652145267405-613.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.admin

Size

...	...	@@ -1,1 +1,0 @@
1		-4.0 KB

Content

1652145275238-798.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.admin

Size

...	...	@@ -1,1 +1,0 @@
1		-1.6 KB

Content

1652145475206-244.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.admin

Size

...	...	@@ -1,1 +1,0 @@
1		-19.7 KB

Content

Changes for page 01 Program execution

Summary

Details

Navigation

Table of Contents