Changes for page 01 Program execution

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

From 13.7 to 13.8 From 19.1 to 20.1

From version 13.8

edited by Stone Wu
on 2022/09/23 15:55

Change comment: (Autosaved)

To version 19.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -218,11 +218,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 /%$@&=~~`^<>?:{}[],;!*.~\~\'" 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"]]
@@ -238,7 +238,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.
@@ -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.
--**(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.
@@ -300,26 +300,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
@@ -333,78 +333,60 @@
  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**
--**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.
--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.
--
--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 /%$@&=~~`^<>?:{}[],;!*.~\~\'" 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"]]
@@ -424,7 +424,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"]]
@@ -434,19 +434,19 @@
  (% style="text-align:center" %)
  [[image:1652250056160-117.png||height="215" width="500" class="img-thumbnail"]]
--**~      2.Timer interrupt**
++**Timer interrupt**
--1. Timer interrupt description
++Timer interrupt description
--1. Timer interrupt is based on the set time, execute the interrupt program every this time, the minimum time interval can reach 100us.
--1. Up to 100 timer interrupt execution programs can be created.
--1. Each timer interrupt program is independent of each other and does not affect each other.
--1. Each timer interrupt program should be configured with priority. When triggered at the same time, it is executed in the order of priority, but when the priority is the same, it is executed in the order of the established program.
--1. The interrupt execution program is executed only after EI is used in the scanner to allow the interrupt
++* Timer interrupt is based on the set time, execute the interrupt program every this time, the minimum time interval can reach 100us.
++* Up to 100 timer interrupt execution programs can be created.
++* Each timer interrupt program is independent of each other and does not affect each other.
++* Each timer interrupt program should be configured with priority. When triggered at the same time, it is executed in the order of priority, but when the priority is the same, it is executed in the order of the established program.
++* The interrupt execution program is executed only after EI is used in the scanner to allow the interrupt
--      2. Timer interrupt step
++Timer interrupt step
--Project managementðProgramðInterruptðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure and select Timer Interrupt as the execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management).
++* Project managementðProgramðInterruptðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure and select Timer Interrupt as the 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-20.png||class="img-thumbnail"]]
@@ -457,34 +457,35 @@
  |(% rowspan="2" %)Timer interrupt|Time|Set the interval time for interrupt triggering|1 to 2147483647 (100us unit)|
  |priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
--1. Write interrupt execution program
++Write interrupt execution program
  (% style="text-align:center" %)
  [[image:1-21.png||class="img-thumbnail"]]
--Double-click the newly created timer interrupt program in the project management to start writing the interrupt execution program. As shown in the figure above, a newly created timer interrupt program is INT0, and the trigger condition is configured to execute the interrupt program every 10ms. If the main program uses EI to enable interrupts, all instruction programs in INT0 will be executed every 10ms, namely D0 It will add 1 to 10ms.
++* Double-click the newly created timer interrupt program in the project management to start writing the interrupt execution program. As shown in the figure above, a newly created timer interrupt program is INT0, and the trigger condition is configured to execute the interrupt program every 10ms. If the main program uses EI to enable interrupts, all instruction programs in INT0 will be executed every 10ms, namely D0 It will add 1 to 10ms.
  (% style="text-align:center" %)
  [[image:1652250294005-455.png||class="img-thumbnail"]]
--**~      3. High-speed counter interrupt**
++**High-speed counter interrupt**
--1. Description of high-speed counter interrupt
++Description of high-speed counter interrupt
--1. The high-speed counter interrupt triggers an interrupt condition after the set value of the high-speed counter HSC0 to HSC7 provided by the PLC and executes the interrupt program.
--1. It can support up to 100 high-speed counter interrupt programs, but the number that can be supported by each channel does not need to be fixed.
--1. When using the high-speed counter interrupt, project must configure the high-speed counter and use the OUT HSC instruction to enable the corresponding counting channel to count before it can be used (see the high-speed counter description section for the specific configuration method).
--1. Each high-speed counter interrupt program should be configured with priority. When triggered at the same time, it will be executed in the order of priority. When the priority is the same, it will be executed in the order of channels HSC0-HSC7. When the channel is also the same, it is executed in order according to the creation promise.
--1. Project must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
++* The high-speed counter interrupt triggers an interrupt condition after the set value of the high-speed counter HSC0 to HSC7 provided by the PLC and executes the interrupt program.
++* It can support up to 100 high-speed counter interrupt programs, but the number that can be supported by each channel does not need to be fixed.
++* When using the high-speed counter interrupt, project must configure the high-speed counter and use the OUT HSC instruction to enable the corresponding counting channel to count before it can be used (see the high-speed counter description section for the specific configuration method).
++* Each high-speed counter interrupt program should be configured with priority. When triggered at the same time, it will be executed in the order of priority. When the priority is the same, it will be executed in the order of channels HSC0-HSC7. When the channel is also the same, it is executed in order according to the creation promise.
++* Project must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
--**✎Note: **Both the HSC channel and the external input interrupt channel must use the PLC input point X. It should be noted that it
++(% class="box infomessage" %)
++(((
++**✎Note: **Both the HSC channel and the external input interrupt channel must use the PLC input point X. It should be noted that it cannot be reused during configuration. For details, please refer to the configuration chapter of the high-speed counter.
++)))
--cannot be reused during configuration. For details, please refer to the configuration chapter of the high-speed counter.
++High-speed counter interrupt steps
--1. high-speed counter interrupt step
++* “Project management”ð“Programð“Interrupt”ðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure, select high-speed interrupt for execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management).
--“Project management”ð“Programð“Interrupt”ðRight click to create. Enter the program name. The program name only supports the combination of English letters, numbers, and underscores, and must start with an English letter. The default is INTx. Click Configure, select high-speed 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-23.png||class="img-thumbnail"]]
@@ -517,7 +517,7 @@
  |Priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
  |Contact|It is available when selecting high-speed comparison set and high-speed comparison reset. The contact is set or reset immediately after the trigger condition is reached.|Y/M/D.b|
--      3. Description of triggering rules
++ 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**
@@ -552,21 +552,22 @@
  The program in INT2 will not be executed
  )))
++(% class="box infomessage" %)
++(((
  **✎Note: **Both HSC channel and external input interrupt channel need to use the INPUT point X, so it should be noted that it cannot be reused in configuration. For details, please refer to the configuration section of high-speed counter.
++)))
--1. Write interrupt execution program
++Write interrupt execution program
  * New interrupt program
++** Create three new interrupt programs under the interrupt of project management, namely HSC0_20000, HSC0_30000, HSC0_40000. Configure the interrupt program in the "program parameters", as shown in the figure below.
--Create three new interrupt programs under the interrupt of project management, namely HSC0_20000, HSC0_30000, HSC0_40000. Configure the interrupt program in the "program parameters", as shown in the figure below.
--
  (% style="text-align:center" %)
  [[image:1-24.png||class="img-thumbnail"]]
  * High-speed counter configuration
++** Configure HSC0 for use in the high-speed counter configuration. After selecting the working mode, click the "Check” button. After the correct configuration box pops up, click Enter.
--Configure HSC0 for use in the high-speed counter configuration. After selecting the working mode, click the "Check” button. After the correct configuration box pops up, click Enter.
--
  (% style="text-align:center" %)
  [[image:1-25.png||class="img-thumbnail"]]
@@ -576,131 +576,123 @@
  Program operation:
--Assuming that the High-speed counter channel 0 has been receiving pulses:
++* Assuming that the High-speed counter channel 0 has been receiving pulses:
++** When the count value of HSC0 accumulates from 0 to 20000, all procedures of HSC0_20000 are executed.
++** When the count value of HSC0 is accumulated from 20000 to 30000, all procedures of HSC0_30000 are executed.
++** When the count value of HSC0 is accumulated from 30000 to 40000, all procedures of HSC0_40000 are executed.
--When the count value of HSC0 accumulates from 0 to 20000, all procedures of HSC0_20000 are executed.
--
--When the count value of HSC0 is accumulated from 20000 to 30000, all procedures of HSC0_30000 are executed.
--
--When the count value of HSC0 is accumulated from 30000 to 40000, all procedures of HSC0_40000 are executed.
--
  **Mask interrupt**
--**~     1. Mask through application instructions**
++Mask through application instructions
--The PLC interrupt is in the shielded state by default when it is powered on, and can only be used after the interrupt is allowed through the EI instruction.
++* The PLC interrupt is in the shielded state by default when it is powered on, and can only be used after the interrupt is allowed through the EI instruction.
++* The interrupt mask instruction DI masks all interrupts without parameters, and masks some priority interrupts with parameters (refer to the program flow instruction DI/EI for details).
--The interrupt mask instruction DI masks all interrupts without parameters, and masks some priority interrupts with parameters (refer to the program flow instruction DI/EI for details).
++Mask through special registers SM and SD
--**~      2. Mask through special registers SM and SD**
--
--1.External input interrupt mask register
--
  (% class="table-bordered" %)
--|(% colspan="4" %)**External input interrupt mask register**
--|**Special register number**|**Type of interrupt**|**Instruction**|**Defaults**
--|SM352|X0 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM353|X0 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM354|X1 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM355|X1 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM356|X2 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM357|X2 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM358|X3 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM359|X3 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM360|X4 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM361|X4 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM362|X5 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM363|X5 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM364|X6 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM365|X6 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM366|X7 rising edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
--|SM367|X7 falling edge interrupt|ON: Mask interrupt OFF: Enable interrupt|OFF
++|=(% colspan="4" %)**External input interrupt mask register**
++|=(% style="width: 266px;" %)**Special register number**|=(% style="width: 308px;" %)**Type of interrupt**|=(% style="width: 390px;" %)**Instruction**|=**Defaults**
++|(% style="width:266px" %)SM352|(% style="width:308px" %)X0 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM353|(% style="width:308px" %)X0 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM354|(% style="width:308px" %)X1 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM355|(% style="width:308px" %)X1 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM356|(% style="width:308px" %)X2 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM357|(% style="width:308px" %)X2 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM358|(% style="width:308px" %)X3 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM359|(% style="width:308px" %)X3 falling edge interrupt|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM360|(% style="width:308px" %)X4 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM361|(% style="width:308px" %)X4 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM362|(% style="width:308px" %)X5 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM363|(% style="width:308px" %)X5 falling edge interrupt|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM364|(% style="width:308px" %)X6 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM365|(% style="width:308px" %)X6 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM366|(% style="width:308px" %)X7 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
++|(% style="width:266px" %)SM367|(% style="width:308px" %)X7 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF
--2. Timer interrupt mask register
--
  (% class="table-bordered" %)
--|(% colspan="4" %)**Timer interrupt mask register**
--|**Special register number**|**Type of interrupt**|**Instruction**|**Default**
--|SD350|1st to 16th timer interrupt|(((
++|=(% colspan="4" %)**Timer interrupt mask register**
++|=(% style="width: 386px;" %)**Special register number**|=(% style="width: 247px;" %)**Type of interrupt**|=(% style="width: 332px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**
++|(% style="width:386px" %)SD350|(% style="width:247px" %)1st to 16th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD351|17th to 32th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD351|(% style="width:247px" %)17th to 32th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD352|33th to 48th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD352|(% style="width:247px" %)33th to 48th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD353|49th to 64th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD353|(% style="width:247px" %)49th to 64th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD354|65th to 80th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD354|(% style="width:247px" %)65th to 80th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD355|81st to 96th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD355|(% style="width:247px" %)81st to 96th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD356|97th to 100th timer interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:386px" %)SD356|(% style="width:247px" %)97th to 100th timer interrupt|(% style="width:332px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
 . high-speed counter interrupt mask register
  (% class="table-bordered" %)
--|(% colspan="4" %)**High-speed counter interrupt mask register**
--|**Special register number**|**Type of interrupt**|**Instruction**|**Default**
--|SD382|1st to 16th high-speed counter interrupt|(((
++|=(% colspan="4" %)**High-speed counter interrupt mask register**
++|=(% style="width: 230px;" %)**Special register number**|=(% style="width: 348px;" %)**Type of interrupt**|=(% style="width: 387px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**
++|(% style="width:230px" %)SD382|(% style="width:348px" %)1st to 16th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD383|17th to 32nd high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD383|(% style="width:348px" %)17th to 32nd high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD384|33th to 48th high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD384|(% style="width:348px" %)33th to 48th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD385|49th to 64th high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD385|(% style="width:348px" %)49th to 64th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD386|65th to 80th high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD386|(% style="width:348px" %)65th to 80th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD387|81st to 96th high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD387|(% style="width:348px" %)81st to 96th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
--|SD388|97th to 100th high-speed counter interrupt|(((
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
++|(% style="width:230px" %)SD388|(% style="width:348px" %)97th to 100th high-speed counter interrupt|(% style="width:387px" %)(((
  Each bit can control the mask of an interrupt.
--ON: Mask interrupt OFF: Enable interrupt
--)))|0
++ON: shield interrupts; OFF: interrupt allowed
++)))|(% style="width:110px" %)0
  == Subroutine ==
--During the execution of the scan program, the executed program can be called by the CALL instruction.
++During the execution of the scan program, the executed program can be called by the CALL instruction. You can create up to 100 new subprograms.
  A subroutine is to split a certain module in the main program for the main program to call, which is conducive to the modularization of the program. Such as other high-level language functions, but this function has no parameters and no return value.
@@ -707,7 +707,7 @@
  (% style="text-align:center" %)
  [[image:1652250926997-587.png||class="img-thumbnail"]]
--1. Instructions for calling subroutines
++**Instructions for calling subroutines**
  After a new subroutine is created, the content of the program is not executed. It is executed only when the CALL(P) instruction is used to call the subroutine in the scan, event, and interrupt programs, and the call is executed once. Three new subroutines SUB0, SUB1, SUB2 are created as shown in the figure below. In the main program MAIN, the subprogram can be called by using the CALL(P) subprogram program name.
@@ -716,87 +716,87 @@
  (% style="text-align:center" %)
  [[image:1-28.png||class="img-thumbnail"]]
--**~      1.✎Note:**
++(% class="box infomessage" %)
++(((
++**✎Note:**
 . When using the timer (OUT T), note that the output will not be reset when the subroutine is not called, and a specific subroutine register must be used.
 . It is not allowed to call recursively between subprograms, that is, call SUB1 in SUB0, and then call SUB0 in SUB1. This is not allowed.
 . 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 ==
--      ~1. Event
++(% class="wikigeneratedid" %)
++**Event**
--      1.ON event
++(% class="wikigeneratedid" %)
++ON event
--If the high-speed pulse instruction is turned on during the ON event, the high-speed pulse instruction will be sent as normal. If the ON contact of the trigger event in the scan period is turned OFF during the pulse sending, select whether to continue sending the pulse or stop the pulse according to the unscanned processing flag bit.
++* If the high-speed pulse instruction is turned on during the ON event, the high-speed pulse instruction will be sent as normal. If the ON contact of the trigger event in the scan period is turned OFF during the pulse sending, select whether to continue sending the pulse or stop the pulse according to the unscanned processing flag bit.
  (% class="table-bordered" %)
--|**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. At this time, it should be noted that if the trigger event OFF contact turns ON after the pulse is sent, the pulse will be sent again.
++* When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. At this time, it should be noted that if the trigger event OFF contact turns ON after the pulse is sent, the pulse will be sent again.
++* When the flag bit is 1 (stop sending pulses), if the trigger event ON contact turns OFF in a certain scan period, it will decelerate and stop.
--When the flag bit is 1 (stop sending pulses), if the trigger event ON contact turns OFF in a certain scan period, it will decelerate and stop.
++ TIME event
--      2. TIME event
++* If the high-speed pulse instruction is turned on in the TIME event, the high-speed pulse instruction will be sent as normal. If the instruction is not scanned in a certain scan period during the pulse transmission, select whether to continue sending the pulse or stop the pulse according to the unscanned processing flag bit.
--If the high-speed pulse instruction is turned on in the TIME event, the high-speed pulse instruction will be sent as normal. If the instruction is not scanned in a certain scan period during the pulse transmission, select whether to continue sending the pulse or stop the pulse according to the unscanned processing flag bit.
--
  (% class="table-bordered" %)
--|**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. In the TIME event, it is impossible to ensure that the instruction is scanned in every scan cycle, so you should avoid using high-speed pulse instructions in the TIME time, otherwise the pulse will be sent again after the pulse is sent.
++* When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. In the TIME event, it is impossible to ensure that the instruction is scanned in every scan cycle, so you should avoid using high-speed pulse instructions in the TIME time, otherwise the pulse will be sent again after the pulse is sent.
++* When the flag bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the flag bit is set to 1 (stop sending pulses), there will be no pulse sending.
--When the flag bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the flag bit is set to 1 (stop sending pulses), there will be no pulse sending.
++**Subroutine**
--       2. Subroutine
--
  If the high-speed pulse instruction is turned on in the subroutine, the high-speed pulse instruction will be sent as normal. If the scanning period is closed during pulse sending, select whether to continue sending or stop the pulse according to the unscanned processing flag.
  (% class="table-bordered" %)
--|**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
  When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. At this time, it should be noted that if the subroutine is called again after the pulse is sent, the pulse will be sent again.
  When the flag bit is 1 (stop sending pulses), if the subroutine is closed during high-speed pulse sending, the speed will decelerate and stop. If the subroutine is closed before sending the pulse, then no pulse is sent.
--      3. Interrupt
++**Interrupt**
--1. External interrupt
++External interrupt
--If the high-speed pulse instruction is enabled in the external interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the unscanned processing flag bit.
++* If the high-speed pulse instruction is enabled in the external interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the unscanned processing flag bit.
  (% class="table-bordered" %)
--|**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
++* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
++* When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
--When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
++Timer interrupt
--        2. Timer interrupt
++* If the high-speed pulse instruction is turned on in the timer interruption, the high-speed pulse instruction is sent as normal. If the instruction is not scanned in a certain scan period in the pulse transmission, the pulse continues to be sent or the pulse stops is selected according to the unscanned processing flag.
--If the high-speed pulse instruction is turned on in the timer interruption, the high-speed pulse instruction is sent as normal. If the instruction is not scanned in a certain scan period in the pulse transmission, the pulse continues to be sent or the pulse stops is selected according to the unscanned processing flag.
--
  (% class="table-bordered" %)
--|**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. In the timer interrupt, it is impossible to ensure that the instruction is scanned in every scan cycle, so it is necessary to avoid using high-speed pulse instructions in the T timer interrupt. Otherwise, after the pulse transmission is completed, the pulse will be sent again.
++* When the flag bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. In the timer interrupt, it is impossible to ensure that the instruction is scanned in every scan cycle, so it is necessary to avoid using high-speed pulse instructions in the T timer interrupt. Otherwise, after the pulse transmission is completed, the pulse will be sent again.
++* When the flag bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the flag bit is set to 1 (stop sending pulses), there will be no pulse sending.
--When the flag bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the flag bit is set to 1 (stop sending pulses), there will be no pulse sending.
++High-speed comparison interrupt
--       3.High-speed comparison interrupt
++* If the high-speed pulse instruction is enabled in the high-speed comparison interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the unscanned processing flag.
--If the high-speed pulse instruction is enabled in the high-speed comparison interrupt, the high-speed pulse instruction selects whether the pulse continues to be sent or the pulse stops according to the unscanned processing flag.
--
  (% class="table-bordered" %)
--|**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
--
--When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
++* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
++* When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.

Changes for page 01 Program execution

Summary

Details

Navigation

Table of Contents