Changes for page 01 Program execution

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

From 15.1 to 16.1 From 22.1 to 23.1

From version 16.1

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

Change comment: There is no comment for this version

To version 22.1

edited by Jim
on 2023/07/25 11:59

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- image-20220926104203-1.jpeg

Details

Page properties

Author

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

Content

@@ -131,7 +131,7 @@
  The initialization based on the status of the CPU module is as follows.
  * **√**: execute
--*  **×**: not execute
++* **×**: not execute
  (% class="table-bordered" %)
  |=(% rowspan="2" %)**Processing item**|=(% colspan="3" %)**Status of the CPU module**
@@ -247,7 +247,7 @@
  *1: Scan program paging: multiple scan programs are established, and each scan program is called a paging. After scan program A is executed, before scan program B is executed, it will be judged whether an event program needs to be executed.
  (% style="text-align:center" %)
--[[image:1652247397997-492.png||class="img-thumbnail"]]
++[[image:image-20220926104203-1.jpeg||class="img-thumbnail"]]
  When it is the turn of the execution sequence of event execution type program C and Y50 is ON, the program is executed.
@@ -596,38 +596,38 @@
  (% class="table-bordered" %)
  |=(% colspan="4" %)**Timer interrupt mask register**
--|=**Special register number**|=(% style="width: 311px;" %)**Type of interrupt**|=(% style="width: 391px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**
--|SD350|(% style="width:311px" %)1st to 16th timer interrupt|(% style="width:391px" %)(((
++|=(% style="width: 262px;" %)**Special register number**|=(% style="width: 309px;" %)**Type of interrupt**|=(% style="width: 394px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**
++|(% style="width:262px" %)SD350|(% style="width:309px" %)1st to 16th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD351|(% style="width:311px" %)17th to 32th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD351|(% style="width:309px" %)17th to 32th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD352|(% style="width:311px" %)33th to 48th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD352|(% style="width:309px" %)33th to 48th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD353|(% style="width:311px" %)49th to 64th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD353|(% style="width:309px" %)49th to 64th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD354|(% style="width:311px" %)65th to 80th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD354|(% style="width:309px" %)65th to 80th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD355|(% style="width:311px" %)81st to 96th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD355|(% style="width:309px" %)81st to 96th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
  )))|(% style="width:110px" %)0
--|SD356|(% style="width:311px" %)97th to 100th timer interrupt|(% style="width:391px" %)(((
++|(% style="width:262px" %)SD356|(% style="width:309px" %)97th to 100th timer interrupt|(% style="width:394px" %)(((
  Each bit can control the mask of an interrupt.
  ON: shield interrupts; OFF: interrupt allowed
@@ -676,7 +676,7 @@
  == 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.
@@ -683,7 +683,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.
@@ -692,87 +692,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.

image-20220926104203-1.jpeg

Author

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

Size

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

Content

Changes for page 01 Program execution

Summary

Details

Navigation

Table of Contents