Wiki source code of 01 Program execution

Last modified by Mora Zhou on 2023/11/22 14:09

version	line-number	content
13.1	1	= Summary =
	2
31.1	3	This manual has a comprehensive introduction to the basic functions of WECON PLC Editor and the actual use. This book is completely aimed at zero-based readers, which is an essential reference book for entry-level readers to quickly and fully grasp WECON PLC and WECON PLC Editor.
13.1	4
	5	This book starts from the basic product of WECON PLC and the basic concept and operation of WECON PLC Editor. It combines with a large number of cases and graphic analysis to comprehensively and deeply explain the use of WECON PLC Editor Software, as well as PLC program.
	6
	7	WECON technology Co., Ltd. All rights reserved.
	8
	9	= Precautions =
	10
	11	Before the installation, operation, maintenance and repair of the micro programmable control, please read this manual and other related manuals to ensure correct use. Please use it after you have mastered the operation method, safety information and all
	12
	13	== Design ==
	14
	15	In the event of an abnormality in the external power supply or failure of the programmable controller, to ensure the safe operation of the entire system, be sure to install a safety circuit outside the programmable controller.
	16
	17	1. Be sure to install an emergency brake circuit, a protection circuit, an interlock circuit for reverse operation, such as an emergency brake circuit, a protection circuit, a forward and reverse circuit, and an interlock circuit for the upper and lower positioning limits to prevent machine damage, in the external circuit of the programmable controller.
	18	1. When the programmable controller CPU detects abnormal conditions such as WDT errors through self-diagnosis, all outputs are shut off. In addition, when the programmable controller CPU cannot detect abnormalities in the input/output control part, etc., it cannot control the output. At this time, in order to make the machine operate safely, please design the external circuit and mechanism.
	19	1. Due to the failure of the relay and transistor of the output unit, it is impossible to control the state of the output to ON or OFF. In order to ensure the safe operation of the machine, please design external circuits and mechanisms for output signals related to major accidents.
	20
	21	== Installation ==
	22
13.3	23	* Please use it in the general specification environment described in the manual.
	24	** Do not use in the following places: places with dust, oily smoke, conductive dust, corrosive gas, flammable gas; places exposed to high temperature, condensation, wind and rain; places with vibration or impact. Electric shock, fire, and misoperation can also cause product damage.
	25	* When processing screw holes and wiring, do not let iron filings or wire ends fall into the ventilation window of the programmable controller. It may cause fire, malfunction, or misoperation.
	26	* Please insert the connecting cable and display module accurately into the specified sockets. Poor contact may cause misoperation.
13.1	27
	28	(% class="box infomessage" %)
	29	(((
	30	✎Note:
	31
30.1	32	* To prevent the temperature from rising, do not install at the bottom, top or vertical direction. Be sure to install it horizontally on the wall as shown on the right.
	33	* Please leave a space of more than 50mm between the host and other equipment or structures. Try to avoid high-voltage lines, high-voltage equipment, and power equipment.
13.1	34	)))
	35
	36	== Wiring ==
	37
	38	The signal input and output lines of the programmable controller cannot pass through the same cable.
	39
	40	In addition, signal input lines and output lines cannot pass through the same pipeline with other power lines and output lines, and cannot be bundled together.
	41
	42	If implemented according to the above precautions, even if the input and output wiring is as long as 50 to 100m, there is almost no noise problem. But generally for safety, the wiring length should be within 20m.
	43
	44	(% style="text-align:center" %)
	45	[[image:PLC Editor2.01 Program execution.WebHome@1652145475206-244.png\|\|height="179" width="200" class="img-thumbnail"]]
	46
	47	(% class="box infomessage" %)
	48	(((
	49	✎Note:
	50
	51	* The installation and wiring must be performed when the external power supply is cut off. Otherwise, it may cause electric shock or product damage.
	52	* After installation and wiring, etc., the terminal cover must be installed before power-on operation to avoid electric shock.
	53	)))
	54
	55	(% class="table-bordered" %)
	56	\|=(% scope="row" %)(((
	57
	58
	59
	60	[[image:PLC Editor2.01 Program execution.WebHome@1652145267405-613.png\|\|class="img-thumbnail"]]
	61
	62	Danger
	63	)))\|(((
	64	(% style="text-align:center" %)
	65	[[image:PLC Editor2.01 Program execution.WebHome@0-1.png\|\|height="141" width="400" class="img-thumbnail"]]
	66
	67	It is very dangerous to close the positive and negative contactors at the same time. For loads like this, in addition to the interlock set by the internal program of the programmable controller, the interlock shown above must also be set outside the programmable controller.
	68	)))
	69	\|=(((
	70	[[image:PLC Editor2.01 Program execution.WebHome@1652145275238-798.png\|\|height="45" width="50" class="img-thumbnail"]]
	71
	72	Attention
	73	)))\|Do not connect the empty terminal to the outside, otherwise the product will be damaged.
	74
13.3	75	* Please connect the AC power supply to the dedicated terminal according to the content in the manual.
	76	* If the AC power supply is connected to the DC input/output terminal or the DC power supply terminal, the programmable controller will be burnt out.
	77	* Please do not supply power to the 24+ terminal of the basic unit from the external power supply, and to the empty terminal . Do not wire from the outside, otherwise the product will be damaged.
	78	* Please ground the ground terminal of the basic unit according to the third method. But please do not share the ground with the strong current system.
13.1	79
	80	Attached
	81
	82	The programmable controller will continue to work if there is an instantaneous power failure of less than 10ms.
	83
	84	When the power is cut for a long time or the voltage is low, the programmable controller will stop working and the output will turn OFF, but once the power supply is restored, it will automatically restart.
	85
	86	== Startup and maintenance ==
	87
	88	(% class="table-bordered" %)
	89	(% class="warning" %)\|=Danger
	90	\|(((
	91	Please do not touch the terminals when the power is on, otherwise it may cause electric shock or misoperation.
	92
	93	Please clean and disassemble the terminal after the power is turned off. Performing it while the power is on may cause electric shock.
	94
	95	Please read the manual thoroughly and fully confirm the safety before proceeding with program changes, forced output, RUN/STOP, etc. during machine operation.
	96
	97	Operation errors can damage the machine and cause accidents.
	98	)))
	99
	100	(% class="table-bordered" %)
	101	(% class="warning" %)\|=Caution
	102	\|(((
	103	Please do not disassemble or modify, otherwise it may cause malfunction, malfunction, fire.
	104
	105	※For repair matters, please contact Fuzhou Wecon Electronic Technology Co., Ltd.
	106
	107	After the power is turned off, perform the installation and disassembly of the extension cables and other connecting cables, otherwise it may cause malfunctions and malfunctions.
	108	)))
	109
	110	== Maintenance ==
	111
	112	Regular inspection: Whether the programmable controller is equipped with consumables with a shorter life.
	113
	114	For relay output type, if the output relay works abnormally at a high frequency or drives a large-capacity load, you must pay attention to its impact on the service life.
	115
	116	Check with other equipment, please pay attention to the following points:
	117
	118	* Whether there is an abnormal increase in the temperature inside the machine due to other heating elements or direct sunlight.
	119	* Whether dust or conductive dust has penetrated into the machine.
	120	* Whether there are loose wiring and terminals or other abnormalities
	121
7.1	122	= Scan structure =
1.1	123
	124	The scan configuration of the CPU module is as follows.
	125
	126	(% style="text-align:center" %)
2.1	127	[[image:1-1.png\|\|height="455" width="700" class="img-thumbnail"]]
1.1	128
7.1	129	== Initialization ==
1.1	130
	131	The initialization based on the status of the CPU module is as follows.
	132
13.2	133	* √: execute
22.1	134	* ×: not execute
1.1	135
	136	(% class="table-bordered" %)
13.3	137	\|=(% rowspan="2" %)Processing item\|=(% colspan="3" %)Status of the CPU module
	138	\|=When the power is ON\|=STOP\|=When STOP RUN
1.1	139	\|Initialization of input and output modules\|√\|×\|×
	140	\|CPU parameter check\|√\|×\|×
	141	\|Check of system parameters\|√\|×\|×
	142	\|Device initialization\|√\|×\|√
	143	\|Error clear\|√\|×\|√
	144
7.1	145	== Input and output point refresh ==
1.1	146
	147	Perform the following before starting program calculation.
	148
13.3	149	* Update the actual input point of the PLC to the input relay X.
1.1	150
	151	The following is executed after the END instruction is executed.
	152
13.3	153	* Update the PLC output relay Y to the actual output point.
1.1	154
	155	Key points
	156
	157	When performing a constant scan, the I/O refresh is performed after the waiting time of the constant scan.
	158
7.1	159	== Operation of the program ==
1.1	160
	161	According to the program setting, the execution starts from step 0 of each program to the END instruction. This program is called the main program.
	162
7.1	163	== END processing ==
1.1	164
	165	Perform the following processing.
	166
	167	* Completion processing of partial instructions
	168	* Watchdog timer reset
	169	* Communication processing
	170	* Setting the value of special relay/special register (when the setting timing is END processing)
	171
7.1	172	= Scan time =
1.1	173
	174	The CPU module repeats the following processing, and the scan time is the total of the following processing and execution time.
	175
	176	(% style="text-align:center" %)
2.1	177	[[image:1-2.png\|\|height="349" width="400" class="img-thumbnail"]]
1.1	178
	179	The initial scan time indicates the time including this processing.
	180
7.1	181	== Initial scan time ==
1.1	182
	183	It is the first scan time of the CPU module in RUN.
	184
13.3	185	Process as the following way: The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).
1.1	186
7.1	187	= The flow of each procedure =
1.1	188
	189	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.
	190
	191	(% style="text-align:center" %)
2.1	192	[[image:1652241271896-263.png\|\|height="344" width="500" class="img-thumbnail"]]
1.1	193
	194	Key points
	195
	196	When the execution types of the programs are the same, they are executed in the order set in the execution order.
	197
13.3	198	(% class="box infomessage" %)
	199	(((
	200	✎Note: When executing instructions that can be completed with multiple cycles (such as OUT T, RAMP, RS, etc.), they should be programmed in the scan program. If it is used in event execution type programs and mid-stage execution type programs, these instructions may not be executed in multiple scan cycles, causing actual results to be different from the ideal results. Therefore, unless events, interrupts and subroutines can be executed in each scan cycle. It is not recommended to use multi-cycle execution instructions in other situations.
	201	)))
1.1	202
7.1	203	= Types of program execution =
1.1	204
7.1	205	== Scan execution program ==
1.1	206
	207	Each scan is executed only once from the next scan of the initial execution type program.
	208
	209	(% style="text-align:center" %)
2.1	210	[[image:1-4.png\|\|height="325" width="700" class="img-thumbnail"]]
1.1	211
	212	When multiple scan execution type programs are executed, the execution time of the scan execution type program is the time until all scan execution type programs are executed. In addition, before the execution of the scan execution type program is completed, if an interrupt program/event execution type program/subroutine is executed, the execution time will also be included.
	213
	214	Creation of multiple scanners
	215
	216	"Project Management"→ "Program"→ "Scan"→ Right click to create
	217
	218	(% style="text-align:center" %)
2.1	219	[[image:1-5.png\|\|height="372" width="300" class="img-thumbnail"]]
1.1	220
13.9	221	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).
	222	1. The input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" is not supported. It cannot exceed 64 characters. The default name is MAINx.
	223	1. The number of scan programs that can be built is limited to 100.
	224	1. Each scan program has been END ended, but only the last END instruction is completed to calculate a scan cycle.
	225	1. The execution sequence runs from top to bottom in the order of creation.
1.1	226
	227	(% style="text-align:center" %)
	228	[[image:1-6.png\|\|class="img-thumbnail"]]
	229
7.1	230	== Event execution program ==
1.1	231
	232	It uses the event specified by the user as a condition to trigger the program to start execution.
	233
	234	(% style="text-align:center" %)
	235	[[image:1-7.png\|\|class="img-thumbnail"]]
	236
	237	Trigger type
	238
	239	The trigger of event execution type program is as follows.
	240
13.9	241	ON event of bit data (TRUE)
1.1	242
	243	* 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.
	244	* The ON event program will only be executed once in a single scan cycle.
	245	* After the ON event is executed, you can set whether to clear the current value of the output (Y) and timer (T) used in the program.
	246
	247	*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.
	248
	249	(% style="text-align:center" %)
20.2	250	[[image:image-20220926104203-1.jpeg\|\|class="img-thumbnail"]]
1.1	251
	252	When it is the turn of the execution sequence of event execution type program C and Y50 is ON, the program is executed.
	253
	254	The devices that can be specified are as follows.
	255
	256	(% class="table-bordered" %)
13.9	257	\|=(% colspan="2" %)Project\|=Content
1.1	258	\|(% rowspan="2" %)Device *1\|Bit Device\|X, Y, M, SM
	259	\|Bit specification of word device\|D.b
	260
	261	*1 The indexed device cannot be specified.
	262
13.9	263	TIME event
1.1	264
	265	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.
	266
	267	(% style="text-align:center" %)
	268	[[image:1652247622598-446.png\|\|class="img-thumbnail"]]
	269
	270	After the specified time has elapsed, when it comes to the first execution sequence, the event execution type program C is executed.
	271
	272	Key points
	273
	274	When set to clear the current value of output and timer, and the scan time is longer than the set value of elapsed time, the current value of output and timer will not be cleared.
	275
	276	Operational steps
	277
	278	1）New event
	279
	280	Project management→ Program→ Event → Right click to create.
	281
	282	(% style="text-align:center" %)
	283	[[image:1-10 E.png\|\|class="img-thumbnail"]]
	284
	285	Event program name:
	286
	287	* The program name requires to match case, and the program name with the same name as the device cannot be used (the device name does not match case).
13.3	288	* The program name does not support /%$@&=~~`^<>?:{}[],;!*.~\~\'" character input.
1.1	289	* The length of the program name cannot exceed 64 characters. The default name is EVENTx.
	290
	291	A maximum of 100 new event programs could be created.
	292
	293	2) Execution type
	294
	295	There are two ways to configure the event execution type:
	296
	297	1. Configure when creating a new event program, as shown in the figure above.w
	298	1. Project management→ Program→ Parameter → Program parameter→Configuration
	299
	300	(% style="text-align:center" %)
2.1	301	[[image:1-11.png\|\|height="419" width="500" class="img-thumbnail"]]
1.1	302
13.9	303	Configuration instructions:
1.1	304
13.9	305	Configuration interface
1.1	306
	307	(% style="text-align:center" %)
2.1	308	[[image:1-12.png\|\|height="372" width="300" class="img-thumbnail"]]
1.1	309
13.9	310	Parameter content:
1.1	311
	312	(% class="table-bordered" %)
13.10	313	\|=(% colspan="2" %)Project\|=(% style="width: 654px;" %)Content\|=(% style="width: 190px;" %)Setting range\|=Default
	314	\|(% colspan="2" %)Execution type\|(% style="width:654px" %)Select event type\|(% style="width:190px" %)Not set/ON event/TIME event\|Not set
	315	\|(% 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\|
	316	\|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" %)(((
1.1	317	True
	318
	319	False
	320	)))\|False
13.10	321	\|(% 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)\|
	322	\|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" %)(((
1.1	323	True
	324
	325	False
	326	)))\|False
	327
	328	Key points
	329
	330	When "ON event" or "TIME event" is specified, if "Clear or not" is set to "Clear", the event program will not be executed in one scan cycle, and all the internal outputs (Y) and current value of timer (T) will all be cleared (except for the cumulative type and subroutine type T). If the time set by the TIME event is less than the scan period, it is equivalent to executing the TIME event every scan period. Even if the clear output is set, the output and timer data in the event program will not be cleared.
	331
7.1	332	== Interrupt execution program ==
1.1	333
	334	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.
	335
13.11	336	* When an interrupt cause occurs, the interrupt program corresponding to the interrupt pointer number will be executed. However, the execution needs to be set to the interrupt enabled state by the EI instruction.
1.1	337
	338	(% style="text-align:center" %)
	339	[[image:1652249587490-678.png\|\|class="img-thumbnail"]]
	340
	341
13.11	342	* 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.
	343	* Interrupt has the characteristic of interrupting the original execution program and executing the interrupt first, but it cannot interrupt the interrupt program being executed.
	344	* 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.
1.1	345
13.11	346	The actions when an interruption cause occurs are as follows:
1.1	347
13.11	348	* Interrupt prohibition (DI) when an interruption cause occurs.
	349	** 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.
	350	* When multiple interrupt causes occur simultaneously in the interrupt enabled state.
	351	** 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.
	352	** 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.
1.1	353
	354	(% style="text-align:center" %)
	355	[[image:1652249553246-688.png\|\|class="img-thumbnail"]]
	356
13.11	357	* When an interrupt occurs during the waiting time when performing constant scan.
	358	** Execute the interrupt program for this interrupt.
	359	* When other interrupts occur during the execution of the interrupt program.
	360	** 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.
	361	* During the execution of the interrupt program, when an interrupt cause with a low priority or the same priority occurs.
	362	** 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.
1.1	363
	364	(% style="text-align:center" %)
	365	[[image:1652249673420-476.png\|\|class="img-thumbnail"]]
	366
13.11	367	* When the same interruption cause occurs during the execution of the interrupt program;
	368	** 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.
1.1	369
	370	Interrupt trigger condition classification
	371
13.11	372	* External input (X) interrupt
	373	** Description of external input interrupt
	374	*** The external input interrupt is triggered by the rising or falling edge of the fixed X point input.
	375	*** 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.
	376	*** The same interrupt trigger condition cannot create multiple interrupt programs.
	377	*** External input interrupt and high-speed counter cannot use the same X point.
	378	*** You must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
	379	* External input interrupt steps.
	380	** Project management→ Program→ Interrupt→ right click to create.
	381	** 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),
	382	** The interrupt program name does not support the input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" characters,
	383	** The length of the interrupt program name cannot exceed 64 characters and cannot be typed. The default name is INTx.
1.1	384
	385	(% style="text-align:center" %)
	386	[[image:1-16.png\|\|class="img-thumbnail"]]
	387
13.11	388	* Click Configure, and select external interrupt for execution type, as shown in the figure below (it can also be configured in "program parameters" in "parameters" in project management):
1.1	389
	390	(% style="text-align:center" %)
	391	[[image:1-17.png\|\|class="img-thumbnail"]]
	392
	393	(% class="table-bordered" %)
	394	\|(% colspan="2" %)Project\|Content\|Setting range\|Default
	395	\|(% colspan="2" %)Execution type\|Select the type of interrupt\|Not set, External input interrupt, Timer event, high-speed counter interrupt\|Not set
	396	\|(% rowspan="4" %)External input interrupt\|channel\|Select the channel for external input interrupt\|X0 to X7\|X0
	397	\|Trigger edge type\|Choose to trigger on rising edge or falling edge\|(((
	398	Rising edge
	399
	400	Falling edge
	401	)))\|Rising edge
	402	\|priority\|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first\|0 to 2\|0
	403	\|Filter time (0.01us)\|(((
	404	Set the filter time of X point, the unit is 0.01us.
	405
	406	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.
	407	)))\|0 to 1700\|1
	408
13.11	409	* Write interrupt execution program
1.1	410
	411	(% style="text-align:center" %)
	412	[[image:1-18.png\|\|class="img-thumbnail"]]
	413
	414	Double-click the newly created interrupt program in the project management to start writing the interrupt execution program. As shown in the figure above, a newly created interrupt program is INT_X0_UP, and the trigger condition is configured to execute the interrupt program when the X0 rising edge is configured. If the EI instruction is used in the main program to allow interrupts, all programs in INT_X0_UP will be executed whenever X0 changes from OFF to ON , That is, D0 will increment once.
	415
	416	(% style="text-align:center" %)
2.1	417	[[image:1652250056160-117.png\|\|height="215" width="500" class="img-thumbnail"]]
1.1	418
13.11	419	Timer interrupt
1.1	420
13.12	421	Timer interrupt description
1.1	422
13.12	423	* Timer interrupt is based on the set time, execute the interrupt program every this time, the minimum time interval can reach 100us.
	424	* Up to 100 timer interrupt execution programs can be created.
	425	* Each timer interrupt program is independent of each other and does not affect each other.
	426	* 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.
	427	* The interrupt execution program is executed only after EI is used in the scanner to allow the interrupt
1.1	428
13.12	429	Timer interrupt step
1.1	430
13.12	431	* 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).
1.1	432
	433	(% style="text-align:center" %)
	434	[[image:1-20.png\|\|class="img-thumbnail"]]
	435
	436	(% class="table-bordered" %)
32.1	437	\|=(% colspan="2" %)Project\|=Content\|=Setting range\|=Default
1.1	438	\|(% colspan="2" %)Execution type\|Select the type of interrupt\|Not set/External input interrupt/Timer event/high-speed counter interrupt\|Not set
	439	\|(% rowspan="2" %)Timer interrupt\|Time\|Set the interval time for interrupt triggering\|1 to 2147483647 (100us unit)\|
	440	\|priority\|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first\|0 to 2\|0
	441
13.12	442	Write interrupt execution program
1.1	443
	444	(% style="text-align:center" %)
	445	[[image:1-21.png\|\|class="img-thumbnail"]]
	446
13.12	447	* 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.
1.1	448
	449	(% style="text-align:center" %)
	450	[[image:1652250294005-455.png\|\|class="img-thumbnail"]]
	451
13.12	452	High-speed counter interrupt
1.1	453
13.12	454	Description of high-speed counter interrupt
1.1	455
13.12	456	* 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.
	457	* 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.
	458	* 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).
	459	* 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.
	460	* Project must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.
1.1	461
13.12	462	(% class="box infomessage" %)
	463	(((
	464	✎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.
	465	)))
1.1	466
13.12	467	High-speed counter interrupt steps
1.1	468
13.12	469	* “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).
1.1	470
	471	(% style="text-align:center" %)
	472	[[image:1-23.png\|\|class="img-thumbnail"]]
	473
	474	(% class="table-bordered" %)
32.1	475	\|=(% colspan="2" %)Project\|=Content\|=Setting range\|=Default
1.1	476	\|(% colspan="2" %)Execution type\|Select the type of interrupt\|Not set, External input interrupt, Timer event, high-speed counter interrupt\|Not set
	477	\|(% rowspan="5" %)High count interrupt\|Mode\|(((
	478	Select the type of high-speed counter interrupt:
	479
	480	(1) High-speed comparison interrupt: The interrupt program is executed after the trigger condition is reached.
	481
	482	(2) High-speed comparison setting: After reaching the trigger condition, the set contact is set.
	483
	484	(3) High-speed comparison reset: reset the set contact after reaching the trigger condition.
	485	)))\|(((
	486	High-speed compare interrupt
	487
	488	High-speed comparison set
	489
	490	High-speed comparison reset
	491
	492	Not set
	493	)))\|(((
	494	High-speed compare interrupt
	495
	496	
	497	)))
	498	\|Channel\|Select the high-speed counter channel used\|HSC0 to HSC7\|HSC0
	499	\|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\|
	500	\|Priority\|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first\|0 to 2\|0
	501	\|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\|
	502
13.12	503	Description of triggering rules
1.1	504
	505	(% class="table-bordered" %)
32.1	506	\|=(% style="width: 135px;" %)Mode\|=(% style="width: 187px;" %)Configuration\|=(% style="width: 128px;" %)The current value\|=(% style="width: 324px;" %)Action
13.8	507	\|(% rowspan="2" style="width:135px" %)High-speed compare interrupt (INT0)\|(% rowspan="2" style="width:187px" %)Comparison value: 10000\|(% style="width:128px" %)9999 → 10000\|(% style="width:324px" %)Execute all programs in interrupt INT0
	508	\|(% style="width:128px" %)10001 → 10000\|(% style="width:324px" %)Execute all programs in interrupt INT0
	509	\|(% rowspan="2" style="width:135px" %)High-speed comparison set (INT1)\|(% rowspan="2" style="width:187px" %)(((
1.1	510	Comparison value: -50,000
	511
	512	Contact: Y10
13.8	513	)))\|(% style="width:128px" %)-50001 → -50000\|(% style="width:324px" %)(((
1.1	514	Y10 is immediately set and mapped to the actual output (not affected by the scan period)
	515
	516	The program in INT1 will not be executed
	517	)))
13.8	518	\|(% style="width:128px" %)-49999 → -50000\|(% style="width:324px" %)(((
1.1	519	Y10 is immediately set and mapped to the actual output (not affected by the scan period)
	520
	521	The program in INT1 will not be executed
	522	)))
13.8	523	\|(% rowspan="2" style="width:135px" %)High-speed comparison reset (INT2)\|(% rowspan="2" style="width:187px" %)(((
1.1	524	Comparison value: 400000
	525
	526	Contact: Y10
13.8	527	)))\|(% style="width:128px" %)399999 → 400000\|(% style="width:324px" %)(((
1.1	528	Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
	529
	530	The program in INT2 will not be executed
	531	)))
13.8	532	\|(% style="width:128px" %)400001 → 400000\|(% style="width:324px" %)(((
1.1	533	Y10 is reset immediately and mapped to the actual output (not affected by the scan period)
	534
	535	The program in INT2 will not be executed
	536	)))
	537
13.12	538	(% class="box infomessage" %)
	539	(((
1.1	540	✎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.
13.12	541	)))
1.1	542
13.12	543	Write interrupt execution program
1.1	544
	545	* New interrupt program
13.12	546	** 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.
1.1	547
	548	(% style="text-align:center" %)
	549	[[image:1-24.png\|\|class="img-thumbnail"]]
	550
	551	* High-speed counter configuration
13.12	552	** 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.
1.1	553
	554	(% style="text-align:center" %)
	555	[[image:1-25.png\|\|class="img-thumbnail"]]
	556
	557	Call the high-speed counter in the main program and enable interrupts:
	558
	559	[[image:1-26.png\|\|class="img-thumbnail"]]
	560
	561	Program operation:
	562
13.12	563	* Assuming that the High-speed counter channel 0 has been receiving pulses:
	564	** When the count value of HSC0 accumulates from 0 to 20000, all procedures of HSC0_20000 are executed.
	565	** When the count value of HSC0 is accumulated from 20000 to 30000, all procedures of HSC0_30000 are executed.
	566	** When the count value of HSC0 is accumulated from 30000 to 40000, all procedures of HSC0_40000 are executed.
1.1	567
	568	Mask interrupt
	569
13.12	570	Mask through application instructions
1.1	571
13.12	572	* 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.
	573	* 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).
1.1	574
13.12	575	Mask through special registers SM and SD
1.1	576
	577	(% class="table-bordered" %)
13.12	578	\|=(% colspan="4" %)External input interrupt mask register
16.1	579	\|=(% style="width: 266px;" %)Special register number\|=(% style="width: 308px;" %)Type of interrupt\|=(% style="width: 390px;" %)Instruction\|=Defaults
	580	\|(% style="width:266px" %)SM352\|(% style="width:308px" %)X0 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	581	\|(% style="width:266px" %)SM353\|(% style="width:308px" %)X0 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	582	\|(% style="width:266px" %)SM354\|(% style="width:308px" %)X1 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	583	\|(% style="width:266px" %)SM355\|(% style="width:308px" %)X1 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	584	\|(% style="width:266px" %)SM356\|(% style="width:308px" %)X2 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	585	\|(% style="width:266px" %)SM357\|(% style="width:308px" %)X2 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	586	\|(% style="width:266px" %)SM358\|(% style="width:308px" %)X3 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	587	\|(% style="width:266px" %)SM359\|(% style="width:308px" %)X3 falling edge interrupt\|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed\|OFF
	588	\|(% style="width:266px" %)SM360\|(% style="width:308px" %)X4 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	589	\|(% style="width:266px" %)SM361\|(% style="width:308px" %)X4 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	590	\|(% style="width:266px" %)SM362\|(% style="width:308px" %)X5 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	591	\|(% style="width:266px" %)SM363\|(% style="width:308px" %)X5 falling edge interrupt\|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed\|OFF
	592	\|(% style="width:266px" %)SM364\|(% style="width:308px" %)X6 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	593	\|(% style="width:266px" %)SM365\|(% style="width:308px" %)X6 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	594	\|(% style="width:266px" %)SM366\|(% style="width:308px" %)X7 rising edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
	595	\|(% style="width:266px" %)SM367\|(% style="width:308px" %)X7 falling edge interrupt\|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed\|OFF
13.13	596
1.1	597	(% class="table-bordered" %)
13.13	598	\|=(% colspan="4" %)Timer interrupt mask register
20.1	599	\|=(% style="width: 262px;" %)Special register number\|=(% style="width: 309px;" %)Type of interrupt\|=(% style="width: 394px;" %)Instruction\|=(% style="width: 110px;" %)Default
	600	\|(% style="width:262px" %)SD350\|(% style="width:309px" %)1st to 16th timer interrupt\|(% style="width:394px" %)(((
1.1	601	Each bit can control the mask of an interrupt.
	602
16.1	603	ON: shield interrupts; OFF: interrupt allowed
	604	)))\|(% style="width:110px" %)0
20.1	605	\|(% style="width:262px" %)SD351\|(% style="width:309px" %)17th to 32th timer interrupt\|(% style="width:394px" %)(((
1.1	606	Each bit can control the mask of an interrupt.
	607
16.1	608	ON: shield interrupts; OFF: interrupt allowed
	609	)))\|(% style="width:110px" %)0
20.1	610	\|(% style="width:262px" %)SD352\|(% style="width:309px" %)33th to 48th timer interrupt\|(% style="width:394px" %)(((
1.1	611	Each bit can control the mask of an interrupt.
	612
16.1	613	ON: shield interrupts; OFF: interrupt allowed
	614	)))\|(% style="width:110px" %)0
20.1	615	\|(% style="width:262px" %)SD353\|(% style="width:309px" %)49th to 64th timer interrupt\|(% style="width:394px" %)(((
1.1	616	Each bit can control the mask of an interrupt.
	617
16.1	618	ON: shield interrupts; OFF: interrupt allowed
	619	)))\|(% style="width:110px" %)0
20.1	620	\|(% style="width:262px" %)SD354\|(% style="width:309px" %)65th to 80th timer interrupt\|(% style="width:394px" %)(((
1.1	621	Each bit can control the mask of an interrupt.
	622
16.1	623	ON: shield interrupts; OFF: interrupt allowed
	624	)))\|(% style="width:110px" %)0
20.1	625	\|(% style="width:262px" %)SD355\|(% style="width:309px" %)81st to 96th timer interrupt\|(% style="width:394px" %)(((
1.1	626	Each bit can control the mask of an interrupt.
	627
16.1	628	ON: shield interrupts; OFF: interrupt allowed
	629	)))\|(% style="width:110px" %)0
20.1	630	\|(% style="width:262px" %)SD356\|(% style="width:309px" %)97th to 100th timer interrupt\|(% style="width:394px" %)(((
1.1	631	Each bit can control the mask of an interrupt.
	632
16.1	633	ON: shield interrupts; OFF: interrupt allowed
	634	)))\|(% style="width:110px" %)0
1.1	635
	636	1. high-speed counter interrupt mask register
	637
	638	(% class="table-bordered" %)
16.1	639	\|=(% colspan="4" %)High-speed counter interrupt mask register
	640	\|=(% style="width: 230px;" %)Special register number\|=(% style="width: 348px;" %)Type of interrupt\|=(% style="width: 387px;" %)Instruction\|=(% style="width: 110px;" %)Default
	641	\|(% style="width:230px" %)SD382\|(% style="width:348px" %)1st to 16th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	642	Each bit can control the mask of an interrupt.
	643
16.1	644	ON: shield interrupts; OFF: interrupt allowed
	645	)))\|(% style="width:110px" %)0
	646	\|(% style="width:230px" %)SD383\|(% style="width:348px" %)17th to 32nd high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	647	Each bit can control the mask of an interrupt.
	648
16.1	649	ON: shield interrupts; OFF: interrupt allowed
	650	)))\|(% style="width:110px" %)0
	651	\|(% style="width:230px" %)SD384\|(% style="width:348px" %)33th to 48th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	652	Each bit can control the mask of an interrupt.
	653
16.1	654	ON: shield interrupts; OFF: interrupt allowed
	655	)))\|(% style="width:110px" %)0
	656	\|(% style="width:230px" %)SD385\|(% style="width:348px" %)49th to 64th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	657	Each bit can control the mask of an interrupt.
	658
16.1	659	ON: shield interrupts; OFF: interrupt allowed
	660	)))\|(% style="width:110px" %)0
	661	\|(% style="width:230px" %)SD386\|(% style="width:348px" %)65th to 80th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	662	Each bit can control the mask of an interrupt.
	663
16.1	664	ON: shield interrupts; OFF: interrupt allowed
	665	)))\|(% style="width:110px" %)0
	666	\|(% style="width:230px" %)SD387\|(% style="width:348px" %)81st to 96th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	667	Each bit can control the mask of an interrupt.
	668
16.1	669	ON: shield interrupts; OFF: interrupt allowed
	670	)))\|(% style="width:110px" %)0
	671	\|(% style="width:230px" %)SD388\|(% style="width:348px" %)97th to 100th high-speed counter interrupt\|(% style="width:387px" %)(((
1.1	672	Each bit can control the mask of an interrupt.
	673
16.1	674	ON: shield interrupts; OFF: interrupt allowed
	675	)))\|(% style="width:110px" %)0
1.1	676
7.1	677	== Subroutine ==
1.1	678
17.1	679	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.
1.1	680
	681	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.
	682
	683	(% style="text-align:center" %)
	684	[[image:1652250926997-587.png\|\|class="img-thumbnail"]]
	685
17.1	686	Instructions for calling subroutines
1.1	687
	688	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.
	689
	690	Through this programming method, the use of the same logic program for different conditions can reduce the number of Circuit program steps and improve the readability of the Circuit program.
	691
	692	(% style="text-align:center" %)
	693	[[image:1-28.png\|\|class="img-thumbnail"]]
	694
17.1	695	(% class="box infomessage" %)
	696	(((
	697	✎Note:
1.1	698
	699	1. 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.
	700	1. 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.
	701	1. 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.
	702	1. Unlike the LX3V series mainframe, the subroutine in the LX5V series mainframe ends with the END instruction instead of SRET.
17.1	703	)))
1.1	704
7.1	705	== Positioning instructions ==
1.1	706
18.1	707	(% class="wikigeneratedid" %)
	708	Event
1.1	709
18.1	710	(% class="wikigeneratedid" %)
	711	ON event
1.1	712
18.1	713	* 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.
1.1	714
	715	(% class="table-bordered" %)
18.1	716	\|=(% scope="row" %)Output shaft\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	717	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	718
18.1	719	* 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.
	720	* 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.
1.1	721
18.1	722	TIME event
1.1	723
18.1	724	* 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.
1.1	725
	726	(% class="table-bordered" %)
18.1	727	\|=(% scope="row" %)Output shaft\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	728	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	729
18.1	730	* 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.
	731	* 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.
1.1	732
18.1	733	Subroutine
1.1	734
	735	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.
	736
	737	(% class="table-bordered" %)
18.1	738	\|=(% scope="row" %)Output shaft\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	739	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	740
	741	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.
	742
	743	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.
	744
18.1	745	Interrupt
1.1	746
18.1	747	External interrupt
1.1	748
18.1	749	* 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.
1.1	750
	751	(% class="table-bordered" %)
18.1	752	\|=(% scope="row" %)Output shaft\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	753	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	754
18.1	755	* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
	756	* When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.
1.1	757
18.1	758	Timer interrupt
1.1	759
18.1	760	* 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.
1.1	761
	762	(% class="table-bordered" %)
18.1	763	\|=(% scope="row" %)Output axis\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	764	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	765
18.1	766	* 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.
	767	* 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.
1.1	768
18.1	769	High-speed comparison interrupt
1.1	770
18.1	771	* 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.
1.1	772
	773	(% class="table-bordered" %)
18.1	774	\|=(% scope="row" %)Output axis\|Y0\|Y1\|Y2\|Y3\|Y4\|Y5\|Y6\|Y7
	775	\|=Not scanned flag bit\|SM899\|SM959\|SM1019\|SM1079\|SM1139\|SM1199\|SM1259\|SM1319
1.1	776
18.1	777	* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.
	778	* When the flag bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.

Wiki source code of 01 Program execution

Navigation

Table of Contents