ADVERTISEMENT

gxiecmanref.pdf

Materiały i spis funkcji w języku polskim dla GXWorks 2 Version 1.54ON

witaj Nie jest to dokładnie to czego byś chciał, ale może coś ci pomoże.


Download file - link to post

MITSUBISHI ELECTRIC

MITSUBISHI ELECTRIC

GX IEC Developer
IEC Programming and
Documentation System

Specifications subject to change without notice.

Art. No.: 43597-F

MITSUBISHI ELECTRIC EUROPE B.V.

V

Reference Manual

GX
IEC
veloper
De

MITSUBISHI ELECTRIC

V

GX
IEC
veloper
De

MELSOFT GX IEC Developer
IEC Programming and
Documentation System
Reference Manual

About this Manual
The texts and illustrations in this manual are provided exclusively as a guide to the IEC
programming and documentation system GX IEC Developer. Separate manuals are available for
MITSUBISHI ELECTRIC’s various series of MELSEC programmable logic controllers.
The GX IEC Developer software is supplied under a legal License Agreement and may only be
used and copied subject to the terms of this License Agreement.
All rights reserved. Without the prior explicit consent in writing from MITSUBISHI ELECTRIC no
part of this manual may be reproduced, stored in a retrieval system of any kind, or transmitted,
in any form, or by any means, electronic, mechanical, photocopying, recording or otherwise, or
translated into another language.
MITSUBISHI ELECTRIC reserves the right to make changes to the technical specifications and
information in this handbook at any time and without prior notice.
The IEC 61131.1 standard cited in this manual is available from the publishers
Beuth Verlag in Berlin (Germany).

6th edition
Copyright 06/2001

MITSUBISHI ELECTRIC EUROPE B.V.
Factory Automation
Gothaer Strasse 8
D - 40880 Ratingen Germany
Phone: (+2102) 486-0
Fax:
(+2102) 486-717

Printed in Germany
Article number: 43597-F (Reference Manual)

Contents I

CONTENTS
CHAPT. 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - 1
1.1

This Manual ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - 1

1.2

The Beginner’s Manual... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - 1

1.3

If you are not yet familiar with Windows... . . . . . . . . . . . . . . . . . . . . . . 1 - 1

1.4

If you are not yet completely familiar with the IEC 61131.3 standard ... . . . . . . . . 1 - 1

1.5

If you are already acquainted with IEC 61131.3 and want to get to work right away ... 1 - 1

1.6

If you need more information on programmable logic controllers ... . . . . . . . . . 1 - 1

1.7

If you need help on programming instructions
when you are developing your programs ... . . . . . . . . . . . . . . . . . . . . . . 1 - 2

1.8

If you get stuck ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - 2

1.9

Typographic Conventions and Visual Cues . . . . . . . . . . . . . . . . . . . . . . . 1 - 2

CHAPT. 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 1
2.1

2.2

Installing GX IEC Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2

2.3

Starting GX IEC Developer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2

2.4

Quitting GX IEC Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2

2.5

Bringing GX IEC Developer into the Foreground . . . . . . . . . . . . . . . . . . . . 2 - 3

2.6

Novell and 32-bit file access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 3

2.7

The MMP400.INI Program Initialisation File . . . . . . . . . . . . . . . . . . . . . . 2 - 4
2.7.1 Format of the MMP400.INI File . . . . . . . . . . . . . . . . . . . . . . . . 2 - 4
2.7.2 Editing MMP400.INI Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 7

2.8

Reference Manual

Hardware requirements . . . . . . . . . . . .
2.1.1 Recommended hardware configuration
2.1.2 Software Requirements . . . . . . . .
2.1.3 Compatibility . . . . . . . . . . . . .
2.1.4 Copyright . . . . . . . . . . . . . . .
2.1.5 Filling out the registration card . . . .

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

2-1
2-1
2-1
2-1
2-2
2-2

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 8
2.8.1 Zoom Header/Body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 8
2.8.2 Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 9
2.8.3 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 10
2.8.4 Graphic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 11
2.8.5 Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 11
2.8.6 CSV-Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 12
2.8.7 Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 12
2.8.8 Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 13
2.8.9 Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 14
2.8.10 Monitor Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 15
2.8.11 Default Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 16

GX IEC Developer

II Contents

2.9

Project specific options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 16
2.9.1 Code generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 17
2.9.2 Reset devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 18

2.10 Connecting the programmable logic controller (PLC) to the computer . . . . . . . . 2 - 19
2.10.1 Connecting FX-/FX2-/FX1S-/FX1N-/FXU-/FX2U-/FX2C series controllers . . . 2 - 20
2.10.2 Connecting FX0/FX0N/FX0S/FX2N series controllers . . . . . . . . . . . . . 2 - 21
2.10.3 Connecting A/QnA series controllers . . . . . . . . . . . . . . . . . . . . 2 - 21
2.11 Connecting Q series controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 24
2.12 Connecting a printer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 26

CHAPT. 3: The User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 1
3.1

The Title Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2

3.2

The Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2
3.2.1 Menu Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2
3.2.2 Selecting menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 3

3.3

The Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 3

3.4

The Project Navigator Window and the Objects it Contains . . . .
3.4.1 Navigator views . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Objects in the Project Navigator window . . . . . . . . .
3.4.3 How objects are displayed in the Project Navigator window
3.4.4 Editing objects . . . . . . . . . . . . . . . . . . . . . .

3.5

The Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 7

3.6

Working with Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 8
3.6.1 Object windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 8
3.6.2 Changing window display size . . . . . . . . . . . . . . . . . . . . . . . . 3 - 10
3.6.3 Dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 11

3.7

Customising the Screen Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 12

3.8

Mouse and keyboard operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 16

3.9

General editing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 16

. . . .
. . . .
. . . .
. . .
. . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

3.10 Working in tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.1 Editing in tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.2 Automatic copying of the contents of the preceding line into the new line
(Autoincrement) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.3 Selecting data types in the declaration table . . . . . . . . . . . . . . . .
3.10.4 Automatic default data types in the declaration table . . . . . . . . . . .

.
.
.
.
.

.
.
.
.
.

3-3
3-4
3-4
3-4
3-6

. 3 - 19
. 3 - 20
. 3 - 22
. 3 - 22
. 3 - 23

3.11 Working in the editors (Body) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 23
3.11.1 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 23
3.12 The text editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 27
3.12.1 Edit functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 28

GX IEC Developer

Reference Manual

Contents III

3.13 The graphical editors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 29
3.13.1
3.13.2
3.13.3
3.13.4
3.13.5
3.13.6
3.13.7
3.13.8

Options. . . . . . . . . . . .
Context menu . . . . . . . .
Right mouse button or F2 . .
Program Elements . . . . . .
AutoConnect . . . . . . . . .
Variables . . . . . . . . . . .
Jump and Return Instructions.
Graphic macros. . . . . . . .

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

3 - 30
3 - 31
3 - 31
3 - 32
3 - 34
3 - 38
3 - 41
3 - 42

3.14 Selecting Programming Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 43
3.15 Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 45
3.15.1 Selecting existing variables and declaring new variables . . . . . . . . . . . 3 - 45
3.15.2 How to automatically write global variables . . . . . . . . . . . . . . . . . 3 - 48
3.15.3 Deleting unused variables . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 49

CHAPT. 4: Projects and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 1
4.1

Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 1
4.1.1 The automatically-generated project files . . . . . . . . . . . . . . . . . . . 4 - 1
4.1.2 Files with standard extensions . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 1

4.2

What are the components of a project? . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2

4.3

The Project Navigator and Objects
4.3.1 Library Pool . . . . . . . .
4.3.2 PLC Parameters . . . . . .
4.3.3 Task Pool . . . . . . . . .
4.3.4 DUT Pool . . . . . . . . .
4.3.5 Global Variables . . . . . .
4.3.6 POU Pool . . . . . . . . .

4.4

The Program Organisation Unit (POU) . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 5

4.5

Preparation Before You Start Programming . . . . . . . . . . . . . . . . . . . . . . 4 - 5

4.6

Library Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 6

4.7

Working with Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 9

4.8

Working with Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 15

4.9

Protecting Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 20

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

4-2
4-2
4-3
4-3
4-3
4-3
4-4

4.10 Printing Out Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 22
4.10.1 Print options for project data . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 23
4.11 Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 27

CHAPT. 5: PLC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 1
5.1

5.2

Latch Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 4
5.2.1 Latch Ranges (MELSEC A) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 4

5.3

Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 5
5.3.1 Device Settings (MELSEC Q/QnA) . . . . . . . . . . . . . . . . . . . . . . . 5 - 5

5.4

Reference Manual

Memory Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 2
5.1.1 Memory Parameters (MELSEC A/FX) . . . . . . . . . . . . . . . . . . . . . . 5 - 2
5.1.2 Memory Parameters (MELSEC Q/QnA). . . . . . . . . . . . . . . . . . . . . 5 - 3

Timer / Counter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 7
5.4.1 Timer-/Counter Configuration (MELSEC A) . . . . . . . . . . . . . . . . . . . 5 - 7

GX IEC Developer

IV Contents

5.5

I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 8
5.5.1
5.5.2
5.5.3
5.5.4

I/O Configuration (MELSEC A) . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 8
I/O Configuration (MELSEC A2C) . . . . . . . . . . . . . . . . . . . . . . . 5 - 9
I/O Configuration (MELSEC QnA). . . . . . . . . . . . . . . . . . . . . . . 5 - 10
I/O Configuration (MELSEC Q) . . . . . . . . . . . . . . . . . . . . . . . . 5 - 11

5.6

Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 12

5.7

MELSECNET/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 13
5.7.1 A series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 13
5.7.2 QnA series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 15
5.7.3 Q series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 17

5.8

PLC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 21
5.8.1 PLC Setup (MELSEC A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 21
5.8.2 PLC Setup (MELSEC Q/QnA) . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 22

5.9

Special Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 25
5.9.1 Special Parameters (MELSEC A). . . . . . . . . . . . . . . . . . . . . . . . 5 - 25

5.10 CC-Link (Q/QnA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 26
5.10.1 CC-Link station information. . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 27
5.10.2 Remote device station initial setting . . . . . . . . . . . . . . . . . . . . . 5 - 27
5.10.3 Interrupt settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 29
5.11 System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 30
5.11.1 System Variables (MELSEC A/FX) . . . . . . . . . . . . . . . . . . . . . . . 5 - 30
5.11.2 System Variables (MELSEC Q/QnA) . . . . . . . . . . . . . . . . . . . . . . 5 - 31
5.12 MELSECNET/MINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 32
5.12.1 MELSECNET/MINI (MELSEC A/QnA) . . . . . . . . . . . . . . . . . . . . . 5 - 32
5.13 CPU Type Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 33

CHAPT. 6: Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 1
6.1

The Structure of GX IEC Developer Programs . . . . . . . . . . . . . . . . . . . . . 6 - 1

6.2

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Event-triggered Tasks . . . . . . . . . . . . . .
6.2.2 Event-triggered tasks with Timer/Output Control
(MC-MCR execution) . . . . . . . . . . . . . . .
6.2.3 Interval-triggered Tasks . . . . . . . . . . . . .
6.2.4 Priority-controlled Tasks . . . . . . . . . . . . .
6.2.5 Special task MELSEC_FIRST . . . . . . . . . . .

6.3

GX IEC Developer

. . . . . . . . . . . . . . . 6-1
. . . . . . . . . . . . . . . 6-1
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

6-2
6-3
6-3
6-3

Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4
6.3.1 Global and Local Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4
6.3.2 Variable declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4
6.3.3 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 5
6.3.4 Identifiers and Absolute Addresses . . . . . . . . . . . . . . . . . . . . . . 6 - 5
6.3.5 Initial Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 8
6.3.6 Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 8
6.3.7 Remark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 8
6.3.8 Autoextern option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 8
6.3.9 Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 9
6.3.10 Address Batch Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 10
6.3.11 Auto Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 10

Reference Manual

Contents V

6.4

Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 11
6.4.1
6.4.2
6.4.3
6.4.4

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

6 - 11
6 - 12
6 - 13
6 - 14

6.5

Programming in Sequential Function Chart Language . . . . .
6.5.1 Sequential Function Chart Language Program Structure
6.5.2 Sequence rules and examples . . . . . . . . . . . . .
6.5.3 Editing elements in the SFC language . . . . . . . . .
6.5.4 Content indication in SFC editor . . . . . . . . . . . .
6.5.5 Zoom functions. . . . . . . . . . . . . . . . . . . . .
6.5.6 Assigning Actions to Steps . . . . . . . . . . . . . . .
6.5.7 Assigning Transition Conditions . . . . . . . . . . . .
6.5.8 Enhanced Display . . . . . . . . . . . . . . . . . . . .
6.5.9 Comments in Sequential Function Chart Language . . .
6.5.10 Manual SFC Control . . . . . . . . . . . . . . . . . .
6.5.11 Sequence errors . . . . . . . . . . . . . . . . . . . .
6.5.12 Start, stop, and initialise SFC for QnA CPUs . . . . . .
6.5.13 ST for Boolean transitions . . . . . . . . . . . . . . .
6.5.14 SV instruction for QnA . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

6 - 16
6 - 16
6 - 17
6 - 20
6 - 20
6 - 20
6 - 21
6 - 22
6 - 23
6 - 24
6 - 25
6 - 26
6 - 27
6 - 30
6 - 38

6.6

Programming Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 43
6.6.1
6.6.2
6.6.3
6.6.4

Networks . . . . . . . . . . . .
Text Editors. . . . . . . . . . .
Graphical Editors . . . . . . . .
Sequential Function Chart (SFC)

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

Using timers in functions . . . . . . . .
Declarations . . . . . . . . . . . . . .
Calling functions in the text editor . . .
Calling functions in the graphical editors

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

6 - 43
6 - 44
6 - 45
6 - 45

6.7

Programming Function Blocks . . . . . . . . . . . . .
6.7.1 Using timers in function blocks . . . . . . . . .
6.7.2 Declaration . . . . . . . . . . . . . . . . . . .
6.7.3 Instantiation . . . . . . . . . . . . . . . . . .
6.7.4 Calling function blocks in the text editor . . . .
6.7.5 Calling function blocks in the graphical editors
6.7.6 Multiple use of a single instance . . . . . . . .
6.7.7 Execution of Function Blocks . . . . . . . . . .
6.7.8 Global Function Blocks . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

6 - 46
6 - 46
6 - 47
6 - 48
6 - 48
6 - 49
6 - 50
6 - 50
6 - 53

6.8

Programming Data Unit Types . . . . . .
6.8.1 Declaration . . . . . . . . . . . .
6.8.2 Use of the DUT as global variable
6.8.3 Use of the DUT as local variable .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

6 - 54
6 - 54
6 - 55
6 - 58

6.9

Programming Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 59
6.9.1 Declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 59
6.9.2 Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 60

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

6.10 Programming Timers and Counters . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 61
6.10.1 TIMER and COUNTER Functions . . . . . . . . . . . . . . . . . . . . . . . 6 - 61
6.10.2 TIMER and COUNTER Function Blocks . . . . . . . . . . . . . . . . . . . . 6 - 63
6.11 The EN input and ENO output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 66
6.11.1 Execution with and without EN and ENO . . . . . . . . . . . . . . . . . . . 6 - 67

Reference Manual

GX IEC Developer

VI Contents

CHAPT. 7: Compiling and Downloading Programs . . . . . . . . . . . . . . . . . 7 - 1
7.1

Error Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 1
7.1.1 Execution order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 2

7.2

Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 2

7.3

Downloading Projects to the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 4
7.3.1 Transfer Setup - Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 4
7.3.2 Transfer Setup - Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 13
7.3.3 Download symbolic information by menu command . . . . . . . . . . . . . 7 - 14
7.3.4 Ignore checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 14
7.3.5 The Q/QnA’s File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 15
7.3.6 Downloading the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 17
7.3.7 Comparing the programs in the PLC CPU and GX IEC Developer . . . . . . . 7 - 17
7.3.8 Online Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 18

7.4

Exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 20
7.4.1 Exporting an GX IEC Developer project into an ASCII file . . . . . . . . . . . 7 - 20
7.4.2 Export to EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 20
7.4.3 CSV variable export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 20

7.5

Importing . . . . . . . . . . . . . . . . . . .
7.5.1 Importing GX IEC Developer ASCII files .
7.5.2 Importing GX Developer ASCII files . . .
7.5.3 Importing MELSEC MEDOC print files. .
7.5.4 Upload PLC to MEDOC . . . . . . . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

7 - 21
7 - 21
7 - 23
7 - 24
7 - 26

CHAPT. 8: Diagnostics Functions and Online Operation . . . . . . . . . . . . . . 8 - 1
8.1

8.2

PLC System Error Check . . .
8.2.1 System errors. . . . .
8.2.2 User-defined errors . .
8.2.3 Hardware Diagnostics
8.2.4 Scan . . . . . . . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

8 - 15
8 - 15
8 - 15
8 - 16
8 - 16

8.3

The Device Editor . . . . . . . . . . .
8.3.1 The worksheet . . . . . . . . .
8.3.2 Buttons. . . . . . . . . . . . .
8.3.3 The pop-up menu . . . . . . .
8.3.4 Editing tables in Microsoft Excel

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

8 - 17
8 - 17
8 - 18
8 - 18
8 - 22

8.4

GX IEC Developer

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 1
8.1.1 PLC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 1
8.1.2 Network Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 5
8.1.3 System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 12

The Monitor Function . . . . . . . . . . . . . . . . . . . . .
8.4.1 Inheritance . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Monitor Mode Options . . . . . . . . . . . . . . . . .
8.4.3 The Online Toolbar . . . . . . . . . . . . . . . . . . .
8.4.4 The Program Monitor . . . . . . . . . . . . . . . . .
8.4.5 The Entry Data Monitor (EDM) and the Header Monitor
8.4.6 Changing variable values . . . . . . . . . . . . . . . .
8.4.7 Display direct address of a variable . . . . . . . . . . .
8.4.8 Tracking variables . . . . . . . . . . . . . . . . . . .
8.4.9 Monitoring Boolean I/Os of function blocks . . . . . .

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

8 - 23
8 - 23
8 - 23
8 - 24
8 - 24
8 - 26
8 - 32
8 - 35
8 - 36
8 - 38

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

Reference Manual

Contents VII

8.5

LLT (Ladder Logic Test). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 38

8.6

Intelligent Function Module Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 40
8.6.1 Starting the utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 41
8.6.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 42

8.7

MXChange Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 43
8.7.1 Software purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 43
8.7.2 General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 43
8.7.3 Functions and menu items . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 44

CHAPT. A: Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A - 1
CHAPT. B: Keyboard Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 1
B.1

GX IEC Developer Menu Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 1

B.2

Project Navigator Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 1

B.3

Object Window Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 2

B.4

Dialog Box Keys

B.5

Table Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 4

B.6

Device Editor Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 5

B.7

Instruction List Editor Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 7

B.8

Graphical Editor Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 8

B.9

Sequential Function Chart Editor Keys . . . . . . . . . . . . . . . . . . . . . . . . B - 10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

B.10 Keys for Checking and Downloading Programs . . . . . . . . . . . . . . . . . . . B - 11
B.11 Online Help System Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B - 11

CHAPT. C: Tools

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

C.1

General Tool Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C - 1

C.2

Instruction List Editor Tool Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . C - 2

C.3

Ladder Diagram and Function Block Diagram Editor Tool Icons . . . . . . . . . . . . C - 2

C.4

Sequential Function Chart Editor Tool Icons

C.5

Project Navigator Window Tool Icons . . . . . . . . . . . . . . . . . . . . . . . . . C - 4

C.6

Online (Monitor Mode) Tool Icons . . . . . . . . . . . . . . . . . . . . . . . . . . C - 4

. . . . . . . . . . . . . . . . . . . . . C-3

CHAPT. D: Temporary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D - 1
D.1
D.2

Reference Manual

Temporary Files Created when Projects are Compiled . . . . . . . . . . . . . . . . . D - 1
Temporary files Created During Downloads

. . . . . . . . . . . . . . . . . . . . . D-1

GX IEC Developer

VIII Contents

CHAPT. E: Programming Instructions . . . . . . . . . . . . . . . . . . . . . . . . E - 1
E.1

IEC Programming Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 4

E.2

IEC – MELSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 8
E.2.1
E.2.2
E.2.3
E.2.4
E.2.5
E.2.6
E.2.7
E.2.8
E.2.9
E.2.10
E.2.11
E.2.12
E.2.13
E.2.14
E.2.15
E.2.16
E.2.17

Addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 8
Subtraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 9
Multiplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 10
Division . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 11
Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 12
BCD – BIN conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 13
Logic Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 14
Start of an Operation and Output of a Result . . . . . . . . . . . . . . . . E - 15
Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 16
Shift. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 17
Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 18
Set and Reset Operations . . . . . . . . . . . . . . . . . . . . . . . . . . E - 19
Rising/Falling Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 20
Negation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - 20
Jumps/Program Branching . . . . . . . . . . . . . . . . . . . . . . . . . E - 21
Calling Subprograms and Function Blocks . . . . . . . . . . . . . . . . . E - 21
Exclusive Q Series Instructions . . . . . . . . . . . . . . . . . . . . . . . . E - 22

CHAPT. F: Menu structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F - 1
CHAPT. G: Compliance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G - 1

GX IEC Developer

Reference Manual

Introduction 1 - 1

1

Introduction
1.1

This Manual ...
... isn’t designed to be read from cover to cover. It is organised so that it can be used as a
reference work in which you can find detailed explanations of all the menus and menu
commands in GX IEC Developer when you need them. However, the Reference Manual is not
based directly on the menu structure of GX IEC Developer, but rather on the central elements of
IEC Standard 61131.3 such as Projects, Objects, Variables, Program Organisation Units and
Programming Languages. The menus and all menu commands and options are listed in the
appendix of this manual.

1.2

The Beginner’s Manual...
... is the ideal aid for getting acquainted with the basic terms and concepts of the new IEC
61131.3 standard. This manual teaches you how to use GX IEC Developer in easy steps, with a
sample program that provides a practical illustration of the most important operations.

1.3

If you are not yet familiar with Windows...
... please at least read the Windows Fundamentals section in the Windows User’s Guide or work
through the exercises of the online Windows tutorial (accessible in the Program Manager).
This will give you the information and skills you need for using the elements of Windows that
are the same in all application programs.

1.4

If you are not yet completely familiar with the IEC 61131.3 standard ...
... please read the chapter on the IEC 61131.3 standard in the Beginner’s Manual. This chapter
explains the basic principles of this industry standard, together with the most important new
terms you need to know. A glossary of all the terms used is provided at the end of this
Reference Manual.

1.5

If you are already acquainted with IEC 61131.3 and want to get to
work right away ...
... you will find the basic instructions you need to be able to produce immediate results in the
‘Getting Started’ chapter in the Beginner’s Manual. This chapter tells you how to perform all the
basic GX IEC Developer operations, from creating new projects to downloading your finished
programs to the PLC (controller).

1.6

If you need more information on programmable logic controllers ...
... please refer to the documentation provided with the hardware components of your system.

Reference Manual

GX IEC Developer

1 - 2 Introduction

1.7

If you need help on programming instructions when you are
developing your programs ...
... use the GX IEC Developer online help system. This provides direct access to brief explanations
of all programming instructions, together with their syntax, parameters and operands. A list of
all IEC and MELSEC programming instructions is also provided in the appendix of this manual.
More detailed descriptions and sample programs can be found in the programming manuals of
the individual PLCs.

1.8

If you get stuck ...
... in what looks like an insoluble problem or if you have questions about GX IEC Developer or
the connected PLC configuration, please first refer to the manuals. Use the detailed index
provided in this Reference Manual. Answers to many of your questions can also be found in GX
IEC Developer‘s context-sensitive online help system, which can always be accessed by pressing
‘. Please also make use of the Search command in the Help menu.
If you fail to find an answer to your particular question in any of these places you can also
obtain help from your local MITSUBISHI ELECTRIC representative. Alternatively, you can call us
directly at the MITSUBISHI ELECTRIC European headquarters in Ratingen, Germany. The
addresses and phone numbers are listed on the rear of all PLC manuals.

1.9

Typographic Conventions and Visual Cues
References to specific keys and key combinations are always identified with the key symbols, e.g.
«, ¨ or §.
Menu names, submenus, menu commands and the options in dialog boxes are identified by the
use of bold type, e.g. the menu command New in the Project menu, or the options CPU-Port
and Computer Link (AJ71C24) in the Transfer Setup dialog box.
These symbols are used to identify special instructions for mouse and keyboard users.

Examples: This symbol identifies examples.

Note: This symbol draws your attention to particularly important hints and information.

WARNING: Always pay particular attention to the warnings identified with this symbol, as they
refer to serious dangers such as the possibility that you may lose data or damage the hardware
system if you do not follow the instructions.

GX IEC Developer

Reference Manual

Installation 2 - 1

2

Installation
2.1

Hardware requirements

2.1.1

Recommended hardware configuration
n
n

n
n
n

2.1.2

Pentium II 350 processor or above
32 MB RAM (Microsoft Windows 95/98/Me),
64 MB RAM (Microsoft Windows NT Workstation 4.0/2000 Professional)
Hard disk with at least 100 MB free
CD-ROM drive
17 " (43 cm) VGA monitor (1024 x 768 pixels)

Software Requirements
GX IEC Developer 4.00 is a 32-bit product. The following operating systems are supported:
n
n
n

2.1.3

Microsoft Windows version 95/98/Me (with all detailed versions e. g. ServicePack 1)
Microsoft Windows NT Workstation 4.0 (with all detailed versions e.g. ServicePack 6)
Microsoft Windows 2000 Professional (with all detailed versions e.g. ServicePack 1)

Compatibility
GX IEC Developer 4.00 can open project databases (*.pro file) of MM+ 2.1, 2.30a, 2.31, 2.31a,
2.32, 2.40, 2.40a, 2.50 and 3.00, but these versions cannot open GX IEC Developer 4.00 project
databases.
GX IEC Developer 4.00 can import projects, which have been exported (*.asc file) by MM+ 2.1,
2.30a, 2.31, 2.31a, 2.32, 2.40, 2.40a, 2.41, 2.50 and 3.00, but these versions can not import
*.asc exports of GX IEC Developer 4.00.
Under Microsoft Windows Me previous 16-bit projects can not be opened or converted directly
in GX IEC Developer 4.00. Such projects can be opened and exported under the other supported
operating systems and then imported into Microsoft Windows Me.
It is possible, that the generated code of GX IEC Developer 4.00 is different from the generated
code of a former version of MM+. This could result in the following facts:
n
n

An online change can fail, if the project was not downloaded with GX IEC Developer 4.00.
The verify functionality can show differences

The reason for the differences are internal changes in the code generator which result from the
implementation of new features in GX IEC Developer 4.00.
Compatibility with other programming software for MELSEC PLCs:
n

n

n

n

n

GX IEC Developer 4.00 can import MELSEC MEDOC /DOS print files (*.tmp) of the versions
1.64b/c, 2.20 and 2.30, if they are generated according to the needs.
GX IEC Developer 4.00 generally can not upload parameters and programs from Q and
QnA/S CPUs, which are generated by GX Developer or GPPQ.
GX IEC Developer 4.00 can upload only programs from Q and QnA/S CPUs which are
generated according to the limitations of GX IEC Developer 4.00 compared to the Q and
QnA/S features.
GX IEC Developer 4.00 can upload programs from A CPUs which are generated with
GX Developer or GPPA.
GX IEC Developer 4.00 can not open project databases from GX Developer, GPPQ or GPPA.

There is currently no possibility to exchange projects between GX IEC Developer 4.00 and
GX Developer, GPPQ or GPPA besides the ASCII import described in section 7.5.

Reference Manual

GX IEC Developer

2 - 2 Installation

2.1.4

Copyright
IMPORTANT NOTICE: This software is protected by copyright. By opening the
distribution CD-ROM package you automatically accept the terms and conditions of the
License Agreement. You are only permitted to make one single copy of the original
distribution disk for your own backup and archiving purposes.

2.1.5

Filling out the registration card
You are only entitled to full technical support from MITSUBISHI ELECTRIC if you fill out and
return the enclosed registration card – don’t forget to include your serial number! You will then
also receive information on updates and new versions of GX IEC Developer.

2.2

Installing GX IEC Developer
During this procedure the installation program will create a directory on your hard disk, into
which all the GX IEC Developer files will be copied.

Installing GX IEC Developer on your hard disk
ቢ Make sure that the correct Microsoft Windows version is properly installed on your computer.
For information on using Windows please refer to the Windows User’s Guide.
ባ Start MS Windows.
ቤ Insert the Installation CD-ROM in the CD-ROM drive.
ቦ Open the Windows Explorer.
ቧ Select and open the CD-ROM drive in which you have inserted the CD-ROM.
ቨ Double-click on the file SETUP.EXE.
This starts the GX IEC Developer installation program.
ቩ Follow the instructions that appear on the screen.
ቪ When the installation procedure is finished the program will create a new program group
containing the GX IEC Developer program icon.
For further details on the necessary Windows procedures please refer to your Windows
documentation.

2.3

Starting GX IEC Developer
ቢ In the Start menu click on the GX IEC Developer program icon. The icon is located in:
Start & gt; Programs & gt; MELSOFT Application & gt; GX IEC Developer. This starts GX IEC Developer
and displays the start-up screen.
ባ Confirm with the « key.
If DLL-files with different version numbers are installed, an error message appears. In this case
GX IEC Developer must be installed again.

2.4

Quitting GX IEC Developer
You can quit GX IEC Developer directly at any point in the program by pressing the key
combination ¦”.
Or:
Double-click on the Quit command in the Project menu.

GX IEC Developer

Reference Manual

Installation 2 - 3

2.5

Bringing GX IEC Developer into the Foreground
When GX IEC Developer is active on the screen at the same time as one or more other
applications you can bring GX IEC Developer into the foreground by double-clicking on its icon in
the Program Manager.

2.6

Novell and 32-bit file access
Executing GX IEC Developer on a computer connected to a Novell network can lead to problems
if 32-bit file access is enabled.

Deactivating 32-bit file access:
ቢ Open the Control Panel in the Windows Main program group.
ባ Activate the 386 Enhanced option.
ቤ Select Virtual Memory.
ብ Select Change & gt; & gt; .
ቦ Deactivate Use 32-bit file access.
ቧ Select OK.
ቨ Confirm with Yes.
ቩ Select Reboot computer (close all open applications save all open files first!).

Reference Manual

GX IEC Developer

2 - 4 Installation

2.7

The MMP400.INI Program Initialisation File
The MMP400.INI initialisation file contains important parameters required by the Windows
application GX IEC Developer. The Install program creates this file automatically and stores it in
your Windows directory. A copy of the MMP400.INI file will remain in the actual GX IEC
Developer directory (© page 2-7).

2.7.1

Format of the MMP400.INI File
MMP400.INI is arranged in several sections that all have the same basic format. The following
list shows the standard and some sample settings:
Contents of the MMP400.INI File
(Standard and sample entries)

Explanation

[PROJECTS]
Project0=C:\MMP_PROJ\SILO1
Project1=C:\MMP_PROJ\TEST3
Project2=C:\MMP_PROJ\EXAMPLE
Project3=C:\MMP_PROJ\SILO2

PROJECT
List of the last four projects opened in GX IEC
Developer
These projects are also displayed at the bottom of the
Project menu.
DO NOT EDIT!

[OPTIONS]

OPTIONS
in the EXTRAS menu

StepZoom=1
FBZoom=1
MacroGraphics=5
AutomaticIOpin=TRUE
AutoExtern=TRUE
PinOverWrite=TRUE
IncremNewDecl=TRUE
CommentCopy=TRUE
ChkDeclareExternal=TRUE
ChkErrors=25
ChkWarnings=100
LRUProjects=4
ArrayElementsToShow=10
CanEditPou=FALSE
MinDiskSpace=20
DefaultStringLength=20
ErrorLogFile=C:\MMP\error.log
InitNetworkHeight=3
CreateTmpVarForPLS=TRUE
CreateTmpVarForPLF=TRUE
CreateTmpVarForALT=TRUE
OnlinePollrate=100
MonitorStringLen=16
AutomaticIOPinENO=TRUE
LRUVarsel=3

Detailed information see page 2-16

[LADDER]
HLineLength=4

VLineLength=3

GX IEC Developer

LADDER DIAGRAM
Horizontal length in Ladder diagram
Length in grid elements
Default setting: 4
Vertical height in Ladder diagram
Height in grid elements
Default setting: 3

Reference Manual

Installation 2 - 5

Contents of the MMP400.INI File
(Standard and sample entries)

Explanation

[RC_GROUP]
1=1,53,Clock, ,
2=2,180,Path, ,
3=3,73,Security Level, ,
4=4,150,Editor Info, ,
5=5,40,Online, ,
6=6,28,System Resources, ,
7=7,88,Free Memory, ,
8=8,250,Messages, ,
9=20,55,CpuType, ,
10=21,110,ConnStatus,
Not Connected,
11=22,70,ErrorStatus,
Not Connected,

STATUS BAR
Status bar configuration settings
DO NOT EDIT!

[WORK_GROUP]
LEFT=20,2,
RIGHT=1,3,

STATUS BAR
Field size of the status bar entries
DO NOT EDIT!

[DEFAULT_GROUP]
LEFT=2,3,
RIGHT=1,

STATUS BAR
Field size of the status bar entries
DO NOT EDIT!

[LIBRARIES]
ManufacturerHelpPath=
C:\MMP\HELP

USER LIBRARIES
Directory for the library help files

ManufacturerLibPath=
C:\MMP\USER_LIB

Directory for the library files

Manufacturer0=Standard_Lib,
SLIB.lib,FUNCTION.HLP

Specification of the libraries
Max. 50 libraries are allowed.
Input order:
ManufacturerX=library name, library file, help file
(help file not necessary)
DO NOT EDIT!

Manufacturer1=Manufacturer_Lib,
MLIB.lib,FUNCTION.LIB
[Ccodegen]
TabDump=TRUE

[PRINT]
PrintFrame=1

PRINTOUT
=1: Printout options are enabled
=0: Printout options are disabled

OemBitmap=C:\MMP\PRNLOGO1.BMP

Directory and file of bitmap
Bitmap is shown in the upper left corner in the page
header

PrBitmap=C:\MMP\PRNLOGO2.BMP

Directory and file of bitmap
Bitmap is shown in the upper right corner in the page
header

Text1=Company XXX
Text2=Department XXX
Text3=Application XXX

Text in footer
3 text lines are shown in the page footer

PrintRaster=10

Size of printout
Default setting:10
depends on printer

ScDoc=1

ScDoc
ScDoc=1: Activates the interface to the documentation
software SCDoc.

[CrossReference]
GenerateSCT=TRUE
GenerateSCX=TRUE

Reference Manual

CODE-GENERATOR
When TabDump=TRUE the following files are generated in
the project directory when GX IEC Developer is started
with the /debug option:
- PRECGEN.TAB
- POSTCMPR.TAB
- POSTCGEN.TAB

CROSS REFERENCE
Automatic link of the SCT files to the SCX file when
creating the cross reference data base
=TRUE: Function enabled
=FALSE: Function not enabled

GX IEC Developer

2 - 6 Installation

Contents of the MMP400.INI File
(Standard and sample entries)

Explanation

[PARAM]
COMPORT=0

PARAMETER
Selection of the COM port of Personal Computer
COMPORT=0 Selection of COM1
COMPORT=1 Selection of COM2
The selection of the COM port will not be saved together
with the project. The COM port can be selected in the
MMP400.INI.

[PATH]
CNF=c:\SC\TYP_CNF
TYP=c:\SC\TYP_CNF
EXE=c:\SC\MAK
PPR=c:\SC\PPR

DIRECTORIES
CNF Configuration files for all PLC types
(special format)
TYP Configuration files for all PLC types
(standard format)
EXE GX IEC Developer program files
PPR Project templates for all PLC types
DO NOT EDIT!

[WIZARD]
MELSEC=FALSE

WIZARD
Automatic POU and Task creation
MELSEC=TRUE
When you create a new project the Wizard is displayed on
the screen with a prompt asking if you wish to create a
POU and a task automatically.
MELSEC=FALSE
This setting disables the Wizard.

[REG]

GX IEC Developer REGISTRATION

NAME: xxxxx
COMPANY: xxxxx
DISTRIBUTOR: xxxxx
SERIAL: xxxxx

Name/Company: information entered when you install GX
IEC Developer
Distributor/Serial: Distributor name and encoded serial
number
DO NOT EDIT!

[DEVICE_SETTING]
USE_COLORS=1

DEVICE EDITOR
Colors
Context menu - Options - Use Colors
=1: Use of different colors in display mode enabled
=0: Use of different colors in display mode disabled

SAFETY_INQUIRY=1

Safety inquiry
Context menu - Options - Additional Safety Inquiry
=1: Additional safety inquiry prompt is displayed
=0: Additional safety inquiry prompt is not displayed

[EDM]
FIELD0=Name
FIELD1=Type
FIELD2=Address (IEC)
FIELD3=Value (dec)
FIELD4=Value (bin)

ENTRY DATA MONITOR
Configuration of Entry Data Monitor table

[SFC]
GenerateSfcStartupCode=TRUE

SEQUENCES
Automatic generation of startup code
LD M9039
OUT M9101
The special relay M9101 starts the execution of the SFC
processing.
1) The section [SFC] or the entry GenerateSfcStartupCode
does not exist or any of them is spelled incorrectly:
➜ The startup code will be generated automatically.
2) The section [SFC]and the entry GenerateSfcStartupCode
exist and the value is set to eiher TRUE, YES or 1:
➜ The statup code will be generated automatically.
3) The section [SFC]and the entry GenerateSfcStartupCode
exist and the value is set to any other value:
➜ The startup code will not be generated.
Usually the entry should be set to TRUE, to generate a
proper SFC processing.

GX IEC Developer

Reference Manual

Installation 2 - 7

2.7.2

Editing MMP400.INI Entries
WARNING: Most MMP400.INI parameters should not be edited by the user! Please observe the
DO NOT EDIT! warnings in the table above.

How to make changes in the user-editable sections
ቢ Create a backup copy of the file MMP400.INI in another directory or on a floppy disk.
If the changes you make don’t work or result in unexpected problems when you run GX IEC
Developer you can then restore the original file in the Windows directory from the backup copy.
Important: When you install GX IEC Developer the MMP400.INI file is copied into your
Windows directory. Although there is also a copy of MMP400.INI in the GX IEC Developer
directory, the program only uses the copy of MMP400.INI in the Windows directory. Before
making any editing changes it is thus always advisable to make a backup of the version of
MMP400.INI stored in the Windows directory, as it is always possible that the file has already
been changed in some way and is no longer identical with the copy stored in the GX IEC
Developer directory.
ባ Load MMP400.INI into a standard text editor such as the Windows Notepad utility.
Do not use an editor or word processor that inserts formatting codes in the text file, as the
system would then no longer be able to read the file.
ቤ Make the necessary editing changes.
ብ Save the edited file.
ቦ Close the GX IEC Developer program and restart it.
Changes made to the MMP400.INI file do not take effect until you restart the GX IEC
Developer program.

Reference Manual

GX IEC Developer

2 - 8 Installation

2.8

Options
The options are configured in the Extras - Options menu.

2.8.1

Zoom Header/Body

Navigator Zoom

Expand Double-clicking on entries in the POU Pool displays/hides lower levels in the
hierarchy (default).


Open Header Double-clicking on entries in the POU Pool opens the corresponding header.



Open Body Double-clicking on entries in the POU Pool opens the corresponding body.

FBD/LD Zoom

Open Header Double-clicking on a function block in a graphical editor opens the
corresponding header (default).


Open Body Double-clicking on a function block in a graphical editor opens the
corresponding body.

Step Zoom Into

Step Action Association Double-clicking on a step opens the Action Association dialog
box (association of an action to a step).




GX IEC Developer

First Action If Any If actions are already associated with the step double-clicking on the step
displays the PLC program of the first action in the list.
Comment Double-clicking on a step displays the Comment dialog box
(for entering comment texts).

Reference Manual

Installation 2 - 9

2.8.2

Editing

Declaration Editor

Autoextern The declaration table of the global variables has a column called Auto Extern.
All global variables identified as Auto Extern are automatically copied to the headers of all
existing and newly-created POUs.


Copy Comment and Type Fields See Incremental New Declarations.



Auto Update Updates global and local variables automatically after changing a variable
declaration. The following changes of a variable declaration are updated: Class, Identifier,
Address, Type, Initial. All changes made in the GVL will also be executed in the POUs. When
you change a POU header, its body will also be changed automatically. The variables are
updated after the declaration editor changes have been saved.



Incremental New Declarations When this option is enabled the contents of the previous
lines are copied automatically when new lines are inserted in the declaration tables.
The designators and addresses are automatically incremented by 1. If you also want the
system to copy the contents of the type and comment fields you must also enable the Copy
Comment and Type Fields check box.

FBD/LD

Declare New Identifiers When you overwrite a dummy variable in a graphical editor with a
variable identifier name that has not yet been declared the Variable Selection (Mode
NewVar) dialog box will be displayed automatically so that you can enter the declaration for
the new variable.


Pin Overwrite When you create a connection to an empty variable connection in a graphical
editor the empty variable will be overwritten.



Automatic Input/Output Variables The system will automatically create the input and
output variables when you insert a function block in a graphical editor.



Automatic ENO Variables The system will automatically create the ENO output variable
when you insert a function block in a graphical editor. If the ENO output variable is not
needed this option has to be disabled.

Online Toolbar
Enables the display of the additional toolbar for online operations when the program is in online
mode (© page 8-24 and Appendix C).
Settings for Variable Selection
When the variable selection dialog box is activated the focus in the libraries list will be on the
library specified here.

Reference Manual

GX IEC Developer

2 - 10 Installation

2.8.3

General

Error Log File
Path and filename for the error log file.
Stop Check By

Errors Stop the check operation when the number of errors found exceeds the maximum
limit specified here.
Range: 0 - 2,000


Warnings Stop the check operation when the number of warnings exceeds the maximum
limit specified here.
Range: 0 - 2,000

Default String Length (characters)
You can set the default length of the STRING data type to any value up to a maximum of 50
characters.
Minimum Disk Space (Mbytes)
GX IEC Developer displays a warning message when the amount of free space available on the
current drive falls below the value specified here.
Last Recent Used Files (number)
The last projects opened are always displayed at the bottom of the Project menu. You can set
the number of projects to be displayed to a maximum of 9.
Array Elements To Show
The Entry Data Monitor can display the individual elements of an array, but this can be
impossible if the array is too large. This option enables you to set the number of array elements
to display to a maximum of 50 (© page 8-31 ).
You can also change this value in the prompt dialog that is displayed when you open an array in
the Entry Data Monitor.

GX IEC Developer

Reference Manual

Installation 2 - 11

2.8.4

Graphic





Horizontal Grid Length of Line Segment Horizontal length of line segments in the ladder
diagram editor, in grid points.
Range: 0 - 100 grid points
Default: 4



Vertical Grid Height of Line Segment Vertical length of line segments in the ladder
diagram editor, in grid points.
Range: 0 - 100 grid points
Default: 3



2.8.5

Initial Network Height The initial height of a network.
Range: 3 - 100 grid points
Default: 3

Number of Graphic Macros Number of additional graphic macros available.
Graphic macros 1 through 5 are always available.
Range: 5 - 25

Cross Reference

Cross Reference Options
Used to define the options for generation of the cross reference database.





Automatically link the *.SCT files to the *.SCX file after ‘Rebuild All’
Activates automatic linking of the SCT files to the SCX file after compiling a project.



Reference Manual

Generate *.SCT files while checking a project Activates generation of the SCT files during
project checks.

Automatically link the *.SCT files to the *.SCX file after ‘Rebuild’
Activates automatic linking of the SCT files to the SCX file after building a project.

GX IEC Developer

2 - 12 Installation

2.8.6

CSV-Export

All variables defined in the GVL and the POU header of a project can be exported as ASCII file in
Comma Separated Value format (*.csv).



Separator Select either the “Comma” or the “Semicolon” as separator character between values.



Export file Select whether to either “Overwrite existing export file” or to “Backup existing
file in .CSX file”.



2.8.7

Export File Enter the path and name of the file to be exported

Generate export file after every successful build process Activate this option, if desired.

Import/Export

Import/Export options
Specifies how the user libraries are handled when a project is imported or exported.




Import all user libraries of the import file without any user confirmation Imports all
user libraries without requesting any confirmation.



GX IEC Developer

Automatic import/export of user libraries
Enables the automatic import or export of the user libraries.

Export all user libraries of the current project without any user confirmation
Exports all user libraries without requesting any confirmation.

Reference Manual

Installation 2 - 13

2.8.8

Compiler

Create temporary variables for instruction PLS_M / PLF_M / ALT_M
System variables are required for internal processing when the output variables of the
instructions PLS_M, PLF_M and ALT_M are used to activate additional instructions. If you use
many instructions of this kind the maximum limit for number of system variables (system labels)
that you can use can be reached very quickly.
If this happens you should disable the option Create temporary variables for instruction
PLS_M / PLF_M / ALT_M. Your PLC program must then be modified accordingly.
Default: Enabled
Output writes directly to the device (no
system variable required)

Output activates the MOV instruction
(uses 1 system variable)

Disable Compiler Warnings
The display of compiler warnings in the error box during a Check, Build, or Rebuild all
execution can be disabled. Default setting: Warnings enabled.

To disable a compiler warning, take the following steps:
ቢ Enter the compiler warning code in the edit field.
ባ Press the Add... button.
The compiler warning is disabled and listed in the list box.

To enable a compiler warning, take the following steps:
ቢ Select a compiler warning code from the list box.
ባ Press the Delete... button.
The compiler warning is enabled and removed from the list box.

Reference Manual

GX IEC Developer

2 - 14 Installation

2.8.9

Monitor Mode





Poll rate Interval at which the monitor polls the CPU, expressed in ms.



GX IEC Developer

Displayed String Length Displaying long strings significantly reduces performance in
monitoring mode. It is thus advisable to limit the number of characters to be displayed.
Enable Autoscroll (SFC) If the SFC body is observed in the monitor mode, you have to scroll
through the window. This can be done manually or by means of the autoscroll function.
The autoscroll function tracks the active steps of the SFC and scrolls the window
automatically. The horizontal and vertical position of the active step in the window can be
defined.If the SFC includes more than one active step, the upper left active step is used for
autoscrolling.The horizontal position of the window display can as well be restricted by the
selection rectangle. The horizontal position of the selection rectangle always remains visible
even if a step outside the visible area would become active.

Reference Manual

Installation 2 - 15

2.8.10 Monitor Indication

If the monitor mode is active, the corresponding icon in the toolbar changes its colour from
black to red.
Indicate Monitoring by Titlebar of

GX IEC Developer main window If the monitor mode is active and objects are monitored
in one window at least (e.g. body of a POU or Entry Data Monitor), the title bar of GX IEC
Developer is blinking according to the defined blink rate.


Window to be monitored If the monitoring is started for a window (e.g. body of a POU or
Entry Data Monitor), the title bar of this window is blinking according to the defined blink rate.



Blink Rate The blink rate can be adjusted depending on the poll rate.

Word type variables

Decimal Displays monitor values of word type variables in decimal format.


Hexadecimal Displays monitor values of word type variables in hexadecimal format
(default setting).

This feature is also available in editors of the type IL, LD, FBD, and MIL via a context menu when
the monitor mode is active.

Reference Manual

GX IEC Developer

2 - 16 Installation

2.8.11 Default Transition

When opening the transition’s rectangle (e.g. by double click or by Zoom Into)
Transition Condition is selected.
The TC editor will appear.
Standard Body is selected.
The standard behaviour is not changed.

2.9

Project specific options
The options are configured in the Extras - Options menu.
The MM+ versions 2.40 and higher provide the possibility to define project specific settings.
The project specific settings will be saved together with the project in the database.
Availability
Due to the fact that the project specific options belong to a specific project and are no general
settings, these new options in the Options dialog are available only if a project has been loaded.
To indicate that these settings refer only to the project currently loaded, the title of the Options
dialog is Project Specific Options.
Database
Opening old projects
When opening old projects, i.e. projects created by lower MM+ versions, missing settings will be
filled up with the settings included in the .INI file. If the entries in the .INI file are not available,
hard coded settings will be inserted instead.
Creating new projects
When creating new projects the individual default values included in the .INI file are inserted. If
the entries do not exist in the .INI file, the hard coded default settings are inserted instead.
This behaviour is exactly the same as to open the Options dialog and pressing the button Load
Defaults of both sections.
Compatibility
Due to the necessary changes in the database a project created by means of MM+ 2.40 or
higher cannot be opened by lower MM+ versions.
Files with the extensions *.PRO and *.PCD generated by MELSEC MEDOC plus 2.50 or lower can
not be opened by the current version of GX IEC Developer. In this case we recommend the
import/export functions or an external conversion tool (available on request).

GX IEC Developer

Reference Manual

Installation 2 - 17

2.9.1

Code generation

The section Code Generation section is available only for Q/QnA projects.
Due to the file structure of the MELSEC QnA CPUs it is necessary to define an additional
program range (in units of steps) for online changes.
After the Additional Program Size has been changed, the value will be checked when leaving the
dialog. This check can be done via the OK button or changing the section by clicking on another
entry in the List Options. In case of an error an error box will appear.
Generate code for Manual SFC Control
If this option is enabled, special sequence code is generated which includes one SET and
one RST instruction for the steps S0 – Sn where n is the maximum step number of all SFC POUs.
The code also includes a BRSET instruction at the beginning which sets the current block
according to a system word register.
This code helps to influence the step flags of every SFC block by setting the values for the D and
M devices. By the SFC editor only on SFC block can be handled at one time. Using LDP allows to
set a step in a running SFC without risking to activate the same step again several times.
The following checks are performed during the manual SFC control operation:
n
n

The consistency is checked between PLC and project.
The PLC must operate in RUN mode.

Generated sample code:
LD & gt;

K-1 D2048

BRSET D2048
LDP

M4100

SET

S0

LDP

M4101

SET

S1
:

LDP

M4120

RST

S0

LDP

M4121

RST

S1
:

Reference Manual

GX IEC Developer

2 - 18 Installation

Reset Defaults
When pressing the button Reset Defaults the settings of this section are reset to their default
values, i.e. the hard coded settings are loaded. This is especially helpful to restore the original
settings.
Load Defaults
When pressing the button Load Defaults the default settings saved in the .INI file are loaded. If
the .INI file does not include any entries, the hard coded settings are loaded.
Save As Defaults
When pressing the button Save As Defaults the current settings are saved as default settings to
the .INI file. If the .INI file does not include any saved default settings yet, they will be created
by this operation.
Note: The maximum Additional Program Size depends on the PLC configuration.

2.9.2

Reset devices

If the option Enable Reset Devices is not selected, all other options are disabled to indicate
that the reset devices are not active.
Reset Defaults
When pressing the button Reset Defaults the settings of this section are reset to their default
values, i.e. the hard coded settings are loaded. This is especially helpful to restore the original
settings.
Load Defaults
When pressing the button Load Defaults the default settings saved in the .INI file are loaded.
If the .INI file does not include any entries, the hard coded settings are loaded.
Save As Defaults
When pressing the button Save As Defaults the current settings are saved as default settings to
the .INI file. If the .INI file does not include any saved default settings yet, they will be created
by this operation.

GX IEC Developer

Reference Manual

Installation 2 - 19

2.10

Connecting the programmable logic controller (PLC) to the computer
In the Project Navigator click on PLC_Parameter and in the dialog box on the button CPU Type.
You get a list containing all CPU types which are supported by GX IEC Developer. A detailled
summary of all CPU types supported by GX IEC Developer is included in section 5.13.
This manual does not include instructions for installing your controller hardware. Each controller
system is supplied with documentation including comprehensive installation instructions.
There are a number of different options for connecting the PLC to your personal computer:
n
n
n
n

Via the CPU interface
Via the computer link modules
Via an Ethernet module
Via the USB interface

The MAC transparent mode enables data transmission by modem between the personal
computer and the PLC. More information see page 7-9.
The options for selecting the connection type and setting the corresponding parameters can be
found in the Online menu under Transfer Setup - Ports
(© Chapter 7).

Reference Manual

GX IEC Developer

2 - 20 Installation

2.10.1 Connecting FX-/FX2-/FX1S-/FX1N-/FXU-/FX2U-/FX2C series controllers
The controllers of the FX series can only be connected to the computer via the CPU interface.
a) Connection via the CPU interface with the SC-09 interface converter
Connect the 9-pin D-shell connector to the computer. If your computer port has a 25-pin
connector you will also need a 9/25-pin adapter. Connect the 25-pin D-shell connector to the FX
controller.
GX IEC
Developer
SC-09

SC-09

MELSEC FX/
FX2/FX1S/FX1N/
FXU/FX2U/FX2C

b) Connection via the CPU interface with the FX-232AW serial interface
You will need two additional cables for connecting the FX-232AW module:
n
n

FX-422CAB for connecting the FX controller to the FX-232AW
F2-232CAB or FX-232CAB for connecting the FX-232AW to the personal computer

If your computer port has a 9-pin connector you will also need a 25/9-pin adapter as both of
these cables (F2-232CAB, FX-232CAB) are fitted with 25-pin D-shell connectors at the PC end.
GX IEC
Developer
F2-232CAB
FX-232CAB

MELSEC FX/FX2/FX1S/
FX1N/FXU/FX2U/FX2C

FX-422CAB

GX IEC Developer

Reference Manual

Installation 2 - 21

2.10.2 Connecting FX0/FX0N/FX0S/FX2N series controllers
The controllers of the FX0/FX0N/FX0S/FX2N series can only be connected to the computer via
the CPU interface.
a) Connection via the CPU interface with the SC09 interface converter
Connect the 9-pin D-shell connector to the computer. If your computer port has a 25-pin
connector you will also need a 9/25-pin adapter. Connect the 8-pin min-DIN connector to the
FX0/FX0N/FX0S/FX2N controller. This connector is delivered together with the SC-09.
GX IEC
Developer
SC-09

MELSEC FX0/FX0N
FX0S/FX2N

b) Connection via the CPU interface with the FX-232AW serial interface
You need three additional cables for connecting the systems with the FX-232AW module:
n

n

The FX-422CAB and the FX-20PCADP cables for connecting the FX0/FX0N/FX0S/FX2N
controller to the FX-232AW
The F2-232CAB or FX-232CAB cable for connecting the FX-232AW to the personal computer

If your computer port has a 9-pin connector you will also need a 25/9-pin adapter, as both these
cables (F2-232CAB, FX-232CAB) have 25-pin D-shell connectors at the computer end.
GX IEC
Developer
F2-232CAB
FX-232CAB

FX-422CAB FX-20PCADP

MELSEC FX0/FX0N
FX0S/FX2N

2.10.3 Connecting A/QnA series controllers
The A series controllers can be connected to the computer via either the CPU interface,
computer link module, the A7BDE interface card or the Ethernet module.
a) Connection via the CPU interface with the SC-09 interface converter
Connect the 9-pin D-shell connector of the SC-09 to the computer. If your computer’s port has a
25-pin connector you will also need a 25/9-pin adapter. Connect the 25-pin D-shell connector to
the CPU port.
GX IEC
Developer

A/QnACPU

SC-09

Reference Manual

GX IEC Developer

2 - 22 Installation

b) Connection via the computer link module
The following ‘computer link’ modules are available: AJ71UC24, A1SJ71UC24, AJ71QC24,
A1SJ71QC24. The computer link module is installed in the base unit (module rack). It is
connected to the computer with a standard RS232 ‘null modem’ cable. Check the pin
assignments of the cable before using it (see below). The communications parameters you set in
Online - Transfer Setup - Ports (© Chapter 7) must match the DIP switch settings on the
computer link modules.
GX IEC
Developer

A/QnACPU

A**J71*C24

RS232

Note: See the computer link module manuals for full details on their settings.
Pin assignments of the RS232 null modem cable
You will need a standard RS232 ‘null modem’ cable for connecting the computer to the
controller via one of the computer link modules. The pin assignments of the 9-pin and 25-pin
connectors for this cable are as follows:
25

25

9

25

9

9

1
2
3
7
6
8
20
4
5

1
3
2
7
6
8
20
4
5

3
2
5
6
1
4
7
8

3
2
7
6
8
20
4
5

2
3
5
6
1
4
7
8

3
2
5
6
1
4
7
8

DIP switch settings
The communications parameters you set in Online - Transfer Setup - Ports
(© Chapter 7) must match the DIP switch settings on the computer link modules.
Note: Please see the computer link module manual for details on the DIP switch settings.

GX IEC Developer

Reference Manual

Installation 2 - 23

c) Connection via the Ethernet module
GX IEC Developer enables a MELSEC A series’ PLC to be programmed via the Ethernet.
The Ethernet module is installed in the base unit. The connection between the Personal
Computer and the Ethernet module is realized via the coaxial cable 10BASE5 (Ethernet) or
10BASE2 (Cheapernet).
The following Ethernet modules can be used:
n
n
n
n
n
n

AJ71E71-S3
AJ71QE71
A1SJ71E71-B2-S3
A1SJ71E71-B5-S5
A1SJ71QE71-B2
A1SJ71QE71-B5

GX IEC
Developer
ETHERNET
Cheapernet

A/QnACPU

A**J71*E71

The communications parameters you set in Online - Transfer Setup - Ports
(© Chapter 7) must match the DIP switch settings on the Ethernet module.
Note: See Ethernet manuals for full details on Ethernet module settings.
Note: The Ethernet modules will only work together properly with GX IEC Developer, if its
version “E” (or higher) is used.
You will find the version number directly on the Ethernet modules.
Note: When the AnU CPU type has been started on the personal computer, change the PLC
type to the AnA CPU.
Communications can only be performed within the same segment.
Communications can not be performed via the router or gateway.

Reference Manual

GX IEC Developer

2 - 24 Installation

2.11

Connecting Q series controllers
The Q series controllers can be connected to the computer via either the CPU interface
(RS232 or USB), computer link module or the Ethernet module.
a) Connection via the CPU interface with the QC30R2 interface cable
Connect the RS232 interface of your computer to the RS232 port of the CPU via the interface
cable QC30R2. If your computer’s port has a 25-pin connector you will also need a 25/9-pin
adapter.

GX IEC
Developer

QC30R2

RS232

Q CPU

b) Connection via the computer link module
The computer link module QJ71C24(-R2) is installed in the base unit (module rack). It is
connected to the computer with a standard RS232 ‘null modem’ cable. Check the pin
assignments of the cable before using it (see below). The communications parameters you set in
Online - Transfer Setup - Ports (© Chapter 7) must match the DIP switch settings on the
computer link modules.

GX IEC
Developer

Q CPU

QJ71C24

RS232

Note: Please see the computer link module manual for details on the DIP switch settings.

GX IEC Developer

Reference Manual

Installation 2 - 25

Pin assignments of the RS232 null modem cable
You will need a standard RS232 ‘null modem’ cable for connecting the computer to the
controller via one of the computer link modules. The pin assignments of the 9-pin and 25-pin
connectors for this cable are as follows:
25

25

9

25

9

9

1
2
3
7
6
8
20
4
5

1
3
2
7
6
8
20
4
5

3
2
5
6
1
4
7
8

3
2
7
6
8
20
4
5

2
3
5
6
1
4
7
8

3
2
5
6
1
4
7
8

DIP switch settings
The communications parameters you set in Online - Transfer Setup - Ports
(© Chapter 7) must match the DIP switch settings on the computer link modules.
Note: Please see the computer link module manual for details on the DIP switch settings.

Reference Manual

GX IEC Developer

2 - 26 Installation

c) Connection via the Ethernet module
GX IEC Developer enables a MELSEC Q series’ PLC to be programmed via the Ethernet.
The Ethernet module QJ71E71(-B2) is installed in the base unit. The connection between the
Personal Computer and the Ethernet module is realized via the coaxial cable 10BASE5 (Ethernet)
or 10BASE2 (Cheapernet).

GX IEC
Developer

Q CPU

QJ71E71

ETHERNET
Cheapernet

Note: See Ethernet manuals for full details on Ethernet module settings.
The communications parameters you set in Online - Transfer Setup - Ports
(© Chapter 7) must match the DIP switch settings on the Ethernet module.

d) Connection via the CPU interface with a standard USB cable
The USB port of the computer is connected to the USB port of the CPU via a standard USB
connection cable.

GX IEC
Developer

Q CPU

Standard
USB Cable

Note: When the PLC CPU is reset while communicating with the PLC CPU via USB connection in
the Windows 2000 environment the message “Unsafe Removal of Device” is displayed.
In this case restart the communication with the PLC CPU after resetting the PLC CPU.

2.12

Connecting a printer
Install your printer, following the manufacturer’s instructions.
The Windows User’s Guide contains detailed instructions on installing printers, printer drivers,
additional fonts, the print options and using the Windows Print Manager.
In GX IEC Developer, you can access the printer setup options by selecting Printer Setup in the
Project menu.

GX IEC Developer

Reference Manual

The User Interface 3 - 1

3

The User Interface
The illustration below shows the screen after loading a project. In this example, the PLC
configuration, a header and a body have all been opened in separate windows.















ƹ

Ƹ

¹

¸

µ

³ Application title bar

Declaration table

¸

Minimise button

· Menu bar



Object window

¹

Status bar

» Toolbar

º

Vertical scrollbar

Ƹ

Horizontal scrollbar

¿ Dialog box

¾

Editor (Body)

ƹ

Project Navigator window

´ Button

Reference Manual

²

µ

Maximise button

GX IEC Developer

3 - 2 The User Interface

3.1

The Title Bar
The title bar contains the name of the project and application, for example:
Garage - GX IEC Developer.

3.2

The Menu Bar
When you start GX IEC Developer only the following menus are displayed:

The complete menu bar with all the GX IEC Developer menus is not displayed until you open or
create a project. When you select one of the menu titles a drop-down list is displayed showing
the menu commands and options. The menu structure and the available options are
context-sensitive, changing depending on what you are currently doing in the program. Options
displayed in light grey are not currently available for selection.
Note: A reference to the complete menu structure is provided at the end of this Reference Manual.

3.2.1

Menu Conventions
·
»

³
²

¿
´

³ Press the key corresponding to the underlined letter in the menu name.
· Menu commands followed by a triangle symbol branch to a submenu with additional
command options, which is displayed as a pop-up menu box.
» Depending on what you are doing, not all menu commands are available at all points in GX
IEC Developer. Menu commands displayed in light grey are currently unavailable.
¿ Menu commands followed by three periods open dialog boxes in which additional entries
and selections must be made.
´ In some cases, key combinations can be used to activate commands directly, without opening
the corresponding menu. When available, these key combinations are shown after the
command in the menu.
² A check mark in front of a menu option shows that this option is currently activated. To
deactivate an activated option, simply select it again. The check mark disappears, indicating
that the option is now inactive.

GX IEC Developer

Reference Manual

The User Interface 3 - 3

3.2.2

Selecting menu commands
Using the mouse
ቢ Point to the menu with the mouse pointer, click with the left mouse button and then click on
the desired command in the drop-down list that appears.
Or:
Click on the appropriate tool icon in the toolbar.
Using the keyboard
ቢ Press ¦ or š to activate the menu bar.
ባ Move the highlight to the desired menu with the cursor keys ¤ and ¥, then select by
pressing «.
Or:
Press the key corresponding to the underlined letter in the menu name (e.g. L for the Online
menu).
ቤ Move the highlight to the desired menu option in the drop-down list with the cursor keys £
and ¢, then press « to select.
Or:
Some menu commands can be selected directly, irrespective of which menu is currently open,
by pressing a key or key combination. These key combinations are shown after the menu
commands in the drop-down menus (e.g. ¦” for Quit in the Project menu).
Note: All the available key combinations for menu commands are listed in the Appendix to
this manual.

3.3

The Toolbar
The toolbar enables you to select the most important menu commands directly by clicking on the
corresponding icons. The toolbar is context-sensitive, i.e. different tool icons are displayed
depending on what you are currently doing in GX IEC Developer. Tool icons can only be selected
with the mouse.
When you start GX IEC Developer, only the icon for opening a project is displayed. You can
switch the toolbar display on or off with the Toolbar option in the View menu.
Note: A complete list of the available tools is provided at the end of this manual.

3.4

The Project Navigator Window and the Objects it Contains
The Project Navigator window is the ‘control centre’ of GX IEC Developer. It contains all the
objects belonging to the project you are working on. All operations on objects are executed
through this window.
The Project Navigator window is not displayed until you open a project. Closing the window
automatically closes the project it contains.
You can always activate the Project Navigator window via the menu item Navigator in the
Window menu.
Three different views can be selected for the project navigator via tabs below the navigator
window:
Project, Calltree, Used by
The Project Navigator window is not displayed until you open a project. Closing the window
automatically closes the project it contains.

Reference Manual

GX IEC Developer

3 - 4 The User Interface

3.4.1

Navigator views
Project
This view gives a total overview of the project. It contains all elements of the project.
Calltree
For this view, the corresponding root items are tasks or also POUs, if they are not related to a
specific task. As subitems all used POUs are shown. Additionally, it can be defined per object, if
used global variables should also be shown.
Used by
This view has exactly two root items. The first root item is the POU pool with its POUs as nodes.
Subitems of the POUs and global variables are always POUs calling respectively using the
corresponding POU or global variable.

3.4.2

Objects in the Project Navigator window
The following standard objects are automatically generated in the Project Navigator window for
every newly-created project:
n
n
n
n
n
n

The Library_Pool
The PLC Parameters
The Task_Pool
The DUT_Pool
Global Variables
The POU_Pool

Note: For a detailed description of these objects please refer to Chapter 4.

3.4.3

How objects are displayed in the Project Navigator window
The entries in the Project Navigator window are arranged hierarchically. The first level is the
project. The entries for the standard objects are located on the second level, from which you can
branch to lower levels where they exist.
The symbol [+] before an entry in the Project Navigator window shows that the entry has
additional lower levels (e.g. [+] POU_Pool).
The symbol [–] before an entry in the Project Navigator window indicates that its subordinate
levels can be ‘collapsed’ so that they are no longer visible (e.g. [–] POU_Pool). This does not
apply for the entry that contains the project name, however.

How to display hidden Navigator hierarchy levels
ቢ Double-click on the entry whose hidden levels you wish to display.
Or:
Select the entry and select the Expand command in the Tools menu.
Or:
Press the key combination [CTRL][+].
Or:
Select the entry and click on the Expand tool icon in the toolbar:
Tool for expanding collapsed Navigator hierarchy levels

GX IEC Developer

Reference Manual

The User Interface 3 - 5

This expands the next level of the hierarchy in the Project Navigator window. These levels can, in
turn, also contain hidden lower levels.
Some of the lower levels in the Project Navigator window are
expanded.

How to hide displayed Navigator hierarchy levels
ቢ Double-click on the entry whose lower levels you wish to hide.
Or:
Select the entry and select Collapse in the Tools menu.
Or:
Press the key combination [CTRL][-].
Or:
Select the entry and click on the Collapse tool in the toolbar:
Tool for collapsing expanded Navigator hierarchy levels

The selected level is collapsed and hidden from view.
Note: There are two possible responses when you double-click on a POU name, depending on
the settings in the MMP400.INI file and in the menu Extras - Options - Zoom Header/Body Navigator Zoom (© Chapter 2).
- Show/hide header and body in the Project Navigator window
- Open Header and body

Reference Manual

GX IEC Developer

3 - 6 The User Interface

How to display additional object information in the Navigator
When you open a new project the additional object information is displayed by default.
ቢ Select the Extended Information command in the View menu.
Useful additional information is then displayed after each entry in the Project Navigator window.
Information when ‘Extended Information’ is not active:
n
n
n

Tasks: Priority, Event
POUs: Program class
Body: Programming language

Additional information when ‘Extended Information’ is active:
n
n
n
n

All entries: Creation date and time
Task_Pool, DUT_Pool, POU_Pool: Number of entries
DUT, Global_Vars, Header: Number of variable entries
POU: Programming language of the program body

Note: In the Sequential Function Chart editor you can activate and deactivate additional
comments for steps with the menu View - Extended Information
(© page 6-24).

3.4.4

Editing objects
The objects at the lowest level of each branch can be opened for editing. These levels are not
marked with [+] or [–] symbols (e.g. PLC_Parameter, Header, Body). Opening them displays
either a dialog box (e.g. PLC_Parameter) or an object window (e.g. Header).
Most operations, such as opening, copying and deleting, can be performed directly in the Project
Navigator window with key combinations. The corresponding menu commands are in the
Object menu. For details on working with objects, see chapter 4.
Note: All key combinations used for working with objects and the Project Navigator are listed
and explained in the Appendix.

GX IEC Developer

Reference Manual

The User Interface 3 - 7

3.5

The Status Bar
The status bar contains information on the current status of your project. You can enable or
disable its display and the information it contains is also configurable. The command for
switching the status bar display on and off is in the View menu.

How to configure the Status Bar
ቢ Double-click in the status bar.
Or:
Select Configure Status bar in the View menu.
The following dialog box is displayed:



CpuType: Display the PLC CPU for which the project is configured



Editor Info: Display the POU name and the number of variable entries in the header



Online: Display online status



Conn Status: Display active connection to the PLC system: PLC state, current scan time.
Display depends on selection of monitoring mode and PLC status.



Error Status: Display PLC system error status.
Display depends on selection of monitoring mode and PLC status.



Security Level: Display current security level



Options

Clock: Display time

How to add status bar items
ቢ Select the item to be displayed in the Possible Status Field list box.
ባ Click on the Add button to display the selected item in the Status bar.
ቤ Repeat steps ቢ and ባ for each additional item to be displayed in the status bar.

How to delete status bar items
ቢ Select the item to be deleted in the Displayed fields list box.
ባ Click on the Delete button to delete the selected item from the Status bar..
ቤ Repeat steps ቢ and ባ for each item to be cleared from the status bar.
Note: You can restore default status bar display settings at any time by clicking on the
Defaults button.

Reference Manual

GX IEC Developer

3 - 8 The User Interface

3.6

Working with Windows
This section only contains a short explanation of the various operations performed with screen
windows. For detailed instructions and definitions of the terms used, please refer to the
Windows User’s Guide. The procedures used with windows in Windows applications programs
are standardised and are not specific to GX IEC Developer.
The following window types are used in GX IEC Developer:
n
n
n

The Project Navigator window
Object Windows
Dialog Boxes

Note: Although it is possible to display several different windows on the screen simultaneously,
only one window can be active for editing at any one time. The currently active window is
identified by a colored title bar.
Please note that you can only open and edit one project, in one Project Navigator window. But
you can start GX IEC Developer several times to open and edit more than one project at a time.

3.6.1

Object windows
How to open windows
ቢ In the Project Navigator window, double-click on the name of the object whose window you
wish to open.
Or:
Select the object in the Project Navigator window by moving the highlight with the cursor
keys £ and ¢, and then press « or select the Open command in the Object menu.
The program opens the object window and displays it to the right of the Project Navigator
window. You can open several object windows at the same time.
Note: When the object window of a body (header) is open you can open its header (body)
with the Open Header (Open Body) command in the Object menu.

How to select an open window
ቢ Click anywhere in the window.
Or:
Select the desired window with the key combination §©.
Or:
Choose the window to be selected from the list of open windows shown in the Window menu.
The title bar of a selected window is highlighted in color.

GX IEC Developer

Reference Manual

The User Interface 3 - 9

How to close a window
ቢ Double-click on the control menu box of the window you wish to close.
Or:
Select the Close command in the window’s control menu.
Or:
Select the window and press §” to activate its control menu Close command.
Or:
Select the window and select the Close command in the Object menu.
The program will ask you if you want to save any editing changes before closing the object
window.
Note: You can close all opened windows at the same time with the Close All command in the
Window menu.

How to arrange windows without overlaps (tiling)
ቢ Select the Tile Horizontally or Tile Vertically command in the Window menu.
The Project Navigator window is displayed on the left of the screen. The object windows are
arranged horizontally or vertically. The size of the object windows depends on how many
windows are currently open.

How to arrange windows with overlaps
ቢ Select the Cascade command in the Window menu.
The Project Navigator window and all open object windows are overlapped across the screen
so that all the title bars are visible, starting at the top left corner.

Reference Manual

GX IEC Developer

3 - 10 The User Interface

3.6.2

Changing window display size
Button Functions
Minimise window
Restore window
Maximise window
Window or Full-size window Ǟ Icon
Click on the Minimise button in the object window (in the upper right corner of the window
title bar), or select Minimise in the window’s control menu.
You can move and position the icons anywhere on the screen. The Arrange Icons command in
the Window menu arranges all the icons in a row at the lower edge of the screen.
The object window icons

Icon Ǟ Previous window size
Click on the Restore button of the icon you wish to open, or simply double-click on the icon.
Full-size window Ǟ Previous window size
Click on the Restore button (in the upper right corner of the window title bar), or select the
Restore command in the control menu.
Window or Icon Ǟ Full-size window
Click on the Maximise button (in the upper right corner of the window title bar), or select the
Maximise command in the control menu.
Note: You can find a list of all the key combinations for working with windows in the Appendix.

GX IEC Developer

Reference Manual

The User Interface 3 - 11

3.6.3

Dialog boxes
Dialog boxes are displayed whenever additional user input is required, for example when you
select the menu commands that are followed by three periods
(e.g. Open ... in the Project menu). In addition to asking you to make entries, dialog boxes can
also contain important information and warnings.
The PLC Parameter dialog box

How to select an open dialog box
ቢ Click anywhere within the dialog box.
Or:
Select the desired box with the key combination ¦–.
The title bar of a selected dialog box is displayed with color shading.

How to close dialog boxes
n

n

If you want to discard the entries or changes you have made in the box, double-click on the
control menu button of the dialog box.
Or:
Select the Close command from the dialog box’s control menu.
Or:
Click on the Cancel button.
Or:
Press the ° key.
If you want to accept the entries in the dialog box, click on the OK button.
Or:
Select the OK button and press the « key.

Note: You can find a list of all the key combinations for working with windows in the Appendix.

Reference Manual

GX IEC Developer

3 - 12 The User Interface

3.7

Customising the Screen Display
The View menu contains all the commands for customising the display for your personal needs.
Toolbar, Status Bar, Horizontal Scrollbar and Grid
You can switch these display elements on and off with the corresponding options in the View
menu, or with the check boxes in the dialog box that is displayed when you select the
Environment option.
The toolbar, status bar, horizontal scrollbar
and the grid can be activated or
deactivated with the check boxes
in the Environment dialog box.

Grid display is enabled.

The check mark  in front of the menu command in the menu View identifies options that are
currently enabled. When you deactivate an option the check mark is no longer displayed.

How to set the screen zoom factor
ቢ Select the Zoom... command in the View menu.
ባ Select one of the four standard zoom factors: 50%, 75%, 100%, 150%.
In addition to these four standard zoom factors you can also enter your own screen display
magnification by changing the display grid size setting.
ቢ Select the Environment... command in the View menu.
ባ Enter a value between 4 and 128 in the Size of Grid field.
The standard zoom factors correspond to the following grid settings:
Zoom factor:
Zoom factor:
Zoom factor:
Zoom factor:

GX IEC Developer

50%
75%
100%
150%

Grid size: 8
Grid size: 12
Grid size: 16
Grid size: 24

Reference Manual

The User Interface 3 - 13

How to select the screen font
ቢ Select the Font command in the View menu.
ባ Choose the font and style you wish to use for the screen display.

All GX IEC Developer texts will be displayed in the selected font. You can use all the fonts
installed in your Windows configuration.
Note: The screen font setting is stored together with the project.

Reference Manual

GX IEC Developer

3 - 14 The User Interface

How to set the display colors
ቢ Select the Colors command in the View menu.
ባ Select the screen element whose color you wish to change:
Background

Monitoring

Selection

Errors

Text

Shade Left Top

Selected Text

Shade Right Bottom

Read Only Text

Grid

Locked Text

Browser Items

Foreground

SFC Raster Elements

The Color dialog box is displayed.
ቤ Click on the color you want in the palette of basic colors.

The current color of the selected element is shown in the two-line palette below the basic
colors palette.
Note: You can also define your own custom colors. For details please refer to the Windows
User’s Guide.
The colors settings are stored with the project.

GX IEC Developer

Reference Manual

The User Interface 3 - 15

How to save the current Workspace
ቢ Select the Save Workspace command in the View menu.
Note: This command only saves the size, arrangement and display of the opened windows with the exception of the Project Navigator window - in the current workspace, ignoring the
font and color settings. The workspace is saved with the project in the file WORKSPACE.SYS.

How to load a previously saved Workspace
ቢ Select the Load Workspace command in the View menu.
This command automatically loads the settings stored with the Save Workspace command by
loading the data from the WORKSPACE.SYS file.

How to load the system defaults
ቢ Select the System Defaults command in the View menu.
When you create a new project the following system defaults are always selected automatically:
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n

Reference Manual

Toolbar display enabled
Status bar display enabled
Horizontal scrollbar display enabled
Grid display enabled
Zoom factor: 100 %
Grid size: 16
Extended information display in Project Navigator enabled
Background: light greySelection: dark grey
Text: black
Selected Text: white
Read Only Text: dark grey
Locked Text: dark grey
Foreground: light grey
Monitoring: blue
Errors: red
Shade left top: white
Shade right bottom: dark grey
Grid: black

GX IEC Developer

3 - 16 The User Interface

3.8

Mouse and keyboard operation
All operations in GX IEC Developer can be performed both with the mouse and the keyboard.
In most cases, a single click with the left mouse button corresponds to the ´ key, and a
double-click corresponds to the « key.
The instructions below are primarily for working with the mouse, but special keyboard key
combinations are also included. All the key combinations for working with tables and the editors
are listed in the Appendix of this manual.
Note: For full details on using the mouse in Windows please refer to Windows Fundamentals
section in the Windows User’s Guide.

3.9

General editing functions
Most of the commands in the Edit menu are identical in all Windows application programs.
Note: You can find detailed explanations of these commands in your Windows User’s Guide.

How to cut, copy and delete data
ቢ Select the element you wish to edit (see following pages):
n
n
n
n
n
n

Cell contents in a Declaration Table: Enable the editing mode in the cell and select the cell text.
Lines in a Declaration Table: Select one or more lines.
Entire networks in the editors: Select the network bar to the left of the network you wish to edit.
Ranges (instruction, operand, lines) in the Instruction List: Select the range to be edited.
Program elements in the graphical editors: Select the elements to be edited.
Program elements in the Sequential Function Chart Language: Select the elements to be
edited. When you select a Step its corresponding Transition is automatically selected as well.

ባ Select the editing command you wish to execute in the Edit menu.
Or:
Press the corresponding key combination:
Cut
X
Copy
C
Delete
µ
IMPORTANT: Deletions are performed directly, without prompting for confirmation. If you
inadvertently delete something you can restore the deleted data by selecting the Undo
command in the Edit menu. However, please note that this only works if you execute Undo
directly after performing the deletion!

GX IEC Developer

Reference Manual

The User Interface 3 - 17

How to paste data
ቢ Select the position at which you wish to insert an element:
n

n

n

n

n

Cell contents in a Declaration Table: Activate editing mode in the cell in which you wish to
insert the text from the clipboard.
Lines in a Declaration Table: Select a cell in the line before which you wish to insert the lines
from the clipboard, or select the lines you wish to overwrite with the data from the clipboard.
Entire networks in the editors: Select the network bar of the network before which you wish
to insert the network stored in the clipboard.
Ranges (instruction, operand, lines) in the Instruction List: Position the cursor at the point at
which you wish to insert the text from the clipboard.
Sequential Function Chart elements: Select the point in the sequence before which you wish
to insert the data from the clipboard.

ባ Select Paste in the Edit menu.
Or:
Press the corresponding key combination:
Paste
§V
ቤ Elements in the graphical editors: When you select the Paste command the mouse pointer
changes to a plus sign symbol. Position the pointer at the location at which you wish to insert
the elements from the clipboard.

How to undo editing operations
ቢ Select Undo or Redo in the Edit menu.
Or:
Press the corresponding key combination:
Undo
¦ BACKSPACE
Redo
§ BACKSPACE
Undo undoes the effects of the last editing operation.
Redo undoes the effects of the last Undo operation.

Reference Manual

GX IEC Developer

3 - 18 The User Interface

Global Search and Replace
The Search and Replace functions can now be used globally to search the entire project
(Edit - Find/Replace menu).

Find in:
This option enables you to search and replace in




the entire project (All objects)
individual objects selected in the Project Navigator
the current editor only

Find What / Replace With:
You can enter the following elements as find/replace arguments:
-

Variable identifiers
Data types
- Adresses
- Sequential function chart language step names
- Sequential function chart language transitions
- POU names
Find options:
-



Match whole word only Search the entire word only



Match case Search and replace operation for text exactly as entered, with upper/or lower
case characters



Search in comments Activating this option extends the search and replace operation to
comment texts

Important note: You can replace function blocks in the graphical editors but no check is
performed. Also, the replace procedure cannot be reversed; the only way to restore the project
to its original state is by not saving it and reloading the old version from the disk.

GX IEC Developer

Reference Manual

The User Interface 3 - 19

3.10

Working in tables
The following objects are managed and defined in tables:
n
n
n
n

Global Variables
Local Variables (Header)
Data Unit Types (structured data types)
Tasks

To open the table object window, double-click on the corresponding object in the Project
Navigator window. If the object window of a body is already open you can open its header by
selecting the Open Header command in the Object menu.














³ Cell with the line number

´

Local Variables Table

· Table cell

²

Up arrow (dialog box)

» Global Variables Table



Down arrow (list box)

¿ Table Column Headings

You cannot change the number or the arrangement of the columns. When you activate a new
table only line 0 is shown, in which you can enter the first variable.
Note: You can also copy all the entries from the global variables list to the header of a POU by
using the clipboard. When you do this, the data fields are automatically placed in the correct
columns.

Reference Manual

GX IEC Developer

3 - 20 The User Interface

3.10.1 Editing in tables
How to select a table cell
ቢ Click on the cell you wish to select.
Or:
Select the cell with the cursor keys.
Selected cells are identified with an outline box.

How to select a table line
ቢ Click on the cell containing the line number.
Or:
Select any cell in the line and press the key combination ² or ¨¶.
The selected lines are highlighted in the display.

How to select multiple table lines
ቢ Select the first line in the range to be selected:
Continuous range: Hold down the ¨ key and click on the last line of the range to be selected.
Or:
Hold down the ¨ key and extend the selection to the lines above or below the first selected
line with the £ or ¢ keys.
Selecting groups of individual lines: Hold down the § key and click on the lines you wish
to select.
The selected lines are highlighted in the display.

How to activate editing mode
ቢ Double-click on the cell in which you wish to edit.
Or:
Select the cell and press the ´ key.
Or:
Select a cell and type the text you wish to enter.

How to deactivate editing mode
ቢ Click on another cell.
Or:
Press the « key.

GX IEC Developer

Reference Manual

The User Interface 3 - 21

How to open a list box or dialog box
ቢ Double-click on the arrow symbol on the right hand side of the cell.
ባ Select the appropriate entry from the list box or dialog box.
Or:
ቢ Select a cell with an arrow symbol at its right hand side.
ባ Press the key combination ¦¢.
ቤ Select the appropriate entry with the £ and ¢ keys, then press « to transfer the entry to
the cell.
When editing mode is activated, the blinking text entry cursor appears in the cell and the
background color of the cell changes.
Note: All the key combinations for working with tables are listed in the Appendix.

How to change column widths
ቢ Position the mouse pointer on the dividing line between the headings of the columns.
The pointer changes to a double-headed arrow symbol.
ባ Hold down the left mouse button and move the shaded column divider line so that the
column has the desired width.

How to insert a new line
ቢ Select New Declaration in the Edit menu.
ባ Select the position at which the new line is to be inserted.
Top
Inserts a new line at the top of the table
Before
Inserts a new line directly before the selected line/cell
After
Inserts a new line directly after the selected line/cell
Bottom
Inserts a new line at the end of the table
Or:
ቢ Select any cell in the last line of the table.
ባ Press the key combination ¨«.
The line numbering is automatically updated after the insertion operation.

How to sort table entries
ቢ Select Sort in the Tools menu.
ባ Select the sort key to be used for the alphabetical sort procedure:
Type
Sort by data type
Class
Sort by class
Identifier Sort by identifier
IMPORTANT: The table should not contain any empty lines.

Reference Manual

GX IEC Developer

3 - 22 The User Interface

3.10.2 Automatic copying of the contents of the preceding line into the new line
(Autoincrement)
When a new line is entered in a declaration table the contents of the preceding line are automatically
copied to the new fields. Identifiers and addresses are automatically incremented by 1.

This function is only available when the Incremental New Declarations option in the Extras Options - Editing - Declaration Editor menu is enabled.
If you also wish to include the contents of the Type and Comment fields you must also activate
the Copy Comment and Type Fields option.

3.10.3 Selecting data types in the declaration table

Libraries

& lt; ALL & gt; All data types (incl. Libraries)


& lt; Project & gt; All data types in the project



Manufacturer_Lib Reserved for functions to be added later



Standard_Lib Reserved for functions to be added later

Type Class
Data type class


Simple Types Simple data types



Data Unit Types Structured data types (DUT)



Function Blocks Function blocks

Types
All existing data types, depends on the selections in the previous list fields.

GX IEC Developer

Reference Manual

The User Interface 3 - 23

3.10.4 Automatic default data types in the declaration table
As soon as you enter an address the most likely data type for that address is automatically
displayed in the Type column.
Examples:
Entry: X1
Default type: BOOL
Entry: D1
Default type: INT

3.11

Working in the editors (Body)
The body contains the actual code of the PLC program. To open the body’s object window,
double-click on the Body entry in the Project Navigator window. If the object window of a
header is already open you can open its body with the Open Body command in the Object
window.


³ Network bar


·

Editing area

3.11.1 Networks
In the Sequential Function Chart, Ladder Diagram and Function Block Diagram languages, the
PLC program is always divided into a number of logical program units referred to as ‘networks’.
These networks are numbered consecutively and can be given network labels which can be used
as destinations for jump (goto) instructions.
IMPORTANT: In the graphical editors (Ladder Diagram and Function Block Diagram) you can
only program a maximum of one circuit in each network.

Reference Manual

GX IEC Developer

3 - 24 The User Interface

How to enter a new network
ቢ Select the New Network command in the Edit menu.
ባ Choose the position at which you wish to insert the network.
Top
At the beginning of the program
Before
Directly before the selected network
After
Directly after the selected network
Bottom
At the end of the program
MELSEC Before
Insert a MELSEC network directly before the selected
network (only possible in Instruction List)
Or:
ቢ Use the following tools:
Tool

Function

Menu Command

Keys

Insert a new network before the
selected network

Edit - New Network - Before

¦B

Insert a new network after the selected
network

Edit - New Network - After

¦A

Or:
ቢ Insert new networks directly in the Network List.
Note: In MELSEC networks you can only use MELSEC programming instructions; you cannot
use the IEC instructions. Also, you can only insert MELSEC networks in Instruction List programs
(© Appendix E).

How to assign network labels
ቢ Double-click on the network bar.
Or:
Activate selection mode, position the mouse pointer over the network bar with the cursor
keys, and then press the « key.
Options

A dialog box is displayed in which you can enter the network label and title:


Label: The label must be terminated with a colon (:) and must consist of a maximum of 8
characters (including the colon). In MELSEC networks you can also assign absolute labels.
An absolute label is a specific pointer address, e.g. P20 (© page 7-26).



Title: This entry is optional. The title can have up to 20 characters.

Note: Network labels and titles can also be entered directly in the Network List.
Network labels can be used as jump destinations in your PLC program, using the JMP operator
in the Instruction List language, and with the jump instruction in the Ladder Diagram and
Function Block Diagram languages.
Remember that every network label uses one system label and that the total number of system
labels is limited to a maximum of 256. Since system labels are also needed for other elements in
GX IEC Developer (© page 5-30), you should only define labels to networks to which you
actually intend to perform a jump.

GX IEC Developer

Reference Manual

The User Interface 3 - 25

How to make the network area larger/smaller
ቢ In select mode, position the mouse pointer on the lower horizontal edge of the network bar.
The pointer changes to a double-headed arrow symbol.
ባ Hold down the left mouse button and drag the dividing line up or down as required.
Or:
Press the ´ key. Hold down the ´ key and drag the dividing line up or down with the £
and ¢ cursor keys.
When you release the mouse button or the ´ key the network is displayed in the new size.
Note: You do not normally have to change network size manually as it is adjusted dynamically;
when you enter program elements or text the network is automatically enlarged as required.

Managing networks
The Network List is a powerful tool that gives you a clear overview of each POU’s networks,
enabling you to manage them easily and efficiently.
The Network List

Reference Manual

GX IEC Developer

3 - 26 The User Interface

ቢ Select the Network List command in the Tools menu.
A list of all the networks with their labels and titles is shown on the left of the dialog box
displayed. The dialog box contains the following buttons:


Insert:
You will be prompted for the label and title of the new network. A new network is then
inserted in the Network List and the body directly before the currently selected network.



Append:
You will be prompted for the label and title of the new network. A new network is then
inserted in the Network List and the body as the last network.



Edit:
Edit the label and title of the currently selected network.



Cut:
Cuts the currently selected network, deleting it from the Network List and the body and
inserting it in the clipboard.



Copy:
Copies the currently selected network to the clipboard.



Paste:
The network in the clipboard is inserted in the Network List and the body, directly before
the currently selected network.



Delete:
Deletes the currently selected network without copying it to the clipboard. If you
accidentally delete a network you can recover it by clicking on the Undo button.
However, please note that Undo only works if you execute it immediately after
performing the Delete command!



Undo:
Undoes the effects of the last command.



Redo:
Undoes the effects of the last Undo command.



Find:
Allows you to find specific network labels in your program. Please note that the search is
case-sensitive and wildcard characters (? and *) are not supported.



Close:
Closes the dialog box, accepting any changes made.

Note: The standard Windows key combinations for Delete, Cut, Copy and Paste are not
supported in this dialog box! You can only perform these operations with the buttons in the
box. However, the key combinations are supported for editing labels and titles.

GX IEC Developer

Reference Manual

The User Interface 3 - 27

3.12

The text editors
Operation of both the text editors – IEC Instruction List and MELSEC Instruction List – is similar
to that of a normal word processor.
The Instruction List consists of a sequence of controller instructions. Each controller instruction
must begin on a new line, and consists of an operator (operator, function or function block) and
one or more operands/variables. The operator and the operand must be separated by a tab stop.




IEC Instruction List









³ Network bar

¿

Column for operand(s)

· Editing Area

´

Operator column

» Comment

²

MELSEC network

Note: See the Chapter 6 for details on programming.
A detailed description on how to insert programming instructions and variables is given at the
end of this chapter.
All key combinations for working in Instruction List language are described in the appendix.

Reference Manual

GX IEC Developer

3 - 28 The User Interface

3.12.1 Edit functions
How to activate editing mode
There are three ways to activate editing mode:
n
n
n

By selecting the Tools - Edit Network command, or
By double-clicking in the editing area, or
By clicking on the Edit Network tool:
Edit Network tool

The entry cursor is then displayed in the editing area.

How to change the column width
ቢ In select mode, position the mouse pointer on the vertical line between the columns.
The pointer changes to a double-headed arrow.
ባ Hold down the left mouse button and drag the dividing line to the left or right as required.
Or:
Hold down the ´ key and move the dividing line left or right with the ¥ and ¤ cursor keys.
When you release the mouse button or the ´ key the dividing line is redisplayed in the new
position.

How to enter comments
ቢ Position the cursor at the point where you wish to enter the comment.
You can insert comments anywhere in the Instruction List, i.e. in the third column or in a new line.
ባ Comment text must always be enclosed by the characters (* and *).

How to insert a programming instruction and a variable
© page 3-43 and 3-45

GX IEC Developer

Reference Manual

The User Interface 3 - 29

3.13

The graphical editors
Operation of the two graphical editors – Ladder Diagram and Function Block Diagram – is
comparable to working in a standard graphics program. The program elements used for writing
PLC programs are provided in the toolbar and the Tools menu.










º




¾
µ

¹

¸

³ Ladder Diagram (LD)



Function

· Function Block Diagram (FBD)

º

Output variable

» Network bar

¾

Output coil (Ladder Diagram only)

¿ Editing area

µ

Comment

´ Input variable (poll for
signal status ‘1’)

¸

Input contact (poll for signal
status ‘1’) (Ladder Diagram only)

² Input variable (negated, poll for
signal status ‘0’)

¹

Power bar (Ladder Diagram only)

Note: See the Chapter 6 for details on programming.
A detailed description on how to insert programming instructions and variables is given at the
end of this chapter.
All key combinations for working in graphical editors are described in the appendix.

Reference Manual

GX IEC Developer

3 - 30 The User Interface

3.13.1 Options
In the menu Options - Extras you can specify options which make handling operations in the
graphic editors easier.

FBD/LD

Declare New Identifiers When you overwrite a dummy variable in a graphical editor with a
variable identifier name that has not yet been declared the Variable Selection (Mode
NewVar) dialog box will be displayed automatically so that you can enter the declaration for
the new variable.




Automatic Input/Output Variables The system will automatically create the input and
output variables when you insert a function block in a graphical editor.



GX IEC Developer

Pin Overwrite When you create a connection to an empty variable connection in a graphical
editor the empty variable will be overwritten.

Automatic ENO Variables The system will automatically create the ENO output variable
when you insert a function block in a graphical editor. If the ENO output variable is not
needed this option has to be disabled.

Reference Manual

The User Interface 3 - 31

3.13.2 Context menu
When edit mode is active you can display the context menu by clicking the right mouse button
or pressing ’.



Line / Arrow (toggle function) Toggles between select mode and interconnect mode.



AutoConnect Makes positioning and moving graphical elements simpler. When elements are
moved the connection lines are redrawn automatically (© page 3-34)
Mouse
Pointer

Purpose
Select Mode

Interconnect Mode

Select Mode + AutoConnect

Interconnect Mode + AutoConnect



VarInput Pin (FBD only) Insert input variable (same as Tools - Input Variable)



Contact (LD only) Insert input contact (same as Tools - Contact)



VarOutput Pin (FBD only) Insert output variable (same as Tools - Output Variable)



Coil (LD only) Insert output coil (same as Tools - Coil)



FUN/FB Opens Function Block Selection dialog box for programming instruction selection



Last 5 function blocks list The last 5 function blocks inserted in the LD or FBD editors can
be reused directly by selecting them from the list at the bottom of the context menu.

3.13.3 Right mouse button or F2



Mouse pointer on variable Opens the Variable Selection dialog box for selection of a
variable from the list.



Reference Manual

Mouse pointer in editing mode / on block Activates context menu

Mouse pointer on a jump instruction Opens the Label List dialog box for selection of a
network label from the list.

GX IEC Developer

3 - 32 The User Interface

3.13.4 Program Elements
Tool

Program element

Menu Command

Key(s)

Lines (Interconnect Mode)

Tools - Network Elements Interconnect Mode

§t

Input contact
(Ladder Diagram only)

Tools - Network Elements Contact

§N

Output coil
(Ladder Diagram only)

Tools - Network Elements Coil

§L

Function block
(programming instruction)

Tools - Network Elements Function block

§F

Input variable

Tools - Network Elements Input Variable

§I

Output variable

Tools - Network Elements Output Variable

§O

Jump instruction

Tools - Network Elements Jump

§J

Return instruction

Tools - Network Elements Return

§R

Vertical space

Tools - Open Row

§w

Horizontal space

Tools - Open Column

§u

Comment text

Tools - Network Elements Comment

§m

How to insert new program elements
Icons are provided in the toolbar for all the available program elements.
ቢ Click on the tool for the element you wish to insert.
Or:
Select the menu command from the Tools menu, or press the corresponding key
combination.
The mouse pointer then changes to the symbol for the selected program element.
ባ Position the tip of the pointer at the point where you want to insert the element and press
the left mouse button or the « key.

How to select program elements
ቢ Click on the program element.
Or:
Position the pointer over the program element with the cursor keys and then press the ´ key.
Selected program elements are highlighted in a different color.

GX IEC Developer

Reference Manual

The User Interface 3 - 33

How to select more than one program element
n

Selecting elements out of sequence: Hold down the ¨ key and click on all the program
elements you wish to select.
Selecting elements in sequence: Position the mouse pointer outside the area to be selected,
hold down the left mouse button and drag the dotted rectangle around the elements you
wish to select.
Or:

n

Selecting elements out of sequence: While holding down the ¨ key, select the elements
one after another by positioning the mouse pointer over them with the cursor keys and
pressing ´.
Selecting elements in sequence: Position the pointer outside the area to be marked. While
holding down the ´ key, use the cursor keys to drag the dotted rectangle around the
program elements you wish to select.

Selected program elements are highlighted in a different color.
Note: You can only select multiple program elements within the same network.

How to increase and decrease editing area spacing
The Tools - Open Row/Open Column commands are used to increase and decrease the
horizontal and vertical spacing in the editing area.
ቢ Select the menu command or the corresponding tool in the toolbar.
The pointer changes to a horizontal or vertical double-headed arrow.
ባ Position the pointer at the location where you wish to increase/decrease spacing.
ቤ Increase spacing: Click with the mouse button or press the ´ key.
Decrease spacing: Hold down the ¨ key while clicking or pressing the ´ key.

How to enter comments
You can enter comments at any point in the editing area.
ቢ Select Comment in the Tools menu or the corresponding tool in the toolbar.
The pointer changes to a comment text symbol.
ባ Move the pointer to the position where you wish to insert the comment.
ቤ Hold down the left mouse button and drag to create a comment field.
Or:
Hold down the ´ key and create a comment field with the cursor keys ¤ and ¢.
When you release the mouse button or the ´ key the blinking editing cursor appears in the
newly-created comment field.
ብ Enter your comment text.

How to insert a programming instruction
© page 3-43

Reference Manual

GX IEC Developer

3 - 34 The User Interface

3.13.5 AutoConnect
The AutoConnect function can be activated in the Tools menu or the context menu.
The AutoConnect mode makes moving and connecting graphical elements much easier. When
you move the elements the connecting lines are stretched and rerouted automatically, so that
you do not need to edit the lines by hand. To connect elements in the AutoConnect mode you
simply click on the start and end points and the lines are drawn automatically.
The mouse pointer has the following forms in AutoConnect mode:
Mouse
Pointer

Purpose
Select Mode + AutoConnect

Interconnect Mode + AutoConnect

Moving elements (rubber banding)
ቢ Activate both select mode and AutoConnect.
ባ Click on the element you wish to move and drag it to the new position, holding the left
mouse button down.
ቤ Release the mouse button when you reach the position at which you wish to place the element.

The lower block MOV_M and its associated
connecting lines are selected.

The block is dragged to its new position.
Temporary diagonal connection lines are
displayed while you are repositioning the block.

The block has been moved to its new position
and the connecting lines have been redrawn
automatically. The variables have also been
moved automatically, thus retaining their
positions relative to the function block.

If there is an anchor point on the connection line the lines will only be modified up to the
position of the first anchor point. The lines on the other side of the anchor point and the anchor
point itself all remain unchanged (© page 3-37 ).

GX IEC Developer

Reference Manual

The User Interface 3 - 35

An error message will be displayed if you try to move an element to a position that GX IEC
Developer cannot calculate. You can then abort the move operation.
The Undo function is available as well.
Inserting connection lines (autorouting)
ቢ Activate both Interconnect mode and AutoConnect.
ባ Click on the position for the starting point. Possible starting points are indicated by black dots.
This activates the connecting line, which follows the mouse pointer as you move it.

ቤ Position the mouse pointer at the end point.

ብ Click on the end point.
The connecting line is drawn automatically.

Reference Manual

GX IEC Developer

3 - 36 The User Interface

Recalculate Line
The menu command Recalculate Line in the Tools menu helps to recalculate lines which have
already been drawn.
In the normal Interconnect Mode (AutoConnect is disabled) a connection with several lines has
been created.

ቢ Activate the Interconnect Mode and AutoConnect.
ባ Click on the connection.
All lines of the connection will be marked.
ቤ Activate the command Recalculate Line in the Tools menu.
The connection is recalculated.

Possible starting and end points
Try moving the connecting line over the various elements in the editing window. As you do so
black dots are displayed to indicate possible connection points. The connecting line is drawn to
the black dot under the tip of the pencil symbol when you click the mouse button.
Examples of possible connection points:
-

Variable connections (without variables) on function blocks
Between variables and variable connections (without variables) on function blocks
Ends of lines
Positions on lines

The positions of the connection points are dictated by the grid raster.
If you click on a position where no black connection dots are displayed the operation will be
aborted automatically, thus preventing the inadvertent creation of connection lines without
connected ends.

GX IEC Developer

Reference Manual

The User Interface 3 - 37

Anchor points
Double-clicking on a potential connection point creates an anchor point. Anchor points are
indicated by small black squares.
When you move elements in the editing window the positions of the anchor points remain
unchanged.

Anchor point

Overwriting unassigned variable pins
If the starting or end point of a new line is an unassigned variable connection (pin) the
connection is overwritten automatically when the line is inserted. You can activate or deactivate
this function with the Extras - Options - Editing - Pin Overwrite option.
Restrictions for connecting lines
Do not try to insert connecting lines between variable pins for which different variable types
have been declared. This will result in an error message when you perform a check on the POU.
Do not try to draw connecting lines through function blocks.

Reference Manual

GX IEC Developer

3 - 38 The User Interface

3.13.6 Variables
How to configure input signals
ቢ Double-click on an input contact or on the connection of the input variable in a function block.
Or:
Position the pointer with the cursor keys on an input contact or on the connection of the
input variable in a function block and press the key combination [CTRL]+[ALT]+[S].
A dialog box is displayed with the following options:
Normal
Poll for signal status ‘1’
Negation
Poll for signal status ‘0’
ባ Make the appropriate selection in the dialog box.
³ Negated input variable



· Normal input variable





» Normal input contact
¿ Negated input contact



An input signal can also be configured directly:
ቢ Click on the input contact or a function block to select it.
ባ Press the key combination [CTRL]+[ALT]+[S] to negate the input or press the key
combination [CTRL]+[ALT]+[C] to undo the negation.
Or:
ቢ Click on the input contact or a function block to select it.
ባ In the menu Edit select Toggle Signal Configuration and click on the selected input. The
signal configuration of this input will be toggle.
If you select Edit - Signal Configuration, after clicking on the the selected input the Signal
Configuration dialog appears.

How to configure output signals
ቢ Double-click on an output coil or on the connection of the output variable in a function block.
Or:
Position the pointer with the cursor keys on an output coil or on the connection of the
output variable in a function block and press the key combination [CTRL]+[ALT]+[S].
A dialog box is displayed with the following options:
Normal
Poll for signal status ‘1’
Negation
Poll for signal status ‘0’
Set
Set (output coil only)
Reset
Reset (output coil only)
ባ Make the appropriate selection in the dialog box.



³ Normal output coil




· Negated output coil
» Set output coil
¿ Reset output coil
´ Normal output variable



GX IEC Developer



² Negated output variable

Reference Manual

The User Interface 3 - 39

How to assign input and output variables to programming instructions
ቢ Select Tools - Input Variable/Output Variable or the corresponding tool in the toolbar.
The pointer changes to an input variable or output variable symbol.
ባ Position the tip of the pointer over the connection of the function block.
ቤ Click on this position.
Or:
Press the ´ key.
The variable is inserted. You must now assign the variable name.
Note: Most programming instructions have a specific number of input variables. However, in
some cases (e.g. ADD_E) the number of input variables can be increased. With these
instructions the Number of Pins field is activated in the programming instruction dialog box.
Enter the required number (max. 28) in this field. Note that the EN input is not included in the
total. For example, if you enter 5 connections for the ADD_E function the resulting Block will
have 5 real connections for the addition operation and one EN input.



ADD_E function with
³ one EN input



· and 5 addition connections

How to insert a variable
© page 3-45

Adding and removing input variables
Select a function block for which the number of input variables can be changed.
There are variety of different ways to add/remove input variable pins:
n

Increment Pins / Decrement Pins options in the Edit menu

n

+ and - keys in the numeric keypad

n

Toolbar icons:
Increment
Decrement

n

Position the mouse pointer on the lower border of the function block. When the pointer
changes to a double arrow press the left button and drag down (increment) or up (decrement).

Incrementing
If the Automatic Input/Output Box option in Extras - Options - Editing is activated empty
dummy variables are automatically inserted when you increment the number of variable pins.
Decrementing
The input variables will be deleted if they are still empty, i.e. if no variable has yet been assigned
to them. However, if variables have already been assigned to them they will not be deleted.

Reference Manual

GX IEC Developer

3 - 40 The User Interface

How to insert input and output variables in the graphical editors automatically
ቢ Activate the Automatic Input/Output Box option in Extras - Options - Editing.
When this option is activated the input and output variables are automatically inserted when
you add a function block in the graphical editors. The dummy identifier ? (question mark) is
inserted in the variable name field.

Deleting variables
ቢ Select the variable’s connecting line.
ባ Press µ.
Or:
ቢ Select the question mark dummy or the variable name.
ባ Press µ.
ቤ Press the © key.
Note: You do not need to delete the variables at the connecting pins before inserting lines in
AutoConnect mode. They are overwritten automatically.

Stepping through variables in a network
Pressing © and ¨© steps through all the variables in the current network forwards or
backwards, selecting them one after another.

GX IEC Developer

Reference Manual

The User Interface 3 - 41

3.13.7 Jump and Return Instructions
How to configure jump instructions (label and signal)
A jump instruction executes a branch to a specified network, using the network label as the
destination.
ቢ Click on the dummy label Label by the jump instruction symbol.
Or:
Position the pointer over the dummy label and press the ´ key.
ባ Enter the jump destination name.
ቤ Double-click on the jump instruction symbol.
Or:
Position the pointer over the jump instruction symbol and press the « key.
A dialog box is displayed with the following options:
Normal
Poll for signal status ‘1’
Negation
Poll for signal status ‘0’
ብ Make the appropriate selection in the dialog box.
Note: The jump instruction corresponds to the JMP operator in the Instruction List.
Operator (IL)
JMP
JMPN
JMPC
JMPCN

Program element (LD/FBD)
Normal jump (poll for signal status ‘1’)
Negated jump (poll for signal status ‘0’)
Normal jump with input condition
Negated jump with input condition

How to configure return instructions (signals)
The return instruction returns control from a function block to the program from which the
function block instance was called.
ቢ Double-click on the return instruction symbol.
Or:
Position the pointer over the return instruction symbol and press the « key.
A dialog box is displayed with the following options:
Normal
Poll for signal status ‘1’
Negation
Poll for signal status ‘0’
ባ Make the appropriate selection in the dialog box.
Note: The return instruction corresponds to the RET operator in Instruction List language (IL).
Operator (IL)
RET
RETN
RETC
RETCN

Reference Manual

Program element (LD/FBD)
Normal return instruction (Poll for signal status ‘1’)
Negated return instruction (Poll for signal status ‘0’)
Normal return instruction with input condition
Negated return instruction with input condition

GX IEC Developer

3 - 42 The User Interface

3.13.8 Graphic macros
Setting the number of graphic macros
You can create and store up to 25 graphic macros.


Number of Graphic macros in Extras - Options - Graphic
Enter the number of graphic macros you wish to use.

How to create graphic macros
ቢ Select the area in the editing area that you wish to store as a graphic macro.
The selected area is highlighted.
ባ Select the Copy command in the Edit menu.
The selected area is copied to the clipboard.
ቤ Select Define Graphic Macros in the Tools menu.
The Configure Custom Tools dialog box appears on the screen.
ብ Select the name under which you wish to store the macro.
If a macro is already stored under the selected name its contents are shown in the Contents box.
ቦ Click on the Paste button.
The contents of the clipboard are pasted into the Contents box.
ቧ Click on the Close button to confirm your entries and close the dialog box.
Creating graphic macros

Selecting graphic macros




GX IEC Developer

Tools - Custom The names of the first five graphic macros are displayed in the menu and
they can also be selected by pressing ¦ together with the corresponding number key.
Tools - More Custom Enables you to select all available graphic macros.

Reference Manual

The User Interface 3 - 43

3.14

Selecting Programming Instructions
Graphical editors:
Menu: Tools - Network Elements - Function Block
n
n

Toolbar icon

n

FUN/FB context menu (right mouse key)

Text editors:
Menu: Tools - List Operators/Operands
n
n
n

’ key
Right mouse key

The Function Block Selection dialog box is displayed. It remains open, active and visible until it
is explicitly closed. It is also closed automatically when you close the current body or activate
another window on the screen.

Libraries

& lt; ALL & gt; All programming instructions available for the PLC currently selected.


& lt; Project & gt; Functions and function blocks created by the user (depends on the selection in the
Operator_Type field)



Manufacturer_Lib All programming instructions in the manufacturer library



Standard_Lib All programming instructions in the standard library

Last recently used
All recently-used programming instructions

Reference Manual

GX IEC Developer

3 - 44 The User Interface

Operator Type

All Types IEC operators, functions and function blocks


Operators IEC operators



Functions Functions



Function Blocks Function blocks

Number of Pins
This field is activated when the instruction allows you to change the number of input contacts
(input pins).
Operators
All available programming instructions (depends on the selections in the previous fields). If you
enter the first letters of an instruction manually the highlight automatically jumps to the first
instruction beginning with that letter or letter combination.
APPLY button

Graphical editors When you move the mouse pointer over the editing window it changes to
a pointer with a function block symbol. Simply click at the position where you wish to insert
the instruction.


Text editors Enters the selected programming instruction in the editor window.

Getting help on specific programming instructions
Select the instruction in the Operators list field and then press the Help button.

GX IEC Developer

Reference Manual

The User Interface 3 - 45

3.15

Variables

3.15.1 Selecting existing variables and declaring new variables
Before you open the Variable Selection dialog box:


Graphical editors: Highlight the variable/instance dummy name



Text editors: Place the cursor in the variables column



Sequential function chart language: Highlight a transition definition

Then:


In the Task Information dialog box: Event (F2 key only)



In both graphical and text editors:
- Tools - List Operators/Operands menu
- ’ key
- Right mouse button

The Variable Selection dialog box is then displayed. This dialog remains open and visible on the
screen and does not need to be closed when you perform other editing actions in the program
body. If you prefer to minimize the dialog box automatically after applying a declaration,
activate the “Minimize Dialog after apply” checkbox.

Libraries

& lt; ALL & gt; All of the project’s variables



& lt; Global Vars & gt; All global variables



Manufacturer_Lib Reserved for functions to be added later



Reference Manual

& lt; Header & gt; All local variables in the header of the currently open POU

Standard_Lib Reserved for functions to be added later

GX IEC Developer

3 - 46 The User Interface

Type
Depends on the selections in the Libraries and Type Class list fields:


Simple Types Simple data types: ANY, ANY_BIT ...



Data Unit Types Structured data types (DUT)



Function Blocks Function blocks

For existing variables the currently valid type is displayed.
Default settings:
- Graphic editor: Data type of formal parameter, contact/coil: BOOL
- Transition in SFC: BOOL
Type Class

Simple Types Simple data types


Data Unit Types Structured data types (DUT)



Function Blocks Function blocks

For existing variables the currently valid type class is displayed.
Selecting a variable
Type Class: Simple Types
Type: BOOL
Variables: The variables are displayed.
Doubleclick on the variable to select it.

Variables
Depends on the selections in the preceding list fields: All existing variables
When you enter the first letters of the variable name the highlight will automatically jump to the
first variable with this letter or letter combination.
APPLY button
Enters the selected variable into the selected variable dummy name in the editor (same effect as
double-clicking).

GX IEC Developer

Reference Manual

The User Interface 3 - 47

NEW ON button
Selecting this button expands the dialog box, displaying an additional area for the declaration of
new variables. The dialog box title changes to Variable Selection (Mode NewVar).

This dialog box also appears:
-

When you select the Tools - New Variable menu option (ALT + N).
When you overwrite a dummy variable name in a graphical editor with the name of a
variable that has not yet been declared. This automatic function can be activated/deactivated
with the option Extras - Options - Editing - Declare New Identifiers.
Dummy variable name

The expanded dialog box fields enable you to declare new variables of the type defined by the
selections in the Library, Type and Type Class fields. The entries are the same as those in the
variable declaration tables.
You can also declare instances, in the same way as in the declaration tables.
DEFINE button
Selecting this button confirms and accepts all your entries for the new variable. The button is
inactive (greyed out) if your entries are incorrect or incomplete.
The new variable is automatically added to the corresponding declaration table.
NEW OFF button
Shrinks the dialog box back to its original size, hiding the new variable declaration fields again.
IEC 61131-3
This field displays all the available IEC information for the selected variable.
TO HEADER button
Copies all selected global variables to the header of the current POU.

Reference Manual

GX IEC Developer

3 - 48 The User Interface

3.15.2 How to automatically write global variables
... to one POU header
Select the variables in the Variable Selection window and click on the To Header button.
... to all POU headers
There are two ways to transfer global variables to all POU headers simultaneously:
Method 1: Extras menu - Declare Externals
ቢ In the global variables list field select the variables you wish to write to the headers of all
existing POUs.
ባ Select the Declare Externals option in the Extras menu.
A prompt is displayed asking you to confirm that you really wish to perform the operation.
If you confirm the selected global variables will then immediately be written to the headers of
all existing POUs.
Method 2: Activate the Autoextern function in the global variables list
The global variables list contains a column called Autoextern. Global variables activated in the
Autoextern column are automatically added to all existing and new POUs (programs and
function blocks only).

ቢ Double-click in the empty field.
This activates the Autoextern function, immediately writing the global variable to all PRG
and FB headers.
This function is only available when the Autoextern option in the Extras - Options - Editing Declaration Editor menu is enabled.
Difference between the two methods:
Declare Externals only writes the global variables to existing POU headers, not to the headers
of new POUs created later.
Variables for which Autoextern is activated are automatically and immediately written to new
POUs.

GX IEC Developer

Reference Manual

The User Interface 3 - 49

3.15.3 Deleting unused variables
You can delete all global variables that are not used in any POUs. However, please note that this
delete operation is only performed on the headers, the variables will still be contained in the list
of global variables. Variables used in the body are also not deleted in the headers.
There are two ways to delete these unused variables:
Method 1: Extras menu - Delete Externals
ቢ The Delete Externals dialog box is displayed in which you can specify whether you wish to
perform the deletion operation in all POUs and variables or just selected POUs and/or
specified variables.
Method 2: Disable the Autoextern function in the global variables list
ቢ Open the global variables list and disable the entry in the Autoextern column.
Difference between the two methods:
Let us assume you have activated Autoextern for two variables in the global variables list, which
means that these variables are now included in all existing headers, even though they are not
used in all bodies.
Delete Externals deletes these two variables from the headers of the POUs that have already
been created. However, as soon as you create a new POU the variables will automatically be
written to the header because the Autoextern function is still active for them.
When you disable Autoextern for the two variables in the global variables list the variables are
also removed from all existing headers. In addition to this, the variables are no longer added to
the headers of new POUs when they are created.

Reference Manual

GX IEC Developer

3 - 50 The User Interface

GX IEC Developer

Reference Manual

Projects and Objects 4 - 1

4

Projects and Objects
4.1

Projects
The project is the object at the top of the hierarchical structure used in GX IEC Developer. In IEC
61131.3 terms, a project is comparable with a resource. In GX IEC Developer it corresponds to
one PLC system.
A project consists of considerably more than just one file. When you create a new project, GX
IEC Developer creates a separate subdirectory with the name of the project. All the files used by
the project are always stored in this directory.

4.1.1

The automatically-generated project files
n

*.PRO Project (all objects except libraries)

n

*.BAK Backup of the file *.PRO

n

*.SAV Extra backup copy of the file *.BAK generated when a restore is performed
(© page 4-12 )

n

PLCDOKU ASCII PLC configuration files when printing (PLC_Parameter)

n

WORKSPACE.SYS Workspace settings (View - Save Workspace)

n

CUSTOM.SYS Graphic Macros (Tools - Custom)

n

LRUBOXES.SYS All the programming instructions used in the project (Last recently Used list
box in the Function Block Selection dialog box in the graphical editors)

n

SFC.OBJ Last program organisation unit created in the Sequential Function Chart language
(temporary file stored in a special format)

Note: During the compilation and data transfer processes GX IEC Developer generates a
number of temporary files that should not be edited or tampered with in any way. See the
Appendix for details.

4.1.2

Files with standard extensions
n
n
n
n
n
n
n
n
n
n

Reference Manual

*.ASC
*.EDM
*.SED
*.PRN
*.SLT
*.SAM
*.XLS
*.SUL
*.SCT
*.SCX

Import/Export File
Entry Data Monitor Settings
Setup for Entry Data Monitor
Print File
Status Latch Definitions
Sampling Trace Definitions
Excel File for Device Editor
User Library
Files for the Cross Reference data base
Automatic link of the SCT files to the SCX file when generating the
cross reference data base

GX IEC Developer

4 - 2 Projects and Objects

4.2

What are the components of a project?
Projects consist of Objects. The following are all objects in GX IEC Developer:
n
n
n
n
n
n

The libraries in the Library_Pool
The PLC parameters
The tasks in the Task_Pool
The data unit types in the DUT_Pool
The global variables
The program organisation units in the POU_Pool, consisting of headers and bodies

These objects are displayed in the Project Navigator window, which is automatically displayed
when you open a project. The project name is displayed as the first entry in this window.
The Project Navigator window is the ‘control centre’ or ‘starting point’ for all operations
performed on these objects. The relationships between the original objects are reflected in the
hierarchical structure of the Project Navigator tree.

4.3

The Project Navigator and Objects
The Project Navigator window

In the Navigator three different views can be selected via tabs: Project, Calltree, and Used by.
For details refer to section 3.4.

4.3.1

Library Pool
The following libraries contain the programming instructions:
n
n
n

Standard Library
Manufacturer Library
User Library

For more information on the library concept see page 4-6.

GX IEC Developer

Reference Manual

Projects and Objects 4 - 3

4.3.2

PLC Parameters
In the dialog box PLC parameter you set and store the following PLC system parameters:
n
n
n
n
n
n
n
n
n
n

Memory parameters
Latch operand range
Timers and Counters range
I/O configuration
Network link settings
PLC setup data
Special parameters
System variables
MiniNet settings
PLC CPU type selection

Note: See chapter 5 for details on configuring your system.

4.3.3

Task Pool
Within a project, the task is the highest level in the hierarchy. The task contains the executable
program organisation units, which are the subprograms that go to make up a project. Tasks can
be either event-triggered or executed at preset intervals. Tasks are also assigned priorities, which
determine the execution hierarchy when tasks are executed under the same conditions.

4.3.4

DUT Pool
Data unit types are structured data types consisting of collections of variables that can be of
different data types. Data unit types must be declared as global variables. In POU headers global
variables are referenced as VAR_EXTERNAL. Values can be assigned to the individual elements
(variables) of the data unit type in the body of the POU (© Chapter 6).

4.3.5

Global Variables
Global variables have fixed hardware addresses (absolute addresses) which refer to a specific
memory location for the variable in the CPU or a physical input or output point. Global variables
are declared for the entire project and can be referenced as VAR_EXTERNAL in the function
block and program POUs. They make it possible to exchange data between all the individual
subprograms that make up the project (© Chapter 6).

Reference Manual

GX IEC Developer

4 - 4 Projects and Objects

4.3.6

POU Pool
The sorting criteria for the listing of the POUs in the POU pool can be toggled. Three different
sorting criteria are available:
n
n
n

By name (alphabetically)
By type
By programming language (alphabetically)

Right-click on the POU pool to open the context menu and select Sorting Criteria. The Sort
Criteria Precedence dialog will be opened. In this dialog you can specify the precedence of
each sorting criteria via the Up and Down buttons.

All program organisation units (POUs) consist of a header and a body.
n

Header: The header contains the declarations of the Local Variables used in the POU.

n

Body :

The body contains the actual PLC program code of the POU.

The entries after the POU name specify the Class:
n

[PRG]

: Program

n

[FB]

: Function Block

n

[FUN:INT]: Function

The entry before the POU name specifies the compilation:
n

*

: The asterisk indicates that this POU has not been compiled.

The entries after ‘Body’ specify the programming language in which the PLC program in the
body is written:
n

: Instruction List

[LD]

: Ladder Diagram

n

[FBD]

: Function Block Diagram

n

[SFC]

: Sequential Function Chart

n

[MELSEC IL]

: MELSEC Instruction List

n

[ST]

: Structured Text

n

GX IEC Developer

[IL]

n

Action_Pool (SFC only) : All the POU’s Actions

Reference Manual

Projects and Objects 4 - 5

4.4

The Program Organisation Unit (POU)
The ‘actual’ PLC program code is stored in the body of each POU. However, this no longer
consists of just one PLC program with its own subroutines. In GX IEC Developer you use groups
of subprograms – the program organisation units. These self-contained subprograms are
administrated by tasks; together, they make up the complete PLC program.
A program organisation unit always consists of a header and a body. The header contains the
variables, which are only available within this POU. The body contains the executable PLC
program code.
Note: An introduction to the IEC 61131.3 standard and the basic principles of this new
programming concept is provided in the Beginner’s Manual in the chapter ‘The IEC 61131.3
Standard’. For tips on writing PLC sequential control programs in the various programming
languages (editors), please refer to Chapter 6 in this Reference Manual.

4.5

Preparation Before You Start Programming
Structured programming ...
To work really effectively with GX IEC Developer it is very important to analyse and plan the task
to be programmed in as much detail as possible before you actually begin to write the code.
Divide the entire machine process into small sub-processes, and treat each sub-process as an
independent unit. Implement each of these sub-processes as a Program Organisation Unit.
... and program management
Develop a sequential structure showing how the individual sub-processes are to be executed.
The program organisation units are called via Tasks (triggered either by events or at defined
intervals).
Global Variables
Draw up a list of your Global Variables, i.e. the variables whose hardware addresses must be
known, and which must be available to all the components of the program (e.g. inputs, outputs,
operands for possible later visual display of the process or operator guidance, analog inputs,
etc). The global variables should be declared before you start developing the program so that
each sub-program can access them. Of course, you can also add to the list in the course of
program development, if necessary.
Reusable subroutines
Program frequently-used processes as Functions or Function Blocks. The functions and
function blocks are stored in a library and can be used at any point in the project where they are
needed.
Note: To be able to call a function block you must create an ‘instance’ of it, in a process known
as ‘instancing’ or ‘instantiation’ (© Chapter 6) .
Data Unit Types
Create Data Unit Types for parts of the process where the same constellations of variables
must be accessed again and again. The creation of data unit types corresponds to the
instantiation of function blocks (© Chapter 6).
Graphical or textual based programming
The best editor type to use for your project, graphical or textual, depends on the type and scope
of the programming task. As a rule of thumb, Ladder Diagram and Function Block Diagram
are best for most applications because of their simple entry options and clear representation of
the program. These graphical editors make programming functions and function blocks
particularly simple. The Instruction List language allows more flexible programming, but it also
requires knowledge of the underlying syntax, for example for calling functions and function
blocks or for programming Arrays. The Sequential Function Chart and the Structured Text
languages are special cases; strictly speaking, they actually are no programming languages at all,
but rather structuring tools. It makes it very easy to see and follow the program sequence.

Reference Manual

GX IEC Developer

4 - 6 Projects and Objects

Individual logical sections of the program (sub-processes) can be programmed as macros
(© Chapter 6).

4.6

Library Concept
A distinction is made between the following three types of library:
n
n
n

Standard Library
Manufacturer Library
User Library

Standard Library
The Standard Library is for information purposes only. It contains the following elements:
n

DUT_Pool

n

: Irrelevant for programming purposes

Global_Vars : Irrelevant for programming purposes

n

POU_Pool

: The POU_Pool contains the standard IEC programming instructions supported
in GX IEC Developer. You can view the variable declarations in the header,
but you cannot edit them.

Note: The SLIB.LIB contains the contents of the Standard Library in packed format.
Manufacturer Library
The Manufacturer Library is also for information purposes only. It contains the following elements:
n

DUT_Pool

n

Global_Vars : Irrelevant for programming purposes

: Irrelevant for programming purposes

n

POU_Pool

: The POU_Pool contains all the ‘Adapted’ MELSEC programming instructions
with nomenclature modified for the IEC editors (© ‘Programming
Instructions’ in the appendix). You can view the variable declarations in the
header but you cannot edit them.

Note: The file MLIB.LIB contains the contents of the Manufacturer Library in packed format.

User Libraries
A user library gives you the possibility of creating functions and program segments which can be
used on a supra-project basis. The program segments are grouped in a library and can be used in
any project. Following updating, changes made to the library can be applied to other projects.
A user library can contain all the objects that are also available in a project: Global Variables List,
Data Unit Types, Arrays and Program Organisation Units. You can assign a password to protect
the know-how in the library.
The name of the user library file has the file extension SUL.
Note: The SC.INI initialisation file contains the LIBRARIES section, where you can make directory
settings (© chapter 2).

GX IEC Developer

Reference Manual

Projects and Objects 4 - 7

How to create a new user library
ቢ Select the Install/Create User Library command in the Edit menu.
The following dialog window is displayed:

ባ Click on the Browse Lib. button. The Select Library Path dialog window appears.
ቤ Choose the directory in which the library is to be stored.
ብ Enter a new name for the library.
ቦ Confirm with OK.
The entries are transferred to the Install/Create User Library dialog window, where they
can also be changed.
ቧ Confirm the library entries with OK.
The new library appears in the Navigator, along with the Standard Library and the
Manufacturer Library.
The Install/Create User Library dialog window

Library Path Directory in which the library file is to be created. This can be any directory,
although it is sensible to choose a central directory for the User Libraries.



Help Path Directory and file name for the Help file. A separate Help file can be created for
each User Library.



Browse LRU... A window is opened which displays the most recently used User Libraries.
You can select a library from this window.



Browse Lib...A window is opened for you to select a directory and enter a library file. A User
Library is given the file extension SUL.



Browse Help...A window is opened for you to select a directory and enter a Help file. A Help
file is given the file extension HLP.



Reference Manual

Library Name Descriptive name for the library, max. 32 characters.

View Help The Help file is opened.

GX IEC Developer

4 - 8 Projects and Objects

How to protect the User Library with a password
ቢ Select the desired User Library in the Navigator.
ባ Select the User Library - Change Password command in the Edit menu.
This opens a dialog window containing the following items:


Old Password When changing an existing password, the old password must first be
entered here. If you are assigning a password for the first time, you must skip this field by
pressing [ENTER].



New Password Entry of the new password.



Confirmation Repeat entry of the new password.

Note: A protected User Library can only be opened and edited if the password is known. As
long as the User Library is closed and the password is not known, it is impossible to make any
unauthorised changes. Only the header of the POU can be viewed, the body cannot be opened.
Remove/Delete User Library
Remove: The Remove User Library command removes the User Library selected in the Navigator
from the project. The library must be open at the time. The file is not deleted by this operation.
Delete: The Delete User Library command physically deletes the User Library selected in the
Navigator, along with the associated library file.
Update User Library
Every User Library can be used and modified in various projects. If, however, a change is made in
Project_1, this change is not available in Project_2 until the Update Libraries command has been
executed in the Edit menu.
Caution: It may, however, also be advisable not to update the library in a particular project.
Consequently, you should always take a look at the associated Help texts of the libraries before
performing an update!
Browse for User Libraries
If User Libraries which are not found in the specified path are accessed (e.g. open User Library,
export project), the Userlib not found dialog opens where you can browse for them. From this
dialog you can also create new User Libraries and save the information from the project to them.
This function does not depend on the current status of the User Libraries (opened, closed,
changed, not changed, password, no password).
Under the following conditions a new User Library has to be created:
ቢ When opening the User Library (transition from installed to opened status)
ባ When saving the user-library (transition from changed to opened status)
ቤ When exporting a project with user-libraries (no transition)
If such a condition is recognised, a dialog is opened where you either can:
ቢ Create a new User Library at the original place
ባ Browse for the User Library
ቤ Create the User Library at any proper place
ብ Cancel the new creation of the User Library

GX IEC Developer

Reference Manual

Projects and Objects 4 - 9

4.7

Working with Projects
How to Create a New Project
ቢ Select New in the Project menu. The dialog box PLC Parameter is displayed.
At this point, CPU Type
Selection is the only
active field.

ባ Select the CPU for which you are programming from the list box.
ቤ Confirm your selection with OK.
The dialog box New Project is displayed.
ብ Select a directory for your project or type in the path in the Project Path field. If you wish,
you can also enter a directory that does not yet exist; GX IEC Developer will then create it for
you automatically.
ቦ Enter the name of the project at the end of the project path.
The project name can be a maximum of 255 characters long
(Microsoft Windows standard for long file names).
The project name does not need an extension as it refers to a
directory and not a file.

ቧ Click on the Create button.
The program displays the Wizard dialog box.
ቨ Select the required project option and confirm with OK.
The program will then create the project database on the disk.

Reference Manual

GX IEC Developer

4 - 10 Projects and Objects

The project creation process is documented in an information box (loading the programming
instructions from the libraries, opening the project).
When it generates a new project GX IEC Developer doesn’t create a single file but a subdirectory
with the project name. This subdirectory contains all the files that make up the project. The two
libraries – the Standard Library and the Manufacturer Library – are always loaded with every
new project that is created. When you begin, they are displayed in the Project Navigator window
with the various pools, which are still ‘empty’.
The Wizard
The Wizard is a special tool. When the new project has been generated the following dialog appears.

Select the desired startup option for your project:


Ladder Diagram Creates a simple project consisting of one task and optionally a Sub task.
Each task contains one Ladder Diagram POU (Program Organisation Unit).



MELSEC IL Creates a simple project consisting of one task and optionally a Sub task. Each
task contains one MELSEC IL (MELSEC Instruction List) POU. You enter the MELSEC mode.
Only the programming language MELSEC IL is available in the project. IEC POUs can not be
added. DOS-MEDOC programs can be imported easily (see section 7.5).



Project Structure Starts the interactive Project Structure Builder Assistant. You are guided
through several steps, creating tasks and POUs depending on your selections,



Empty Project Does not use any assistance. Creates an empty project containing no tasks or
POUs.

Note: If you do not wish to use the Wizard’s support you can deactivate it by editing the
Wizard setting in the MMP400.INI file (© Chapter 2).

GX IEC Developer

Reference Manual

Projects and Objects 4 - 11

How to open an existing project
ቢ Select Open in the Project menu, or click on the corresponding tool in the Toolbar.
Tool for opening an existing project

The Open Project dialog box is displayed.
ባ Select the drive, the directory and the project name.
ቤ Click on the Open button.
Projects are easy to identify in the directory list – their path symbols are displayed in
yellow.
If the project was not stored properly because of a power failure or because it was not
closed correctly a ‘cracked’ yellow path symbol is displayed next to the project name.
Usually, such projects can be restored.

Note: Please note that you can only open and edit one project, in one Project Navigator
window. But you can start GX IEC Developer several times to open and edit more than one
project at a time.

How to recover a project
GX IEC Developer has a facility for recovering projects that were not closed properly because of
a power failure or some other problem. These projects are identified by a ”cracked” directory
path symbol in the Open Project dialog box.
ቢ Click on the ”cracked” directory symbol.
A dialog box is displayed with three options: Recover, Use Backup and Cancel.
Recover: This option restores all the project’s data so that nothing is lost. The system
restores the exact editing status of the project at the point the unplanned termination
happened.
Use Backup: Loads the status of the project as it was the last time you loaded it for editing.
All changes made between then and the unplanned termination are lost. An additional
backup copy of the project is generated and stored in the file *.SAV.
Cancel: Cancels the procedure and closes the dialog box.
ባ Click on the appropriate button.
Note:
When you create a new project the files *.PRO and *.BAK are created automatically. All editing
changes and entries you make are stored in the PRO file.
When you open an existing project that was closed correctly GX IEC Developer loads *.PRO and
creates *.BAK. Here too, all the entries and editing changes you make are stored in the PRO file.
The BAK file stores the status of the project at the point it was loaded.
As you can imagine, when you select Recover, the system loads the PRO file in which all the
editing changes up to the termination point are stored.
By the same token, selecting Use Backup loads the BAK file. This means that if you first created
the project in the editing session in which the termination occurred the BAK file will be empty!!!
If you loaded an existing project in the last editing session the BAK file contains the status of
the project from the point when you began the editing session. Whenever a *.BAK file is loaded
an automatic additional backup copy of the project is generated and stored in the file *.SAV.

Reference Manual

GX IEC Developer

4 - 12 Projects and Objects

How to open the SAV file
ቢ Open the File Manager.
ባ Create a new directory.
ቤ Copy the SAV file into this new directory.
ብ Rename the file *.SAV into *.PRO.
ቦ Open this PRO file in GX IEC Developer.

How to close a project
ቢ Select Close in the Project menu.
Or:
Close the Project Navigator window with the Close command in its control menu (key
combination §’), or by double-clicking on the control menu button.
A prompt will be displayed asking you if you wish to save the project. If object windows (e.g.
headers or bodies) with unsaved editing changes are open a separate prompt will be displayed
for each window.

How to Save a Project
ቢ Saving your project with the current name: Select Save in the Project menu, or click on the
corresponding tool in the Toolbar.
Tool for saving the current project

Saving under a new project name: Select Save As in the Project menu. Select the desired
subdirectory and assign a new project name.
When you save the project the backup file is updated automatically.

How to delete a project
ቢ In the Project menu open the Other submenu and select Delete.
The Delete Project dialog box is displayed.
ባ Select the drive, directory and project name.
GX IEC Developer projects are identified by a yellow path symbol next to the directory name.
ቤ Click on the Delete button.
Note: You cannot delete a project while it is open!

How to rename a project
ቢ In the Project menu open the Other submenu and select Rename.
The Rename Project dialog box is displayed.
ባ Select the drive, directory and project name.
GX IEC Developer projects are identified by a yellow path symbol next to the directory name.
ቤ Enter the new project name in the New Project Name field.
The project name can have a maximum of 8 characters. You can also enter the name of a
directory that does not yet exist, and GX IEC Developer will create it for you automatically.
ብ Click on the Rename button.
Note: You cannot rename a project while it is open.

GX IEC Developer

Reference Manual

Projects and Objects 4 - 13

How to copy a project
ቢ In the Project menu open the Other submenu and select Copy.
The Copy Project dialog box is displayed, with two list boxes.
ባ Select the drive, directory and name of the project to be copied in the left list box.
GX IEC Developer projects are identified by a yellow path symbol next to the directory name.
ቤ Creating a copy with the same name: Simply select the target drive and directory in the list
box on the right.
Creating a copy with a new name: Select the target drive and directory in the right hand list
box, and then enter a new name at the end of the path. The new project name can have a
maximum of 8 characters. You can also enter the name of a directory that does not yet exist;
GX IEC Developer will then create it for you automatically.
Overwriting an existing project with a copy: Select an existing project in the right hand list box.
ብ Click on the Copy button.
Note: You cannot copy or overwrite a project while it is open.
Please also have a look at the functions provided by the Import and Export commands in the
Project - Other menu (© Chapter 7).

How to back up a project
The command Extras - Backup Project packs the project files and stores them to a medium on
the selected drive. External data media such as floppy disks are supported. If the resulting
project file is larger than the capacity of the disks it is automatically split across the necessary
number of disks.
ቢ Select Backup Project in the Extras menu. The following dialog box is displayed.

ባ Select the format for the backup operation:


Packed project database File format *.PCD: The complete database (already compiled)
and the libraries will be packed.



Packed export format File format: *.PCE: The project data (without compilation, without
libraries) will be exported and packed. When restoring a PCE file you have to compile the
project again.

ቤ Select the target drive and directory, then enter a name for the target file.
ብ Click on the OK button to pack the project and copy it to the selected drive.
ቦ If the target drive is a floppy disk drive you will be prompted to insert the first disk. If the
packed file is too large to fit on the disk it will be automatically split across the necessary
number of disks. You will be prompted to change disks when necessary.

Reference Manual

GX IEC Developer

4 - 14 Projects and Objects

Note: The Backup Project command can only be executed for the project currently opened.
With the Export function in the Project - Other menu the project data are exported into an
ASCII file only, without being compiled or split across the necessary number of disks.

How to restore a project
The command Extras - Restore Project is used to restore a backed up project from a packed
file. After being unpacked the project is automatically opened.
ቢ In the Extras menu select Project Restore.
The following dialog box is displayed.

ባ In the upper line select the PCD or PCE file which you wish to unpack and open.
ቤ In the lower line select the target drive and directory and enter a name for the target project.
ብ Click on the OK button to unpack and open the project.
Note: The name for the target project is not a file, but a directory.

How to reorganize a project database
The command Tools - Reorganize Database... is used to reorganize a project database. This
function fixes possible defragmentation problems in GX IEC Developer 32-bit *.pro project files
and repairs damaged database records. The menu item is available only if no project is opened.
ቢ Select Tools - Reorganize Database....
A standard file open dialog is displayed.
ባ Select the desired *.pro file to be reorganized and click on the Open button. The project file
is reorganized while the progress status is indicated.

GX IEC Developer

Reference Manual

Projects and Objects 4 - 15

4.8

Working with Objects
How to open objects
ቢ Double-click on the object in the Project Navigator window.
Or:
Select the object in the Navigator and then click on Open in the Object menu.
The window or dialog box of the selected object will then be opened.
Note: There are two possible responses when you double-click on a POU name, depending on
the settings in the MMP400.INI file and in the menu Extras - Options - Zoom Header/Body Navigator Zoom (© Chapter 2).
- Show/hide header and body in the Project Navigator window
- Open Header and body

How to close objects
ቢ Close the object window.
ባ Before the operation is executed a prompt will be displayed asking you if you wish to save
any editing changes. Click on Yes if you wish to save the changes.
Note: The various different ways of closing windows are explained in Chapter 3.

How to create new objects
ቢ In the Toolbar, select the tool for the object you wish to create.
Or:
Select New in the Object menu, then select the desired object type from the pop-up list
displayed (POU, DUT, Task or Action).
ባ Make the necessary entries in the dialog box. Enter the name of the object. In the case of
program organisation units you must also specify the POU’s class (Program, Function Block or
Function) and the programming language. In the case of actions you must select the
programming language.
The newly-created object is displayed in the Project Navigator window. You can now open the
object to edit it, if necessary.

How to save objects
ቢ Select the window of the object you wish to save.
ባ Select Save in the Object menu.
Or:
Press the following key combination:
Save §S

How to rename objects
ቢ Select the object to be renamed in the Project Navigator window.
ባ Select Rename in the Object menu.
ቤ Enter the new name in the dialog box.
The new name of the object will then be displayed in the Project Navigator window.
Note: You can only rename closed objects.

Reference Manual

GX IEC Developer

4 - 16 Projects and Objects

How to cut, copy or delete objects
ቢ In the Project Navigator window, select the object that you wish to cut, copy or delete.
ባ Select the appropriate command in the Edit menu.
Or:
Press the corresponding key combination:
Cut
§X
Copy
§C
Delete
µ
Note: The Cut operation deletes the data from its original position and stores it in the clipboard.
The Copy operation copies the data to the clipboard without changing it in its original location.
The Delete operation deletes the data from its present location without copying it to the
clipboard. This means that any data that was in the clipboard prior to the delete operation
remains unchanged.
Objects can only be deleted if the corresponding object windows are closed (e.g. header and
body in the case of POUs).

How to paste objects
ቢ Activate the Project Navigator window.
ባ Select Paste in the Edit menu.
Or:
Press the following key combination:
Paste
§V
Note: Please note that the system does not prompt you for a new name before inserting the
data. Objects in the clipboard are inserted in the new location with their original names. You
must then rename the new objects manually with Edit - Rename, and it may also be necessary
to perform editing to eliminate double variable declarations (in the case of POUs).
The Copy and Paste functions can also be used to copy and paste objects between projects,
not just within the current project.

How to copy objects from the current project to another project
ቢ Select the object or objects to be copied in the Project Navigator window.
ባ Select Copy in the Edit menu.
Or:
Press the following key combination:
Copy
§C
A copy of the data is now in the clipboard.
ቤ Close the current project, then open the project into which you wish to copy the objects.
ብ Activate the Project Navigator window.
ቦ Select Paste in the Edit menu.
Or:
Press the following key combination:
Paste
§V
The data from the clipboard are inserted in the Project Navigator window.
Note: You can also exchange objects between projects with the Import and Export functions
(Project - Other - Export/Import).

GX IEC Developer

Reference Manual

Projects and Objects 4 - 17

How to enter comments
ቢ In the Project Navigator window, select the object for which you wish to enter a comment.
Or:
Activate the object window.
ባ Select Comment in the Object menu.
ቤ Type your comment text in the left field.

How to copy, cut and paste comments
ቢ Select the text to copy or cut.
You can use the standard Windows mouse operations and key combinations for selecting text.
ባ Click on the Cut, Copy or Paste button.
Note: You can also use the standard Windows key combinations for these operations:
Cut
§X
Copy
§C
Paste
§V

How to view the object information
ቢ In the Project Navigator window, select the object whose information you wish to view.
Or:
Activate the corresponding object window.
ባ Select Information in the Object menu.
Or:
Press the key combination ¦«.
A dialog box is opened showing attributes of the selected object.
General Options
Name: Name of the selected object
Size: Size of the selected object in bytes
Type: Type of the selected object
Last Change: Data and time of the last editing
change
Security Level: Current security level
Read Access: Read access for lower security levels
Comment: Comment text

Additional Options for Body Objects
Language: Programming language

Reference Manual

GX IEC Developer

4 - 18 Projects and Objects

ATTENTION: The system will allow you to change the programming language of a POU, but if
you do this you will lose all the code in the body! A message will be diplayed.
Additional Options for Functions
Result Type: Result data type (displayed when you
change the program class)
Use with EN/ENO: If you change the program class
to Function this field allows you to specify whether
the function is to have a Boolean input and output.
Type: Program class
Language: Programming language used in the body

Additional options for Function Blocks
Macrocode: Macrocode execution of the function
block (© page 6-50)
MC-MCR: MC-MCR execution of the function block
(© page 6-50)
Use with EN/ENO: If you change the program class
to FB (Function Block) this field allows you to specify
whether the function block is to have a Boolean input
and output.
Type: Program class
Language: Programming language used in the body

GX IEC Developer

Reference Manual

Projects and Objects 4 - 19

Additional Options for Task Objects
Note: Task attributes can only be set in this dialog box.
Event: Event-triggered
Interval: Interval-trigg ered
Priority: Priority level of the task
Timer/Output Control: MC-MCR execution of the
task (© page 6-2 )

How to display an object’s Call Tree (subordinate objects)
ቢ Select the object whose Call Tree you wish to display.
ባ In the Object menu, select Show and then select Call Tree from the submenu displayed.
An information box is opened showing all the objects used in the selected object.
n

Task Call Tree: All associated POUs and all the global variables used in the POUs

n

POU, Body and Header Call Trees: All function block instances and all global variables

How to display an object’s Reference List (superordinate objects)
ቢ Select the object whose Reference List you wish to display.
ባ In the Object menu, select Show and then select Reference List from the submenu
displayed.
An information box is opened showing all the objects in which the selected object is used.
n

n

Reference Manual

Function Block Reference List: The headers in which the instances of the function block were
generated
POU Reference List: The associated task

GX IEC Developer

4 - 20 Projects and Objects

4.9

Protecting Your Data
GX IEC Developer has a eight-level data security system. You can assign a different password to
each level, and you can assign security levels to both the entire project and each individual
object within the project. The security level assigned to any object will be inherited to all its child
objects provided their security level is not higher.
For example, if you assign a security level of 5 to the project you can edit all objects with security
levels 0 through five. Objects with security levels 6 and 7 are not editable, but you can view their
contents. The names of protected objects are displayed in grey in the Project Navigator window.
POUs that are both read and write protected also do not allow you to branch into their headers
and bodies in the Project Navigator window.

How to assign security level passwords
ቢ Select Change Passwords in the Project menu.
ባ Select the security level to which you wish to assign a password.
ቤ Enter the current password in the Old Password field. If you have not yet entered a
password for this level, simply leave this field empty.
ብ Enter the new password in the New Password field.
As an additional security measure asterisks are displayed on
the screen instead of the characters you enter.

ቦ Confirm your entry by re-entering the same new password in the Re-enter Password field.
ቧ Click on the Change button to enter the password.
A message will be displayed telling you whether the system has accepted the old and new
passwords.

How to change the project’s security level
ቢ Select Change Security Level in the Project menu.
ባ Select the desired security level.
ቤ Enter the valid password for this security level in the Password field.
An error message will be displayed if you enter the password incorrectly.

GX IEC Developer

Reference Manual

Projects and Objects 4 - 21

How to assign read and write protection to objects
ቢ Select the object to be protected in the Project Navigator window.
ባ Select Information in the Object menu.
Or:
Press the key combination ¦«.
The Object Information dialog box is displayed.

ቤ Click on the desired security level.
ብ Write protection: Click on a security level higher than the current level in order to protect the
object against unauthorised editing.
ቦ Read protection: Deactivate the Allow Read Access For Lower Levels check box to
prevent read access to the object.
Note: If the project has security level 5 and the object has already been assigned security level
6 you cannot change the security level of the object in this dialog box. Security levels that
cannot be selected are displayed in light grey. To change the security level of such objects you
must first change the level of the project; for instance, in this example, you would have to
change the project security level to 6. This is only possible if you know the password of this
security level, of course.
Action: Check and enter PLC keyword for access to the PLC CPU.

How to protect the PLC program
Access to the PLC CPU can be restricted by entering a PLC keyword to prevent unauthorised
persons from transferring programs from the CPU.
The user is prompted to enter the password once before every Online operation. The password
is also checked internally before execution of every subsequent Online operation.
ቢ In the Online menu select the PLC keyword command, then select Current, New or Delete.
ባ Enter the appropriate PLC keywords in the corresponding fields. You can move from field to
field with the [TAB] key. For security, all the characters you enter are displayed as asterisks
on the screen.
ቤ Confirm your entries with OK.
Meaning of the fields:



New If an old PLC keyword has already been entered you must first enter it for confirmation.
Then enter the new PLC keyword in the next field, after which you must enter it again for
confirmation in the last field.



Reference Manual

Current Enter current PLC keyword for access to the Online functions.

Delete Delete the current PLC keyword for the PLC CPU.

GX IEC Developer

4 - 22 Projects and Objects

4.10

Printing Out Project Data
How to configure the printer
ቢ Select Printer Setup in the Project menu. This opens the Windows Print Setup dialog box
showing the current default printer and its parameters. The changes and settings you can
make in this dialog box depend on the printer connected to your computer.
Note: For full details, consult the Windows User’s Guide and your printer manual.

How to print an object
ቢ Select any obect in the Project Navigator or open the window of the object to be printed.
ባ Select Print Preview in the Object menu to open the print preview display. The display gives
you quite a precise preview of what the printout will look like. If the printout includes more
than one page, you can navigate through the pages via the Page buttons. You can Zoom In
(increase) or Zoom Out (decrease) the view size via the Zoom buttons. You can cancel
printing by clicking the Close button.
ቤ Click the Print button.
Or:
Press the key combination ¦p.
The Print dialog box is displayed.
ብ Select the appropriate print options.
Selecting the Setup button opens the Print Setup dialog box, in which you can set the
parameters of the default printer or select another printer.
ቦ Start the printout with the OK button.
If you do not need to preview the printout, you can directly print any selected or opened object.
In the Object menu select Print.

How to print project data
ቢ Select Print Preview in the Project menu to open the print preview display. The display
gives you quite a precise preview of what the printout will look like. If the printout includes
more than one page, you can navigate through the pages via the Page buttons. You can
Zoom In (increase) or Zoom Out (decrease) the view size via the Zoom buttons. You can
cancel printing by clicking the Close button.
ባ Click the Print button.
Or:
Press the key combination ¦p.
The Print dialog box is displayed.
ቤ Select the appropriate print options.
Selecting the Setup button opens the Print Setup dialog box, in which you can set the
parameters of the default printer or select another printer.
ብ Start the printout with the OK button.
If you do not need to preview the printout, you can directly print any selected or opened object.
In the Project menu select Print.

GX IEC Developer

Reference Manual

Projects and Objects 4 - 23

4.10.1 Print options for project data
The content and layout of the project data printout can be customised extensively. Different
print options settings can be saved as profiles. In the Project menu select Print Options to
open the Change Configuration dialog.

Dialog items

Object Select whether only the current Project Tree or the currently Selected Items
according to the current profile are printed.


Current Profile Type or select (from the combo box) the name of the profile that you want
to load, save, set as default, or delete.



Loaded Profile Displays the currently loaded profile. If this field remains blank, the loaded
profile was changed and and not yet saved.



Default Profile Displays the default profile for every printout. The default profile can be
specified via the Set Default button.



Watch Indicates whether any property setting of the loaded profile was changed, but the
current profile is not saved. In this case the Loaded Profile field remains blank.



Save If any property setting of the loaded profile was changed, this button becomes active.
Click the Save button to save the current profile under the name entered in the Current
Profile box.



Delete Deletes the profile entered in the Current Profile box. If the currently entered profile
does not exist, an error message is returned.



Set Default Sets the profile entered in the Current Profile box to the default profile. If the
currently entered profile does not exist, an error message is returned.



Load Loads the profile entered in the Current Profile box. The loaded profile is indicated in
the Loaded Profile box.



Properties... Opens the Document Configuration dialog where you can change the property
settings of the loaded profile (for details see below). If any property setting of the loaded
profile was changed, this button becomes active and the Loaded Profile box is cleared.



List... Opens the Checked Properties List where the specified property settings are
summarized in a list.

Document Configuration
In the Document Configuration dialog all property settings of the loaded profile for the project
data printout can be specified.

Reference Manual

GX IEC Developer

4 - 24 Projects and Objects

How to open the Document Configuration dialog:
ቢ In the Project menu select Print Options.... to open the Change Configuration dialog.
ባ In the Change Configuration dialog click on the Properties... button.
The Document Configuration dialog opens:

The Document Configuration dialog includes the following property sheet tabs:
Scope
Selects the object class to be documented. This configured scope is related primarily with the
selected objects in the main view.
The following objects can be selected for the printout:
n
n
n
n
n
n

Cover Page
Table of Contents
Project Tree
Cross Reference
Global Variable List
POUs (FBD, IL/MELSEC IL, LD, SFC, ST)

If FBD, IL, SFC and/or LD are checked, only the selected objects of this type will be documented.
The scope defined by each selection may be restricted through the detailed configuration of the
items. The items may be configured via the other tabs.
Cross Reference
The following objects can be selected for the printout:
n
n

GX IEC Developer

Call Tree
Global Variables
The following selections are posible if Global Variables is selected:
a) Used Read/Write variables (the cross reference for used read/write variables can be
documented either for variable names or all adresses or a user-specified address range).
b) External declarations

Reference Manual

Projects and Objects 4 - 25

Page Numbers
The following options can be selected for the printout:
n

n

Show page number in cross reference
(Variable page reference)
Show page number in split reference

SFC
The following objects can be selected for the printout:
n
n
n
n
n
n
n

Main Network
Macros
Steps
Transitions
Actions
Table of Content
More steps/actions/transitions on one sheet

Left Footer
The following fields can be edited directly for the printout:
n
n

Rev, Change, Date, Name
Date, Drawn, Appr., Rel.

The captions for the entry fields can be edited by clicking on the respective caption button.
Right Footer
Enter any information into the blank entry fields.
General/Project Tree
The following options can be selected for the printout:
n
n
n

Reference Manual

General: Zoom condensed or normal
Project Tree: Actual State or Expanded
LD and FBD: Not separated input/output pin directly connected.
If activated: After the calculation of the layout in FBD and LD an additional calculation will
determine all functions and function blocks which have formal input or output pins (only
input or output elements directly connected). This option avoids a page break within the
function and ensures that the input or output will print the function and function block with
their input or output elements on the next page.

GX IEC Developer

4 - 26 Projects and Objects

Frame Logos
You can specify several bitmap graphics files (*.bmp) and a title for the printout appearing on
every page in the header and footer:
n

n

Header: Logo Left, Logo Right, Title
Enter or browse for a bitmap graphics file to be printed.
Footer: Logo Bottom
Enter or browse for a bitmap graphics file to be printed.

Cover Page
You can specify several text entries and a logo (*.bmp) for the printout appearing on the cover page:
n
n

Logo: Enter or browse for a bitmap graphics file (*.bmp) to be printed.
Project, Comment, Prj. Number, Prj. Manager, PLC Type: Enter text for the respective entry fields.

POUs
The following options can be selected for the printout:
n

n

n

n
n
n

GX IEC Developer

Header
If selected, the POU header for each selected POU will be printed.
Local Cross Reference
If selected the local reference for each selected POU will be printed.
Body
If selected, the following objects can be selected from the section Networks: Network Cross
Reference, Network Variable Lists, Cross ref./var. list after network
Either Multiple object on a page or Each object on a page
Use local variables in Cross Reference
Show header occurences in Cross Reference

Reference Manual

Projects and Objects 4 - 27

4.11

Cross Reference
The Cross Reference function generates a database listing of all the project variables.
Relationships become clearer, it is easier to find certain variables, and unused variables can be
identified.
Default settings in the MMP400.INI initialisation file
[CrossReference]
GenerateSCT=TRUE
TRUE: cross reference function enabled.
FALSE: cross reference function disabled.
Cross reference options
In the Extras - Options - Cross reference menu you can set the cross reference options.



Generate *.SCT files while checking a project Activates generation of the SCT files during
project checks



Automatically link the *.SCT files to the *.SCX file after ‘Rebuild All’Activates automatic
linking of the SCT files to the SCX file after compiling the project



Automatically link the *.SCT files to the .SCX file after ‘Build’ Activates automatic
linking of the SCT files to the SCX file after building the project

To create a cross reference database
ቢ Compile the entire project.
ባ In the Project menu choose the command Make Cross Reference.
The program now compiles all the details required for the cross reference database. The
procedure is documented in the status window Cross Reference Linker. The time needed
for this procedure depends on the project length.

Reference Manual

GX IEC Developer

4 - 28 Projects and Objects

ቤ Choose Browse in the Project menu.
The Browser dialog box is presented, prompting you to enter the search criteria.

Query


Variable name



Namespace Object name; e.g. Program Organisation Unit, Global Variable List



Datatype e.g. BOOL, INT



Scope Class; e.g. VAR, VAR_GLOBAL



Address parameter Variable address



Button: Search Starts the search. The result of the search is presented in the windows.



hits Number of matches found

Search result in window
All records that have been found are listed alphabetically.

Declares/References
Depending on the element that is marked in the left-hand window after a search, further details
are listed in the right-hand window and in the Variable Info List. You can set further search
filters for these details.

Filters



GX IEC Developer

Namespace Object name
Access Tells you how the variable is accessed in the projects

Reference Manual

Projects and Objects 4 - 29

Search result in window


Declaration Program organisation units in which the variable was declared



References Program organisation units in which the variable was inserted

Search result in the Variable Info List



Type Data type



Scope Class; e.g. VAR, VAR_GLOBAL



Access Access type; e.g. Read, Write, Read and Write



Reference Manual

Name Name of variable

Editor Programming language, network number in editor

GX IEC Developer

4 - 30 Projects and Objects

GX IEC Developer

Reference Manual

PLC Parameters 5 - 1

5

PLC Parameters
The PLC_Parameter command in the Project Navigator provides options for configuring your
system or changing the PLC type you are programming for. Clicking on the CPU type selection
button activates the CPU selection list in the box on the right, and the buttons on the left are
greyed to indicate that they are temporarily deactivted. Clicking on the CPU type button again
deactivates the list box and reactivates the other buttons.
The default settings produce trouble-free program performance for most applications. If you are
using a network you must configure it with PLC_Parameter before starting work, however. If
the configuration parameter settings lead to problems in your project, GX IEC Developer will
display an explanatory warning message.
Note: The PLC parameters are set automatically for the PLC type you select. Some of the
parameters explained below are not relevant for all PLC types, and they are thus not displayed
when some specific PLC types are selected.

Reference Manual

GX IEC Developer

5 - 2 PLC Parameters

5.1

Memory Parameters

5.1.1

Memory Parameters (MELSEC A/FX)
This dialog box contains all the settings for the assignment and allocation of memory. In
addition, you can also enable or disable Status Latch and Sampling Trace.





Symbolic data Displays the number of steps required in the controller for symbolic
information. This field is refreshed only after a symbolic download.



Sub sequence Allocation of SUB program sequence memory
1 step = 2 bytes
The program checks the maximum value automatically. After compilation the memory
actually required is shown in parentheses after this entry.



File register Allocation of memory for the file registers
The available memory depends on the type of memory cassette installed.



Comment space Not used
This option is reserved for future enhancements.



SFC area Allocation of memory for microcomputer programs
This option is only relevant for Sequential Function Chart programs for the PLC CPUs of the
AnN series. The memory for these programs must be allocated in steps of 2 kByte.



Sub micro Not used
This option is reserved for future enhancements.



Link parameter Displays the number of steps reqired in the controller for the link settings.



GX IEC Developer

Main sequence Allocation of MAIN program sequence memory
1 step = 2 bytes
The program checks the maximum value automatically. After compilation the memory
actually required is shown in parentheses after this entry.

Status Latch Devices for Status Latch (only for AnN)
Data Memory: All devices without File registers
File register:
File registers

Reference Manual

PLC Parameters 5 - 3



Sampling Trace Enables or disables Sampling Trace. If Sampling Trace is enabled, additional
memory in the controller is reserved.
Valid only for AnN (no A1N), AnS, and AnSH.



Used memory Total memory used by the current project.

Note: The Status Latch and Sampling Trace are only enabled for AnN controllers. In all other
controller series these parameters are edited directly with the Debug menu functions.

5.1.2

Memory Parameters (MELSEC Q/QnA)
In addition to showing the program size parameters for the selected CPU this dialog box is also
used to define the number of file registers you wish to use.

Program Size

Maximum Shows the maximum program size memory capacity in program steps.


Used Shows the amount of memory used by the program in program steps. This value is
only displayed after the project has been compiled.

File Register
If you wish to use file registers in Q/QnA series CPUs you have to define the number you wish to
use here first.


Amount Specify the number of file registers you wish to use (units: k points). The Q/QnA
CPU can handle a maximum of 1,024 addresses (i.e. 1MB). However, since a few addresses
are also used for making the file registers available you can only actually use a maximum of
1,018 addresses.



Drive Specify the number of the drive corresponding to the external memory card you wish
to use for the file registers. Valid entries: Drive numbers 1-4.
Drive 1: RAM in the card in the first slot
Drive 2: ROM in the card in the first slot (QnA only)
Drive 3: RAM in the card in the second slot
Drive 4: ROM in the card in the second slot (QnA only)

Note: File registers can not be created in the flash card ROM of a Q CPU under GX IEC Developer.

Reference Manual

GX IEC Developer

5 - 4 PLC Parameters

5.2

Latch Ranges
The PLC Parameter settings include a check mechanism. If a setting in the System Variables
overlaps with the corresponding setting in the Latch Range, an overlap warning will be
displayed. You can ignore this warning and continue or modify the settings.

5.2.1

Latch Ranges (MELSEC A)
This dialog box includes all the settings available for the division and allocation of the retentive,
battery-powered memory ranges. The data in these ranges is then stored in the event of a
power failure or a system reset. Please note that the settings you make here have nothing to do
with the Status Latch settings in the Debug menu!

The values for parameters followed by an H in parentheses (H) must
be entered in hexadecimal format.





Timers Device range for the 10 ms and 100 ms timers



Counters Counter device range



Data/Link Registers Register device range



Extended Timers Device range for extended timers



GX IEC Developer

Latch Relays / Link Relays Device range for the memory-resident latch and link relays. The
parameter values must be entered in hexadecimal format.

Extended Counters Device range for extended counters

Reference Manual

PLC Parameters 5 - 5

5.3

Device Settings

5.3.1

Device Settings (MELSEC Q/QnA)
This dialog box is used to define the devices to be used in the project. You can also specify
whether the latch operation is to be performed or not for the non-volatile device ranges with
battery backup.

The following table shows the correspondences between the devices in the A series and the
Q/QnA series:
MELSEC A Devices
Accumulators A0 and A1
Link registers B
Counters C
Data registers D0 - D8191
Special registers D9000 - D9255
Annunciators F
Hexadecimal constants H
Interrupt pointers I
Constants K
Latch relays L0 - L8191
Internal Relays M0 - M8191
Special relays M9000 - M9255
Nesting N
Pointers P
File registers R
Step relays S0 - S8191
Timers T (low-speed 100ms)
Timer T (high-speed 10ms)
Accumulator (retentative) timers T
Index registers V, V1, V2, .....
Link registers W
Input relays X
Output relays Y
Index registers Z, Z1, Z2, ...

Reference Manual

MELSEC Q/QnA Devices
Diagnostics link registers SD718 and SD719

Diagnostics link registers SD1000 - SD1255

Diagnostics link relays SM1000 - SM1255

Accumulator timers ST
Index registers Z7, Z8, Z9 ...

Index registers Z0, Z1, Z2, ...

GX IEC Developer

5 - 6 PLC Parameters

RAD
Input format (10 = decimal, 16 = hexadecimal)
Devices
Enter the number of devices you wish to use in your project in this column. The device types
with no entry fields have a fixed range which cannot be changed by the user:
-

Input relays X = 8K
Output relays Y = 8K
Diagnostics link relays SB = 2K
Step relays S = 8K
Diagnostics link registers SW = 2K



Maximum Input Limits
Maximum value for bit devices: 32K address points
Maximum number of all bit devices: 64K address points
Maximum total number of devices: 29K words



Number of bits per word/Kword
1 word = 16 bits
1Kword = 1,024 words = 16,384 bits



Number of bits per address
X, Y, M, L, B, F, SB, V, S : 1 address = 1 bit
D, W, SW: 1 address = 16 bits = 1 word
T, ST, C: 1 address = 18 bits = 1 word + 2 bits

Enable C/L Key
These fields are used to specify the device ranges for which the Latch Clear operation can be
performed.
Disable C/L Key
These fields are used to specify the device ranges for which the Latch Clear operation cannot be
performed.

GX IEC Developer

Reference Manual

PLC Parameters 5 - 7

5.4

Timer / Counter Configuration

5.4.1

Timer-/Counter Configuration (MELSEC A)





Watchdog Timer Setting Time value in ms for the Watchdog Timer



Interrupt Counter Head No Device head numbers for the counters connected to the
active interrupts.



Start Address (Extended Timers) ! Only relevant for AnA/AnU CPUs !
This field is used to set the starting addresses of the extended timers. You can only enter
values divisible by 16.



Range Settings ! Only relevant for AnA/AnU CPUs !
Number of extended timers and counters.



Init Device Timer ! Only relevant for AnA/AnU CPUs !
Register type and head number (start address) of the setpoint value registers used for the
extended timers (© Chapter 6).



Reference Manual

Start Address (Normal Timers) This field is used to set the device head numbers (start
addresses) for the timers. You can only enter values divisible by 8.

Init Device Counter ! Only relevant for AnA/AnU CPUs !
Register type and head number (start address) of the setpoint value registers for the
extended counters (© Chapter 6).

GX IEC Developer

5 - 8 PLC Parameters

5.5

I/O Configuration

5.5.1

I/O Configuration (MELSEC A)
All the modules, their slot numbers and I/O address number ranges are entered in this dialog
box. A PLC system can consist of up to 8 base units with 8 slots each, thus providing up to a
maximum of 64 slot numbers.
Entering the configuration data is particularly important for:
n

n

AnA and AnU systems. With these systems certain commands for specific special function
modules can only be executed if the configuration has been explicitly defined.
Systems for which address ranges different from the current configuration need to be
defined to reserve addresses for future expansions.




I/O Type Module type: Input, Output or Special Function Module



I/O Range Number of addresses allocated in the base unit



GX IEC Developer

I/O Slot Number of the base unit slot in which the module is installed

Module Type List of the MITSUBISHI modules that can be used. Depends on the settings
made in I/O Type and I/O Range.

Reference Manual

PLC Parameters 5 - 9

5.5.2

I/O Configuration (MELSEC A2C)
The A2C is configured in MINI NET mode. You can install a maximum of 14 stations in the A2C
network. The station numbers to be allocated depend on the address numbers of the modules
used in the configuration.


Last station number Enter the last station number actually used in this field. A module with
32 addresses occupies 4 station numbers.

Online Mode
The Online Mode parameter defines the CPUs operating mode.


Automatic return set After a communications error in the network operation is resumed
automatically as soon as the module is ready.



Automatic return not set After a communications error in the network communication
remains interrupted until a reset has been executed.



Stop communication during error Network communications are stopped when an error
occurs.



Number The station number



Station Starting address of the station. The calculation of the number must be performed
by the user. The first address is always station number 1. For example, you must add 4
station numbers for each module occupying 32 addresses; the starting address for module 2
would thus be 5.

Protocol

Mini MINI NET protocol, normally used in most situations.


Reference Manual

Freerun If you are using the AJ35PTF RS232 module select the Freerun protocol to transfer
freely-defined protocols (texts).

GX IEC Developer

5 - 10 PLC Parameters

5.5.3

I/O Configuration (MELSEC QnA)
This dialog box is used to enter all the modules and extension units installed in the system.

I/O Config

Slot List All slots (max. 64)


Slot Selected slot



Type Input module, output module, special function module or spare slot



Items Number of addresses occupied by the slot



1stXY Starting address of the module in units of 16 addresses



Type Name List of supported MITSUBISHI modules

Base Settings

Extension List 1 base unit and up to a maximum of 7 extension units



Power Supply Designation of the power supply



GX IEC Developer

Base Name Designation of the base unit
Extension Cable Designation of the extension cable

Reference Manual

PLC Parameters 5 - 11

5.5.4

I/O Configuration (MELSEC Q)
This dialog box is used to enter all the modules and extension units installed in the system.

I/O Configuration

Slot List All slots (max. 64)


Slot Selected slot



Type Input module, output module, special function module or spare slot



Items Number of addresses occupied by the slot



1stXY Starting address of the module in units of 16 addresses



Type Name List of supported MITSUBISHI modules

Base Settings

Base Name Designation of the base unit



Reference Manual

Power Supply Designation of the power supply
Extension Cable Designation of the extension cable

GX IEC Developer

5 - 12 PLC Parameters

Switch setting
This button opens the following dialog:



Switch 1 – 5 Settings for switching operations. Device range: 0000h – FFFFh.



Clear All Clears all defined switch settings.



Clear Slot Clears the switch settings only for the selected slot.

Detailled setting
This button opens the following dialog:




Operation mode on error Select whether to stop or continue the operation in case of an
error.



5.6

Output mode on error Select whether to clear or hold the output value in case of an error.

I/O response time Select the response time after which the I/O values have reached a valid
value.

Default Configuration
Clicking on this button returns the PLC configuration back to the default values. Use with
caution, as any settings you may have made will then be lost!

GX IEC Developer

Reference Manual

PLC Parameters 5 - 13

5.7

MELSECNET/Ethernet
The MELSECNET/Ethernet settings define the hardware, communications addresses and paths in
a network. The dialogs differ depending on the selected CPU module. The FX family CPUs do not
support network communications. For details refer to the manuals of the network modules.

5.7.1

A series
GX IEC Developer supports MELSECNET/10 and MELSECNET (II) connections to the AnU CPU
and A2US CPU modules.
MELSECNET/10




Head I/O No. Enter the first I/O number for the network module in hexadecimal format.



Network No. Enter the network number for MELSECNET/10.



Refresh Opens a dialog to enter and edit the refresh parameters of the network module for
the MELSEC network.



Specific Opens a dialog to enter and edit the specific station parameters.



Effective Module No. Enter the number of the defined module to be effective.



Transfer Opens a dialog to enter and edit the transfer parameters for communications
among the network modules.



Reference Manual

Module No.1... 4 Here you select the connection type for the network module.

Routing Opens a dialog to enter and edit the routing parameters. This dialog is valid for
Ethernet modules too. The routing parameters allow to specify network numbers of Ethernet
modules as relay networks.

GX IEC Developer

5 - 14 PLC Parameters

MELSECNET (II)





Net Mode... Select the desired mode.



Station list Lists all specified local or remote stations and their address ranges used.



Add Local-Station Opens a dialog where local station parameters can be specified, and adds
the specified station to the station list.
Value ranges:
B: 0 – 3FF hex. in steps of 16 bits
(entry will be rounded down to a multiple of 16).
W: 0 – 3FF hex. in steps of 1 word.
X, Y: 0 – 3FF hex. in steps of 16 bits



Add Remote-Station Opens a dialog where remote station parameters can be specified, and
adds the specified station to the station list.
Value ranges:
B: 0 – 3FF hex. in steps of 16 bits
(entry will be rounded down to a multiple of 16).
W: 0 – 3FF hex. in steps of 1 word.
X, Y: 0 – 3FF hex. in steps of 16 bits



Change Values Opens a dialog where the station parameters of the station selected in the
station list can be edited.



GX IEC Developer

Melsec Net Parameters... Enter the required parameters. If an area range overlaps with any
range already used, an error message is returned.
Value ranges:
B: 0 – 3FF hex. in steps of 16 bits
(entry will be rounded down to a multiple of 16).
W: 0 – 3FF hex. in steps of 1 word.
Watch dog timer: 0 – 2000 ms in steps of 10 ms.

Delete Station Deletes the station selected in the station list.

Reference Manual

PLC Parameters 5 - 15





5.7.2

Second half (not active for Melsec Net Mode) Opens a dialog where the second range
settings can be specified.
Link Used Ranges Lists all address ranges currently used for network communications.

QnA series
GX IEC Developer supports MELSECNET/10, MELSECNET (II), and Ethernet connections to the
QnA CPU module.
Restrictions:

n

The total number of network modules (MELSECNET modules + Ethernet modules) must not
exceed four.
The communication via Ethernet to the QnA series is fixed to the binary protocol.
The communication via a Computer Link module to the QnA series is fixed to the format 1.
The communication via Ethernet and MELSECNET (II) to the QnA series is not supported.



Module No.1... 4 Here you select the connection type for the network module.



1st I/O No. Enter the first I/O number for the network module in hexadecimal format. The
first I/O number must be a multiple of 16 (10h). The first I/O numbers must not overlap even
with defined Ethernet modules and keep a gap of at least 20h.



Network No. Enter the network number for MELSECNET/10. The network number must not
overlap with defined Ethernet modules.



Unit No. Enter the unit number, if required.



Refresh Opens a dialog to enter and edit the refresh parameters of the network module for
the MELSEC network.



Common/Specific Button toggles between common PLC network parameters or specific
station parameters. Opens a dialog to enter and edit these parameters.



Effective Module No. Enter the number of the defined module to be effective.

n

n
n

Reference Manual

GX IEC Developer

5 - 16 PLC Parameters



Transfer Opens a dialog to enter and edit the transfer parameters for communications
among the network modules.



Routing Opens a dialog to enter and edit the routing parameters. This dialog is valid for
Ethernet modules too. The routing parameters allow to specify network numbers of Ethernet
modules as relay networks.



Ethernet Opens a dialog to enter and edit the Ethernet settings (for details see below).



Monitor Opens a dialog to enter and edit the settings for monitoring via the network.

Ethernet Settings



Module 1... 4 These sections contain the settings for the individual network module.



1st I/O Number Enter the first I/O number for the network module in hexadecimal format.
The first I/O number must be a multiple of 16 (10h). The first I/O numbers must not overlap
even with defined MELSECNET modules and keep a gap of at least 20h.



Network (1–255) Enter the network number for Ethernet. The network number must not
overlap with defined MELSECNET modules.



Group (0–9) Enter the group number.



Station (1–64) Enter the station number.



IP Address Enter the IP address in decimal coding. Each part may contain a value from 0 – 255.

After the Ethernet settings have been set up successfully the modules will be sorted according
to their first I/O numbers.
Note: The connection to the PLC via Ethernet is only supported for the AJ71QE71/A1SJ71QE71
from version B or higher and the QnA or QnAS CPU. The product version is printed on the
device label. For details refer to the hardware manual of the device.
GX IEC Developer can not access the Q4AR CPU via Ethernet.
Note: Do not apply a Windows Forced Close Operation (CTRL + ALT + DEL) during the
communication between GX IEC Developer and the PLC or an communication error will occur
when starting GX IEC Developer the next time. In this case restart Microsoft Windows.

GX IEC Developer

Reference Manual

PLC Parameters 5 - 17

5.7.3

Q series
GX IEC Developer supports MELSECNET/10 and Ethernet connections to the Q CPU module.

MELSECNET/10 parameters




Mode Select the desired mode from the drop-down list.



Return type Select the desired return type from the drop-down list.



Starting I/O No. Range: 0 – FFF. Enter the starting I/O number for the network module in
hexadecimal format. The starting I/O number must be a multiple of 16 (10h). The starting
I/O numbers must not overlap even with defined Ethernet modules and keep a gap of at
least 20h.



Network No. Range: 1 – 239. Enter the network number. The network number must not
overlap with other defined modules.



Group No. Range: 0 – 32. Enter the group number.



Reference Manual

Network type Select the desired network type from the drop-down list.

Interrupt Opens a dialog to enter and edit the interrupt settings for the selected module.

GX IEC Developer

5 - 18 PLC Parameters



Refresh Opens a dialog to enter and edit the refresh parameters for the selected module.



Common Opens a dialog to enter and edit the common parameters for the selected module.



Transfer Opens a dialog to enter and edit the transfer parameters for communications
among the network modules.



Routing Opens a dialog to enter and edit the routing parameters.

Interrupt settings
In this dialog you edit the MELSECNET/10 interrupt settings.

The New Item button adds a parameter set to the list. A selected parameter set can be edited
via the top fields and drop-down lists. The Delete Item button deletes a selected parameter set.
Refresh parameters
In this dialog you edit the refresh parameters for a selected Q module.

The New Item button adds a link device to the list. A selected link device can be edited via the
top fields and drop-down lists. The Delete Item button deletes a selected parameter set.

GX IEC Developer

Reference Manual

PLC Parameters 5 - 19

Common parameters

The Append button appends a set of link device settings to the list. The Delete button deletes
the selected set of link device settings from the list. The Change button opens a dialog to edit
the selected set of link device settings.



Points Opens a dialog to edit the points allocation.



Area Select Toggles between the two areas LY(1); LX(1) and LY(2); LX(2).



Specific Opens a dialog to edit the station specific parameters.



I/O Master Specifies the selected link device as I/O master.



Reserve Specifies the selected link device as reserved device.



Reference Manual

Average Opens a dialog to edit the average allocation of devices.

Extension Opens a dialog to edit the extension settings for the Q CPU.

GX IEC Developer

5 - 20 PLC Parameters

Ethernet parameters

Network type Select Nothing to clear the network connection.
Mode




Mode Select the desired mode from the drop-down list.



Starting I/O No. Range: 0 – FFF. Enter the starting I/O number for the network module in
hexadecimal format. The starting I/O number must be a multiple of 16 (10h). The starting
I/O numbers must not overlap even with defined MELSECNET modules and keep a gap of at
least 20h.



Network No. Range: 1 – 239. Enter the network number. The network number must not
overlap with other defined modules.



Group No. Range: 0 – 32. Enter the group number.



Station No. Range: 0 – 64. Enter the station number.



IP Address Enter the IP address in decimal coding. Each part may contain a value from 0 – 255.



Data code Select the data code format, binary or ASCII.



Initial Timing Select the initial timing setting.
Do not wait for OPEN means that communications are impossible during STOP time.
Always wait for OPEN means that communications are possible during STOP time.



Interrupt Opens a dialog to edit the Ethernet interrupt settings.



GX IEC Developer

Network type Select the desired network type from the drop-down list. Select “Nothing” to
clear the parameter set.

Routing Opens a dialog to edit the routing parameters.

Reference Manual

PLC Parameters 5 - 21

5.8

PLC Setup

5.8.1

PLC Setup (MELSEC A)





Display Comment Enable or disable the comment display on the A3A, A3N, and A3U CPUs.



Behaviour on System Error These option buttons set CPU response to the following error
situations:
– Fuse failure
– Calculation error
– I/O module error
– Special function module error



Reference Manual

Control Input These fields are used for entering the inputs (X) used for controlling the PLC’s
operating mode.
Run The PLC is set to RUN mode as soon as this input is on.
Pause When this input is on the PLC is switched to PAUSE mode.
Relay M9040 must be set for this to be possible.

Output Mode at Stop to Run Behaviour of the PLC CPU after a system stop and restart of
the process.
Previous State
Resume process
Recalculate State
Recalculate

GX IEC Developer

5 - 22 PLC Parameters

5.8.2

PLC Setup (MELSEC Q/QnA)

Error Check
Enables you to activate/deactivate the following error checking functions:
-

Battery
Fuse
I/O modules

WDT Setting
Setting for the watchdog timer.
Range: 10 - 2,000 ms in units of 10 ms
# of Free Slots
Enter the number of addresses occupied by a free slot in this field.
Range: 0 - 64 in units of 16
Constant Scan
Enter the constant scan cycle period here.
Range: 5 - 2,000 ms in units of 5 ms
Operation Mode at Error
These options enable you to specify whether the CPU is to pause or continue working when the
following error conditions are registered:
-

GX IEC Developer

Calculation error
Extended Ins
Fuse blown
I/O unit compare error
Special function unit access error
IC card access error
IC card operation error

Reference Manual

PLC Parameters 5 - 23

System Interrupt
These fields enable you to specify the counters you wish to allocate to the system interrupt
signals. A total of 32 interrupts are available (I0 - I31).


1st Int Counter The first interrupt counter can be an address from the following counter range:
C0 - [sum of all counters minus 48]
Example:
Assuming you have set 1K of addresses for the counters in the Device Settings dialog box
you have 1,024 counter addresses available (C0 - C1023).
A possible entry for the first interrupt counter would thus be:
C0 - 1024 minus 48, which gives you
C0 - C976



I28 / I29 / I30 / I31 Const Interval You can set constant interrupt intervals for interrupts
I28 - I31.
Range: 5 - 1,000ms in units of 5ms

Allow Remote Reset
Used to enable or disable remote reset capability.
Output at Stop - & gt; Run
Specifies how the PLC CPU is to behave when the process is restarted again after a system stop.


Prior to Calc Restart at output status directly preceding the STOP condition (resume)



After one scan Output status one cycle following RUN (recalculate)

SFC program start mode

Initial start Initial start of the SFC program.


Resume start Continue from the program step where the SFC program was stopped.

Timer Interval
Used to set the intervals for the high-speed and low-speed timers. The timers will then act as
high-speed or low-speed timers when they are activated by the appropriate instructions in the
PLC program.
Low-speed timer instructions: TIMER (IEC editor), OUT (MELSEC editor)
High-speed timer instructions: TIMER_H (IEC editor), OUT_H (MELSEC editor)
Low-speed timer range: 10 - 1,000ms in units of 10ms
High-speed timer range: 1 - 100ms in units of 1ms
Run Pause Contact
Enter the inputs to be used to control the operating mode of the PLC here.
Range: X0 - X1FFF (QnA series)
The PLC will be switched to RUN or PAUSE mode as soon as the corresponding input is set.
When using the PAUSE contact the diagnostics link relay SM206 (QnA series) must also be set.

Reference Manual

GX IEC Developer

5 - 24 PLC Parameters

Intelligent modules (Q series only)




Interrupt pointer no. of module Enter the number of modules to be monitored by the
interrupt pointer.



Start I/O number Enter the I/O start address.



GX IEC Developer

Interrupt pointer start number Enter the start number of the interrupt pointer.

Start SI number Enter the SI start address.

Reference Manual

PLC Parameters 5 - 25

5.9

Special Parameters

5.9.1

Special Parameters (MELSEC A)



Input Control Defines the processing mode for the input values. The option to be chosen
depends on the PLC CPU in the system.
Direct
Direct mode processing
Buffered
Process I/O image processing (refresh mode)



Output Control Defines the processing mode for the output values. The option to be
chosen depends on the PLC CPU in the system.
Direct
Direct mode processing
Buffered
Process I/O image processing (refresh mode)

Interrupt Counter Settings
The interrupt signals are allocated to counters. The counter addresses/device numbers begin
with C224 (Int 0). The end address is C252, which is assigned to Int 31.



IModul Assigns all the interrupt addresses of special function modules AI61 and A1SI61 to
their corresponding counter device numbers (Int 0 – Int 15,
C224 – C239).



ISlot Interrupts Int 16 – Int 23 are generated by special function modules.



Periodic Interrupts Int 29 – Int 31 are periodic interrupts that are generated by the PLC CPU
at millisecond intervals.
Int 29
40 ms (C250)
Int 30
20 ms (C251)
Int 31
10 ms (C252)



Reference Manual

All Assigns all interrupts to their corresponding counters.

None Disables all interrupt allocations.

GX IEC Developer

5 - 26 PLC Parameters

5.10

CC-Link (Q/QnA)
The CC-Link settings define the hardware, communications addresses and paths in a network.
For details refer to the manuals of the network modules.





Start I/O number Enter the start I/O number in multiples of 10h. The start I/O number of
the individual boards must not overlap. Value Range: 0000 – 0FE0.



Type Select the desired type from the drop-down list.



Master station link type Select the desired type from the drop-down list.



Mode Select the desired mode from the drop-down list.



Parameter name Enter a parameter name.



Data link disorder station setting Select whether to hold the input data or not.



Number of exclusive stations Select the number of exclusive stations from the drop-down list.



1. – 6. Enter the addresses for used items.



All connect count Enter the total number of connected CC-Link stations.



Retry count Enter value.



Automatic reconnection station count Enter value.



Standby master station number Enter value.



Delay information setting Enter value.



PLC down select Select Stop (default) or Continue for CC-Link communications in case the
PLC has stopped.



Scan mode setting Select Asynchronous (default) or Synchronous scan mode.



Information This button opens the CC-Link station information dialog (see below).



Initial This button opens the Remote device station initial setting dialog (see below).



GX IEC Developer

Number of boards within modules Before you can edit the CC-Link settings you have to
select the number of CC-Link boards from the drop-down list. Several boards can be editied in
individual dialog boxes. Each dialog box can be selected via tabs.

Interrupt This button opens the Interrupt settings dialog (see below).

Reference Manual

PLC Parameters 5 - 27

5.10.1 CC-Link station information
In the CC-Link setting dialog click on the Information button to open the following dialog.

The total number of CC-Link stations you specified in the CC-Link setting dialog in the field All
connect count are listed. Click on any station number to select a station entry and edit it via the
drop-down lists and entry fields on top.


Station type Select the station type.



Exlusive station count Select a number for the exclusive station.



Reserve/invalid station select Enter the station status.



Intelligent buffer select Enter the buffer sizes. Value ranges: 0 – 4096



Default This button resets the selected station number to default values.



Check This button checks the settings of the selected station number for errors.

5.10.2 Remote device station initial setting
In the CC-Link setting dialog click on the Initial button to open the following dialog.




Amount reg. procedures Lists the total amount of registered procedures for each target
station.



Register target station Enter a number for the target station to be registered or edited.
Value range: 1– 64.



Register proc This button opens the procedure registration dialog (see below) for a target
station either selected from the list or entered in the Register target station field.



Reference Manual

Target number Lists the number of the registered target station.

Delete This button deletes a selected target station from the list.

GX IEC Developer

5 - 28 PLC Parameters

Procedure registration dialog
In the Remote device station initial setting dialog click on the Register proc button to open
the following dialog.

The procedures for the target station are listed. Click on any procedure entry to select and edit it
via the drop-down lists and entry fields on top.



Condition device Select a a condition device from the drop-down list.



Device number Enter address of the condition device.



Execute condition Select from drop-down list.



Write device Select from drop-down list.



Device number Enter address of the write device.



Write data Select ON or OFF from the drop-down list.



New This button adds a new entry to the list.



Delete This button deletes a selected entry from the list.



Default This button resets a selected entry to default values.



GX IEC Developer

Execute flag Select to set the execute flag.

Check This button checks a selected entry for setting errors.

Reference Manual

PLC Parameters 5 - 29

5.10.3 Interrupt settings
In the CC-Link setting dialog click on the Interrupt button to open the following dialog.

The interrupt settings for the selected CC-Link board are listed. Click on any entry to select and
edit it via the drop-down lists and entry fields on top.



Device number Enter a device number. Value range: 0000 – 07FF.



Detection method Select a detection method from the drop-down list.



Interrupt condition Select an interrupt condition from the drop-down list.



Word device: Setting value Enter a setting value for word devices.
Value range: 0 – 65535



Board number Enter the board number.



Interrupt (SI) number Enter value. Value range: 0 – 15.



New This button adds a new entry to the list.



Delete This button deletes a selected entry from the list.



Default This button resets a selected entry to default values.



Reference Manual

Device code Select a device code from the drop-down list.

Check This button checks a selected entry for setting errors.

GX IEC Developer

5 - 30 PLC Parameters

5.11

System Variables
System variables that do no need a minimum setting can be left empty so that they are not
available for the compiler. If the compiler requires a system varaiable which was left empty, an
error message will be returned and the compilation will fail.

5.11.1 System Variables (MELSEC A/FX)
It is not normally necessary to change the settings of the system variables. If conflicts or overlaps
occur GX IEC Developer will output a message explaining the cause of the problem.



Word Range These fields are used to enter the range used by the Code Generator for
temporary 16 and 32 bit variables. These variables are needed for Function Blocks and the
nodes of multiple output connections. You can specify whether the temporary variables are
to be stored in D, R or W registers.

Note: A few commands can not be executed with W and R.




System Timers The system timers are used for Task management. Interval-triggered Tasks
are handled by the System Timers.



System Counters Range to be used for internal counters



System Labels Used for specifying the range to be used for the system labels. The system
labels (pointers) are system variables that GX IEC Developer needs for internal management
of the project. A maximum of 256 system labels are supported. One system label is needed
for each of the following elements:
- Every instance of a function block (© page 6-48, 6-51)
- Every user-defined function (© page 6-43)
- Every event-triggered task (© page 6-1)
- Every network label (© page 3-24)
- PLS_M, PLF_M, ALT_M with further instructions (© page 2-13)



Step Flags The Step Flags are need for Step Ladder programming and are only relevant for
the FX series of controllers.



GX IEC Developer

Bit Range The same applies for the Bit Range as for the Word Range, except that the Bit
Range is the range used for the temporary values for bit devices.

Used Ranges button Displays a list of all devices and address ranges used for system variables.

Reference Manual

PLC Parameters 5 - 31

5.11.2 System Variables (MELSEC Q/QnA)
System variables (system labels) are used for internal processes. By default the upper half of the
address range specified in the Device Settings dialog box is reserved for system variables.
Example:
Device settings:
System variables:

D = 12K
D = 6144 - 12287





Bit Range The bit range for temporary variables



System Timers the range to be used for internal timers
Standard: Normal timers T
Acumlt: Accumulator timers ST
NB: Timers only function as accumulator timers when they are activated by the appropriate
instructions in the PLC program, e.g. OUT_ST.



System Counters Range to be used for internal counters



System Labels Used for specifying the range to be used for the system labels. The system
labels (pointers) are system variables that GX IEC Developer needs for internal management
of the project. A maximum of 256 system labels are supported. One system label is needed
for each of the following elements:
- Every instance of a function block (© page 6-48, 6-51)
- Every user-defined function (© page 6-43)
- Every event-triggered task (© page 6-1)
- Every network label (© page 3-24)
- PLS_M, ALT_M with further instructions (© page 2-13)



Step Flags Range to be used for step flags



Reference Manual

Word Range The word range for temporary variables
Select the appropriate device type and enter the address range.

Used Ranges button Displays a list of all devices and address ranges used for system variables.

GX IEC Developer

5 - 32 PLC Parameters

5.12

MELSECNET/MINI

5.12.1 MELSECNET/MINI (MELSEC A/QnA)
The settings for the MiniNet are made in the table. The line above the buttons displays either a
note on correct entry or an error message, depending on the cell selected in the table.




Type Selection of the network type: MiniNet or MiniNet-S3



Station Total number of all remote I/O stations in the network



Receive Definition of the operands for refreshing receive data. The following operands are
valid: X, M, L, S, B, T, C, D, W, R



Send Definition of the operands for refreshing send data. The following operands are valid:
X, M, L, S, B, T, C, D, W, R



Retry Number of attempts to re-establish communication with a remote I/O station which
has failed



Response Priority for access to the buffer memory of the Master Module



Data clr. Deletion or retention of the data of a failed station



Detection Register with which the data refresh of the failed station is to be performed



Error Code Register with which the error code refresh is to be performed



At fault The status of data transmission in the event of a communication error.
The following entries are possible:
TEST Output of a test string
OFF
Transmission of a 00 string to the remote I/O station
HOLD Sends data to the remote I/O station shortly before communication



GX IEC Developer

I/O no. Start address of the MiniNet module

CPU halt Specifies the operating status of the MELSECNET/MINI when the PLC was stopped:
RESUME: MELSECNET/MINI continues operation
PAUSE: MELSECNET/MINI suspends operation
Valid only for QnA.

Reference Manual

PLC Parameters 5 - 33

5.13

CPU Type Selection
The CPU Type Selection button opens the list box for selection of the CPU type. To change the
CPU type, open the list box, select the new CPU type and confirm with OK.
Note: When you change the CPU GX IEC Developer deletes the old libraries and regenerates
the Standard and Manufacturer libraries for the new PLC type. This process can take a while as
all the instructions for the new CPU must be integrated in the libraries.
The following table lists all supported CPU types.
PLC Series

CPU Type

A1

A1N

A2C

A2C

A2

A2N

A3N

A3N

AnS

A1S, A1S-S1, A2S, A2S-S1

AnSH

A1SH, A1SJH, A2SH, A2SH-S1

A2A

A2A, A2A-S1

A3A

A3A

A2AS

A2AS, A2AS-S1, A2AS-S30, A2AS-S60

A2U

A2U, A2U-S1

A3U

A3U

A2US

A2US, A2US-S1, A2US-S30, A2US-S60

FX2

FX / FX2

FX0

FX0 / FX0S

FX0N

FX0N

FX1S

FX1S

FX1N

FX1N

FX2N

FX2N / FX2NC

FX2C

FXU / FX2U / FX2C

QnA

Q2A(H), Q2AS(H), Q2A(H)-S1, Q2AS(H)-S1, Q3A, Q4A

Q4AR

Q4AR

Q

Reference Manual

Q02(H), Q06H, Q12H, Q25H

GX IEC Developer

5 - 34 PLC Parameters

GX IEC Developer

Reference Manual

Programming 6 - 1

6

Programming
6.1

The Structure of GX IEC Developer Programs
Data Unit Types

POUs

DUT 1

POU 1
Program

DUT 2

POU 2
Function

DUT 3

POU 3
Program

Task 1
POU 1
Program
POU 3
Program
POU 4
Program

POU 4
Program

Globale Variables

Task 2

VAR_EXTERNAL

POU 6
Program

POU 6
Program

VAR_EXTERNAL

POU 7
Program

POU 7
Program

VAR_EXTERNAL

6.2

POU 5
Function block

POU 8
Function

Tasks
The Task Pool is the ‘control centre’ for the execution of your programs. You must define at
least one task for the project in the Task Pool. In turn, each task contains one or more PRG
(program) type POUs. Each POU can only be defined once in any one task in the Task Pool.
The tasks in the Task Pool are polled cyclically.
Note: You cannot directly manage either function blocks or their instances in tasks.
The execution of tasks is controlled by the following three parameters:
n
n
n

Event
Interval
Priority

All tasks are either event-triggered or interval-triggered.
Note: In order to address the SUB memory range with the A3 CPUs you must create a special
task called MELSEC_SUB.

6.2.1

Event-triggered Tasks
Events can have the following Boolean values:
n

n

Reference Manual

TRUE/FALSE: Tasks with the event value TRUE are always executed. The TRUE or FALSE
parameter must be entered in UPPER CASE letters!
Interrupts: Interrupt-triggered execution control is only possible with input modules that
support this function. You can poll up to 32 different interrupts (I0 – I31). The task will be
executed when the interrupt polled is set. The interrupt number (e.g.: I20) is entered after
Event in the task attributes in the Task Information dialog box.

GX IEC Developer

6 - 2 Programming

Note: Remember that the EI instruction (Enable Interrupt) must be programmed within the
program POU when using interrupt-triggered tasks (only possible in the MELSEC editor).
This POU must not be programmed in SFC language.

n

Relays: The task is executed when the corresponding relay is set (e.g.: M100).

n

I/Os: The task is executed if the status conditions of the corresponding inputs or outputs are
satisfied (e.g.: X0).

Note: Every event-triggered task is allocated one system label (© page 5-30).

6.2.2

Event-triggered tasks with Timer/Output Control
(MC-MCR execution)
If you enter a Boolean device as an event you can then select the Timer / Output Control option.

The following table explains how this option influences the processing of the task.
Timer / Output Control not
activated

Timer / Output Control activated

Execution mode

Normal execution

MC-MCR execution

Task event

X10

X100

Execution sequence

LD X10
POU execution

LD X100
MC N Internal relay
POU execution
MCR
LDI X100
CJ
End of Task

LDI
CJ

X10
End of Task

Behaviour when
event is active

If X100 is set execution of the program sequence
between the MC and MCR instructions begins.
If X100 is not set the PLC program branches to the end
of the task.

Behaviour when
event is not active

GX IEC Developer

If X10 is set the POU associated
with the task is executed.
If X10 is not set the PLC program
branches to the end of the task.
The program branches to the end of
the task but some of the device
statuses are preserved:
- Timers: continue to run
- Retentative/accumulator timers
and counters: status preserved
- Devices in OUT instructions:
status preserved

The statuses of the devices are reset:
- Timer: Count value reset to 0, contacts remain off
- Retentative timers and counters:
count value and input contact status preserved, output
contact is reset
- Devices in OUT instructions: outputs are reset
- Devices in SET, RST, SFT
instructions: current status preserved

Reference Manual

Programming 6 - 3

6.2.3

Interval-triggered Tasks
The intervals are entered in units of 10 ms. If a task is to be executed at fixed intervals you must
enter FALSE for the Event parameter in the Task Information dialog box.
Syntax:

T#[Time]ms

[Time] This is the value for the interval duration.
An entry of T#10ms defines an interval duration of 10 ms.
IMPORTANT: You must consider the program cycle period when defining the interval
duration! Defining intervals shorter than the program cycle period can lead to unpredictable
results. When in doubt, always calculate the cycle period of the task using the instruction
execution times listed in the controller manual.

6.2.4

Priority-controlled Tasks
The task with the lowest priority value has priority and it will call its associated programs first.
You can assign priority values between 0 and 31.

How to define task execution attributes
ቢ n the Project Navigator window, select the name of the task you wish to edit.
ባ Press the key combination ¦« to open the Task Information dialog box.
ቤ Enter your values for the task attributes.
ብ Confirm with OK.
The attribute settings are shown in parentheses after the name of the task in the Project
Navigator window.
Tasks in order of their execution priority:
– Event-triggered via Interrupt I0
– Event-triggered via M100
– Event-triggered via X10
– Always executed
– Interval-triggered, every 10 ms

Note: The procedure for creating a new task is described in Chapter 4.

6.2.5

Special task MELSEC_FIRST
If you name a task MELSEC_FIRST (not case sensitive), it is handled with its assigned POUs in a
special way:
n
n

The assigned POUs will be the first ones in the MAIN sequence program.
All internal code parts from the code generator which must be positioned at the beginning of
the MAIN sequence program will be positioned after this task.

The following checks are performed during the code generation and will cause an error on
occurrence:
n
n

n

Interrupt events are not possible for this task.
Because SFC POUs must be initialised in the first scan before they are used, they could not be
assigned to this task.
The SFC control functions SFC_CTRL and SFC_PAUSE use a semaphore which is reset at the
beginning of the MAIN sequence (now after MELSEC_FIRST). Therefore this functions could
not be used directly by programs assigned to MELSEC_FIRST or within their calltree.

The task priority is ignored for MELSEC_FIRST - you are informed of this circumstance by a
warning. All errors or warnings are displayed in the error listbox.

Reference Manual

GX IEC Developer

6 - 4 Programming

6.3

Variables

6.3.1

Global and Local Variables
Variables are similar to operands. They contain the values of inputs, outputs or internal memory
locations in the PLC. There are two types of variables:
n
n

Global Variables
Local Variables

Global Variables
Global variables have fixed hardware addresses (absolute addresses). These absolute addresses
refer to a specific memory location for the variable in the CPU or a physical input or output.
Global variables are defined for the entire project and they can be referenced as VAR_EXTERNAL
in function block and program POUs. They make it possible to exchange data between all the
sub-programs that go to make up the project.
Local Variables
Local variables (VAR) are only accessible within the one specific program organisation unit (POU)
in which they are declared. Thus, they cannot be used for exchanging data between POUs.
Note: All variables that need to be referenced via fixed hardware addresses (e.g. relays,
registers and I/Os) should be declared as global variables. The great advantage of this
approach is that you can then use the symbolic names instead of the hardware addresses to
reference them in your program. This greatly improves the readability of your programs, making
them much easier to update and maintain. For example, if input X0 triggers the Emergency-Off
control routine, a reference to the symbolic name ‘Emerg_Off’ is much easier to understand
than a reference to input X0.

6.3.2

Variable declarations
Each variable declaration has the following elements:
n
n
n
n
n
n
n
n

GX IEC Developer

Class,
Autoextern option,
Identifier,
Absolute address (global variables only),
Data type,
Initial value (automatically),
Comment (optional),
Remark (optional).

Reference Manual

Programming 6 - 5

6.3.3

Class
The class keyword assigns the variable a specific property that defines how it is to be used in the
project.
Class

Use in POUs:

Meaning

PRG

FUN

FB

VAR

X

X

X

Variable that is only used within the POU

VAR_CONSTANT

X

X

X

Local variable with unchangeable initial value
used within the POU

VAR_INPUT

-

X

X

Variable passed from outside that cannot be
altered within the POU

VAR_OUTPUT

-

-

X

Variable passed (output) by the POU

VAR_IN_OUT

-

-

X

Local variable passed from outside and
passes (output) by the POU, can be altered
within the POU

VAR_EXTERNAL

X

-

X

Global variable used in the POU header

VAR_EXTERNAL_CONSTANT

-

X

VAR_GLOBAL

X

-

X

Global variable declared in the Global
Variable List

VAR_GLOBAL_CONSTANT

6.3.4

X

Global variable with unchangeable initial
value used in the POU header

X

-

X

Global variable with unchangeable initial
value declared in the Global Variable List

Identifiers and Absolute Addresses
Each variable is given a symbolic address, i.e. a name. This is referred to as the identifier; it
consists of a string of alphanumeric characters and underline characters. The identifier must
always begin with a letter or an underline character. Spaces and mathematical operator
characters (e.g. +, -, *) are not permitted.
Examples of identifiers:

FAULT
ZEROSIG
LIM_SW_5

When global variables are declared absolute addresses can be assigned that reference the
memory location of the variable in the CPU or a physical input or output.
When local variables are declared in the header of the POU they are automatically assigned a
suitable memory location in the CPU.
You can use either the IEC syntax (IEC-Addr.) or the MITSUBISHI syntax (MIT-Addr.) to assign the
absolute addresses. Two address columns are available.
As soon as you have entered an address in one of these columns, the other address also
appears. You can enter either of the two address formats in both columns. If, for instance, you
enter a MITSUBISHI address in the IEC column, GX IEC Developer identifies it immediately, places
it in the correct column and produces the matching IEC address in the other column.
Use upper case letters only and no spaces or mathematical operator characters
(e.g. +, -, *) in addresses.
When you define global variables you must specify the hardware addresses for each individual
variable. The address declarations are shown in the table below.

Reference Manual

GX IEC Developer

6 - 6 Programming

MITSUBISHI
Address

IEC
Address

Size ᕥ

%I

X

X0
X1F
X37
X7FFF






%IX0
%IX31 ᕣ
%IX31 ᕤ
%IX32767 ᕥ

%Q

X

Y0
Y1F
Y37
Y7FFF






%QX0
%QX31 ᕣ
%QX31 ᕤ
%QX32767 ᕥ

W, D

0

D450
D501+
D502



%M

%MW0.450



%MD0.501




%MX0.0.5
%MX0.100.15

Range

X

Y

D

Example

%M
W ᕣᕥ

Xᕥ

0

D0.5
D100.F

W, D

1

W35F
W301+
W302



%M

%MW1.863



%MD1.769




%MX1.863.5
%MX1.863.15

%M
R ᕣᕥ

Xᕥ

1

W35F.5
W35F.F

W, D

2

R450
R501+
R502



%M

%MW2.450



%MD2.501




%MX2.450.5
%MX2.450.15

%M

X5

2

R450.5
R450.F

%M

X

0

M0
M1024




%MX0.0
%MX0.1024

B ᕣᕥ

%M

X

1

B3F



%MX1.63

S ᕢ

%M

X

2

S10



%MX2.10

T Contact ᕧ

%M

X

3

TS10



%MX3.10

T Value

%M

W

3

TN40



%MW3.40

C Contact

%M

X

4

CS10



%MX4.10

%M

W, D

4

CN10
CN210




%MW4.10
%MD4.210 ᕤ

T Coil

%M

X

5

TC20



%MX5.20

C Coil

%M

X

6

CC20



%MX6.20



5

A0
A0+
A1

%MW5.0



%MD5.0



%MW6.1

M / L / S ᕡᕢ

C Value

Aᕣ

Vᕢᕣ

%M

W,D

%M

W,D

6

V1
V2+
Z2



%MD6.2

%M

W

7

Z2



%MW7.2

%M

Xᕥ

7

Z2.5
Z2.F




%MX7.2.5
%MX7.2.15

F

%M

X

7

F20



%MX7.20

Lᕥ

%M

X

8

L30



%MX8.30

Vᕥ

%M

X

9

V47



%MX9.47

Z

N

Not permitted in IEC

P

Cf. network label

I

Only allowed in event-triggered tasks

K

K0



0

HFF



16#FF

H
SM ᕥ

%M

X

10

SM1024



%MX10.1024

SD ᕥ

%M

W, D

10

SD450



%MW10.450

%M

GX IEC Developer

16#

X

10

SD45.5
SD45.F




%MX10.45.5
%MX10.45.15

Reference Manual

Programming 6 - 7

MITSUBISHI
Address

IEC
Address

Size ᕥ

Range

Example

SB ᕥ

%M

X

11

SB3F



%MX11.63

SW ᕥ

%M

W, D

11

SW35F



%MW11.863




%MX11.95.5
%MX11.95.15

%M
ZR ᕥ

X

11

SW5F.5
SW5F.F

W, D

12

ZR327
ZR40501 +
ZR40502



%M

%MW12.327



%MD12.40501




%MX12.27.5
%MX12.27.15
%MX8.10

%M

X

12

ZR27.5
ZR27.F

ST Contact ᕥ ᕧ

%M

X

13

STS10



ST Value ᕥ

%M

W

13

STN40



%MW8.40



14

U1\G8
U2\G10 +
U2\G11

%MW14.1.8



%MD14.2.10

14

U1\G8.5
U1\G8.F




%MX14.1.8.5
%MX14.1.8.15

U \G ᕥ

%M
%M

ST Coil ᕥ

W, D
X

%M

X

15

STC20



%MX9.20

%I

X

16

J1\X1F



%IX16.1.31

J \Y ᕥ

%Q

X

16

J1\Y1F



%QX16.1.31

J \B ᕥ

%M

X

16. .1

J2\B1F



%MX16.2.1.31

J \SB ᕥ

%M

X

16. .1

J2\SB1F



%MX16.2.11.31



16. .1

J1\W35F
J1\W301 +
J1\W302

%MW16.1.1.863
%MD16.1.1.769

16. .1

J1\W5F.5
J1\W5F.F




%MX16.1.1.95.5%MX16.1.1.95.1
5

J1\SW35F
J1\SW301 +
J1\SW302



%MW16.1.11.863
%MD16.1.11.769

J1\SW5F.5
J1\SW5F.F




%MX16.1.11.95.5
%MX16.1.11.95.15

J \X ᕥ

J \W ᕥ

%M
%M

W, D
X

J \SW ᕥ



↔$
!C5,
5,0,2
55,2
55,2
55

%M

W, D

16. .11

%M

X

16. .11

BL ᕥ

%M

W

17

BL319



%MW17.319

TR ᕥ

%M

X

18

TR511



%MX18.511

DX ᕥ

%I

X

1

DX1F



%IX1.31

DY ᕥ

%Q

X

1

DY1F



%QX1.31

FX ᕥ
FY ᕥ

Not needed in IEC
corresponds to VAR_OUTPUT or function result

FD ᕥ

Not needed in IEC
corresponds to VAR_OUTPUT, VAR_INOUT or function
result

Jᕥ

Not permitted in IEC

Uᕥ

Reference Manual

Not needed in IEC
corresponds to VAR_INPUT

Not permitted in
IEC

GX IEC Developer

6 - 8 Programming

Table notes
³ M, L and S devices are not compatible to old MEDOC projects. The system does not check
whether latch relay devices L (e.g. L100) are within the latch range of the relay devices M.
Memory-buffered M relays are not displayed as L latch relays.
L and S relays are handled differently in the Q/QnA series.
· In the A series CPUs the step status devices S are treated in the same way as M relay devices.
For example, this means that M100 and S100 are identical.
In the F and Q/QnA series CPUs the S devices are treated as step status devices
The devices S can not be used by the user program.
» Applies for A series controllers only
¿ Applies for F series controllers only
´ Applies for Q/QnA series controllers only
² The size prefix is optional, i.e. the entries %IX10 and %I10 are effectively identical.
Prefixes:
X Bit device
W Word device
D Double word device
¶ The following types of MITSUBISHI devices are used for timers and counters:
STS, TS, CS
Contact (Timer, Counter)
STC, TC, CC
Coil (Timer, Counter)
STN, TN, CN, T, C
Value (Timer, Counter)

6.3.5

Initial Value
The initial values are set automatically by the system and cannot be changed by the user.

6.3.6

Comment
You can add a comment up to 64 characters long for each variable.

6.3.7

Remark
You can add additional user information.

6.3.8

Autoextern option
Global variables activated in the Autoextern column are automatically added to all existing and
new POUs (programs and function blocks only). Detailed information see page 3-48.

GX IEC Developer

Reference Manual

Programming 6 - 9

6.3.9

Data Types
The data type of a variable defines the number of bits it contains, how they are processed and
the variable’s value range. The following data types are available.
Data type

Value range

INT

Integer

DINT

Double integer

WORD

Bit string 16

1 bit

-32768 to 32 767

Boolean

Size

0 (FALSE), 1 (TRUE)

BOOL

16 bits

-2147483648 to 2147483647

DWORD

Floating-point value

TIME

Time value

STRING ³

16 bits

Bit string 32

REAL

32 bits

0 to 65535
0 to 4294967295

32 bits

3.4 E +/- 38 (7 digits)

32 bits

T#-24d-0h31m23s648.00ms
to
T#24d20h31m23s647.00ms

32 bits

Character string

max. 50 characters

³ You can set the default value for the number of characters in string variables with the option
Extras - Options - General - Default String Length (characters).
The STRING datatype is only available for MELSEC Q/QnA series.
Data unit types (DUT) are structured, derived data types containing a collection of variables
which can be of different data types (© page 6-54).
Data types hierarchy ANY
ANY

ARRAY

ANY_SIMPLE

ANY_NUM

ANY_BIT

TIME

DUT

STRING

BOOL
WORD
DWORD

ANY_REAL

ANY_INT
INT

REAL

DINT

Data types hierarchy ANY16 and ANY32
ANY_16

WORD

Reference Manual

ANY_32

INT

DWORD

DINT

GX IEC Developer

6 - 10 Programming

6.3.10 Address Batch Replace
The Address Batch Replace function is available for the global variable list of the project and in
the global variable lists of the included libraries.
This function replaces an existing address range by a new address range.
In the Tools menu select Address Batch Replace to open the following dialog.

The address range can be entered in either IEC or Mitsubishi format. Both formats must not be
combined.
The greyed last entry field is calculated automatically.
Example:

The variables with the addresses D100 – D 199 are replaced by the addresses D200 – D299. A
variable with the address D100.0 will be changed to D200.0.
Note: The Undo function is not supported for the Address Batch Replace.

6.3.11 Auto Update
Global and local variables can be updated automatically by the Auto Update function. This
function can be activated via the menu Extras - Options - Editing (refer to 2.8.2).
The following changes of a variable declaration are updated: Class, Identifier, Address, Type,
Initial. All changes made in the GVL will also be executed in the POUs. When you change a POU
header, its body will also be changed automatically. The variables are updated after the
declaration editor changes have been saved.
Via the menu Extras - Update Variables all references of the selected variables are updated.
For every reference to be updated a message box appears where you can decide to update the
reference or not.

GX IEC Developer

Reference Manual

Programming 6 - 11

6.4

Programming Languages

6.4.1

Networks
Programming is done in ‘networks’ in all programming languages except Sequential Function
Chart (SFC) and Structured Text (ST). You can define multiple networks, each of which is
identified with a network label. It is then possible to switch from one network to another within
the PLC program by using jump instructions in the program code. For a detailed description of
this please refer to chapter 3.
Network labels can have a maximum of eight characters and must always be terminated with a
colon (:). You can also assign a title to each network. These network titles can be descriptive
names up to 22 characters long, and using them makes handling large projects with many
networks a great deal easier.
Note: Remember that every network label uses one system label and that the total number of
system labels is limited to a maximum of 256. Since system labels are also needed for other
elements in GX IEC Developer (© page 5-30), you should only define labels to networks to
which you actually intend to perform a jump.
The Network List
The networks in your program organisation units are managed in the Network List, which you
can only open when the body window of the corresponding POU is open. The list window
contains all the POUs networks with their labels and titles. In the window you can add more
networks and edit existing ones. A search function (Find) is provided for finding specific
networks quickly (© Chapter 3).
IMPORTANT: For all practical purposes it is not possible to change the programming language
of a POU once you have selected it. The system will allow you to make the switch, but if you do
this you will lose all the code in the body. You should thus only switch the programming
language of bodies that do not contain any code!

Reference Manual

GX IEC Developer

6 - 12 Programming

6.4.2

Text Editors
Instruction List (IL)
Programming in Instruction List is performed with a simple text editor.
An Instruction List program consists of a sequence of controller instructions. Each controller
instruction must contain an operator or a function or function block and one or more
operands/variables. Each controller instruction must begin in a new line. You can also add
optional comments to each instruction. All the programming elements in the individual
instructions must be separated by tab stops.
MELSEC Instruction List
The user interface for programming in MELSEC IL is identical to that for IEC IL. However, only
the ‘Pure’ MELSEC instruction set is supported (© Appendix E); you cannot write IEC standard
programs in the MELSEC IL editor. The functionality of the MELSEC IL language corresponds to
that of the MELSEC MEDOC programming and documentation system. This enables you to easily
import programs developed with MELSEC MEDOC and integrate them into your GX IEC
Developer programs
(© Chapter 7).
IEC Instruction List
The user interface for programming in IEC IL is identical to that for MELSEC IL. There are just a
few differences in programming:
n

n

MELSEC Networks in IEC IL
You can also integrate MELSEC networks in IEC IL programs, thus effectively giving you
access to the ‘Pure’ MELSEC programming instructions.
The Accumulator
The accumulator is a result management system often used in high-level languages. The
result of every operation is stored in the accumulator directly after execution of the
instruction. The accumulator thus always contains the operation result of the last instruction
executed. You do not need to program any input conditions (execution conditions) for the
operations; execution always depends on the contents of the accumulator.

Note: The difference between programming in the MELSEC editor (with execution condition)
and in the IEC editor (with accumulator) is described in the Beginner’s Manual (© Chapter 3).
Structured Text (ST)
ST is a text-oriented editor (programming language), similar to PASCAL and supports
mathematical functions and a simple creation of loops.
Structured Text (ST) is an editor from the IEC 61131 programming standard. The Structured Text
editor is compatible to the IEC 61131.3.
All IEC 61131 (IEC 61131-3: PART3-1992) standard functions are supported.
All MELSEC instructions are supported.

GX IEC Developer

Reference Manual

Programming 6 - 13

6.4.3

Graphical Editors
Ladder Diagram (LD)
In Ladder Diagram you can use both IEC and MELSEC programming instructions in every
network. A Ladder Diagram program consists of contacts (break and make), coils, function
blocks and functions. These elements are connected with horizontal and vertical lines called
interconnects. The circuits always begin at the power bar on the left.
Functions and function blocks are displayed as graphical blocks. In addition to their input and
output parameters, some blocks also have a Boolean input (EN = ENable) and a Boolean output
(ENO = ENable Out). The status of the output always corresponds to that at the input.
IMPORTANT: You must normally create a separate network for each circuit in a Ladder
Diagram program. However, you can also create an additional power bar parallel to the
standard one provided by the editor, connecting the two at one point. This option makes it
possible to perform programming in just one network where this is more convenient.
Function Block Diagram (FBD)
In Function Block Diagram language, as in Ladder Diagram language, you can use both IEC and
MELSEC programming instructions in every network (© Appendix E). All instructions are
implemented using graphical blocks, which are connected with one another with horizontal and
vertical connecting lines. There are no power bars (rails) in Function Block Diagram language.
Functions and function blocks are displayed as graphical blocks. In addition to their input and
output parameters, some blocks also have a Boolean input (EN = ENable) and a Boolean output
(ENO = ENable Out). The status of the output always corresponds to that at the input.
IMPORTANT: In Function Block Diagram language you must create a separate network for
each circuit.

Reference Manual

GX IEC Developer

6 - 14 Programming

6.4.4

Sequential Function Chart (SFC)
Sequential Function Chart is a graphical language. Strictly speaking it is not really a genuine
programming language but rather a structural tool which allows a clear representation of
processes.
The program (PRG) is the only program organisation unit supported in SFC.
SFC language has two basic elements, Steps and Transitions (continue conditions). An SFC
program sequence consists of a series of steps separated by transitions. Only one step can be
active at any one time in such a program sequence. The next step in the sequence is activated
when the preceding step has been implemented and the transition condition is satisfied.
Steps and Actions
Several actions can be assigned to one step. An action can be a Boolean output variable or a
program, which can be written in any of the editors, including Sequential Function Chart itself.
All actions are listed in the Action Pool in the Project Navigator window. A step to which no
action is assigned is treated as a wait loop that stops execution until the following transition
condition is fulfilled. A step is activated when the transition condition (continue condition)
immediately preceding it is fulfilled.
Steps are represented graphically as rectangles containing a name (descriptor).
Macro Steps
Each step can be declared as a macro step, which in turn consists of a sequential structure. The only
limitation on the nesting depth of such structures is the memory capacity of the controller used.
Macro steps are identified by two additional horizontal lines within the step rectangle.
Transitions
Each transition has a transition condition. Transition conditions can be programmed in the
Instruction List, Ladder Diagram and Function Block Diagram languages. Like the steps, the
transitions are also listed in the Project Navigator window.
Transitions are displayed in the editor with a small box lying on the vertical connecting line
between the steps.
Initial Step
An SFC sequence always begins with an initial step. The initial step does not have to be at the
beginning, however – it can also be placed at another point in the sequence.
Note: The initial step is always the first step that is executed in an SFC program, even if it is
not placed at the physical beginning of the sequence.
The initial step is identified by a double outline.
Branching
SFC programs support both selective and parallel branching. Selective branches divide into two
or more transition conditions. Parallel branches are always inserted after transitions, and they
always activate actions or jumps.
Selective branching
In a selectively-branched sequence not more than one step can be active simultaneously. If the
transition conditions of two or more transitions in a selectively-branched sequence are active at
the same time the execution priority is determined on the basis of the order of the sequences
from left to right. This means that only the sequence that is furthest to the left will be executed.
The sequences to the right of this sequence will not be executed, even if their transition
conditions evaluate true.
Selective branches are displayed as single horizontal lines.

GX IEC Developer

Reference Manual

Programming 6 - 15

Parallel branching
Parallel-branched sequences allow the activation of multiple steps simultaneously. The steps
leading off the parallel branch become active as soon as the preceding step and the transition
condition are satisfied.
Several processes can be executed simultaneously in parallel branches.
Parallel branches are displayed as double horizontal lines.
Jumps
Jumps are executed with exit and entry steps (jumps and jump destinations). Each entry step (i.e.
the jump destination) is always directly followed by an action. You can thus only insert an entry
step when the action which is to follow it is selected. The exit step must always be programmed
after a transition, as it replaces the action that would normally come in this position. This means
that no further actions or transitions can follow an exit step, which is thus also the final instance
within its SFC sequence. The relationship between the exit and entry steps is established by using
the same label (name) for both of them.
When you program a jump instruction pressing ’ displays a list of all the labels (i.e. potential
jump destinations) that have already been defined. You can then simply select the appropriate
label from the list and confirm to enter it.
Note: You will find examples of the sequencing rules described here on the following pages.

EMERGENCY OFF for FX Series
For the FX series PLCs it is now possible to integrate an EMERGENCY OFF switch in an SFC
program. All step relays in the sequence are reset as soon as the EMERGENCY OFF switch is
activated. The calculated values in the steps are not lost when this happens. The program
process branches back to the initial step. This does not mean that the complete sequence is
re-initialized, however – the sequence is only interrupted. You should always exercise caution
when restarting processes. The EMERGENCY OFF switch is declared as a BOOL variable with the
comment !RESET!. It is also possible to declare this variable in the Global Variable List.

Reference Manual

GX IEC Developer

6 - 16 Programming

6.5

Programming in Sequential Function Chart Language
Programming in SFC language calls for systematic analysis of the control sequence before you
start. The algorithm for implementing the control task should be drawn up in a systematic
step-by-step procedure. SFC programs are planned on the basis of statuses and status
transitions. One starts by identifying all the statuses in the process and connecting them with
status transitions. The general statuses formulated in the first program development phase can
then be gradually made more precise. In the final phase each status is implemented in a
program and each status transition in a condition (program).
Note: In the Beginner’s Manual (© Chapter 6) you will learn step by step how to create an SCF
program and to use the tools in the SFC editor.

6.5.1

Sequential Function Chart Language Program Structure
The body of a newly-generated SFC POU always consists of the initial step, a transition and the
final step.
Note: When you are first trying out the SFC editor it’s a good idea to keep an eye on the active
tools in the Toolbar. Only the elements whose tool icons are active can be inserted at the
selected position. Create a test program to experiment with all the available ways of using SFC
language elements.
The following basic rules of thumb will help you with writing your first SFC programs:
n

n

n

n

n

GX IEC Developer

Each step must always be followed by a transition, each transition by a step.
The only exceptions to this rule are exit and entry steps (jumps and jump destinations). Both
of them ‘replace’ steps, and they must thus always be programmed directly after transitions.
Entry steps (jump destinations) must logically always be followed by a step that can be executed.
An exit step (jump) must always be programmed after a transition that is not followed by a step.
Selective branches can only be inserted before transitions.
Since a selective branch polls a variety of conditions before executing a step these conditions
must be placed in transitions directly after the branch.
Parallel branches can only be inserted after transitions.
This is because a parallel branch has the effect that two or more steps are performed
simultaneously after a common transition.
You must assign a transition condition to every transition in the program.
A transition condition is a program that defines the conditions under which the transition to
the next step is to be enabled.
You must assign an action to every step in the program.
An action can be either a program or a Boolean output variable. Please note that an action’s
program is not a POU, however!

Reference Manual

Programming 6 - 17

6.5.2

Sequence rules and examples
Simple sequences
A simple sequence consists of a series of alternating ‘Step – Transition’ pairs.
STEP_1

TRAN_1

Example:
The transition from STEP_1 to STEP_2 is only executed if STEP_1 has been executed and
transition condition TRAN_1 evaluates true.

STEP_2

Divergence into selective sequences
Branching to a selection of alternative sequences (divergence) is
programmed by programming one transition beneath the horizontal line for
each alternative sequence to be included in the selection. Note that if
several transition conditions evaluate true at the same time only the
sequence that is furthest to the left will actually be executed!

STEP_1

TRAN_2

TRAN_1
STEP_2

STEP_3

Example:
The transition from STEP_1 to STEP_2 only takes place when STEP_1 has
been executed and transition condition TRAN_1 evaluates true. The
transition from STEP_1 to STEP_3 only takes place when STEP_1 has been
executed, TRAN_2 evaluates true and TRAN_1 evaluates false.

Convergence from selective sequences
The end of a selectively branched sequence is converged again by
programming one transition above the horizontal line for each branch
sequence to be terminated.

STEP_2

STEP_1

TRAN_2

TRAN_1

Example:
The transition from STEP_1 to STEP_3 only takes place when STEP_1 has
been executed and transition condition TRAN_1 evaluates true. The
transition from STEP_2 to STEP_3 only takes place when STEP_2 has been
executed and TRAN_2 evaluates true.

STEP_3

Divergence into parallel sequences
You can only program one transition directly above the double horizontal
synchronisation line.
STEP_1

Example:
The transition from STEP_1 to STEP_2 and STEP_3 only takes place when
STEP_1 has been executed and transition condition TRAN_1 evaluates true.
Following simultaneous activation of STEP_2 and STEP_3 the two sequences
are executed in parallel, independently of one another.

TRAN_1

STEP_2

Reference Manual

STEP_3

GX IEC Developer

6 - 18 Programming

Convergence of parallel sequences
You can only program one common transition beneath the double horizontal
synchronisation line.
STEP_2

STEP_1

Example:
The transition from STEP_1 and STEP_2 to STEP_3 only takes place when both
STEP_1 and STEP_2 have been executed and are connected by the double
horizontal line above the transition. The transition condition TRAN_1 must also
evaluate true.

TRAN_1
STEP_3

Empty branches
This is a special form of selective branching in which one or more
alternative branches contain no steps.
STEP_1

TRAN_1

TRAN_4

Example:
If and only if TRAN_1 is false and TRAN_2 is true the transition
runs from STEP_1 to STEP_4, skipping STEP_2 and STEP_3.

STEP_2

TRAN_2

STEP_3

TRAN_3

STEP_4

Exit and Entry Steps (Jumps)
A transition condition can be followed by an exit step ³ instead
of a step. The label of the exit step references the corresponding
entry step ·, which can be placed anywhere in a sequence
directly before an executable step. The exit and entry steps must
have the same designators (names). This structure can be used to
program loop constructs.

STEP_1
TRAN_1
LABEL_1 ³
STEP_2

Example:
The sequence is processed up to STEP_3. Then, if STEP_3 has been
executed, TRAN_3 evaluates false and TRAN_4 evaluates true,
execution performs a jump back to STEP_2 via LABEL_1.

TRAN_2

STEP_3

TRAN_3

TRAN_4
LABEL_2 ·

STEP_4

GX IEC Developer

Reference Manual

Programming 6 - 19

Creating a Sample Program
Operations and Order of Procedure:
³ Step and Transition

³

· Parallel Branch (Divergence)
» Convergence
¿

¿ Step and Transition
´ Selective Branch (Divergence)

´

·

² Step and Transition
¶ Step and Transition
²

º Step and Transition
¾ Convergence



The illustration shows the creation of an example
program in nine steps. The shaded areas show the
position of the selection highlight for insertion of the
corresponding element.

»

º
¾

Reference Manual

GX IEC Developer

6 - 20 Programming

6.5.3

Editing elements in the SFC language
You can edit all the elements in an SFC sequence. The commands for editing elements are
accessed in the Edit menu under Modify. Here too, only the commands that can be performed
for the current selection are active:
n
n
n
n
n

6.5.4

Initial step
Final step
Macro step
Entry step
Exit step

Content indication in SFC editor
The content of a body or transition in an SFC can be indicated by a filling in a user-definable
color. The color can be defined in the menu View - Colors - SFC Raster Elements.
The filling indicates that
n
n

6.5.5

A step inlcudes an assigned action
A transition includes an assigned condition

Zoom functions
Zoom functions for transitions
If you have not yet created a transition double-clicking on the transition symbol opens the New
Transition dialog box for the definition of a new transition.
If the transition has already been defined double-clicking on the transition symbol opens the
editor for the creation of the corresponding PLC program.
Zoom functions for steps
The Step Zoom Into option in Extras - Options - Zoom Header/Body enables you to define
which dialog box is to be opened when you double-click on a step symbol.



First Action If Any If at least one action is already associated to the step the PLC program
of the first action in the list is opened for editing.



GX IEC Developer

Step Action Association Action Association dialog box: Association of an action to a step

Comment Dialog box Comment: Enables you to enter a comment text. If you want the
comment text to be displayed on the screen in the step box you must activate the Extended
Information feature in the View menu. This will also display additional information in the
Project Navigator window.

Reference Manual

Programming 6 - 21

6.5.6

Assigning Actions to Steps
You can assign actions to every step. An action is a program that can be written in Instruction
List (IEC or MELSEC), Ladder Diagram or Function Block Diagram language. These programs are
all listed in the Action Pool in the Project Navigator window.

How to associate actions to steps
ቢ Select the step to which you wish to assign an action.
ባ Select Edit Action Association in the Tools menu to open the Action Association dialog box.
ቤ Press ’ to open the Action Name List, which shows all the programs in the Action Pool.
Note: The procedure for creating a new action is described in Chapter 4 (‘How to create new
objects’).
ብ Select the required action and confirm with OK. The name is then displayed in the Action
Association field.
ቦ Press ° to close the dialog box.
The selection of actions from the Action Name List as described in step ቤ is for the association
of programs already stored in the Action Pool. If no actions have yet been created a message is
displayed when you press ’.
The action associated with a step does not have to be a program; you can also associate steps
with direct operands, effectively defining the operand as an action.
Note: Steps that have already been associated with actions are shown shaded in the editor.

Reference Manual

GX IEC Developer

6 - 22 Programming

6.5.7

Assigning Transition Conditions
Each transition must be associated with a transition condition. A transition condition can be
n
n
n

a program written in the IL (IEC IL only), LD or FBD languages
a Boolean operand with a value of FALSE or TRUE
a Boolean variable with a value of FALSE or TRUE

How to assign transition conditions
ቢ Open the body of the SFC POU.
ባ Select the transition symbol to which you wish to assign a condition.
ቤ Enter the name of the condition.
ብ Select Zoom Body from the Tools menu. The New Transition dialog box is displayed with
the new transition name.
ቦ Select the programming language you wish to use for the transition program.
ቧ Confirm your selection with OK.
The editing window of the selected language editor is then opened, and the name of the new
transition is displayed below the Body entry of the SFC POU in the Project Navigator window.
You can now write the program for the transition condition.
Transitions that have been assigned a name are shown shaded in the sequence chart, even if the
associated program has not yet been created. This means that the identification feature that
applies for steps does not apply for transitions; you can only check whether the associated
program has been created by looking in the Project Navigator window. If the program has been
created the name of the transition will appear under the Body entry in the Navigator.
Programming Transition Conditions
Programming a transition condition is the same as programming any other POU. However, the
program must be written in a network. Also, you are only allowed to use one output variable,
and this variable must have the name of the transition or the name TRAN.

GX IEC Developer

Reference Manual

Programming 6 - 23

6.5.8

Enhanced Display
If you need information about the actions contained in a step or programs contained in a
transition you can automatically open and arrange the respective windows via the Enhanced
Display function. If an SFC body is monitored, the monitor mode is automatically activated for
the opened bodies.

How to activate the enhanced display
ቢ In an SFC body click on a step or transition to select it.
ባ To open the Enhanced Display context menu
right-click on the SFC body or press [Shift]+[F10].
ቤ From the context menu select Enhanced Display - Open action / transition.
ብ The action and the transition of the selected item are opened and arranged as shown below.
The monitor mode is automatically activated.

The body of the action is displayed in the upper right section of the SFC body.
The body of the transition is displayed in the lower right section of the SFC body.
If a step was selected, the first action of this step and the body of the following transition are
opened.
If a transition was selected, the body of the first action of the previous step and the body of this
transition are opened. If more than one previous step is available (parallel sequences) the
leftmost located step is displayed.
Actions and transitions which were already opened will be closed before the Enhanced
Display.
The menu item Enhanced Display - Close windows closes all windows which were opened
and arranged automatically.

Reference Manual

GX IEC Developer

6 - 24 Programming

6.5.9

Comments in Sequential Function Chart Language
You can now enter an additional comment for each step in the SFC editor. Each comment can
be up to 256 characters long.

Entering comments
ቢ Activate the Extended Information option in the View menu to increase the size of the
step display in SFC language.
ባ Select the step in the sequence for which you wish to enter a comment. Take care to only
mark the step itself and not its name.
ቤ Activate the Edit Step Comment option in the Tools menu to display the comment entry
dialog box.
ብ Enter the text of your comment.

ቦ Press §« to insert the comment text into the box representing the step.

ቧ You can suppress the comment text display by deactivating the Extended Information
option in the View menu.
See also the Comment option in Extras - Options - Zoom Header/Body Step Zoom Into (chapter 2).

GX IEC Developer

Reference Manual

Programming 6 - 25

6.5.10 Manual SFC Control
Via the manual SFC control a machine can be controlled by manual operation of the SFC sequence.
By mouse or menu operation the selected steps can either be set or reset. Alternatively, all active
steps are reset and all selected steps are set.
Before the corresponding command will be executed, a message box appears including one of
the following warnings:
n
n

All selected steps are set and all selected steps are reset.
All active steps are reset and all selected steps are set.

You can execute or cancel the selected command.
Step selection
It is possible to select a step either via the mouse or the keyboard. If you want to select more
than one step, you can click on the corresponding steps while pressing the [CTRL] key. Multiple
selections via the keyboard are not possible.
Availability
If an SFC body is opened, the submenu SFC Control is available after the menu item Debug Step has been opened.
The submenu SFC Control is also available in a context menu which can be opened either via
the key [SHIFT]+[F10] or a right-click on the SFC body.
The submenu SFC Control includes the following menu items:


Set selected steps... All selected steps are set.



Reset selected steps... All selected steps are reset.



Replace active by selected steps... All active steps are reset and all selected steps are set.

The submenu SFC Control is available only if the monitor mode is enabled. If the monitor mode
is disabled, the submenu is greyed, i. e. not available.
Limitations
If you select more than one step at time and then call the set or replace function, it will not be
checked whether the SFC configuration is valid or executable.
The manual SFC control is not available for selected macro steps.
Code generation for manual SFC control
The step flags of every SFC block can be influenced by automatically generated code. For details
refer to 2.9.1.

Reference Manual

GX IEC Developer

6 - 26 Programming

6.5.11 Sequence errors
The following examples illustrate two typical errors in SFC programs.
An ‘unsafe’ sequence
Transition T_4 can only be polled when both S_2 and S_4 have been
executed. However, as soon as T_2 is false and T_3 is true, sequence
execution continues with S_5. The result is that it is possible for the
process to restart without S_4 being active and without it being
possible to execute S_6.
This type of process is referred to as ‘unsafe’.

S_1
T_1
S_3

S_2

T_2
S_4

T_3
S_5
T_5

T_4
S_6

S_7
T_6

T_7

An ‘inaccessible’ sequence
This sequence suffers from a similar problem. In this case, T_6 is
completely inaccessible when the sequence containing steps S_5 and
S_7 is executed. T_6 can only be polled if both S_6 and S_7 are
active. S_6 can never be active, however, because T_4 can only be
polled and execute its transition when S_2 and S_4 are active.

S_1
T_1
S_2

S_3
T_2
S_4

T_3
S_5
T_5

T_4
S_6

S_7
T_6

GX IEC Developer

Reference Manual

Programming 6 - 27

6.5.12 Start, stop, and initialise SFC for QnA CPUs
To control SFCs in a project from other program parts, GX IEC Developer provides the following
functions for the QnA CPU: Start, stop, and initialise.
Additionally, a function including inverse logic is available.
SFC control functions
All SFC control functions are declared as manufacturer functions in the Manufacturer Library
(MLIB). These SFC control functions can be used for QnA CPUs only. They are realised as
functions which are not called, but directly expanded by the code generator at the locations
where they are used.
Functions:
SFC_START
SFC_PAUSE, SFC_PAUSED
SFC_STOP, SFC_STOPPED
SFC_CTRL,
The names used for SFC POUs and SFC steps must be valid. If they are invalid, an error message
appears.
Additionally, the used SFC POUs must be assigned to a task. If they are not assigned to a task,
an error message appears.
SFC_START

Via SFC_START a paused SFC POU is started again. The step name is not used for paused SFC
POUs.
Via SFC_START also a stopped SFC POU can be started again. If a Step_name is given, the POU
is started at the specified step. If several steps should be activated, several SFC_START functions
have to be used.
If a paused SFC POU should continue with the last active step, the empty string must be used. A
stopped SFC POU will be started with its initial step.

Reference Manual

GX IEC Developer

6 - 28 Programming

SFC_PAUSE

When the input EN is TRUE the SFC POU given with SFC_name is paused when it is not already
paused.
When the input parameter OUT_mode is TRUE the output of all coils, which are used with an
OUT instruction at the step being executed when the SFC POU will be paused, are maintained.
When it is FALSE they are switched off.
The OUT_mode behaviour is realised with the special relay SM325. The SFC POU is paused when
its according block is not executed. The value of SM325 is used to decide how to handle the coils.
To avoid the influence of other SFC_PAUSE functions with a different OUT_mode set, an
additional “Pause-is-Currently-Executed-Flag” is used to pause in one scan all SFC POUs with the
same OUT_mode set. At the next scan all SFC POUs will be effected where the OUT_mode has
the opposite setting. Therefore for the EN and OUT_mode inputs of the SFC_PAUSE no pulsed
devices should be used.
SFC_PAUSED

The status of the given SFC POU is assigned to the output parameter Paused. If the SFC POU is
paused, the output parameter Paused is TRUE. If the SFC POU is not paused, the output
parameter Paused is FALSE.
SFC_STOP

Via SFC_STOP the specified SFC POU is stopped. All steps are reset and the status of the output
of all coils is switched off. The output of all coils is used with an OUT instruction at the step
being executed when the SFC POU will be stopped.

GX IEC Developer

Reference Manual

Programming 6 - 29

SFC_STOPPED

Via SFC_STOPPED the status of the given SFC POU is assigned to the output parameter Stopped.
The output parameter Stopped is TRUE when the SFC POU is stopped. The output parameter
Stopped is FALSE when the SFC POU is not stopped.
SFC_CTRL

The function SFC_CTRL is activated via the EN input. If EN is TRUE, the SFC POU is influenced.
If EN is FALSE, the SFC POU is not influenced.
As long as SFC_ON is TRUE the specified SFC POU will be executed.
If SFC_ON is FALSE, the SFC POU is paused. The output of all coils depends on the input
parameter OUT_mode at the step being executed when the SFC POU will be paused (see ).
If SFC_INI is TRUE, the specified SFC POU is stopped. All steps are reset and the output of all
coils is switched off at the step being executed when the SFC POU will be stopped.
If SFC_INI is FALSE again and SFC_ON is TRUE, the SFC POU is started with the initial step.
If SFC_ON and SFC_INI are both active, the SFC POU is paused and reset.
The SFC_hold output is always FALSE.
The SFC_CTRL can be used within the SFC POU which is controlled by the SFC_CTRL. In this case
the SFC_CTRL is executed only when the step containing the action including the SFC_CTRL
function is active. When the SFC POU is paused or reset the SFC_CTRL must be started outside
of the SFC POU.
Conditions of using SFC control functions
The control functions SFC_PAUSE and SFC_CTRL, which include “OUT_Mode” influence the relay
SM325. This special relay controls the OUT instruction behaviour of SFC POUs.
Since SFC POUs are also paused when they are assigned to a conditioned task, only one of both
methods to control the OUT instruction behaviour is allowed to be active at the same time. This
is not checked or guaranteed by the code generator, but must be done by the user. Therefore,
you should use only one method at a time to avoid problems.

Reference Manual

GX IEC Developer

6 - 30 Programming

6.5.13 ST for Boolean transitions
The permanently visible direct variable name or transition name has been expanded by a
window, which is shown below the conditions. In this window IEC 61131.3 ST Boolean
arithmetic for the Transition Condition can be edited in textual form. These Boolean expressions
meet the IEC 61131.3 standard. The transition is executed according to the Boolean expression.
Normally this window will show one line consisting of approx. 25 characters (depending on the
selected font, scrollable). A line not completely visible can be indicated by dots. If the transition
or the step before is selected (or if it is active in monitor mode), a window of appropriate size is
displayed. If text is added into the window, slider bars might appear.
Tools
The command Edit Transition Condition
The command Edit Transition Condition is included in the SFC toolbar and in the menu Tools.
Edit Transition Condition is available if the SFC editor is active. The SFC editor is active if a
transition rectangle is marked at the moment. Otherwise the SFC editor is disabled.
The function of this command depends on the current status of the transition or on the current
content of the transition’s rectangle respectively.
a) Transition rectangle is empty (no transition defined yet)
n
n

Create a new transition: name= " " , language = ST.
Open the Transition Condition editor.

b) Transition rectangle contains a name which is no variable, no transition name, and
not TRUE or FALSE
n
n
n

Create a new transition: name= " " , language = ST.
Set transition rectangle to “”.
Open the Transition Condition editor.

c) Transition is a Boolean variable whose direct address is TRUE or FALSE
n

n
n
n
n

You are asked whether you want to convert the direct variable into a Transition Condition:
“Do you really want to replace ‘varX’ by a Transition Condition?”
NO: nothing is done, exit function
YES: continues
Create a new transition: name= " " ; language = ST.
Clear the old transition’s rectangle name.
Transform the Boolean variable or direct address into the ST format.
Open the Transition Condition editor.

d) Transition is already a Transition Condition
n

Open the Transition Condition editor.

e) Transition is a standard transition including a body in any language
n

n
n
n

GX IEC Developer

You are asked:
“There is a body defined for this transition!
Do you want to delete this body?”
NO: nothing is done, exit function
YES: continues
Delete the existing transition body.
Create a new transition: name= " " ; language = ST.
Open the Transition Condition editor.

Reference Manual

Programming 6 - 31

The command Zoom Body
The command Zoom Body opens the Transition Condition editor if the corresponding transition
is already a Transition Condition. Otherwise the appropriate editor will be opened (as before).
a) If the current transition is a valid device or variable, nothing will happen.
b) If the transition is empty (new definition), it depends on the INI-file entry what happens.
[Options]
SFC_TransitionConditionIsDefaultEditor =
If this value is set to TRUE, the Transition Condition editor will appear. Otherwise the dialog
New Transition will be opened.
The command Zoom Into
The command Zoom Into behaves like Zoom Body.
The command Zoom Out
The command Zoom Out works also in the Transition Condition editor. Changes will be stored
to the database.
The command End Edit
The command End Edit behaves like Zoom Out.
The command List Operands
The command List Operands opens the dialog Variable Selection, which can be called by
means of the menu command, the toolbar icon, or by pressing the key F2 within the TC editor.
The command New variable
The command New Variable opens the dialog Variable Selection in the NewVar mode. This
dialog can also be called by pressing ALT+N.
Transition rectangle
Display
The transition rectangle display contains the beginning (if there is not enough space to display
the complete Transition Condition) of the Transition Condition in brackets with a leading ‘=’.
‘...’ shows that there is not enough space to display the complete condition.
Example:
TC:

(X10 AND X11) OR (aBool1 OR aBool2)

Transition Display: =[(X10 AND X11) OR ((aBoo...]
In the display carriage returns, line feed, and tabs will be replaced by spaces.

Reference Manual

GX IEC Developer

6 - 32 Programming

Edit field of the Transition name
When leaving the edit field of the Transition name, additional checks will be performed. There
are the following situations:
a) A Transition Condition exists and has been replaced by a Boolean variable or address.
You are asked whether you want to delete the existing Transition Condition.

Yes:
Delete the corresponding ST Transition
Set the given variable into the Transition’s rectangle
No:
n
n

n

Nothing will be done, exit function

b) A Transition Condition exists and will be replaced by an identifier not yet defined
You are asked whether you want to delete the existing Transition Condition.

Yes:
Delete the corresponding ST Transition
Set the given identifier into the Transition’s rectangle
No:
n
n

n

Nothing will be done, exit function

Double-click behaviour
A double click on the Transition’s rectangle has the same effect as using the commands Zoom
Into or Zoom Body.
The double click opens the Transition Condition editor if the corresponding Transition is already
a Transition Condition. Otherwise the appropriate editor will be opened.
If the current transition is a valid device or variable, nothing will happen.
If the transition is empty (new definition), it depends on the INI-file entry what happens.
[Options]
SFC_TransitionConditionIsDefaultEditor =
If this value is set to TRUE, the Transition Condition editor will appear. Otherwise the dialog
New Transition will appear.

GX IEC Developer

Reference Manual

Programming 6 - 33

Edit window

The left upper corner of the edit window is located at the right upper corner of the transition
rectangle.
The edit window has a maximum and a minimum size. Within this range the window is adapted
to the current size of its content.
Syntax
ST Boolean expressions can be entered. All types of IEC 61131.3 ST expressions resulting in a
Boolean value can be entered.
The following table shows the IEC 61131.3 ST operators and to their priority level.
Priority level
1
2
3
4

5

6
7
8
9
10
11

Operation
Brackets
Function call
Exponentiation
Negation

Operator symbol
()
Fun( )
**
-

Complement
Multiplication

NOT
*

Division

/

Modulo
Addition

MOD
+

Subtraction
Comparison
Equality

& lt; , & gt; , & lt; =, & gt; =
=

Inequality
Logical AND
Logical Exclusive OR
Logical OR

Comments

& lt; & gt;
AND, &
XOR
OR

Unary minus
Remainder of integer
division
Binary minus

It is also possible to enter only the pure expression in the SFC transition (ST Boolean expressions) :
X1 AND X2
ST Boolean expressions are nameless. Therefore they are not displayed in the project navigator.
Navigator
Cut, Copy, Paste
Since the TC bodies are not visible for the user, there is no possibility to cut, copy, paste these
bodies explicitly.
Cut, copy, and paste the complete SFC POU also include the TC bodies.
SFC UNDO
The SFC UNDO function handles the Transition Conditions in a similar way as standard transitions.

Reference Manual

GX IEC Developer

6 - 34 Programming

Transition body
a) Blank transition before defining a new TC
Take the following steps:
ቢ Delete the created ST body.
ባ Delete the internal SFC transition body.
b) Direct transition before defining a new TC
A direct transition can be TRUE or FALSE, a direct Boolean variable, or a direct Boolean address.
Take the following steps:
ቢ Delete the created ST body.
ባ Delete the internal SFC transition body.
ቤ Restore the old direct transition name.
c) Standard transition before defining a new TC
Take the following steps:
ቢ Delete the created ST body.
ባ Delete the internal SFC transition body.
ቤ Restore the old transition name.
Replace an existing TC
a) Direct transition
To replace an existing TC by a direct transition,
ቢ clear the name of the direct transition.
Remark
Step 1 is not implemented because this feature is not available when replacing a standard
transition body.
b) Transition name
To replace an existing TC by a transition name,
ቢ clear the name of the transition body name.
Remark
Step 1 is not implemented because this feature is not available when replacing a standard
transition body.

GX IEC Developer

Reference Manual

Programming 6 - 35

Unused transitions
When leaving the SFC editor without saving the changes problems may occur.
In the following situations unused ST bodies will be left:
n
n
n

Replace a direct transition by a Transition Condition
Leave the SFC editor and cancel the saving of the changes
Open the SFC editor. The direct transition is displayed again, but the corresponding transition
body still exists in the database

The situations described above are also valid for standard transition bodies, but standard
transition bodies are visible for the user. You can delete unused transitions by yourself.
Since Transition Conditions are hidden in the navigator, it is not allowed to create unused ST bodies.
Monitoring
What is monitored?
GX IEC Developer provides a monitoring feature splitting the Transition Conditions into several
Boolean expression parts monitored separately. The splitting is done by the Boolean operators,
except for NOT (see evaluate in the following table). If a Boolean operator is included in an
expression, the expression is split into two expression parts (one part on the left and one part on
the right of the operatror). For all parts this algorithm is used recursively, until no more Boolean
operators can be found in any part. Brackets will be handled according to the arithmetic rules.
The Boolean operator NOT will be handled uniformly. NOT will be evaluated with the inverted
expression if this is a single monitoring expression (it will be monitored separately). If the
inverted expression cannot be monitored because it includes ignored operators for example, the
complete expression part including NOT will not be monitored neither.
All parts will be searched for comparison operators (see evaluate in the following table). If a
comparison operator is found, it will be compared with a Boolean value and monitored.
If an expression part includes any other operator, this expression part will be ignored and not
monitored (see ignored in the following table).
Priority level
1
2
3
4

5

6
7
8
9
10
11

Reference Manual

Operation
Brackets
Function call
Exponentiation
Negation

Operator symbol
()
Fun( )
**
-

When monitoring
handled
ignored
ignored
ignored

Complement
Multiplication

NOT
*

evaluate
ignored

Division

/

ignored

Modulo
Addition

MOD
+

ignored
ignored

Subtraction
Comparison
Equality

& lt; , & gt; , & lt; =, & gt; =
=

ignored
evaluate
evaluate

Inequality
Logical AND
Logical Exclusive OR
Logical OR

AND, &
XOR
OR

evaluate
separator
separator
separator

GX IEC Developer

6 - 36 Programming

The following examples show how transitions are monitored. The underlined parts will be
monitored as one Boolean value.
Example 1:
X1 AND X2 OR X3
Example 2:
(D1 & lt; 0) OR ((D2 & gt; 0) AND (D3 & gt; 0))
Example 3:
X1 AND (X2 OR X3) AND ((D0 0) OR X3)
Example 4:
NOT (D1 & lt; D2)
Example 5:
NOT ((D5 & gt; 0) AND (D3 & lt; 0))

Example 6:
NOT (D1 & lt; D2) AND (D3 & gt; D4 + D5)
Example 7:
(M1 AND M2) OR (M3 AND M4)
Example 8:
NOT M1 AND M2 OR M3 XOR M4

Display
There are three possible display modes: the edit mode, the online mode, and the monitoring mode.
a) Edit mode
Edit control
The edit control opens when the online mode is not active. When the online mode is closed, the
edit control opens automatically.
See sections above

GX IEC Developer

Reference Manual

Programming 6 - 37

b) Online mode
The edit mode is closed. The content of the Transition Conditions is displayed using the standard
background colour of the editor.

c) Monitoring mode
The edit mode is closed. The content of the Transition Conditions is displayed using the standard
background colour of the editor. The state of the Boolean variables and direct addresses is
displayed additionally.
Values which cannot be indicated completely within the window will not be monitored.

Starting or stopping the Transition Condition monitor automatically
Starting the Transition Condition monitor
The Transition Condition monitor starts automatically when the SFC body is monitored.
Stopping the Transition Condition monitor
The Transition Condition monitor stops when
n
n
n

the Transition Condition editor has been closed.
the SFC body monitor has been stopped.
the online mode has been left.

Multiple monitors
Only one Transition Condition monitor can be active per SFC editor. However, it is possible that
more TCs can be monitored at the same time if they are included in different SFCs.

Reference Manual

GX IEC Developer

6 - 38 Programming

6.5.14 SV instruction for QnA
Definitions
SV program PLC program for supervision (SV)
SV table

Table containing inputs for the SV program

General concept
An array of help memories includes the information when to start an SV and where the
information is located in an SV table. If a Help Memory Cell is set to ON, a supervised output is
set to ON and the SV starts. All necessary supervision parameters are included in a relative place
of the memory cell in the array. The index indicates the reference to an element in an SV table
(see below).
If the acknowledge Stop input does not get its expected value within the supervision time, a
TimeOut memory cell is activated.
M-cell
0 M1000
1 M1001
2 M1002
3 M1003

ON

.
.
.

Help Memory Cells

Time
0 100
1 80
140
2
3 160
4
5

998
999

Stop
X56
XE2
X10
X8F
.
.
.

Out
Y200
Y10F
Y100
Y135
.
.
.

TimeOut
F600
M1700
M1504
F601
.
.
.

Margin
12
25
25
50

.
.
.

.
.
.

SV table in the PLC

Example: If the Run input of an OUT_SV function block is active, the according Help Memory
Cell (here M1002) is switched to ON, i.e. that the SV program fetches all data from line 2 of the
SV table. If the SV times out, the TimeOut memory cell (here M1504), is switched to ON. The
values in the SV table are not coded correctly.
Besides F devices the TimeOut column can contain also the device values of other M memory
cells, which can be used as trigger for other user program parts.
The Margin fields are reserved for future use.
Each register of the SV table contains only a value, i.e. no memory cell or pointer can be
included. The possibilities to code SV table elements are described in section “Coding of the SV
table elements” (see page 6-42).
SV library
GX IEC Developer includes an SV library containing all necessary items for supervising:
OUT_SV, OUT_SV2 – OUT_SV6 function blocks to activate outputs and start
supervising stop inputs
SV

supervising program

To enable the SV functionality in GX IEC Developer, the new library must be specified in the file
MMP400.INI and loaded project into an existing GX IEC Developer via Project - Other - Update
Libraries.
When creating a new project, use pre-packed projects already containing the User and the
Standard libraries for the specified CPU type. After the menu command Project - New ... has
been executed, the file MMP400.INI is scanned automatically in order to check whether
additional libraries must be included into the new project. You have the possibility to update the
libraries of your new project.

GX IEC Developer

Reference Manual

Programming 6 - 39

Code generation for OUT_SV
At each step where an OUT_SV is used, the code generator of GX IEC Developer sets the
according Help Memory Cell to ON to enable the supervision.
The GX IEC Developer code generator maintains an internal code generator SV table including
information about all used supervisions. This table collects all static SV parameters during
compiling. From the code generator SV table the SV table of the PLC is created and downloaded
to the PLC when the program is transferred to the PLC. During online changes the internal code
generator SV table and the PLC SV table are updated.
For the OUT_SV a predefined function block instance must be used. This is necessary because
OUT_SV has three outputs which cannot be used together with a function. The same
predefined function block instances should be used for different TimeOuts. It is also possible to
define only one global OUT_SV function block instance and to use it at several locations.
The following table shows the possible parameters.
Name

Type

Input range

Run

BOOL

Any Boolean expression

Stop

BOOL

X, M, B

_Time

INT

0 – 32767 (0,0 – 3276,7 sec) or a VAR_INPUT if it is used in
an FB

Margin

INT (constant)

0 (to disable teach in) / 12/ 25/ 50/ 100 %

Out

BOOL

Y, M, B

T_O (* TimeOut *)

BOOL

Any M or F address

For all parameters except Run only a direct connection to a constant or a variable is allowed. The
parameter Stop can also be used negatively. The parameters Out or TimeOut cannot be used
negatively.
For the parameter _Time only a direct constant or a VAR_INPUT of a function block can be used.
VAR_CONSTANT or VAR_GLOBAL_CONSTANT are not allowed to be constants. For a
VAR_INPUT code is produced, which writes the value to the SV table. For each variable a new
line is inserted into the SV table to be independent of other entries using constants for the
parameter _Time.
For the parameter Margin only direct constants are allowed. To be able to use OUT_SV in a
macro FB with VAR_INPUT for the parameter Margin, the code generator checks whether a
constant is used.
The parameter of OUT_SV cannot be used directly in other instructions, e.g. ST
InstOUT_SV.Margin is not allowed.
For the parameters Stop and Out all local variables, global variables, or direct addresses can be
used if they meet the address range restrictions described in the section “Coding of the SV table
elements” (see page 6-42).
For the output parameter TimeOut only M or F devices can be used. In this case direct addresses,
global variables, or local variables are allowed. If any other device type is used for the TimeOut,
an error is generated during compiling.

Reference Manual

GX IEC Developer

6 - 40 Programming

The following figure shows a code which has been programmed manually in an editor.

The second network shows an example in which stop has been negated (set with a double click
in the OUT_SV box near the stop parameter).
Codes generated for the first network:
LD
AND
OUT
ANI
OUT

X0
X1
Help Memory Cell
X100
Y200

No interlocking is made when the Help Memory Cell is already activated.
It is not necessary to set a Help Memory Cell, because the Help Memory Cell is activated by the
SV program. After the activation the value of the Help Memory Cell can change without
influencing the SV program.
Codes generated for the second network:
LD
AND
OUT
AND
OUT

X0
X1
Help Memory Cell
X300
Y300

The SV parameters in the code generation SV table are updated for all networks during compiling.
For each Stop/ Out/ TimeOut combination a new line is added to the internal code generation
SV table. If a Stop/ Out/ TimeOut combination is already included in this table, Time and Margin
must be the same. Otherwise an error is generated during compiling.
To allow several Stop/ TimeOut combinations to be used with the same Time and Margin,
additional OUT_SV function blocks can be used. They must be defined as new function blocks
including their own names, because GX IEC Developer does not support extended output
parameters. OUT_SV2 allows two Stop/TimeOut combinations, OUT_SV3 allows three
combinations, etc.
For each Stop/ TimeOut combination the code generator does the same as for OUT_SV, but it
uses the same Time and Margin for the SV table.

GX IEC Developer

Reference Manual

Programming 6 - 41

Example for OUT_SV6:

Generated codes:
LD
X0
AND X1
OUT Help Memory Cell 1
:
:
OUT Help Memory Cell 6
LDIX100
ORI X20
ORI M10
ORI B2F
ORI MotorAus
ORI M20
ANB
OUT Y200
For the parameter TimeOut output M and F devices can be mixed.
F devices and User Error file
If F devices are used as TimeOut parameters for OUT_SV, the SV will activate the F devices if the
Stop input does not get its specified value within the specified time. Via Debug - User Errors a
list box can be opened in GX IEC Developer displaying the active F devices.
If the project directory includes the file USER_ERR.TXT, the project directory is scanned for user
defined error texts. For this, the text lines in the file must have the following format:
[F Device Value] [Space or ‘,’ or Tab]1-n [Error text]
Example:
1 Error text for user error 1
10

Go to Motor 12 and check whether it is running

11, Robot 10 did not reach the target B
A line can include 260 characters maximum and the error text 255 characters maximum.
Interface of the SV program
To enable the supervision, assign the SV program to an task always running. It is not possible to
include a predefined task in a library in GX IEC Developer. If you program some OUT_SV
without assigning the SV program to a task, a warning will be generated.
The SV program uses fixed addresses. The fixed addresses will be defined as global variables in
the SV library as a reference for the user that these addresses are reserved. They cannot be
changed by the user. Internally these addresses will be used directly due to some restrictions of
the MELSEC networks concerning symbolic programming and in order to have a quick base for
testing. In a second step the SV program will be changed to symbolic programming.

Reference Manual

GX IEC Developer

6 - 42 Programming

Coding of the SV table elements
Name
Stop

Supervision Time
Teach In Margin

Type
M
B
X

Offset (hex)
0
3000
6000

M
B
X
K

8000
B000
E000

K

TimeOut Memory Cell

Y
M
B
M

0
2000
A000
0

F

Out

8000

Input range
0
3000
6000
-

2FFF
5FFF
7FFF

8000
AFFF
B000
DFFF
E000
FFFF
0 - 32767
0
12/ 25/ 50/ 100
0
1FFF
2000
8FFF
A000
FFFF
0
7FFF
8000

-

FFFF

Expected status Number
1
12288
1
12288
1
8192
0
0
0
no Teach In
1
1
1
-

12288
12288
8192

8192
32768
24576
32768
32768

Additional menu commands
The additional menu commands
Extras - SV - Export Alarm Info
Extras - SV - Options
are enabled only when the SV library is present, i.e. when the SV library is part of the project.
The values which can be edited by the user are set in the dialog Option.

If the number of the Help Memory Cells is not a multiple of 32, it is adjusted to the next lower
value which can be divided by 32. If a value for the number of the SV Help Memory Cells is
entered, which is too high, it is adjusted automatically. The maximum value will result from the
length of the SV table. The default value will be 160 = 5 x 32 blocks.
When compiling the project, the addresses of the specified Help Memory Cells are allocated and
reserved in the system address range of the project. By this, these addresses will not be used
directly anywhere else in the project.
The values of the SV Options are exported or imported respectively together with the PLC
configuration.
All necessary inputs for the SV program will be set by GX IEC Developer via symbolic
VAR_GLOBAL_CONSTANTs in the SV library. The user cannot change the values of the
constants.
Symbolic name

Content set by GX IEC Developer

SV_HELP_START

Start of SV Help Memory Cells (e.g. 1234 to start at M1234) Automatically calculated by GX
IEC Developer.

SV_HELP_BLOCKS

Number of 32 bit blocks of SV Help Memory Cells

The constants will be updated when the user has changed the value in the dialog SV Options or
when new addresses have been allocated by the compiler.
When SV_HELP_START or SV_HELP_BLOCKS are changed, the SV program and all GX IEC
Developer objects, which use OUT_SV – OUT_SV6, are set to Must be compiled.

GX IEC Developer

Reference Manual

Programming 6 - 43

6.6

Programming Functions
Programming the header and body of a function is not different from programming a program
POU. You can program functions in the following editors:
n
n
n
n

Instruction List (IL)
Ladder Diagram (LD)
Structured Text (ST)
Function Block Diagram (FBD)

The two main characteristics of functions are that they output exactly one data element when
they are processed and that they always deliver the same output values in response to the same
input values. Functions do not have any memory, and although they can contain more than one
data element (arrays) they can only output one data element. Functions are thus independent
program blocks; they have the same functionality as normal programming instructions, and can
be replaced and used in other program sections at will.
Note: Each user-defined function uses one system label, irrespective of how often the function
is called (© page 5-30).

6.6.1

Using timers in functions
If you are not careful, programming timers in subprograms, functions and function blocks can
lead to problems. You should always remember that once a timer has been triggered it just goes
on counting independently, irrespective of whether the condition that triggered the branch to
the subprogram, function or function block is still true or not. It is thus better to avoid using
timers in this way if possible, and if you can’t avoid it you should make allowances for this
behaviour in the code of your program.

Reference Manual

GX IEC Developer

6 - 44 Programming

6.6.2

Declarations
The first step in creating a function block is to declare it as a program organisation unit.
Header
In the header you must declare all the variables used in the function. Function variables can be
either of the type VAR, VAR_INPUT or VAR_CONSTANT. The function itself can be one of the
data types (BOOL, INT, DINT, WORD, DWORD, TIME, REAL).
The variables declared in the header are also referred to as formal parameters.
Body
The body contains the program code to be performed on the variables declared in the header.
The result of the function must be explicitly assigned to the function name.
Note: The procedure for creating a new function is described in section 4.8, ‘How to create
new objects’.

Formal
parameters

The result is
assigned to
the function
name

GX IEC Developer

Reference Manual

Programming 6 - 45

6.6.3

Calling functions in the text editor
Note: All variables must be assigned when a function is called; the parameter list must be complete.
When you call a function in Instruction List language you must first load the first parameter into
the accumulator with the Load instruction (LD). The next program line then contains the
references to the function’s name, as the operator, and to the other variables declared in the
header. When this statement is executed actual parameters – i.e. specific values – are passed to
the remaining formal parameters defined in the header. The result of the function is stored in
the accumulator.
The value 10 is loaded into the accumulator. This is then
followed by the function call FUN_1. The value in the
accumulator is added to Factor_A and multiplied by Factor_B.
The result is stored both in D100 and the accumulator.

Note: Please note that you must always assign the values to the variables in the correct order
as dictated by the syntax!

Using the editing support function
ቢ Position the cursor in the first column and enter the name of the function.
INSERT

ባ Press § and ‘. The parameters are inserted automatically, with dummy variable question
marks and the data type in the actual parameter positions.
LD
INSERT
ST

?STRING
?STRING,
?INT
?STRING

ቤ Overwrite the dummy variable names with a direct address or a variable name.

6.6.4

Calling functions in the graphical editors
The same procedure is used for calling functions in Ladder Diagram and Function Block Diagram.

How to call functions in the graphical editors
ቢ Open the POU body
ባ Select Function Block in the Tools menu. This opens the Function Block Selection dialog box.
ቤ Select the required function’s name (© page 3-43).
ብ Confirm with OK.
ቦ The mouse pointer changes to a function ‘block’ symbol. Position it at the required location
in the editing area and press «. The graphical block representing the function is inserted at
the pointer location. The names of the variables are shown at the function, inside the block
representing the function. The name of the function itself is shown at the output, which is
also inside the function ‘block’ symbol.
ቧ Allocate actual parameters (outside) to the formal parameters (inside).

Actual parameters

Reference Manual

Formal parameters

GX IEC Developer

6 - 46 Programming

6.7

Programming Function Blocks
Programming the headers and bodies of function blocks is no different from programming
normal program POUs. You can program function blocks with the following languages:
n
n
n

Instruction List (IL)
Ladder Diagram (LD)
Function Block Diagram (FBD)

Function blocks can have one or more outputs and can produce one or more different output
values for the same input values. The results are stored after the function block has been
processed, and these values are used the next time the function block is called. Function blocks
must be instantiated before they can be called in a POU.

6.7.1

Using timers in function blocks
If you are not careful, programming timers in subprograms, functions and function blocks can
lead to problems. You should always remember that once a timer has been triggered it just goes
on counting independently, irrespective of whether the condition that triggered the branch to
the subprogram, function or function block is still true or not. It is thus better to avoid using
timers in this way if possible, and if you can’t avoid it you should make allowances for this
behaviour in the code of your program.

GX IEC Developer

Reference Manual

Programming 6 - 47

6.7.2

Declaration
The first step in creating a function block is to declare it as a program organisation unit.
Header
All the variables used in the function block’s code must be declared in the header. Variables in
function blocks can be of the types VAR, VAR_IN_OUT, VAR_INPUT, VAR_OUTPUT,
VAR_CONSTANT, VAR_EXTERNAL or VAR_EXTERNAL_CONSTANT. The result of the function can
be one of the data types (BOOL, INT, DINT, WORD, DWORD, TIME, REAL).
Body
The body contains the program code to be performed on the variables declared in the header.
Direct programming of hardware addresses is not permitted.
EXAMPLE
The function block COUNTER stores the duration of a process. The header contains declarations
of three output variables (Hours, Minutes, Seconds), one input variable (Process) and one global
variable (SecClck) that addresses relay M9032, which switches once per second.
Note: The procedure for creating a new function block is described in section 4.8, ‘How to
create new objects’.
Header of the function block

Body of the function block
As soon as an input signal is registered the variable
‘Seconds’ is incremented once per second.
When the value of ‘Seconds’ reaches 60 ‘Minutes’ is
incremented by 1 and ‘Seconds’ is reset to 0.

When the value of ‘Minutes’ reaches 60 ‘Hours’ is
incremented by 1 and ‘Minutes’ is reset to 0.

Reference Manual

GX IEC Developer

6 - 48 Programming

6.7.3

Instantiation
Function blocks cannot be called directly, they must be called as ‘instances’. When a function
block is ‘instantiated’ an instance, or copy, of it is created in the header declaration table of the
POU in question. The instance is declared as a variable VAR, for which any identifier can be used.
The ‘Type’ is the name of the function block.
Note: You can make multiple instances of one function block. However, remember that each
instance you create uses up one system label (© page 5-30).
EXAMPLE
In this example, the COUNTER function block programmed above is instantiated in the MAIN
program POU as PROCESS_TIME.

6.7.4

Calling function blocks in the text editor
You do not have to assign all the variables in the parameter list when you call a function block.
The old register values are used for those parameters not assigned in the call.
Function blocks are called with the following instructions
CAL
(Call)
CALC
(CallConditional: conditional call)
CALCN
(CallConditionalNot: negated conditional call)
Calling with a list of input parameters:
Syntax:
CAL

‘Instance Name’(‘Formal parameter’:=’Actual parameter’, ...)

EXAMPLE
The instance name of the function block is PROCESS_TIME. In this example, the actual
parameters X0, D1, D2 and D3 are assigned to the formal parameters ‘Process’, ‘Seconds’,
‘Minutes’ and ‘Hours’.
CAL

Process_Time(Process:=X0, Seconds:=D1, Minutes:=D2, Hours:=D3)

Call with input parameter load/store:
Actual parameter
Syntax: LD
ST
CAL

Formal parameter
FBName()

EXAMPLE
The instance name of the function block is PROCESS_TIME. In this example, the actual
parameters X0, D100, D200 and D300 are assigned to the formal parameters ‘Process’,
‘Seconds’, ‘Minutes’ and ‘Hours’.
LD
ST
LD
ST
LD
ST
LD
ST
CAL

GX IEC Developer

X0
Process
D100
Seconds
D200
Minutes
D300
Hours
Process_Time()

Reference Manual

Programming 6 - 49

Using the editing support function
ቢ Position the cursor in the first column and enter the CAL instruction.
ባ Position the cursor in the second column and press ’.
ቤ Select the function block instance (FB_INST in the example) from the Variable Selection
dialog box.
CAL

FB_INST

ብ Press § and ‘. The parameters are inserted automatically. The names of the internal
function block variables are entered as the formal parameters. Dummy variable question
marks and the data type are displayed in the actual parameter positions.
CAL

FB_INST(IN1:=?BOOL,
IN2:=?BOOL,
IN3:=?BOOL)

ቦ Overwrite the dummy names with either a direct address or a variable name. Tip: If you
select the dummy name (?BOOL) and press ’ you can select the variable directly from the
list displayed. Select Apply to enter the variable.
CAL

6.7.5

FB_INST(IN1:=X1,
IN2:=VAR_EIN1,
IN3:=VAR_EIN2)

Calling function blocks in the graphical editors
How to call function blocks in the graphical editors
ቢ Open the body of the program POU in which you wish to call the function block.
ባ Select Function Block in the Tools menu. This opens the Function Block Selection dialog box.
ቤ Select the required function block’s name and confirm with OK.
ብ Move the mouse pointer to the desired position in the editing window and press the Space
Bar to insert the function block.
ቦ Press ’ for a list of the instance names declared in the header.
ቧ Select the appropriate instance name and confirm with OK. The name is then used as the
identifier for the function block instance.
ቨ Terminate the procedure by pressing «.
The names of the formal parameters are
shown in the function block. The function
block type is COUNTER, the instance name
is ‘Process_Time’
(© Header).

Formal
Actual
parameters parameters

ቩ Assign the actual parameters (outside) to the formal parameters (inside).

Reference Manual

GX IEC Developer

6 - 50 Programming

6.7.6

Multiple use of a single instance
You can use the same instance of a function block in several different places within a POU, or, if
it is defined globally, in several different places within the same PLC program.
Note: If the EN of an FB or an FUN is zero, the output is not defined.

6.7.7

Execution of Function Blocks
Function blocks can be executed in different ways:
n
n
n

Macrocode execution
MC-MCR execution
Use with EN/ENO

The execution mode is selected in the Function Information dialog box.

How to set the execution option
ቢ Select the function block in the Project Navigator window.
ባ Display the Function Information dialog box by pressing ¦«.
ቤ Activate the check box. The Use MC-MCR option can only be activated when the other two
options have already been activated.
This does not make any changes to instantiation and the programming of instances in the
various programming languages.

GX IEC Developer

Reference Manual

Programming 6 - 51

Macrocode execution
n
Standard execution: The function block is called via a system label
n
Macrocode execution: The function block is expanded internally
With Macro Code

With Macro Code Without Macro Code (standard execution)

No internal system labels are needed to
execute a function block instance.

Each instance uses internal system labels (pointers). ³

Consequence: The number of function blocks
you can use is only limited by the size of the
PLC memory as function blocks are
independent of system labels.

Consequence: Since the number of available system labels is limited
(FX: 128, A: 256, Q: 1024) you cannot use more than a theoretical
limited number of function blocks. In practice this number is even
smaller as system labels are also required for other internal
processes.

User-oriented execution of the function block

Implementation of the function block construct in conformity with
the IEC 61131.3 standard

No restrictions on the handling of timers and
coils within the function block.

Restrictions on the handling of timers and coils within the function
block (subroutines).

³ To set the system labels parameter select the PLC_Config entry in the Project Navigator
window and then click on the System Variables button (© page 5-30).

The maximum permitted number of system labels
(internal pointers) is limited by the used PLC-CPU.

Macrocode execution, MC-MCR execution, Use with EN/ENO
The function blocks FB_1 through FB_5 and the corresponding instances i_FB_1 through i_FB_5
show the different execution possibilities.

The function block

Use of the funtion block

Reference Manual

GX IEC Developer

6 - 52 Programming

FB_1

FB_2

FB_3

FB_4

FB_5

Macro

NO

YES

NO

YES

YES

MC-MCR

NO

NO

NO

NO

YES

EN-ENO

NO

NO
LD X20
AND X21
INCP D20

Generated
Code

Instance
(no macro)

LD M4096
AND M4097
INCP D6144
RET

Sytem labels

1 System label
(no macro)

No system labels
(macro)

Behaviour of:
- Timers
- Counters
- Outputs

GX IEC Developer

LD X10
OUT M4096
LD X11
OUT M4097
LD SM400
CALL P2048
LD SM400
MOV D6144
D10

The function block is
always executed. The
timers, counters and
outputs are thus
controlled by the
program.

The function block is
always executed. The
timers, counters and
outputs are thus
controlled by the
program.

YES

YES

YES

LD M4
OUT M41
LDI M4
CJ P2050
LD X40
AND X41
INCP D40P2050

LD M5
OUT M51
MC N0
M4103
LD X50
AND X51
INCP D50
MCR N0

1 System label
(no macro)

1 System label
(EN/ENO and jump)

No system labels
(macro and MC/MCR)

The function block is
only executed if the
EN input is set. This
means that the
timers, counters and
outputs retain their
status from the last
execution. Timers
continue to run. The
status of counters,
accumulator/retentati
ve timers and outputs
in OUT instructions is
preserved.

The function block is
only executed if the
EN input is set. This
means that the
timers, counters and
outputs retain their
status from the last
execution. Timers
continue to run. The
status of counters,
accumulator/retentati
ve timers and outputs
in OUT instructions is
preserved.

The statuses of the devices are reset:
- Timer: Count value
reset to 0,
contacts remain off
- Retentative timers
and counters:
count value and
input contact
status preserved,
output contact is
reset
- Devices in OUT
instructions:
outputs are reset
- Devices in SET, RST,
SFT instructions:
current status
preserved

LD M3
OUT M4098
AND X30
SET M4099
LD M4098
ANI X30
RST M4099
LD M4098
AND X31
SET M4100
LD M4098
ANI X31
RST M4100
LD M4098
OUT M4101
CALL P2049
LD M4101
OUT M31
LD SM400
MOV D6145
D30
LD M4099
AND M4100
INCP D6145
RET

Reference Manual

Programming 6 - 53

6.7.8

Global Function Blocks
Function blocks allow global instancing, so that the same instance can be used in different
program organisation units.

How to create a global instance
ቢ Create a program organisation unit as a function block (in our example: MAIN).
ባ Create an instance (Main_Instance1) of this function block (MAIN) in the Global Variable List.

ቤ Declare this instance as VAR_EXTERNAL in the header of the POU (in our example: INSERT)
where the instance is to be inserted.

ብ Call up the function block in the body, and allocate to it the name of the instance.

Reference Manual

GX IEC Developer

6 - 54 Programming

6.8

Programming Data Unit Types
Data unit types (DUT) are structured, derived data types containing a collection of variables which
can be of different data types. Data unit types can be declared as global or as local variables.
Note: Data unit types can only be used in the IEC editors. DUT components or arrays can not
be used in MELSEC IL.

6.8.1

Declaration
Data unit types must be defined in the DUT_Pool.
All the variables in the DUT structure must be declared in a special declaration table. After this
you must then create one or more instances of the data unit type in the global variables
declaration table.

How to declare a data unit type
ቢ In the Object menu select New, then select Data Unit Type.
ባ Enter a name for the new DUT (max. 32 characters) and confirm with OK. The name of the
new DUT is displayed in the DUT_Pool of the Project Navigator window.
ቤ Double-click on the name of the new DUT in the Project Navigator window to open its special
declaration table.
ብ Enter a name (identifier) for the variable in the first field.
ቦ Select the data type for this variable in the second field.
ቧ The default initial value (Initial) is added automatically. If you wish, you can also enter an
optional comment for the variable.
ቨ Repeat steps ቢ – ቧ until all the variables of the data unit type are defined.
EXAMPLE
The following example shows the creation of a data unit type called SiloType. The variable
collection of SiloType contains two variables of the type INT and one variable of the type BOOL.
ቢ Enter the following lines in the declaration table for the data unit type:

ባ Save your entries.

GX IEC Developer

Reference Manual

Programming 6 - 55

6.8.2

Use of the DUT as global variable
How to declare the DUT
ቢ Double-click on Global_Vars in the Project Navigator window.
ባ Enter the following lines in the global variables declaration table:

Silo1 and Silo2 are the names of the variable of data type Silo_Type. Since the elements
in type SiloType can have different data types the address assignment is handled
automatically by the PLC, and no default initial values are shown.

How to call the DUT
The data unit types declared as global variables can be referenced as VAR_EXTERNAL in program
and function block POUs.
ቢ In the Project Navigator window, double-click on the header of the POU in which you wish to
declare a copy of the data unit type.
ባ Select VAR_EXTERNAL in the Class column in the table.
ቤ In the Identifier column, open the dialog box with the list of the defined DUTs.
ብ Select the appropriate DUT name and confirm with OK. The data type, in this case the name
of the DUT, is entered in the Type field automatically.
ቦ Enter a comment for your entry, if you wish.

EXAMPLE
You have created a Data Unit type called SiloType. Two variables of the type SiloType,
Silo1 and Silo2, have now been declared in the global variables list. The structure of both is
identical, so to reference the individual variables of each DUT you only needs to prefix their
names with the name of the respective global variable.
In Silo1 the values for the temperature and volume variables are determined by the contents
of registers D0 and D1, in Silo2 by D10 and D11. In Silo1 the Emergency Off (EmergOFF
variable) switch is controlled by the status of input X0, in Silo2 by input X1.
The variables are stored in the Global Variable List. If you apply an element of an instance of a
DUT or FB (e. g. Motor.Status) from the Global Variable List to an editor via the Variable
Selection dialog, the corresponding DUT or FB is automatically inserted in the header of the
editor. Like for simple data types the library & lt; Global Variables & gt; must be selected in the Variable
Selection dialog.

Reference Manual

GX IEC Developer

6 - 56 Programming

Instruction List:
SILO1
LD
ST
LD
ST
LD
ST

SILO2
D0
Silo1.Temperature
D1
Silo1.Volume
X0
Silo1.EmergOff

LD
ST
LD
ST
LD
ST

D10
Silo2.Temperature
D11
Silo2.Volume
X1
Silo2.EmergOff

Ladder Diagram and Function Block Diagram:

In the Ladder Diagram version of the example a function block of the type ‘Monitoring’ has been
programmed for assigning the register values and the Boolean input to the elements of the
DUTs. Two separate instances (Silo_1 and Silo_2) of this function block were then created
for the two silos.
Define direct addresses for data unit variables
The GVL has been extended to define addresses for all elements of a data unit variable. Not
defined addresses are handled by the system.
Appearance and handling
In the GVL data unit variables will display their IEC and Mitsubishi address fields in controls
similar to push buttons. On these controls the elements for which an address is defined will be
displayed in the form ‘element: address’.

To view all definitions at once (if more than one definition is available), DUT entries in the GVL
can be expanded by double-clicking the row number field.

GX IEC Developer

Reference Manual

Programming 6 - 57

Editing
It is not possible to edit the addresses directly in the GVL. To edit the EC and Mitsubishi
addresses, click on a DUV’s IEC or Mitsubishi address field. Then a separate dialog (application
modal) will appear and you can edit the addresses for each DUV element.

After you have selected an element you can edit this element like in other address fields in the
GVL (e.g. by. double clicking or pressing the space key).
When the two edit fields are displayed, the focus can be moved between them by clicking on
one of the fields or pressing the TAB key. By pressing ENTER or clicking outside of the edit fields
the editing will be finished and the modifications accepted. By pressing ESC the editing will also
be finished, but the modifications are cancelled.
If you activate the Automatic filling checkbox, when entering a address all variables of the
same type that are not yet addressed will be addressed automatically.
MELSEC Q/QnA only:
If the function Automatc filling is activated the additional function All types is available.
If you activate the All types function, when entering an address all addresses of all variable
types are filled automatically.
For timers and counters the All types function is not available, addresses of these types are not
filled automatically neither.

Reference Manual

GX IEC Developer

6 - 58 Programming

6.8.3

Use of the DUT as local variable
Data unit types can also be passed directly as variables:
-

As input and output parameters in function blocks
As input parameters in functions

Create the Control function block
The function block processes the input variables and passes the results to the output variables.
The input variables IN_Temperature, IN_Volume and IN_EmergOff are declared in the
header, along with the output variable Silo_Output. Silo_Output is declared as the data
unit type Silo_Type.

Calling the Control_Use function block and passing the data unit type directly as an output
parameter
The function block Control is called in the program organisation unit Control_Use, creating
the instance Silo_FB_1.
The input variables of the function block obtain their values from devices D0, D1 and X0.
The output variables of Silo_Output are passed to the data unit type Silo_DUT_1.

GX IEC Developer

Reference Manual

Programming 6 - 59

6.9

Programming Arrays
An array is a collection of variables of the same data type. GX IEC Developer supports arrays
with up to a maximum of three dimensions.
Note: Arrays are only supported in the IEC editors.

6.9.1

Declaration
Arrays are declared in the header of the program POU. They can be declared as Local or global
variables.
EXAMPLE
This example shows the definition of a one-dimensional array called ArrSingle with three
elements of the type INT, and a two-dimensional array called ArrDouble with three elements
of the type INT in the first dimension and five elements of the type INT in the second dimension.
ቢ Open the header of a POU.
ባ Add a new line to the table with the following entries:




VAR_EXTERNAL: This array is defined as a global variable and referenced in the header of
program POU ‘P_3’ as an external (global) variable.



ArrSingle / ArrDouble: Names of the arrays.



ARRAY [0..2] OF INT: The one-dimensional array has three elements (0 – 2) of the type
integer (INT)



ARRAY [0..2, 0..4] OF INT: This array is two-dimensional. The second dimension is
separated by a comma between the braces. In this example the first dimension of ArrDouble
has three elements (0 – 2) and the second dimension has five elements (0 – 4).



3(0): Number of elements (3) with the default value 0 (0)



Reference Manual

VAR: Definition of the array as a local variable in the program organisation unit ‘P_3’.

15(0) Number of elements (3 x 5 = 15) with the default value 0 (0)

GX IEC Developer

6 - 60 Programming

6.9.2

Calling
Instruction List:
n

One-dimensional arrays
LD
ST

n

Actual parameter
‘Array Name’[‘Element’]

Two-dimensional arrays
LD
ST

Actual parameter
‘Array Name’[‘Element of 1st Dimension’,
‘Element of 2nd Dimension’]

EXAMPLE
A two-dimensional array called ArrDouble has been defined with three elements in the first
dimension and five elements in the second dimension.
The data registers D0 and D1 are assigned to the following elements:
D0:
D1:

Position 1 in the first dimension I, position 2 in the second dimension II
Position 2 in the first dimension I, position 3 in the second dimension II

II
4
3

D1

ArrDouble

D0

2
1
0
0

1

2

I

Instruction List:
LD
ST
LD
ST

D0
ArrDouble[1,2]
D1
ArrDouble[2,3]

Ladder Diagram and Function Block Diagram:

GX IEC Developer

Reference Manual

Programming 6 - 61

6.10

Programming Timers and Counters

6.10.1 TIMER and COUNTER Functions
The timer and counter functions are stored in the manufacturer library.
Timer Functions

Counter Functions

TIMER_M

COUNTER_M

TIMER_VALUE_M

COUNTER_VALUE_M

TIMER_START_M

COUNTER_START_M

TIMER_H_M

-

Operands
Normal
timers/counters and
extended
timers/counters

Action
Pass setpoint value and call (start)
timer/counter

Extended
timers/counters only

Pass setpoint value

MELSEC Q/QnA
series’ high-speed
timer

Pass setpoint value and call (start) timer

Call (start) timer/counter

Set timer intervals by parameters

Timers and counters always have the following four elements:
Timer

Counter

Setpoint value

TValue

CValue

Actual value

TN

CN

Output coil

TC

CC

Input contact (status)

TS

CS

Note: The use of the various functions is illustrated below using a timer as an example.
Counters are used in exactly the same way.
The TIMER_M function
Note: A detailed example of the use of the TIMER_M function is provided in the Beginner’s Manual.

TIMER_M
Use of the normal timer TC20

Use of the extended timer TC256

The TIMER_M function both passes the setpoint value and starts the timer TC (TCoil). The
setpoint value is passed to TValue. With normal timers the setpoint value is passed directly. With
extended timers the passed setpoint value is assigned to the timer and the setpoint value
register (see below).

Reference Manual

GX IEC Developer

6 - 62 Programming

The TIMER_VALUE_M and TIMER_START_M functions
Using TIMER_VALUE_M and TIMER_START_M together provides exactly the same functionality
as TIMER_M. The only difference is that the parameter passing and timer start operations are
handled separately, which makes it possible to use them at different points in the PLC program.
TIMER_VALUE_M and TIMER_START_M can only be used with the extended timers, and you
must define the setpoint values registers for the extended timers.
TIMER_VALUE_M
Passes the reference value to the
extended timer TC256

TIMER_START_M
Starts timer TC256

Defining the reference value registers for extended timers and counters
You must always define and set a number of parameters when you use timers or counters. The
dialog box shown below when you select the T/C Range button in the PLC_Parameter
window of the Project Navigator:
³

·

»¿

´

²

³ Start address of the normal timers to be used
· Start address of the extended timers to be used
» Number of timers to be used
¿ Number of counters to be used
´ Type and head number (starting address) of the setpoint value registers to be used for the
extended timers
² Type and head number (starting address) of the setpoint value registers to be used for the
extended counters

GX IEC Developer

Reference Manual

Programming 6 - 63

Explanation of parameter values shown in the example
The start address for the extended 100ms timers is 256, i.e. TC256 (ᕢ). Register type D (data
registers) is selected for the setpoint value registers with a head number of 200 i.e. D200 (´).
This means that the setpoint value of extended timer TC256 is stored in D200. The assignments
for the other timers and registers are thus automatically:

Extended Timer

Setpoint Value Register

TC256

D200

TC257

D201

TC258

D202

...

...

TC273

D217

6.10.2 TIMER and COUNTER Function Blocks
A selection of new standard function blocks are provided for programming local timers and
counters. The system automatically uses free timers and counters from the system range.
Advantages: No direct timer and counter addresses are required. You can create any number of
instances – depends on the number of system timers – with different timers from just one
function block.
The following function blocks are provided:
Function Blocks

Comment

TIMER_10_FB_M

10 ms timer

TIMER_100_FB_M

100 ms timer

TIMER_CONT_FB_M

retentative timer

TIMER_HIGH_FB_M

high-speed timer

MELSEC Q/QnA series only

TIMER_LOW_FB_M

low-speed timer

MELSEC Q/QnA series only

TIMER_CONTHFB_M

retentative high-speed timer

MELSEC Q/QnA series only

COUNTER_FB_M

counter

MELSEC Q/QnA series’ timers
The timers will act as high-speed or low-speed timers when they are activated by the appropriate
instructions in the PLC program.
The timer intervals for the high-speed and low-speed range can be set in the PLC Setup dialog
box (© page 5-23). In order to be compatible to A series projects, the function blocks
TIMER_10_FB_M and TIMER_100_FB_M are available in the MELSEC Q/QnA series as well. In a
MELSEC Q/QnA series project they are the same as the function blocks TIMER_HIGH_FB_M and
TIMER_LOW_FB_M. But in this case, they are no longer 10-ms and 100-ms timers. Instead the
timer interval set by the parameters is valid.

MELSEC A/AnS

MELSEC Q/QnA

TIMER_10_FB_M

TIMER_100_FB_M

Reference Manual

TIMER_HIGH_FB_M

TIMER_LOW_FB_M

Comment

For the MELSEC Q/QnA series, it is not the
intervals 10 ms and 100 ms which are valid, but
the timer interval set by the parameters.

GX IEC Developer

6 - 64 Programming

Defining the system range
You must define the system range before attempting to use local timers or counters. The system
then automatically selects a free timer or counter from this range. A compile error will be
displayed if you try to use these new function blocks without previously defining the
corresponding system range.
ቢ Open the System Variables dialog box (PLC_Parameter – System Variables).

System timer
- 100 msec
- 10 msec
- retentive

System counter

ባ Define the necessary system range in the System Timers or System Counters fields. This
disables access to these addresses by other applications using direct addressing. Please note
that the three timer function blocks must use three separate system timer ranges. The
settings for the system timers must match the general timer settings (PLC_Config –
Timer/Counter Ranges).
Timer start address

Instantiation
The use of these new function blocks is illustrated below using a 10 ms timer as an example.
ቢ Declare the following variables in the header:
TIMER_XYZ is the instance of function
block TIMER_10_FB_M Timer start
address

GX IEC Developer

Reference Manual

Programming 6 - 65

ባ Select function block TIMER_10_FB_M in the body.

The timer function block has the following input and output variables:

The timer function block TIMER_10_FB_M for 10 msec timers

Designation
in the
Function

Meaning

Coil

Coil

Preset

Setpoint value

ValueIn

Initial value

ValueOut

Output contact

(Normally: 0)
➜ Note

Actual value

Status

Activation condition for the timer process

The output contact is set when execution of the function block is
complete.

ቤ Assign the instance names defined in the header to the function block and allocate the
necessary input and output variables.

Instance TIMER_XYZ of function block TIMER_10_FB_M

Note: If you do not need one of the parameters for your application, e.g. ValueIn in the
example, you can simply leave the contact unassigned. In this case, no program code will be
generated.
For MELSEC FX series controllers the ValueIn parameter must be left unassigned!

Reference Manual

GX IEC Developer

6 - 66 Programming

6.11

The EN input and ENO output
Some programming instructions have an EN input and an ENO output in addition to the normal
input and output variables. These instructions are identified in the standard library by the suffix
_E, e.g. ABS_E, BCD_TO_DINT_E . The functions in the manufacturer library do not have this
suffix as they are all automatically provided with an EN input and an ENO output.
Functionality
The EN input controls the execution of the instruction.
There are several different ways to connect the EN input:
³

´

·

´

»

¿

´

¿

³ Direct connection of the EN input to the power bar at the left (LD only). The EN input is then
always on and the instruction is always executed. When ADD_E is used like this it will
produce exactly the same result as ADD without the EN input.
· Link the EN input to a Boolean input variable. The instruction is then only exectued when
Variable_1 is active.
» Connect the Boolean result of a an operation to the EN input. The instruction is then only
executed when the result of the operation is TRUE.
¿ Connect the EN input to the ENO output of the preceding instruction. The three instructions
are then only executed when Variable_1 is active.
´ The ENO output does not have to be connected; it can be left unconnected if it is not needed.

GX IEC Developer

Reference Manual

Programming 6 - 67

6.11.1 Execution with and without EN and ENO
User-written function WITH_EN_ENO:
With EN input and ENO output

User-written function WITHOUT_EN_ENO:
Without EN input and ENO output

User function WITH_EN_ENO
Execution of the function is controlled by relay M4 (when the input EN is processed).
M4 = 1 (TRUE):
-

The function is executed.
The result of the operation is written to D56.
A new value is always written to D56.
-

M4 = 0 (FALSE):
-

The function is not executed.
No new value is written to D56. The value stored in D56 remains unchanged, it is not reset.

User function WITHOUT_EN_ENO
-

Reference Manual

The function is executed continuously.
The result of the operation is written to D57.
A new value is always written to D57.

GX IEC Developer

6 - 68 Programming

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 1

7

Compiling and Downloading Programs
7.1

Error Check
Before compiling your project it is advisable to perform an error check on the project or
individual objects. The following checks are carried out:
Header
Checks of all the variable declarations (unique descriptors, addressing etc).
Body
The following checks are performed in the editors:
Graphical editors
n
Validity of the data types
n
Variable names (declarations)
n
Validity of the IEC addresses
n
Validity of the MITSUBISHI addresses
n
Definition of the input variables
n
Recursions
n
Interconnects
n
Label syntax
Text editors
n
Syntax of the operators and operands
n
Number of operands
n
Recursions
n
Jumps
n
Comments
Errors and warnings are displayed in the Compiler/Check Messages status window with
explanations.
Note: When you double-click on an error message or warning in the status window GX IEC
Developer automatically opens the corresponding object, moves the point in the program where
the error was found and highlights the error in a different colour.

How to perform an error check on an object
ቢ Select Check in the Object menu.
Or:
Click with the left mouse button on the Check tool:
Note: You do not have to save your editing changes in open objects before selecting the Check
option. If changes have been made the object is saved automatically before Check is executed.

How to specify the max. number of errors and warnings
ቢ Select the option Stop Check By in the Extras - Options - General menu.
ባ Enter the maximum number of errors and warnings. The check operation will be stopped
when the number of errors and warnings exceeds the limit specified here. Range: 0 - 2,000.

Reference Manual

GX IEC Developer

7 - 2 Compiling and Downloading Programs

7.1.1

Execution order
In some cases the execution order in a ladder or FBD network is not clear, for example if
complex connections between different elements are established.
The scanner for ladder / FBD networks recognises these critical networks. In this case a warning
is indicated in the dialog Compile / Check Messages.
On demand the generated Melsec IL code of the respective network will be displayed if the POU
has been compiled. To do so take the following steps:
ቢ Mark the network.
ባ Select the menu item Tools - Show MELSEC code of network.

7.2

Compiling
The compilation process translates the project written in GX IEC Developer into code that the
PLC CPU can execute. This translation process must be performed before downloading the
program to the PLC system.

How to compile the complete project
ቢ Select Rebuild All in the Project menu.
GX IEC Developer first performs checks on all the objects in the project and displays any errors or
warnings in the Compiler/Check Messages status window. If no errors are displayed this
means that the program code has been compiled without errors.

Once the project has been compiled, the Compiler/Check Messages status window can be
opened any time via the menu item Window - Show Compile/Check Messages.
In the status window occurred errors and warnings can be browsed via the following Window
menu items:
n
n
n
n

GX IEC Developer

Show Next Error
Hotkey: [F4]
Show Previous Error
Hotkey: [SHIFT] + [F4]
Show Next Warning
Show Previous Warning

Reference Manual

Compiling and Downloading Programs 7 - 3

How to compile only modified objects
POUs that have not yet been compiled are identified in the Project Navigator with an asterisk.
POUs marked in this way were either created after the last compilation or are not part of a task.
Already compiled
Not yet compiled

ቢ Select Build in the Project menu.
Only the new objects which have not yet been compiled and the project elements which depend
on the changes will be compiled.
Note: When you double-click on an error message or warning in the status window GX IEC
Developer automatically opens the corresponding object, moves the point in the program where
the error was found and highlights the error in a different colour.
IMPORTANT: Please note that only those Program POUs that you have included in your tasks
are checked and compiled!

Earlier MM+ versions
You must completely recompile projects generated with earlier versions of MM+ (Compile
Project) before you can use the Build function on them to compile only changes made in the
editing session.

Reference Manual

GX IEC Developer

7 - 4 Compiling and Downloading Programs

7.3

Downloading Projects to the CPU

7.3.1

Transfer Setup - Ports
You can only download compiled projects to the CPU. Before making your first download, check
that the port and its parameters are configured correctly.
Note: See Chapter 2 and the manuals of your MELSEC hardware for details on connecting the
controller to your computer.

How to configure the communications port
ቢ Select Transfer Setup in the Online menu, then select Ports from the submenu displayed. A
dialog box will be opened with the following options (varies depending on your configuration):

ባ Select the correct port for your configuration, then select the Setup button.
ቤ After making your entries in the Setup and Transfer Setup dialog boxes, confirm with OK.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 5

a) Via the CPU interface



PC Port You can select one of the serial ports COM1 through COM10 for the PC Port setting.



MELSECNET Access Host, Net/NetII, or Net 10 Station.
If the PLC is installed in a station in MELSECNET/10 you must also enter the network
number and the station number.



Time Out [sec] Max. time for establishing the communication in seconds.



Mac transparent mode / modem Enables data transmission by modem between the
personal computer and the PLC.



Baud Rate Data transfer speed (9600 – 115200 Baud)



Parity Communications parity (none, even or odd)



Data Bits Number of data bits (7 or 8)



Stop Bits Number of stop bits (1 or 2)

Configurations
The table below shows the variations for MELSECNET access.
PLC connected to
GX IEC Developer

Remote PLC

Remark

A

A

Supports MELSECNET (II) and MELSECNET/10

A

QnA

Not supported

QnA

QnA

Supports MELSECNET (II) and MELSECNET/10

QnA

A

QnA series CPU must be switched to A series protocol (hardware
switch).
Supports MELSECNET (II) and MELSECNET/10

Reference Manual

GX IEC Developer

7 - 6 Compiling and Downloading Programs

b) Via the computer link module
The communication via the computer link module to the QnA is fixed to the format 1.



PC Port You can select one of the serial ports COM1 through COM10 for the PC Port setting.



MELSECNET Access Host, Net/NetII, or Net 10 Station.
If the PLC is installed in a station in MELSECNET/10 you must also enter the network
number and the station number.



Time Out [sec] Time for identification of the carrier signal in seconds



Checksum Calculation Use checksumming to check for communication errors



Mac transparent mode / modem Enables data transmission by modem between the
personal computer and the PLC.



Baud Rate Data transfer speed (9600 – 115200 Baud)



Parity Communications parity (none, even or odd)



Data Bits Number of data bits (7 or 8)



Stop Bits Number of stop bits (1 or 2)



Module Type Computer Link module type



Station No. Station number of computer link module

If the communication is opened, the connected PLC type is not checked. So make sure that the
PLC type is identical to the PLC type of the GX IEC Developer project.
In contrast to the Ethernet communication the modem connection functionality is available.
There are some restrictions concerning the computer link communication.
It is not possible to
n
n

monitor the devices BLn, Sn, BLn\TRm (monitoring via CPU port is not possible neither).
monitor the devices TC, TS, CC, CS, STC, and STS.

Note: GX IEC Developer may require several minutes to detect a lost communication
connection. This behaviour occurs with an A series and a Q/QnA series CPU.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 7

c) Via the Ethernet
The communication via Ethernet to the QnA is fixed to the binary protocol.




MELSECNET ACCESS: Access between Ethernet and MELSECNET
Host: Direct access to host station
Net/NetII Station: Access to MELSECNET (II) station
Net10Station: Access to MELSECNET/10 station



Time Out [sec] Max. time for establishing the communication in seconds.



Reference Manual

PC Side Network number and station number of the Ethernet device

PLC Side
Module Type: Ethernet module type
IP & Port Input Mode: HEX or DEC
IP Address: Address of Layer 3 in hexadecimal or decimal format (format depends on
selection under IP & Port Input Mode).
Port No. (UDP): Port number defined by the user The PLC Ethernet interface module is
able to handle up to 8 open connections simultaneously. Each connection is defined by
the Port Number. Calculated automatically.
Network No.: Copied from PC Side.
Station No.: The station number must be set if a station other than the host station is defined.
MELSECNETLocal: Station numbers 1 - 64
MELSECNET/10:
Loop system: network number and station number 1 - 64
Bus system: network number and station number 1 - 31.

GX IEC Developer

7 - 8 Compiling and Downloading Programs

Important: The following DIP switches must be set on the Ethernet modules AJ71E71 and
A1SJ71E71-B2/B5 in order to enable GX IEC Developer to interact with the PLC.
DIP switch

AJ71E71

A1SJ71E71-B2 A1SJ71E71-B5

1

OFF

OFF

2

ON

ON

3

OFF

ON

4

OFF

OFF

5

OFF

-

6

OFF

-

7

ON

-

8

OFF

-

If the communication is opened, the connected PLC type is not checked. So make sure that the
PLC type is identical to the PLC type of the GX IEC Developer project.
There are some restrictions concerning the Ethernet communication.
It is not possible to
n
n

monitor the devices BLn, Sn, BLn\TRm (monitoring via CPU port is not possible neither).
monitor the devices TC, TS, CC, CS, STC, and STS.

Note: GX IEC Developer may require several minutes to detect a lost communication
connection. This behaviour occurs with an A, Q, and QnA series CPU.

d) Via the USB-Port





GX IEC Developer

MELSECNET Access Host or Net 10 Station.
If the PLC is installed in a station in MELSECNET/10 you must also enter the network
number and the station number.
Time Out [sec] Max. time for establishing the communication in seconds.

Reference Manual

Compiling and Downloading Programs 7 - 9

e) MAC transparent mode
In transparent mode you can access the PLC and a MAC control terminal at the same time. You
can select either the PLC or the computer link module as the interface.
The communication parameters are fixed in the MAC transparent mode. They cannot be changed.
The communication parameters are 19200 baud, odd parity, 8 data bits, and 1 stop bit.
If no MAC control terminal is connected transparent mode must be switched off.
Note: Detailed information on transparent mode and the necessary parameters are provided in
the MAC manuals.
f) Modem Transmission between a PC and a MAC
Data transmission by modem allows you to conduct remote maintenance on stored program
control from a PC. Note, however, that data transmission settings between a PC and a MAC can
differ from the default transmission settings of the PLC. The following diagram illustrates the
communication path:

GX IEC
Developer

MAC control
unit

PLC
ACPU

Data transmission settings must
be identical on these devices.

AJ71C**

Default data
transmission settings:
Baud rate: 9,600
Parity: odd
Data bits: 8
Stop bits: 1

Important: Always make sure GX IEC Developer, the two modems and the MAC control
unit have the same data transmission settings.

Reference Manual

GX IEC Developer

7 - 10 Compiling and Downloading Programs

Settings in GX IEC Developer
ቢ Activate MAC transparent mode PLC
ባ Select the PC communications port with which the modem is connected.
ቤ Set the desired data transmission settings.
Important: Let us assume that you have set certain data transmission settings in transparent
mode which are different from the default. If you decide to disable transparent mode at a later
stage, without resetting the default values, GX IEC Developer will notice this and present a
warning. You can now either re-enable transparent mode or reset the data transmission
settings to the default values.

Default: MAC transparent mode remains turned off. Data transmission settings are reset to
default values.
Set MAC mode: MAC transparent mode is set again. Data transmission settings remain as set.

MAC control unit settings
ቢ Set the desired data transmission settings.
Detailed instructions for the control units are available in the MAC user’s manuals.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 11

Modem settings
ቢ Set the desired data transmission settings on the sending and receiving modems. You can
use any terminal program (e.g. Windows HyperTerminal) to configure the modem settings.

ባ Receiving modem: set “Auto Answer On” (Hayes-compatible modem: ATS0=0).

Data transmission procedure
ቢ Set data transmission settings in GX IEC Developer and on MAC.
ባ Receiving modem: set “Auto Answer On”.
ቤ Set data transmission settings on receiving and sending modems.
ብ Start connection: dial receiving modem.
ቦ Quit terminal software, though without hanging up.
ቧ Take the necessary steps in GX IEC Developer.
g) Close communications
When the PLC and other devices (e.g. the MAC terminal in transparent mode) are connected to
the Personal Computer via the same communication port, the communications must be closed to
release the COM port when switching between the two software applications GX IEC Developer
and MAC Programmer.
ቢ Click on the command Close communications in the Online menu.
Important: The communications can not be closed when GX IEC Developer is running in
monitor mode.

Reference Manual

GX IEC Developer

7 - 12 Compiling and Downloading Programs

Important: Follow the following precautions for access to the other station in the following Q,
QnA, and A CPU mixed system are as follows:
Request
target

Relay
station

Request
source

NET/10

NET/10

A CPU
selected
Q/QnA
CPU

AnA
CPU

ቢ Change the peripheral device to the PLC type of the request target. Communication can not
be performed, if the PLC type differs.
ባ The relay station used should be the Q or QnA CPU.
ቤ If GX IEC Developer is connected to the QnA CPU and the request target is the A CPU GX IEC
Developer can not communicate with the request target (A CPU).
ብ If GX IEC Developer is connected to the Q CPU and the request target is the Q CPU, GX IEC
Developer can not communicate with the request target (Q CPU) via the relay station
(QnA/A CPU).

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 13

7.3.2

Transfer Setup - Project
You can specify precisely which objects and source information in your project you want to
download.

How to set the transfer settings
ቢ In the Online menu select Transfer Setup, then select Project.
ባ Select the desired options in the Download Object and Source Information fields of the
dialog box.


PLC Parameter Downloads only the PLC configuration data to the PLC CPU.



Program Downloads only the compiled program code to the PLC.



PLC Parameter and Program Downloads both the configuration data and the compiled
program code to the PLC.



Downloadobject

Init System Addresses Initialises all system variables during download. This is done by a
direct memory write.


Download
source information

Symbolic Downloads the project together with all information, including the POUs not
defined in tasks.
If a project, which includes the setting structure (used in lower MM+ versions), is
downloaded the setting will be converted automatically to symbolic. This means that the
information in the project database will not be changed, but when the information is
queried, structure will be handled as symbolic.




Drive Before transferring the source data to the MELSEC Q/QnA series CPU, you must first
specify the drive to be used.



MELSEC IL (always drive 0) Reads the binary code from the PLC CPU and creates a POU in
MELSEC IL language with the standard name PRG_MAIN and a task with the standard name
MELSEC_MAIN.



UPLOAD mode

No Information Downloads only the binary program code to the CPU.

Source information Reads all the graphical and structural information from the PLC CPU in
addition to the binary code.

ቤ Confirm your selections with OK.
IMPORTANT: The first time you download a new project it is important to ensure that the
option PLC Parameter and Program is selected.

Reference Manual

GX IEC Developer

7 - 14 Compiling and Downloading Programs

7.3.3

Download symbolic information by menu command
The menu Project - Transfer includes a menu command to download symbolic information of
the current project to the PLC. This is independent of the current settings concerning source
information in the transfer setup.
This menu command will be shown only when the current PLC type is Q/QnA.

7.3.4

Ignore checks
If the project currently open in GX IEC Developer and the project on the connected PLC have
different time stamps, there is the possibility to continue the current action, although the
projects are not equal.

This dialog is used for the following actions:
n
n
n

Project online program change
Online change mode
Download symbolic information

During monitoring the button Ignore Checks is enabled. In this non-critical case the user is
allowed to monitor the projects although the projects are not equal. In all other cases the button
Ignore Checks is disabled.
It is not possible to ignore checks when starting a project online program change or entering
the online change mode.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 15

7.3.5

The Q/QnA’s File Structure
How to format and defragment the Q/QnA series drive
Before you can use the memory in the MELSEC Q/QnA series CPUs you must first format the
corresponding drive. This applies both for the internal RAM and the external memory cards.
ቢ Select Format Drive in the Online menu. The Format / Defrag dialog box is displayed.





Format Selecting this button starts the format procedure.



Reference Manual

Create system area... If a Q/QnA is connected to GX IEC Developer and a remote Q/QnA is
to be monitored, both PLCs (host and remote) have to be formatted with at least 1-K steps
system area available in the dialog Format / Defrag.
If one of both PLCs is not formatted with this system area, the remote Q/QnA cannot be
monitored.
Defrag Because of the file structure used in the Q/QnA series CPUs it is possible for the
drives to become fragmented after data have been written to the CPU, just as with a normal
hard drive. Selecting the Defrag button executes a procedure that defragments the contents
of the drive for better performance.

GX IEC Developer

7 - 16 Compiling and Downloading Programs

How to get File Information
ቢ Select File Info in the Online menu. The File Info dialog box displays information on the
memory and the files in the CPU.

Memory use (Internal RAM)

Size of download data Amount of downloaded data (unit: bytes)


Available memory Amount of memory available for use (unit: bytes)



Largest free block Largest free memory block available (unit: bytes)
In case this block is not large enough, use the Defrag option.

Files

Internal RAM Files stored in internal RAM (Drive 0)


IC Card A (RAM/ROM) Files in the RAM or ROM of the first memory card (Drives 1 and 2)



IC Card B (RAM/ROM) Files in the RAM or ROM of the second memory card (Drives 3 and 4)

Note: Full details on the file structure used by the MELSEC Q/QnA series CPUs can be found in
the CPU manuals.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 17

7.3.6

Downloading the Project
When you have checked the port settings and project parameters you can download your
project to the controller.

How to download the project to the PLC
ቢ Select Transfer in the Project menu, then select MEDOC to PLC.
The progress of the download process will be documented in a status window. The successful
transfer to the PLC is confirmed by a message box.
Check list before downloading
n
n
n

7.3.7

Has the project been compiled without errors?
Are the port parameters set properly for the transfer?
Are the project parameters set correctly?

Comparing the programs in the PLC CPU and GX IEC Developer
The function Verify in the menu Project - Transfer compares the program code stored in the
PLC CPU with the code of the current project compiled by GX IEC Developer.
Only sequence code differences are shown. Differences for SFC programs of A serires CPUs
which will be transferred to the main micro computer area will not be shown.
Detected differences in the program code can be shown in a Main or Sub Program Difference
window via the Show button. The verify results are listed as recompiled MELSEC IL, the
differences are highlighted in the error color. The left part of the window lists the project code,
the right part of the window lists the uploaded PLC code.
When the Main or Sub Program Difference window is opened the following menu items are
available in the Tools menu:


Next Difference Next Difference or the tabulator key will position the text in the window so
that the first line of the next difference is the top most line. The top most line will be selected.
The according calltree, number of network and for IL and ST the line in the network of the
selected line are shown in the status bar.If no next difference exists, the menu item is greyed.



Previous Difference Previous Difference or the shift tabulator key will position the text in
the window so that the first line of the previous difference is the top most line. The top most
line will be selected.The according calltree, number of network and for IL and ST the line in
the network of the selected line are shown in the status bar. If no previous difference exists,
the menu item is greyed.



Goto Editor
Goto Editor or a double click on a selected line will open the according POU body. In IL/ ST
the according line and in LD/ FBD the according network is positioned to the visible area and
marked with the browser colour in the network column.
If no POU body relates to the selected line a message window is opened to inform you of this
circumstance. The message text will be “The selected line belongs to code generated for task
or program handling. No editor could be opened.”



Show Step Number
This menu item is checked as default. If it is checked, the step number for each instruction
for the code of the project and of the PLC are displayed.
If it is not checked, the step number are not displayed. If a line is selected and the step
number are not displayed, the line is marked with a small box in front of the instruction.

Reference Manual

GX IEC Developer

7 - 18 Compiling and Downloading Programs

7.3.8

Online Changes
There are two different ways to make changes to programs when the controller is in RUN mode:


Project – Online Program Change This option compiles the modified program and
transfers it to the PLC.



Online – Online Change Mode Selecting this option compiles changes made in a
program network and transfers it to the PLC.
Tool for the menu command Online - Online Change Mode

After an online change has been made GX IEC Developer checks whether symbolic source
information is selected in the transfer setup. If this is the case, you will be asked whether you
want to download symbolic information. This dialog can be disabled for the current GX IEC
Developer session.
If you do not want to download any symbolic information or the option no information is
selected in the transfer setup, symbolic information is deleted on the PLC.
Important notes:
You should only ever make changes to one contiguous program range in the PLC at a time, and
the range should not be too large. If you want to be absolutely sure that you are not modifying
excessively large sections it is advisable to use Online Change Mode, as this mode only permits
you to make changes to one network at a time. After every change made to a network the
system automatically performs a program compare and transfers the modification directly to the
PLC. This approach ensures maximum program consistency and security.
In FX0 CPUs you can only change counters and timers when the PLC is in RUN mode.
Add new network
In the Online Change Mode new networks can be added to programs of the type IL, LD, FBD,
and MIL in the editors. To add a new network, in the Edit menu select New Network. From the
opening submenu select where to insert the new network: Top, Before, After, Bottom.
In the ST editor (Structured Text) online changes can be performed in the network.
Recover Online Changes
If the online change fails, a message box appears giving three options:

Undo
The changes recently made are rejected and the unmodified network saved at the beginning is
recovered. GX IEC Developer remains in online change mode. Additional Undo/Redo in the
menu Edit is not possible.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 19

Continue
The changes recently made are kept and you have the possibility to correct the faulty network
manually. Recent changes can be restored by means of the functions Edit - Undo and Edit Redo.
GX IEC Developer remains in online change mode.
Abort
The changes recently made are kept and the online change mode will be left. Recent changes
can be restored by means of the functions Edit - Undo and Edit - Redo.
Via mouse clicks to the navigator area the online change mode will be left.
If you have made changes, you are asked whether you want to remain in the online change
mode. Additionally you have the option to undo the changes which have already been done.

Yes
Leaves the online change mode and undoes the changes
No
Leaves the online change mode and keeps the changes
The project is now inconsistent. The online change mode can be reactivated by compiling the
project and redownloading it into the PLC.
Recent changes can be restored by means of the functions Edit - Undo and Edit - Redo.
Cancel
Remains in online change mode and keeps the changes (see Continue).
Code Generation Options
In the Extras - Options menu the Code Generation command is available (refer to 2.9.1).
The file structure used in the CPUs of the MELSEC Q series makes it necessary to define an
additional program range (in units of steps) for online changes when you are using these
controllers.

Reference Manual

GX IEC Developer

7 - 20 Compiling and Downloading Programs

7.4

Exporting
When you perform an import/export both the PLC program data and all the parameter settings
are now imported and exported.

7.4.1

Exporting an GX IEC Developer project into an ASCII file
You can export and save the contents of your projects in ASCII format for archiving or to provide
the information to others. The ASCII file contains all the project data and has the added
advantage that it takes up significantly less storage space than the contents of a complete
project directory.

How to export the entire project
ቢ Select the command Other in the Project menu, then select Export.
A dialog box is displayed.
ባ Enter the name for the ASCII file.
ቤ Click on the OK button.
The progress of the export process is documented in a status window.

How to export individual objects
ቢ Select the objects in Project Navigator you wish to export.
ባ Select the command Export in the Object menu.
A dialog box is displayed.
ቤ Enter the name for the ASCII file.
ብ Click on the OK button.
The progress of the export process is documented in a status window.

7.4.2

Export to EPROM
This function stores an ASCII file in Motorola format which can then be used to program PLC
EPROMS with a standard EPROM programmer. Every line in the ASCII file contains the
corresponding hardware address and values. The Export to EPROM command is in the Other
submenu of the Project menu.

7.4.3

CSV variable export
The menu item Extras - Export Variables exports all variables defined in the GVL and the POU
header of a project in the CSV (Comma Separated Variables) format into a text file. This file can
be opened in external tools, e.g. process visualisation or Microsoft Excel.
Before the function is available, the project must be compiled. Besides the variable declarations
(including class, identifier, address, type, initial value, comment), the exported file contains
general project information (e.g. project name and GX IEC Developer version number).
The options for the CSV variable export can be set under Extras - Options - CSV-Export
(refer to 2.8.6).

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 21

7.5

Importing
When you perform an import/export both the PLC program data and all the parameter settings
are now imported and exported.
GX IEC Developer provides a number of data import functions, which are listed briefly below.
Importing Programs from Files
n
Import a GX IEC Developer ASCII file
(Project - Other - Import) (Object - Import)
n

n

Import a GX IEC Developer ASCII file
(Tools - Import - GX Developer Network)
Import a MELSEC print file
(Tools - Import MEDOC Network)

Importing Programs from the PLC CPU
n
Symbolic Upload: Upload the project from the PLC CPU, together with all graphical
information (Project - Transfer - PLC to MEDOC (Symbolic))
n

7.5.1

MELSEC Upload: Upload the project from the PLC CPU in a MELSEC network
(Project - Transfer - PLC to MEDOC (MELSEC))

Importing GX IEC Developer ASCII files
A project saved as an ASCII file can be imported selectively. If you do not create a new project
before performing the import the selected objects are added to those in the current project. This
applies for all POUs, the tasks, DUTs and the global variables. The import function only works on
ASCII files saved with the GX IEC Developer Export function!
Note: You must first create an export file before you can perform an import.
Importing a large ASCII file may take a while without any indication.

How to import the entire project
ቢ Select the command Other in the Project menu, then select Import.
A dialog box is displayed.
ባ Select the desired ASCII file.
ቤ Click on the OK button.
The progress of the import process is documented in a status window.

Reference Manual

GX IEC Developer

7 - 22 Compiling and Downloading Programs

How to import individual objects
ቢ Select the command Import in the Object menu.
A dialog box is displayed in which you can select the objects that you wish to import into the
new or existing project.

ባ Mark the check boxes of the objects you wish to import.
– Data Unit Types (DUTs)
– Data Units Variables
– POUs
– Global Variables
– Tasks
– PLC Parameter
– User Objects
– User Libraries
ቤ Click on the OK button.
A dialog box is displayed.
ብ Select the desired ASCII file.
ቦ Click on the OK button.
The progress of the import process is documented in a status window.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 23

7.5.2

Importing GX Developer ASCII files
GX Developer (former GPP/WIN) ASCII files can be imported. The ASCII file must have been
exported from GX Developer by the separate software package GX Converter.
Open any editor of the type IL or MELSEC IL and select a network. In the Tools menu select the
item Import GX Developer Network. Select the required file from GX Developer (text or CSV)
to be imported into the selected network.
Note: Functions not supported by GX IEC Developer are ignored during the import (e. g. device
comments, initial values, program execution types).
SFC programs can not be imported.
The data to be imported must comply with the following requirements:
Common:
The maximum length of an import line is limited to 512 characters.
The width of the different datafields is limited to the following values:
n
n
n
n
n
n

Step number:
Line statement:
Instruction:
P/I-Statement:
Note:
Device:

7
64
15
64
32
15

Text files:
n

n

n

n

n

Reference Manual

Text files have to start with a step number followed by a blank (‘ ‘); otherwise the text file is
not recognized as a text file
Line statements have to start with a step number, followed by one or more blanks, followed
by a ‘;’ and followed directly with the linestatement.
Sample:
7 ;I am a linestatement
Notes may not start with a step number and can be located wherever in the importline; they
have to be enclosed by ‘ & lt; ’ and ‘ & gt; ’
Sample:
& lt; I am a Note & gt;
P/I-statements may not start with a step number and can be located wherever in the import line;
they have to be enclosed by ‘[’ and ‘]’. Separate Statements must start with a ‘*’ before the ‘[‘.
Sample:
*[I am a separate Statement]
[I am an embedded Statement]
If a line only contains device data and no statement, the device information must start in
column 25, columns 9 to 24 must be blank (‘ ‘)

GX IEC Developer

7 - 24 Compiling and Downloading Programs

CSV-Files:
n

n
n
n
n
n
n
n
n
n
n

n

n

7.5.3

CSV-files have to start with a step number followed by a comma (‘,’), otherwise CSV-Files are
not recogniced as CSV-Files
Step numbers must be located in column 1
Line statements must be located in column 2
Instructions must be located in column 3
Devices must be located in column 4
Column 5 must be empty
P/I statements must be located in column 6
Noten must be located in column 7
Columns 8 and 9 must be empty
Each line must contain exactly 8 separators
Notes, line statements and P/I statements, which contain one or more ‘,’ must be enclosed
with quotes ‘”’
Quotes within notes, line statements and P/I statements must be musked with another
quote; the whole statements must be enclosed with quotes
Separate P/I-statements must start with ‘*’

Importing MELSEC MEDOC print files
Print files generated by MELSEC MEDOC (DOS version) can be loaded into IEC or MELSEC
Instruction Lists as MELSEC networks. The POU into which you wish to load the file must be
open and the network must be selected. Please note that performing this import procedure
automatically overwrites the contents of the selected network in the body!

How to import MELSEC MEDOC print files
In MELSEC MEDOC (DOS version):
ቢ Select a file name as the printer port. The extension TMP is added to the file name
automatically.
ባ Select only the Instruction List and Name List in the program listing. Make sure that the
header is switched off!
ቤ Start the print procedure.
In GX IEC Developer:
ብ Open the body of a MELSEC Instruction List or create a new MELSEC Instruction List POU.
This new POU must be a Program (PRG).
ቦ Select New Network in the Edit menu, then select MELSEC Before from the submenu
displayed.
ቧ Select Import MELSEC Network in the Tools menu.
ቨ In the dialog box displayed specify the drive and directory where the import file is stored and
select the import file (TMP). Confirm your selection with OK. An option box is opened.
GX IEC Developer checks whether the specified file is a valid import file, and whether it
contains program code and symbolic names. The default settings displayed in the option box
depend on the results of this check. For example, if no symbolic names are found this option
will be displayed in light grey and is not selectable.

GX IEC Developer

Reference Manual

Compiling and Downloading Programs 7 - 25

ቩ Confirm the selections with OK.
The progress of the import process is documented in a status window.


MELSEC Program Import only the program code lines of the Instruction List.



Options

MELSEC Symbolic Names Import only the Name List. The entries from the list are inserted
both in the global variables declaration table and in the header of the POU. Comments after
relays and data registers are converted into symbolic names and imported as comments.
When this conversion is performed spaces, quotes and periods are either deleted or replaced
with underline characters in accordance with the IEC standard.

The translation of the symbolic names can result in duplicate names for some variables. If this
happens the following dialog box is displayed:

The first two entries show the name of the existing variable and the name that the program
proposes to use to overwrite this variable.
Replace Replace the old variable name with the new one.
Repl. all Replace all existing variable names with new names. If you select this button the
program will replace all subsequent variables without prompting.



Skip Skip this variable name without replacing it. The name is also not added to the Variable List.



Reference Manual




Buttons

Skip all Skip all variables with duplicate names and do not add any of them to the Variable
List. If you select this button the program will skip all subsequent duplicate variables without
prompting.

GX IEC Developer

7 - 26 Compiling and Downloading Programs

7.5.4

Upload PLC to MEDOC
The upload function reads the binary code from the PLC CPU and creates a POU in MELSEC IL
language with the standard name PRG_MAIN and a task with the standard name
MELSEC_MAIN. In addition to the binary code all the graphical and structural information from
the PLC CPU can be uploaded.

How to upload project code from the CPU
ቢ In the Project menu select Transfer. Then select PLC to MEDOC...
ባ Select the PLC type and confirm with OK.
ቤ The upload must be stored in a new project. Enter the name of the new project to be created
in the dialog box displayed.
ብ Confirm your entry with OK.
ቦ A dialog box is displayed showing a selection of ports for the transfer procedure:
– CPU Port
– Computer Link
– Ethernet
ቧ Select the appropriate port for your configuration and confirm with OK.
ቨ A dialog box is displayed showing a selection of UPLOAD modes:
- MELSEC IL
- Source Information
ቩ Select the required UPLOAD mode and confirm with OK.
When you select symbolic source information to be uploaded from the PLC, GX IEC
Developer will check whether symbolic information is available on the PLC.
The progress of the import procedure is documented in a status window.
Absolute Label
Absolute labels are used as jump destinations when PLC programs are uploaded in GX IEC
Developer. Absolute labels are specific pointer addresses (e.g. P20). Every program section
identified with a pointer in the original PLC program is loaded to a separate MELSEC network.
The absolute label is P_20

Absolute labels can also be assigned by the user, but you must be very careful to use the correct
syntax. Only addresses with the format P – underline – address are interpreted as absolute labels.
P_20

Reference to pointer P20 (absolute label)

P20

Reference to a free pointer P** (not an absolute label)

Note: The labels with the format LAB_20 generated when you import MELSEC MEDOC print
files are not absolute labels!

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 1

8

Diagnostics Functions and Online Operation
8.1

Debugging
The functions in the Debug menu allow to perform precise troubleshooting and error analysis
on your progress.

8.1.1

PLC diagnostics
A CPU diagnostics
The status and the error codes of the CPU can be displayed. In the Debug menu select PLC
Diagnostics. The PLC will be checked and the dialog below is opened.








³ PLC Panel
Shows the operation status of the target PLC.
· Error display (Present Error)
This section shows whether the displayed error is a present error or an error from the error log.
Click on the Present Error button to display errors currently occurring in the connected CPU.
For an AnA or AnU CPU click on the Error log button to display recent error messages from
an error log. The Clear Log button clears this error log.
» Monitor
The Start monitor button starts the communications with the PLC and the error display is
updated.
The Stop monitor button stops the communication with the PLC and the error display.
Clicking on Error log or Clear Log automatically stops monitoring.
¿ Error display (Error message)
This section lists the detected errors.

Reference Manual

GX IEC Developer

8 - 2 Diagnostics Functions and Online Operation

QnA CPU diagnostics
The status and the error codes of the CPU can be displayed. In the Debug menu select PLC
Diagnostics. The PLC will be checked and the dialog below is opened.










³ PLC panel
Shows the PLC panel status of the target PLC.
· PLC operation status
Shows the PLC operation status of the target PLC.
» Monitor
The Start monitor button starts the communications with the PLC and the error display is
updated.
The Stop monitor button stops the communication with the PLC and the error display.
Clicking on Error log or Clear Log automatically stops monitoring.
¿ Swap module during run
Select the base number and the slot number for the module to be swapped and click on
Detach target.
´ Error display
Click on the Present Error button to display errors currently occurring in the connected CPU.
Click on the Error log button to display recent error messages from an error log. The Clear
Log button clears this error log.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 3

Q CPU diagnostics
The status and the error codes of the CPU can be displayed. In the Debug menu select PLC
Diagnostics. The PLC will be checked and the dialog below is opened.








³ PLC operation status
Shows the PLC operation status of the target PLC.
· Monitor run/stop
The Start monitor button starts the communications with the PLC and the error display is
updated.
The Stop monitor button stops the communication with the PLC and the error display.
Clicking on Error log or Clear Log automatically stops monitoring.
» Error log
This section lists the detected errors.
¿ Error status
This section shows whether the displayed error is a present error or an error from the error log.
Click on the Present Error button to display errors currently occurring in the connected CPU.
Click on the Error log button to display recent error messages from an error log. The Clear
Log button clears this error log.

Reference Manual

GX IEC Developer

8 - 4 Diagnostics Functions and Online Operation

FX diagnostics






³ PLC panel
Shows the PLC panel status of the target PLC.
· Error indication
Click on the Current Error button to display errors currently occurring in the connected CPU.
The date and time values refer to the moment when the Current Error button was activated
but not when the error occurred.
The currently occurring errors are listed including the error code and error message.
» Monitor start/stop
The Start monitor button starts the communications with the PLC and the error display is
updated.
The Stop monitor button stops the communication with the PLC and the error display.
Note: Double-click on a present/current error shown in the list to open the Error details dialog.
The Error details dialog shows the content of SD5 – SD15 (common error information) and
SD16 – SD26 (individual error information).
Double-click

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 5

8.1.2

Network Diagnostics
From a selectable target host station the status of a MELSECNET (II) or MELSECNET/10 network
can be checked.














³ Tabs for link modules
Select the tab for the link module for displaying the diagnostics results (AnN or AnA CPUs
only support 2 modules).
· Network information
Shows information on the network the selected target host station belongs to (for
MELSECNET (II) the network number and group address are not displayed).
» Link information
Shows the network status.
¿ Monitoring
The Start monitor button starts monitoring. In RUN mode the display will be updated.
The Stop monitor button stops monitoring.
´ Communication information
Shows the communications status of the selected network (for MELSECNET/10 only the
communications status is displayed).
² Error History Monitor (see below)
Network Monitor Details (see below)
Other station information (see below)
¶ Network diagnostics (see below)
Network test
Setup confirmation test
Station order check test
Communication test

Reference Manual

GX IEC Developer

8 - 6 Diagnostics Functions and Online Operation

Note: In a MELSECNET (II) network at maximum 2 link modules can be installed.
In a MELSECNET/10 network at maximum 4 link modules can be installed.
The network diagnostics check the network the connected host station belongs to. To change
the network simply change the connection to the host station and select the connection to
another host station.
For the connection to remote I/O modules the network diagnostics are not supported.
If the connection is established via a E71 unit the monitoring of an AnU CPU is performed like
for an AnA CPU. MELSECNET (II) information can be monitored but no MELSECNET/10
information.
Error history Monitor
This button in the Network diagnostics dialog opens a dialog that monitors and lists
communication errors in an error history. Communication errors are listed separately for
the forward and the reverse loop. Error history details can be monitored and the error history
can be cleared.

Network Monitor Details
This button in the Network diagnostics dialog opens a dialog that displays network monitor details.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 7

Other station information
This button in the Network diagnostics dialog opens a dialog that monitors other stations
connected to the MELSECNET (II) or 10.
The following items are available:
n
n

n

n
n

Reference Manual

Network information: Shows information on the network of the selected target host station.
Other station information/Error information: If an error in a station, a stopped station, a
reserved station, or a station with external power supply the error information field reads
ERR. Click on the respective button to select an object for the error information to show
detailled error information.
Display field for detailled error information: Shows the status of the relevant station for the
selected item.
Start monitor: Starts monitoring.
Stop monitor: Stops monitoring.

GX IEC Developer

8 - 8 Diagnostics Functions and Online Operation

The following information on other stations is available for the A series:
MELSECNET /10
MELSECNET /10

MELSECNET (II)

Control Station

Normal Station

Loop

Branch

Loop

Branch

Loop

1 Communications Status

Ȝ

Ȝ

Ȝ

Ȝ

2 Data Link Status

Ȝ

Ȝ

Ȝ

Ȝ

Information on
each Station



MELSECNET (II)
Master Station

Master

Local

Branch





Ȝ

Ȝ

Ȝ



Ȝ

Ȝ





3 Parameter Status

Ȝ

Ȝ

(—)

(—)

Ȝ

Ȝ

Ȝ



4 CPU Operation Status

Ȝ

Ȝ

Ȝ

Ȝ









5 CPU RUN Status

Ȝ

Ȝ

Ȝ

Ȝ





Ȝ

Ȝ

6 Loop Status

Ȝ



Ȝ



Ȝ



Ȝ



7 Res. Station Designation

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ





8 External Power Supply

















9 Error Search Status













Ȝ



Ȝ = available, – = not available
The following information on other stations is available for the Q/QnA:
MELSECNET /10
MELSECNET /10

MELSECNET (II)
MELSECNET (II)

Normal Station

Loop

Branch

Loop

Branch

Loop

Branch

1 Communications Status

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ



2 Data Link Status

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ





3 Parameter Status

Ȝ

Ȝ

(—)

(—)

Ȝ

Ȝ

Ȝ



4 CPU Operation Status

Ȝ

Ȝ

Ȝ

Ȝ









5 CPU RUN Status

Ȝ

Ȝ

Ȝ

Ȝ





Ȝ

Ȝ

Information on
each Station

Master Station



Control Station

Master


Local


6 Loop Status

Ȝ



Ȝ



Ȝ



Ȝ



7 Res, Station Designation

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ

Ȝ





8 External Power Supply

Ȝ

(—)

Ȝ

(—)

Ȝ

(—)





9 Error Search Status













Ȝ



Ȝ = available, – = not available

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 9

Network diagnostics/Network test
This button in the Network diagnostics dialog opens a dialog where you can start or stop the
link operation for the MELSECNET/10 host station, selected stations, or all stations.
The following items are available:
n
n
n

Network information: Shows information on the network of the selected target host station.
All stations operating status: Displays the operating status of the tested modules.
Link start/stop:
Link start: Stations that were stopped by the host station can be started. Stations that were
stopped by another station can not be started.
Link stop: Stations can be stopped by the host station or another station.
Force link start: Stations can be started regardless of whether they have been stopped by by
a host station or another station.
However, the start can not be forced, if all stations were stopped. A start can not be forced
neither, if for the link target another station is the target.
By monitoring SB and SW can be determined whether a forced start of a peripheral device
can be performed. By monitoring SW0000 – SW0004 can be determined whether the
execution was started or stopped by a host station.
A start can be forced, if the connection is established via C24, UC24, or QC24.
Via a MELSECNET (II) or 10 interface board the start can not be forced.
Via E71/QE71 the start can not be forced.

Reference Manual

GX IEC Developer

8 - 10 Diagnostics Functions and Online Operation

Network diagnostics/Setup confirmation test
This button in the Network diagnostics dialog opens a dialog where you can check the status
of the station number, network address, and group address.
The following items are available:
n
n

n

Network information: Shows information on the network of the selected target host station.
Setting check test:
Parameter settings: All stations that are setup in the parameters except the reserved station
are tested (If no network settings are setup, all stations are tested).
All stations: All stations are tested. No specified station is addressed.
Target module: The module by default selected for the for the line monitor is specified. If
no MELSECNET/10 module is connected, an error message is returned.
Execution results:
Station number: Shows the station number up to the specified station
(64 station numbers max.).
Loopback station: If the same loopback station was assigned to more than one station a “*”
is displayed.
Network number: If the same network number was assigned to more than one station, “*”
is displayed.
Group number: Shows the group addresses of the stations for which the setup confirmation
test is performed. For a remote I/O network faulty stations are indicated by a blank.
Reserved station: For stations specified as reserved stations “*” is displayed (if parameter
confirmation was selected as test object).
Error: If a station is reserved in the parameter settings or if a module in all selected stations
is faulty “*” is displayed.
Error network type (Q series only): Stations for which the parameter settings and current
link do not match are indicated as “*”.
Double multiplex remote master station (Q series only): Stations with more than one sub
master station within the same network are indicated by “*”.
Double parallel remote master stationXXX (Q series only): Stations with more than one
sub master station within the same network are indicated by “*”.

Note: The tests can not be performed for more than one station at one time.
During the test execution the scan execution is stopped.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 11

Network diagnostics/Station order check test
This button in the Network diagnostics dialog opens a dialog where you can check the station
order in the forward and reverse loops of a MELSECNET/10.
The following items are available:
n

n

n

Network information: Shows the information on the network of the selected target host station.
The loop status is displayed for forward loops, reverse loops, forward/reverse loops, or
loopback. The displayed total number of stations includes also the reserved-by station.
Loop test:
Parameter settings: All stations specified in the parameter settings except the reserved
stations are tested (If no network settings were specified, all stations are tested).
All stations: All stations are tested. No specific station is addressed.
Target module: The module by default selected for the for the connection monitor is
specified. If no MELSECNET/10 module is connected, an error message is returned.
Execution results: The station order is displayed in forward loop and reverse loop direction
beginning from the host station.
For loopback only the station order in forward loop direction is displayed.

Note: The tests can not be performed for more than one station at one time.
During the test execution the scan execution is stopped.
Network diagnostics/Communication test
This button in the Network diagnostics dialog opens a dialog that displays general
communication test results.

Reference Manual

GX IEC Developer

8 - 12 Diagnostics Functions and Online Operation

8.1.3

System Monitor
The System Monitor displays comprehensive information on the entire connected PLC system.
The System Monitor supports Q series PLCs only.
In the Debug menu select System Monitor to open the following dialog:

Installed status
This section illustrates the selected base and shows the installed modules and vacant slots
(”not mounted”).
Base
This section lists the connected bases and displays the error status coded by colors (see section
“Status”). If several bases are connected, the base to be displayed can be selected via radio buttons.
Parameter status
This section gives additional information on the installed modules and their addresses.
Status
Indicates the color codes for the status displayed in the “Base” section.
Start monitor/Stop monitor
Starts or stops monitoring.
Diagnostics
Also available in the context menu as Diagnosis feature execution.
Opens appropriate diagnostics functions for the selected module:
n
n

n

GX IEC Developer

For a CPU module the PLC diagnostics dialog (see section 8.1.1) is opened.
For an Intelligent Function Module the Intelligent Function Module Utility (see section 8.6)
is opened.
For network modules the Networks Diagnostics dialog (see section 8.1.2) is opened.

Reference Manual

Diagnostics Functions and Online Operation 8 - 13

Module’s Detailed Information
Also available in the context menu as module’s detailed information or via double-click on a
module.
Opens the following dialog that displays detailed information on the selected module.

Note: It may take a few seonds until all details are displayed especially those for the error display.
Error History: Displays the stored error history.
H/W Information: Opens a dialog that displays more details on the LED and SW status.
Start monitor: Starts monitoring.
Stop monitor: Stops monitoring
Base Information
Opens the following dialog that dislays information on the selected base.

Reference Manual

GX IEC Developer

8 - 14 Diagnostics Functions and Online Operation

Product Inf. List
Opens the Product Information List that gives an overview of the connected PLC system. The
Product Information List can be exported into a CSV file (comma separated value) via the CSV
file creating button. The CSV format can be imported by many other applications.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 15

8.2

PLC System Error Check

8.2.1

System errors
If a system error occurs GX IEC Developer outputs the corresponding error code. You can obtain
additional information on the error message by selecting the Help button.

8.2.2

User-defined errors
Error flags combined with an error location program make it possible to display errors that occur
in the course of the process. If an error is encountered an error flag (F) is set, together with a
special relay (M) to indicate the presence of an error condition (not valid for the FX series).

n
n
n



Special relay M9009 ᕃ is used to register the presence of a set error flag.
Special register D9009 ᕃ stores the first set address of the error flag.
Special register D9124 ᕃ: F0 – F127 are programmed in the MELSEC network with the OUT
function.
Not valid for FX series.

The text for the error messages must be stored in the error file USER_ERR.TXT in the current
project’s directory.

How to create an error messages file
ቢ Open the Windows Notepad editor (you can also use any other editor that saves files in ASCII
format without formatting codes).
ባ Create a new file.
ቤ Enter the error messages, one message per line.
Syntax
F0; Text1
F1; Text2
You must enter a space between the semicolon and the text of the error message.
ብ Store the file as USER_ERR.TXT in the current project’s directory.

Reference Manual

GX IEC Developer

8 - 16 Diagnostics Functions and Online Operation

8.2.3

Hardware Diagnostics
Selecting HW Diagnosis in the Debug menu shows all hardware errors registered
(not available for FX series).


M9000 (A) / SM60 (Q/QnA) Fuse blown. This relay is set as soon as a blown fuse is
registered in one or more modules in the system. The relay will remain set even after you
switch back to normal status. (Does not apply for A2C CPUs.)



M9002 (A) / SM61 (Q/QnA) I/O module verify error.



M9005 (A) / SM53 (Q/QnA) Mains power drop. The relay is set after a power drop of no
more than 20 ms. You can reset the relay after switching the power supply off and on again.



M9006 (A) / SM52 (Q/QnA) Battery low. The voltage of the retentive memory battery has
dropped below the minimum level. This flag is reset when the battery is replaced.



M9007 (A) / SM51 (Q/QnA) Battery low (latch relay). The voltage of the retentive memory
battery has dropped below the minimum level. This flag is reset when the battery is replaced.



M9026 (A) / SM211 (Q/QnA) Clock data error. Set in the event of incorrect clock data
(registers D9025 – D9028). (Only for AnN/AnS CPUs.)

Hardware errors are indicated by cross symbols instead of minus signs on the corresponding
buttons. Clicking on a button with a cross displays context-sensitive help for that error.
Note: You will find detailed descriptions and information on special relays and special registers
in the controller manuals.

8.2.4

Scan
The Scan command in the Debug menu provides a statistical display of the scan time
performance of the program in the PLC CPU.
The program execution cycle periods can vary depending on status conditions, e.g. whether
inputs are polled during the cycle or not. The PLC CPU logs the following scan times:




Minimal Scan Time The last minimum scan time saved (special register D9017 in the A
series; D8011 in the FX series)



GX IEC Developer

Actual Scan Time The current program cycle time (special register D9018 in the A series;
D8010 in the FX series)

Maximal Scan Time The last maximum scan time saved (special register D9019 in the A
series; D8012 in the FX series)

Reference Manual

Diagnostics Functions and Online Operation 8 - 17

8.3

The Device Editor
The device editor is a tool for displaying and editing the contents of the PLC-CPU’s word and bit
devices. The main element of the device editor is a table that is very similar to a Microsoft Excel
worksheet, both in its appearance and in the way it is used.
You can read the values from the CPU to the table, and after editing them you can then write
the new values back to the CPU. Additionally, you can also write the table contents to an
external file and load external files for editing. These files are stored in Excel 4.0 format, which
makes it possible to edit them with Microsoft’s Excel spreadsheet program as well.
Maximum table size is 16,383 lines and 255 columns, which means it can handle a total of
4,177,665 cells. Effectively, the number of bit and word devices you can load to the table is only
restricted by the amount of available memory on your computer.
Warning prompts are displayed before all operations that alter table ranges, before critical
operations (e.g. writing to CPU inputs) and before you close the device editor.

8.3.1

The worksheet
The Device Editor option in the Debug menu opens the Device Edit window, which contains
the worksheet table in which all editing actions are performed.
·

³

»

¿

´
²

The leftmost column of the table · contains the first of a consecutive sequence of devices. Each
series of devices is displayed across a table line »; the numbers of the devices following the first
device are obtained by adding the values shown at the heads of the column ³. The values of
the devices are contained in the individual table cells ¿.
The current display mode ´ of the selected cell is shown underlined. The display mode is set in
the pop-up menu (right mouse button).
Commands can be accessed by clicking on the buttons ² or with the pop-up menu, which can
by displayed by clicking with the right mouse button or pressing ¨š.

Reference Manual

GX IEC Developer

8 - 18 Diagnostics Functions and Online Operation

8.3.2

Buttons


Read from PLC Reads the values of word and bit devices (registers) from the PLC. You can
choose to read either the entire table or a selected table range.



Write to PLC Writes the table values to the PLC’s word and bit devices (registers). You can
write either the entire table or a selected table range.
Selected Devices: Read/write only the devices selected in the table.
All Devices: Read/write all the registers in the table.



Read from File Loads an external file stored in Excel 4.0 format.



Write to File Writes the GX IEC Developer device table data to an external file in Excel 4.0
format.

IMPORTANT: The device table settings are not stored with the GX IEC Developer project. They
are lost irrevocably when you close the Device Edit window. If you want to access the data
again later you should always save the table to a file before closing the edit window.

8.3.3

The pop-up menu
To display the pop-up menu click with the right mouse button or press ¨.





Copy Copies the contents of selected cells to the clipboard (§C)



Paste Pastes the content of the clipboard to the table (§V)



GX IEC Developer

Cut Copies the contents of selected cells to the clipboard and deletes them from the table
(§x)

Paste Text Opens a dialog box in which you can enter ASCII text to paste to the table. ASCII
characters are only displayed in the table in the ASC display mode. You cannot enter more
characters than the selected device can store. A data register can only store two ASCII
characters, for example. You can enter more characters by selecting several cells (i.e. a series
of registers) and entering ASCII text.

Reference Manual

Diagnostics Functions and Online Operation 8 - 19



Insert Devices Displays this dialog box:
Device: List of the available devices for selection.
All: Selects the entire range of devices for insertion in
the table.
Adresses: Allows specification of a specific address
range.
Display Mode: Specifies the display mode for the new
registers



Delete Devices Deletes the selected device or device range. A prompt is displayed asking for
confirmation before the delete operation is executed.



Find Device Searches for specific devices. You can select the search direction.



Find Value You can also search for a specific value in a device register. Again, you can
specify the search direction.



Replace Value Search and replace function for replacing device register values.



Display Mode Displays this dialog box:
Display Mode: Mode for displaying the selected devices
Register: Selects 16 or 32 bit register display.



Options Displays the following dialog box in which you can set the basic options for the
table structure:

Number of Columns
Automatic: 8 rows for octal registers, 10 rows for decimal registers, 16 rows for hex registers
Input Number: You can enter a value between 1 an 255.
Number of Rows
Maximum Number (16383): Sets the rows to the maximum of 16,383 rows.
Input Number: You can enter a value between 1 and 16,383.

Reference Manual

GX IEC Developer

8 - 20 Diagnostics Functions and Online Operation

Use Colors
When this check box is selected the table is displayed using different colors.
Additional Safety Inquiry
When this check box is selected the system displays an additional prompt asking for
confirmation for some critical operations.

Inserting devices with the Insert Devices dialog box
Open the Device Edit window and select the top left cell of the table.
ቢ Click with the right mouse button to open the pop-up menu.
ባ Click on Insert Devices with the left mouse button to display the Insert Devices dialog box.
ቤ Select the device type, address range and display mode, then click on OK.
Data registers D
Address range: D12 – D16
Display mode: Decimal

The devices are inserted in the table. Initially, all the devices are given a default value of 0.
Devices D12 – D16 have been
inserted in the table.

D12

D13

D14

D15

D16

Inserting devices directly
Open the Device Edit window.
ቢ Click in any cell in a free line. All the cells in the line must be empty!
ባ Enter the device. The system automatically switches to editing mode when you make an
entry. GX IEC Developer only accepts valid entries. If you make an incorrect entry editing
mode will remain active.
The inserted device is then displayed in the leftmost table column.
Note: When you enter registers directly you can only store one register in a line; the remaining
cells in the line are disabled and cannot be selected.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 21

Entering device values
ቢ Select the cell where you want to enter the value.
ባ Enter the new value. The system switches to editing mode automatically when you make an
entry. GX IEC Developer only accepts valid entries. If you make an incorrect entry editing
mode will remain active.
Note: Double-clicking on a bit device (or pressing ´) toggles the value of the device between
0 and 1. Double-clicking on a word device activates editing mode.

Entering 32-bit values
A 32-bit value is stored in two 16-bit registers.
ቢ Select the first of the two table cells.
ባ Hold down the¨ key and extend the selection to include the second cell using the mouse or
cursor key. Both cells now have a bold outline and the second cell is shaded.
ቤ Press§m to select the Display Mode dialog box from the pop-up menu.
ብ Select the 32-bit option in the Registers field.
ቦ Click on OK to link the two selected cells.
ቧ Enter a 32-bit value in the cell. GX IEC Developer will only accept valid entries.
Note: You can use the standard Windows mouse actions and key combinations in the device
table. Special key combinations are listed in the Appendix of this manual.

Reference Manual

GX IEC Developer

8 - 22 Diagnostics Functions and Online Operation

8.3.4

Editing tables in Microsoft Excel
Entries in Excel
D12 – D16
X5 – X9

Changing device designations
ቢ Overwrite the entry in D12 in leftmost colum, e.g. by entering D24.
The line now contains the five data registers D24 – D28.

Adding devices to a line
ቢ Select the cell in column +5 and enter the value to be contained by the new register D17.
ባ Click with the right mouse button to open the pop-up menu and select the Number Format
option.
ቤ Select the appropriate number format from the list in the dialog box.
The number formats in Excel correspond to the display mode in GX IEC Developer. These
formats are represented by a fixed number of spaces and the @ character:

BIN: 1 space
HEX: 2 spaces
ASC: 3 spaces
DEC: No spaces
OCT: 4 spaces

Note: Setting the correct number format (i.e. the right display mode) is absolutely essential
when you add new devices in an Excel table that you plan to reload in GX IEC Developer later!

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 23

8.4

The Monitor Function
The monitor function enables you to follow program execution and to check the status of
operands/devices in runtime. The data for monitor mode is read from the PLC itself.
GX IEC Developer supports different monitoring modes:
n
n
n
n

Program Monitor
Entry Data Monitor
Header Monitor
Link Monitor (see page 5-13)

Note: When the monitoring mode is activated all GX IEC Developer editing functions are disabled.

8.4.1

Inheritance
The monitor mode is inherited to objects that are opened by other objects they depend on.
Therefore, the monitor mode does not need to be enabled for depending objects manually.
For the following actions the monitor mode will be inherited:
Action

Monitor mode inherited to

Change instance of a function block

New instance

Zoom function blocl

Body of function block

Zoom function

Body of function

Open transition from SFC body

Action

Open new windows during tracking

8.4.2

Transition

Open action from SFC body

New window

Monitor Mode Options
In the Extras - Options menu you can specify options for the monitor mode.





Reference Manual

Displayed String Length Displaying long strings significantly reduces performance in
monitoring mode. It is thus advisable to limit the number of characters to be displayed.
Pollrate Interval at which the monitor polls the CPU, expressed in ms.

GX IEC Developer

8 - 24 Diagnostics Functions and Online Operation

8.4.3

The Online Toolbar
You can display an additional toolbar for online operations in monitoring mode.

The tools are described in the Appendix C.

How to display the online toolbar
ቢ Select Extras - Options - Editing and activate the Online Toolbar option.

8.4.4

The Program Monitor
In the text and graphical editors the values of all visible variables are displayed in the editing
window, and they are updated after every program scan. The variables shown are always those
lying within the current editing window pane. If you scroll the contents of the window or
change its size the system automatically shows the values of all new variables that come into the
window, and stops displaying the values of all variables that move out of the window.
Inputs and outputs that are set are displayed in the colours corresponding to the colour
parameter settings.
When you start monitoring in the Sequential Function Chart editor the active Steps in the current
window are shown in the colours set in the parameters. This enables you to follow which Step is
currently active.

How to open the Program Monitor window
ቢ Switch to Online mode by activating Monitor Mode in the Online menu or clicking on the
monitor mode icon:
Tool for activating the monitor mode

ባ Open and select the body of the POU that you wish to switch to monitoring mode.
ቤ Select Start Monitoring in the Online menu.
Active inputs and outputs are identified in colour.

Register D100 takes the value 255 of the base-8 literal.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 25

In addition to Program POUs you can also use the Program Monitor for function blocks and
functions. When you activate monitoring for the operand status of function blocks GX IEC
Developer first prompts you to specify the Instance of the function block for which you wish to
activate the Program Monitor.
In the body of the program there is a signal on
the inputs and outputs of Log_Add_1, which is
an instance of function block FB_1.

Log_Add_2 (an instance of function block FB_1)
has no signals on its I/Os …

... as a result, no signals are displayed for the
devices of fucntion block FB_1 in Monitor mode.
In Monitor mode, there would be signals in the
devices In_1, In_2 and Out_1 of FB_1.

How to stop the Program Monitor window
ቢ Activate the command Stop Monitoring in the Online menu.
Note: If you experience difficulties in distinguishing symbols that are closely spaced e. g. the “-”
and the “#” symbols in the example below in the default Arial font setting, switch to another
font such as Courier New or Fixedsys for better viewing.
Display in Arial font

Display in Courier New font

Refer to section 3.7 for details on the font selection.

Reference Manual

GX IEC Developer

8 - 26 Diagnostics Functions and Online Operation

8.4.5

The Entry Data Monitor (EDM) and the Header Monitor
The Entry Data Monitor can be used to group objects from the open project in order to obtain a
display of their current status. Several windows can be opened at once. The Header Monitor
essentially offers all the functions available in the Entry Data Monitor. The only difference,
although an important one, is that calling up the Header Monitor automatically displays the
objects of the active POU.
The status of the following objects can be monitored in the Entry Data Monitor: Global and
Local Variables, POUs and Tasks.
The central element of the Data Entry Monitor is a table which the user can configure himself.
The values in the table can be read from the CPU and also written back to the CPU after editing.
There is also the possibility of writing the table, i.e. the grouped objects, and the configuration
of the table into an external file, or of reading the data from an external file.
The table is restricted to a maximum of 16,383 rows and 255 columns. This means that a total
of 4,177,655 cells can be managed. The number of objects in the table is limited only by the
available memory on your computer.
A security function is available to prevent data being written into the CPU.
The worksheet
In the Online menu, the Entry Data Monitor command calls up the EDM window.

If a direct address (in the IEC and Mitsubishi Editor) was entered in lower-case letters, these
characters will automatically be converted into upper-case letters.
Rows including Boolean objects are highlighted if the respective object is active. The colour is
defined in the project settings.
By means of this option it is possible to monitor an object in the Mitsubishi Kn notation.
Example: K1M10 will monitor the relays M10 to M13.
The result is displayed in the result columns offering a suitable style, e.g. Value (bin), Value
(dec), Value (hex). The objects will be displayed in their respective representations.
Example: Bit pattern of M0 to M7 is displayed as 1000 1101.
In the column Value (bin) it will be displayed as 1000 1101.
In the column Value (dec) it will be displayed as 141.
In the column Value (hex) it will be displayed as 8D.
In the Mitsubishi Kn notation object values cannot be changed.
Note: The commands in the Edit and Tools menus can also be called up via the pop-up menu.
The pop-up menu appears if you press the right-hand mouse button or press the key
combination ¨š.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 27

The Edit menu
The following commands are available in the Edit menu when the window of the Data Entry
Monitor is active:




Next Object The object following the currently selected object is inserted. If the selection
marker is positioned on an Array entry, the next element of this Array is inserted. If the
selection marker is positioned on a numbered entry, the element with the next number is
inserted. In all other cases, the object with the next consecutive address is inserted. This
command is only available if the selected row contains an elementary object and the selected
object is not a sub-object.



Insert Forced Inputs (not for FX family) Inserts all user-forced input devices into the EDM.
The “Status” column indicates that they are “Forced” (see below). Forced inputs can be
cleared via Online - PLC Clear - Forced Inputs.



Insert Set Inputs (FX family only) Inserts all user-set input devices into the EDM. The
“Status” column indicates that they are “Set” (see below).



Reference Manual

Insert Object The Object List window appears containing all the objects available in the
current project. The objects can be selected via a group filter and a type ahead input field.

Insert Set Outputs Inserts all user-set outputs into the EDM. The “Status” column indicates
that they are “Set” (see below).

GX IEC Developer

8 - 28 Diagnostics Functions and Online Operation



Clear Device File All forced or set inputs and outputs are stored in the DeviceFile.MON in
the project path. This file is cleared.



Insert Row A new row is inserted in front of the selected row. As the EDM does not offer
copy and paste operations, you cannot insert several rows at once.



Delete Rows The selected row is deleted. You can also delete several rows at once. This
command is only available if the first object selected and the object after the last object
selected are not sub-objects.



Delete All All entries in the table and the table configuration are deleted. You are asked to
confirm the command before it is executed.



Close The EDM window is closed. All information is automatically saved. The information
concerning the current settings is stored in the MMP400.INI file and is loaded as the default
when the EDM is next called up.

The Tools menu
The following commands are available in the Tools menu when the window of the Entry Data
Monitor is active:


Read from PLC The data are read from the PLC and displayed in the EDM table. This
command is only available in Offline mode.



Write to PLC The data from the EDM table are written to the PLC. A dialog window appears
which allows you to choose whether only the selected objects or all objects are to be
transmitted. This command is only available in Offline mode.



Read from File The file previously created with the Write to File command is called up. This
command is only available in Offline mode.



Write to File Both the grouped objects and the configuration of the table can be saved in an
external file. This file has the file extension EDM. This command is only available in Offline mode.



Setup The Setup dialog window is opened, in which the EDM table can be configured and
the security function activated.
The columns for the EDM table are compiled in
the consecutive rows.

Disable automatic search
If you enter a direct address into the Entry Data Monitor, the system searches automatically
for a corresponding variable in the GVL of the project. If a variable has been found, the
variable name is added to the Entry Data Monitor.
This feature can cause long delays if the projects include many global variables. To increase
the performance of GX IEC Developer, disable the automatic search in the setup of the Entry
Data Monitor.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 29

Monitor only visible objects in window
In the monitor mode all objects entered in the Entry Data Monitor are monitored, even if
they are not visible. This feature can cause long delays if the window contains many EDM
elements. To increase the performance of GX IEC Developer, it is possible to monitor only
visible objects in the Entry Data Monitor. This option is realised in the setup of the Entry Data
Monitor:
The disadvantage of this option is that short delays may be caused during scrolling in the
Entry Data Monitor. These delays are caused by the registration, which is changed every time
when the visible part of the window has been changed.


Always on top Keeps the Entry Data Monitor always on top of other windows. This
option can be enabled or disabled in the menu Tools or Context. If this option is active, a
check mark is placed next to the menu item. Only one Entry Data Monitor can be on top.

The pop-up menu for configuring the table
The Shortcut menu appears if you select the desired row and click on the right-hand mouse
button or press the key combination ¨š.


Field list The Field List contains the possible column entries for the EDM table.



Insert row A new row is inserted in front of the selected row.



Delete row The selected row is deleted.



Delete All All entries are deleted. You are asked to confirm your choice before the command
is executed.

The buttons for configuring the table

Close The dialog window is closed. The settings are saved.


Cancel The operation is aborted. The settings are not saved.



Read Setup The file previously created with the Write Setup is called up.



Write Setup The table configuration can be stored in an external file. This file is given the
extension SED.



Password The password for the security function is defined here.



Security on/off A security function is available to prevent data being written into the CPU.
The security function can be switched on or off. You are prompted for the password.

How to open the Entry Data Monitor or the Header Monitor
ቢ Activate the Monitor Mode command in the Online menu.
ባ Select the POU to be switched to Monitor Mode.
ቤ Select the Entry Data Monitor or Header Monitor command in the Online menu. The
dialog window containing the EDM table appears.

Reference Manual

GX IEC Developer

8 - 30 Diagnostics Functions and Online Operation

How to insert an object
ቢ Select any cell in the desired row. A selected cell is indicated by the double border. (If the
Name or Address column is selected, you can now enter the name or address directly.)
ባ Select the Insert Object command from the Edit menu or from the pop-up menu.
ቤ Select the desired object and click on OK. You can also select several objects in the list consecutively or selectively. You also have the possibility of transferring the entire list of
Global Variables, as well as the entire POU and Task pool.

How to insert a 32-bit register
ቢ As an IEC address: Enter the corresponding address in the Address (IEC) column, e.g. %MD0.0.
As a MITSUBISHI address: Enter the two contiguous MITSUBISHI addresses in the Name
column, e.g. D3+D4.

How to change the values of the objects
ቢ Select the desired values column.
ባ In the case of bit operands: You can switch between the two possible entries (0 and 1) by
double-clicking or pressing the SPACE key.
In the case of word operands: Activate the Edit Mode (mouse click or m). Enter the desired
value. GX IEC Developer only accepts valid entries. Pay attention to the correct format
(decimal, octal, etc.). The Edit Mode remains active in the event of an incorrect entry.

How to open and close a structure
The word Structure in the Type column indicates a tree structure. If a tree structure is open, all
the associated variables of the POU are displayed.
ቢ Select the Name cell in the row containing a structure.
ባ Closing an open structure: The open structure is indicated by a minus sign in front of the
name. Double-click on the Name cell or press the §- key combination. This closes the tree
structure.
Opening a closed structure: The closed structure is indicated by a plus sign in front of the
name. Double-click on the Name cell or press the §+ key combination. This opens the tree
structure.

Open
structure
Closed
structure

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 31

Arrays in the Entry Data Monitor
You can enter arrays in the Entry Data Monitor. All elements of the array can be read, written
and set.
If the array is large it may not be possible to display all its elements on the screen at the same
time. You can set the default number of elements to display to a maximum of 50 with the
option Extras - Options - General - Array Elements To Show.
You can also change this value in the prompt dialog that is displayed when you open an array in
the Entry Data Monitor.

The entry in the Lower Bound field specifies the first array element to be displayed.

Reference Manual

GX IEC Developer

8 - 32 Diagnostics Functions and Online Operation

8.4.6

Changing variable values
The value of a variable can be changed in the Entry Data Monitor (EDM). Additionally the
variable value can be changed directly in an editor (IL, Melsec IL, Ladder, FBD, and SFC). This is
realised by means of new dialogs for simple data types, which can be opened in the monitor
mode. The restriction to simple data types means that it is not possible to change the values of
structured data types (e.g. DUTs).
Dialog layouts
Two different dialog layouts are available for changing a variable value in an editor:
a) Dialog to toggle Boolean variables or devices
This dialog appears, if you want to change a Boolean variable or device. This dialog can be
switched off by selecting the correspondent option in the dialog. This setting is valid until you
leave the monitor mode.

b) Dialog to change numerical variables or devices
This dialog appears, if you want to change a numerical variable or device. It contains the type
and the current value of the variable or device. The new value can be entered either as a decimal
or as a hexadecimal value.

Dialog operations
There are the following dialog operations:
a) Changing the value of a variable or device
After you have entered the new value in the edit control, press Enter or OK to leave the dialog.
A message will appear asking whether the value should be written to the PLC. If the new value
has a wrong format, a message in the dialog appears and the value in the edit control is
selected. In this case the value is not written to the PLC. For numerical data types (INT, WORD,
DWORD, DINT), the value can be entered in the hexadecimal format.
b) Changing the name of a variable or device
After you have entered a new variable or device and left the corresponding edit control, the
dialog will be updated. If the variable can be monitored, the new name and the current value
are displayed. The cursor is set to the edit control New Value.
The following objects are valid:
n
n
n

GX IEC Developer

global variables
local variables which are declared in the POU of the active body
direct addresses

Reference Manual

Diagnostics Functions and Online Operation 8 - 33

c) Changing the display type
For numerical data types it is possible to switch the display format of the current value and the new
value between decimal or hexadecimal. This option is disabled for Boolean variables or devices.
d) Updating the current value
The current value of the variable or device will be updated according to the poll rate of the
monitor mode.
Opening the dialogs
The dialogs to change the variable or device values can be opened in the monitor mode in the
following ways for the corresponding windows:
a) SFC Body
ቢ Choose Modify variable in the menu Online or use the shortcut CTRL+F9.
If a transition with a variable or device is selected in the POU body, the corresponding dialog
with this variable or device is opened. If no transition with a variable or device is selected, the
dialog is empty and you can enter a variable or device.
ባ Double-click with the left mouse button on a transition with a variable or device. The
corresponding dialog with this variable or device is opened.
Example for a selected transition with the variable OperationDone:

b) MELSEC IL / IL Body
ቢ Choose Modify variable in the menu Online or use the shortcut CTRL+F9.
If a variable or device is selected in the POU body, the corresponding dialog with this variable
or device is opened. If no variable or device is selected, the dialog is empty and you can enter
a variable or device.
ባ Double-click with the left mouse button on a variable or device. The corresponding dialog
with this variable or device is opened.
Example in IL for the selected variable MotorVal:

Reference Manual

GX IEC Developer

8 - 34 Diagnostics Functions and Online Operation

c) Ladder / FBD Body
ቢ Choose Modify variable in the menu Online or use the shortcut CTRL+F9.
If a variable or device is selected in the body of the POU, the corresponding dialog with this
variable or device is opened. If no variable or device is selected, the dialog is empty and you
can enter a variable or device.
ባ Double-click with the left mouse button on a variable or device. The corresponding dialog is
opened with this variable or device.
Example in Ladder for the selected variable MotorVal:

d) Navigator
ቢ To open the dialog select Modify variable in the menu Online or press the shortcut
CTRL+F9. The dialog is empty and you can enter a variable or device.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 35

8.4.7

Display direct address of a variable
In the monitor mode the direct address instead of the symbolic name of global variables can be
displayed. This is possible for global variables of simple data types in Ladder and FBD.
Toggle direct address and symbolic name
In the monitor mode direct address and symbolic name of a variable can be toggled.
ቢ Select the symbolic name or direct address of a global variable and choose Toggle variable
in the menu Online or press the shortcut ALT+F9.
ባ Press CTRL and double-click with the left mouse button on the symbolic name or direct
address of the global variable.
Example in Ladder
A) Global variable MotorVal before calling the toggle functionality:

B) Global variable MotorVal after the toggle functionality has been called:

If the monitoring is stopped for a window, the direct addresses of the toggled global variables
are still available. If the monitor mode is finished, the symbolic names of the toggled global
variables are restored.

Reference Manual

GX IEC Developer

8 - 36 Diagnostics Functions and Online Operation

8.4.8

Tracking variables
The write access to variables can be tracked during monitoring. The tracking of variables is
available within the IL, MELSEC IL, ST, LD, and FBD editors for the following objects:
n
n
n

POU bodies
SFC transitions
SFC actions

The tracking functions are available from
n
n

the menu Tools - Tracking
the editor context menu (right-click on variable or keys [SHIFT]+[F10])

The tracking function is available only if the monitor mode is active. The variable to be tracked
must be selected in one of the editors mentioned above. To select a variable, simply move the
mouse cursor over it.
The Start Tracking function creates an internal list (from the browser information). This internal
list indicates where the selected variable name is used for write access. If this list already exists, it
will be overwritten. A window will be opened showing where the variable name is used for the
first time. In this window the corresponding variable is highlighted. If the corresponding variable
name can not be found or if the browser information is not available, an appropriate message
box will appear.
If the variable name could be found, the next, previous, first, and last occurence of the
variable can be tracked via menu commands. Each occurence is shown in a window where the
variable is highlighted. If the corresponding variable name can not be found or if the browser
information is not available, an appropriate message box will appear.
Tracking menu items and functions
Start Tracking:
n
n
n
n
n
n

GX IEC Developer

Open the browser.
The code location selected is the first entry in the browser list box.
Open the code location of the occurrence.
Mark the code location of the variable occurrence.
Start monitoring of the newly opened editor.
If no ‚First‘ is found, the following message box is displayed: ‘Start Tracking:
No reference found’.

Reference Manual

Diagnostics Functions and Online Operation 8 - 37

Next:
n
n
n
n
n

According to the browser information the selection is set to the next occurrence.
Open the code location of the occurrence.
Mark the code location of the variable occurrence.
Start monitoring of the newly opened editor.
If no Next is found, the following message box is displayed: “No reference found”.

Previous:
n
n
n
n
n

According to the browser information the selection is set to the previous occurrence.
Open the code location of the occurrence.
Mark the code location of the variable occurrence.
Start monitoring of the newly opened editor.
If no ‚Previous‘ is found, the following message box is displayed: “Previous:
No reference found”.

First:
n

n
n
n
n

According to the browser information the selection is set to the first occurrence within the
browser.
Open the code location of the occurrence.
Mark the code location of the variable occurrence.
Start monitoring of the newly opened editor.
If no First is found, the following message box is displayed: “Already placed on desired
location”.

Last:
n

n
n
n
n

According to the browser information the selection is set to the last occurrence within the
browser.
Open the code location of the occurrence.
Mark the code location of the variable occurrence.
Start monitoring of the newly opened editor.
If no Last is found, the following message box is displayed: “Already placed on desired
location”.

Limitations
If a variable is used in the MELSEC IL, the variable can not be displayed by the tracking function.

Reference Manual

GX IEC Developer

8 - 38 Diagnostics Functions and Online Operation

8.4.9

Monitoring Boolean I/Os of function blocks
Boolean inputs and outputs of function blocks are monitored even if they are connected to a
network. The function block itself does not need to be opened and monitored individually.
All Boolean inputs and outputs of a function block are monitored in the function block box, if
the monitor mode is active. The Boolean variables of the value FALSE are indicated by a
highlighted frame and the Boolean variables of the value TRUE are indicated by a completely
highlighted rectangle.

8.5

LLT (Ladder Logic Test)
The ladder logic test tool is a utility for offline simulation and debugging of PLC programs. It
provides the simulation of external devices, load and save buffer memory contents, timing charts
and much more.
Step execution is also supported even for an FX CPU.
LLT can only be started, if the tool is installed, the project is compiled, and GX IEC Developer is
not in online-mode.
In the Online menu select Ladder Logic Test. The PLC parameters are transferred to LLT and
the main LLT window appears. The main LLT window shows the PLC CPU condition and allows
to start different tools.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 39

The device memory monitor of the LLT shows the values of the selected devices and allows to
change them.

The timing chart shows the condition of the selected devices within a selected timing range.

It is not possible to perform online changes. Rounging errors may occur in the results of
instructions using the floating decimal point
Note: After the error correction by the LLT program module the program must be transferred
to the specified PLC and checked again before it is executed.

Reference Manual

GX IEC Developer

8 - 40 Diagnostics Functions and Online Operation

The following functions are not supported:
n
n
n
n
n
n
n

Physical special function modules
Physical I/O modules
Networks
Interrupt programs
Read from PLC, Compare with PLC
Comments
SFC programs

There are other CPU related restrictions in device ranges, PLC memory format, etc. For more
details refer to the manual for the Ladder Logic Test.

8.6

Intelligent Function Module Utility
The inlcuded intelligent function module utility has to be installed separately. It supports an easy
configuration of intelligent function modules by dialogue based input instead of PLC program
code needed to access the module buffer memory setup area.
The utility is available only if a Q series project is active and the utility is installed. The utility
supports the Q series only. For details refer to the documentation of the utility.
GX IEC Developer supports the call of the intelligent function module utility and a check for
address collisions between refresh parameters for the modules and GX IEC Developer system
addresses. The configuration file has to be written by the intelligent function utility to the PLC and
to the hard disk. A corresponding message is displayed by GX IEC Developer if the utility is started.
If initial setting and automatic refresh setting are performed, the intelligent function module
parameters require a maximum of 76 bytes per module.
If the project is saved with a different name, GX IEC Developer informs the utility about a closed
project because the iparam.wpa file of the old project path is not saved with the new project!
The iparam.wpa file is the configuration file, created by the utility. It can be found in the
subdirectory Resource of the current project. You have to close the utility, and copy the
iparam.wpa file from the old project to the new one.
Note: After configuration of the intelligent function module, please save the parameters to
hard disk!
The intelligent function module utility will be closed, if the current project is closed or changed.
Please remember to save the configuration BEFORE closing or changing the project.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 41

8.6.1

Starting the utility
From the Extras menu select Intelligent Function Utility - Start to start the external utilities
and navigate via the utility’s menus.
From the Extras menu select Intelligent Function Utility - Verify System Variables to start the
external utilities and directly verify the system variables.
Address collisions between refresh addresses and GX IEC Developer system addresses.

Intelligent function module utility with configuration for three different modules.

Reference Manual

GX IEC Developer

8 - 42 Diagnostics Functions and Online Operation

Example for the auto refresh configuration of the A/D conversion Module Q64AD.

8.6.2

Troubleshooting
In very rare cases problems might occur which will be solved in future software versions.
ቢ Problem: If GX IEC Developer 4.00 is already installed before installing GX Developer (version
& lt; 4), the Intelligent Function Utility can not be started anymore from GX IEC Developer 4.00.
Solution: Install GX IEC Developer 4.00 again.
ባ Problem: If GX Developer (Version & lt; 4) is already installed before installing GX IEC Developer
4.00, GX Developer can not be started anymore.
Solution: Install GX Developer again in a newer version (version & gt; 4).
ቤ Problem: If GX Developer as well as GX IEC Developer 4.00 are installed and GX Developer
will be deinstalled afterwards, the Intelligent Function Utility can not be started anymore
from GX IEC Developer 4.00.
Solution: Install GX IEC Developer 4.00 again.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 43

8.7

MXChange Support
By default the MXChange support is not enabled in GX IEC Developer. To activate the
MXChange support, take the following steps:
ቢ In the file C:\WINDOWS\MMP400.INI search the section [MXchange]. By default this
section includes the entry MXchange=FALSE.
ባ Change this entry to MXchange=TRUE and save the file C:\WINDOWS\MMP400.INI.
ቤ Start GX IEC Developer.
Now, the MXChange support is enabled.

8.7.1

Software purpose
The separately sold software package MXChange is designed to integrate MITSUBISHI ELECTRIC
automation development tools into a single environment which harmonises programming,
supervision, network configuration, and simulation components.
For further details refer to the MXChange software manual and to the additional manual
MXChange for Melsec Medoc plus.
Note: MXChange is sold in Europe only. Please contact the following Mitsubishi Office
concerning MXChange:
MEU-GER, Tel.: +49-2102-486-334

8.7.2

General features
MXChange provides the following features:
n
n
n
n
n
n
n
n
n

Reference Manual

Simultaneous definition of I/O references in multiple packages and projects.
Automatic transfer of changes of I/O references to other parts of the automation project.
Automatic transfer of ProfiMap POU blocks to the corresponding GX IEC Developer projects.
Save GX IEC Developer project to MXChange.
Import and export of parts of the MXChange configuration for use with other MXChange servers.
Import and export in Microsoft Excel compatible format (CSV).
Simultaneous generation of multiple tags for all projects based on a supplied pattern.
Synchronisation mechanism.
Security mechanism with log in and password.

GX IEC Developer

8 - 44 Diagnostics Functions and Online Operation

8.7.3

Functions and menu items
Only if the MXChange support is enabled (see above), the following menu items are available:
Project menu
Enable MXchange
MXchange actions

Ǡ

Log on
Open Project from MXChange
Show changes
Call Tag-editor
Global Adjust
Change Password
Disable MXchange

Extras menu
Declare MXchange Tags
Delete MXchange Tags

Enable MXChange
The item Enable MXChange is available only if the current project is a non-MXChange project.
The function does not work if any GVL editor is open at the moment. In this case an error
message appears.
If all GVL editors are closed, you are asked to insert the TCP/IP address or the network name of
the machine the MXChange server is running on. Furthermore, the login details are required.





Browse The button Browse opens a list box where you can select a server to connect. The
timeout used to connect the servers is 3000 ms by default. This value can be modified by an
entry in the INI file. In the following example the timeout is set to 5000 ms.



Automatic Update After Logon If the item Automatic Update After Logon is selected,
the MXChange data will be updated immediately after each logon (similar to
Project- & gt; Save).



GX IEC Developer

Use Local Address The button Use Local Address inserts the TCP/IP address of the
personal computer GX IEC Developer is running on. In some cases the TCP/IP address cannot
be determined, e.g. if the PC is not running in a network. If this is the case, you are asked
whether the local host address should be used instead (which is 127.0.0.1 by define).

Show Message if MXChange data has been Modified by other Applications
If this item is selected, GX IEC Developer will display a message if any other application has
changed MXChange data of the current GX IEC Developer project. This message appears the
first time when a change has been made after the last update (project save), i.e. it does not
appear for each change.

Reference Manual

Diagnostics Functions and Online Operation 8 - 45

MXChange action / Logon
If you are logged in when selecting the menu command logon, a logoff is performed. If you are
logged off when selecting the menu command logon, a logon is performed.
The logon status is shown by a button in front of the menu item. If the button is activated you
are logged in and vice versa.
The menu command logon is available only if an MXChange project is open.
If the logon procedure does not find the project in the selected MXChange database (for
example if the PLC node has been deleted within the Super Project Manager, a message will be
displayed asking you to create a new project node.
A new project node will be created in the MXChange database. During the next update (when
saving the GX IEC Developer database) all MXChange tags stored in the GX IEC Developer
database will be exported to the new project node.
MXChange action / Open Project from MXChange
Opens a project in GX IEC Developer that exists as project node in MXChange.
MXChange action / Show changes
The menu item Show Changes opens a window indicating the changes made by other
applications. The list includes all changes concerning the project node and its child nodes which
have to be considered by GX IEC Developer.
The list is sorted alphabetically and includes three different classes: declarations, POU blocks, and
the PLC data. Each item has one of the three change flags: deleted, added, or modified.
MXChange action / Call Tag-editor
The menu item Call Tag editor calls the global MXChange tag editor. To use this function a
connection to the MXChange server must be available and the current status must be logged on.
MXChange action / Global Adjust
It might be that both databases (GX IEC Developer and MXChange) do not have exactly the
same tags or data or some tags differ by single items.
The following reasons are possible for that
n
n

n

Using a backup version of the MXChange database.
Using an older GX IEC Developer or MM+ 2.40 project, i.e. you do not use the current
project.
Malfunction of the normal update mechanism.

The standard update mechanism does not note these cases. To realise an acceptable update
duration, only data which has been changed is updated.
Starting the Global Adjustment
The global adjustment is an extra command.
By means of the global adjustment you can select either GX IEC Developer or MXChange to
include the more recent data.

Reference Manual

GX IEC Developer

8 - 46 Diagnostics Functions and Online Operation

a) Selection GX IEC Developer includes the more recent data:
n
n
n

All tags not defined in GX IEC Developer but in MXChange are imported to GX IEC Developer.
All tags not defined in MXChange but in GX IEC Developer are exported to MXChange.
Tags defined in MXChange and GX IEC Developer are adjusted to the tags defined in GX IEC
Developer, i.e. the tags in MXChange will be overwritten.

b) Selection MXChange includes the more recent data:
n
n
n

All tags not defined in GX IEC Developer but in MXChange are imported to GX IEC Developer.
All tags not defined in MXChange but in GX IEC Developer are exported to MXChange.
Tags defined in MXChange and GX IEC Developer are adjusted to the tags defined in
MXChange, i.e. the tags in GX IEC Developer are overwritten.

MXChange action / Change Password
This menu item changes the password for the MXChange database.
MXChange action / Disable MXChange
The menu item Disable MXChange is available only if the project currently loaded is an
MXChange project. Disable MXChange removes all MXChange data from the project database
and the MXChange column in the GVL. Via this menu item the PLC project will not be removed
from the Super Project. This has to be done using the Super Project Manager. To disable
MXChange all GVL editors must be closed.
Declare MXChange tags
If the current project is an MXChange project, another column named MXChange is added to
the GVL. If the current project is not an MXChange project, the appearance will not be modified.
A “X” in the MXChange column indicates that this variable is declared to be an MXChange tag.
User library GVLs cannot declare variables as MXChange tags although they include also the
additional column. If you click into the MXChange field, a system beep will be generated.
To declare a variable as MXChange tag
n
n
n

click into the MXChange field using the left mouse button or
press SPACE within this field or
select the variable and from the menu Extras select Declare MXChange tags.

The menu item Declare MXChange tags is available only if the GVL editor is open and has the
input focus and at least one declaration is selected. For non-MXChange projects Declare
MXChange tags is not available.
There are variables which cannot be declared as MXChange tags. There are the following
restrictions:
n
n

The variable declaration must be valid. Otherwise an error message appears.
The variable type must be of the following types: BOOL, INT, STRING, DINT, WORD, DWORD,
REAL, TIME, or ARRAYS of the types mentioned before. Otherwise an error message appears.

If you try to change an MXChange tag type into a type not allowed in MXChange, the change is
not accepted and the tag type which has been valid before entering the invalid type will be valid
again when leaving the edit field.

GX IEC Developer

Reference Manual

Diagnostics Functions and Online Operation 8 - 47

Delete MXChange tags
To delete an MXChange tag remove the “X” from the MXChange column in the GVL. To remove
the “X” from the MXChange column
n
n
n

click into the MXChange field using the left mouse button or
press SPACE within this field or
select the variable and from the menu Extras select Declare MXChange tags.

The menu item Delete MXChange tags is available only if the GVL editor is open and has the
input focus and at least one declaration is selected. For non-MXChange projects Delete
MXChange tags is not available.
During the next update (when saving the GX IEC Devceloper project) this information will be
given to the MXChange server. If you delete a variable which is an MXChange tag, it will also be
removed from the MXChange database.
All declarations that are defined as MXChange tags will be declared to be non-MXChange tags
(see also section on page ). The other declarations will not be influenced.
Restrictions
It is not allowed to change the name of a, MXChange declaration in the GVL editor. If you try to
open the edit field of the variable name a message beep will be generated.

Reference Manual

GX IEC Developer

8 - 48 Diagnostics Functions and Online Operation

GX IEC Developer

Reference Manual

APPENDIX

Reference Manual

GX IEC Developer

GX IEC Developer

Reference Manual

Glossary A 1

A

Glossary
Absolute address
A variable’s absolute address references a fixed memory location in the CPU or a physical input or output. This
absolute address can be assigned using either IEC syntax (IEC address) or MITSUBISHI syntax (MITSUBISHI address).
The user must only assign absolute addresses for the global variables. The program assigns suitable memory locations
for the local variables automatically.
Absolute Label
Absolute labels are the addresses of specific pointers in the PLC program (e.g. P20). When PLC programs are
uploaded to GX IEC Developer absolute labels are assigned as jump instruction destinations. Every program section
identified by a pointer in the original PLC program is loaded in a separate MELSEC network. You can also use absolute
labels (Syntax: P_20) when you assign your own names to networks.
Accumulator
The accumulator is a result handling facility used in IEC Instruction List. You may be familiar with it from other
high-level programming languages. The result of every operation performed is written to the accumulator directly
after execution. The accumulator thus always contains the result of the last instruction programmed. This means that
you do not have to program any input conditions (execution conditions) for the operations, as execution is always
dependent on the contents of the accumulator.
Action

An action is allocated to every step in an SFC sequence. These actions can be Boolean output variables or PLC
programs.

Action Pool
When you write a POU in Sequential Function Chart language the action pool is displayed in the Project Navigator
window as an entry in that POU. The Action Pool contains all the actions belonging to the program organisation unit.
Actual parameters
Functions and function blocks have two kinds of parameters: Formal parameters and actual parameters. The formal
parameters are the variables used when you create a function or a function block. The actual parameters are the
variables or values passed to the function or function block instance when they are used in another program
organisation unit.
’Adapted’ MELSEC instructions
‘Adapted’ MELSEC instructions are MITSUBISHI ELECTRIC instructions with a special modified nomenclature (e.g.
BMULTI_M, PLUS_M, FLOAT_MD) for use in the IEC editor. They always have the suffix _M for ‘MELSEC’ or _MD for
‘MELSEC Dedicated instruction’. All the ‘adapted’ MELSEC instructions are stored in the Manufacturer Library. These
instructions can only be used in the IEC editor (© Appendix E).
Array

Arrays are derived data types, consisting of fields of one kind of variable. You can define arrays with up to three
dimensions.

AutoConnect mode
The Autoconnect mode is a special editing mode used in the graphical editors (© Chapter 3).
Body

Program organisation units (POUs) always consist of a header and a body. The body contains the actual
PLC program code.

Breakpoint
Breakpoints are a debugging aid. You can set a breakpoint at any point in a program organisation unit. The execution
of the PLC program will then automatically stop at this point.
Class

The class is specified in the declaration table to define the way variables are to be used in the project. The following
classes are supported: VAR, VAR_CONSTANT, VAR_INPUT, VAR_OUTPUT, VAR_IN_OUT, VAR_EXTERNAL,
VAR_EXTERNAL_CONSTANT, VAR_GLOBAL and VAR_GLOBAL_CONSTANT.

Comment
You can enter and store explanatory comment texts for all objects used in GX IEC Developer. National characters can
be used.
Compiling
When you compile a project GX IEC Developer translates the program into code that can be read and executed
directly by the PLC.
Computer link module
One of the several ways of connecting the PLC to your personal computer is with a MITSUBISHI ELECTRIC computer
link module. Computer link modules available from MITSUBISHI ELECTRIC include the following models: AJ71C21,
AJ71UC24, AJ71QC24, A1SJ71QC24, QJ71C24.
Continue condition
© ‘Transition condition’

Reference Manual

GX IEC Developer

A 2 Glossary

Controller instruction
PLC programs written in Instruction List language consist of a series of controller instructions. Each controller
instruction contains an operator, i.e. the programming instruction, and an operand, i.e. the variable.
CPU interface
You can connect the PLC to your personal computer via the CPU interface, which is located on the PLC unit.
Data type
The data type of a variable defines the number of bits it contains, how they are processed and the variable’s value
range. The following data types are available: BOOL, INT, DINT, WORD, DWORD, TIME, REAL, ARRAY, STRING.
Data Unit Type
The Data Unit Type (DUT) is a structured data type. It contains a collection of variables.
Declaration table
Declaration tables are lists used for managing and declaring both global and local variables.
Device Editor
The device editor allows you to display and edit the contents of the PLC CPU’s bit and word devices (registers). The
central element of the device editor is a table that is very similar to a Microsoft Excel worksheet, both in its
appearance and in the way it is used.
Dialog box
A dialog box is a special kind of window used for handling dialogs with the user. They can contain a number of
different elements, including fields for entering data, check boxes or radio buttons for selecting options and
messages containing important warnings or information. Dialog boxes are displayed at many different points in the
program, for example when you select menu commands followed by three periods (e.g. Open...).
Download
Transfer process from GX IEC Developer to the PLC
DUT Pool
The DUT Pool is one of the standard entries in the Project Navigator window (DUT_Pool). It contains all the Data Unit
Types used in the project.
Edit mode
When you are editing the body of a POU you can choose between Select mode and Edit mode. In Edit mode you can
perform actions on selected program elements (e.g. move, overwrite, delete etc).
Editing area
The editing window for working on the body of a POU is divided into two main areas, the network bar and the editing
area. The editing area is where you enter the component elements of your program.
Editor

The GX IEC Developer editors are program modules used for writing and editing programs in the supported
programming languages. The editors are displayed as separate windows on the screen. GX IEC Developer includes
text, graphical, IEC and MELSEC editors.

EN input
In addition to their input and output variables, some function blocks also have a Boolean input (EN = ENable) and a
Boolean output (ENO = ENable Out). The status of the ENO output always corresponds to the current status of the EN
input.
ENO output
© ‘EN input’
Entry Data Monitor
GX IEC Developer supports a variety of different monitoring modes: Program Monitor, Entry Data Monitor and
Header Monitor. In the Entry Data Monitor mode the program displays the status of a user-defined list of variables.
The variables in this list can be displayed in any order.
Ethernet card
One of the several ways of connecting the PLC to your personal computer is via an Ethernet network. To do this, you
must then have an Ethernet card in your PC and connect it to the MITSUBISHI ELECTRIC Ethernet module.
Final step
The final step is the last step in an SFC sequence.
Formal parameters
© ‘Actual parameters’
Function
The function is a program organisation unit (POU) with the class ‘Function’ (FUN). It can be used in the same way as a
normal programming instruction. When they are executed, functions deliver precisely one output variable. Functions
do not store any internal status data. This means that all a function’s internal variables are always set to 0. When a
function is called with the same input parameters it thus always delivers the same output value.

GX IEC Developer

Reference Manual

Glossary A 3

Function block
The function block is a program organisation unit (POU) with the class ‘Function Block’ (FB). It can be used in the same
way as a normal programming instruction. Function blocks deliver one or more output variables when they are
executed. All the values of the output variables and the internal variables are stored in the function block following
execution. This means that function blocks do not necessarily always deliver the same output values when they are
called again with the same input parameters. Function blocks can only be called in the form of instances. Be careful
not to confuse these function blocks with the graphical function blocks used in the Function Block and Ladder
Diagram language!!
Function Block Diagram
Function Block Diagram (FBD) is a programming language. Programming instructions are displayed as graphical
blocks which are connected with horizontal and vertical interconnect lines. Be careful not to confuse these graphical
function blocks with the Function Block (FB) program organisation units!!
Function blocks in the graphical editors
In the graphical editors most programming instructions are displayed as graphical blocks in the editing screen. These
graphical blocks are sometimes referred to as ‘function blocks’. Be very careful not to confuse these blocks with the
Function Block program organisation units!!
Global variable
Global variables have fixed hardware addresses (absolute addresses). They are declared ‘globally’ for the entire
project and can be referenced from all function block (FB) and program (PRG) program organisation units by
declaring them in the header as VAR_EXTERNAL. They make it possible to exchange data between the individual
program modules that make up the project. The global variables are also included as a standard entry in the Project
Navigator window, Global_Vars.
Graphic macro
You can define any selected section of a PLC program as a graphic macro. Macros are a useful construct when you
need to use the same piece of code several times at different points in your PLC program. Graphic macros are only
supported in the graphical editors.
Graphical editor
The following programming languages use graphical editors, which are used in the same way as a standard graphics
drawing program: Ladder Diagram (LD), Function Block Diagram (FBD) and Sequential Function Chart (SFC).
Header

Program organisation units (POUs) always consist of a header and a body. The header contains the declarations of all
the variables used in the POU, which are organised in a declaration table.

Header Monitor
GX IEC Developer supports a variety of different monitoring modes: Program Monitor, Entry Data Monitor and Header
Monitor. Header Monitor mode is fundamentally the same as Entry Data Monitor mode. However, in addition to the
user-defined list of variables the monitor also always displays the variables of the active program organisation unit.
Identifier
The identifier is the name allocated to a variable that serves as its symbolic address.
IEC address
The IEC address assigns a fixed memory location to a global variable. The syntax of IEC addressing is defined in the IEC
61131.3 standard. Examples: %IX0 (input X0) , %MW0.450 (data register D450).
IEC editor
The IEC editor is used for programming in the IEC 61131.3 programming languages.
IEC function
© ‘Programming instructions’
IEC function block
© ‘Programming instructions’
IEC Instruction List
GX IEC Developer supports both IEC Instruction List language and MELSEC Instruction List. In IEC Instruction List the
program is written according to the IEC 61131.3 standard, using only the instructions from the IEC standard library.
However, if you need to do so you can insert MELSEC networks in programs written in IEC Instruction List.
IEC operator
© ‘Programming instructions’
IEC programming instruction
© ‘Programming instructions’
Initial step
The initial step is the first step in an SFC sequence.
Initialisation file
SC.INI is the ‘initialisation file’ for GX IEC Developer. It is stored in the Windows directory and contains all the
parameters necessary for initialising the GX IEC Developer program when it is started.
Input variable
© ‘Output variable’

Reference Manual

GX IEC Developer

A 4 Glossary

Installation program
The installation program INSTALL.EXE copies the contents of the GX IEC Developer program distribution disks to your
hard disk and sets the program up for your hardware configuration.
Instance
An instance is a copy of a function block. Function blocks can only be called in the form of instances. Instances are
created by declaring them in the headers of program organisation units, and they are called in the body of the POU.
Special programming instructions are provided for calling instances.
It is also possible to create global function block instances. These global instances can be used in different program
organisation units.
Instructions
© ‘Programming instructions’, ‘Controller instructions’
Instruction List
Instruction List is a programming language. GX IEC Developer supports two Instruction List variants, IEC Instruction
List and MELSEC Instruction List. An Instruction List program consists of a list of controller instructions.
Interconnect mode
Interconnect mode is a special editing mode in the Ladder Diagram editor, with functionality similar to a line-drawing
tool in a graphics program. In Interconnect mode you connect programming elements by drawing horizontal and
vertical lines between them.
Interface card
One of the several ways of connecting the PLC to your personal computer is with the A7BDE interface card from
MITSUBISHI ELECTRIC and a MITSUBISHI network. This is an expansion card which must be installed in your
computer. (Not yet supported)
Jump entry point
The jump entry point is the point in an SFC sequence to which a jump is to be performed (i.e. the jump label).
Jump exit point
The jump exit point is the point in an SFC sequence from which a jump is to be performed (i.e. the position of the jump
instruction).
Jump instruction
Jump instructions are used to execute a branch from the current POU to another network. In the graphical editors the
jump instruction is implemented as a tool. In IEC Instruction List jumps are programmed with the JMP operator.
Label

The word ‘Label’ is automatically displayed as a dummy variable when you are programming jump instructions in the
graphical editors. It must be overwritten with the designator of the actual jump entry point or destination (©
absolute label, network label, system label)

Ladder Diagram
Ladder Diagram is a programming language. The programming elements are contacts (inputs), coils (outputs) and
programming instructions which are displayed as graphical blocks. These elements are connected to make circuits
using horizontal and vertical interconnect lines. The circuits always start at the power bar on the left.
Library

There are three types of libraries: Standard Library, Manufacturer Library and User Library.

Local variables
Local variables are only accessible within the program organisation units in which they are declared. They are
declared in the POU header.
Macro step
In an SFC sequence a macro step is a step that in turn contains another complete SFC sequence.
Manufacturer Library
The Manufacturer Library (Manufacturer_Lib) contains the ‘adapted’ MELSEC programming instructions, with a
special nomenclature for use in the IEC editor (© ‘Programming Instructions’ in the appendix).
MELSEC editor
The MELSEC editor is used for editing MELSEC Instruction Lists and MELSEC networks.
MELSEC Instruction List
GX IEC Developer supports both IEC Instruction List language and MELSEC Instruction List language. MELSEC
Instruction List programs only contain MELSEC networks.
MELSEC network
MELSEC networks are programmed according to the DIN 19239 standard, using only the ‘pure’ MELSEC instructions.
MELSEC programming instructions
© ‘Programming instructions’
MELSEC upload
The MELSEC upload procedure loads a program into GX IEC Developer from the PLC unit. Only the binary data is read
in when this process is carried out.

GX IEC Developer

Reference Manual

Glossary A 5

MITSUBISHI address
The MITSUBISHI address is used to assign a fixed memory location to a global variable. Examples: X0, M1024.
Monitoring mode
GX IEC Developer supports a variety of different monitoring modes: Program Monitor, Entry Data Monitor and
Header Monitor.
Network
A network is a logically continuous program section within a program organisation unit.
Network bar
The editing window in which you work on the body of a POU is divided into the network bar and the editing area. The
network bar is used for making the network label and title assignments.
Network label
The network label is the name assigned to a network. It can be used as the destination address for jump instructions
in PLC programs.
Network list
The network list contains all the networks in a program organisation unit, along with their network labels and titles.
Network title
The network title is a brief description of the network. It is optional, and it is not displayed in the network bar.
Null modem cable
© ‘RS-232 cable’
Object

GX IEC Developer uses the following objects: The IEC Standard Library (Standard_Lib), the Manufacturer Library
(Manufacturer_Lib), the PLC Parameter (PLC_Parameter), the Task Pool (Task_Pool), the Data Unit Type Pool
(DUT_Pool), the Global Variables (Global_Vars) and the POU Pool (POU_Pool). These objects are all displayed as
standard entries in the Project Navigator window.

Object window
Object windows contain the data of selected objects (e.g. the declaration table for the global variables or a task’s table).
Output variable
Function blocks have input and output variables. The input variables give the function block the values it uses to perform
its programmed operations. The output variables pass the results of these operations out of the function block.
PLC Parameter
The PLC parameter (PLC_Parameter) is one of the standard entries in the Project Navigator window. It contains the
user-editable parameters of the connected PLC system.
POU Pool
The POU Pool is one of the standard entries displayed in the Project Navigator window (POU_Pool). It contains all the
program organisation units used in the project.
Power bar
In the Ladder Diagram graphical editor all circuits start at the vertical power bar on the left of the editing area. This bar
is sometimes also referred to as the rail.
Program
1) Program = An application program (e.g. GX IEC Developer);
2) Program = A PLC program, consisting of a series of programming instructions;
3) Program = A program organisation unit classed as a ‘Program’ (PRG). Program POUs can only be executed in tasks.
Program class
The program class of a POU defines its functionality. You can declare POUs as Programs (PRG), Function Blocks (FB) or
Functions (FUN).
Program group
The Windows Program Manager organises programs in groups called ‘program groups’. Each group can contain a
large number of individual programs (i.e. application programs). The GX IEC Developer installation program
automatically creates a program group for GX IEC Developer containing the GX IEC Developer program icon.
Program Monitor
GX IEC Developer supports a variety of different monitoring modes: Program Monitor, Entry Data Monitor and
Header Monitor. You can activate the Program Monitor mode in all the editors. This monitor displays the values and
switching statuses of the variables visible in the current editor window.
Program organisation unit
Program organisation units (POUs) can be regarded as subprograms or program modules. There are three different
POU classes, defined by their functionality: Programs (PRG), Function Blocks (FB) and Functions (FUN). Every POU
consists of a header and a body.
Programming elements
Examples of programming elements in the graphical editors include contacts, function blocks, interconnect lines and
variable connections.

Reference Manual

GX IEC Developer

A 6 Glossary

Programming instructions
GX IEC Developer supports the following groups of programming instructions: IEC programming instructions, MELSEC
programming instructions and user programming instructions (© ‘Programming Instructions’ in the appendix).
Programming language
GX IEC Developer supports the following programming languages for writing PLC programs: Instruction List (IL),
Ladder Diagram (LD), Function Block Diagram (FBD), Sequential Function Chart (SFC).
Project

The project is the element at the top of the GX IEC Developer object hierarchy. It is equivalent to a PLC system.

Project name
The project name is actually the name of a subdirectory. This subdirectory contains all the individual files that form the
components of a project.
Project Navigator
The Project Navigator is the control centre of GX IEC Developer. It is used to administrate all the objects that go to
make up a project. It is displayed on the screen as a separate window, the Project Navigator window.
Project Navigator tree
The entries in the Project Navigator window are arranged using a hierarchical tree structure. Some of the levels can be
expanded and collapsed to display or hide further levels of the tree hierarchy.
Project Navigator window
All the objects contained in a project are listed in the Project Navigator window. This window is opened on the left
hand side of the screen as soon as you create or open a project. It always contains the following standard entries:
Standard_Lib, Manufacturer_Lib, PLC_Parameter, Task_Pool, DUT_Pool, Global_Vars and POU_Pool.
’Pure’ MELSEC Instructions
The ‘pure’ MELSEC instructions are the original MITSUBISHI MELSEC instructions with the standard nomenclature
(e.g. AND=, +, FLOAT). These instructions are only supported in the MELSEC editor (© ‘Programming Instructions’ in
the appendix).
Return instruction
The Return instruction effects a return from a function block to the point in the program from where the function
block was called. In the graphical editors the Return instruction is implemented as a tool. In the IEC Instruction List
editor returns are implemented with the RET operator.
RS-232 cable
An RS-232 cable wired as a null modem cable is required for connecting the personal computer to a computer link
module.
Select mode
When you are working in the programming editors you can choose between Select mode and Edit mode. In Select
mode the mouse pointer is displayed as an arrow with which you can select the various programming elements.
Sequence
Sequences are written with the Sequential Function Chart language (SFC). An SFC sequence consists of steps,
actions, transitions and transition conditions. Both parallel and selective branching are supported in sequences.
Sequential Function Chart Language
Sequential Function Chart is a programming language in which steps are linked together with conditions referred to
as continue conditions. The elements of the SFC language are steps, actions, transitions and transition conditions.
SFC sequence
© ‘Sequence’
Signal configuration
You can set the following signal configuration parameters for the input and output variables of a function block and
the input contacts and output coils used in the Ladder Diagram language: Poll for signal status 0 or 1, set and reset.
Standard Library
The Standard Library (Standard_Lib) contains the standard IEC functions (e.g. INT_TO_BOOL) and function blocks
(e.g. R_TRIG).
Status bar
The status bar displayed at the bottom of the screen shows information on the current status of the project. You can
configure the status bar to suit your personal requirements.
Step

Sequences in the SFC language always consist of several steps connected by transitions. An action is assigned to each
step in the sequence.

Step mode
Step mode execution is a debugging aid. In this mode, the program is executed one step at a time. Please note that
the connected PLC system must be switched to step run mode when you use this option.
STRING

GX IEC Developer

A STRING data type contains characters.

Reference Manual

Glossary A 7

System Label
The system labels (pointers) are system variables that GX IEC Developer needs for internal management of the project.
The number of available system labels depends on the PLC used. One system label is needed for each of the following
elements: every instance of a function block, every user-defined function, every event-triggered task, every network
label.
Task

A task contains one or more program organisation units of the class ‘Program’ (PRG). The task controls the execution
of its component POUs. Tasks can be event-triggered, interval-triggered or priority-triggered.

Task Pool
The Task Pool (Task_Pool) is one of the standard entries in the Project Navigator window. It contains all the tasks
defined in the project.
Text editor
The text editor is used for writing and editing Instruction List programs. Its functionality is similar to that of a standard
word processor.
Toolbar

The toolbar displays icons with which the most-used menu commands can be selected directly by clicking with the
mouse.

Transition
Transitions connect steps in SFC language sequences. Each transition is allocated a transition condition, i.e. a
continue condition that controls how and when control is passed to the next step in the sequence.
Transition condition
A transition condition is a PLC program. It is executed when the preceding SFC step is completed, and if the condition
is satisfied control is passed to the next step in the sequence.
Upload

Transfer process from the PLC to GX IEC Developer

User library
A user library gives you the possibility of creating functions and program segments which can be used on a
supra-project basis. The program segments are grouped in a library and can be used in any project. Following
updating, changes made to the library can be applied to other projects. A user library can contain all the objects that
are also available in a project: Global Variables List, Structured Data Types, Arrays and Program Organisation Units.
You can assign a password to protect the know-how in the library. The name of the user library file has the file
extension SUL.
User programming instructions
Programming instructions written by the user. © ‘Programming instructions’.
Variable
Variables can be compared with operands. They contain the values of inputs, outputs or internal memory locations in
the PLC. GX IEC Developer makes a distinction between global and local variables. Variables are declared and
administered in declaration tables; they are defined with a class, an identifier, an absolute address (global variables
only) and a data type.
Wizard

Reference Manual

The Wizard is a special aid that can be activated and deactivated by editing the initialisation file SC.INI. When the
Wizard is activated the program can automatically generate a program organisation unit and a task for you when you
create a new project.

GX IEC Developer

A 8 Glossary

GX IEC Developer

Reference Manual

Keyboard Commands B - 1

B

Keyboard Commands
B.1

GX IEC Developer Menu Keys
Key(s)

¦

Activate/deactivate the Menu Bar

š

Activate/deactivate the Menu Bar

¤

Move through Menu Bar to the right (GX IEC Developer menus and Windows control menu)

¥

Move through Menu Bar to the left (GX IEC Developer menus and Windows control menu)

A-Z

When Menu Bar or menu activated: Select corresponding menu or menu option/command
(e.g. L for Online)

«

Activate highlighted menu or menu option/command

£

Move highlight up through menu options

¢

Move highlight down through menu options

°

Exit menu/selection

¦”

Quit GX IEC Developer (Project - Quit)

‘

Activate Help system

¦©

Open Task List (list of all application programs currently running) and select program

§ø

B.2

Functions

Open Windows Start menu

Project Navigator Keys
Key(s)

£

Move highlight up through Project Navigator Window

¢

Move highlight down through Project Navigator Window

¤

Scroll window contents to the right

¥

Scroll window contents to the left

³

Page window contents up one screen

·

Page window contents down one screen

§+
+: num. keypad

Display lower tree levels of selected entry (Tools - Expand)

§-: num. keypad

Hide lower tree levels of selected entry (Tools - Collapse)

§x

Cut selected entry and copy to the clipboard (not available for all entries!) (Edit - Cut)

§C

Copy selected entry to clipboard (not available for all entries!) (Edit - Copy)

§v

Paste data from the clipboard to highlight position (Edit - Paste)

µ

Delete selected entry (not available for all entries!) (Edit - Delete)

«

Open object window or dialog box of selected entry (Object - Open)

§”

Reference Manual

Function

Close Project Navigator Window (i.e. close project) (Project- Close)

GX IEC Developer

B - 2 Keyboard Commands

B.3

Object Window Keys
Key(s)

§©

Step through all opened windows

§–

Switch to next window

§¨–

Switch to previous window

³

Page window contents one screen up

·

Page window contents one screen down

§³

Scroll window contents to the left

§·

Scroll window contents to the right

¦-

Open the Windows control menu of the active window

§”

Close the active window (Object - Close)

§¨t

Arrange all opened windows side by side (Window - Tile)

£

1) Move pointer up in window
2) Following selection of Move (Size) in the control menu: Move window up
(resize window)

¢

1) Move pointer down in window
2) Following selection of Move (Size) in control menu: Move window down
(resize window)

¤

1) Move pointer right in window
2) Following selection of Move (Size) in control menu: Move window right
(resize window)

¥

1) Move pointer left in window
2) Following selection of Move (Size) in control menu: Move window left
(resize window)

«

1) Storing the new window position or window size
2) In Project Navigator Window: Open the object window or dialog box of
the selected entry

§s

Save object (Object - Save)

¦C

Check object (Object - Check)

§P

Print object (Object - Print)

¦«

GX IEC Developer

Function

View object information (Object - Information)

Reference Manual

Keyboard Commands B - 3

B.4

Dialog Box Keys
Key(s)

¦–

Move to next dialog box

¦¨–

Move to previous dialog box

¦

Activate/deactivate control menu button

š

Activate/deactivate control menu button

©

Step through options from top to bottom / from left to right

¨©

Step through options from bottom to top / from right to left

¦A - Z

Execute option (e.g. L for Latch Range)

«

1) Control menu button selected: Open control menu
2) Option selected: Execute option (often the same as clicking the OK! button)
3) List box: Activate selected element

¦”

Close dialog box (often the same as selecting the Cancel! button)

ø

Close dialog box (often the same as selecting the Cancel! button)

¤¥

Step through options

£¢

1) Step through options
2) List box: Page list up/down one screen at a time

²

1) List box: Move to first list element
2) Text box: Move to first character



1) List box: Move to last list element
2) Text box: Move to last character

´

Reference Manual

Function

1) List box: Activate/deactivate list element
2) Activate/deactivate check boxes

GX IEC Developer

B - 4 Keyboard Commands

B.5

Table Keys
Key(s)

£
¢
¤
¥
³
·
²

Move up one line at a time



1) Move to cell in the last column
2) Editing mode: Move to last character in the cell

©
¨©
§²
§¶
¨£
¨¢
¨²
¨¶
¨§²
¨§¶
¦¢
´
«
µ

Step through all cells from left to right

¸

1) Delete selected range
2) Editing mode: Delete character to left of cursor

§x
§C
§v
¨«

Cut selected range and copy to clipboard (Edit - Cut)

¦¸
§¸
¦“
“
§+
+: num. keypad
§-: num. keypad

GX IEC Developer

Function

Undo the last command (not supported for all operations!) (Edit - Undo)

Move down one line at a time
Move right one cell at a time
Move left one cell at a time
Page window contents up one screen at a time
Page window contents down one screen at a time
1) Move to cell in the first column
2) Editing mode: Move to first character in the cell

Step through all cells from right to left
Move highlight to beginning of table
Move highlight to end of table
Extend or reverse continuous selection up one line at a time
Extend or reverse continuous selection down one line at a time
Select current line
Select current line
Select all lines from the first line to the current line
Select all lines from the current line to the last line
Open dialog box or list box of a selected cell containing an arrow symbol
Activate editing mode in the current cell
Deactivate editing mode in the current cell
1) Delete selected range
2) Editing mode: Delete character to right of cursor (Edit - Delete)

Copy selected range to clipboard (Edit - Copy)
Paste data from clipboard to current position (Edit - Paste)
1) From any cell: Move to first column of the next line
2) From any cell in the last line: Insert a new line

Undo the last Undo command (not supported for all operations!) (Edit - Redo)
Find (Edit - Find)
Find Next (Edit - Find Next)
First cell in the line is marked by a - sign: Display all lines in the comment column
(Tools - Expand declaration)
First cell in the line is marked by a + sign: Display only one line in the comment column
(Tools - Collapse declaration)

Reference Manual

Keyboard Commands B - 5

B.6

Device Editor Keys
Key(s)

£

Move up one cell

¢

Move down one cell

¤

Move right one cell

¥

Move left one cell

§£

Move to top of current data range

§¢

Move to bottom of current data range

§¤

Move to right edge of current data range

§¥

Move to left edge of current data range

³

Page up

·

Page down

§³

Page left

§·

Page right

²

Select cell in first column of current row



Select cell in last column of current row

§²

Select cell in first column of first row (top left)

§¶

Select cell in last column of last row (bottom right)

©

Step through all cells from left to right

¨©

Step through all cells from right to left

«

Step down through all cells

¨«

Step up through all cells

¨£

Extend or cancel selection upwards one line at a time

¨¢

Extend or cancel selection downwards one line at a time

¨¤

Extend or cancel selection right one cell at a time

¨¥

Extend or cancel selection left one cell at a time

§¨£

Extend or cancel selection to top of current data range

§¨¢

Extend or cancel selection to bottom of current data range

§¨¤

Extend or cancel selection to right edge of current data range

§¨¥

Extend or cancel selection to left edge of current data range

¨³

Extend or cancel selection up one page

¨·

Extend or cancel selection down one page

§¨³

Extend or cancel selection left one page

§¨·

Extend or cancel selection right one page

¨²

Extend or cancel selection to beginning of current line

¨¶

Extend or cancel selection to end of current line

§¨²

Extend or cancel selection to first column in first line (top left)

§¨¶

Extend or cancel selection to last column in last line (bottom right)

¨´

Select current line

§´

Select current column

§¨´

Reference Manual

Function

Select entire table

GX IEC Developer

B - 6 Keyboard Commands

Key(s)

§A

Select entire table

µ

Delete selected range

§x

Cut selected range to clipboard

§C

Copy selected range to clipboard

§v

Paste contents of clipboard

§±

Copy selected range to clipboard

¨±

Paste contents of clipboard

¨µ

Cut selected range to clipboard

’

Activate editing mode for selected cell

¸

Clear contents of selected cell and activate editing mode

§«

Terminate editing mode

ø

Abort editing mode

«

GX IEC Developer

Function

Toggle value of selected bit device between 0 and 1

Reference Manual

Keyboard Commands B - 7

B.7

Instruction List Editor Keys
Key(s)

¦tE
¦tD
£¢¤¥

Activate editing mode (Tools - Edit Network)

«

1) Select mode - Pointer on network bar: Open dialog box for entry of network labels and titles
2) Editing mode: Select/enter new line

´(2x)
´

Select mode - pointer on network bar: Open dialog box for assigning network label and title

´£¢
´¤¥
©

Pointer on bottom border line of network bar: Change size of network area

’

1) Cursor/pointer in first column: Open programming instructions list
2) Cursor/pointer in second column: Open variables list

³
·
§³
§·
²

§²
§¶
¨¤
¨¥
¨£
¨¢
¨§²
¨§¶
µ

Page window contents up one screen

¸

1) Delete selected range
2) Delete character left of cursor

§x
§C
§v
¦“
“
¦¸
§¸
¦A
¦B

Reference Manual

Function

Cut selected range and copy to clipboard (Edit - Cut)

Activate Select mode (Tools - End Edit)
1) Select mode: Move cursor/pointer in window
2) Editing mode: Scroll through Instruction List

1) Select mode - pointer on network bar: Activate network
2) Select mode - cursor/pointer in editing window: Activate editing mode
Pointer on column dividing line: Change column width
1) Line without text: Select next column
2) Line with text: Move text to next column

Page window contents down one screen
Scroll window contents to the right
Scroll window contents to the left
Move to first character in the line
Move to last character in the line
Move to beginning of Instruction List
Move to end of Instruction List
Extend or reverse selection to the right one character at a time
Extend or reverse selection to the left one character at a time
Extend or reverse selection up one line at a time
Extend or reverse selection down one line at a time
Select all lines from the first line to the current line
Select all lines from the current line to the last line
1) Delete selected range
2) Delete character to right of cursor (Edit - Delete)

Copy selected range to clipboard (Edit - Copy)
Paste data from clipboard to current position (Edit - Paste)
Find (Edit - Find)
Find Next (Edit - Find Next)
Undo last command (not supported for all operations!) (Edit - Undo)
Undo last Undo command (not supported for all operations!) (Edit - Redo)
Insert a new network after the current network (Edit - New Network - After)
Insert new network before the current network (Edit - New Network - Before)

GX IEC Developer

B - 8 Keyboard Commands

B.8

Graphical Editor Keys
Key(s)

§A

Activate Select mode (Tools - Select Mode)

§t

Activate Interconnect mode (draw lines) (Tools - Interconnect Mode)

£¢¤¥

Move pointer

´(2x)

1) Pointer on network bar: Open dialog box for entering network labels and titles
2) Pointer on a contact: Open dialog box for signal configuration F " Helvetica " P10

«

Pointer on network bar: Open dialog box to assign network label and title

´£¢

Pointer on lower border of network bar: Change size of network area

³

Page window contents up by one screen

·

Page window contents down by one screen

§³

Scroll window contents to the right

§·

Scroll window contents to the left

´

1) Select programming element
2) Select network bar
3) Activate editing mode to overwrite the dummy names Var and Label

’

1) Editing mode for overwriting dummy variable name Var: Open list of variables
2) Open list of programming instructions

´£¤¢¥

1) Move selected programming element
2) Following selection of Tools - Open Row/Column: Increase row/column spacing
3) Following selection of Tools - Comment: Draw a comment box
4) Interconnect mode: Draw interconnect lines

´£¤¢¥

Select a continuous group of program elements

¨£¤¢¥

Select several program elements individually

µ

1) Delete selected range
2) Delete character right of cursor (Edit - Delete)

¸

Delete character left of cursor

§x

Cut selected range and copy to clipboard (Edit - Cut)

§C

Copy selected range to clipboard (Edit - Copy)

§v

Paste data from clipboard to current position (Edit - Paste)

¦“

Find (Edit - Find)

“

Find Next (Edit - Find Next)

¦¸

Undo last command (not supported for all operations!) (Edit - Undo)

§¸

Undo last Undo command (not supported for all operations!) (Edit - Redo)

§n

Insert input contact (Tools - Contact)

§l

Insert output coil (Tools - Coil)

§J

Insert jump instruction (Tools - Jump)

§r

Insert return instruction (Tools - Return)

§I

Insert input variable (Tools - Input Variable)

§o

Insert output variable (Tools - Output Variable)

§g

Draw horizontal line segment (Tools - Horizontal Line Segment)

§E

Draw vertical line segment (Tools - Vertical Line Segment)

§F

Insert programming instruction (Function Block) (Tools - Function Block)

§w

Increase horizontal spacing (Tools - Open Row)

§u

GX IEC Developer

Function

Increase vertical spacing (Tools - Open Column)

Reference Manual

Keyboard Commands B - 9

Key(s)

Function

¦1

Insert graphic macro 1 (Tools - Custom 1)

¦2

Insert graphic macro 2 (Tools - Custom 2)

¦3

Insert graphic macro 3 (Tools - Custom 3)

¦4

Insert graphic macro 4 (Tools - Custom 4)

¦5

Insert graphic macro 5 (Tools - Custom 5)

¦A

Insert new network after the current network (Edit - New Network - After)

¦B

Insert new network before the current network (Edit - New Network - Before)

©

Step through all the variable objects in the current network forwards, selecting them one after
another.

¨©

Step through all the variable objects in the current network backwards, selecting them one
after another.

+

Function block is activated: Increment number of input variables (pins)
(Edit - Increment Pins)

(+: num. keypad)

(-: num. keypad)

Reference Manual

Function block is activated: Decrement number of input variables (pins)
(Edit - Decrement Pins)

GX IEC Developer

B - 10 Keyboard Commands

B.9

Sequential Function Chart Editor Keys
Key(s)

£¢¤¥
§¥
§¤
§£
§¢
¨¥
¨¤
¨£
¨¢
¨§¥
¨§¤
¨§£
¨§¢
©
¨©
²

§²
§¶
¨²
¨¶
¨§²
¨§¶
«
ú
µ
³
·
¦“
“
§u
§F
§t
§l
§r
¨§l
¨§r
§¨J
§J
§I
§b

GX IEC Developer

Function
Move highlight

1) Undo all selections

Highlight on a connection line: Move highlight to the leftmost branch in the row
Highlight on a connection line: Move highlight to the rightmost branch in the row
Move highlight to the next branch above or to the Initial Step
Move highlight to next branch below or to the Final Step
Extend selection to the element to the left of the highlight
Extend the selection to the element to the right of the highlight
Extend the selection up one element
Extend the selection down one element
Highlight on a connection line: Extend the selection to the leftmost element in the row
Highlight on a connection line: Extend the selection to the rightmost element in the row
Extend the selection to the next element above or to the Initial Step
Extend the selection to the next element below or to the Final Step
Move the highlight to the next element
Extend the selection to the next element
Move the highlight to the first column
Move the highlight to the last column
Move the highlight to the beginning of the program
Move the highlight to the end of the program
Select all elements between the current highlight position and the left column
Select all elements between the current highlight position and the right column
Select all elements between the current highlight position and the beginning of the program
Select all elements between the current highlight position and the end of the program
1) Highlight on an unnamed Transition or an unnamed Step: Switch to Editing mode
2) Highlight on a named Step: Open window of associated POU
3) Highlight on a Macro Step: Open Macro Program window
Delete selected elements
Page window contents up by one screen
Page window contents down by one screen
Find (Edit - Find)
Find Next (Edit - Find Next)
Insert Step/Transition unit at the current position (Edit - Insert - Step/Trans Unit)
Insert Step at the current position (Edit - Insert - Step)
Insert Transition at the current position (Edit - Insert - Transition)
Insert left divergence from the current position (Edit - Insert - Left Divergence)
Insert right divergence from the current position (Edit - Insert - Right Divergence)
Insert left convergence to the current position (Edit - Insert - Left Convergence)
Insert right convergence to the current position (Edit - Insert - Right Convergence)
Insert Label (jump destination/entry step) (Edit - Insert - Label)
Insert Jump (jump/exit step) (Edit - Insert - Jump)
Open (zoom) Step, Transition or Macro Program window (Tools - Zoom Into)
Undo zoom operation (Tools - Zoom Back)

Reference Manual

Keyboard Commands B - 11

B.10

Keys for Checking and Downloading Programs
Key(s)

¨§C
§¦w
¨§D
¦C
§˜
¦˜
¨¦˜
¨§˜
ùú
¦s
•
—
¨¦E
¦u

B.11

Function
Compile project (Project - Rebuild All)
Download project to CPU (Project - Transfer - Medoc - & gt; PLC)
Change program in Online mode operation (Project - Online Prog. Change)
Check object (Object - Check)
Start program monitoring (Online - Start Monitoring)
Stop program monitoring (Online - Stop Monitoring)
Open monitoring window for variable status of current Header (Online - Monitor Header)
Open Entry Data Monitor (Online - Entry Data Monitor)
Activate Monitoring mode (Online - Monitoring Mode)
Switch PLC CPU to Start or Stop mode (Online - Start/Stop PLC)
Go to breakpoint (Debug - Go To Breakpoint)
Execute program in stop mode, stopping after each step (Debug - Step)
Display contents of system error registers (Debug - System Errors)
Associate error messages to error flags (Debug - User Errors)

Online Help System Keys
Key(s)

Function

‘
i
s
z
r
& lt;
& gt;
¦
©

Activate Help system

¨©

Select one of the icons/buttons on the screen
Step through the icons/buttons anticlockwise

§©
§«
¨«
¦”

Select all the icons/buttons on the screen

Contents button
Search button
Back button
History button
& lt; & lt; button (previous topic)
& gt; & gt; button (next topic)
Activate Menu Bar
Select one of the icons/buttons on the screen
Step through the icons/buttons clockwise

Copy the current help topic text to the clipboard
Copy the clipboard contents to the Annotate dialog box
Close the Help window

For more details on using the online Help system select How to use help in the Help menu.

Reference Manual

GX IEC Developer

B - 12 Keyboard Commands

GX IEC Developer

Reference Manual

Tools C - 1

C

Tools
C.1

General Tool Icons
Tool

Menu command
Project - Open

Save an opened project

Project - Save

Print the active object

Project - Print

Shows a print preview of the active object

Project - Print Preview

Cut the selected object to the clipboard

Edit - Cut

§x

Copy the selected object to the clipboard

Edit - Copy

§C

Paste object from the clipboard

Edit - Paste

§v

Undo the last action

Edit - Undo

¦¥

Redo the previously undone action

Edit - Redo

§¥

Edit the properties of current selection

Object - Information

¦«

Open the cross reference browser

Project - Browse

Start the check routine for the currently
selected object

Object - Check

¦C

Build the current project

Project - Build

¨¦B

Rebuild the current project

Project - Rebuild All

¨¦C

Logon/logoff to MXChange server

Project - MXChange actions

Enable or disable the monitoring mode

Online - Monitoring Mode

Activate Online Change mode

Online - Online-Change Mode

Download the current project to the PLC

Project - Transfer Download to PLC

Upload the project from the PLC

Reference Manual

Function
Open an existing project

Key(s)

Project - Transfer Upload from PLC

¨ø

§¦w

GX IEC Developer

C - 2 Tools

C.2

Instruction List Editor Tool Icons
Tool

Menu command

Key(s)

Insert a new network before the current
network

Edit - New Network - Before

¦B

Insert a new network after the current
network

Edit - New Network - After

¦A

Activate Select mode, End Editing mode

Tools - End Edit

Activate Editing mode, End Select mode

C.3

Function

Tools - Edit Network

Ladder Diagram and Function Block Diagram Editor Tool Icons
Tool

Menu command

Key(s)

Edit - New Network - Before

¦B

Insert a new network after the current
network

Edit - New Network - After

¦A

Activate Select mode, End Editing mode
(toggles with Interconnect mode)

Tools - Select Mode

§A

Activate Interconnect mode, Line tool
(toggles with Select mode)

Tools - Interconnect Mode

§t

Activate Auto Connect mode

Tool - Auto Connect

§b

Insert input contact (Ladder Diagram only)

Tools - Network Elements Contact

§n

Insert output coil (Ladder Diagram only)

Tools - Network Elements Coil

§l

Insert programming instruction
(Function Block)

Tools - Network Elements Function Block

§F

Insert input variable

Tools - Network Elements Input Variable

§I

Insert output variable

Tools - Network Elements Output Variable

§o

Insert Jump instruction

Tools - Network Elements Jump

§j

Insert Return instruction

Tools - Network Elements Return

§r

Increase vertical spacing

Tools - Open Row

§u

Increase horizontal spacing

Tools - Open Column

§w

Insert comment

GX IEC Developer

Function
Insert a new network before the current
network

Tools - Network Elements Comment

§m

Reference Manual

Tools C - 3

C.4

Sequential Function Chart Editor Tool Icons
Tool

Menu command

Key(s)

Insert a Step/Transition unit at the current
position

Edit - Insert - Step/Trans Unit

§U

Insert a Step at the current position

Edit - Insert - Step

§F

Insert a Transition at the current position

Edit - Insert - Transition

§T

Insert a left divergence from the current
position

Edit - Insert - Left Divergence

§L

Insert a right divergence from the current
position

Edit - Insert - Right
Divergence

§r

Insert a left convergence to the current
position

Edit - Insert - Left
Convergence

¨§l

Insert a right convergence to the current
position

Edit - Insert - Right
Convergence

¨§r

Insert a Label (entry step/jump destination)

Edit - Insert - Label

§¨J

Insert a Jump (exit step jump instruction)

Edit - Insert - Jump

§J

Open (zoom) a Macro Program window

Tools - Zoom Macro

Open (zoom) the Action Association
window for the selected Step

Tools - Edit Action
Association

Edit the Step Comment

Tools - Edit Step Comment

Edit the Transition Condition

Tools - Edit Transition
Condition

Open (zoom) the Body of a Step or
Transition

Tools - Zoom Body

Open (zoom) a Step, Transition, or Macro
Program window

Tools - Zoom Into

§I

Undo zoom operation (i.e. close window)

Tools - Zoom Back

§B

List all available variables or operands

Reference Manual

Function

Tools - List Operands...

’

GX IEC Developer

C - 4 Tools

C.5

Project Navigator Window Tool Icons
Tool

Key(s)

Tools - Expand

¦+

Hide displayed levels of the Project
Navigator

Tools - Collapse

¦-

Create a new Program Organisation Unit

Object - New - POU

¦N

Create a new Data Unit Type

Object - New - DUT

Create a new Task

Object - New - Task

¦K

Create a new Action (this icon is only
enabled when a POU written in Sequential
Function Chart language is selected)

Object - New - Action

¨¦A

Function

Menu command

Key(s)

Set breakpoint

Debug - Set Breakpoint

Delete breakpoint

Debug - Delete Breakpoin

Go to breakpoint

Debug - Go to Breakpoint

•

Open POU body

Debug - Step

—

Open Entry Data Monitor

Online - Entry Data Monitor

¨§˜

Sampling Trace

Debug - Sampling Trace

Monitor header of the active POU bodys

Online - Monitor Header

¨¦˜

Start monitoring in the active window

Online - Start Monitoring

§˜

Stop monitoring in the active POU body

Online - Stop Monitoring

¦˜

Online (Monitor Mode) Tool Icons
Tool

GX IEC Developer

Menu command

Display lower levels of the Project Navigator
tree

C.6

Function

Reference Manual

Temporary Files D - 1

D

Temporary Files
D.1

Temporary Files Created when Projects are Compiled
A number of temporary files are created during compilation. These files are normally deleted
when the program is finished with them; if you don’t want them to be deleted you must start
GX IEC Developer with the /debug command line option. To do this, add this option to the GX
IEC Developer command line in the Program Item Properties dialog box in the Windows Program
Manager:
c:\melsec\gx iec developer\sc.exe /debug.
n

n

_tsksub.sic Data of the Task MELSEC_SUB, allocated to the SUB memory range (stored in a
special format)
_tsksub.out Data of the Task MELSEC_SUB, allocated to the SUB memory range (special
MELSEC code)
_tsksub.bin Data of the Task MELSEC_SUB, allocated to the SUB memory range (the
compiled code that is downloaded to the controller)

n

POUname.sic Data of a specific Program Organisation Unit (stored in a special format)
POE-Name.out Data of a specific Program Organisation Unit (special MELSEC code)
POE-Name.bin Data of a specific Program Organisation Unit (the compiled code that is
downloaded to the controller)

n

_end.sic Data of the END instruction (stored in a special format)
_end.out Data of the END instruction (special MELSEC code)
_end.bin Data of the END instruction (the compiled code that is downloaded to the controller)

n

main.map All the data of the program allocated to the MAIN memory range (compiled
structural tree)

n

sub.map All the data of the program allocated to the SUB memory range (compiled
structural tree)

n

sfc.map All the data of the program written in Sequential Function Chart Language
(compiled structural tree)

n

sfccode.cod Data of the Program Organisation Units that were written in Sequential
Function Chart Language (compiled code)

n

mmicro.bin Data of the Program Organisation Units that were written in Sequential Function
Chart Language - MELSEC A-Series (compiled code)

n

D.2

_tskmain.sic Data of all tasks allocated to the MAIN memory range (stored in a special format)
_tskmain.out Data of all tasks allocated to the MAIN memory range (special MELSEC code)
_tskmain.bin Data of all tasks allocated to the MAIN memory range (the compiled code that
is downloaded to the controller)

build.out, tab.out, rebuild.out, comp.out Compiling data

Temporary files Created During Downloads
n
n
n
n
n
n
n
n

Reference Manual

dwl_sym.asc
upl_sym.pac
upl_main.bin
upl_sub.bin
fnw_main.dis
fnw_sub.dis
fnw_imp.asc
task_imp.asc

GX IEC Developer

D - 2 Temporary Files

GX IEC Developer

Reference Manual

Programming Instructions E - 1

E

Programming Instructions

Programming Instructions

IEC Programming Instructions
IEC Editors

MELSEC
Programming Instructions

User-programmed
Programming Instructions
in the form of
Program Organisation Units
(POUs)
IEC Editors

IEC Operators
(e.g. LD, ST, CAL)

‘Pure’
MELSEC Instructions
MELSEC Editor
(e.g. +, B*)

Functions
(Name of the Function POU)

IEC Functions
(e.g. INT_TO_BOOL, ROR)

‘Adapted’
MELSEC Instructions
IEC Editors
(e.g. PLUS_M, BMULTI_M,
FLOAT_K_P_MD)

Function Blocks
(Name of the
Function Block POU)

IEC Function Blocks
(e.g. R_TRIG, F_TRIG)

Contents of the
Standard Library

Contents of the
Manufacturer
Library

Standard Library
The standard library contains all the IEC functions and function blocks. Every available function
has a FUN (function) POU, the headers of which you can open and view on the screen.
Manufacturer Library
The Manufacturer Library contains the ‘adapted’ MELSEC instructions, with a nomenclature
adapted for use in IEC. Every function has a FUN (function) POU, the headers and bodies of
which you can open and view on the screen. With the help of a special tool you can also add
your own POUs to the Manufacturer Library. These POUs can be declared as functions (FUN),
function blocks (FB) or programs (PRG).

Reference Manual

GX IEC Developer

E - 2 Programming Instructions

MELSEC Instructions
The functionality of the ‘adapted’ and ‘pure’ MELSEC functions is identical. The only difference
between the two versions is the way they are written and how they are used in the various editors.
The ‘pure’ MELSEC instructions use the familiar MELSEC nomenclature (e.g. AND=, +, FLOAT).
These instructions can only be used in the MELSEC editor.
This dialog box is displayed when you are working in the MELSEC editor. The list
contains the ‘pure’ MELSEC instructions.

The ‘adapted’ MELSEC instructions use a special nomenclature. Their names always end with _M
for MELSEC or _MD for MELSEC Dedicated Instructions (e.g. PLUS_M, FLOAT_K_P_MD). You can
use these instructions in the IEC editor.
This dialog box is displayed when you are working in the IEC editor.
The list of the Manufacturer Library contains the ‘adapted’ MELSEC
instructions.

The suffixes _P_MD and _K_MD indicate that the instruction in question is executed on a rising
edge or with a constant.

GX IEC Developer

Reference Manual

Programming Instructions E - 3

Example
MELSEC Editor
LEDA
FLOAT
LEDC
(S)
LEDC
(D)
LEDR
LEDB
FLOAT
LEDC
(S)
LEDC
(D)
LEDR
LEDA
FLOAT
SUB
(S)
LEDC
(D)
LEDR
LEDB
FLOAT
SUB
(S)
LEDC
(D)
LEDR
LEDA
DFLOAT
LEDC
(S)
LEDC
(D)
LEDR
LEDB
DFLOAT
LEDC
(S)
LEDC
(D)
LEDR
LEDA
DFLOAT
DXNR
(S)
LEDC
(D)
LEDR
LEDB
DFLOAT
DXNR
(S)
LEDC
(D)
LEDR

IEC Editor
FLOAT_MD

Explanation
Normal execution (16 Bit)

FLOAT_P_MD

Pulse-triggered execution (16 Bit)

FLOAT_K_MD

Normal execution (16 Bit) Constant used in operand (S)

FLOAT_K_P_MD

Pulse-triggered execution (16 Bit) Constant used in operand (S)

DFLOAT_MD

Normal execution (32 Bit)

DFLOAT_P_MD

Pulse-triggered execution (32 Bit)

DFLOAT_K_MD

Normal execution (32 Bit) Constant used in operand (S)

DFLOAT_K_P_MD

Pulse-triggered execution (32 Bit) Constant used in operand (S)

Meaning of extensions in the IEC editor
The following table lists the extensions of MELSEC instructions in the IEC editor. The
nomenclature is as follows:
n
_instruction_
n
_instruction
Extension in IEC Editor
_M

Meaning
MELSEC instruction

_P_M

Pulse triggered execution of MELSEC instruction

_MD

Dedicated MELSEC Instruction

_P_MD

Pulse triggered execution of dedicated MELSEC Instruction

_K_MD

Constant used in dedicated MELSEC Instruction

_K_P_MD
_E
_S, _STRING
S_, STRING_

Constant used in and pulse triggered execution of dedicated MELSEC Instruction
Floating point number operands are used
String operands are used

_J_M,
_JP_M

Network number of HOST station is used in operand

_U_M,
_UP_M

Head I/O address of network in HOST station is used in operand

EN input and ENO output
In the Standard Library, most of the programming instructions are displayed in two similar forms.
The only difference between these programming instructions is the suffix _E. This suffix specifies
functions and function blocks which have an EN input and an ENO output (➜ page 6-67).
The functions in the Manufacturer Library do not have this suffix although they all have an EN
input and an ENO output.

Reference Manual

GX IEC Developer

E - 4 Programming Instructions

E.1

IEC Programming Instructions

Instruction

Modifier

Description

Data types

No. of
input
variables

Input
variables

Output
variables

)

IEC Instruction List operator
Right parenthesis
The right parenthesis (close parenthesis) is used to evaluate
a deferred operation. The beginning of the deferred
operation is marked with a left parenthesis

e.g.
AND(

MUL(

NE(. The left
parenthesis
is added to
the operator
itself as a
modifier.

ABS
ABS_E

Absolute value
Writes the input variable data to the output variable with a
positive sign.

1

INT, DINT

INT, DINT

Addition

n
(2 – 28)

(IN1) –
(INn):
INT, DINT,
Constant

INT, DINT

Addition

2

(IN1), (IN2):
TIME

TIME

Logical AND operation

n
(2 – 28)

WORD,
DWORD,
BOOL,
Constant

WORD,
DWORD,
BOOL

BCD_TO_DINT
BCD_TO_DINT_E

Converts BCD format to binary format (DINT)

1

BOOL,
WORD,
DWORD

DINT

BCD_TO_INT
BCD_TO_INT_E

Converts BCD format to binary format(INT)

1

BOOL,
WORD,
DWORD

INT

BOOL_TO_DINT
BOOL_TO_DINT_E

Converts BOOL data type to DINT data type

1

BOOL

DINT

BOOL_TO_DWORD
BOOL_TO_DWORD_E

Converts BOOL data type to DWORD data type

1

BOOL

DWORD

BOOL_TO_INT
BOOL_TO_INT_E

Converts BOOL data type to INT data type

1

BOOL

INT

BOOL_TO_TIME
BOOL_TO_TIME_E

Converts BOOL data type to TIME data type

1

BOOL

TIME

BOOL_TO_WORD
BOOL_TO_WORD_E

Converts BOOL data type to WORD data type

1

BOOL

WORD

IEC Instruction List operator
Calls a Function Block instance.
In the Instruction List language Function Block instances are
called with the CAL operator. The operator must be
followed by the instance name, which in turn must be
followed by the argument list in parentheses, containing
the actual parameters to be passed to the formal
parameters.

-

-

-

DINT_TO_BCD
DINT_TO_BCD_E

Converts binary format (DINT) to BCD format

1

DINT,
Constant

BOOL,
WORD,
DWORD

DINT_TO_BOOL
DINT_TO_BOOL_E

Converts DINT data type to BOOL data type

1

DINT

BOOL

DINT_TO_DWORD
DINT_TO_DWORD_E

Converts DINT data type to DWORD data type

1

DINT

DWORD

DINT_TO_INT
DINT_TO_INT_E

Converts DINT data type to INT data type

1

DINT

INT

DINT_TO_REAL
DINT_TO_REAL_E

Converts DINT data type to REAL data type

1

DINT

REAL

DINT_TO_TIME
DINT_TO_TIME_E

Converts DINT data type to TIME data type

1

DINT

TIME

DINT_TO_WORD
DINT_TO_WORD_E

Converts DINT data type to WORD data type

1

DINT

WORD

ADD
ADD_E

(

ADD_TIME
ADD_TIME_E
AND
AND_E

CAL

GX IEC Developer

N, (

C, N

Reference Manual

Programming Instructions E - 5

Instruction

Modifier

Description

Data types

No. of
input
variables

Input
variables

Output
variables

Division; (IN1) : (IN2)

2

(IN1), (IN2):
INT, DINT,
Constant

INT, DINT

DIV_TIME
DIV_TIME_E

Division; (IN1) : (IN2)

2

(IN1), (IN2):
TIME

TIME

DWORD_TO_BOOL
DWORD_TO_BOOL_E

Converts DWORD data type to BOOL data type

1

DWORD

BOOL

DWORD_TO_DINT
DWORD_TO_DINT_E

Converts DWORD data type to DINT data type

1

DWORD

DINT

DWORD_TO_INT
DWORD_TO_INT_E

Converts DWORD data type to INT data type

1

DWORD

INT

DWORD_TO_TIME
DWORD_TO_TIME_E

Converts DWORD data type to TIME data type

1

DWORD

TIME

DWORD_TO_WORD
DWORD_TO_WORD_E

Converts DWORD data type to WORD data type

1

DWORD

WORD

Equality (=);
[(IN1 = IN2)] & [(IN2) = (IN3)] & ... & [(INn-1) = (INn)];
If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.

n
(2 – 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL,
Constant

BOOL

Function Block;
Falling edge detector; the current signal status on the
output variable (Q) changes in response to a falling edge on
the input variable (CLK).

1

(CLK): BOOL

Q: BOOL

DIV
DIV_E

EQ
EQ_E

(

(

F_TRIG
F_TRIG_E

GE
GE_E

(

Greater than/equals sequential comparison ( & gt; =);
[(IN1) & gt; = (IN2)] & [(IN2) & gt; = (IN3)] & ... & [(INn-1) & gt; = (INn)];
If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.

n
(2 – 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL,
Constant

BOOL

GT
GT_E

(

Greater than sequential comparison ( & gt; )
[(IN1) & gt; (IN2)] & [(IN2) & gt; (IN3)] & ... & [(INn-1) & gt; (INn)]
If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.

n
(2 – 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL,
Constant

BOOL

INT_TO_BCD
INT_TO_BCD_E

Converts binary format (INT) to BCD format

1

INT

BOOL,
WORD,
DWORD

INT_TO_BOOL
INT_TO_BOOL_E

Converts INT data type to BOOL data type

1

INT

BOOL

INT_TO_DINT
INT_TO_DINT_E

Converts INT data type to DINT data type

1

INT

DINT

INT_TO_DWORD
INT_TO_DWORD_E

Converts INT data type to DWORD data type

1

INT

DWORD

INT_TO_REAL
INT_TO_REAL_E

Converts INT data type to REAL data type

INT

REAL

INT_TO_TIME
INT_TO_TIME_E

Converts INT data type to TIME data type

INT

TIME

INT_TO_WORD
INT_TO_WORD_E

Converts INT data type to WORD data type

1

INT

WORD

JMP

C, N

IEC Instruction List operator
Jump to network label
Performs a jump from one program section to a label in
another network. You must specify the network label name
after the operator.

-

-

-

LD

N

IEC Instruction List operator
Load
Loads the value of the specified operand into the
accumulator.

1

BOOL,
WORD,
DWORD,
INT, DINT

-

Reference Manual

GX IEC Developer

E - 6 Programming Instructions

Data types

Description

No. of
input
variables

Less than/equals sequential comparison ( & lt; =)
[(IN1) & lt; = (IN2)] & [(IN2) & lt; = (IN3)] & ... & [(INn-1) & lt; = (Inn)]

n
(2 – 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL,
Constant

BOOL

Value limitation
If (IN) & gt; (MX), then (MX) to output.
If (IN) & lt; (MN), then (MN) to output.
If (MN) & lt; (IN) & gt; (MX), then (IN) to output

3

(MN), (IN),
(MX): INT,
DINT,
WORD,
DWORD,
BOOL

INT, DINT,
WORD,
DWORD,
BOOL

Less than sequential comparison ( & lt; )
[(IN1) & lt; (IN2)] & [(IN2) & lt; (IN3)] & ... & [(INn-1) & lt; (INn)]
If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.

n
(2 – 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL

BOOL

MAX
MAX_E

Select maximum value
The largest value in (IN1) – (INn) as written to the output.

n
(2 - 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL

INT, DINT,
WORD,
DWORD,
BOOL

MIN
MIN_E

Select minimum value
The smallest value in (IN1) – (INn) is written to the output.

n
(2 - 28)

(IN1) – (INn):
INT, DINT,
WORD,
DWORD,
BOOL

INT, DINT,
WORD,
DWORD,
BOOL

MOD
MOD_E

Remainder (IN1) - [(IN1) : (IN2)] x (IN2)

2

(IN1), (IN2):
INT, DINT

INT

MOVE
MOVE_E

Move

1

INT, DINT

INT, DINT

Multiplication

n
(2 – 28)

(IN1) – (INn):
INT, DINT

INT, DINT

MUL_TIME
MUL_TIME_E

Multiplication

2

(IN1), (IN2):
TIME

TIME

MUX
MUX_E

Multiplexer
Writes the data of the input variable between (INO) and
(Inn) to the output. The input variable is specified in (K).

n
(2 – 28)

(K): INT,
DINT; (IN0) –
(INn): INT,
DINT,
WORD,
DWORD,
BOOL

INT, DINT,
WORD,
DWORD,
BOOL

Not equal ( & lt; & gt; )
[(IN1) & lt; & gt; (IN2)]
If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.

2

(IN1), (IN2):
INT, DINT,
WORD,
DWORD,
BOOL

BOOL

Negation

1

WORD,
DWORD,
BOOL

WORD,
DWORD,
BOOL

Logical OR operation

n
(2 – 28)

WORD,
DWORD,
BOOL

WORD,
DWORD,
BOOL

R

IEC Instruction List operator
Reset
Resets the BOOL variable to 0. This operation is only
performed if the value in the accumulator is 1.

1

BOOL

-

R_TRIG
R_TRIG_E

Function Block
Rising edge detector
The status of the output variable (Q) is changed in
accordance with the presence of a rising edge on the input
variable (CLK).

1

(CLK): BOOL

(Q): BOOL

REAL_TO_DINT
REAL_TO_DINT_E

Converts REAL data type to DINT data type

REAL

DINT

Instruction
LE
LE_E

Modifier
(

If the comparison result is true, then 1 to output.
If the comparison result is false, then 0 to output.
LIMIT
LIMIT_E

LT
LT_E

MUL
MUL_E

NE
NE_E

(

(

(

NOT
NOT_E
OR
OR_E

GX IEC Developer

N, (

Input
variables

Output
variables

Reference Manual

Programming Instructions E - 7

Instruction

Modifier

REAL_TO_INT
REAL_TO_INT_E
RET

Description
Converts REAL data type to INT data type

C, N

Data types

No. of
input
variables

Input
variables

Output
variables

REAL

INT

IEC Instruction List operator
Return from a Function Block
Executes a return from a Function Block to the program in
which the Function Block instance was called.

-

-

-

ROL
ROL_E

Rotate left
Rotates the data of the input variable (IN) to the left by (N)
bits. No bits are lost in this process.

2

(IN): BOOL,
WORD,
DWORD; (N):
Constant

WORD,
DWORD,
BOOL

ROR
ROR_E

Rotate right
Rotates the data of the input variable (IN) to the right by
(N) bits. No bits are lost in this process.

2

(IN): BOOL,
WORD,
DWORD; (N):
Constant

WORD,
DWORD,
BOOL

S

IEC Instruction List operator
Set
Sets the value of the BOOL variable to 1. This operation is
only performed when the value in the accumulator is 1.

1

BOOL

-

SEL
SEL_E

Binary selection
When (G) = 0 then (IN0) to output.
When (G) = 1 then (IN1) to output.

3

(G): BOOL;
(IN0), (IN1):
INT, DINT,
WORD,
DWORD,
BOOL

INT, DINT,
WORD,
DWORD,
BOOL

SHL
SHL_E

Left shift
Shifts the data of the input variable (IN) to the left by (N)
bits. The upper (N) bits of (IN) are lost in this process.

2

(IN): BOOL,
WORD,
DWORD; (N):
Constant

WORD,
DWORD,
BOOL

SHR
SHR_E

Right shift
Shifts the data of the input variable (IN) to the right by (N)
bits. The lower (N) bits of (IN) are lost in this process.

2

(IN): BOOL,
WORD,
DWORD; (N):
Constant

WORD,
DWORD,
BOOL

ST

N

IEC Instruction List operator
Store
Stores the value of the specified operand to the
accumulator.

1

BOOL,
WORD,
DWORD,
INT, DINT

-

SUB
SUB_E

(

Subtraction; (IN1) - (IN2)

2

(IN1), (IN2):
INT, DINT

INT, DINT

SUB_TIME
SUB_TIME_E

Subtraction; (IN1) - (IN2)

2

(IN1), (IN2):
TIME

TIME

TIME_TO_BOOL
TIME_TO_BOOL_E

Converts TIME data type to BOOL data type

1

TIME

BOOL

TIME_TO_DINT
TIME_TO_DINT_E

Converts TIME data type to DINT data type

1

TIME

DINT

TIME_TO_DWORD
TIME_TO_DWORD_E

Converts TIME data type to DWORD data type

1

TIME

DWORD

TIME_TO_INT
TIME_TO_INT_E

Converts TIME data type to INT data type

1

TIME

INT

TIME_TO_WORD
TIME_TO_WORD_E

Converts TIME data type to WORD data type

1

TIME

WORD

WORD_TO_BOOL
WORD_TO_BOOL_E

Converts WORD data type to BOOL data type

1

WORD

BOOL

WORD_TO_DINT
WORD_TO_DINT_E

Converts WORD data type to DINT data type

1

WORD

DINT

WORD_TO_DWORD
WORD_TO_DWORD_E

Converts WORD data type to DWORD data type

1

WORD

DWORD

WORD_TO_INT
WORD_TO_INT_E

Converts WORD data type to INT data type

1

WORD

INT

WORD_TO_TIME
WORD_TO_TIME_E

Converts WORD data type to TIME data type

1

WORD

TIME

Logical exclusive OR operation

n
(2 – 28)

WORD,
DWORD,
BOOL

WORD,
DWORD,
BOOL

XOR
XOR_E

Reference Manual

N, (

GX IEC Developer

E - 8 Programming Instructions

E.2

IEC – MELSEC
The following tables list the most common IEC programming instructions with their
corresponding MELSEC programming instructions. For a complete overview of instructions refer
to the programming manuals for the A/Q and FX series.

E.2.1

Addition

Programming instruction

No. of
input
variables

Description

Notes

n
(2 – 28)

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0
The number of input variables is fixed
using the MELSEC functions and
variable using the IEC functions (min. 2,
Q, QnA, FX max. 28).

IEC
IEC Editor
Addition of numerical data/with EN
input and ENO output

ADD
ADD_E
Modifier: (

Series

MELSEC
IEC Editor

MELSEC
MELSEC Editor

ADD_M
DADD_M

ADD
DADD

Addition of numerical data (16/32 bit)

3

PLUS_M
DPLUS_M

+
D+

Addition of numerical data (16/32 bit)

2

Q, QnA, A All the MELSEC functions have an EN
input and an ENO output.

Addition of numerical data (16/32 bit)

3

Q, QnA, A

PLUS_3_M
DPLUS_3_M
ADD_MD

ADD
Addition of floating-point numbers
(with LED* !)ቢ

2

Q, QnA,
AnA

BPLUS_M
DBPLUS_M

B+
DB+

BCD addition (16/32 bit)

2

Q, QnA, A For BCD data only

BCD addition (16/32 bit)

3

Q, QnA, A

2

Q, QnA,
AnA

BPLUS_3_M
DBPLUS_3_M
SADD_MD

SADD
Concatenation of two ASCII strings
(with LED* !)ቢ

IEC
ADD_E with 3 input variables
of data type INT

For floating-point numbers only

WARNING!
No addition!

MELSEC in the IEC Editor
©

ADD_E with 2 input variables of data type DINT ©

ADD_M for the FX series
PLUS_3_M for the A series
DPLUS_M for the A series

Advantage: Enables addition of up to 28 input
variables.

ቢ Dedicated instructions with LEDA/B

GX IEC Developer

Reference Manual

Programming Instructions E - 9

E.2.2

Subtraction

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor
Subtraction of numerical data/with EN
input and ENO output

SUB
SUB_E
Modifier: (

2

Series

Notes

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0
All the MELSEC functions have an EN
input and an ENO output.

MELSEC
IEC Editor

MELSEC
MELSEC Editor

SUB_3_M
DSUB_3_M

SUB
DSUB

Subtraction of numerical data
(16/32 bit)

3

FX

MINUS_M
DMINUS_M

D-

Subtraction of numerical data
(16/32 bit)

2

Q, QnA, A

Subtraction of numerical data
(16/32 bit)

3

Q, QnA, A

MINUS_3_M
DMINUS_3_M
SUB_MD

SUB
Subtraction of floating-point
(with LED* !)ቢ numbers

2

Q, QnA,
AnA

BMINUS_M
DBMINUS_M

BDB-

BCD subtraction
(16/32 bit)

2

Q, QnA, A For BCD data only

BCD subtraction
(16/32 bit)

3

Q, QnA, A

Execute a microcomputer program

1

Q, QnA, A WARNING!
No subtraction!

BMINUS_3_M
DBMINUS_3_M


SUB

IEC

For floating-point numbers only

MELSEC in the IEC Editor

SUB_E with input variables
of data type INT

©

MINUS_M for the A series

SUB_E with input variables
of data type DINT

©

DMINUS_M for the A series

ቢ Dedicated instructions with LEDA/B
ባ These instructions are not supported by the IEC editor.

Reference Manual

GX IEC Developer

E - 10 Programming Instructions

E.2.3

Multiplication

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor
Multiplication of numerical data/with
EN input and ENO output

MUL
MUL_E
Modifier: (

n
(2 – 28)

Series

Notes

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

MUL_M
DMUL_M

MUL
DMUL

Multiplication of numerical data
(16/32 bit)

3

FX

MULTI_M
DMULTI_M

*
D*

Multiplication of numerical data
(16/32 bit)

2

A

Multiplication of numerical data
(16/32 bit)

3

The number of input variables is fixed
using the MELSEC functions and
variable using the IEC functions (min. 2,
max. 28).

Q, QnA, A

MULTI_3_M
DMULTI_3_M
MUL_MD

MUL
Multiplication of floating-point numbers 2
(with LED* !)ቢ

Q, QnA,
AnA

BMULTI_M
DBMULTI_M

B*
DB*

All the MELSEC functions have an EN
input and an ENO output.

For floating-point numbers only

2

Q, QnA, A For BCD data only

BCD multiplication (16/32 bit)

BMULTI_3_M
DBMULTI_3_M

BCD multiplication (16/32 bit)

3

A

IEC

MELSEC in the IEC Editor

MUL_E with 3 input variables of
data type INT

©

MUL_M for the FX series
MULTI_3_M for the A series

MUL_E with 2 input variables of
data type DINT

©

DMULTI_M for the A series

Advantage: Enables multiplication of up to 28
input variables.

ቢ Dedicated instructions with LEDA/B

GX IEC Developer

Reference Manual

Programming Instructions E - 11

E.2.4

Division

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor
Division of numerical data/with EN
input and ENO output

DIV
DIV_E
Modifier: (

2

Series

Notes

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0
All the MELSEC functions have an EN
input and an ENO output.

MELSEC
IEC Editor

MELSEC
MELSEC Editor

DIV_M
DDIV_M

DIV
DDIV

Division of numerical data (16/32 bit)

3

FX

DIVID_M
DDIVID_M

/
D/

Division of numerical data (16/32 bit)

2

A

Division of numerical data (16/32 bit)

3

Q, QnA, A

DIVID_3_M
DDIVID_3_M
DIV_MD

DIV
Division of floating-point numbers
(with LED* !)ቢ

2

Q, QnA,
AnA

BDIVID_M
DBDIVID_M

B/
DB/

BCD division (16/32 bit)

2

Q, QnA, A For BCD data only

BCD division (16/32 bit)

3

A

BDIVID_3_M
DBDIVID_3_M

IEC

For floating-point numbers only

MELSEC in the IEC Editor

DIV_E with input variables of
data type INT

©

DIVID_M for the A series

DIV_E with input variables of
data type DINT

©

DDIVID_M for the A series

ቢ Dedicated instructions with LEDA/B

Reference Manual

GX IEC Developer

E - 12 Programming Instructions

E.2.5

Move

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor
MOVE
MOVE_E

Moves numerical data/
with EN input and ENO output

1

Series

Notes

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

MOV_M
DMOV_M

MOV
DMOV

Moves numerical data (16/32 bit)

1

Q, QnA, A,
FX, FX0

BMOV_M

BMOV

Block data move

2

Q, QnA, A, Special move operations
FX, FX0

BMOVR_MD

BMOVR
Moves the data from one block to
(with LED* !)ቢ another block with the extension file
registers

2

AnA

FMOV_M

FMOV

Fill move

2

Q, QnA, A,
FX, FX0

SMOV_M

SMOV

Shift move

4

FX

SMOV_MD

SMOV
Character string move
(with LED* !)ቢ

1

Q, QnA,
AnA

IEC

All the MELSEC functions have an EN
input and an ENO output.

MELSEC in the IEC Editor

MOVE_E with 1 input variable of
data type INT

©

MOV_M for the A and FX series

MOVE_E with 1 input variable of
data type DINT

©

DMOV_M for the A and FX series

ቢ Dedicated instructions with LEDA/B

GX IEC Developer

Reference Manual

Programming Instructions E - 13

E.2.6

BCD – BIN conversion

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor

Series

Notes

The IEC functions with input
variables of the INT (DINT) data
Q, QnA, A, type correspond to the MELSEC
functions with 16 (32) bit data.
FX, FX0

INT_TO_BCD
INT_TO_BCD_E

Conversion of binary format (INT) to BCD
format/with EN input and ENO output

1

DINT_TO_BCD
DINT_TO_BCD_E

Conversion of binary format (DINT) to BCD
format/with EN input and ENO output

1

BCD_TO_INT
BCD_TO_INT_E

Conversion of BCD format to binary format
(INT)/with EN input and ENO output

1

BCD_TO_DINT
BCD_TO_DINT_E

Conversion of BCD format to binary format
(DINT)/with EN input and ENO output

1

Q, QnA, A,
FX, FX0

Q, QnA, A,
All the MELSEC functions have an
FX, FX0
EN input and an ENO output.
Q, QnA, A,
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

BCD_M
DBCD_M

BCD
DBCD

Conversion of binary format to BCD format
(16/32 bit)

1

Q, QnA, A,
FX, FX0

BIN_M
DBIN_M

BIN
DBIN

Conversion of BCD format to binary format
(16/32 bit)

1

Q, QnA, A,
FX, FX0

BINDA_MD
DBINDA_MD

Conversion of binary data (16/32 bit) to an
BINDA
ASCII string (decimal)
DBINDA
(with LED* !)ቢ

1

Q, QnA,
AnA

BINHA_MD
DBINHA_MD

Conversion of binary data (16/32 bit) to an
BINHA
ASCII string (hexadecimal)
DBINHA
(with LED* !)ቢ

1

Q, QnA,
AnA

DABIN_MD
DDABIN_MD

Conversion of an ASCII string (decimal) to
DABIN
binary data (16/32 bit)
DDABIN
(with LED* !)ቢ

1

Q, QnA,
AnA

HABIN_MD
DHABIN_MD

Conversion of an ASCII string (hexadecimal) 1
HABIN
to binary data (16/32 bit)
DHABIN
(with LED* !)ቢ

Q, QnA,
AnA

BCDDA_MD
DBCDDA_MD

BCDDA
DBCDDA
(with LED * !)

Conversion of BCD data (16/32 bit) to an
ASCII string (decimal)

1

Q, QnA,
AnA

DABCD_MD
DDABCD_MD

Conversion of an ASCII string (decimal) to
DABCD
BCD coded data (16/32 bit)
DDABCD
(with LED* !)ቢ

1

Q, QnA,
AnA

IEC

For ASCII strings

MELSEC in the IEC Editor

INT_TO_BCD_E

©

BCD_M for the A and FX series

BCD_TO_INT_E

©

BIN_M for the A and FX series

ቢ Dedicated instructions with LEDA/B

Reference Manual

GX IEC Developer

E - 14 Programming Instructions

E.2.7

Logic Operations

Programming instruction

No. of
input
variables

Description

IEC
IEC Editor

Notes

The IEC functions with input variables
of the INT (DINT) data type correspond
Q, QnA, A, to the MELSEC functions with 16 (32)
bit data.
FX, FX0

AND
AND_E
Modifier: N, C

Logical AND operation/with EN input
and ENO output

OR
OR_E
Modifier: N, C

Logical OR operation/with EN input and n
ENO output
(2 – 28)

XOR
XOR_E
Modifier: N, C

Logical exclusive OR
operation/with EN input and ENO
output

n
(2 – 28)

Logical AND operation (16/32 bit)

2

Q, QnA, A

Logical AND operation (16/32 bit)

3

Q, QnA, A,
FX, FX0

Logical OR operation (16/32 bit)

2

Q, QnA, A

Logical OR operation (16/32 bit)

3

A, FX, FX0

Logical exclusive OR
operation (16/32 bit)

2

Q, QnA, A

Logical exclusive OR
operation (16/32 bit)

3

Q, QnA, A,
FX, FX0

Logical exclusive NOR operation
(16/32 bit)

2

Q, QnA, A Exclusive NOR is not available as an IEC
function.

Logical exclusive NOR operation
(16/32 bit)

3

Q, QnA, A

MELSEC
IEC Editor

MELSEC
MELSEC Editor

WAND_M
DAND_M

WAND
DAND

n
(2 – 28)

Series

WAND_3_M
DAND_3_M
WOR_M
DOR_M

WOR
DOR

WOR_3_M
DOR_3_M
WXOR_M
DXOR_M

WXOR
DXOR

WXOR_3_M
DXOR_3_M
WXNR_M
DXNR_M

WXNR

WXNR_3_M
DXNR_3_M

The number of input variables is fixed
Q, QnA, A,
using the MELSEC functions and
FX, FX0
variable using the IEC functions (min. 2,
max. 28).
Q, QnA, A,
FX, FX0
All the MELSEC functions have an EN
input and an ENO output.



AND

AND operation with poll for signal
status 1

1

Q, QnA, A, Input contacts
FX, FX0



ANI

AND operation with poll for signal
status 0

1

A, FX, FX0



OR

OR operation with poll for signal status 1
0

Q, QnA, A,
FX, FX0



ORI

OR operation with poll for signal status 1
0

A, FX, FX0



AND**
ANDD**

AND comparison operations (16/32 bit) 2

Q, QnA, A Comparison
(© Comparisons table)



OR**
ORD**

OR comparison operations (16/32 bit)

Q, QnA, A

IEC

2

MELSEC in the IEC Editor

AND_E with 3 input variables of
data type WORD

©

WAND_3_M for the A and FX series

AND_E with 2 input variables of
data type DWORD

©

DAND_M for the A and FX series

Advantage: Enables operation performance of
up to 28 input variables.

ባ These instructions are not supported by the IEC editor.

GX IEC Developer

Reference Manual

Programming Instructions E - 15

E.2.8

Start of an Operation and Output of a Result

Programming instruction

Description

No. of
input
variables

Series

IEC
IEC Editor
LD
Modifier: N

IEC Instruction List operator
Load specified value/variables into the
accumulator

1

ST
Modifier: N

IEC Instruction List operator
Load specified value/variables into the
accumulator

1

Q, QnA, A,
FX, FX0

Notes
The IEC function LD does not function
as an input condition. This function
loads a value into the accumulator.

The MELSEC LD and LDI functions are
used as the input condition for the
Q, QnA, A, subsequent operations.
FX, FX0
The IEC functions LD and ST are
operators that are only used in the IEC
Instruction List language
Q, QnA, A, (© Chapter 6).

MELSEC
IEC Editor

MELSEC
MELSEC Editor



LD

Start of a logic operation with poll for
signal status 1 (input contact)

1



LDI

Start of a logic operation with poll for
signal status 0 (input contact)

1

Q, QnA, A,
FX, FX0



LD**
LDD**

Start of comparison operations (16/32
bit)

1

Q, QnA, A



OUT

Output, Assignment of a logic
operation result (output coil)

1

Q, QnA, A,
FX, FX0

FX, FX0

ባ These instructions are not supported by the IEC editor.

Reference Manual

GX IEC Developer

E - 16 Programming Instructions

E.2.9

Comparisons

Programming instruction

Description

No. of
input
variables

Series

Notes

GT
GT_E

Decreasing sequence & gt; /with EN input
and ENO output

n
(2 – 28)

The number of input variables is fixed
using the MELSEC functions and
variable using the IEC functions
Q, QnA, A,
(min. 2, max. 28).
FX, FX0

GE
GT_E

Monotonic sequence & gt; =/with EN input
and ENO output

n
(2 – 28)

Q, QnA, A,
FX, FX0

EQ
EQ_E

Equality =/with EN input and ENO
output

n
(2 – 28)

Q, QnA, A,
FX, FX0

LE
LE_E

Monotonic sequence & lt; =/with EN input
and ENO output

n
(2 – 28)

Q, QnA, A,
FX, FX0

LT
LT_E

Increasing sequence & lt; /with EN input
and ENO output

n
(2 – 28)

Q, QnA, A,
FX, FX0

NE
NE_E

Inequality & lt; & gt; /with EN input and ENO
output

2

Q, QnA, A,
FX, FX0

IEC
IEC Editor

MELSEC
IEC Editor

MELSEC
MELSEC Editor



LD & gt;
LDD & gt;

Beginning of a comparison, Sequential
comparison & gt; (16/32 bit)

2

Q, QnA, A



LD & gt; =
LDD & gt; =

Beginning of a comparison, Sequential 2
comparison & gt; = (16/32 bit)

Q, QnA, A



LD=
LDD=

Beginning of a comparison,
Equality = (16/32 bit)

2

Q, QnA, A



LD & lt; =
LDD & lt; =

Beginning of a comparison, Sequential
comparison & lt; = (16/32 bit)

2

Q, QnA, A



LD & lt;
LDD & lt;

Beginning of a comparison, Sequential
comparison & lt; (16/32 bit)

2

Q, QnA, A



LD & lt; & gt;
LDD & lt; & gt;

Beginning of a comparison, Inequality
& lt; & gt; (16/32 bit)

2

Q, QnA, A



AND & gt;
ANDD & gt;

AND comparison,
Sequential comparison & gt; (16/32 bit)

2

Q, QnA, A



AND & gt; =
ANDD & gt; =

AND comparison,
Sequential comparison & gt; = (16/32 bit)

2

Q, QnA, A



AND=
ANDD=

AND comparison,
Equality = (16/32 bit)

2

Q, QnA, A



AND & lt; =
ANDD & lt; =

AND comparison,
Sequential comparison & lt; = (16/32 bit)

2

Q, QnA, A See above



AND & lt;
ANDD & lt;

AND comparison,
Sequential comparison & lt; (16/32 bit)

2

Q, QnA, A



AND & lt; & gt;
ANDD & lt; & gt;

AND comparison,
Inequality & lt; & gt; (16/32 bit)

2

Q, QnA, A



OR & gt;
ORD & gt;

OR comparison,
Sequential comparison & gt; (16/32 bit)

2

Q, QnA, A



OR & gt; =
ORD & gt; =

OR comparison,
Sequential comparison & gt; = (16/32 bit)

2

Q, QnA, A



OR=
ORD=

OR comparison,
Equality = (16/32 bit)

2

Q, QnA, A



OR & lt; =
ORD & lt; =

OR comparison,
Sequential comparison & lt; = (16/32 bit)

2

Q, QnA, A



OR & lt;
ORD & lt;

OR comparison,
Sequential comparison & lt; (16/32 bit)

2

Q, QnA, A



OR & lt; & gt;
ORD & lt; & gt;

OR comparison,
Inequality & lt; & gt; (16/32 bit)

2

Q, QnA, A

GX IEC Developer

Reference Manual

Programming Instructions E - 17

IEC

MELSEC in the IEC Editor

GT_E with 2 input variables of
data type INT

©

LD_GT_M for the A series

GT_E with 2 input variables of
data type DINT

©

LDD_GT_M for the A series

Advantage: Enables comparison of up to 28
input variables.

ባ These instructions are not supported by the IEC editor.

E.2.10

Shift

Programming instruction

Description

No. of
input
variables

Series

Notes
The upper bits are lost in the IEC functions.

IEC
IEC Editor

With the MELSEC functions the upper bits
Q, QnA, A,
are also lost
FX, FX0

SHL
SHL_E

2
Left shift
Shifts the data of the input variable
(IN1) to the left by (N) bits. The
upper (N) bits of (IN1) are lost in
this process/with EN input and ENO
output

SHR
SHR_E

2
Right shift
Shifts the data of the input variable
(IN1) to the right by (N) bits. The
upper (N) bits of (IN1) are lost in
this process /with EN input and ENO
output

Q, QnA, A,
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

SFL_M

SFL

Shift a 16-bit data word to the left
by (n) bits (Carry Flag)

2

Q, QnA, A

SFR_M

SFR

Shift a 16-bit data word to the right 2
by (n) bits (Carry Flag)

Q, QnA, A

SFTL_M

SFTL

Shift bit devices (n) bits to the left

FX

SFTR_M

SFTR

Shift bit devices (n) bits to the right 4

FX

WSFL_M

WSFL

Shift word devices (n) places to the
left

4

FX

WSFR_M

WSFR

Shift word devices (n) places to the
right

4

FX

SFT_M

SFT

Shift bit devices by 1 bit

1

Q, QnA, A

BSFL_M

BSFL

Shift bit devices one place to the
left (Carry Flag)

2

Q, QnA, A

BSFR_M

BSFR

Shift bit devices one place to the
right (Carry Flag)

2

Q, QnA, A

DSFL_M

DSFL

Shift word devices one place to the
left

2

Q, QnA, A

DSFR_M

DSFR

Shift word devices one place to the
right

2

Q, QnA, A

4

IEC

MELSEC in the IEC Editor

SHL_E with input variables of
data type WORD

SFL_M for the A series (Difference: Carry Flag)

SHR_E with input variables of
data type WORD

Reference Manual

©
©

SFR_M for the A series (Difference: Carry Flag)

GX IEC Developer

E - 18 Programming Instructions

E.2.11

Rotation

Programming instruction

No. of
input
variables

Description

Series

Notes
None of the bits are lost.

IEC
IEC Editor
ROL
ROL_E

Rotate left
The data in (IN) are rotated left by (N)
bits; no bits are lost/with EN input and
ENO output

2

Q, QnA, A,
FX, FX0

ROR
ROR_E

2
Rotate right
The data in (IN) are rotated right by (N)
bits; no bits are lost /with EN input and
ENO output

Q, QnA, A,
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

ROL_M
DROL_M

ROL
DROL

Rotate left in A0 and A1 (16/32 bit)

1

Q, QnA, A

ROR_M
DROR_M

ROR
DROR

Rotate right in A0 and A1 (16/32 bit)

1

Q, QnA, A

ROL_2_M
DROL_2_M

ROL
DROL

Rotate left (16/32 bit)

2

FX

ROR_2_M
DROR_2_M

ROR
DROR

Rotate right (16/32 bit)

2

FX

RCL_2_M
DRCL_2_M

RCL
DRCL

Rotate left with Carry Flag (16/32 bit)

2

FX

RCR_2_M
DRCR_2_M

RCR
DRCR

Rotate right with Carry Flag (16/32 bit) 2

FX

RCL_M
DRCL_M

RCL
DRCL

Rotate left in A0 and A1 with Carry Flag 1
(16/32 bit)

Q, QnA, A

RCR_M
DRCR_M

RCR
DRCR

Rotate right in A0 and A1 with Carry
Flag (16/32 bit)

Q, QnA, A

IEC

1

Special rotation

MELSEC in the IEC Editor

ROL_E with input variables of
data type WORD

ROL_M for the A series
(Difference: Carry Flag,
Fixed device A0)

ROR_E with input variables of
data type DWORD

GX IEC Developer

©

©

DROR_M for the A series
(Difference: Carry Flag,
Fixed devices A0 and A1)

Reference Manual

Programming Instructions E - 19

E.2.12

Set and Reset Operations

Programming instruction

Description

No. of
input
variables

IEC
IEC Editor

Series

Notes

In the IEC functions the contents of the
accumulator have an effect on the
execution of the functions
Q, QnA, A,
(© Chapter 6)
FX, FX0

S

1
IEC Instruction List operator
Set
Sets the value of the BOOL variable to
1. This operation is only executed when
the value in the accumulator is 1.

R

1
IEC Instruction List operator
Reset
Sets the value of the BOOL variable to
0. This operation is only executed when
the value in the accumulator is 1.

Q, QnA, A,
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

SET_M

SET

Device set operation

1

Q, QnA, A,
FX, FX0

RST_M

RST

Device reset operation

1

Q, QnA, A,
FX, FX0

BSET_M

BSET

Used to set individual bits in word
devices

2

Q, QnA, A Special set and reset operations

BRST_M

BRST

Used to reset individual bits in word
devices

2

Q, QnA, A

DSET_MD

DSET
Direct set
(with LED* !)ቢ

1

Q, QnA,
AnA

DRST_MD

DRST
Direct reset
(with LED* !)ቢ

1

Q, QnA,
AnA

ZRST_M

ZRST

2

FX

Reset device zones

ቢ Dedicated instructions with LEDA/B

Reference Manual

GX IEC Developer

E - 20 Programming Instructions

E.2.13

Rising/Falling Edge

Programming instruction

No. of
input
variables

Description

Series

Notes

R_TRIG/E_R_TRIG and F_TRIG/E_F_TRIG
are Function Blocks. This means that
you must create instances of them
Q, QnA, A,
before you can use them in your
FX
program (© Chapter 6).

IEC
IEC Editor
R_TRIG
R_TRIG_E

1
Function block
Rising edge detect
The current signal status of the output
variable (Q) changes on the rising edge
on the input variable (CLK)/with EN
input and ENO output

F_TRIG
F_TRIG_E

1
Function block
Falling edge detect
The current signal status of the output
variable (Q) changes on the falling edge
on the input variable (CLK)/with EN
input and ENO output

Q, QnA, A,
FX

MELSEC
IEC Editor

MELSEC
MELSEC Editor

PLS_M

PLS

Generates a single pulse on rising edge; 1
the current signal status changes on a
rising edge.

Q, QnA, A,
FX, FX0

PLF_M

PLF

Generates a single pulse on a falling
edge;
the current signal status changes on a
falling edge.

1

Q, QnA, A,
FX, FX0

IEC

MELSEC in the IEC Editor

R_TRIG_E

PLS_M

F_TRIG_E

E.2.14

©
©

PLF_M

Negation

Programming instruction

No. of
input
variables

Description

Series

Notes

IEC
IEC Editor
NOT
NOT_E

Negation/with EN input and ENO
output

1

Q, QnA, A,
FX, FX0

MELSEC
IEC Editor

MELSEC
MELSEC Editor

CML_M
DCML_M

CML
DCML

Data negation (16/32 bit)
Negation of the individual bits

2

Q, QnA, A,
FX, FX0

NEG_M
DNEG_M

NEG
DNEG

Data negation (16/32 bit)
Formation of the two’s complement

0

Q, QnA, A,
FX, FX0

IEC

MELSEC in the IEC Editor

NOT_E with an input variable
of data type WORD

CML_M

NOT_E with an input variable
of data type DWORD

GX IEC Developer

©
©

DCML_M

Reference Manual

Programming Instructions E - 21

E.2.15

Jumps/Program Branching

Programming instruction

Description

No. of
input
variables

IEC
IEC Editor
0
IEC Instruction List operator.
Jump to a network label.
You can execute a jump to another
network within a program section.
Specify the name (label) of the network
after the operator.

JMP
Modifiers: N, C

Series

Notes

The IEC JMP function is normally
executed without any input condition.
You must use the modifier to program
Q, QnA, A,
a conditional jump.
FX, FX0
Network labels are used as jump
destinations.
(© Chapter 6).

MELSEC
IEC Editor

MELSEC
MELSEC Editor



JMP

Unconditional jump within a program

1

Q, QnA, A



CJ

Conditional jump within a program

1

Q, QnA, A,
FX



SCJ

Conditional jump within a program,
executed in the next program cycle

1

Q, QnA, A

Meaning of the modifiers for the jump function JMP:


JMP

(Jump) The jump is always executed unconditionally.



JMPC

(Jump Conditional) The jump is only executed when the value in the
accumulator is 1.

JMPCN (Jump Conditional Not) The jump is only executed when the value in the
accumulator is 0.
ባ These instructions are not supported by the IEC editor.



E.2.16

Calling Subprograms and Function Blocks

Programming instruction

Description

No. of
input
variables

Series

Notes
The IEC functions are used for jumps to
and returns from Function Blocks.

IEC
IEC Editor
CAL
Modifiers: C, N

IEC Instruction List operator
Call to a Function Block instance.
In Instruction List the instances of
Function Blocks can only be called via
the CAL operator. Specify the instance
name after the operator, then pass the
actual parameters to the formal
parameters.

0

A, FX

RET
Modifiers: C, N

IEC Instruction List operator
Return from a Function Block.
From a Function Block, you can return
to the program from which the
Function Block instance was called.

0

Q, QnA, A,
FX

1

Q, QnA, A,
FX

MELSEC
IEC Editor

MELSEC
MELSEC Editor



CALL

Call a subprogram



SRET

End/return from a subprogram



RET

The MELSEC functions are used for
jumps to and returns from the normal
subroutines/subprograms in the PLC
sequence program.

Terminate Step Ladder

0

FX

0

Q, QnA, A

0

FX

ባ These instructions are not supported by the IEC editor.

Reference Manual

GX IEC Developer

E - 22 Programming Instructions

E.2.17 Exclusive Q Series Instructions
Programming instruction

Description

No. of
input
variables

Series

MELSEC
IEC Editor

MELSEC
MELSEC Editor

UNIRD_M

UNIRD
UNIRDP

Read the module information stored in 3
the area starting from the designated
I/O No. and store it in the area starting
from the designated device.

Q

UNIRDP_M
TRACE_M

TRACE

Store trace data set at a peripheral
device to trace file in IC memory card
by the designated number when
SM800, SM801, and SM802 turn ON.

0

Q

TRACER_M

TRACER

Reset the data set by the TRACE
instruction.

0

Q

SP.FWRITE_M

SP.FWRITE

Write data to a designated file.

6

Notes

Q

SP.FREAD_M

SP.FREAD

Read data from a designated file.

6

Q

PLOADP_M

PLOADP

2
Transfer the program stored in a
memory card or standard memory card
(other than drive 0) to drive 0 und place
the program in stand-by status.

Q

PUNLOADP_M PUNLOADP

Delete the stand-by program stored in
standard memory (drive 0).

2

Q

PSWAPP_M

PSWAPP

Delete stand-by program stored in
designated standard memory (drive 0).
Then the program stored in a memory
card or standard memory (other than
drive 0) is transferred to drive 0 and
placed in stand-by status.

3

Q

RBMOV_M
RBMOVP_M

RBMOV
RBMOVP

Block data move

3

Q

GX IEC Developer

Reference Manual

Menu structure F - 1

F

Menu structure
The following pages show the menu structure of GX IEC Developer. The menu structure and the
available commands are context-sensitive, changing depending on what you are currently doing
in the program.

Project
New...
Open...
Close
Save
Save as...
Other

Ǡ

Delete...
Rename...
Copy...
Import...
Export...
Export to Eprom
Update Libraries

Build
Rebuild All
Transfer

Ǡ

Upload from PLC
Download to PLC
Verify
Download symbolic informations

Online Prog. Change
Browse
Make Cross Reference
Enable MXchange
MXchange actions

Ǡ

Log on
Open Project from MXChange
Show changes
Call Tag-editor
Global Adjust
Change Password
Disable MXchange

Printer Setup...
Print Options...
Print Preview...
Print...
Change Security Level...
Change Passwords...
(Recent Files)
Quit

Reference Manual

GX IEC Developer

F - 2 Menu structure

Object
New

Ǡ

POU...
Task...
Action...
Data Unit Type...

Open
Close
Save
Rename...
Comment...
Information...
Check
Print...
Print Preview...
Import...
Export...

Object
in Body IL, MIL, LD, FBD, ST, SFC
Close
Save
Comment...
Information...
Check
Print...
Print Preview...
Open Header

Object
in declaration editors
Close
Save
Comment...
Information...
Check
Print...
Print Preview...
Open Body

GX IEC Developer

Reference Manual

Menu structure F - 3

Edit
in Navigator
Cut
Copy
Paste
Delete
Find...
Replace...
Update Library
User Library

Ǡ

Install/Create...
Deinstall
Modify...
Open...
Close
Save
Delete
Change Password...

Edit
common items: IL, MIL, LD, FBD, ST, SFC, declaration editors
Undo
Redo
Cut
Copy
Paste
Delete
Find...
Replace...

Edit
specific items: IL, MIL
New Network

Ǡ

Top
Before
After
Bottom
MELSEC Before ᕡ

ᕡ only available in the IEC Instruction List

Edit
specific items: LD, FBD
New Network

Ǡ

Top
Before
After
Bottom

Increment Pins
Decrement Pins
Signal Configuration...
Toggle Signal Config.

Reference Manual

GX IEC Developer

F - 4 Menu structure

Edit
specific items: SFC
Mark
Macro
Expand Macro
Modify

Ǡ

Insert

Ǡ

Name
Initial Step
Final Step
Macro Step
Entry Step
Exit Step
Step/Transition Unit
Step
Transition
Left Divergence
Right Divergence
Left Convergence
Right Convergence
Label
Jump

Edit
specific items: Declaration editors
New Declaration

Ǡ

Top
Before
After
Bottom

Edit
specific items: Entry Data Monitor (EDM) and Header Monitor
Insert Objects...
Next Object
Inert Forced Inputs
Insert Set Inputs
Insert Set Outputs
Clear Device File
Insert Row
Delete Rows
Delete All
Close

Edit
specific items: Show Generated Code
Copy All

GX IEC Developer

Reference Manual

Menu structure F - 5

Tools
in Navigator
Expand
Collapse

Tools
in IL, MIL
Edit Network
End Edit
Network List...
Show MELSEC Code OF
Network
Import GX Developer Network
Import MEDOC Network
List Operators/Operands
Tracking
Ǡ

New Variable...
Zoom

Reference Manual

Ǡ

Start Tracking
Next
Previous
First
Last
Header
Body

GX IEC Developer

F - 6 Menu structure

Tools
in LD and FBD
Network Elements

Ǡ

Contact ᕡ
Coil ᕡ
Jump
Return
Function Block
Input Variable
Output Variable
Horizontal Line Segment
Vertical Line Segment
Comment

Open Row
Open Column
Define Graphic Macros...
Custom

Ǡ

Custom 1
Custom 2
Custom 3
Custom 4
Custom 5

More Custom...
Select Mode
Interconnect Mode
Auto Connect
Recalculate Line
Network List...
Show MELSEC Code Of
Network
List Operators/Operands
Tracking

Ǡ

Start Tracking
Next
Previous
First
Last

New Variable...
Zoom

Ǡ

Header
Body



only available in Ladder Diagram

Tools
in SFC
Edit Action Association
Edit Step Comment
Edit Transition Condition
End Edit
List Operands...
New Variable...
Zoom Macro
Zoom Body
Zoom Into
Zoom Back
Find Error

GX IEC Developer

Reference Manual

Menu structure F - 7

Tools
in declaration editors
Expand Declaration
Collapse Declaration
Sort

Ǡ

Class
Identifier
Type

Find Overlapping Addresses
Address Batch Replace ᕡ



only available in Global Variable List

Tools
in the Entry Data Monitor (EDM) and Header Monitor
Expand Declaration
Collapse Declaration
Read from PLC
Write to PLC
Read from File
Write to File
Setup...
Always on top

Tools
when no project is opened
Reorganize Database

Reference Manual

GX IEC Developer

F - 8 Menu structure

Online
Start Monitoring
Stop Monitoring
Monitor Header
Entry Data Monitor
Modify variable value
Toggle variable
Online-Change Mode
Monitoring Mode
Change Instance...
Start/Stop PLC
PLC Status
PLC Keyword

Ǡ

Transfer Setup

Ǡ

Modem
Ladder Logic Test
PLC Clear

Ǡ

Current
New
Delete
Ports
Project

All
Devices
Latch
Forced Inputs

Format Drive
File Info
Close commuications

Debug
SFC Control ᕡ (Q/QnA only)

PLC Diagnostics
Network Diagnostics
System Monitor
Device Edit
System Errors
User Errors
HW Diagnosis
Scan

Set selected steps
Reset Selected steps
Replace active by selected steps

(not FX)
(Q only)

(not FX)
(not FX)

ᕡ only available in SFC

GX IEC Developer

Reference Manual

Menu structure F - 9

View
Toolbar
Statusbar
Horizontal Scrollbar
Grid
Zoom

Ǡ

50%
75%
100%
150%

Font...
Colors

Ǡ

Background...
Selection...
Text...
Selected Text...
Read Only Text...
Locked Text...
Foreground...
Monitoring...
Errors...
Shade left top...
Shade right bottom...
Grid...
Browsed Item...
SFC Raster Elements...

Save Workspace
Load Workspace
Extended Information
Environment
Configure Status Bar
System Defaults

Extras
Project Backup...
Project Restore...
Declare Externals...
Delete Externals...
Declare MXchange Tags
Delete MXchange Tags
Update Variables
Export Variables
Intelligent Function Utility
Options...
SV

Reference Manual

Start
Verify System Variables
Export Alarm Info...
Update Time
Options...

GX IEC Developer

F - 10 Menu structure

Window
Tile Horizontally
Tile Vertically
Cascade
Arrange Icons
Close All
Navigator
Show Compile/Check
Messages
Show Next Error
Show Previous Error
Show Next Warning
Show Previous Warning

GX IEC Developer

Reference Manual

Compliance List G - 1

G

Compliance List
This list provides a description of all the features of the GX IEC Developer programming and
documentation system that comply with the specifications of IEC standard 61131, Part 3.
The format of the list corresponds to the tables in IEC 61131.3. This makes it possible to obtain
additional information quickly by referring to the corresponding tables and the accompanying
texts in the IEC standard publication.

Note

ISO/IEC 646 character set “A-Z,_”

Supported

2

Lower case characters “a-z”

Supported

3a
3b

Number sign “#”
Pound sign “£”

Supported
Not supported

4a

Dollar sign “$”

Supported

4b
5a
5b

Currency sign
Vertical bar “|”
Exclamation mark “!”

Not supported
Not supported
Not supported

6a
6b

Table 2

Character set features
No. Description
1

Table 1

Left and right brackets “[]”
Left and right parentheses “()”

Supported (Arrays)
Supported

Identifier features
No. Description
1
2
3

Note

Upper case and numbers
Supported
Upper and lower case, numbers, embedded underlines Supported
Upper and lower case, numbers, leading or embedded Supported
underlines

Note

1

Table 3

Comment feature
No. Description

Supported

(*This is a comment*)

Reference Manual

Note

1
2
3
4
5
6
7
8

Table 4

Numeric literals
No. Description

Supported
Not supported
Not supported
Supported
Supported
Supported
Not supported
Supported

Integer literals
Real literals
Real literals with exponents
Base 2 literals
Base 8 literals
Base 16 literals
Boolean zero (0) and one (1)
Boolean FALSE and TRUE

GX IEC Developer

G - 2 Compliance List

Character string literals
No. Description

Note

1

Table 5

Supported

‘’, ‘A’, ‘ ‘, ‘$ " , ‘$R$L " , ‘$0D$0A’, ‘$$1.00’

$$

Not supported

3

$’

Not supported

4
5

$L or $I
$N or $n

Not supported
Not supported

6

$P or $p

Not supported

7
8

Table 7

Note

2

Table 6

Two-character combinations in character strings
No. Description

$R or $r
$T or $t

Not supported
Not supported

Duration literal features
No. Description
1a

Duration literals without underlines:
Short prefix

1b
2a

Long prefix
Duration literals with underlines:
Short prefix
Long prefix

2b

Note
Supported
Not supported
Supported
Not supported

Table 9

Date and time of day literals
No. Description

Note

1
2
3
4
5
6

Table 8

Not supported
Not supported
Not supported
Not supported
Not supported
Not supported

Date literals (long prefix)
Date literals (short prefix)
Time of day literals (long prefix)
Time of day literals (short prefix)
Date and time literals (long prefix)
Date and time literals (short prefix)

Date and time of day literals notation
No. Description
Time literals notation

GX IEC Developer

Note
Not supported

Reference Manual

Compliance List G 3

Note

BOOL

Supported

2

SINT

Not supported

3
4

INT
DINT

Supported
Supported

5

LINT

Not supported

6
7

USINT
UINT

Not supported
Not supported

8

UDINT

Not supported

9
10

ULINT
REAL

Not supported
Supported

11

LREAL

Not supported

12
13

TIME
DATE

Supported
Not supported

14

TIME_OF_DAY or TOD

Not supported

15
16
17
18

DATE_AND_TIME or DT
STRING
BYTE
WORD

Not supported
Supported
Not supported
Supported

19
20

Table 11

Elementary data types
No. Description
1

Table 10

DWORD
Supported
LWORD
Not supported
Plus: EDGE, CHANGE, SGRAY, GRAY, DGRAY, BCD, WFIX, DFIX

Hierarchy of generic data types
No. Description
ANY

Note

ANY_NUM
ANY_REAL
REAL
ANY_INT
DINT
INT

ANY_BIT
DWORD
WORD
BOOL
TIME

Reference Manual

GX IEC Developer

G 4 Compliance List

Note

Direct derivation of elementary data types

Not supported

2

Enumerated data types

Not supported

3
4

Subrange data types
Array data types

Not supported
Supported

5

Table 13

Data type declaration feature
No. Description
1

Table 12

Structured data types

Supported

Default initial values
No. Description
BOOL = FALSE
INT, DINT = 0
WORD, DWORD = 0
REAL = 0.0
TIME = T#0s

Note
Supported
Supported
Supported
Supported
Supported

Note

Initialisation of directly derived types
Initialisation of enumerated data types
Initialisation of subrange data types

Not supported
Not supported
Not supported

4
5
6

Table 15

Data type initial value declaration features
No. Description
1
2
3

Table 14

Initialisation of array data types
Initialisation of structured data type elements
Initialisation of derived structure data types

Not supported
Not supported
Not supported

Location and size prefix features for directly represented variables
No. Description
Note
1
I, Input location
2
Q, Output location
3
M, Memory location
4
X, Single bit size
5
None, Single bit size
6
B, Byte (8 bits) size
7
W, Word (16 bits) size
8
D, Double word (32 bits) size
9
L, Long (quad) word (64 bits) size
* See table page 6 - 4

GX IEC Developer

Supported *
Supported *
Supported *
Supported *
Not supported
Supported *
Supported *
Supported *
Not supported

Reference Manual

Compliance List G - 5

Table 16

Variable declaration keywords
No. Description
VAR / VAR_CONSTANT
VAR_INPUT
VAR_OUTPUT
VAR_IN_OUT
VAR_EXTERNAL / VAR_EXTERNAL_CONSTANT
VAR_GLOBAL / VAR_GLOBAL_CONSTANT
VAR_ACCESS
RETAIN
CONSTANT
AT
* Supported implicitly through the editor

Table 17

Variable type assignment features
No. Description
1
2

Note
Supported
Supported
Supported
Supported
Supported
Supported *
Not supported
Not supported
Not supported
Supported *

Note

Declaration of directly represented, non-retentive variables
Supported
Declaration of directly represented retentive variables
Not supported

3
4

Supported
Supported

5
6
7

Automatic memory allocation of symbolic variables
Array declaration
Retentive array declaration

Supported
Supported
Not supported

8

Table 18

Declaration of locations of symbolic variables
Array location assignment

Declaration of structured variables

Supported

Variable initial value assignment features
No. Description
1
2
3
4
5
6
7
8
9

Reference Manual

Note

Initialisation of directly represented, non-retentive variables
Not supported
Initialisation of directly represented retentive variables
Not supported
Location and initial value assignment to symbolic variables
Not supported
Array location assignment and initialisation
Not supported
Initialisation of symbolic variables
Not supported
Array initialisation
Not supported
Retentive array declaration and initialisation
Not supported
Initialisation of structured variables
Not supported
Initialisation of constants
Not supported

GX IEC Developer

G 6 Compliance List

Note

Negated input

Supported

2

Table 20

Graphical negation of Boolean signals
No. Description
1

Table 19

Negated output

Supported

Use of EN input and ENO output
No. Description
1
2

3

Table 21

Use of EN and ENO
Required for Ladder Diagram (LD) language
Use of EN and ENO
Optional for Function Block Diagram (FBD) language
FBD without EN and ENO

Typed and overloaded functions
No. Description
1
Overloaded functions (untyped)
2
Typed functions
* Implicit typing through passing of the actual parameters

Note
Supported

Supported
Supported

Note
Supported *
Not supported

*_TO_**
TRUNC
BCD_TO_**

Supported
Not supported
Supported

4

Table 23

Note

1
2
3

Table 22

Type conversion function features
No. Description

*_TO_BCD

Supported

Standard functions with one numeric variable
No. Description

Note

1
ABS
Supported
2
SQRT
Supported *
3
LN
Supported *
4
LOG
Not supported
5
EXP
Supported *
6
SIN
Supported *
7
COS
Supported *
8
TAN
Supported *
9
ASIN
Supported *
10
ACOS
Supported *
11
ATAN
Supported *
* Only for PLC systems that support floating point values: Q, QnA, AnA, AnU

GX IEC Developer

Reference Manual

Compliance List G - 7

Standard arithmetic functions
No. Description

Note

12

ADD

Supported

13

MUL

Supported

14
15

SUB
DIV

Supported
Supported

16

MOD

Supported

17
18

Table 24

EXPT
MOVE

Supported *
Supported

* Only for PLC systems that support floating point values: Q, QnA, AnA, AnU
Standard bit-shift functions
No. Description

Note

1

SHL

Supported

2

SHR

Supported

3
4

Table 25

ROR
ROL

Supported
Supported

Standard bitwise Boolean functions
No. Description

Note

5
6
7

AND
OR
XOR

Supported
Supported
Supported

8

Table 26

NOT

Supported

Note

1
2a
2b
3
4

Table 27

Standard selection functions
No. Description

Supported
Supported
Supported
Supported
Supported

SEL
MAX
MIN
LIMIT
MUX

Reference Manual

Note

5
6
7
8
9
10

Table 28

Standard comparison functions
No. Description

Supported
Supported
Supported
Supported
Supported
Supported

GT
GE
EQ
LE
LT
NE

GX IEC Developer

G - 8 Compliance List

Standard character string functions
No. Description

Note

1

LEN

Supported *

2

LEFT

Supported *

3
4

RIGHT
MID

Supported *
Supported *

5

CONCAT

Supported *

6
7

INSERT
DELETE

Supported *
Supported *

8

Table 29

REPLACE

Supported *

9
FIND
Supported *
* Only for PLC systems that support character strings: Q, QnA
Note

1

ADD (TIME, TIME, TIME)

Not supported

2
3

ADD (TOD, TIME, TOD)
ADD (DT, TIME, DT)

Not supported
Not supported

4
5
6

SUB (TIME, TIME, TIME)
SUB (DATE, DATE, TIME)
SUB (TOD, TIME, TOD)

Not supported
Not supported
Not supported

7
8

SUB (TOD, TOD, TIME)
SUB (DT, TIME, DT)

Not supported
Not supported

9
10

SUB (DT, DT, TIME)
MUL (TIME, ANY_NUM, TIME)

Not supported
Not supported

11

DIV (TIME, ANY_NUM, TIME)

Not supported

12
13
14

Table 30

Functions of time data types
No. Description

CONCAT (DATE, TOD, DT)
DT_TO_TOD
DT_TO_D

Not supported
Not supported
Not supported

Table 32

Functions of enumerated data types
No. Description

Note

1
2
3
4

Table 31

Not supported
Not supported
Not supported
Not supported

SEL
MUX
EQ
NE

Function block I/O parameter usage features
No. Description
Input read
Input write
Output read
Output write

GX IEC Developer

Note
Supported
Supported
Supported
Supported

Reference Manual

Compliance List G - 9

Function block declaration features
No. Description

Note

1

RETAIN qualifier on internal variables

Not supported

2

RETAIN qualifier on output variables

Not supported

3
4a

RETAIN qualifier on internal function blocks
Input/output declaration (textual)

Not supported
Supported

4b

Input/output declaration (graphical)

Not supported

5a
5b

Function block instance name as input (textual)
Function block instance name as input (graphical)

Not supported
Not supported

6a

Function block instance name as input/output
(textual)

Not supported

6b

Function block instance name as input/output
(graphical)

Not supported

7a

Function block instance name as external variable
(textual)

Not supported

7b

Function block instance name as external variable
(graphical)

Not supported

8a
8b
9a

Declaration of rising edge inputs (textual)
Declaration of falling edge inputs (textual)
Declaration of rising edge inputs (graphical)

Not supported
Not supported
Not supported

9b

Table 33

Declaration of falling edge inputs (graphical)

Not supported
Note

1
2
3

Table 34

Standard bistable function blocks
No. Description

Not supported
Not supported
Not supported

Bistable function block (set dominant)
Bistable function block (reset dominant)
Semaphore with non-interruptable “Test and Set”

Note

1
2

Table 35

Standard edge detection function blocks
No. Description

Supported
Supported

Rising edge detector
Falling edge detector

Reference Manual

Standard counter function blocks
No. Description

Note

1
2
3

Table 36

Not supported
Not supported
Not supported

Up-counter
Down-counter
Up-down counter

GX IEC Developer

G - 10 Compliance List

Standard timer function blocks
No. Description

Note

1

Table 37

Not supported

TP

2a

Not supported

T—-0
TOF

Not supported
Not supported

3b

Table 38

TON

2b
3a

0—-T

Not supported

Standard timer function blocks — timing diagrams
No. Description
TP
TON
TOF

Table 39

Program declaration features
No. Description
1-9b Features 1 to 9b of table 23
10
Formal input and output parameters
11-14 Features 1-4 of table 17
15-18 Features 1-4 of table 18
19
Use of directly represented variables
20
VAR_GLOBAL...END_VAR
declaration within a program
21
VAR_ACCESS...END_VAR
declaration within a program

Note
Not supported
Not supported
Not supported

Note
Not supported

Supported
Supported
Not supported

Note

1

Table 40

Step features
No. Description

Supported

2
3a
3b
4

GX IEC Developer

Step - graphical form with directed links
Initial step - graphical form with directed links
Step - textual form without directed links
Initial step - textual form without directed links
Step flag - general form:
name.X = a variable of type BOOL
Step flag - direct connection of Boolean variable
name.X to right side of step
Step elapsed time - general form
name.T = a variable of type TIME

Not supported
Not supported
Not supported
Not supported

Reference Manual

Compliance List G 11

Transitions and transition conditions
No. Description

Note

1

Transition condition using ST language

Not supported

2

Transition condition using LD language

*

3
4

Transition condition using FBD language
Use of transition connector

*
Supported

4a

Transition condition in LD language with transition connector
Supported

4b

Transition condition in FBD language with transition connector
Supported

5

Transition condition in ST in textual form

Not supported

6
7

Transition condition in IL in textual form
Transition with transition name

Not supported
Supported

7a

Transition condition using LD language

Supported

7b
7c

Table 41

Transition condition using FBD language
Transition condition using IL language

Supported
Supported

7d
Transition condition using ST language
* Supported through connectors

Table 42

Declaration of actions
No. Description
1

Not supported

Note

2I
2s
2f

Inclusion of SFC elements in an action
Graphical declaration of an action in FBD language

Not supported
Supported

3s
3i

Table 43

Any Boolean variable declared in a VAR or VAR_OUTPUT block,
or their graphical equivalents, can be an action.
Supported
Graphical declaration of an action in LD language
Supported

Textual declaration of an action in ST language
Textual declaration of an action in IL language

Not supported
Supported

Step/action association
No. Description
1
Action block
2
Concatenated action blocks
3
Textual step body with action calls
4
Action block “d” field
* Implemented through the editors

Reference Manual

Note
*
*
Not supported
Not supported

GX IEC Developer

G 12 Compliance List

Action block features
No. Description

Note

1

“a”: Qualifier

Not supported

2

“b”: Action name

Not supported

3
4

“c”: Boolean “indicator” variables
“d”: Action using IL language

Not supported
Not supported

5

“d”: Action using ST language

Not supported

6
7

“d”: Action using LD language
“d”: Action using FBD language

Not supported
Not supported

8

Use of action blocks in ladder diagrams

Not supported

9

Table 44

Use of action blocks in function block diagrams

Not supported

Note

1

None: Non-stored (mull qualifier)

Supported

2
3

N: Non-stored
R: overriding Reset

Not supported
Not supported

4
5
6

S: Set (stored)
L: time Limited
D: time Delayed

Not supported
Not supported
Not supported

7
8

P: Pulse (edge)
SD: Stored and time Delayed

Not supported
Not supported

9
10

Table 45

Action qualifiers
No. Description

DS: Delayed and Stored
SL: Stored and time Limited

Not supported
Not supported

Sequence evolution
No. Description

Note

1
2a

Table 46

Supported
Supported

Single sequence
Divergence of sequence selection, priority of
evaluation from right to left
2b
Divergence of sequence selection, user-defined
priority of evaluation (numbers)
2c
Divergence of sequence selection with user-defined
mutual exclusion of transition conditions as specified
by IEC 848.
3
Convergence of sequence selection
4
Simultaneous sequences — divergence
Simultaneous sequences — convergence
5abc Sequence skip (corresponding to 2a, b, c)
6abc Sequence loop (corresponding to 2a, b, c)
7
Directional arrows in SFC charts

GX IEC Developer

Not supported
Not supported

Supported
Supported
Supported (2a only)
Not supported
Not supported

Reference Manual

Compliance List G - 13

Note

1, 3a, 3b, 4

Not supported

41

1, 2, 3, 4, 4a, 4b, 7, 7a, 7b

Not supported

42
43

1, 2l, 2s, 2f
1, 2, 4

Not supported
Not supported

44

1 to 9

Not supported

45
46

1 to 10
1 to 7

Not supported
Not supported

57

Table 48

Compatible SFC features (graphical only)
No. Description
40

Table 47

all

Not supported

SFC minimal compliance requirements (graphical only)
No. Description

Note

40

1

Supported

41

1 or 2 or 3 or (4 and (4a or 4b)) or
(7 and (7a or 7b or 7c or 7d))

Supported

42

1 or 2l or 2f

Supported

43
45

1 or 2 or 4
1 or 2

*
Supported

46
47

1 and (2a or 2b or 2c) and 3 and 4
(1 or 2) and (3 or 4) and (5 or 6) and (7 or 8) and
(9 or 10) and (11 or 12)
* Implemented through the editors

Reference Manual

Supported
Not supported

GX IEC Developer

G 14 Compliance List

Configuration and resource declaration features
No. Description

Note

1

CONFIGURATION...END_CONFIGURATION
construction
VAR_GLOBAL...END_VAR
construction within CONFIGURATION
RESOURCE...ON...END_RESOURCE
construction
VAR_GLOBAL...END_VAR
construction within RESOURCE
Periodic TASK construction within RESOURCE

Not supported

5a
5b

Non-periodic TASK construction within RESOURCE

Not supported

6a
6b

Table 49

PROGRAM declaration PROGRAM-to-TASK association Not supported
PROGRAM declaration with FUNCTION BLOCK-to-TASK Not supported
association
PROGRAM declaration with no TASK association
Not supported

2
3
4

6c

Not supported
Not supported
Not supported
Not supported

7

Declaration of directly represented variables in
VAR_GLOBAL

Not supported

8a

Not supported

9b
10a
10b

Connection of directly represented variables to
PROGRAM inputs
Connection of GLOBAL variables to PROGRAM inputs
Connection of PROGRAM outputs to directly
represented variables
Connection of PROGRAM outputs to GLOBAL variables
VAR_ACCESS...END_VAR construction
Access paths to directly represented variables

10c
10d
10e

Access paths to PROGRAM inputs
Access paths to GLOBAL variables in RESOURCES
Access paths to GLOBAL variables in CONFIGURATION

Not supported
Not supported
Not supported

10f

Access paths to PROGRAM outputs

Not supported

8b
9a

GX IEC Developer

Not supported
Not supported
Not supported
Not supported
Not supported

Reference Manual

Compliance List G - 15

Task features
No. Description

Note

1a

Textual declaration of periodic TASKS according
to feature 5a of table 49
Textual declaration of non-periodic TASKS according
to feature 5b of table 49
Graphical representation of periodic TASKS

Not supported

2a
2b

Graphical representation of non-periodic TASKS

Supported

3a

Textual association with PROGRAMS according
to feature 6a of table 49

Not supported

3b

Textual association with FUNCTION BLOCKS according
to feature 6b of table 49

Not supported

4a

Graphical association with PROGRAMS
(within RESOURCES)

Supported

4b

Graphical association with FUNCTION BLOCKS
(within PROGRAMS in RESOURCES)

Supported

5a
5b

Table 50

Non-pre-emptive scheduling
Pre-emptive scheduling

Supported
Not supported

1b

Table 51

Examples of instruction fields
No. Description
Label, Operator, Operand

Not supported
Supported

Note
Supported

Note

LD
ST
S, R

Supported
Supported
Supported

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

Reference Manual

Instruction List (IL) operators
No. Description
1
2
3

Table 52

AND, N, (
& , N, (
OR, N, (
XOR, N, (
ADD, (
SUB, (
MUL, (
DIV, (
GT, (
GE, (
EQ, (
NE, (
LE, (
LT, (
JMP, C, N
CAL, C, N
RET, C, N
)

Supported
Not supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

GX IEC Developer

G - 16 Compliance List

Note

CALL with input parameter list

Supported

2

CALL with load/store of input parameters

Supported

3

Table 54

Function block invocation features for IL language
No. Description
1

Table 53

Use of input operators

Not supported

Standard function block input operators for IL language
No. Description

Note

!!!Only relevant when supported in 53.3!!!

Note

1

(Expression) parenthesisation

Supported

2

Function call (argument list)

Supported

3
4
5
6

**
- (Negation)
NOT
*

Supported
Supported
Supported
Supported

7
8

/
MOD

Supported
Supported

9
10

+
- (Subtraction)

Supported
Supported

11

& lt; , & gt; , & lt; =, & gt; =

Supported

12
13
14

=
& lt; & gt;
&

Supported
Supported
Supported

15
16
17

Table 55

Operators of the ST language
No. Description

AND
XOR
OR

Supported
Supported
Supported

GX IEC Developer

ST language statements
No. Description

Note

1
2
3
4
5
6
7
8
9
10

Table 56

Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Assignment :=
Function block invocation and FB output usage
RETURN
IF
CASE
FOR
WHILE
REPEAT
EXIT
Empty statement

Reference Manual

Compliance List G - 17

Representation of lines and blocks
No. Description

Note

1

Horizontal lines: ISO 646 “–” character, semigraphic

Not supported

2

Horizontal lines, graphic

Supported

3
4

Vertical lines ISO 646 “+” character, semigraphic
Vertical lines, graphic

Not supported
Supported

5

Horizontal/vertical connection ISO 646 “+” character,
semigraphic

Not supported

6

Horizontal/vertical connection, graphic

Supported

7

Line crossing without connection ISO 646 characters,
semigraphic

Not supported

8
9

Line crossing without connection, graphic
Connected and non-connected corners ISO 646
“+” character, semigraphic
Connected and non-connected corners, graphic

Supported
Not supported

11

Blocks with connecting lines, ISO 646 character,
semigraphic

Not supported

12
13
14

Table 57

Blocks with connecting lines, graphic
Connectors using ISO 646 characters, semigraphic
Connectors, graphic

Supported
Not supported
Supported

10

Supported

Note

1
2
3

Unconditional jump in FBD language
Unconditional jump in LD language
Conditional jump in FBD language

Supported
Supported
Supported

4
5
6
7
8

Table 58

Graphic execution control elements, examples
No. Description

Conditional jump in LD language
Supported
Conditional return in LD language
Supported
Conditional return in FBD language
Supported
Unconditional return from functions and function blocks Supported
Alternative representation in LD language
Supported

Power bar
No. Description

Note

1
2

Table 59

Supported
Not supported

Left power bar with attached horizontal link
Right power bar with attached horizontal link

Reference Manual

Note

1
2

Table 60

Link elements
No. Description

Supported
Supported

Horizontal link
Vertical link (with attached horizontal links)

GX IEC Developer

G - 18 Compliance List

Contacts
No. Description

Note

1

Normally open contact (make) —| |—

Supported *

2

Normally open contact (make) —! !—

Not supported *

3
4

Normally closed contact (break) —| / |—
Normally closed contact (break) —! / !—

Supported *
Not supported *

5

Positive transition-sensing contact —| P |—

Supported *

6
7

Positive transition-sensing contact —! P !—
Negative transition-sensing contact —| N |—

Not supported *
Supported *

Negative transition-sensing contact —! N !—

Table 61

Not supported *

* Graphical

Coil —( )—

Supported *

2
3

Negated coil —( / )—
SET (latch) coil —( S )—

Supported *
Supported *

4
5
6

RESET (unlatch) coil —( R )—
Retentive (memory) coil —( M )—
SET retentive (memory) coil —( SM )—

Supported
Not supported
Not supported

7
8

RESET retentive (memory) coil —( RM )—
Positive transition-sensing coil —( P )—

Not supported
Not supported

9

GX IEC Developer

Note

1

Table 62

Coils (terminating operations)
No. Description

Negative transition-sensing coil —( N )—

Not supported

Reference Manual

INDEX

Reference Manual

GX IEC Developer

GX IEC Developer

Reference Manual

Index i

INDEX

!
32-bit file access · · · · · · · · · · · · · · · · · · · · · · · · 2-3

A
Absolute address · · · · · · · · · · · · · · · · · · · · · 6-4, A-1
Absolute label · · · · · · · · · · · · · · · · · · · 3-24, 7-26, A-1
Accumulator · · · · · · · · · · · · · · · · · · · · · · · 6-12, A-1
Action · · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-1
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Pool · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-1
Actual parameter · · · · · · · · · · · · · · · · · · · · 6-49, A-1
Address · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-1
Absolute address · · · · · · · · · · · · · · · · · · · · · 6-5
MITSUBISHI address · · · · · · · · · · · · · · · · · · · · 6-5
Array · · · · · · · · · · · · · · · · · · · · · · · · · · 6-59, A-1
Calling · · · · · · · · · · · · · · · · · · · · · · · · · · 6-60
Declaration · · · · · · · · · · · · · · · · · · · · · · · · 6-59
Entry data monitor · · · · · · · · · · · · · · · · · · · · 8-31
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-59
ASCII file
Export · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
Import · · · · · · · · · · · · · · · · · · · · · · · 7-21, 7-23
Auto Update · · · · · · · · · · · · · · · · · · · · · · · · · 6-10
Autoconnect function · · · · · · · · · · · · · · · · · · · · 3-34
Autoextern function · · · · · · · · · · · · · · · · · · · · · 3-48
Autorouting function · · · · · · · · · · · · · · · · · · · · · 3-35

B
Body · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-1, A-1
Editing · · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Information · · · · · · · · · · · · · · · · · · · · · · · 4-17
Opening · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
Breakpoint · · · · · · · · · · · · · · · · · · · · · · · · · · · A-1

C
Call Tree · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-19
Class · · · · · · · · · · · · · · · · · · · · · · · · · 6-4, 6-5, A-1
Closing
Dialog box · · · · · · · · · · · · · · · · · · · · · · · · 3-11
Object · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-9
Window · · · · · · · · · · · · · · · · · · · · · · · · · · 3-9
Collapsing · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-5
Colors · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-14
COM Port· · · · · · · · · · · · · · · · · · · · · · · · · · · 7-11
Release · · · · · · · · · · · · · · · · · · · · · · · · · · 7-11
Comment· · · · · · · · · · · · · · · · · · · · · · · 6-4, 6-8, A-1
Graphical editor · · · · · · · · · · · · · · · · · · 3-29, 3-33
Object · · · · · · · · · · · · · · · · · · · · · · · · · · 4-17
Sequential Function Chart · · · · · · · · · · · · · · 3-6, 6-24
Text editor · · · · · · · · · · · · · · · · · · · · · 3-27, 3-28
Compatibility · · · · · · · · · · · · · · · · · · · · · · · 2-1, 2-16
Compiling · · · · · · · · · · · · · · · · · · · · · · · · · 7-2, A-1
Object · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-3
Project · · · · · · · · · · · · · · · · · · · · · · · · 4-4, 7-2
Compliance list · · · · · · · · · · · · · · · · · · · · · · · · G-1
Computer link module · · · · · · · · · · · · · · · · · · 7-6, A-1
Installation · · · · · · · · · · · · · · · · · · · · · 2-22, 2-24
Copyright · · · · · · · · · · · · · · · · · · · · · · · · · · · 2-2

Reference Manual

Counter
Counter function · · · · · · · · · · · · · · · · · · · · · 6-61
Counter function block · · · · · · · · · · · · · · · · · · 6-63
Extended counter · · · · · · · · · · · · · · · · · · · · · 5-4
Interrupt counter · · · · · · · · · · · · · · · · · · · · · 5-25
Latch range · · · · · · · · · · · · · · · · · · · · · · · · 5-4
Local counter· · · · · · · · · · · · · · · · · · · · · · · 6-63
Parameters · · · · · · · · · · · · · · · · · · · · · · · · 5-7
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-61
CPU type · · · · · · · · · · · · · · · · · · · · · · · · · · · 5-33
Cross Reference · · · · · · · · · · · · · · · · · · · · · · · 4-27
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-27
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-5
Options · · · · · · · · · · · · · · · · · · · · · · · · · 2-11
Query · · · · · · · · · · · · · · · · · · · · · · · · · · 4-28
CSV export · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
CSV-Export · · · · · · · · · · · · · · · · · · · · · · · · · · 2-12

D
Data type · · · · · · · · · · · · · · · · · · · 3-22, 3-23, 6-4, A-2
Hierarchy · · · · · · · · · · · · · · · · · · · · · · · · · 6-9
Data unit type · · · · · · · · · · · · · · · · · · · · · · 6-54, A-2
Calling · · · · · · · · · · · · · · · · · · · · · · · · · · 6-55
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Declaration · · · · · · · · · · · · · · · · · · · · · · · · 6-54
Pool · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-3
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-54
Debugging · · · · · · · · · · · · · · · · · · · · · · · · · · · 8-1
Default setting
Parameters · · · · · · · · · · · · · · · · · · · · · · · · 5-12
Screen display · · · · · · · · · · · · · · · · · · · · · · 3-15
Status bar · · · · · · · · · · · · · · · · · · · · · · · · · 3-7
Device editor· · · · · · · · · · · · · · · · · · · · · · · 8-17, A-2
32-bit value· · · · · · · · · · · · · · · · · · · · · · · · 8-21
Copying · · · · · · · · · · · · · · · · · · · · · · · · · 8-18
Cutting · · · · · · · · · · · · · · · · · · · · · · · · · · 8-18
Deleting devices · · · · · · · · · · · · · · · · · · · · · 8-19
Display mode · · · · · · · · · · · · · · · · · · · · · · · 8-19
File· · · · · · · · · · · · · · · · · · · · · · · · · · 4-1, 8-18
Inserting devices · · · · · · · · · · · · · · · · · · 8-19, 8-20
Keyboard commands · · · · · · · · · · · · · · · · · · · B-5
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-6
Pasting · · · · · · · · · · · · · · · · · · · · · · · · · · 8-18
Pop-up menu · · · · · · · · · · · · · · · · · · · · · · · 8-18
Table in Microsoft Excel · · · · · · · · · · · · · · · · · 8-22
Worksheet · · · · · · · · · · · · · · · · · · · · · · · · 8-17
Dialog box · · · · · · · · · · · · · · · · · · · · · · · · · · 3-11
Closing · · · · · · · · · · · · · · · · · · · · · · · · · · 3-11
Keyboard commands · · · · · · · · · · · · · · · · · · · B-3
Selecting · · · · · · · · · · · · · · · · · · · · · · · · · 3-11
Downloading
SEE Transfer

E
Editing
Body · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
Editor · · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
General· · · · · · · · · · · · · · · · · · · · · · · · · · 3-16
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-29
Object · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-6
Table · · · · · · · · · · · · · · · · · · · · · · · · 3-19, 3-20
Text editor · · · · · · · · · · · · · · · · · · · · · · · · 3-28
Editor · · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-2
Editing · · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
SEE ALSO Graphical editor
SEE ALSO Text editor· · · · · · · · · · · · · · · · · · · 3-27
Emergency off · · · · · · · · · · · · · · · · · · · · · · · · 6-15
EN/ENO · · · · · · · · · · · · · · · · · · · · · · · 4-18, A-2, E-3
Function block · · · · · · · · · · · · · · · · · · · · · · 3-39

GX IEC Developer

ii Index

Entry data monitor· · · · · · · · · · · · · · · · · · · · 8-26, A-2
32-bit register · · · · · · · · · · · · · · · · · · · · · · 8-30
Array · · · · · · · · · · · · · · · · · · · · · · · · · · · 8-31
Changing values · · · · · · · · · · · · · · · · · · · · · 8-30
Deleting objects · · · · · · · · · · · · · · · · · · · · · 8-28
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 8-28
Inserting objects · · · · · · · · · · · · · · · · · · · · · 8-27
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-6
Opening · · · · · · · · · · · · · · · · · · · · · · · · · 8-29
Pop-up menu · · · · · · · · · · · · · · · · · · · · · · · 8-29
Structures · · · · · · · · · · · · · · · · · · · · · · · · 8-30
Worksheet · · · · · · · · · · · · · · · · · · · · · · · · 8-26
Entry Data Monitor
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
Environment · · · · · · · · · · · · · · · · · · · · · · · · · 3-12
Error check
Error message file · · · · · · · · · · · · · · · · · · · · 8-15
Hardware diagnosis · · · · · · · · · · · · · · · · · · · 8-16
Scan · · · · · · · · · · · · · · · · · · · · · · · · · · · 8-16
System errors· · · · · · · · · · · · · · · · · · · · · · · 8-15
User-defined errors · · · · · · · · · · · · · · · · · · · · 8-15
Ethernet · · · · · · · · · · · · · · · · · · · · · · · · · 5-13, 7-7
Installation · · · · · · · · · · · · · · · · · · · · · 2-23, 2-26
Expanding · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-4
Export · · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
ASCII files · · · · · · · · · · · · · · · · · · · · · · · · 7-20
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
Object · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
Project · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
To Eprom· · · · · · · · · · · · · · · · · · · · · · · · · 7-20

Graphical editor · · · · · · · · · · · · · · · · · · 3-29, 6-13, A-3
Anchor point · · · · · · · · · · · · · · · · · · · · · · · 3-37
Autoconnect · · · · · · · · · · · · · · · · · · · · · · · 3-34
Autorouting · · · · · · · · · · · · · · · · · · · · · · · 3-35
Changing editing area spacing · · · · · · · · · · · · · · 3-33
Comment · · · · · · · · · · · · · · · · · · · · · 3-29, 3-33
Configuring input signals · · · · · · · · · · · · · · · · · 3-38
Configuring output coils · · · · · · · · · · · · · · · · · 3-38
Context menu · · · · · · · · · · · · · · · · · · · · · · 3-31
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Function Block Diagram · · · · · · · · · · · · · · · · · 6-13
Inserting elements · · · · · · · · · · · · · · · · · · · · 3-32
Inserting lines · · · · · · · · · · · · · · · · · · · · · · 3-35
Jump instruction · · · · · · · · · · · · · · · · · · · · · 3-41
Keyboard commands · · · · · · · · · · · · · · · · · · · B-8
Ladder Diagram · · · · · · · · · · · · · · · · · · · · · 6-13
Macro · · · · · · · · · · · · · · · · · · · · · · · · · · 3-42
Moving elements · · · · · · · · · · · · · · · · · · · · · 3-34
Options · · · · · · · · · · · · · · · · · · · · · · · · · 3-30
Power bar · · · · · · · · · · · · · · · · · · · · · · · · 3-29
Programming instruction · · · · · · · · · · · · · · · · · 3-43
Recalculate lines · · · · · · · · · · · · · · · · · · · · · 3-36
Rubberbanding · · · · · · · · · · · · · · · · · · · · · · 3-34
Selecting an element · · · · · · · · · · · · · · · · · · · 3-32
Selecting several elements · · · · · · · · · · · · · · · · 3-33
Tools · · · · · · · · · · · · · · · · · · · · · · · · 3-32, C-2
Variable · · · · · · · · · · · · · · · · · · · 3-29, 3-38, 3-45
Grid · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-12

F

Hardware requirements · · · · · · · · · · · · · · · · · · · · 2-1
Header · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-3
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Opening · · · · · · · · · · · · · · · · · · · · · · · · · 3-19
Header monitor· · · · · · · · · · · · · · · · · · · · · · · · 8-26

File structure
MELSEC Q series · · · · · · · · · · · · · · · · · · · · · 7-15
Files · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
Fonts · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-13
Formal parameter · · · · · · · · · · · · · · · · · · · · 6-49, A-2
Function · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-2
Calling · · · · · · · · · · · · · · · · · · · · · · · · · · 6-45
Declaration · · · · · · · · · · · · · · · · · · · · · · · · 6-44
Editing support in text editor · · · · · · · · · · · · · · · 6-45
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-43
Using timer· · · · · · · · · · · · · · · · · · · · · · · · 6-43
Function block · · · · · · · · · · · · · · · · · · · · · · 6-46, A-3
Calling · · · · · · · · · · · · · · · · · · · · · · · · · · 6-48
Declaration · · · · · · · · · · · · · · · · · · · · · · · · 6-47
Editing support in text editor · · · · · · · · · · · · · · · 6-49
Instantiation · · · · · · · · · · · · · · · · · · · · · · · 6-48
Macrocode execution · · · · · · · · · · · · · · · · · · 4-18
MC-MCR · · · · · · · · · · · · · · · · · · · · · · 4-18, 6-50
Using timer· · · · · · · · · · · · · · · · · · · · · · · · 6-46
Function Block
Global FB · · · · · · · · · · · · · · · · · · · · · · · · · 6-53
Macrocode execution · · · · · · · · · · · · · · · · · · 6-50
Function Block Diagram · · · · · · · · · · · · · · · · · · · · A-3
SEE ALSO Graphical editor

G
Global DUT · · · · · · · · · · · · · · · · · · · · · · · · · · 6-55
Global Function Block· · · · · · · · · · · · · · · · · · · · · 6-53
Global variable · · · · · · · · · · · · · · · · · · · · 4-3, 6-4, A-3

GX IEC Developer

H

I
I/O configuration · · · · · · · · · · · · · · · · · · · · · · · 5-8
Icon · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-10
Identifier · · · · · · · · · · · · · · · · · · · · · · · 6-4, 6-5, A-3
IEC address · · · · · · · · · · · · · · · · · · · · · · · · · · 6-5
Ignore checks· · · · · · · · · · · · · · · · · · · · · · · · · 7-14
Import · · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-21
ASCII files · · · · · · · · · · · · · · · · · · · · · 7-21, 7-23
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
MELSEC Upload · · · · · · · · · · · · · · · · · · · · · 7-26
Object · · · · · · · · · · · · · · · · · · · · · · · · · · 7-22
Options · · · · · · · · · · · · · · · · · · · · · · · · · 2-12
Print files · · · · · · · · · · · · · · · · · · · · · · · · · 7-24
Project · · · · · · · · · · · · · · · · · · · · · · · · · · 7-21
Initial value· · · · · · · · · · · · · · · · · · · · · · · · · · · 6-4
Initial Value · · · · · · · · · · · · · · · · · · · · · · · · · · 6-8
Input
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-38
Negation · · · · · · · · · · · · · · · · · · · · · · · · · 3-38
Installation · · · · · · · · · · · · · · · · · · · · · · · · · · · 2-1
Instance · · · · · · · · · · · · · · · · · · · · · · 6-48, 6-50, A-4
Instruction List · · · · · · · · · · · · · · · · · · · · · · · · · A-4
SEE Text editor
Intelligent Function Module Utility · · · · · · · · · · · · · · 8-40
Interconnect mode · · · · · · · · · · · · · · · · · · · · · · 3-31

Reference Manual

Index iii

J
Jump
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-41
Sequential Function Chart · · · · · · · · · · · · · 6-15, 6-18

K
Keyboard
Selecting menu commands · · · · · · · · · · · · · · · · 3-3
Working in tables and editors · · · · · · · · · · · · · · 3-16
Keyboard commands· · · · · · · · · · · · · · · · · · · · · · B-1

L
Label · · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-4
Absolute label · · · · · · · · · · · · · · · · · · · 3-24, 7-26
Network label · · · · · · · · · · · · · · · · · · · · · · 3-24
System label · · · · · · · · · · · · · · · · · · · · 3-24, 5-30
Ladder Diagram · · · · · · · · · · · · · · · · · · · · · · · · A-4
SEE ALSO Graphical editor
Latch range · · · · · · · · · · · · · · · · · · · · · · · · · · 5-4
Library · · · · · · · · · · · · · · · · · · · · · · · · · · 4-6, A-4
Editor · · · · · · · · · · · · · · · · · · · · · · · · · · 3-43
SEE ALSO Manufacturer library
Pool · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-2
SEE ALSO Standard library
SEE ALSO User library
Variable · · · · · · · · · · · · · · · · · · · · · · · · · 3-45
Local DUT · · · · · · · · · · · · · · · · · · · · · · · · · · 6-58
Local variable · · · · · · · · · · · · · · · · · · · · · · · 6-4, A-4

M
MAC transparent mode · · · · · · · · · · · · · · · · · · · · 7-9
Macrocode execution · · · · · · · · · · · · · · · · · · 4-18, 6-50
Manual SFC Control · · · · · · · · · · · · · · · · · · · · · 6-25
Manufacturer library · · · · · · · · · · · · · · · · · 4-6, A-4, E-1
MC-MCR execution
Function block · · · · · · · · · · · · · · · · · · · 4-18, 6-50
Task · · · · · · · · · · · · · · · · · · · · · · · · · · · · 6-2
MELSECNET · · · · · · · · · · · · · · · · · · · · · · · · · 5-13
Memory parameters · · · · · · · · · · · · · · · · · · · · · · 5-2
Menu bar · · · · · · · · · · · · · · · · · · · · · · · · · 3-1, 3-2
Menu commands· · · · · · · · · · · · · · · · · · · · · · · · F-1
Keyboard commands · · · · · · · · · · · · · · · · · · · B-1
MiniNet· · · · · · · · · · · · · · · · · · · · · · · · · · · · 5-32
MITSUBISHI address· · · · · · · · · · · · · · · · · · · · 6-5, A-5
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · · · 2-4
Modem transmission · · · · · · · · · · · · · · · · · · · · · · 7-9
Monitoring· · · · · · · · · · · · · · · · · · · · · · · · 8-23, A-5
Entry data monitor · · · · · · · · · · · · · · · · · · · · 8-26
Header monitor · · · · · · · · · · · · · · · · · · · · · 8-26
Online toolbar · · · · · · · · · · · · · · · · · · · · 8-24, C-4
Program monitor · · · · · · · · · · · · · · · · · · · · · 8-24
Mouse
Selecting menu commands · · · · · · · · · · · · · · · · 3-3
Working in tables and editors · · · · · · · · · · · · · · 3-16

N
Navigator · · · · · · · · ·
Collapsing · · · · · · ·
Displaying objects · · ·
Editing objects · · · · ·
Expanding · · · · · · ·
Extended information ·
Keyboard commands ·
Levels · · · · · · · · ·
Tools · · · · · · · · ·

Reference Manual

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

·
·
·
·
·
·
·
·
·

3-1, 3-3, 4-2, A-6
· · · · · · · 3-5
· · · · · · · 3-4
· · · · · · · 3-6
· · · · · · · 3-4
· · · · · · · 3-6
· · · · · · · B-1
· · · · · 3-4, 3-5
· · · · · · · C-4

Network · · · · · · · · · · · · · · · · · · · · · · 3-23, 6-11, A-5
Changing size · · · · · · · · · · · · · · · · · · · · · · 3-25
Entering a new network · · · · · · · · · · · · · · · · · 3-24
MELSEC network · · · · · · · · · · · · · · · · · · · · · 3-27
MELSEC Network· · · · · · · · · · · · · · · · · · · · · 6-12
Network bar · · · · · · · · · · · · · · · · · · · · · · · 3-23
Network label · · · · · · · · · · · · · · · · · · · · · · 3-24
Network list · · · · · · · · · · · · · · · · · 3-24, 3-25, 6-11
Network Diagnostics · · · · · · · · · · · · · · · · · · · · · · 8-5
Novell · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2-3

O
Object · · · · · · · · · · · · · · · · · · · · · · · · 3-4, 4-1, A-5
Call Tree · · · · · · · · · · · · · · · · · · · · · · · · · 4-19
Closing · · · · · · · · · · · · · · · · · · · · · · · 3-9, 4-15
Comment · · · · · · · · · · · · · · · · · · · · · · · · 4-17
Compiling · · · · · · · · · · · · · · · · · · · · · · · · · 7-3
Copying · · · · · · · · · · · · · · · · · · · · · · · · · 4-16
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Cutting · · · · · · · · · · · · · · · · · · · · · · · · · · 4-16
Deleting · · · · · · · · · · · · · · · · · · · · · · · · · 4-16
Displaying in the navigator · · · · · · · · · · · · · · · · 3-4
Editing · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-6
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Export · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
Import · · · · · · · · · · · · · · · · · · · · · · · · · · 7-22
Information · · · · · · · · · · · · · · · · · · · · · · · 4-17
Keyboard commands · · · · · · · · · · · · · · · · · · · B-1
Opening · · · · · · · · · · · · · · · · · · · · · · · 3-8, 4-15
Pasting · · · · · · · · · · · · · · · · · · · · · · · · · · 4-16
Printing· · · · · · · · · · · · · · · · · · · · · · · · · · 4-22
Reference List · · · · · · · · · · · · · · · · · · · · · · 4-19
Renaming · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Saving · · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Security level · · · · · · · · · · · · · · · · · · · · · · · 4-21
Subordinated objects · · · · · · · · · · · · · · · · · · · 4-19
Superordinated objects · · · · · · · · · · · · · · · · · · 4-19
Online
Changes in online mode · · · · · · · · · · · · · · · · · 7-18
SEE ALSO Monitoring
Online Help System
Keyboard commands · · · · · · · · · · · · · · · · · · · B-11
Online toolbar · · · · · · · · · · · · · · · · · · · · · · 8-24, C-4
Opening
Body · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-23
Header · · · · · · · · · · · · · · · · · · · · · · · · · · 3-19
Object · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-8
Table · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-19
Window · · · · · · · · · · · · · · · · · · · · · · · · · · 3-8
Options · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2-8
Output
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-38
Negation · · · · · · · · · · · · · · · · · · · · · · · · · 3-38
Set/Reset· · · · · · · · · · · · · · · · · · · · · · · · · 3-38

P
Parameters· · · · · · · · · · · · · · · · · · · · · · · · · · · 5-1
Transfer · · · · · · · · · · · · · · · · · · · · · · · · · 7-13
PLC
Changing PLC type · · · · · · · · · · · · · · · · · · · · 5-1
Connecting PLC to PLC · · · · · · · · · · · · · · · · · · 2-19
Setup· · · · · · · · · · · · · · · · · · · · · · · · · · · 5-21
PLC diagnostics · · · · · · · · · · · · · · · · · · · · · · · · 8-1
PLC keyword · · · · · · · · · · · · · · · · · · · · · · · · · 4-21
Pointer · · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-26

GX IEC Developer

iv Index

Printer
Configuration · · · · · · · · · · · · · · · · · · · · · · 4-22
Connection · · · · · · · · · · · · · · · · · · · · · · · · 2-26
Printing · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-22
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-5
Options · · · · · · · · · · · · · · · · · · · · · · · · · 4-23
Program · · · · · · · · · · · · · · · · · · · · · · · · · · · · A-5
Program monitor · · · · · · · · · · · · · · · · · · · · · · · 8-24
Program organisation unit· · · · · · · · · · · · · · · · · 4-5, A-5
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Information · · · · · · · · · · · · · · · · · · · · · · · 4-18
Pool · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-4
Programming instruction · · · · · · · · · · · · 3-43, A-6, E-1, E-2
Assigning variables · · · · · · · · · · · · · · · · · 3-38, 3-45
EN/ENO · · · · · · · · · · · · · · · · · · · · · · · 3-39, E-3
Programming language · · · · · · · · · · · · · · · · · · · · 6-11
SEE ALSO Editors
Project · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1, A-6
Backup · · · · · · · · · · · · · · · · · · · · · · · · · · 4-13
Closing · · · · · · · · · · · · · · · · · · · · · · · · · · 4-12
Compiling · · · · · · · · · · · · · · · · · · · · · · · 4-4, 7-2
Copying · · · · · · · · · · · · · · · · · · · · · · · · · 4-13
Creating · · · · · · · · · · · · · · · · · · · · · · · · · · 4-9
Deleting · · · · · · · · · · · · · · · · · · · · · · · · · 4-12
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Export · · · · · · · · · · · · · · · · · · · · · · · · · · 7-20
Import · · · · · · · · · · · · · · · · · · · · · · · · · · 7-21
Opening · · · · · · · · · · · · · · · · · · · · · · · · · 4-11
Password · · · · · · · · · · · · · · · · · · · · · · · · · 4-20
Printing· · · · · · · · · · · · · · · · · · · · · · · · · · 4-22
Recovering · · · · · · · · · · · · · · · · · · · · · · · · 4-11
Renaming · · · · · · · · · · · · · · · · · · · · · · · · 4-12
Reorganizing · · · · · · · · · · · · · · · · · · · · · · · 4-14
Restore Backup· · · · · · · · · · · · · · · · · · · · · · 4-14
Saving · · · · · · · · · · · · · · · · · · · · · · · · · · 4-12
Security level · · · · · · · · · · · · · · · · · · · · · · · 4-20
Transfer · · · · · · · · · · · · · · · · · · · · · · · 7-4, 7-17
Using Backup· · · · · · · · · · · · · · · · · · · · · · · 4-11
Project specific options · · · · · · · · · · · · · · · · · · · · 2-16
Protection · · · · · · · · · · · · · · · · · · · · · · · · · · 4-20
Object · · · · · · · · · · · · · · · · · · · · · · · · · · 4-21
PLC program · · · · · · · · · · · · · · · · · · · · · · · 4-21
Project · · · · · · · · · · · · · · · · · · · · · · · · · · 4-20
User library · · · · · · · · · · · · · · · · · · · · · · · · 4-8

Q
Quitting MM+ · · · · · · · · · · · · · · · · · · · · · · · · · 2-2

R
Redo · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-17
Reference List · · · · · · · · · · · · · · · · · · · · · · · · 4-19
Remark · · · · · · · · · · · · · · · · · · · · · · · · · · 6-4, 6-8
Replacing data · · · · · · · · · · · · · · · · · · · · · · · · 3-18
Resource · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
Return instruction
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-41

GX IEC Developer

S
Screen display
Customizing · · · · · · · · · · · · · · · · · · · · · · · 3-12
Fonts · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-13
Saving · · · · · · · · · · · · · · · · · · · · · · · · · · 3-15
Zoom factor · · · · · · · · · · · · · · · · · · · · · · · 3-12
Scrollbar · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-12
Searching data · · · · · · · · · · · · · · · · · · · · · · · · 3-18
Select mode · · · · · · · · · · · · · · · · · · · · · · · · · 3-31
Sequential Function Chart · · · · · · · · · · · · · · · · 6-14, A-6
Action · · · · · · · · · · · · · · · · · · · · · · · · · · 6-14
Assigning action to step · · · · · · · · · · · · · · · · · 6-21
Assigning transition condition · · · · · · · · · · · · · · 6-22
Branching · · · · · · · · · · · · · · · · · · · · · · · · 6-14
Comment · · · · · · · · · · · · · · · · · · · · · · · · · 3-6
Initial step · · · · · · · · · · · · · · · · · · · · · · · · 6-14
Jump · · · · · · · · · · · · · · · · · · · · · · · · 6-15, 6-18
Keyboard commands · · · · · · · · · · · · · · · · · · · B-10
Macro step · · · · · · · · · · · · · · · · · · · · · · · · 6-14
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-6
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-16
Sequence errors · · · · · · · · · · · · · · · · · · · · · 6-26
Sequence rules · · · · · · · · · · · · · · · · · · · · · · 6-17
Step · · · · · · · · · · · · · · · · · · · · · · · · · · · 6-14
Tools · · · · · · · · · · · · · · · · · · · · · · · · · · · C-3
Transition · · · · · · · · · · · · · · · · · · · · · · · · 6-14
Zooming · · · · · · · · · · · · · · · · · · · · · · · · · 6-20
SFC Raster Elements · · · · · · · · · · · · · · · · · · · · · 6-20
Software Requirements · · · · · · · · · · · · · · · · · · · · 2-1
Standard library· · · · · · · · · · · · · · · · · · · · 4-6, A-6, E-1
Starting MM+ · · · · · · · · · · · · · · · · · · · · · · · 2-2, 3-2
Status bar · · · · · · · · · · · · · · · · · · · 3-1, 3-7, 3-12, A-6
Configuration · · · · · · · · · · · · · · · · · · · · · · · 3-7
Default setting· · · · · · · · · · · · · · · · · · · · · · · 3-7
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-5
Status Latch · · · · · · · · · · · · · · · · · · · · · · · · · · 5-2
System label · · · · · · · · · · · · · · · · · · · · 3-24, 5-30, A-7
System variable · · · · · · · · · · · · · · · · · · · · · · · · 5-30

T
Table · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-19
Column width · · · · · · · · · · · · · · · · · · · · · · 3-21
Dialog box · · · · · · · · · · · · · · · · · · · · · · · · 3-21
Editing · · · · · · · · · · · · · · · · · · · · · · · 3-19, 3-20
Inserting a new line · · · · · · · · · · · · · · · · · · · 3-21
Keyboard commands · · · · · · · · · · · · · · · · · · · B-4
List box· · · · · · · · · · · · · · · · · · · · · · · · · · 3-21
Opening · · · · · · · · · · · · · · · · · · · · · · · · · 3-19
Selecting a line · · · · · · · · · · · · · · · · · · · · · · 3-20
Selecting cells · · · · · · · · · · · · · · · · · · · · · · 3-20
Selecting several lines · · · · · · · · · · · · · · · · · · 3-20
Sorting entries · · · · · · · · · · · · · · · · · · · · · · 3-21
Task · · · · · · · · · · · · · · · · · · · · · · · · · · · · 6-1, A-7
Creating · · · · · · · · · · · · · · · · · · · · · · · · · 4-15
Information · · · · · · · · · · · · · · · · · · · · · · · 4-19
MC-MCR · · · · · · · · · · · · · · · · · · · · · · · · · · 6-2
Pool · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-3

Reference Manual

Index v

Text editor · · · · · · · · · · · · · · · · · · · · · 3-27, 6-12, A-7
Accumulator · · · · · · · · · · · · · · · · · · · · · · · 6-12
Column width · · · · · · · · · · · · · · · · · · · · · · 3-28
Comment · · · · · · · · · · · · · · · · · · · · · 3-27, 3-28
Editing mode · · · · · · · · · · · · · · · · · · · · · · · 3-28
Error check · · · · · · · · · · · · · · · · · · · · · · · · 7-1
Instruction List · · · · · · · · · · · · · · · · · · · · · · 6-12
Keyboard commands · · · · · · · · · · · · · · · · · · · B-7
MELSEC Instruction List· · · · · · · · · · · · · · · · · · 6-12
Programming instruction · · · · · · · · · · · · · · · · · 3-43
Tools · · · · · · · · · · · · · · · · · · · · · · · · · · · C-2
Variable · · · · · · · · · · · · · · · · · · · · · · · · · 3-45
Texteditor
Strukturierter Text · · · · · · · · · · · · · · · · · · · · 6-12
Timer
Extended timer · · · · · · · · · · · · · · · · · · · · · · 5-4
In function · · · · · · · · · · · · · · · · · · · · · · · · 6-43
In function block · · · · · · · · · · · · · · · · · · · · · 6-46
Latch range · · · · · · · · · · · · · · · · · · · · · · · · 5-4
Local timer · · · · · · · · · · · · · · · · · · · · · · · · 6-63
Parameters · · · · · · · · · · · · · · · · · · · · · · · · 5-7
Programming· · · · · · · · · · · · · · · · · · · · · · · 6-61
Timer function · · · · · · · · · · · · · · · · · · · · · · 6-61
Timer function block · · · · · · · · · · · · · · · · · · · 6-63
Timer interval· · · · · · · · · · · · · · · · · · · · · · · 5-23
Toolbar · · · · · · · · · · · · · · · · · · · · · · · · · 3-1, 3-12
Tools· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · C-1
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-32
Transfer · · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-4
Comparing projects · · · · · · · · · · · · · · · · · · · 7-17
Computer link module · · · · · · · · · · · · · · · · · · · 7-6
Configuring communications port · · · · · · · · · · · · · 7-4
CPU interface · · · · · · · · · · · · · · · · · · · · · · · 7-5
Ethernet · · · · · · · · · · · · · · · · · · · · · · · · · · 7-7
Import · · · · · · · · · · · · · · · · · · · · · · · · · · 7-21
Keyboard commands · · · · · · · · · · · · · · · · · · · B-11
MAC transparent mode · · · · · · · · · · · · · · · · · · 7-9
Modem · · · · · · · · · · · · · · · · · · · · · · · · · · 7-9
Online changes · · · · · · · · · · · · · · · · · · · · · · 7-18
Ports (MMP400.INI) · · · · · · · · · · · · · · · · · · · · 2-6
Setup· · · · · · · · · · · · · · · · · · · · · · · · · · · 7-13

V
Variable · · · · · · · · · · · · · · · · · · · · 3-38, 3-45, 6-4, A-7
Autoextern · · · · · · · · · · · · · · · · · · · · · · · · 3-48
Declaration · · · · · · · · · · · · · · · · · · · · · · · · 6-4
External variable · · · · · · · · · · · · · · · · · · · · · 3-48
SEE ALSO Global variable
Graphical editor · · · · · · · · · · · · · · · · · · · · · 3-38
SEE ALSO Local variable
System variable· · · · · · · · · · · · · · · · · · · · · · 5-30
Text editor · · · · · · · · · · · · · · · · · · · · · · · · 3-27

W
Window · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-8
Arranging · · · · · · · · · · · · · · · · · · · · · · · · · 3-9
Changing display size· · · · · · · · · · · · · · · · · · · 3-10
Closing · · · · · · · · · · · · · · · · · · · · · · · · · · 3-9
Icons · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-10
Opening · · · · · · · · · · · · · · · · · · · · · · · · · · 3-8
Selecting· · · · · · · · · · · · · · · · · · · · · · · · · · 3-8
Wizard · · · · · · · · · · · · · · · · · · · · · · · · · · 4-10, A-7
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-6
Workspace
Loading · · · · · · · · · · · · · · · · · · · · · · · · · 3-15
Saving · · · · · · · · · · · · · · · · · · · · · · · · · · 3-15

Z
Zooming · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2-8

U
Undo · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3-17
USB
Installation · · · · · · · · · · · · · · · · · · · · · · · · 2-26
USB-Port · · · · · · · · · · · · · · · · · · · · · · · · · · · · 7-8
User library · · · · · · · · · · · · · · · · · · · · · · · · 4-6, A-7
Browsing · · · · · · · · · · · · · · · · · · · · · · · · · 4-8
Creating · · · · · · · · · · · · · · · · · · · · · · · · · · 4-7
Deleting · · · · · · · · · · · · · · · · · · · · · · · · · · 4-8
File · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4-1
MMP400.INI · · · · · · · · · · · · · · · · · · · · · · · · 2-5
Password · · · · · · · · · · · · · · · · · · · · · · · · · 4-8
Removing · · · · · · · · · · · · · · · · · · · · · · · · · 4-8
Updating · · · · · · · · · · · · · · · · · · · · · · · · · 4-8

Reference Manual

GX IEC Developer

vi Index

GX IEC Developer

Reference Manual

MITSUBISHI ELECTRIC

V

GX
IEC
veloper
De

MITSUBISHI ELECTRIC

MITSUBISHI ELECTRIC

GX IEC Developer
IEC Programming and
Documentation System

Specifications subject to change without notice.

Art. No.: 43597-F

MITSUBISHI ELECTRIC EUROPE B.V.

V

Reference Manual

GX
IEC
veloper
De