01 Program execution

= **Summary** =

This manual provides a comprehensive introduction to the basic functions and actual use of WECON PLC Editor. It is completely aimed at zero-based readers and is an essential reference book for entry-level readers who want to quickly and fully grasp WECON PLC and WECON PLC Editor.

4

This book starts with the basic product of WECON PLC and the basic concept and operation of WECON PLC Editor. It then uses a large number of cases and graphic analysis to comprehensively and deeply explain the use of WECON PLC Editor Software and the PLC program.

= Precautions =

Before the installation, operation, maintenance and repair of the micro programmable control, please read this manual and other related manuals to ensure correct use. Please use it after you have mastered the operation method, and safety information.

== Design ==

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.

15

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, please design the external circuit and mechanism so that the machine can operate safely.

16

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. To ensure the safe operation of the machine, please design external circuits and mechanisms for output signals related to major accidents.

== Installation ==

* Please use it in the general specification environment described in the manual.

21

** Do not use in the following places: places with dust, oily smoke, conductive dust, corrosive gas, or 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.

22

* 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.

23

* Please insert the connecting cable and display module accurately into the specified sockets. Poor contact may cause misoperation.

24

25

(% class="box infomessage" %)

(((

**✎Note:**

* To prevent the temperature from rising, do not install at the bottom, top or vertical direction. Be sure to install it horizontally on the wall as shown on the right.

30

* Please leave a space of more than 50mm between the host and other equipment or structures. Try to avoid high-voltage lines, high-voltage equipment, and power equipment.

)))

== Wiring ==

The signal input and output lines of the programmable controller cannot pass through the same cable.

36

37

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.

38

39

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.

40

41

(% style="text-align:center" %)

42

[[image:PLC Editor2.01 Program execution.WebHome@1652145475206-244.png||height="179" width="200" class="img-thumbnail"]]

43

44

(% class="box infomessage" %)

(((

**✎Note:**

* The installation and wiring must be performed when the external power supply is cut off. Otherwise, it may cause electric shock or product damage.

49

* After installation and wiring, etc., the terminal cover must be installed before power-on operation to avoid electric shock.

50

)))

51

52

(% class="table-bordered" %)

53

|=(% scope="row" %)(((

[[image:PLC Editor2.01 Program execution.WebHome@1652145267405-613.png||class="img-thumbnail"]]

**Danger**

)))|(((

(% style="text-align:center" %)

62

[[image:PLC Editor2.01 Program execution.WebHome@0-1.png||height="141" width="400" class="img-thumbnail"]]

63

64

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.

65

)))

66

|=(((

67

[[image:PLC Editor2.01 Program execution.WebHome@1652145275238-798.png||height="45" width="50" class="img-thumbnail"]]

68

69

**Attention**

70

)))|Do not connect the empty terminal to the outside, otherwise the product will be damaged.

71

72

* Please connect the AC power supply to the dedicated terminal according to the content in the manual.

73

* 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.

74

* 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.

75

* Please ground the ground terminal of the basic unit according to the third method. But please do not share the ground with the strong current system.

**Attached**

The programmable controller will continue to work if there is an instantaneous power failure of less than 10ms.

80

81

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.

82

83

== Startup and maintenance ==

84

85

(% class="table-bordered" %)

86

(% class="warning" %)|=**Danger**

87

|(((

88

Please do not touch the terminals when the power is on, otherwise it may cause electric shock or misoperation.

89

90

Please clean and disassemble the terminal after the power is turned off. Performing it while the power is on may cause electric shock.

91

92

Please read the manual thoroughly and fully confirm the safety before proceeding with program changes, forced output, RUN/STOP, etc. during machine operation.

93

94

Operation errors can damage the machine and cause accidents.

95

)))

96

97

(% class="table-bordered" %)

98

(% class="warning" %)|=**Caution**

99

|(((

100

Please do not disassemble or modify, otherwise it may cause malfunction, malfunction, fire.

101

102

※For repair matters, please contact Fuzhou Wecon Electronic Technology Co., Ltd.

103

104

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.

105

)))

106

107

== **Maintenance** ==

108

109

Regular inspection: Whether the programmable controller is equipped with consumables with a shorter life.

110

111

For the 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.

112

113

Check with other equipment, please pay attention to the following points:

114

115

* Whether there is an abnormal increase in the temperature inside the machine due to other heating elements or direct sunlight.

116

* Whether dust or conductive dust has penetrated the machine.

117

* Whether there are loose wiring and terminals or other abnormalities

= Scan structure =

The scan configuration of the CPU module is as follows.

122

123

(% style="text-align:center" %)

124

[[image:1-1.png||height="455" width="700" class="img-thumbnail"]]

== Initialization ==

The initialization based on the status of the CPU module is as follows.

* **√**: execute

* **×**: not execute

(% class="table-bordered" %)

134

|=(% rowspan="2" %)Processing item|=(% colspan="3" %)Status of the CPU module

135

|=When the power is ON|=STOP|=When STOP RUN

136

|Initialization of input and output modules|√|×|×

137

|CPU parameter check|√|×|×

138

|Check of system parameters|√|×|×

139

|Device initialization|√|×|√

140

|Error clear|√|×|√

141

142

== Input and output point refresh ==

143

144

Perform the following before starting program calculation.

145

146

* Update the actual input point of the PLC to the input relay X.

147

148

The following is executed after the END instruction is executed.

149

150

* Update the PLC output relay Y to the actual output point.

**Key points**

When performing a constant scan, the I/O refresh is performed after the waiting time of the constant scan.

155

156

== Operation of the program ==

157

158

According to the program setting, the execution starts from step 0 of each program to the END instruction. This program is called the main program.

== END processing ==

Perform the following processing.

163

164

* Completion processing of partial instructions

165

* Watchdog timer reset

166

* Communication processing

167

* Setting the value of special relay/special register (when the setting timing is END processing)

= Scan time =

The CPU module repeats the following processing, and the scan time is the total of the following processing and execution time.

172

173

(% style="text-align:center" %)

174

[[image:1-2.png||height="349" width="400" class="img-thumbnail"]]

175

176

The initial scan time indicates the time including this processing.

177

178

== Initial scan time ==

179

180

It is the first scan time of the CPU module in RUN.

181

182

Process as the following way: The value stored in SD134 (initial scan time (ms unit)) and SD135 (initial scan time (s unit)).

183

184

= The flow of each procedure =

185

186

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.

187

188

(% style="text-align:center" %)

189

[[image:1652241271896-263.png||height="344" width="500" class="img-thumbnail"]]

**Key points**

When the execution types of the programs are the same, they are executed in the order set in the execution order.

194

195

(% class="box infomessage" %)

196

(((

197

**✎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.

198

)))

199

200

= Types of program execution =

201

202

== Scan execution program ==

203

204

Each scan is executed only once from the next scan of the initial execution type program.

205

206

(% style="text-align:center" %)

207

[[image:1-4.png||height="325" width="700" class="img-thumbnail"]]

208

209

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.

210

211

**Creation of multiple scanners**

212

213

"Project Management"→ "Program"→ "Scan"→ Right click to create

214

215

(% style="text-align:center" %)

216

[[image:1-5.png||height="372" width="300" class="img-thumbnail"]]

217

218

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).

219

1. The input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" is not supported. It cannot exceed 64 characters. The default name is MAINx.

220

1. The number of scan programs that can be built is limited to 100.

221

1. Each scan program has been END ended, but only the last END instruction is completed to calculate a scan cycle.

222

1. The execution sequence runs from top to bottom in the order of creation.

223

224

(% style="text-align:center" %)

225

[[image:1-6.png||class="img-thumbnail"]]

226

227

== Event execution program ==

228

229

It uses the event specified by the user as a condition to trigger the program to start execution.

230

231

(% style="text-align:center" %)

232

[[image:1-7.png||class="img-thumbnail"]]

**Trigger type**

The trigger of event execution type program is as follows.

237

238

**ON event of bit data (TRUE)**

239

240

* 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.

241

* The ON event program will only be executed once in a single scan cycle.

242

* 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.

243

244

*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.

245

246

(% style="text-align:center" %)

247

[[image:image-20220926104203-1.jpeg||class="img-thumbnail"]]

248

249

When it is the turn of the execution sequence of event execution type program C and Y50 is ON, the program is executed.

250

251

The devices that can be specified are as follows.

252

253

(% class="table-bordered" %)

254

|=(% colspan="2" %)**Project**|=**Content**

255

|(% rowspan="2" %)Device *1|Bit Device|X, Y, M, SM

256

|Bit specification of word device|D.b

257

258

*1 The indexed device cannot be specified.

**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.

263

264

(% style="text-align:center" %)

265

[[image:1652247622598-446.png||class="img-thumbnail"]]

266

267

After the specified time has elapsed, when it comes to the first execution sequence, the event execution type program C is executed.

**Key points**

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.

272

273

**Operational steps**

**1）New event**

Project management→ Program→ Event → Right click to create.

278

279

(% style="text-align:center" %)

280

[[image:1-10 E.png||class="img-thumbnail"]]

Event program name:

* The program name requires to match case, and the program name with the same name as the device cannot be used (the device name does not match case).

285

* The program name does not support /%$@&=~~`^<>?:{}[],;!*.~\~\'" character input.

286

* The length of the program name cannot exceed 64 characters. The default name is EVENTx.

287

288

A maximum of 100 new event programs could be created.

289

290

**2) Execution type**

291

292

There are two ways to configure the event execution type:

293

294

1. Configure when creating a new event program, as shown in the figure above.w

295

1. Project management→ Program→ Parameter → Program parameter→Configuration

296

297

(% style="text-align:center" %)

298

[[image:1-11.png||height="419" width="500" class="img-thumbnail"]]

299

300

**Configuration instructions:**

301

302

Configuration interface

303

304

(% style="text-align:center" %)

305

[[image:1-12.png||height="372" width="300" class="img-thumbnail"]]

Parameter content:

(% class="table-bordered" %)

310

|=(% colspan="2" %)**Project**|=(% style="width: 654px;" %)**Content**|=(% style="width: 190px;" %)**Setting range**|=**Default**

311

|(% colspan="2" %)Execution type|(% style="width:654px" %)Select event type|(% style="width:190px" %)Not set/ON event/TIME event|Not set

312

313

|Whether to clear|(% style="width:654px" %)When the bit device of the trigger condition set by the ON event is turned OFF, whether to clear the current value of the output (Y) and timer (T) used in the execution program of the ON event in the next cycle.|(% style="width:190px" %)(((

True

False

)))|False

|Whether to clear|(% style="width:654px" %)When the TIME event is executed, if the event is not executed in the next scan cycle, select whether to clear the output (Y) used in the TIME event execution program and the current value of the timer (T).|(% style="width:190px" %)(((

True

False

)))|False

**Key points**

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.

328

329

== Interrupt execution program ==

330

331

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.

332

333

* 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.

334

335

(% style="text-align:center" %)

336

[[image:1652249587490-678.png||class="img-thumbnail"]]

337

338

339

* 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.

340

* Interrupt has the characteristic of interrupting the original execution program and executing the interrupt first, but it cannot interrupt the interrupt program being executed.

341

* 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.

342

343

**The actions when an interruption cause occurs are as follows:**

344

345

* Interrupt prohibition (DI) when an interruption cause occurs.

346

** 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.

347

* When multiple interrupt causes occur simultaneously in the interrupt enabled state.

348

** 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.

349

** 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.

350

351

(% style="text-align:center" %)

352

[[image:1652249553246-688.png||class="img-thumbnail"]]

353

354

* When an interrupt occurs during the waiting time when performing constant scan.

355

** Execute the interrupt program for this interrupt.

356

* When other interrupts occur during the execution of the interrupt program.

357

** 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.

358

* During the execution of the interrupt program, when an interrupt cause with a low priority or the same priority occurs.

359

** 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.

360

361

(% style="text-align:center" %)

362

[[image:1652249673420-476.png||class="img-thumbnail"]]

363

364

* When the same interruption cause occurs during the execution of the interrupt program;

365

** 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.

366

367

**Interrupt trigger condition classification**

368

369

* **External input (X) interrupt**

370

** Description of external input interrupt

371

*** The external input interrupt is triggered by the rising or falling edge of the fixed X point input.

372

*** 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.

373

*** The same interrupt trigger condition cannot create multiple interrupt programs.

374

*** External input interrupt and high-speed counter cannot use the same X point.

375

*** You must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.

376

* **External input interrupt steps.**

377

** Project management→ Program→ Interrupt→ right click to create.

378

** 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),

379

** The interrupt program name does not support the input of /%$@&=~~`^<>?:{}[],;!*.~\~\'" characters,

380

** The length of the interrupt program name cannot exceed 64 characters and cannot be typed. The default name is INTx.

381

382

(% style="text-align:center" %)

383

[[image:1-16.png||class="img-thumbnail"]]

384

385

* 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):

386

387

(% style="text-align:center" %)

388

[[image:1-17.png||class="img-thumbnail"]]

389

390

(% class="table-bordered" %)

391

|(% colspan="2" %)**Project**|**Content**|**Setting range**|**Default**

392

|(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set

393

394

|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

400

|Filter time (0.01us)|(((

401

Set the filter time of X point, the unit is 0.01us.

402

403

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.

404

)))|0 to 1700|1

405

406

* Write interrupt execution program

407

408

(% style="text-align:center" %)

409

[[image:1-18.png||class="img-thumbnail"]]

410

411

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.

412

413

(% style="text-align:center" %)

414

[[image:1652250056160-117.png||height="215" width="500" class="img-thumbnail"]]

**Timer interrupt**

Timer interrupt description

419

420

* Timer interrupt is based on the set time, execute the interrupt program every this time, the minimum time interval can reach 100us.

421

* Up to 100 timer interrupt execution programs can be created.

422

* Each timer interrupt program is independent of each other and does not affect each other.

423

* 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.

424

* The interrupt execution program is executed only after EI is used in the scanner to allow the interrupt

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).

429

430

(% style="text-align:center" %)

431

[[image:1-20.png||class="img-thumbnail"]]

432

433

(% class="table-bordered" %)

434

|=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**

435

|(% colspan="2" %)Execution type|Select the type of interrupt|Not set/External input interrupt/Timer event/high-speed counter interrupt|Not set

436

437

|priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0

438

439

Write interrupt execution program

440

441

(% style="text-align:center" %)

442

[[image:1-21.png||class="img-thumbnail"]]

443

444

* 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.

445

446

(% style="text-align:center" %)

447

[[image:1652250294005-455.png||class="img-thumbnail"]]

448

449

**High-speed counter interrupt**

450

451

Description of high-speed counter interrupt

452

453

* 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.

454

* 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.

455

* 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).

456

* 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.

457

* Project must use EI in the scan program to allow interrupts before the interrupt execution program will be executed.

458

459

(% class="box infomessage" %)

460

(((

461

**✎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.

462

)))

463

464

High-speed counter interrupt steps

465

466

* “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).

467

468

(% style="text-align:center" %)

469

[[image:1-23.png||class="img-thumbnail"]]

470

471

(% class="table-bordered" %)

472

|=(% colspan="2" %)**Project**|=**Content**|=**Setting range**|=**Default**

473

|(% colspan="2" %)Execution type|Select the type of interrupt|Not set, External input interrupt, Timer event, high-speed counter interrupt|Not set

474

|(% rowspan="5" %)High count interrupt|Mode|(((

475

Select the type of high-speed counter interrupt:

476

477

(1) High-speed comparison interrupt: The interrupt program is executed after the trigger condition is reached.

478

479

(2) High-speed comparison setting: After reaching the trigger condition, the set contact is set.

480

481

(3) High-speed comparison reset: reset the set contact after reaching the trigger condition.

482

)))|(((

483

High-speed compare interrupt

484

485

High-speed comparison set

486

487

High-speed comparison reset

Not set

)))|(((

High-speed compare interrupt



)))

|Channel|Select the high-speed counter channel used|HSC0 to HSC7|HSC0

496

|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|

497

|Priority|When multiple interrupts arrive at the same time, the order of priority execution, the smallest value is executed first|0 to 2|0

498

|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|

499

500

Description of triggering rules

501

502

(% class="table-bordered" %)

503

|=(% style="width: 135px;" %)**Mode**|=(% style="width: 187px;" %)**Configuration**|=(% style="width: 128px;" %)**The current value**|=(% style="width: 324px;" %)**Action**

504

|(% 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

505

|(% style="width:128px" %)10001 → 10000|(% style="width:324px" %)Execute all programs in interrupt INT0

506

|(% rowspan="2" style="width:135px" %)High-speed comparison set (INT1)|(% rowspan="2" style="width:187px" %)(((

507

Comparison value: -50,000

508

509

Contact: Y10

510

)))|(% style="width:128px" %)-50001 → -50000|(% style="width:324px" %)(((

511

Y10 is immediately set and mapped to the actual output (not affected by the scan period)

512

513

The program in INT1 will not be executed

514

)))

515

|(% style="width:128px" %)-49999 → -50000|(% style="width:324px" %)(((

516

Y10 is immediately set and mapped to the actual output (not affected by the scan period)

517

518

The program in INT1 will not be executed

519

)))

520

|(% rowspan="2" style="width:135px" %)High-speed comparison reset (INT2)|(% rowspan="2" style="width:187px" %)(((

521

Comparison value: 400000

522

523

Contact: Y10

524

)))|(% style="width:128px" %)399999 → 400000|(% style="width:324px" %)(((

525

Y10 is reset immediately and mapped to the actual output (not affected by the scan period)

526

527

The program in INT2 will not be executed

528

)))

529

|(% style="width:128px" %)400001 → 400000|(% style="width:324px" %)(((

530

Y10 is reset immediately and mapped to the actual output (not affected by the scan period)

531

532

The program in INT2 will not be executed

533

)))

534

535

(% class="box infomessage" %)

536

(((

537

**✎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.

538

)))

539

540

Write interrupt execution program

541

542

* New interrupt program

543

** 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.

544

545

(% style="text-align:center" %)

546

[[image:1-24.png||class="img-thumbnail"]]

547

548

* High-speed counter configuration

549

** 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.

550

551

(% style="text-align:center" %)

552

[[image:1-25.png||class="img-thumbnail"]]

553

554

Call the high-speed counter in the main program and enable interrupts:

555

556

[[image:1-26.png||class="img-thumbnail"]]

Program operation:

* Assuming that the High-speed counter channel 0 has been receiving pulses:

561

** When the count value of HSC0 accumulates from 0 to 20000, all procedures of HSC0_20000 are executed.

562

** When the count value of HSC0 is accumulated from 20000 to 30000, all procedures of HSC0_30000 are executed.

563

** When the count value of HSC0 is accumulated from 30000 to 40000, all procedures of HSC0_40000 are executed.

**Mask interrupt**

Mask through application instructions

568

569

* 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.

570

* 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).

571

572

Mask through special registers SM and SD

573

574

(% class="table-bordered" %)

575

|=(% colspan="4" %)**External input interrupt mask register**

576

|=(% style="width: 266px;" %)**Special register number**|=(% style="width: 308px;" %)**Type of interrupt**|=(% style="width: 390px;" %)**Instruction**|=**Defaults**

577

|(% style="width:266px" %)SM352|(% style="width:308px" %)X0 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

578

|(% style="width:266px" %)SM353|(% style="width:308px" %)X0 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

579

|(% style="width:266px" %)SM354|(% style="width:308px" %)X1 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

580

|(% style="width:266px" %)SM355|(% style="width:308px" %)X1 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

581

|(% style="width:266px" %)SM356|(% style="width:308px" %)X2 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

582

|(% style="width:266px" %)SM357|(% style="width:308px" %)X2 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

583

|(% style="width:266px" %)SM358|(% style="width:308px" %)X3 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

584

|(% style="width:266px" %)SM359|(% style="width:308px" %)X3 falling edge interrupt|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed|OFF

585

|(% style="width:266px" %)SM360|(% style="width:308px" %)X4 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

586

|(% style="width:266px" %)SM361|(% style="width:308px" %)X4 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

587

|(% style="width:266px" %)SM362|(% style="width:308px" %)X5 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

588

|(% style="width:266px" %)SM363|(% style="width:308px" %)X5 falling edge interrupt|(% style="width:390px" %)ON: Shield interrupts; OFF: interrupt allowed|OFF

589

|(% style="width:266px" %)SM364|(% style="width:308px" %)X6 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

590

|(% style="width:266px" %)SM365|(% style="width:308px" %)X6 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

591

|(% style="width:266px" %)SM366|(% style="width:308px" %)X7 rising edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

592

|(% style="width:266px" %)SM367|(% style="width:308px" %)X7 falling edge interrupt|(% style="width:390px" %)ON: shield interrupts; OFF: interrupt allowed|OFF

593

594

(% class="table-bordered" %)

595

|=(% colspan="4" %)**Timer interrupt mask register**

596

|=(% style="width: 262px;" %)**Special register number**|=(% style="width: 309px;" %)**Type of interrupt**|=(% style="width: 394px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**

597

|(% style="width:262px" %)SD350|(% style="width:309px" %)1st to 16th timer interrupt|(% style="width:394px" %)(((

598

Each bit can control the mask of an interrupt.

599

600

ON: shield interrupts; OFF: interrupt allowed

601

)))|(% style="width:110px" %)0

602

|(% style="width:262px" %)SD351|(% style="width:309px" %)17th to 32th timer interrupt|(% style="width:394px" %)(((

603

Each bit can control the mask of an interrupt.

604

605

ON: shield interrupts; OFF: interrupt allowed

606

)))|(% style="width:110px" %)0

607

|(% style="width:262px" %)SD352|(% style="width:309px" %)33th to 48th timer interrupt|(% style="width:394px" %)(((

608

Each bit can control the mask of an interrupt.

609

610

ON: shield interrupts; OFF: interrupt allowed

611

)))|(% style="width:110px" %)0

612

|(% style="width:262px" %)SD353|(% style="width:309px" %)49th to 64th timer interrupt|(% style="width:394px" %)(((

613

Each bit can control the mask of an interrupt.

614

615

ON: shield interrupts; OFF: interrupt allowed

616

)))|(% style="width:110px" %)0

617

|(% style="width:262px" %)SD354|(% style="width:309px" %)65th to 80th timer interrupt|(% style="width:394px" %)(((

618

Each bit can control the mask of an interrupt.

619

620

ON: shield interrupts; OFF: interrupt allowed

621

)))|(% style="width:110px" %)0

622

|(% style="width:262px" %)SD355|(% style="width:309px" %)81st to 96th timer interrupt|(% style="width:394px" %)(((

623

Each bit can control the mask of an interrupt.

624

625

ON: shield interrupts; OFF: interrupt allowed

626

)))|(% style="width:110px" %)0

627

|(% style="width:262px" %)SD356|(% style="width:309px" %)97th to 100th timer interrupt|(% style="width:394px" %)(((

628

Each bit can control the mask of an interrupt.

629

630

ON: shield interrupts; OFF: interrupt allowed

631

)))|(% style="width:110px" %)0

632

633

1. high-speed counter interrupt mask register

634

635

(% class="table-bordered" %)

636

|=(% colspan="4" %)**High-speed counter interrupt mask register**

637

|=(% style="width: 230px;" %)**Special register number**|=(% style="width: 348px;" %)**Type of interrupt**|=(% style="width: 387px;" %)**Instruction**|=(% style="width: 110px;" %)**Default**

638

|(% style="width:230px" %)SD382|(% style="width:348px" %)1st to 16th high-speed counter interrupt|(% style="width:387px" %)(((

639

Each bit can control the mask of an interrupt.

640

641

ON: shield interrupts; OFF: interrupt allowed

642

)))|(% style="width:110px" %)0

643

|(% style="width:230px" %)SD383|(% style="width:348px" %)17th to 32nd high-speed counter interrupt|(% style="width:387px" %)(((

644

Each bit can control the mask of an interrupt.

645

646

ON: shield interrupts; OFF: interrupt allowed

647

)))|(% style="width:110px" %)0

648

|(% style="width:230px" %)SD384|(% style="width:348px" %)33th to 48th high-speed counter interrupt|(% style="width:387px" %)(((

649

Each bit can control the mask of an interrupt.

650

651

ON: shield interrupts; OFF: interrupt allowed

652

)))|(% style="width:110px" %)0

653

|(% style="width:230px" %)SD385|(% style="width:348px" %)49th to 64th high-speed counter interrupt|(% style="width:387px" %)(((

654

Each bit can control the mask of an interrupt.

655

656

ON: shield interrupts; OFF: interrupt allowed

657

)))|(% style="width:110px" %)0

658

|(% style="width:230px" %)SD386|(% style="width:348px" %)65th to 80th high-speed counter interrupt|(% style="width:387px" %)(((

659

Each bit can control the mask of an interrupt.

660

661

ON: shield interrupts; OFF: interrupt allowed

662

)))|(% style="width:110px" %)0

663

|(% style="width:230px" %)SD387|(% style="width:348px" %)81st to 96th high-speed counter interrupt|(% style="width:387px" %)(((

664

Each bit can control the mask of an interrupt.

665

666

ON: shield interrupts; OFF: interrupt allowed

667

)))|(% style="width:110px" %)0

668

|(% style="width:230px" %)SD388|(% style="width:348px" %)97th to 100th high-speed counter interrupt|(% style="width:387px" %)(((

669

Each bit can control the mask of an interrupt.

670

671

ON: shield interrupts; OFF: interrupt allowed

672

)))|(% style="width:110px" %)0

== Subroutine ==

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.

677

678

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.

679

680

(% style="text-align:center" %)

681

[[image:1652250926997-587.png||class="img-thumbnail"]]

682

683

**Instructions for calling subroutines**

684

685

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.

686

687

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.

688

689

(% style="text-align:center" %)

690

[[image:1-28.png||class="img-thumbnail"]]

691

692

(% class="box infomessage" %)

(((

**✎Note:**

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.

697

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.

698

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.

699

1. Unlike the LX3V series mainframe, the subroutine in the LX5V series mainframe ends with the END instruction instead of SRET.

700

)))

701

702

== Positioning instructions ==

703

704

(% class="wikigeneratedid" %)

705

**Event**

706

707

(% class="wikigeneratedid" %)

708

ON event

709

710

* 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.

711

712

(% class="table-bordered" %)

713

|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

714

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

715

716

* 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.

717

* 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 unscanned processing flag bit.

722

723

(% class="table-bordered" %)

724

|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

725

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

726

727

* 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.

728

* 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**

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.

733

734

(% class="table-bordered" %)

735

|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

736

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

737

738

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.

739

740

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.

**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.

747

748

(% class="table-bordered" %)

749

|=(% scope="row" %)**Output shaft**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

750

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

751

752

* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.

753

* 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 unscanned processing flag.

758

759

(% class="table-bordered" %)

760

|=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

761

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

762

763

* 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.

764

* 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.

765

766

High-speed comparison interrupt

767

768

* 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.

769

770

(% class="table-bordered" %)

771

|=(% scope="row" %)**Output axis**|Y0|Y1|Y2|Y3|Y4|Y5|Y6|Y7

772

|=**Not scanned flag bit**|SM899|SM959|SM1019|SM1079|SM1139|SM1199|SM1259|SM1319

773

774

* When the flag bit is 0 (continue to send pulse), continue to send high-speed pulses until it stops.

775

* 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