Changes for page 01 Execution of the Program

Last modified by Iris on 2026/04/06 18:55

From 2.2 to 2.3 From 3.1 to 4.1

From version 2.3

edited by Iris
on 2026/03/02 13:42

Change comment: There is no comment for this version

To version 3.1

edited by Iris
on 2026/04/06 18:52

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -82,7 +82,7 @@
  When the CPU module changes to the RUN state, the programs are executed in sequence according to the program execution type and execution sequence settings.
  (% style="text-align:center" %)
--[[image:3.png]]
++[[image:1775460314418-471.png||height="333" width="482"]]
  **Key points**
@@ -112,7 +112,7 @@
  **Creation of multiple scanners**
--"Project Management"→ "Program"→ "Scan"→ Right click to create
++"Project Management"→ "Program"→ "Scan"→ "Right click to create"
  (% style="text-align:center" %)
  [[image:6.png]]
@@ -132,7 +132,7 @@
  (% style="text-align:center" %)
  [[image:8.png]]
--**Tigger type**
++**Trigger type**
  The trigger of event execution type program is as follows.
@@ -153,7 +153,7 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% colspan="2" %)**Project**|=**Content**
--|(% rowspan="2" %)Device *1|Bit Device|X, Y, M, SM
++|(% rowspan="2" %)Device *1|Bit device|X, Y, M, SM
  |Bit specification of word device|D.b
  *1 The indexed device cannot be specified.
@@ -160,8 +160,10 @@
  **(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.[[image:1772422285611-760.png]]
++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.
++[[image:1775461360680-630.png]]
++
  After the specified time has elapsed, when it comes to the first execution sequence, the event execution type program C is executed.
  **Key points**
@@ -206,13 +206,13 @@
  |(% 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|
++|(% 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|Set how long to execute the event program once.|1 to 2147483647 (100us unit)|
++|(% 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
@@ -234,11 +234,11 @@
  * 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.
++* The interrupt program has the concept of priority. The smaller the priority value,  the higher the response priority. 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.
++1) Interrupt prohibition (DI) When an interrupt 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.
@@ -261,14 +261,14 @@
 ) 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.
++The interrupt 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:16.png]]
--6) When the same interruption cause occurs during the execution of the interrupt program;
++6) When the same interrupt 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 interrupt 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 interrupt cause occurs multiple times, the interruption cause is stored only once.
  **Interrupt trigger condition classification**
@@ -300,11 +300,11 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
  |(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set
--|(% rowspan="4" %)External input interrupt|channel|Select the channel for external input interrupt|X0 to X7|X0
++|(% rowspan="4" %)External input interrupt|channel|Select the channel for external input interrupt|X0 to X7|X0
  |Trigger edge type|Choose to trigger on rising edge or falling edge|Rising edge; Falling edge|Rising edge
  |priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0
--|Filter time (0.01us)|(((
--Set the filter time of X point, the unit is 0.01us.
++|Filter time (0.01μs)|(((
++Set the filter time of X point, the unit is 0.01μs.
  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
@@ -323,7 +323,7 @@
 ) Timer interrupt description
--* Timer interrupt is based on the set time, execute the interrupt program every time, the minimum time interval can reach 100us.
++* Timer interrupt is based on the set time, execute the interrupt program every time, the minimum time interval can reach 100μs.
  * 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.
@@ -331,7 +331,7 @@
 ) 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 Manager → [Program] → [Interrupt] → [Right-click to create]. 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:21.png]]
@@ -339,8 +339,8 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
  |(% colspan="2" %)Execution type|Select the type of interrupt|Not set/External input interrupt/Timer event/high-speed counter interrupt|Not set
--|(% 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
++|(% rowspan="2" %)Timer interrupt|Time|Set the interval time for interrupt triggering|1 to 2147483647 (100μs unit)|
++|Priority|When multiple interrupts occur simultaneously, they are executed in priority order,  the smallest value is executed first|0 to 2|0
 ) Write interrupt execution program
@@ -352,120 +352,6 @@
  (% style="text-align:center" %)
  [[image:23.png||height="190" width="558"]]
--**(3)High-speed counter interrupt**
--
--1) Description of high-speed counter interrupt
--
--* 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.
--
--{{info}}
--**✎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.
--{{/info}}
--
--2) high-speed counter interrupt steps
--
--“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:24.png]]
--
--|=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**
--|(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set
--|(% rowspan="5" %)High count interrupt|Mode|(((
--Select the type of high-speed counter interrupt:
--
--(1) High-speed comparison interrupt: The interrupt program is executed after the trigger condition is reached.
--
--(2) High-speed comparison setting: After reaching the trigger condition, the set contact is set.
--
--(3) High-speed comparison reset: reset the set contact after reaching the trigger condition.
--)))|(((
--High-speed compare interrupt
--
--High-speed comparison set
--
--High-speed comparison reset
--
--Not set
--)))|High-speed compare interrupt
--|Channel|Select the high-speed counter channel used|HSC0 to HSC7|HSC0
--|Comparison value|Set the comparison value of the high-speed counter. When the high-speed counter value of the set channel passes this value, the trigger condition is reached.|-2147483648 to 2147483647|
--|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
--
--|=**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
--)))|-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
--)))
--|-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" %)High-speed comparison reset (INT2)|(% rowspan="2" %)(((
--Comparison value: 400000
--
--Contact: Y10
--)))|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
--)))
--|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
--)))
--
--{{info}}
--**✎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.
--{{/info}}
--
--4) 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.
--
--(% style="text-align:center" %)
--[[image:25.png]]
--
--② 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.
--
--(% style="text-align:center" %)
--[[image:26.png]]
--
--Call the high-speed counter in the main program and enable interrupts:
--
--(% style="text-align:center" %)
--[[image:27.png]]
--
--Program operation:
--
--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.
--
  **Mask interrupt**
  **(1) Mask through application instructions**
@@ -481,22 +481,22 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% colspan="4" %)**External input interrupt mask register**
  |**Special register number**|**Type of interrupt**|**Instruction**|**Defaults**
--|SM352|X0 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM353|X0 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM354|X1 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM355|X1 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM356|X2 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM357|X2 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM358|X3 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM359|X3 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM360|X4 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM361|X4 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM362|X5 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM363|X5 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM364|X6 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM365|X6 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM366|X7 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
--|SM367|X7 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF
++|SM352|X0 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM353|X0 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM354|X1 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM355|X1 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM356|X2 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM357|X2 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM358|X3 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM359|X3 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM360|X4 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM361|X4 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM362|X5 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM363|X5 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM364|X6 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM365|X6 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM366|X7 rising edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
++|SM367|X7 falling edge interrupt|ON: Shield interrupts; OFF: Interrupt allowed|OFF
 ) Timer interrupt mask register
@@ -506,37 +506,37 @@
  |SD350|1st to 16th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD351|17th to 32th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD352|33th to 48th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD353|49th to 64th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD354|65th to 80th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD355|81st to 96th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD356|97th to 100th timer interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
 ） High-speed counter interrupt mask register
@@ -546,37 +546,37 @@
  |SD382|1st to 16th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD383|17th to 32nd high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD384|33th to 48th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD385|49th to 64th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD386|65th to 80th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD387|81st to 96th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|0
  |SD388|97th to 100th high-speed counter interrupt|(((
  Each bit can control the mask of an interrupt.
--ON: shield interrupts; OFF: interrupt allowed
++ON: Shield interrupts; OFF: Interrupt allowed
  )))|(((
  )))
@@ -619,39 +619,39 @@
 ) 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 sign bit.
++If the high-speed pulse instruction is enabled 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 non-scanned processing sign bit.
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 sign 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
--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 non-scanned sign bit.
++If the high-speed pulse instruction is enabled 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 non-scanned sign bit.
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Non-scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 sign 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 sign 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.
  (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 non-scanned sign bit.
++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 non-scanned flag bit.
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Non-scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 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 sign 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.
++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**
@@ -661,23 +661,23 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Non-scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 sign 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
--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 non-scanned sign bit.
++If the high-speed pulse instruction is enabled 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 non-scanned flag bit.
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Non-scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 sign 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 sign 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 sign bit is set to 1 (stop sending pulses), there will be no pulse sending.
 ) HIgh-speed comparison interrupt
@@ -685,17 +685,10 @@
  (% style="margin-left:auto; margin-right:auto" %)
  |=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7
--|=**Not scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
++|=**Non-scanned sign bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319
--When the sign 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 sign 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.
--
--
--
--
--
--
--

Changes for page 01 Execution of the Program

Summary

Details

Navigation

Table of Contents