PLC Editor2 Help (LX6)

= **Overview** =

Compared with LX5CPU series, LX6CPU series has new FB/FC function. The following text describes the new or changed part of the software to support FB/FC function. For other functions, please refer to the “LX6V Series Software Help Document” in PLC Editor2 software.

4

5

= **Programming** =

6

7

== **Overall Introductions** ==

=== **Toolbar** ===

Add ladder diagram symbol menu for inserting series/parallel operation blocks:

12

13

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

14

[[image:图片108.png]]

15

16

=== **Project Management** ===

17

18

Add function blocks, functions, custom structures, custom unions, and global variables:

19

20

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

21

[[image:图片1.png]]

22

23

=== **Ladder Diagram Editing** ===

24

25

The program page is divided into the upper and lower areas of variable table and ladder diagram editing:

26

27

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

28

[[image:图片2.png]]

29

30

Variables can be created, deleted, and moved up and down in the variable editing area. For detailed operation of variables, please refer to [[4 Variable>>https://docs.we-con.com.cn/bin/view/LX6/PLC%20Editor2%20Help%20(LX6)/#H4Variable]].

31

32

Users can write programs in the ladder diagram editing area. After selecting a node in the network, elements such as contacts, operation blocks, and coils can be inserted through the ladder diagram symbols, the instruction editing window, and shortcut keys on the toolbar, or existing elements can be modified and deleted.

33

34

**1) Instruction editing**

35

36

Method 1: insert ladder diagram symbol;

37

38

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

39

[[image:图片3.png]]

40

41

Method 2: insert by shortcut key;

[[image:图片4.png]]

Method 3: click Enter or directly input characters.

46

47

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

48

[[image:图片5.png]]

49

50

**2) Row and column editing/network editing**

51

52

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

53

[[image:图片6.png]]

54

55

=== **Description of Programming Restrictions** ===

56

57

* FC does not support the use of FB;

58

* Array indexing supports variables, but array nesting is not supported. For example: array[var] is allowed, array[array[var] is not allowed;

59

60

FB/FC does not support the use of combined device as variables;

61

62

* FB/FC, structure/union support up to 6 levels of nesting;

63

* Support variables used by contacts, coils, FB/FC, and application instructions;

64

* Variable names are not case-sensitive, so A1 and a1 are the same variable;

65

66

Do not support the use of device T/C/HSC/LC as BOOL input and output parameters of FB/FC.

67

68

= **Function Blocks and Functions (FB/FC)** =

69

70

== **Function Blocks (FB)** ==

71

72

Function block can encapsulate a part program that is reused in a program into a general program block, which can be called repeatedly in a program. Using function blocks in programming can improve the efficiency of program development, reduce programming errors, and improve program quality.

73

74

Function blocks can produce one or more values when executed, and retain their own special internal variables. The controller execution system allocates memory to the internal status variables of the Function Blocks, and these internal variables constitute their own state characteristics. For the input variable value of the same parameter, there may be different internal state variables, and different calculation results will be obtained.

75

76

The basic steps of using a function block are: create a new function block -> program a function block -> instantiate a function block -> run a function block.

77

78

=== **Create a New Function Block** ===

79

80

Create a new function block via PLC Editor2 software.

81

82

Right-click the "Function Block" node in the project management area, select the New, enter the function block name and other information in the pop-up dialog box, and click "OK" to complete the creation of the function block.

83

84

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

85

[[image:图片7.png]]

86

87

=== **Function Block Programming** ===

88

89

Function blocks only support ladder diagram programming. Double-click the newly created function block under the "Function Block" node to enter the function block program editing interface.

90

91

There is no difference between the function block program editing interface and the common program editing interface, and there is a local variable definition window in both.

92

93

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

94

[[image:图片8.png]]

95

96

① Category: Properties of function block variables.

97

98

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

99

|=**Category**|=**Category description**|=(% style="width: 555px;" %)**Description**

100

|VAR|Local variable|(% style="width:555px" %)It is only valid in this logic block and cannot be accessed externally

101

|VAR_IN_OUT|Input and output variable|(% style="width:555px" %)Input and output variables can not only be passed into the called logic block, but also can be modified inside the called logic block

102

|VAR_INPUT|Input variable|(% style="width:555px" %)This parameter is provided by the logic block that calls it and command passed to the logic block is entered

103

|VAR_OUTPUT|Output variable|(% style="width:555px" %)Provide parameters to the logic block that calls it, output structure data from the logic block

104

|VAR_TEMP|Temporary variables|(% style="width:555px" %)Variables used for program and function block internal storage, and when the block is called each time, temporary variables are initialized

② Symbol

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

109

|=**Category**|=**Category description**|=**Description**

110

|CONSTANT|Constant|During the running of the program, this data can only be read but not modified

111

|RETAIN|Reserved|This variable will be saved after power-off, and the initialization operation will be performed when the initial value is set.

112

|PRESISTENT|Save|This variable will be saved after power-off, and the initialization operation will not be performed when the initial value is set. This variable will only be cleared when the PLC memory is cleared

113

114

③ Name: the name of the variable. Refer to the input constraints of the variable for the name constraints.

115

116

④ Data type: The variable data type supports BOOL, BYTE, INT, DINT, REAL and so on, and user can also define array variables, structures, and union. When using a structure variable, user needs to create structure members in the structure of the global variable.

117

118

⑤ Initial value: Set the initial data at the start of variable execution.

119

120

The function block program uses ladder diagram programming. In the function block program, functions (FC) or function blocks (FB) can be called, and up to 6 levels of nesting are supported.

121

122

In addition to variables, function block programs can also use devices as global variables. The current ladder diagram can use variable contacts, coils, function blocks/functions and some 5V instructions. (For details, please refer to "LX6V PLC Programming Manual")

123

124

=== **Example: Encapsulating AND with FB** ===

125

126

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

[[image:图片9.png]]

**Function block instantiation call**

131

132

After the FB program is written, it needs to be instantiated and called for the function block to be used in the application program. In the upper menu of the software, click the "Insert Operation Block" button in the "Ladder Diagram Symbol" or execute the shortcut key F2.

133

134

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

135

[[image:图片10.png]]

136

137

After inserting the function block, enter the name of the function block at the "???" inside the function block, and press the "Enter" key on the keyboard.

138

139

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

140

[[image:图片11.png]]

141

142

After entering the function block name, "???" will appear at the top of the function block instruction. Enter the variable name in "???", press the "Enter" key, and click "OK" in the pop-up dialog box to complete the instantiation of the function block.

143

144

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

145

[[image:图片12.png]]

146

147

== **Function (FC)** ==

148

149

Function (FC) is an independently encapsulated program block. The program block can define input/output parameters type, and can also define non-static internal variables, so when a function is called with the same input parameters, the output result is the same. The important feature of a function is that its internal variables are static, without internal status storage; the same input parameters will get the same output, and it is the main difference between a function (FC) and a function block (FB). Function (FC) is often used in various mathematical operation functions as the basic algorithm unit, such as sin(x) and sqrt(x), which are typical function types.

150

151

The basic steps of using a function are: New Function -> Function Programming -> Call Function.

152

153

=== **New Function** ===

154

155

Create a new function via PLC Editor2 software.

156

157

Right-click the "Function Block" node in the project management area, select the New, enter the function name and other information in the pop-up dialog box, and click "OK" to complete the creation of the function.

158

159

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

160

[[image:图片13.png]]

161

162

=== **Function Programming** ===

163

164

The function only supports ladder diagram programming. Click the newly created function under the "Function" node to enter the function program editing interface. The function program editing interface is similar to that of function block.

165

166

* Compared with the variables of the function block, the function variables are non-retentive and cannot be saved after power-off;

167

* The function program uses the ladder diagram programming, and in the function program, functions can be called. The function itself can be called by other functions, function blocks and programs;

168

* In addition to variables, function programs can use global variables and devices;

169

* In the function program, instructions related to status or under multi-cycle execution cannot be used.

170

171

=== **Example: Encapsulating OR with FC** ===

172

173

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

[[image:图片14.png]]

**Function calling**

After the FC program is written, it can be used in function blocks/program.

179

180

Click the "Insert Operation Block" button in the "Ladder Diagram Symbol" and enter the function name.

181

182

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

183

[[image:图片15.png]]

184

185

=== **Function Return Value** ===

186

187

Create a new function, or select the function in the project management and right-click to set, click "..." in the pop-up dialog box, and the input assistant dialog box will pop up, where user can select the data type of the return value.

188

189

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

[[image:图片16.png]]

In the editing interface of the function module, the function name (FC1 in the figure below) can be programmed as the return value variable.

[[image:图片17.png]]

When the return value is a FB function block or a custom structure, the function name can be used as the instance name of the function block (FB), as the first-level variable to call the input and output variables under the FB. As shown in the figure below, the return value of FC1 is the FB1 function block, and the variable newVar of FB1 can be set through FC1.newVar.

198

199

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

200

[[image:图片18.png]]

201

202

When using a custom function in the network view, there will be one more pin than the built-in function, and the pin description is empty, followed by a variable of the same data type as the function return value (FC0_return in the figure below), which is used to save the return value of the function (support blank).

203

204

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

205

[[image:图片19.png]]

206

207

== **Support Constant Input** ==

208

209

=== **Usage Rules** ===

210

211

All operation block input pins (except for input output / output type) can be set to constant, constant type supports binary, octal and hexadecimal system. Integer constants are 64 bits.

212

213

=== **Input Format** ===

214

215

Floating point constants: -10.0, 1.2E+34

216

217

Decimal constants: 10, -10

218

219

Binary constants: 2#10111001

220

221

Octal constants: 28#0007, 8#1777

222

223

Hexadecimal constants: 16#FF, 16#FFFF, 16#FFFFFFFF

224

225

BOOL constants: TRUE and FALSE

226

227

Time constants: TIME#0ms, valid range: 0ms to 4294967295ms

228

229

TOD#0:0:0.001, valid range: 0:0:0 to 23:59:59

230

231

DATE#1970-1-1, valid range: 1970-01-01 to 2106-02-07

232

233

DT#1970-01-01:0:0:0, valid range: 1970-01-01:0:0:0 to 2106-02-07-06:28:15

234

235

LTIME#0ns, valid range: 0ns to (2^64-1)ns

=== **Examples** ===

The use of octal and decimal integers:

240

241

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

242

[[image:图片20.png]]

243

244

== **Support Input and Output Vacant** ==

245

246

=== **Usage Rules** ===

247

248

① Built-in FC is not allowed to be vacant

249

250

② Input of the custom FC is not allowed to be vacant, but the output can be vacant;

251

252

③ Custom FB input and output can be vacant;

253

254

④ Built-in FB can be vacant unless otherwise specified (for details, please refer to the description of the built-in FB in "LX6V Series PLC Programming Manual").

=== **Examples** ===

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

[[image:图片21.png]]

== **Support Extended Input** ==

263

264

Input an operation block that supports extended input, select the operation block area, right-click ~-~-> select Add Input or use the shortcut key Shift+I to add additional input points, for example:

265

266

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

267

[[image:图片22.png]]

268

269

To delete the added input point, user can select the added input point and click the “Delete” to delete it.

270

271

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

[[image:图片23.png]]

= **Variable** =

== **Custom Variables** ==

277

278

In PLC Editor2 programming, in addition to directly using addresses, such as M, D, S, X, Y and other devices for programming, user can also program in the form of [variables] without specific storage addresses, improve the convenience and reusability of code writing. The types of custom variables supported by this software are as follows:

279

280

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

281

|=**Data type**|=**Keyword**|=**Length (bits)**|=**Value range**

282

|BOOL|BOOL|1|FALSE (0) or TRUE (1)

283

|Byte|BYTE|8|0 to 255

284

|Word|WORD|16|0 to 65535

285

|Double Word|DWORD|32|0 to 4294967295

286

|Long Word|LWORD|64|0-(2^64-1)

287

|Short Int|SINT|8|-128-127

288

|Unsigned Short Int|USINT|8|0 to 255

289

|Int|INT|16|-32768 to 32767

290

|Unsigned Int|UINT|16|0 to 65535

291

|Double Int|DINT|32|-2147483648 to 2147483647

292

|Unsigned Double Int|UDINT|32|0 to 4294967295

293

|Long Int|LINT|64|-2^63 -(2^63-1)

294

|Real Number|REAL|32|±1.175495E-38 to ±3.402823E+38

295

|Long Real Number|LREAL|64|±2.225073858507202E-308 to ±1.797693134862315E+308

296

|(% rowspan="5" %)Time|TIME|(% rowspan="4" %)32|0ms - 4294967295ms

297

|TIME_OF_DAY|0:0:0 - 23:59:59

298

|DATE|1970-01-01 - 2106-02-07

299

|DATE_AND_TIME|1970-01-01 : 0 : 0 : 0 - 2106-02-07-06 : 28 : 15

300

|LTIME|64|0ns - (2^64-1)ns

301

302

== **Custom Variables** ==

303

304

PLC Editor2 supports custom variables, users can directly use variable names in the program by defining global variables/local variables. The following rules shall be followed when defining global variable names:

305

306

① Can only be composed of "numbers, letters and underlines" and cannot start with "numbers";

307

308

② Cannot have the same name as "instruction, device, constant, standard data type";

309

310

③ Cannot have the same name as "program, function block, function, custom structure, custom union";

311

312

④ It cannot be keywords such as "struct, union, GVL";

313

314

⑤ It cannot start with "device + number";

315

316

⑥ The length should not exceed 32 characters.

317

318

Note: Variable names are case insensitive, i.e. A1 and a1 are the same variable.

319

320

=== **Variable Data Types** ===

321

322

Variable definition supports structures and arrays, and supported variable data type is shown in【Table 1 Custom variable types supported by this software】

323

324

=== **Define Global Variables** ===

325

326

The "Program" -> "Global Variables" -> "GVL" table in the PLC Editor2 programming software project management column is used for variable management, which can realize the addition, deletion and editing of variables.

327

328

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

329

[[image:图片24.png]]

330

331

**Add variable**: Click the New button [[image:image-20230721113024-1.png]] at the top left of the global variable table to create a new global variable.

332

333

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

334

[[image:图片25.png]]

335

336

① Variable flags (constant and retain type) can be set in the category column, and the settings in the initial value column are only valid for non-retentive variables;

337

338

② Double-click the variable name column in the variable table to enter the custom variable name, and you can directly use the variable name to program when programming

339

340

③ Data type can choose the supported basic data types, arrays, structures, and unions (define the structure and union in advance). When selecting array as the data type, set the array variable type and interval length in the dialog box (the maximum length of the interval is [0,49]). When selecting a pre-defined structure or union, user can define the structure or union variable;

341

342

④ Double-click the initial value column to define the initial value for the variable, and the array, structure, and union can define the initial value of each element separately;

343

344

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

345

[[image:图片26.png]]

346

347

⑤ User can set the comment information of the variable in the comment column.

348

349

**Delete variable**: Click the delete button [[image:image-20230721113115-2.png]] on the top left of the global variable table to delete the selected variable.

350

351

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

[[image:图片27.png]]

=== **Defining Local Variables** ===

356

357

The difference between local variables and global variables is that local variables are defined in the program page/function block/function, and the scope is only in the defined window.

358

359

In the local variable window category, variables can be set as input variables, output variables, input and output variables, and temporary variables.

360

361

=== **Defining Structure/Union** ===

362

363

If you need to define a structure/union variable in the variable definition, you need to define the data structure of the structure/union in advance.

364

365

In "Program" -> right-click "Custom structure" / "Custom union" -> select "New" -> enter the program name in the pop-up dialog box -> click "OK", double-click the data structure name, open the data structure definition window to define the structure/union.

366

367

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

368

[[image:图片28.png]]

369

370

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

371

[[image:图片29.png]]

372

373

After establishing the structure/union and variable in the data structure definition window, user can select the structure in the data type of variable definition to define the structure/union variable. The operation steps are as follows:

374

375

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

376

[[image:图片30.png]]

377

378

①Create a new Variable;

379

380

②Set the data type and select the input helper;

381

382

③Click the structure data type, select the name of the custom structure STRUCT0, and click "OK";

383

384

④Use the following methods to quote the defined structure data variable stu in the ladder diagram.

385

386

Method 1: Double-click the device variable name, click the button on the right, and select the variable in the variable tree information displayed in the pop-up window.

387

388

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

389

[[image:图片31.png]]

390

391

Method 2: Write the ladder diagram and directly input stu.stu_a.

392

393

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

394

[[image:图片32.png]]

395

396

=== **The Usage of Variable** ===

397

398

After the variable is defined, the variable name can be directly used for programming during programming, and there is no need to re-allocate the device.

399

400

1. Directly perform variable programming operations;

401

1. When using an array variable, use "[Number]" in programming to indicate the array element, and the number starts from 0;

402

1. When using a structure variable, use "structure variable name. "Member variable" in programming to indicate a structure member;

403

1. When using global variables, use "GVL. variable name" in programming to indicate a global variable.

404

405

== **Using Variables as Array Subscripts** ==

406

407

=== **Usage Rules** ===

408

409

General rules for using variables as array subscripts: in the entire variable composition, at most one variable is used as a subscript, and the format is defined as array[index] or stu.var[index], wherein array means an array or a structure array, and index means a variable , stu represents the structure.

410

411

=== **Basic Combination Types** ===

412

413

1) array variable, as an array variable, only supports BOOL, BYTE, DATE, ATE_AND_TIME, DINT, DWORD, INT, LINT, LREAL, LTIME, LWORD, REAL, SINT, TIME, TIME_OF_DAY, LDINT, UINT, USINT, WORD, does not support pointer variables, etc.;

414

415

(2) index variable, as the variable of the array subscript, supports devices C, D, HSC, LC, R, SD, T, V, Z, and does not allow offsets; supports variable types BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT; array nesting is not supported, such as array[index[5]];

416

417

(3) Structure arrays with double or multiple variables are not supported;

=== **Examples** ===

Create an array variable array[10] in the variable table, and declare array[1] for reference in the ladder diagram.

422

423

(4) Two-dimensional or multidimensional arrays array[index1][index2] are not supported.

424

425

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

426

[[image:图片33.png]]

427

428

If the array is defined in the global variable table, it is used as GVL.array[1] in the ladder diagram;

429

430

If the array is defined in a custom structure/union, it will be used as stu.array[1] in the ladder diagram.

431

432

== **Variable Binding Address** ==

433

434

In programs or global variables, custom variable binding to soft element addresses is supported. After binding, the address of the custom variable is associated with the address of the soft element. The binding method involves entering a valid mapping address in the variable definition table. Only D or R soft elements can be mapped in program pages or global variables

= **Compilation** =

The ladder diagram function remains consistent with the 5V function, including single-page compilation and full compilation, compilation result display, and double-clicking the compilation error report to jump to the compilation error problem. The current compilation will check the following errors:

439

440

**(1) Single-page compilation** will only compile the program of the current page, and **full compilation** will compile the programs of all pages in the project management.

441

442

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

443

[[image:图片34.png]]

444

445

(2) Quick compilation

446

447

Check Quick Compilation in [Toolbar] ~-~-> [View] ~-~-> [Experiment], after enabling Quick Compilation, click Compile or Quick Compile to skip the compiled network and velocity up the compilation.

448

449

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

450

[[image:图片35.png]]

451

452

(3) Normal program without error

453

454

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

[[image:图片36.png]]

(4) Compilation error

460

461

① Using undefined variables

462

463

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

[[image:图片37.png]]

② The variable type of the function block call does not match

468

469

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

470

[[image:图片38.png]]

471

472

③ Too many layers of structure nesting (more than 6 layers)

473

474

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

475

[[image:图片39.png]]

476

477

④ The instantiation type does not match

478

479

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

480

[[image:图片40.png]]

481

482

(5) Error jump: double-click the error message to jump to the error device for highlighting display.

483

484

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

485

[[image:图片41.png]]

486

487

= **Communication and Monitoring** =

488

489

== **Communication Test** ==

490

491

(1) Function: The main purpose of the communication test is to check whether the project model created by the current PLC Editor2 software matches the model of the lower PLC and whether it can be connected for normal communication!

(2) Steps for usage:

① Open and run PLC Editor2;

496

497

② Move the mouse pointer to the [Online] module above the program panel;

498

499

③ Move the mouse pointer to the [Transfer Settings] button, and left-click the button;

500

501

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

502

[[image:图片42.png]]

503

504

④ Wait for the program to respond, and the [Communication Settings] dialog box will pop up;

505

506

⑤ The [Communication Settings] dialog box will pop up. If the [Detailed Settings] checkbox is not checked, select the specified port, and the panel is shown as below;

507

508

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

509

[[image:图片43.png]]

510

511

⑥ There are currently three channels that support communication with the PLC. Select the corresponding communication channel and configure the corresponding parameters (the use of each channel will be introduced below), and click the [Communication Test] button. If the PLC model is inconsistent with the project model, the following window will pop up.

512

513

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

514

[[image:图片44.png]]

515

516

If there is a problem with the selected channel and the connection cannot be made, the following window will pop up.

517

518

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

519

[[image:图片45.png]]

520

521

If it can communicate with PLC normally, the following window will pop up.

522

523

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

524

[[image:图片46.png]]

525

526

(3) Use of three communication channels

527

528

① USB connection: The USB channel of the 6V PLC uses the USB-C (Type-c) interface, which only supports USB-C cable for connection. If the current PC uses a USB-C cable to connect to the USB-C port of the PLC, the software will select [USB connection] button by default.

529

530

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

531

[[image:图片47.png]]

532

533

② Serial port connection: The serial port channel of the 6V PLC device uses the RS485 interface. After the PC is connected to the PLC using the 485 cable, you can select the required baud rate through the drop-down box of [Baud Rate], and check the [Detailed Settings] button to configure the corresponding serial port parameters. (Note: The default parameters of the serial port connection in the new 6V project are also the default parameters of the 6V PLC 485 serial port.)

534

535

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

536

[[image:图片49.png]]

537

538

③ Ethernet configuration: 6V PLC supports communication via Ethernet connection. Plug the Ethernet interface on the 6V PLC device into the network cable to support Ethernet communication! Click the [NIC selection] drop-down box to select the network card, and enter the IP address of the PLC device in the [IP Address] input box to start the communication connection.

539

540

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

[[image:图片50.png]]

If user do not know the IP address of the PLC, first upload the parameter information through the USB-C or serial port, and then view the Ethernet-related information configuration on the parameter interface; or user can click the [Device Search] button to search for the PLC devices connected in the same network segment.

545

546

**Device search**: used to search for all PLCs that support Ethernet functions in the network segment that match the subnet mask. The network segment that matches the subnet mask refers to following circumstance: if the IP of the machine is 192.168.56.237 and the subnet mask is 255.255.255.0, then the PLC in the network segment of 192.168.56 is searched; if the IP of the machine is 172.16.56.1, the subnet mask is 255.255.0.0, then the PLC in the network segment of 172.16 is searched; If the IP of the machine is 10.244.56.9 and the subnet mask is 255.0.0.0, then the PLC in the network segment of 10 is searched.

547

548

Use of device search: Click [Device Search] to pop up the search interface, click the search button to search for devices in the relevant network segment. Select the device information line to be connected, and then click OK. The selected IP address information will be automatically filled in IP address input box of [Communication Settings] interface.

549

550

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

[[image:图片51.png]]

(4) Device Info

① Function: It is used to view the relevant information of the connected PLC, such as PLC model, production date and other relevant information.

556

557

② Use steps: After establishing a communication connection with the PLC device through the above steps, user can click the [Device Information] button to pop up the corresponding device information interface.

558

559

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

560

[[image:图片52.png]]

561

562

== **Ladder Diagram Monitoring** ==

563

564

**Function**:Monitor the value of the devices and FB/FC parameters on the ladder diagram, modify and debug the program.

**Steps:**

① Connect to the PLC and switch to monitoring mode;

569

570

② Modification of device value: modify the used device value in the pop-up window for modifying device value.

571

572

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

573

[[image:图片53.png]]

574

575

The window for modifying device values supports modification of variables.

576

577

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

578

[[image:图片54.png]]

579

580

③ Variable value monitoring: In the monitoring mode, in the local variable table window, select a variable, right-click the menu, click “Add to variable window” to add the variable to the monitoring variable window below, and then monitor the variable value.

581

582

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

583

[[image:图片55.png]]

584

585

Variable value modification: after adding the variable to the monitoring variable window, modify the value in the following steps.

586

587

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

588

[[image:图片56.png]]

589

590

= **Search and Replace** =

591

592

**Search/Replace**: Similar to the search and replace function of OFFICE, it can locate the data block specified by the user in a large amount of data, or perform batch addition, deletion, modification and query, which can greatly improve efficiency.

593

594

**Usage method**: Open the main program, after creating a new project, click [Ctrl] + [F] on the keyboard to pop up the search/replace interface, as shown in the figure below.

595

596

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

597

[[image:图片57.png]]

598

599

Buttons are divided into four categories: device, instruction, string and result, as shown in the figure above. Click any one to switch to the corresponding operation interface.

600

601

**Device:** The following contents can be searched/replaced.

① All devices

② Legal custom variables, including array type variables and multi-level variables

606

607

③ Real numbers in scientific notation format

608

609

④ Strings with quotation marks

610

611

⑤ Customize the name of FC

⑥ FB instance names

(% class="box infomessage" %)

616

(((

617

**Note: **It does not support instruction search, does not support the option setting of device points, does not support replacing variable names in the variable list with devices, and does not support replacing variable names in the variable list with existing variable names

618

)))

619

620

**Instruction: **The following contents can be searched/replaced.

①All instructions

②Built-in FB/FC

③ Custom FB/FC

= **Device Usage List** =

629

630

The device usage list mainly displays the specified type of devices. You could check the usage, and the corresponding comment of the device. Devices used in program pages such as scans, events, subroutines, interrupts, function blocks, and functions can be displayed.

631

632

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

633

[[image:图片58.png]]

634

635

**Instructions** **for** **device usage list:**

636

637

① Device selection drop-down box: select a device, search and display the usage of the corresponding type of device (starting from serial number 0);

638

639

② Starting device drop-down box: You can input the full name or serial number of the starting device, press the Enter key or click the "Search" button to search for the usage of specified type of device (starting from the initial button, search and display the serial number). Record the search record in the drop-down box. After selecting the record, you could perform the search again.

640

641

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

642

[[image:图片59.png]]

643

644

③Search button: perform a search operation. When the starting device is empty, it will prompt to input a device.

645

646

④ Search range: specify the device search range;

647

648

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

649

[[image:图片60.png]]

650

651

Whole project: for all program pages of the current project;

652

653

Current program page: Search only for the currently active program page.

654

655

Current program type: Only for all program pages of the same type in the currently activated program page. (Program page types are divided into: scan, event, subroutine, interrupt, function block, function.)

⑤ Display options

All devices: After selecting, search and display all devices of this type;

660

661

Used devices: After selecting, search and display the used devices of this type according to the contact and coil options;

662

663

Neither the contact nor the coil is selected, and all the devices of this type that have been used in the program are displayed;

664

665

Select the contact (coil) to display the device of this type as the contact (coil) in the program.

666

667

Select both contacts and coils, display the devices of this type that are used as contacts and coils in the program.

668

669

Unused devices: After selecting, display all the devices of this type that are not used in the program.

670

671

⑥ Expand and close the sub-item of the device usage list, including the instruction, step number, type and other information of the device in the program. Double-click the content of the subitem to locate the corresponding position in the program.

672

673

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

674

[[image:图片61.png]]

675

676

Device comment: (the background color is white) displays the comment of the device.

677

678

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

679

[[image:图片62.png]]

680

681

= **Expansion Module** =

682

683

== **Description** ==

684

685

The expansion module is used to expand the functions of the PLC. It is easy to install, and the number of modules can be increased or decreased. The types of modules include IO modules, analog quantities, communication modules, etc. (LX6V series PLC currently only supports IO modules). The upper computer can download the module parameter information to the expansion module through the function of the expansion module configuration.

686

687

== **Use of Functions** ==

688

689

(1) Expansion module configuration interface display

690

691

[Expansion module configuration] is located under the [Extended function] note of project management, double-click to open the expansion module configuration interface!

692

693

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

694

[[image:图片63.png]]

695

696

(2) Functions of each part of the expansion module configuration interface

697

698

① Device information interface: the information under the PLC host node stores the host points supported by the current model. User can manually select or switch different host points. The maximum number of expansion modules supported by PLC with different points is different; the information under the expansion module node stores the expansion module models supported by the current model, and user can choose to add modules of the corresponding model;

699

700

② Display interface for the specific information of the currently added module: the slot number shows the position of the current module configuration (the 0th position defaults to display the PLC information with the corresponding points); the configuration device name shows the model of the expansion module; the equipment description shows the brief introduction of the expansion module; the device occupation shows the device range mapped by the current module (note: when adding a module, an unused address will be allocated in order by default); the actual installation type shows the actual expansion module model at the corresponding position of the lower computer (note: this will only display the actual expansion module model at the corresponding position in the monitoring mode); the device version number shows the actual expansion module version number of the corresponding position of the lower computer (note: only in the monitoring mode will the actual expansion module model of the corresponding position be displayed);

701

702

③ Configuration interface of expansion module: configure the extension module in a visual way, which makes the effect more intuitive! Operations such as moving the position of the expansion module, deleting the expansion module, and exchanging the position of the expansion module improve the efficiency of human-machine interaction.

703

704

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

705

[[image:图片64.png]]

706

707

(3) Basic operation of expansion module configuration

708

709

① Add an expansion module: first select the corresponding PLC host points, then select the corresponding expansion module model and double-click, the picture of the corresponding configuration expansion module will appear in the configurationinterface, and the corresponding device information will also appear in the lower left corner of the interface, then the extension module is added successfully.

710

711

When adding an expansion module, the system will assign an unused device address for the IO mapping of the expansion module by default, and the user can also enter the configuration interface to manually modify the range of the IO mapping.

712

713

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

714

[[image:图片65.png]]

715

716

② User can drag the position of the expansion module, and drag the expansion module to different machine slot positions.

717

718

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

719

[[image:图片66.png]]

720

721

③ Configure expansion module parameters: method 1: user can right-click on the corresponding expansion module in the configuration interface to select configuration parameters or double-click to directly pop up the parameter configuration interface; method 2: in the configuration interface of the expansion module, double-click the corresponding module configuration line to pop up the parameter configuration interface.

722

723

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

724

[[image:图片67.png]]

725

726

④ The information to be configured is different for different expansion module models, but a default configuration information will be generated when an expansion module is added. Currently there are mainly 3 configuration interfaces.

727

728

* **Device info**: mainly used to store some basic information of the current expansion module.

729

730

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

731

[[image:图片68.png||height="701" width="862"]]

732

733

* **I/O mapping interface**: It is mainly used to allocate the input and output mapping corresponding to the expansion module. Enter a starting device in the edit box, and a continuous address will be automatically assigned. After clicking OK, the corresponding I/O mapping configuration will be saved. (Note: Clicking the reset button will reassign unused addresses according to the order of addresses.)

734

735

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

736

[[image:图片69.png||height="736" width="905"]]

737

738

Note 1: Software that has already been mapped is not allowed to be re-mapped, otherwise an error will be reported when the configuration is saved.

739

740

Note 2: Unsupported I/O mapping address is not allowed to be assigned. (For the address type of I/O mapping supported by the expansion module, please refer to the manual of the corresponding expansion module model.)

741

742

Note 3: For device of octal type X and Y, the address of I/O mapping must be X0~~X7, X10~~X17(consecutive 8-multiple addresses), and discontinuous addresses such as X1~~X10, X2~~X11 are not allowed.

743

744

* **Module configuration interface**: mainly used to configure parameters information of the module. (For the parameter information to be configured by the expansion module, please refer to the manual of the corresponding expansion module model.)

745

746

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

747

[[image:图片70.png||height="669" width="823"]]

748

749

(4) After the configuration of the expansion module interface is completed, the corresponding module configuration information can be downloaded to the PLC through the download interface. The PLC expansion module configuration can also be uploaded through the configuration upload interface.

750

751

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

752

[[image:图片71.png||height="842" width="931"]]

753

754

Note 1: When downloading the configuration of the extension module, the configuration of the module must be continuous in order to ensure normal download. As shown in following left figure, if the expansion module is placed at following intervals, the configuration cannot be downloaded normally. The module position shall be adjusted and the configuration can be downloaded normally when the modules are continuously arranged.

755

756

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

757

[[image:图片72.png||height="412" width="1024"]]

758

759

Note 2: When downloading the extension module configuration, the configuration host points must be the same as the actual PLC host points to ensure normal download.

760

761

(5) After the download is completed, enter the monitoring mode. On the display interface of the specific information of the currently added modules, the actual installation type column and the device version number column will display the corresponding model and version number according to the type of module actually connected to the corresponding position of the PLC.

762

763

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

764

[[image:图片73.png||height="501" width="1650"]]

765

766

(6) User can view the occupied address of the device configured by the expansion module through the device usage list interface.

767

768

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

769

[[image:图片74.png||height="557" width="1699"]]

770

771

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

772

[[image:图片75.png||height="643" width="1699"]]

= **EtherCAT** =

== **Description** ==

778

779

EtherCAT is an open industrial field technology based on Ethernet, which has the characteristics of short communication refresh cycle, small synchronization jitter, and low hardware cost.

780

781

== **Master Station Configuration** ==

782

783

Double-click the EtherCAT node of the project management tree to pop up the EtherCAT configuration, modify the configuration and save it.

784

785

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

786

[[image:图片76.png||height="729" width="1295"]]

787

788

== **Importing and Adding Slaves** ==

789

790

=== **Importing Configurations** ===

791

792

Right-click the EtherCAT node in the project management tree, click New, click the Import button in the pop-up Add Slave window, and select the EtherCAT xml file of the corresponding manufacturer to import.

793

794

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

795

[[image:图片77.png||height="748" width="1332"]]

796

797

=== **Adding a Slave** ===

798

799

Right-click the EtherCAT node in the project management tree, click New, select a slave type and click Add, a new slave node will be added to the EtherCAT node in the project management tree, and click Close to end the operation of adding a slave.

800

801

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

802

[[image:图片78.png||height="955" width="1699"]]

803

804

== **Slave Configuration** ==

=== **Delete** ===

① Right-click the EtherCAT node, select Delete All, and delete all currently created slave station configurations.

809

810

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

811

[[image:图片79.png]]

812

813

② Right-click the slave station under the EtherCAT node, select Delete, and delete the current slave station configuration.

814

815

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

816

[[image:图片80.png]]

817

818

=== **Updating Devices** ===

819

820

① Right-click the EtherCAT node and select Update All Devices to update the configuration information of the current EtherCAT node to the newly imported EtherCAT configuration file information.

821

822

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

823

[[image:图片81.png]]

824

825

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

826

[[image:图片82.png]]

827

828

② Right-click the slave station under the EtherCAT node, select Update equipment, and update the configuration information of the corresponding slave station node to the newly imported EtherCAT configuration file information.

829

830

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

831

[[image:图片83.png]]

832

833

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

834

[[image:图片84.png]]

835

836

=== **Slave Parameters** ===

837

838

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

839

[[image:图片85.png]]

840

841

Double-click the slave station under the EtherCAT node to pop up the EtherCAT configuration dialog box. In the slave station parameter interface, check the enable expert parameter to use the expert process data interface and the check box and edit box below.

842

843

* **Check Vendor ID**: check whether the downloaded slave configuration is consistent with the vendor ID of the slave connected to the PLC during activation;

844

* **Check product ID**: check whether the downloaded slave configuration is consistent with the product ID of the slave connected to the PLC during activation;

845

* **Check the version number**: check whether the version number is consistent during activation;

846

* **SDO access timeout:** set the SDO access time.

847

848

=== **Expert Parameters** ===

849

850

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

851

[[image:图片86.png]]

852

853

* Select ① the synchronization manager table area, select input and output, and ② the PDO allocation table area will be updated with the PDO allocation list corresponding to the output or input of the synchronization manager;

854

* Check or uncheck to enable the ②PDO allocation list area, which will be fed back to the ③PDO list;

855

* Select the checked row in the ③PDO list, and the contents of the ④PDO content table will be updated;

856

* In the ④PDO content table, right-click the menu and select Add or click the ⑤Add button, select the content to be added in the Add PDO content interface, and then click Add;

857

* After selecting the content to be deleted in the ④PDO content table, right-click the menu and select Delete or directly click the ⑥Delete button to delete.

858

859

=== **Process Data** ===

860

861

Except that the process data interface cannot customize the PDO content, other functions are basically the same as the expert process parameters.

862

863

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

864

[[image:图片87.png]]

865

866

=== **I/O Mapping** ===

867

868

For the PDO content set by the process parameters, user can select devices or variables for mapping.

869

870

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

871

[[image:图片88.png]]

872

873

=== **Start-up Parameters** ===

874

875

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

[[image:图片89.png]]

**① Add**

Right-click the menu to select Add or click the Add button directly to enter the interface for adding startup parameters, select the corresponding item, and add startup parameters.

**② Delete**

After selecting the parameter content to be deleted, right-click the menu and select delete or directly click the delete button to delete.

885

886

=== **Slave Information** ===

887

888

Display slave information.

889

890

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

891

[[image:图片90.png]]

892

893

== **Activate Download and Upload** ==

894

895

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

[[image:图片91.png]]

**① Download**

Select EtherCAT node in the project management tree and right-click, and select Download EtherCAT configuration or upload it by using PLC download interface.

**②Upload**

Select EtherCAT node in the project management tree and right-click, and select Upload EtherCAT configuration or upload it by using PLC upload interface.

905

906

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

[[image:图片92.png]]

**③Activate**

Select EtherCAT node in the project management tree and right-click, and select Activate EtherCAT configuration. (Note: The servo device connected to the PLC needs to correspond to the downloaded configuration slave during activation, otherwise an activation error will occur.)

912

913

= **Motion Control** =

914

915

== **Description** ==

916

917

In the LX6V motion control system, the object of motion control is called "logic axis". Axis is the bridge between mapped Motion Control function blocks and servo drives. The logic axis of LX6V is used to control the EtherCAT bus driver conforming to the CIA402 protocol, and can also be configured as local high-velocity pulse output and input (the current version of high-velocity pulse input and output is not yet supported).

918

919

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

920

[[image:图片94.png]]

921

922

Inside the PLC, the basic composition and processing logic of the logic axis are as follows:

923

924

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

925

[[image:图片95.png]]

926

927

== **Motion Control Axis Operation** ==

=== **New** ===

Method 1: Creating a new EtherCAT slave station will automatically create a motion control axis. And the newly created motion control axis will be bound to the newly created EtherCAT slave station.

932

933

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

934

[[image:图片96.png]]

935

936

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

937

[[image:图片97.png]]

938

939

Method 2: Create a new motion control axis directly. The output device of the newly created motion control axis in this way is unallocated by default.

940

941

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

942

[[image:图片98.png]]

943

944

=== **Setting up Output Devices** ===

945

946

Only the idle EtherCAT slave axis can be selected in the drop-down box, click OK after selection, other axes cannot select the output device.

947

948

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

949

[[image:图片99.png]]

950

951

=== **Upload and Download** ===

952

953

Follow the EtherCAT upload and download, there is no separate download and upload interface.

954

955

== **Configuration Interface** ==

956

957

=== **Basic Settings** ===

958

959

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

960

[[image:图片100.png]]

961

962

① Axis number: automatically generated by the system and unique. The current software version only supports binding motion control function blocks through axis numbers;

963

964

② Axis type: the current version only supports the motion control function of the bus servo axis;

965

966

③ Input device: the current version does not support;

967

968

④ Output device: used to select and bind the physical servo axis on the EtherCAT bus;

969

970

⑤ Virtual axis mode: provide virtual axis mode to support use in the mode without physical axis, for debugging purposes or other advanced programming methods;

971

972

⑥ Automatic mapping: TxPDO and RxPDO in the bound EtherCAT bus physical servo axis will be automatically mapped to the output and input supported by motion control.

973

974

975

=== **Unit Conversion Settings** ===

976

977

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

978

[[image:图片101.png]]

979

980

① Reverse: opposite to the set motor rotation direction (for example: after selecting reverse option, set the target position as positive, and the motor will run in the reverse direction);

981

982

② Decimal display of pulse number: display the pulse number value in decimal system;

983

984

③ Number of command pulses for one revolution of the motor/encoder: the real encoder resolution of the bound servo drive;

985

986

④ The amount of movement of the worktable in one rotation: this is the relationship amount between the user unit and the pulse unit;

987

988

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

989

[[image:图片102.png]]

990

991

Example: The encoder resolution of the user's servo axis is 17 bits, and the set pulse number is 131072. At this time, set the movement amount of the worktable to rotate one circle as 1 user unit. When using the motion control function and the target position is 1 (Unit), the number of pulses received by the servo drive is 131072 when the target position is reached, that is, the servo makes one revolution. When the target velocity is set to 5 (Unit)/s, it means that the servo operating velocity in the constant velocity section is 5 revolutions/s.

⑤Enabling gearboxes;

⑥ The amount of movement of the worktable in one rotation: set the movement amount of the worktable for one circle

996

997

⑦⑧ are respectively (5) and (6) in the linear model.

998

999

**Mode/Parameter Setting**

1000

1001

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

1002

[[image:图片103.png]]

1003

1004

① Encoder mode: Incremental mode and absolute mode are optional. Under the current software settings, only incremental mode is supported;

1005

1006

② Mode setting: linear mode and rotary mode are optional. The current software only supports linear mode;

1007

1008

③ Cycle setting: cannot be modified. controlled by the EtherCAT task cycle;

1009

1010

④ Velocity acceleration and deceleration type: currently supports S-curve and T-curve. Among them, the S-shaped curve is a 7-segment and 5-segment adaptive curve;

1011

1012

⑤ Software limit: It is optional to enable software limit. When it is turned on, periodically check whether the target position exceeds the limit in the motion control function;

1013

1014

⑥ Software error response: limit deceleration and axis fault deceleration can be set, currently only support limit deceleration;

1015

1016

⑦ Tracking error: You can set the maximum tracking error threshold allowed by the system (user unit);

1017

1018

⑧ Axis velocity setting: the axis velocity limit function is enabled by default. User can set the maximum velocity (Vel), maximum acceleration (Jerk), and jog maximum velocity (JogVel) respectively;

1019

1020

⑨ Torque setting: set the limit of positive torque and negative torque. The motion control function will check whether the torque value fed back by the servo exceeds the corresponding limit every cycle, and if it exceeds, an error will be reported;

1021

1022

Hardware limit logic, probe, output mode, counter mode setting, preset setting and comparison output setting: bus servo axis does not support such settings.

= **E-CAM** =

== **Description** ==

1027

1028

The electronic cam is essentially the movement of the slave axis following the master axis, and the motion relationship between the master axis and the slave axis can be expressed by cam table data or electronic gear ratio.

1029

1030

== **Instructions for Use of E-CAM Table ** ==

1031

1032

(1) In the project management window, right-click [Electronic Cam Table], click [New], enter the table name, and click [OK] to create an electronic cam table.

1033

1034

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

1035

[[image:图片104.png]]

1036

1037

(2) Open the newly created electronic cam table and enter the relevant configuration interface.

1038

1039

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

1040

[[image:图片105.png]]

1041

1042

(3) Curve description: ①SPos: displacement curve; ②PU Speed: Speed curve; ③S-Acc: Acceleration curve.

1043

1044

(4) The middle key point of the displacement curve allows dragging up, down, left, and right, and the rightmost key point allows dragging up and down; the speed curve only allows the middle key point to be dragged up and down; the acceleration curve does not allow dragging.

1045

1046

== **Data Configuration** ==

1047

1048

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

1049

[[image:图片106.png]]

1050

1051

① MPos: master axis phase, set the phase of the master axis, the data range is 0 to 9999999;

1052

1053

② SPos: slave axis displacement, set the offset position of the slave axis, data range: -9999999 to 9999999;

1054

1055

③ PU Speed: connection speed, data range: -9999999 to 9999999；

1056

1057

④ Type: curve type; Line: straight line; Spline: 5th degree curve;

1058

1059

⑤ Table data configuration description: the master axis phase and slave axis offset of the first point are 0 by default and cannot be changed; the value of the next point of the master axis phase must be greater than the value of the previous point; the last point of the master axis determines the period of the master axis, so there is no need to set the cycle separately.

1060

1061

== **E-CAM Table Download** ==

1062

1063

On the PLC download page, check the name of the electronic cam table to be downloaded, click "Execute", and wait for the PLC to be written; when there is an electronic cam table, the download page will display the electronic cam table checkbox, otherwise it will not be displayed; after checking, all electronic cam tables are downloaded.

1064

1065

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

[[image:图片107.png]]

= **Caution** =

**Description of the function disable instructions**

1071

1072

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

1073

|=Project management|=Extended function|=Electronic CAM table|=No

1074

|(% rowspan="3" %)Edit Function|Comment edit| |No

1075

|Statement editor| |No

1076

|Switch| |No

1077

|(% rowspan="6" %)Communication related|PLC checksum|Detail check|No

1078

|U disk download| |No

1079

|Generate download ﬁle| |No

1080

|Calculation of total program steps| |No

1081

|Monitor edit (W)| |No

1082

|Module monitoring| |No

1083

1084

= **Shortcut Keys** =

1085

1086

For general shortcut keys, refer to the “Software Help” in PLC Editor2 software. The following table shows the shortcut keys available in the Ladder Diagram Editor.

1087

1088

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

1089

|=**Shortcut key**|=**Summary**

1090

|F5|Normally open contact

1091

|Shift+F5|Normally open contact OR

1092

|F6|Normally closed contact

1093