01 Execution of the Program

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.

83

84

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

[[image:3.png]]

**Key points**

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

90

91

(% class="box infomessage" %)

(((

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

96

)))

97

98

== **Types of Program Execution** ==

----

=== **Scan Execution Program** ===

----

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

107

108

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

109

[[image:5.png]]

110

111

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.

112

113

**Creation of multiple scanners**

114

115

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

116

117

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

118

[[image:6.png]]

119

120

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

121

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

122

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

123

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

124

125

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

126

[[image:7.png]]

127

128

=== **Event Execution Program** ===

129

130

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

131

132

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

[[image:8.png]]

**Tigger type**

The trigger of event execution type program is as follows.

138

139

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

140

141

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

142

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

143

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

144

145

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

146

147

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

148

[[image:9.png]]

149

150

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

151

152

The devices that can be specified are as follows.

153

154

(% style="margin-left:auto; margin-right:auto" %)

155

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

156

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

157

|Bit specification of word device|D.b

158

159

*1 The indexed device cannot be specified.

**(2) TIME event**

After the program is to RUN state and the specified time has elapsed, event is executed one time when it comes to the execution sequence of the first corresponding program. For the second and subsequent executions, the time is re-measured from the start of the last event execution type program. After the specified time has elapsed, the program is executed repeatedly when it comes to the execution sequence of the first corresponding program. In addition, in the next scan after the corresponding program is executed, the current value of the output (Y) and timer (T) used in the corresponding program can be cleared. It can be used for programs that do not need to respond in a fixed period of time.

164

165

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

166

[[image:10.png]]

167

168

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.

173

174

**Operational steps**

**(1) New event**

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

179

180

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

[[image:11.png]]

Event program name:

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

186

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

187

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

188

189

A maximum of 100 new event programs could be created.

190

191

**(2) Execution type**

192

193

There are two ways to configure the event execution type:

194

195

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

196

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

197

198

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

199

[[image:12.png||height="427" width="510"]]

200

201

Configuration instructions:

202

203

1) Configuration interface:

204

205

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

206

[[image:13.png]]

207

208

2) Parameter content:

209

210

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

211

|(% colspan="2" %)Execution type|Select event type|Not set/ON event/TIME event|Not set

212

213

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

True

False

)))|False

|Whether to clear|When the TIME event is executed, if the event is not executed in the next scan cycle, select whether to clear the output (Y) used in the TIME event execution program and the current value of the timer (T).|(((

True

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.

228

229

=== **Interrupt Execution Program** ===

230

231

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.

232

233

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

234

235

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

236

[[image:14.png||height="295" width="700"]]

237

238

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

239

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

240

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

241

242

The actions when an interruption cause occurs are as follows:

243

244

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

245

246

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.

247

248

2) When multiple interrupt causes occur simultaneously in the interrupt enabled state.

249

250

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.

251

252

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.

253

254

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

255

[[image:15.png]]

256

257

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

258

259

Execute the interrupt program for this interrupt.

260

261

4) When other interrupts occur during the execution of the interrupt program.

262

263

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.

264

265

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

266

267

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.

268

269

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

270

[[image:16.png]]

271

272

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

273

274

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.

275

276

**Interrupt trigger condition classification**

277

278

**(1) External input (X) interrupt**

279

280

1) Description of external input interrupt

281

282

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

283

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

284

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

285

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

286

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

287

288

2) External input interrupt steps.

289

290

Project management→ Program→ Interrupt→ right click to create

291

292

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

293

[[image:17.png]]

294

295

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

296

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

297

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

298

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

299

300

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

301

[[image:18.png]]

302

303

(% style="margin-left:auto; margin-right:auto" %)

304

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

305

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

306

307

|Trigger edge type|Choose to trigger on rising edge or falling edge|Rising edge; Falling edge|Rising edge

308

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

309

|Filter time (0.01us)|(((

310

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

311

312

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.

313

)))|0 to 1700|1

314

315

3) Write interrupt execution program

316

317

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

318

[[image:19.png]]

319

320

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.

321

322

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

323

[[image:20.png||height="138" width="317"]]

(2)Timer interrupt

1) Timer interrupt description

328

329

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

330

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

331

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

332

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

333

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

334

335

2) Timer interrupt step

336

337

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

338

339

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

340

[[image:21.png]]

341

342

(% style="margin-left:auto; margin-right:auto" %)

343

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

344

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

345

346

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

347

348

3) Write interrupt execution program

349

350

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

351

[[image:22.png]]

352

353

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.

354

355

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

356

[[image:23.png||height="190" width="558"]]

357

358

**(3)High-speed counter interrupt**

359

360

1) Description of high-speed counter interrupt

361

362

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

363

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

364

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

365

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

366

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

367

368

369

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

370

371

372

2) high-speed counter interrupt steps

373

374

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

375

376

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

377

[[image:24.png]]

378

379

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

380

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

381

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

382

Select the type of high-speed counter interrupt:

383

384

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

385

386

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

387

388

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

389

)))|(((

390

High-speed compare interrupt

391

392

High-speed comparison set

393

394

High-speed comparison reset

395

396

Not set

397

)))|High-speed compare interrupt

398

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

399

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

400

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

401

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

402

403

3) Description of triggering rules

404

405

|=**Mode**|=**Configuration**|=**The current value**|=**Action**

406

|(% rowspan="2" %)High-speed compare interrupt (INT0)|(% rowspan="2" %)Comparison value: 10000|9999 → 10000|Execute all programs in interrupt INT0

407

|10001 → 10000|Execute all programs in interrupt INT0

408

|(% rowspan="2" %)High-speed comparison set (INT1)|(% rowspan="2" %)(((

409

Comparison value: -50,000

410

411

Contact: Y10

412

)))|-50001 → -50000|(((

413

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

414

415

The program in INT1 will not be executed

416

)))

417

|-49999 → -50000|(((

418

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

419

420

The program in INT1 will not be executed

421

)))

422

|(% rowspan="2" %)High-speed comparison reset (INT2)|(% rowspan="2" %)(((

423

Comparison value: 400000

424

425

Contact: Y10

426

)))|399999 → 400000|(((

427

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

428

429

The program in INT2 will not be executed

430

)))

431

|400001 → 400000|(((

432

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

433

434

The program in INT2 will not be executed

)))

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

439

440

441

4) Write interrupt execution program

442

443

① New interrupt program

444

445

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.

446

447

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

448

[[image:25.png]]

449

450

② High-speed counter configuration

451

452

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.

453

454

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

455

[[image:26.png]]

456

457

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

458

459

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

[[image:27.png]]

Program operation:

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

465

466

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

467

468

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

469

470

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

**Mask interrupt**

**(1) Mask through application instructions**

475

476

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.

477

478

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

479

480

**(2) Mask through special registers SM an d SD**

481

482

1) External input interrupt mask register

483

484

(% style="margin-left:auto; margin-right:auto" %)

485

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

486

|**Special register number**|**Type of interrupt**|**Instruction**|**Defaults**

487

|SM352|X0 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

488

|SM353|X0 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

489

|SM354|X1 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

490

|SM355|X1 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

491

|SM356|X2 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

492

|SM357|X2 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

493

|SM358|X3 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

494

|SM359|X3 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

495

|SM360|X4 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

496

|SM361|X4 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

497

|SM362|X5 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

498

|SM363|X5 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

499

|SM364|X6 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

500

|SM365|X6 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

501

|SM366|X7 rising edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

502

|SM367|X7 falling edge interrupt|ON: shield interrupts; OFF: interrupt allowed|OFF

503

504

2) Timer interrupt mask register

505

506

(% style="margin-left:auto; margin-right:auto" %)

507

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

508

|**Special register number**|**Type of interrupt**|**Instruction**|**Default**

509

|SD350|1st to 16th timer interrupt|(((

510

Each bit can control the mask of an interrupt.

511

512

ON: shield interrupts; OFF: interrupt allowed

513

)))|0

514

|SD351|17th to 32th timer interrupt|(((

515

Each bit can control the mask of an interrupt.

516

517

ON: shield interrupts; OFF: interrupt allowed

518

)))|0

519

|SD352|33th to 48th timer interrupt|(((

520

Each bit can control the mask of an interrupt.

521

522

ON: shield interrupts; OFF: interrupt allowed

523

)))|0

524

|SD353|49th to 64th timer interrupt|(((

525

Each bit can control the mask of an interrupt.

526

527

ON: shield interrupts; OFF: interrupt allowed

528

)))|0

529

|SD354|65th to 80th timer interrupt|(((

530

Each bit can control the mask of an interrupt.

531

532

ON: shield interrupts; OFF: interrupt allowed

533

)))|0

534

|SD355|81st to 96th timer interrupt|(((

535

Each bit can control the mask of an interrupt.

536

537

ON: shield interrupts; OFF: interrupt allowed

538

)))|0

539

|SD356|97th to 100th timer interrupt|(((

540

Each bit can control the mask of an interrupt.

541

542

ON: shield interrupts; OFF: interrupt allowed

543

)))|0

544

545

3） High-speed counter interrupt mask register

546

547

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

548

|**Special register number**|**Type of interrupt**|**Instruction**|**Default**

549

|SD382|1st to 16th high-speed counter interrupt|(((

550

Each bit can control the mask of an interrupt.

551

552

ON: shield interrupts; OFF: interrupt allowed

553

)))|0

554

|SD383|17th to 32nd high-speed counter interrupt|(((

555

Each bit can control the mask of an interrupt.

556

557

ON: shield interrupts; OFF: interrupt allowed

558

)))|0

559

|SD384|33th to 48th high-speed counter interrupt|(((

560

Each bit can control the mask of an interrupt.

561

562

ON: shield interrupts; OFF: interrupt allowed

563

)))|0

564

|SD385|49th to 64th high-speed counter interrupt|(((

565

Each bit can control the mask of an interrupt.

566

567

ON: shield interrupts; OFF: interrupt allowed

568

)))|0

569

|SD386|65th to 80th high-speed counter interrupt|(((

570

Each bit can control the mask of an interrupt.

571

572

ON: shield interrupts; OFF: interrupt allowed

573

)))|0

574

|SD387|81st to 96th high-speed counter interrupt|(((

575

Each bit can control the mask of an interrupt.

576

577

ON: shield interrupts; OFF: interrupt allowed

578

)))|0

579

|SD388|97th to 100th high-speed counter interrupt|(((

580

Each bit can control the mask of an interrupt.

581

582

ON: shield interrupts; OFF: interrupt allowed

)))|(((

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.

592

593

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.

594

595

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

596

[[image:28.png]]

597

598

(1) Instruction for calling subroutines

599

600

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.

601

602

Through this programming method, the use of the same logic program for different conditions can reduce the number of ladder diagram steps and improve the readability of the ladder diagram.

603

604

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

[[image:29.png]]

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

611

612

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

613

614

3) The subroutine can be nested up to 32 levels. If the level exceeds 32 levels, a serious error will be reported and the ladder diagram operation will be forcibly stopped.

615

616

617

=== **Positioning instructions** ===

----

(1) Event

1) ON event

If the high-speed pulse instruction is turned on during the ON event, the high-speed pulse instruction will be sent as normal. If the ON contact of the trigger event in the scan period is turned OFF during the pulse sending, select whether to continue sending the pulse or stop the pulse according to the unscanned processing sign bit.

626

627

(% style="margin-left:auto; margin-right:auto" %)

628

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

629

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

630

631

When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. At this time, it should be noted that if the trigger event OFF contact turns ON after the pulse is sent, the pulse will be sent again.

632

633

When the sign bit is 1 (stop sending pulses), if the trigger event ON contact turns OFF in a certain scan period, it will decelerate and stop.

2) TIME event

If the high-speed pulse instruction is turned on in the TIME event, the high-speed pulse instruction will be sent as normal. If the instruction is not scanned in a certain scan period during the pulse transmission, select whether to continue sending the pulse or stop the pulse according to the non-scanned sign bit.

638

639

(% style="margin-left:auto; margin-right:auto" %)

640

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

641

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

642

643

When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. In the TIME event, it is impossible to ensure that the instruction is scanned in every scan cycle, so you should avoid using high-speed pulse instructions in the TIME time, otherwise the pulse will be sent again after the pulse is sent.

644

645

When the sign bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the sign bit is set to 1 (stop sending pulses), there will be no pulse sending.

(2) Subroutine

If the high-speed pulse instruction is turned on in the subroutine, the high-speed pulse instruction will be sent as normal. If the scanning period is closed during pulse sending, select whether to continue sending or stop the pulse according to the non-scanned sign bit.

650

651

(% style="margin-left:auto; margin-right:auto" %)

652

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

653

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

654

655

When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, the pulse will continue to be sent until it stops. At this time, it should be noted that if the subroutine is called again after the pulse is sent, the pulse will be sent again.

656

657

When the sign bit is 1 (stop sending pulses), if the subroutine is closed during high-speed pulse sending, the speed will decelerate and stop. If the subroutine is closed before sending the pulse, then no pulse is sent.

**（3） Interrupt**

1） External interrupt

662

663

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 non-scanned sign bit.

664

665

(% style="margin-left:auto; margin-right:auto" %)

666

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

667

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

668

669

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

670

671

When the sign bit is 1 (stop sending pulse), the high-speed pulse decelerates and stops.

2) Timer interrupt

If the high-speed pulse instruction is turned on in the timer interruption, the high-speed pulse instruction is sent as normal. If the instruction is not scanned in a certain scan period in the pulse transmission, the pulse continues to be sent or the pulse stops is selected according to the non-scanned sign bit.

676

677

(% style="margin-left:auto; margin-right:auto" %)

678

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

679

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

680

681

When the sign bit is 0 (continue to send pulse), if the instruction is not scanned in the current scan cycle, continue to send pulses until it stops. In the timer interrupt, it is impossible to ensure that the instruction is scanned in every scan cycle, so it is necessary to avoid using high-speed pulse instructions in the T timer interrupt. Otherwise, after the pulse transmission is completed, the pulse will be sent again.

682

683

When the sign bit is 1 (stop sending pulses), if the instruction is not scanned in the current scan cycle, it will decelerate and stop. In the TIME event, if the sign bit is set to 1 (stop sending pulses), there will be no pulse sending.

684

685

3) HIgh-speed comparison interrupt

686

687

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 non-scanned sign bit.

688

689

(% style="margin-left:auto; margin-right:auto" %)

690

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

691

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

692

693

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

694

695