CNC

600 Series
60/60S Series

PLC DEVELOPMENT SOFTWARE MANUAL

(MELSEC TOOL SECTION)

BNP-B2252C(ENG)
MELSEC and MELDAS are the registered trademarks of Mitsubishi Electric Corporation.
Microsoft, Windows and Microsoft Windows NT are the registered trademarks of Microsoft Corporation in
the United States and/or other countries.
Other company and product names herein may be the trademarks or registered trademarks of their
respective owners.
 INTRODUCTION
In the MELDAS600, 60/60S Series, the user PLC development environment is supported using MELSEC
PLC development tool, which is Mitsubishi integrated FA software MELSOFT series (GX Developer), in
addition to the conventional MELDAS PLC programming tool (PLC4B) and onboard ladder tool.
This manual explains user PLC development environment using GX Developer, mainly usage specific to
MELDAS.

Details described in this manual

CAUTION
Items not described in this manual must be interpreted as "not possible".
Some screens and functions may differ depending on the NC system or its version,
and some functions may not be possible. Please confirm the specifications before
use.
General precautions

Refer to the respective manuals for details of the MELDAS series PLCs and for details of various
tools described in this manual. Refer to the MELSEC Series manual for details on the various tools
and instructions for the MELSEC Series.

[MELDAS Series PLC related documents]

MELDAS 60/60S Series PLC Onboard Instruction Manual ……………….. BNP-B2213

MELDAS 60/60S Series PLC Programming Manual (Ladder section with MELSEC tool)
.………………. BNP-B2269
[MELSEC Series Software Package Manual]

GX Developer Version 8 Operating Manual (Startup Section)

GXDEV8-0-IN-E 13JU40 SH-080372E
GX Developer Version 8 Operating Manual
GXDEV8-0-E 13JU41 SH-080373E
GX Converter Version 1 Operating Manual
SW0D5-CNVW (OPE)-E 13J949 IB-080004E

(Caution)
• The version numbers are current as of the editing of this manual, but may be
updated in the future.
• GX Developer Version 8 (Model SW8D5C-GPPW) is the new name of the old
"Windows Version GPP Function Software package" (common name GPPW).
 Precautions for Safety
Always read the specifications issued by the machine maker, this manual, related
manuals and attached documents before installation, operation, programming,
maintenance or inspection to ensure correct use.
Understand this numerical controller, safety items and cautions before using the unit.
This manual ranks the safety precautions into "Danger", "Warning" and "Caution".

When the user may be subject to imminent fatalities or major

DANGER
injuries if handling is mistaken.

When the user may be subject to fatalities or major injuries if

WARNING
handling is mistaken.

CAUTION When the user may be subject to bodily injury or when physical
damage may occur if handling is mistaken.

Note that even items ranked as " CAUTION", may lead to major results depending on
the situation. In any case, important information that must always be observed is
described.

DANGER
Not applicable in this manual.

WARNING
Not applicable in this manual.

CAUTION
1. Items related to product and manual
For items described as "Restrictions" or "Usable State" in this manual, the instruction
manual issued by the machine maker takes precedence over this manual.
An effort has been made to describe special handling of this machine, but items that
are not described must be interpreted as "not possible".
This manual is written on the assumption that all option functions are added. Refer to
the specifications issued by the machine maker before starting use.
Refer to the Instruction Manual issued by each machine maker for details on each
machine tool.
Some screens and functions may differ depending on the NC system or its version,
and some functions may not be possible. Please confirm the specifications before
use.

2. Precautions for startup and maintenance

Before starting program modification, forced output, RUN, STOP or similar operation
during running, read the manual carefully and ensure safety fully. Not doing so can
cause machine damage or accidents due to operation mistakes.
(Continued on next page)
 CAUTION
3. Items related to program development
Always observe the cautions before development to develop a program.
If the data transferred does not follow the file name rule, the NC will mistake it for
another data, resulting in unexpected operation, e.g. PLC program erasure.
Do not read a ladder file on which a conversion error occurred into the GX Developer
side. The file may include unexpected contents to result an illegal operation.
When an error occurred at GX Developer On-line function, the error message may not
explain exactly the state in the CNC controller side.
Always refer to the error list.
 CONTENTS

1. PLC DEVELOPMENT ENVIRONMENT..........................................................................1

1.1 System Configuration ................................................................................................1
1.2 Software Configuration ..............................................................................................2
1.3 Outline of GX Developer Functions and List of Supported Functions ......................4
1.3.1 Function support conditions (general section) ..................................................4
1.3.2 Function support conditions (on-line section)....................................................8
1.4 Memory Specifications ............................................................................................11
1.4.1 Memory configuration ......................................................................................11
1.4.2 PLC data storage method................................................................................11
1.4.3 Selecting the memory with GX Developer ......................................................12

2. SETUP ............................................................................................................................14
2.1 Setting up Each Tool ...............................................................................................14
2.2 RS-232C Connection Procedures...........................................................................14
2.3 Setting the CNC Parameters...................................................................................15

3. PLC PROGRAM DEVELOPMENT................................................................................17

3.1 User PLC (Ladder) Development Procedure ..........................................................18
3.2 Precautions before Development ............................................................................19
3.3 Newly Creating a PLC Program ..............................................................................21
3.4 Specifying the Connection Target ...........................................................................22
3.4.1 Operation procedure........................................................................................22
3.5 Starting/Stopping the PLC of the CNC Controller ...................................................23
3.5.1 Operation procedure........................................................................................23
3.6 Writing the PLC Program to the CNC Controller.....................................................24
3.6.1 Operation procedure........................................................................................24
3.6.2 Operation to be performed at write error .........................................................24
6.6.3 How to confirm the error step number.............................................................25
3.7 Reading the PLC Program from the CNC Controller ..............................................26
3.7.1 Operation procedure........................................................................................26
3.8 Verifying the PLC Programs ....................................................................................28
3.8.1 Operation procedure........................................................................................28
3.9 Monitoring the PLC Program...................................................................................29
3.9.1 Operation procedure........................................................................................29
3.10 Using PLC4B Type PLC Programs .......................................................................30
3.10.1 Development procedure ................................................................................30
3.10.2 Starting GX Converter and specifying the file to be converted .....................31
3.10.3 Conversion format setting..............................................................................31
4. PLC MESSAGE DEVELOPMENT ................................................................................34
4.1 Development Procedure..........................................................................................34
4.1.1 Using a general text editor...............................................................................35
4.1.2 Entering messages directly from GX Developer .............................................35
4.2 Message Data Description Method .........................................................................36
4.2.1 Description format............................................................................................36
4.2.2 Description method..........................................................................................37
4.2.3 Precautions ......................................................................................................38
4.3 Converting Data into GX Developer Format ...........................................................39
4.3.1 Starting GX Converter and specifying the file to be converted .......................39
4.3.2 Conversion format setting................................................................................39
4.4 Entering/Editing Data Using GX Developer ............................................................41
4.4.1 Interlinear statement display using circuit display ...........................................41
4.4.2 Interlinear statement display using list display ................................................42
4.4.3 Editing of integrated type interlinear statements .............................................43
4.5 Writing to the CNC Controller ..................................................................................44
4.6 Reading and Verifying from the CNC Controller .....................................................44
4.6.1 Menu selection/screen operation.....................................................................44
4.6.2 Message read format.......................................................................................45

5. DEVICE COMMENT CREATION ..................................................................................46

5.1 Development Procedure..........................................................................................46
5.2 Description Method for Indirect Entry ......................................................................47
5.3 Converting Device Comments.................................................................................48
5.3.1 Starting GX Converter and specifying the file to be converted .......................48
5.3.2 Conversion format setting................................................................................48

6. RELATIONSHIPS BETWEEN GX DEVELOPER AND ONBOARD FUNCTIONS .....51

6.1 Function Differences................................................................................................51
6.2 Specification Differences .........................................................................................51

7. PROCEDURE FOR WRITING PLC PROGRAMS, ETC. TO ROM..............................53

7.1 Data That Can Be Written to ROM..........................................................................53
7.2 ROM Writing Operation Procedure .........................................................................53

8. LIST OF ERROR STATES ............................................................................................55

APPENDIX 1. OPERATION METHODS USING GPPQ...................................................57
Appendix 1.1 GPPQ Function Outline and Functions Supported by the M600,
M60/60S Series .......................................................................................57
Appendix 1.1.1 Function support conditions (general section) ................................57
Appendix 1.1.2 Function support conditions (on-line section) .................................60
Appendix 1.2 Ladder Transfer to the CNC Controller...................................................65
Appendix 1.2.1 Menu selection.................................................................................65
Appendix 1.2.2 Screen operation .............................................................................65
Appendix 1.2.3 Operation during a transfer error.....................................................66
Appendix 1.2.4 Error step No. confirmation method ................................................66
Appendix 1.3 Ladder Read from the CNC Controller ...................................................67
Appendix 1.3.1 Menu selection.................................................................................67
Appendix 1.3.2 Screen operation .............................................................................67
Appendix 1.4 Ladder Comparison with CNC Controller ...............................................68
Appendix 1.4.1 Menu selection.................................................................................68
Appendix 1.4.2 Screen operation .............................................................................68
Appendix 1.5 PLC-Related Data Development Procedure...........................................69
Appendix 1.5.1 Conversion to GPPQ data...............................................................69
Appendix 1.5.2 Commercially available software QnA conversion setting............70
Appendix 1.5.3 Conversion execution......................................................................70
Appendix 1.5.4 Operation with the GPPQ................................................................71
Appendix 1.5.5 Transfer to the controller .................................................................73
Appendix 1.5.6 Reading and comparing from the controller....................................73
Appendix 1.6 Procedure for ROM Writing.....................................................................75
Appendix 1.6.1 Procedure to write to ROM..............................................................75
Appendix 1.6.2 PLC data region formatting .............................................................76
Appendix 1.6.3 ROM writing from the GPPQ...........................................................76

APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN

PLC4B AND M600, M60/60S ....................................................................79
Appendix 2.1 Development Tools, etc. .........................................................................79
Appendix 2.2 Devices and Device Assignments...........................................................80
Appendix 2.3 PLC Instructions ......................................................................................84
Appendix 2.3.1 Instructions that cannot be handled with the GX Developer ..........84
Appendix 2.3.2 Instructions with the format that differs from that of the
GX Developer ..................................................................................85
Appendix 2.3.3 Instructions that can be used with the GX Developer, but cannot
be used by the M600, M60/60S ......................................................86

APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER .................87

Appendix 3.1 Sequence Instructions.............................................................................87
Appendix 3.2 Comparison Operation Instructions ........................................................88
Appendix 3.3 Application Instructions ...........................................................................93
 1. PLC DEVELOPMENT ENVIRONMENT
1.1 System Configuration

1. PLC DEVELOPMENT ENVIRONMENT

1.1 System Configuration
Most of the development work can be done by connecting a personal computer and a CNC unit by
an RS-232C cable.
[Note] The supported peripheral devices and like change depending on the model.

GX Developer (GPPW) system

Personal computer

GX Developer
Printout
(GPPW)
General-purpose printer

PLC program creation

Message creation Ladder printout
Ladder monitor Message printout

RS -232C

CNC control unit

MELDAS 600, 60/60S series Floppy disk unit IC card unit

Onboard development Data save

PLC program editing ROM cassette Floppy disk drive unit DOS format FLD IC card
Ladder monitor
ROM making
New development is enabled by offline
development only.

-1-
 1. PLC DEVELOPMENT ENVIRONMENT
1.2 Software Configuration

1.2 Software Configuration

PLC development tool

(1)
for MELSEC
GX Developer
(2)
Data conversion
package for MELSEC
(3)
GX Converter
Ladder list converter
PLC onboard CLST6L (4)
Comment converter
CLST6M
QnA simulator R S -2 3 2 C List output converter (5)
PCNV6L
*1
IBM PC/AT
CNC controller Compatible PC
*1:IBM PC/AT compatible personal
computer with Windows OS

(1) GX Developer (PLC development software package)

GX Developer is a programming software package (model name: SW8D5C-GPPW) designed

for Mitsubishi Electric's MELSEC series programmable logic controllers. By performing
operations similar to those of the MELSEC series, you can develop user PLC ladders for the
MELDAS series. Note that some functions specific to the "MELSEC series" may not be
unavailable.
For MELDAS series ladder development, we recommend you to use GX Developer Version 4
(SW4D5C-GPPW) or later. For function details, refer to the Operating Manual supplied.
The DOS version "GPPQ" (SW2IVD/NX-GPPQ GPP function software package) of this
package is also usable. Refer to Appendix "OPERATION METHODS USING GPPQ" for details.

(2) GX Converter (data conversion software package)

The GX Converter is a tool that carries out data conversion of GX Developer data files and the
following (Start up GX converter from the GX Developer menu as a add-on tool for GX
Developer):
• Ladder list files and comment text files output by the CLST6L
• Alarms and operator messages created by the text editor
• Data files of commercially available spreadsheet software, word processors and editors
This tool is a software package for various MELSEC support. GX Converter needs to be used
with the versions following GX Developer Version 3 (SW3D5C-GPPW). Refer to the enclosed
Operating Manual for function details.
The DOS version "CNVQ" (SW0IVD/NX-CNVQ data conversion software package) of this tool
can also be used. Refer to Appendix "OPERATION METHODS USING GPPQ" for details.

(3) CLST6L (Ladder list converter)

This tool converts the user PLC ladder list data developed for the PLC4B to M600, M60/60S
specification instructions and devices, and outputs the data in a ladder list format. The user
PLC ladder developed in the PLC4B can be used for M600, M60/60S Series with the GX
Developer by using the GX Converter to further convert the conversion results of this tool.
This tool runs on Windows DOS.

-2-
 1. PLC DEVELOPMENT ENVIRONMENT
1.2 Software Configuration

(4) CLST6M (Device comment converter)

This tool outputs the contact/coil comment data of a user PLC ladder developed for the PLC4B
in the text format of the M600, M60/M60S series device specifications. The contact/coil
comment data developed in the PLC4B can be used with GX Developer by using GX Converter
to further convert the conversion results of this tool.
This tool runs on Windows DOS.

(5) PCNV6L (List output converter)

This tool outputs a MELDAS specification ladder printout image with cross information in a text
format from the GX Developer specification ladder list and comment data.
This tool runs on Windows DOS.

-3-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

1.3 Outline of GX Developer Functions and List of Supported Functions

The GX Developer functions explained here are those supported by the M600, M60/60S Series in
the "off-line functions" operated with the GX Developer independently and "on-line functions" carried
out connected to the M600, M60/60S controller.
Refer to the enclosed Operating Manual for function details.
Refer to "APPENDIX 1. OPERATION METHODS USING GPPQ" for the GPPQ-specific functions
and operations when the DOS version "GPPQ" (SW2IVD/NX-GPPQ GPP function software
package) of this package is used.

1.3.1 Function support conditions (general section)

The following shows a list of GX Developer outline functions supported by the M600, M60/60S
Series.
A mark indicates functions that can be used by the M600, M60/60S Series. An r mark indicates
that the function cannot be used because it is related to "MELSEC Series" characteristic functions.
The function details during on-line are described in the next section.

List of general section functions (1) : Possible, : Limitedly possible, U : Not possible
Program type Support Remarks
Ladder
List
SFC U
MELSAP-L U
Function block U

Function Menu Sub menu Support Remarks

Project New project
Open project
Close project
Save
Save as
Delete project
Verify
Copy
Edit Data New
Copy
Delete
Rename
Change PLC type Fixed Q4A
Import file Import from GPPQ format file
Import from GPPA format file U
Import from FXGP(DOS) format file U
Import from FXGP(WIN) format file U
Import from TEXT ,CSV format file
Export file Export to GPPQ format files
Export to GPPA format files U
Export to FXGP(DOS) format file U
Export to FXGP(WIN) format file U
Export to TEXT ,CSV format file

-4-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

List of general section functions (2) : Possible, : Limitedly possible, U : Not possible
Function Menu Sub menu Support Remarks
(Project) Macro Registration macros
Macro utilize
Delete macros
Macro reference path
Printer setup
Print
Start new GX Developer session
Exit GX Developer
Edit Undo
Restore after ladder conversion
Cut
Copy
Paste
Insert line
Delete line
Insert row
Delete row
Insert NOP batch
Delete NOP batch
Draw line
Delete line
Change TC setting
Read mode
Write mode
Ladder symbol Open contact
Close contact
Open branch
Close branch
Coil
Application instruction
Vertical line
Horizontal line
Delete vertical line
Delete horizontal line
Rising pulse Instead of DEFR
Falling pulse U
Rising pulse open branch U
Falling pulse close branch U
Invert operation results U
Convert operation results to U
rising pulse
Convert operation results to U
falling pulse
Documentation Comment
Statement
Note
Statement/Note block edit

-5-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

List of general section functions (3) : Possible, : Limitedly possible, U : Not possible
Function Menu Sub menu Support Remarks
Find/Replace Find device
Find instruction
Find step no.
Find character string
Find contact or coil
Replace device
Replace instruction
Change open/close contact
Replace character string
Replace unit head I/O No. U
Replace statement/note type
List of used contact coils
List of used devices
Convert Convert
Convert (All programs being
edited)
Convert (Online change) U
View Comment
Statement
Note
Alias
Macro instruction format display
Comment format 4*8 characters
3*5 characters
Alias format display Replace device name and
display
Arrange with device and display
Toolbar
Status bar
Zoom 50%
75%
100%
150%
Specify
Auto
Project data list
Instruction list
Set the contact 9 contacts
11 contacts
Elapsed time U
Online Refer to "List of on-line section Refer to "List of on-line section
functions" functions"

Diagnostics PLC diagnostics U

MELSECNET(II)/10/H U
diagnostics
Ethernet diagnostics U
CC-Link/CC-Link/LT diagnostics U
System monitor U
Online module change U

-6-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

List of general section functions (4) : Possible, : Limitedly possible, U : Not possible
Function Menu Sub menu Support Remarks
Tools Check program
Merge data
Check parameter U
Transfer ROM Read U
Write U
Verify U
Write to file U
Delete unused comments
Clear all parameters U
IC memory card Read IC memory card U
Write IC memory card U
Read image data U
Write image data U
Start ladder logic test U
Set TEL data Connection U
Disconnection U
TEL data U
AT command U
Call book U
Intelligent function utility Utility list U
Customize keys
Change display color
Options Limited partly
Create start-up setting file
Window Cascade
Tile vertically
Tile horizontally
Arrange icons
Close all windows
Help CPU error U
Special relay/register U
Key operation list
Product information
Connect to MELFANSweb

-7-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

1.3.2 Function support conditions (on-line section)

The following shows a list of GX Developer on-line functions supported by the M600, M60/60S
Series.
A mark indicates functions that can currently be used by the M600, M60/60S Series. An r mark
indicates that the function cannot be used because it is related to "MELSEC Series" characteristic
functions.

List of on-line section functions (1) : Possible, : Limitedly possible, U : Not possible
Menu Sub menu Detailed function Support Remarks
Transfer setup PC side I/F
PLC side I/F Only for QnACPU
Other station U
Network route U
Co-existence network U
route
Read from PLC Target memory
Title
File selection
Device data U
Program U
Common U
Local U
Refresh view
Free space volume
Create title U
Write to PLC Target memory
Title
File selection
Device data U
Program U
Common U
Local U
Free space volume
Create title U
Verify with PLC Target memory
Title
File selection
Program U
Refresh view
Free space volume
Create title U
Write to PLC Write the program U
(Flash ROM) memory to ROM
Write to PLC U
(Flash ROM)
Delete PLC data Target memory
Title
File selection
Refresh view
Free space volume
Create title U
Change PLC data U
attributes
PLC user data Read PLC user data U
Write PLC user data U
Delete PLC user data U

-8-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

List of on-line section functions (2) : Possible, : Limitedly possible, U : Not possible
Menu Sub menu Detailed function Support Remarks
Monitor Monitor mode ON/OFF state
Scan time display U
CPU state display
Monitor [Write mode] U
Start monitor
[All windows]
Stop monitor
[All windows]
Start monitor
Stop monitor
Change current value
monitor [Decimal]
Change current value
monitor [Hexadecimal]
Local device monitor
Device batch Device
Connect
Coil
Setting value
Current value
Monitor format : Bit & word
Monitor format : Bit
Monitor format : word
Display : 16bit integer
Display : 32bit integer
Display : Real number U
Display : ASCII character U
Value : DEC
Value : HEX
T/C set value Reference
program
Device test
Entry data monitor Device
ON/OFF/Current
Setting value
Connect
Coil
Display : 16bit integer
Display : 32bit integer
Display : Real number U
Display : ASCII character U
Value : DEC
Value : HEX
T/C setting value, Local
label Reference program
Device test
Buffer memory batch U
Monitor condition setup Device
Step No.
Monitor stop condition setup Device
Step No.
Program monitor list U
Interrupt program monitor list U
Scan time measurement U
Entry ladder monitor
Delete all entry ladder

-9-
 1. PLC DEVELOPMENT ENVIRONMENT
1.3 Outline of GX Developer Functions and List of Supported Functions

List of on-line section functions (3) : Possible, : Limitedly possible, U : Not possible
Menu Sub menu Detailed function Support Remarks
Debug Device test FORCE ON
FORCE OFF
Toggle force
Device
Buffer memory U
Forced input output U
registration/cancellation
Debug U
Skip execution U
Partial execution U
Step execution U
Trace Sampling trace U
Remote operation PLC status
RUN
STOP
PAUSE U
Latch clear U
STEP-RUN U
Reset U
Operation during RUN, U
STEP-RUN
Specify execution U
destination
Keyword setup Register U
Delete U
Disable U
Clear PLC memory U
Format PLC Target memory Only internal RAM other than
memory ladder storage area.
Format Type U
Arrange PLC U
memory
Set time YY MM DD Hr. Min. Sec.
Day of week U
Specify execution U
destination

- 10 -
 1. PLC DEVELOPMENT ENVIRONMENT
1.4 Memory Specifications

1.4 Memory Specifications

1.4.1 Memory configuration

The M600, M60/60S series stores PLC data onto flash ROM (hereafter abbreviated to the F-ROM).
The following shows the storage area structure.

F-ROM (for storage)

Control information area

Non-ladder file storage

area such as messages 128 Kbyte
and device comments

256 Kbyte
Control information area

Ladder storage area 128 Kbyte

1.4.2 PLC data storage method

The PLC data transferred from GX Developer are stored in either of the following two storage
methods, which differs depending on the model.

(1) Two-step storage method (M600 series)

As for the transferred data, the PLC ladder code is first stored into the nonvolatile RAM area
(hereafter abbreviated to the S-RAM) designed for execution. The non-ladder PLC data are
stored into the normal RAM area (hereafter abbreviated to the D-RAM).
Write them to the F-ROM on the CNC controller side I/O screen. At power-ON of the CNC
controller, the data are transferred from the F-ROM to the S-RAM and D-RAM areas, where
they will be executed.

GX Developer Internal F-ROM

D-RAM

S-RAM Cassette F-ROM

(2) Direct storage method (M60/60S series)

The transferred data are stored into the F-ROM area designed for both storage and execution.
They can also be copied to the cassette F-ROM area for maintenance purpose.

GX Developer Internal F-ROM Cassette F-ROM

- 11 -
 1. PLC DEVELOPMENT ENVIRONMENT
1.4 Memory Specifications

1.4.3 Selecting the memory with GX Developer

(1) Areas that can be selected on GX Developer

The following table indicates the storage areas that can be selected for the online functions
(Write to PLC, Read from PLC, Verify with PLC) of GX Developer.
Function M600 series M60/60S series
Write to PLC S-RAM Internal F-ROM
Read from PLC, S-RAM Internal F-ROM
Verify with PLC Internal F-ROM
Cassette F-ROM

- 12 -
 1. PLC DEVELOPMENT ENVIRONMENT
1.4 Memory Specifications

(2) Display of storage area on GX Developer

Any of the storage areas that can be selected for the online functions (Write to PLC, Read from
PLC, Verify with PLC) of GX Developer can be specified as a [Target memory] item on the
corresponding operation screen.
Also, pressing the [Title] button displays the comment of that storage area if PLC data exists. It
is not displayed if the storage memory is not fitted or the data does not exist.
Further, pressing the [Free space volume] button displays [Total free space volume] and
[Largest continuous volume] of the selected area.

Some storage areas displayed as the target memory differ from the actual storage areas of the
CNC controller. The following tables indicates the relationships between the [Target memory]
items and storage areas.

Table 1.4.3.1 M600 series

Meaning in
Screen indication Title indication Free area indication
M600 series
Internal RAM Internal S-RAM ON BOARD S-RAM Target : All storage areas
(ladder program) + (D-RAM) of Internal RAM
IC Card A[RAM] Internal D-RAM ON BOARD D-RAM Target : Non-ladder file
(non-ladder data) storage area
IC Card A[ROM] Internal F-ROM ON BOARD F-ROM Target : All storage areas
of Internal F-ROM
IC Card B[RAM] Not used
IC Card B[ROM] Cassette F-ROM ADD ON F-ROM Target : All storage areas
of cassette F-ROM

Table 1.4.3.2 M60/60S series

Meaning in
Screen indication Title indication Free area indication
M60/60S series
Internal RAM/ Internal F-ROM ON BOARD F-ROM Target : All storage areas
Device memory of Internal F-ROM
IC Card A[RAM] Not used
IC Card A[ROM] Not used
IC Card B[RAM] Not used
IC Card B[ROM] Not used

- 13 -
 2. SETUP
2.1 Setting up Each Tool

2. SETUP
2.1 Setting up Each Tool
In the M600 M60/60S Series PLC development environment, it is assumed that the various tools
are used with an IBM PC/AT compatible personal computer. Prepare each tool so that it is IBM
PC/AT compatible personal computer.
Refer to the enclosed Operating Manual (Startup) and Operating Manual for the setup and start
procedures of each tool.

2.2 RS-232C Connection Procedures

The serial port connected with the CNC controller differs depending on the model. Also, it may
require a special branch cable. Refer to the connection manual of that model.

Between the IBM PC/AT compatible personal computer that uses GX Developer and the CNC
controller, use an RS-232C serial cable equivalent to the one shown below in the RS-232C
connection diagram.

[Note]
The cables given in the connection diagrams of the GX Developer Operating Manual cannot be
used.
Settings such as the GPPW communication speed are not required on the NC side.

Personal
NC side
computer side
(25-pin D-SUB)
(9-pin D-SUB)
Cable
Pin Pin
Signal name connection and Signal name
No. No.
signal direction
CD 8 1 DC
SD 2 2 RD
RD 3 3 SD
DR (DSR) 6 4 ER (DTR)
SG 7 5 SG
ER (DTR) 20 6 DR (DSR)
CS (CTS) 5 7 RS (RTS)
RS (RTS) 4 8 CS (CTS)
22 9 RI
∗ The above shows a general RS-CS method connection format.
∗ The pin Nos. of dotted lines are not used.

- 14 -
 2. SETUP
2.3 Setting the CNC Parameters

2.3 Setting the CNC Parameters

Each model of the M600, M60/60S series has bit selection parameters related to GX Developer. If
an appropriate value is not set in the parameters, an error will occur in communication with GX
Developer.

(1) M600M series

7 6 5 4 3 2 1 0
# (51) Data (0 0 1 0 0 0 0 0)

0 : GPP communication enabled

Use No. 51. 1 : GPP communication disabled
[Reference] #51 corresponds to the low side of the file register R5025.

Bit 5 = 0
The serial port is used for communication with GX Developer.
(This serial port cannot be used concurrently with the other function.)
Bit 5 = 1
The serial port is not used for communication with GX Developer.
(When the serial port is used for another function)

(2) M600L series

7 6 5 4 3 2 1 0
# (6451) Data (0 0 1 1 0 0 0 0)
1 : GPPW mode
Use No. 6451. 0 : GPP communication disabled
1 : GPP communication enabled

[Reference] #6451 corresponds to the low side of the file register R2925.

Bit 4 = 1
The PLC development environment of GX Developer is used.
Bit 5 = 0
The serial port is not used for communication with GX Developer.
(When the serial port is used for another function)
Bit 5 = 1
The serial port is used for communication with GX Developer.
(This serial port cannot be used concurrently with the other function.)

- 15 -
 2. SETUP
2.3 Setting the CNC Parameters

(3) M60/60S series

7 6 5 4 3 2 1 0
# (6451) Data (0 0 1 1 0 0 0 0)
0 : PLC4B mode
1 : GPPW mode
Use No. 6451.
0 : GPP communication disabled
1 : GPP communication enabled
[Reference] #6451 corresponds to the low side of the file register R2925.

(a) PLC environment selection parameter

Choose the PLC development environment. Independently of the setting of this bit, the currently
stored ladder of either format operates.
Note that the onboard function is inactive if the format of the currently stored ladder differs from
the environment selected here.

Bit 4 = 0
The PLC development environment of PLC4B is used.
Bit 4 = 1
The PLC development environment of GX Developer is used.

(b) GPPW serial port use selection parameter

When using the PLC development environment of GX Developer, choose whether the serial
port used for communication with GX Developer will be used or not.

Bit 5 = 0
The serial port is not used for communication with GX Developer.
(When the serial port is used for another function)
Bit 5 = 1
The serial port is used for communication with GX Developer.
At this time, the onboard function is not started if bit 4 = 1.
When the GPPW serial port use selection parameter is set to "1" (enabled),
GPPW occupies the communication so communication (input/output) other than
GPPW cannot be used.

- 16 -
 3. PLC PROGRAM DEVELOPMENT

3. PLC PROGRAM DEVELOPMENT

This chapter mainly describes MELDAS-specific usage about the PLC program development
procedure.

- 17 -
 3. PLC PROGRAM DEVELOPMENT
3.1 User PLC (Ladder) Development Procedure

3.1 User PLC (Ladder) Development Procedure

The following indicates a procedure for creating a general user PLC ladder.

Procedure Personal Computer CNC Unit

Start

Determination of
machine
Determination of
CNC and PLC
specifications
Determination of the Commercially available
numbers of I/O points spreadsheet tool The data created with the
Device Name Commen t
Assignment of I/O X0 X-OT X-axis OT
commercially available
signals X1 Y-OT Y-axis OT spreadsheet tool can be
Assignment of X2 Z-OT Z-axis OT
used as ladder comment
internal relays
data.
GX Developer
Use GX Developer for
Programming programming.
After completion, download
the data through RS-232C.

Onboard
GX Developer Perform monitoring/correction
Debugging
(RAM operation) with GX Developer's online
function or onboard function.
Program correction

Is debugging I/O screen

NO complete? ROM writing is enable with
YES On-board or Input/Output
screen.
ROM writing
[Note]
ROM making operation is not
ROM operation by
CNC unit necessary for the MELDAS
60/60S series.
Is ROM
operation OK?
NO
YES GX Developer

Printout to a commercial
Printout
printer connected with the
personal computer from GX
Developer.

Program data:
Data save onto FLD
Saved using GX Developer
Binary data:
Completion Program data Binary data Saved using I/O screen

- 18 -
 3. PLC PROGRAM DEVELOPMENT
3.2 Precautions before Development

3.2 Precautions before Development

Pay careful attention to the following items before developing ladder programs using the GX
Developer.

(1) PLC Type Selection

The PLC type must be set when newly creating programs, etc. Select the following CPU type when
requested to select the PLC type by the GX Developer. An error will occur during transfer of the
ladder program to the CNC controller if another PLC type is selected.

CAUTION Select "Q4A" for CPU type.

(2) Device Setting

Do not set the devices when developing the ladder program for the CNC controller. Develop the
program with the device settings (No. of points, etc.) left at their default values applied when GX
Developer was started. The ladder program cannot be transferred to the CNC controller normally
when it is developed with settings other than the default values.

CAUTION Do not set the devices.

(3) PLC Instructions

MELSEC-specific PLC instructions cannot be used in the ladder program development for the CNC
controller. Only PLC instructions and formats in PLC programming manual can be used.
The format, etc., are changed with some instructions. Refer to "Appendix 2. DIFFERENCES IN
DEVELOPMENT ENVIRONMENT BETWEEN PLC4B AND M600, M60/60S" for details.

CAUTION MELSEC-specific PLC instructions cannot be used.

(4) Label at the beginning of ladder program

In a MELDAS ladder program, a processing unit is differentiated by specifying a reserved label

number at the beginning of processing. There are the following different processing units. (Since
programmable processings are changed depending on the model, refer to the PLC programming
manual of that model.)
P251 : PLC high-speed processing program starting label
P252 : PLC main processing program starting label
P253 : Initial processing program starting label
If only the PLC main processing is to be performed, do not omit but describe the above label at the
beginning of a ladder program. Unless the label is described, normal RUN cannot be performed.

CAUTION Specify a label at the beginning of a ladder program.

- 19 -
 3. PLC PROGRAM DEVELOPMENT
3.2 Precautions before Development

(5) Statements and notes

GX Developer allows a ladder program to be commented (with interlinear statements and notes).
They are available in two types: integrated and peripheral.
Integrated type : Can be downloaded together with a ladder program to the CNC
controller.
Peripheral type : Cannot be downloaded.
The integrated type cannot be used with the M600, M60/60S series. If it is used, a ladder program
cannot be transferred to the CNC controller properly.

CAUTION Do not use integrated type interlinear statements and

notes.
(6) File Name

Inside the M600, M60/60S series, PLC-related data are controlled and stored in the following
categories. Therefore, they are also developed in the same categories.

CAUTION
If the data transferred does not follow the file name rule, the NC will mistake
it for another data, resulting in unexpected operation, e.g. PLC program
erasure.

File name rule

M1 xxxx. W PG or W CD

Extensions .... Automatically attached with the GX Developer

(expresses file classification)
Random file name .... User free designation

Data classification and language classification .... user fixed

(M1: Message 1st language) designation

When data is transferred by GX Developer, its data type is distinguished by the file name.
An extension indicates a file type, and the first two characters denote a data type and a language
type.
The file name can be designated with eight characters (excluding the extension) which contain the
data type and language type.
[Note] Unusable file name
Data type : "M", "C" or "H" (alphabet)
Language type : "0" to "9" (numeral)
at the beginning of a file name are reserved on the NC side. Do not use the file name of this
combination.

- 20 -
 3. PLC PROGRAM DEVELOPMENT
3.2 Precautions before Development

List of PLC related data

File name
Related data classification Remarks
(GX Developer)
1 PLC program (ladder) zzzzzz.WPG PLC ladder code
2 PLC program comment zzzzzz.WCD Comment data for GX Developer
3 Message 1st language M1xxxx.WPG 1st language for alarm/operator
messages, PLC switches, tool
registration comments/load meter
comments
4 Message 2nd language M2xxxx.WPG Same as above
(2nd language data)

(a) PLC program (ladder)

• Ladder program developed using GX Developer.

• Only one file can be stored in the NC.

(b) PLC program comment

• Program comment for GX Developer display

• Only one file can be stored in the NC with the same file name as the ladder program.
• A device comment (32 characters) and a device name (10 characters) can be defined for each
device.
• Stored mainly when it is read to GX Developer and used as a comment.

(c) Message 1st language, (d) Message 2nd language

• Alarm message/operator message/PLC switch/comment message data.

• One 1st language file and one 2nd language file can be stored in the NC.
• The messages can be handled and edited as "integrated type interlinear statements" by GX
Developer.
• The maximum message length and the number of messages can be specified for each message
type.

3.3 Newly Creating a PLC Program

The ladder program is newly created with GX Developer.
Refer to the Operating Manual for details on newly creating a program.

- 21 -
 3. PLC PROGRAM DEVELOPMENT
3.4 Specifying the Connection Target

3.4 Specifying the Connection Target

You must specify the connection target before performing online operations from GX Developer to
the CNC controller.

3.4.1 Operation procedure

Perform the following operation from GX Developer to start the setting screen.

[Online] → [Transfer setup]

Set only the following items. Leave the other items unchanged from the initial values.

(1) Personal computer side

Interface : [Serial interface]

Serial port name : [COM1] or [COM2]
Baudrate : [19.2Kbps]

(2) PLC side

Interface : [CPU unit]

J Setting screen of SW4D5-GPPW

- 22 -
 3. PLC PROGRAM DEVELOPMENT
3.5 Starting/Stopping the PLC of the CNC Controller

3.5 Starting/Stopping the PLC of the CNC Controller

Before writing a PLC program, you must stop the PLC of the CNC controller.

3.5.1 Operation procedure

Perform the following operation from GX Developer to start the operation screen.

[Online] → [Remote operation] or Alt + 6

On the following screen, set "STOP" or "RUN" in the [PLC] part under [Operation] and click
[Execute]. The current status is displayed in [PLC status] under [Connection target information].

[Note] Operations other than RUN and STOP are not possible.

The operation is completed when the following dialog appears. Click [OK]. The status after
completion appears in [PLC status] on the remote operation screen displayed behind. If the status
does not change, check whether an alarm is displayed or not on the CNC controller side.

- 23 -
 3. PLC PROGRAM DEVELOPMENT
3.6 Writing the PLC Program to the CNC Controller

3.6 Writing the PLC Program to the CNC Controller

The following indicates how to write ladders from GX Developer to the CNC controller (especially
the restrictions and M600, M60/60S series-specific operations).

3.6.1 Operation procedure

Perform the following operation from GX Developer to start the operation screen.

[Online] → [Write to PLC]

On the following screen, choose the ladder file to be written from the [File selection] tab and click
[Execute].
You can command RUN/STOP of the PLC using [Remote operation] under [Related functions].

[Note] As [Target memory], only [PLC RAM/Device memory] is valid.

Do not set the other tabs ([Device data], [Program], [Common], [Local]) than [File
selection].

3.6.2 Operation to be performed at write error

As soon as a ladder is written from GX Developer to the CNC controller, the CNC controller
converts it into the CNC-specific ladder machine code. A conversion error occurs if any of the
devices and instruction formats not supported by the M600, M60/60S series is used.
At a conversion error, the CNC side ladder machine code is converted into the "NOP code", the
ladder up to the last step is transferred, and the following dialog is then displayed on the GX
Developer screen.

- 24 -
 3. PLC PROGRAM DEVELOPMENT
3.6 Writing the PLC Program to the CNC Controller

When the file that resulted in a conversion error is displayed with the [File selection] tab of the
[Read from PLC] screen, the following warning appears in the title field.
"∗∗ WARNING Checksum ERROR!! ∗∗"
If you execute RUN the PLC as-is, an alarm occurs on the CNC side and the PLC does not RUN.

CAUTION
Do not read a ladder file on which a conversion error occurred into the GX
Developer side. The file may include unexpected contents to result an illegal
operation.
3.6.3 How to confirm the error step number

The PLC verification function can be used to confirm the error step. Executing verification with PLC
displays mismatches as in the following example. For details of the PLC verification function, refer to
"3.8 Verifying the PLC Programs".
Following example shows the step where CNC controller outputs a conversion error because NOP
instructions mismatched between CNC and GX Developer.
Double-click the mismatch to display and to edit the corresponding part of the GX Developer side.
<Memory> indicates the GX Developer side, and <PLC> the CNC controller side.

GX Developer side CNC controller side

- 25 -
 3. PLC PROGRAM DEVELOPMENT
3.7 Reading the PLC Program from the CNC Controller

3.7 Reading the PLC Program from the CNC Controller

The following indicates how to read a ladder from the CNC controller to GX Developer.

3.7.1 Operation procedure

Perform the following operation from GX Developer to start the operation screen.

[Online] → [Read from PLC]

On the following screen, choose the ladder file to be read from the [File selection] tab, and click
[Execute].

[Note] As [Target memory], the fitted memory is valid.

Do not set the other tabs ([Device data], [Program], [Common], [Local]) than [File
selection].

If a ladder file with the same name already exists in the GX Developer side, following dialogue will
appear.

[Note] Choosing [Yes (Y)] in the dialogue will overwrite the GX Developer side ladder file. The
file before overwriting will be erased.
Confirm the file enough before choosing [Yes (Y)].

- 26 -
 3. PLC PROGRAM DEVELOPMENT
3.7 Reading the PLC Program from the CNC Controller

The [Read from PLC] screen can also be used as a CNC controller side file listing function. Move
the scroll bar of the [File selection] tab to the right to display the write date and size of each file.
Click [Free space volume] to display the free area of the target memory.

- 27 -
 3. PLC PROGRAM DEVELOPMENT
3.8 Verifying the PLC Programs

3.8 Verifying the PLC Programs

The following indicates how to verify ladders between the CNC controller and GX Developer.

3.8.1 Operation procedure

Perform the following operation from GX Developer to start the operation screen.

[Online] → [Verify with PLC]

On the following screen, choose the ladder files to be verified from the [File selection] tab, and click
[Execute].
[Verify source] : GX Developer side [Verify dest] : CNC side

[Note] As [Target memory], the fitted memory is valid.

Do not set tabs ([Program]) other than [File Selection].

If verification mismatches occur, the following mismatch screen appears. Double-click the mismatch
to display the corresponding part of the GX Developer side file.

GX Developer side CNC controller side

- 28 -
 3. PLC PROGRAM DEVELOPMENT
3.9 Monitoring the PLC Program

3.9 Monitoring the PLC Program

There are no MELDAS-specific operations to monitor a PLC program. Refer to the Operating
Manual for the operation methods. For usable functions, refer to "1.3.2 Function support conditions
(on-line section)". This section explains the operation procedure outline and precautions.

3.9.1 Operation procedure

Perform the following operation from GX Developer to start monitoring.

(1) Display the ladder program to be monitored and move to the circuit part to be monitored.

(2) Perform the following operation to start monitoring.

[Online] → [Monitor] → [Monitor mode] or F3

(3) Perform the following operation to stop monitoring.

[Online] → [Monitor] → [Stop monitor] or Alt + F3

[Note] If the ladder program being run by the CNC controller differs from the one being displayed
on GX Developer, monitoring will not result in an error but will continue.

- 29 -
 3. PLC PROGRAM DEVELOPMENT
3.10 Using PLC46 Type PLC Programs

3.10 Using PLC4B Type PLC Programs

The PLC program developed with the conventional MELDAS PLC programming tool (PLC4B) can
be used.

3.10.1 Development procedure

IBM PC/AT compatible personal computer

Creation
PLC4B/LIST4B
LIST4B output
ladder list
zzzz.TXT
Ladder list conversion
CLST6L
Ladder list for
M600, M60
zzzz.TXT
List to ladder conversion
GX Converter CNC controller
Ladder data
for M600, M60
zzzz.W PG
Editing (transfer)
GX Developer

RS232C

Device Messages for

comments M600, M60
for M600, M60
zzzz. W CD M1xxx.W PG

(1) Creation
The PLC program created for the old model is output in a list format.

(2) Conversion
Using CLST6L (ladder list converter), the output program is converted into a PLC program for
M600, M60/60S series (list format). Using GX Converter (data conversion software package),
the list format program is converted into the GX Developer data.

(3) Editing/transfer
The resultant program can be handled like a newly created PLC program.

- 30 -
 3. PLC PROGRAM DEVELOPMENT
3.10 Using PLC46 Type PLC Programs

3.10.2 Starting GX Converter and specifying the file to be converted

Perform the following operation from GX Developer to start GX Converter (read).

[Project] → [Import file] → [Import to TEXT ,CSV format file]

On the following screen, choose the file to be converted (LDTEST.TXT) and click [OK].

3.10.3 Conversion format setting

Set the conversion format on the following data conversion wizard screen.

(1) Data conversion wizard 1/4

Choose [Original Data Type]-[Delimited] and [Data Type]-[List], and click [Next>].

- 31 -
 3. PLC PROGRAM DEVELOPMENT
3.10 Using PLC46 Type PLC Programs

(2) Data conversion wizard 2/4

Choose [Delimiters]-[Tab] and click [Next>].

(3) Data conversion wizard 3/4

Choose to highlight the Instruction column part in the [Data Preview] list and choose [Column
Data Format]-[Instr].

(4) Data conversion wizard 3/4

Further, choose to highlight the Argument column part in the [Data Preview] list and choose
[Column Data Format]-[I/O(Device)]. Click [Next>].

- 32 -
 3. PLC PROGRAM DEVELOPMENT
3.10 Using PLC46 Type PLC Programs

(5) Data conversion wizard 4/4

Set the program name used on GX Developer at [Data name] column and a ladder annotation
at [Title] column, and click [Finish].

(6) Completion

The setting is complete when the following completed dialog appears after the converting dialog.
Click [OK].

- 33 -
 4. PLC MESSAGE DEVELOPMENT
4.1 Development Procedure

4. PLC MESSAGE DEVELOPMENT

This chapter describes a procedure for developing PLC-related data such as alarm messages,
operator messages, and PLC switches.

4.1 Development Procedure

There are the following two methods as a general development procedure of message data.

(1) Making conversion into GX Developer data using a general text editor or spreadsheet tool and
data conversion package.
(When there is a large volume of message data and you want to control them with a
commercially available tool, for example)

(2) Entering messages directly from GX Developer

(When there is a small volume of message data or when addition or correction is to be made,
for example)

IBM PC/AT compatible personal computer

Creation
Spreadsheet tool
Text editor
M600, M60
message
M1 xxx.TXT
Conversion
GX Converter
CNC controller
M600, M60
message
M1xxx.W PG
Transfer (edit)
GX Developer

RS232C

M600, M60 M600, M60

device comment ladder
zzzz.W CD zzzz. W PG

- 34 -
 4. PLC MESSAGE DEVELOPMENT
4.1 Development Procedure

4.1.1 Using a general text editor

(1) Creation

The message data is described using a general text editor. The description method and format
will be described later.

(2) Conversion

The conversion from text data to GX Developer data is carried out using the "GX Converter
(data conversion software package)".

(3) Transfer

With the GX Developer, the message data is handled as a PLC program interlinear comment,
and can also be edited.
The message data is transferred to the CNC controller using the GX Developer, in the same
manner as the ladder program.

4.1.2 Entering messages directly from GX Developer

(1) Creation

The message data is described directly from GX Developer. The message data is handled as a
PLC program interlinear comment by GX Developer. The description method and format will be
described later.

(2) Transfer

The message data is transferred from GX Developer to the CNC controller in the same manner
as the ladder program.

- 35 -
 4. PLC MESSAGE DEVELOPMENT
4.2 Message Data Description Method

4.2 Message Data Description Method

The message data can be described as text data by a general text editor and also by commercially
available spreadsheet software in addition to the direct input with GX Developer.

4.2.1 Description format

Message data is classified into setting areas to store the setting for each message and message
areas to store message data. It is described in the following respective description format.

(1) Setting area

The message length and No. of messages are set for each message in the setting area. The
message data region secured by the CNC controller can be adjusted to the most efficient status
using these settings. The respective maximum values are set if nothing is set. (Refer to "4.2.3
Precautions" for the maximum values.)

;$, message classification code, maximum message length, No. of messages [CR]

Alarm message : A Operator message : O

PLC switch :P Comment message : M

(2) Message area

The message area is described using the following description format.

The description format cannot be abbreviated. Comma(,) and [CR] must be described, even the
message character string is blank.

Message classification Description format

Alarm message ;A, index No., data register No., message character string [CR]
Operator message ;O, index No., data register No., message character string [CR]
PLC switch ;P, switch No., message character string [CR]
Comment message ;M, device, device No., message character string [CR]

Message classification : A one-byte alphabetic character expressing each message

code classification
Index No. : One-byte number (0 to No. of messages in the setting area - 1)
Switch No. : One-byte number (0 to No. of messages in the setting area - 1)
Data register No. : One-byte number
Device : One-byte number (1 or 2)
Device No. : One-byte number (0 to 10)
Message character : One-byte alphanumeric character, No. of characters in the setting
string area message length.
Semicolons, commas, spaces and tabs can also be used. Note that
the tab at the head of the message character string is ignored.
Semicolon( ; ) : Message data identification code
Comma( , ) : Separator between each description (a comma only is used to leave
a message character string blank)
[CR] : Line feed code, (CR/LF) or (LF).

- 36 -
 4. PLC MESSAGE DEVELOPMENT
4.2 Message Data Description Method

4.2.2 Description method

The message data is described as text data by the following description format.

;#M635 ladder ver1. '97.08.01 ... Comment

;$, A,32, 200
;$, 0, 40, 200 ... Setting area
;$, P, 14, 32
;$, M, 60, 20
NOPLF
;A, 0, 0, Emergency stop
;A, 11, 1, Spindle alarm
:
:
NOPLF ... Message area (alarm messages)
:
:
NOPLF
:
:
NOPLF ... Page break code
;0, 1, 9000, MELDAS 600LADDER Ver1.0
;0, 20, 9000, BND-400W000-A0 ... Message area (operator messages)
:
:
NOPLF
;P, 1, Program restart
;P, 2, Automatic power OFF ... Message area (PLC switches)
:
:
NOPLF
;M, 1, 0, [Spindle]
;M, 1, 0, [Standby 1] ... Message area (comments)
:
:
END ... End code

(1) Comment

Statements having a semicolon (;) at the head of the line, in a different format than described in
"4.2.1 Description format", are regarded as comments. These comments are handled as
comment data in the GX Developer also, but are erased during the transfer to the CNC
controller. An error will occur if there is no semicolon at the head of the line.

(2) Setting area

Each message is set here. This area must be described before the message area of the
relevant message. That setting will be ignored if it is described in the middle of or after the
relevant message description.

(3) Message area

Collect similar messages in a group and describe them. There is no description order in the
respective messages, but the latter description is validated if there are descriptions with the
same factors (index No., etc.).

(4) Page break code

A page break code is described at one or more places approx. every 15 lines in the setting area
and message area. The message data may skip if there is no page break code.

- 37 -
 4. PLC MESSAGE DEVELOPMENT
4.2 Message Data Description Method

(5) End code

An end code is described at the end of the description. Description after the end code are
ignored.
An error will occur if there is no end code.

4.2.3 Precautions

No. of characters, quantity limitations, handling of information other than settings, handling of
information other than format are described below.

(1) Message data maximum value

Processing will be carried out with the following values considered as the maximum values if the
setting is not carried out in the setting area, or if the description position in the setting area is
illegal.

Data size by multiplying

Message Max. message Max. No. of
max. message length by
classification length messages
max. No. of messages
Alarm messages 32 byte 512 16 Kbyte
Operator messages 60 byte 512 30 Kbyte
PLC switches 14 byte 32 0.5 Kbyte
Comments 60 byte 100 6 Kbyte

[Note] Two-byte data in the message character string is handled as two characters.
GX Developer accepts 64 characters as an interlinear comment. However, since that
includes information other than a message character string (e.g. message classification
code, index No. and data register No.), the message character string is actually up to
58 characters long.

(2) When the setting value and message data do not match

When the message data contents (such as index No., switch No. and message character string)
overflows from the settings in the setting area, the data that overflowed is ignored.

- 38 -
 4. PLC MESSAGE DEVELOPMENT
4.3 Converting Data into GX Developer Format

4.3 Converting Data into GX Developer Format

Convert the message data, which was described using a text editor or like, into GX Developer data
in the following method. Use "GX Converter (data conversion software package)" for conversion.
GX Converter can be started from the GX Developer menu.

4.3.1 Starting GX Converter and specifying the file to be converted

Perform the following operation from GX Developer to start GX Converter (read).

[Project] → [Import file] → [Import from TEXT ,CSV format file]

On the following screen, specify the file to be converted (M1TEST.TXT) and click [OK].

4.3.2 Conversion format setting

Set the conversion format on the following data conversion wizard screen.

(1) Data conversion wizard 1/4

Choose [Original Data Type]-[Fixed Width] and [Data Type]-[List], and click [Next>].

- 39 -
 4. PLC MESSAGE DEVELOPMENT
4.3 Converting Data into GX Developer Format

(2) Data conversion wizard 2/4

Just click [Next>].

(3) Data conversion wizard 3/4

Choose to highlight the Instruction column part in the [Data Preview] list and choose [Column
Data Format]-[Instruction ,Statement ,Note]. Click [Next>].

(4) Data conversion wizard 4/4

Set the program name used on GX Developer in [Data name] and a data annotation in [Title],
and click [Finish]. Data conversion is completed when the Completed dialog appears. Click
[OK].

- 40 -
 4. PLC MESSAGE DEVELOPMENT
4.4 Entering/Editing Data Using GX Developer

4.4 Entering/Editing Data Using GX Developer

The message data in GX Developer are handled as the "integrated type interlinear statements" of a
PLC program. "Integrated type interlinear statements" are interlinear comments provided to assist
the understanding of the PLC program, and those transferred to the controller together with the PLC
program are called the "integrated type".
"Interlinear statements" can be displayed and edited using [Ladder] or [Instruction list].

4.4.1 Interlinear statement display using circuit display

(1) Display of project data list

Perform the following operation to display the "Project data list" window and double-click the file
name to display the edit screen. First, the normal ladder screen appears.

[View] → [Project data list], then double-click [File name you want to display].
(2) Display of message data

Perform the following operation to display the message data that are integrated type interlinear
statements.

[View] → [Statement]

- 41 -
 4. PLC MESSAGE DEVELOPMENT
4.4 Entering/Editing Data Using GX Developer

4.4.2 Interlinear statement display using list display

(1) Display of project data list

Perform the following operation to display the "Project data list" window and double-click the file
name to display the edit screen. First, the normal ladder screen appears.

[View] → [Project data list], then double-click [File name you want to display].
(2) Display of list data

Perform the following operation to display the list data. The list display also shows the message
data that are integrated type interlinear statements.

[View] → [Instruction list]

Perform the following operation to return to the circuit display.

[View] → [Ladder]

- 42 -
 4. PLC MESSAGE DEVELOPMENT
4.4 Entering/Editing Data Using GX Developer

4.4.3 Editing of integrated type interlinear statements

(1) Circuit display

On the circuit display screen that shows the integrated type interlinear statements, double-
clicking the interlinear statement you want to edit displays the following dialog. Perform editing
operation on the dialog and click [OK] or press [Enter].

(2) List display

On the list display screen, double-clicking the interlinear statement you want to edit displays the
following dialog. Perform editing operation on the dialog and click [OK] or press [Enter].

(3) Entering new message data

• Displaying new edit screen

Perform the following operation to display the [New] dialog, and set the [Data name] and
[Title]. After setting, click [OK].

[Project] → [Edit Data] → [New]

• Changing to list display mode

Perform the following operation to display the list data.

[View] → [Instruction list]

• Entering message data

Press "Enter" at the "END" line, and input the data in the same manner as 4.4.3 (2) above.
Then, press "Enter" on the next line, and input the message data.

- 43 -
 4. PLC MESSAGE DEVELOPMENT
4.5 Writing to the CNC Controller

4.5 Writing to the CNC Controller

The following shows the method of transferring a message from the GX Developer to the CNC
controller. The transfer method is the same as the ladder code transfer method. Ladder codes and
message data are distinguished by their file names only.
Perform the following operation to display the [Write to PLC] screen, and choose the file to be
written.

[Online] → [Write to PLC]

The following example transfers a message first language file "M1TEST.WPG".

4.6 Reading and Verifying from the CNC Controller

The following shows the method of reading and verifying a message from the CNC controller to the
GX Developer. The method of reading and verifying is the same as that of ladder codes. Ladder
codes and message data are distinguished by their file names only.

4.6.1 Menu selection/screen operation

Refer to the following sections for operation methods.

For read : "3.7 Reading the PLC Program from the CNC Controller"
For verification : "3.8 Verifying the PLC Programs"

- 44 -
 4. PLC MESSAGE DEVELOPMENT
4.6 Reading and Verifying from the CNC Controller

4.6.2 Message read format

The message description format was shown in "4.2.1 Description format", but there are no special
rules concerning provision of descriptions in the setting area or the order of message description in
the message area. For that reason, the description format may differ between transfer and reading
of the message data.
The following shows the format during reading as the "Standard description format".

Standard description format of message data

Alarm message setting …(1)

Operator message setting
PLC switch setting
Comment message setting
Alarm messages …(2)
Operator messages …(3)
PLC switches …(4)
Comment messages …(5)
NOPLF
END

(1) Setting area

The settings are described in order of alarm, operator, PLC switch and comment.
The maximum value is described if the setting is abbreviated.

(2) Alarm messages

Each message data is described in order of the index Nos.

(3) Operator messages

The same as the alarm messages.

(4) PLC switches

Each message data is described in order of the switch Nos.

(5) Comment messages

These messages are described in the same order as described before transfer.

(6) Others
• Spaces and tabs are not included before and after the comma(,) separating the message data
factors.
• The message character string is handled the same as normal data even when blank.
• The NOPLF code between messages is described to the position to which the message data
following the NOPLF code during transfer moved.

- 45 -
 5. DEVICE COMMENT CREATION
5.1 Development Procedure

5. DEVICE COMMENT CREATION

There are no MELDAS-specific operations for device comments. Therefore, refer to the Operating
Manual for the development method. This section describes the device comment development
procedure outline and the development method using a general-purpose tool.

5.1 Development Procedure

The following two methods can be used as general development procedures of message data.

(1) Indirect entry

In this method, device comments are converted into GX Developer data using a general text
editor or spreadsheet tool and data conversion package. Use this method when you want to
divert the device comments of the old model or when a device comment volume is large and
you want to control them with a commercially available tool, for example.

IBM PC/AT compatible personal computer

Creation
Spreadsheet tool
Text editor
M600, M60
device
comment
zzzz.TXT Conversion
GX Converter CNC controller
M600, M60
device
comment
zzzz.W CD
Editing
GX Developer

RS232C

M600, M60
ladder
zzzz. W PG

(2) Direct entry

In this method, device comments are entered directly from GX Developer. Use this method
when a device comment volume is small or when addition or correction is to be made, for
example.
There are the following three methods for direct entry from GX Developer. Refer to the
Operating Manual for details.

• Creating comments on the device comment edit screen

• Creating device comments after circuit creation during ladder circuit creation
• Making addition/correction to device comments in the created ladder circuit

- 46 -
 5. DEVICE COMMENT CREATION
5.2 Description Method for Indirect Entry

5.2 Description Method for Indirect Entry

The following explains the description method for creating device comments using a spreadsheet
tool or like. The following example describes device comments using a spreadsheet tool.

Describe device, equipment

Safety unit run name and comment on the
Safety cover close same line.

Operation ready complete

Oil pressure motor
Parts A ready complete

Device- Equipment Comment-

only name-on ly only
column column column

Column data format Explanation

Device (1) Describe a device.
• Conversion cannot be made if a device has not been described.
Always describe a device.
(2) A device is a required item. Describe it in one-byte code.
Equipment name (1) Describe an equipment name.
• It is not registered if the device part on the same row is blank or the
device is illegal.
(2) You can describe an equipment name of up to 8 characters.
Comment (1) Describe a comment.
• It is not registered if the device part on the same row is blank or the
device is illegal.
(2) You can describe a comment of up to 32 characters.

[Note] Describe data in any of the following combinations.

(1) Device, equipment name, comment
(2) Device, comment
(3) Device, equipment name

Save the above data in the CSV format. The following example shows the above data saved in the
CSV format.

X0, SAFETY, Safety unit run

X1, COVER, Safety cover close
X2, READY, Operation ready complete
X3, OIL-M, Oil pressure motor
X4, PARTS-A, Parts A ready complete

- 47 -
 5. DEVICE COMMENT CREATION
5.3 Converting Device Comments

5.3 Converting Device Comments

Convert the comment data (CSV format), which was created using a spreadsheet tool or like, into
GX Developer data in the following method. Use "GX Converter (data conversion software
package)" for conversion. GX Converter can be started from the GX Developer menu.

5.3.1 Starting GX Converter and specifying the file to be converted

Perform the following operation from GX Developer to start GX Converter (read).

[Project] → [Import file] → [Import from TEXT ,CSV format file]

On the following screen, specify the file to be converted (cmnt_all.txt) and click [OK].

5.3.2 Conversion format setting

Set the conversion format on the following data conversion wizard screen.

(1) Data conversion wizard 1/4

Choose [Original Data Type]-[Delimited] and [Data Type]-[Comment], and click [Next>].

- 48 -
 5. DEVICE COMMENT CREATION
5.3 Converting Device Comments

(2) Data conversion wizard 2/4

Choose [Delimiters]-[Tab] and click [Next>].

(3) Data conversion wizard 3/4

Make sure that the column parts in the [Data Preview] list are in order of [Device Number],
[Label] and [Comment], and click [Next>].

(4) Data conversion wizard 4/4

Choose [Data type]-[Common comment] or [Program comment], set the comment file name
used on GX Developer in [Data name] and a comment annotation in [Title], and click [Finish].

- 49 -
 5. DEVICE COMMENT CREATION
5.3 Converting Device Comments

(5) Completion

The setting is complete when the following dialog appears. Click [OK].

(6) Error status

If an error occurred during conversion, its status and the line where it occurred are displayed.

- 50 -
 6. RELATIONSHIPS BETWEEN GX DEVELOPER AND ONBOARD FUNCTIONS
6.1 Function Differences

6. RELATIONSHIPS BETWEEN GX DEVELOPER AND ONBOARD

FUNCTIONS
The CNC controller has onboard functions as the PLC development environment that does not use
GX Developer. The onboard functions have monitoring and editing functions for ladder program
testing and adjustment.
This chapter explains the items related to GX Developer and onboard functions.

6.1 Function Differences

The onboard functions do not have the following functions among the main functions as the PLC
development environment.

• Function to create a new ladder program

• All PLC message-related functions
• All device comment-related functions

6.2 Specification Differences

There are the following differences in specifications between GX Developer and onboard functions.

(1) Restriction specifications related to circuit display/editing

The restriction specifications related to circuit display/editing differ between GX Developer and
onboard functions. Since the restriction specifications of the onboard functions are narrower
than those of GX Developer, care should be taken when creating a circuit on the GX Developer
side.

(a) Limits according to circuit handling specifications

Onboard GX Developer
Number of 8 contacts, 1 coil 11 contacts, 1 coil
Display contacts
specifications Number of 9 lines Depending on window
of single screen lines size and screen reduction
ratio
Restriction specifications of 18 lines (return count: 0) 24 lines of 200 or more
single circuit (Note 1) series contacts

(Note 1) The relationships between the return count and the maximum value of the vertical
width of the circuit that can be created at that time are as follows.
Return count (times) 0 1 2 3 4 5 6 7 8
Vertical width of circuit (lines) 18 11 7 5 4 3 3 2 2
Excess over the above will result in "LADDER ERROR".

(b) Handling a circuit exceeding the 18-line restriction specifications

If the circuit created on the GX Developer side exceeds the circuit restriction specifications
of the onboard functions, the following message is displayed.
Operation Message Handling
When "read" or "monitor" function "DISPLAY OVER FLOW" Circuit is not displayed.
is used to display circuit (Only bus is displayed)
When "write", "insertion", "NOT WRITE" Editing operation is
"deletion" or "conversion" function inhibited.
is selected

- 51 -
 6. RELATIONSHIPS BETWEEN GX DEVELOPER AND ONBOARD FUNCTIONS
6.2 Specification Differences

(2) Step count calculation specifications

The step count specifications in the individual instructions of the MELSEC and MELDAS differ
in some instructions. Therefore, steps may be different when the same circuit is displayed by
GX Developer and onboard functions.
This will give rise to a problem especially when the circuit diagram printed from GX Developer
is used for maintenance with the onboard functions. To resolve this problem, a tool (PCNV6LM)
to print a circuit diagram in the MELDAS step specifications is available.

(3) NC instructions which cannot be used with GX Developer

MELDAS original specification instructions that cannot be handled with GX Developer are used
after being replaced with alternate instructions which can be handled by GX Developer. The
specifications when these instructions are displayed with the onboard are shown below.

Table of alternate instruction correspondence

Instruction
Classification symbol
Onboard display GX Developer display

D
Bit DEFR ⎯[ DEFR D ]⎯
⎯ ↑ ⎯
Average value AVE ⎯[ AVE S D n ] ⎯[ S.AVE S D n ]
Carry flag set STC ⎯[ STC ] ⎯[ S.STC ]
Carry flag reset CLC ⎯[ CLC ] ⎯[ S.CLC ]
ATC ATC ⎯[ ATC Kn Rn Rm Mm ] ⎯[ S.ATC Kn Rn Rm Mm ]
ROT ROT ⎯[ ROT Kn Rn Rm Mm ] ⎯[ S.ROT Kn Rn Rm Mm ]
TSRH TSRH ⎯[ TSRH Rm Rn Mn ] ⎯[ S.TSRH Rm Rn Mn ]
DDBA DDBA ⎯[ DDBA Rn/Dn ] ⎯[ S. DDBA Rn/Dn]
DDBS DDBS ⎯[ DDBS Rn ] ⎯[ S. DDBS Rn ]
CAL1 CAL1 ⎯[ CAL1 Pn ] ⎯[ S. CAL1 Pn ]
LDBIT [ < = S1 n ]⎯ [ < = S1 n ]⎯
ANDBIT ⎯[ < = S1 n ]⎯ ⎯[ < = S1 n ]⎯
ORBIT [ < = S1 n ] [ < = S1 n ]
BIT
LDBII [< > S1 n ]⎯ [ < > S1 n ]⎯
ANDBII ⎯[ < > S1 n ]⎯ ⎯[ < > S1 n ]⎯
ORBII [ < > S1 n ] [ < > S1 n ]

(4) Circuit representation specifications

The circuit of the END instruction is not displayed by the onboard functions.

- 52 -
 7. PROCEDURE FOR WRITING PLC PROGRAMS, ETC. TO ROM
7.1 Data That Can Be Written to ROM

7. PROCEDURE FOR WRITING PLC PROGRAMS, ETC. TO ROM

This chapter explains the procedure for ROM writing for the ladder programs and PLC-related data
that have been developed. For the M60/60S series, this operation is not required since data is
written to the ROM as soon as it is written from GX Developer.

7.1 Data That Can Be Written to ROM

The following four data can be written to ROM. Note that multiple data of the same type cannot be
written to ROM.

Related data
Remarks
classification
1 PLC program (ladder) PLC program code
2 PLC program comment Comment data for GPPQ/W
3 Message 1st language 1st language data of message data such as alarm
messages, operator messages, and PLC switches
4 Message 2nd language Same as above
(2nd language data)

7.2 ROM Writing Operation Procedure

GX Developer does not have the ROM writing function for ladder programs, etc. from GX Developer
by remote operation. Perform ROM writing operation from the I/O screen of the CNC controller.
By specifying the transfer source information (internal RAM) and transfer destination information (F-
ROM) on the I/O screen and starting transfer, the ladder program, etc. stored in the RAM are written
to the ROM. The contents of ROM is erased automatically before write is performed.
The following shows the I/O screen example of the M600M. (Write from internal RAM to external
cassette F-ROM)

- 53 -
 7. PROCEDURE FOR ROMING PLC PROGRAMS, ETC.
7.2 ROM Writing Operation Procedure

The following gives the common operations and individual operations of the M600M and M600L
operation procedures. For details of the I/O screen, refer to the instruction manual of that model.

(1) Common operation

Set the [Device], [Directory] and [File] of [A:Device] and [B:Device] respectively. Selecting any
of the following functions on the menu keys starts the corresponding operation.
(a) [Trnsfr A->B]
Data is transferred from Device A to Device B. If Device B is an F-ROM, the F-ROM
contents is erased and the data of Device A is written to it. Devices A, B may be other than
the internal RAM or F-ROM (storage such as the hard disk).
(b) [Compare A:B]
Data of Device A and Device B are compared. Devices A, B may be other than the internal
RAM or F-ROM.
(c) [Erase A]
The data of Device A is erased. Note that it is not erased when the internal RAM is
specified.
(d) [Erase B]
The data of Device B is erased. Note that it is not erased when the internal RAM is
specified.

(2) Individual operations (How to set the [Device], [Directory] and [File])

(a) M600M
(i) Device selection
Specify [Memory] from the menu key.
(ii) Directory designation
Type the storage region type in the setting box.
Internal RAM : "/MEM"
Internal F-ROM : "/FRA"
External cassette F-ROM: "/FRB"
(iii) File name designation
Type the file name in the setting box.
Fixed to "LAD.DAT"

(b) M600L
(i) Device selection
Specify [Memory] from the menu key.
(ii) Directory designation
Specify [PLC prog] from the menu key.
(iii) File name designation
Specify the storage region type from the menu key.
[Inside RAM], [Inside F-ROM] or [Outside F-ROM]

- 54 -
 8. LIST OF ERROR STATES

8. LIST OF ERROR STATES

If an error has occurred in GX Developer, the following dialog appears. The error message and error
status are displayed in the dialog.

(1) Error message

(2) Error status

[Note] When an error occurred at GX Developer On-line function, the error message may not
explain exactly the state in the CNC controller side.
Always refer to the error list.

The following table indicates the causes and remedies of the errors that can occur during online
operation with the CNC controller. For other errors, refer to the GX Developer Operating Manual.

[Note] Read "PLC" in the messages as "CNC controller".

Status Message Cause Remedy

2056 The executed function is not The GX Developer version and This occurs if the GX
supported. Please check the NC do not match. Developer version is 7.10L to
manual and other 7.14Q. Upgrade the version to
documentation. 7.17T or above.
The version upgrade can be
downloaded from MELFANS
web.
4002 The executed function is not An operation not supported by Check the operation
supported. Please check the the specifications was procedures.
manual and other attempted.
documentation.
4010 Cannot write because the PLC The PLC of the NC is running. After stopping the PLC of the
is executing a RUN command. NC, start execution again.
Stop the PLC, then execute
again.
4021 The applicable drive is not The specified target memory Change the target memory.
ready. Check the applicable does not exist or is not in a
drive, then execute again. usable status.
4029 Insufficient file capacity. An attempt was made to write Examine the file structure so
Execute again after deleting a file that exceeds the storage that the data falls within the
unnecessary files. capacity. limited capacity.
402b The file cannot be accessed. An attempt was made to write After deleting the same type of
Carry out formatting, then the same type of file. file from the NC side, start
execute again. execution again.
4031 The specified device No. The access request given is Check the number range of
exceeds the permissible range. outside the accessible device each device.
Specify a device No. that is range.
within the range set in the
parameter.
4052 The file is write protected. The specified target memory is Specify "internal RAM" as the
Change the file attributes to a write-disabled device target memory.
enable writing to the file. (F-ROM).
4053 Writing to the flash ROM failed. An error occurred in the The hardware may be faulty or
process to erase or to write deteriorated. Contact a
data into the flash ROM. Mitsubishi Sales Office.
(Only MELDAS 60/60S Series)

- 55 -
 8. LIST OF ERROR STATES

Status Message Cause Remedy

4070 The program before correction A ladder instruction outside the Perform verification to identify
differs from the registered specification is included. the instruction that is the cause
program. of the problem.
4080 Incorrect abnormal. When executing "Read from The sequence program or
PLC" or "Verify PLC" function: message data in the CNC
Data not included in the controller may be damaged.
specifications was found in Delete the corresponding file
the designated file. and start again, or initialize the
PLC data storage area. If the
problem cannot be resolved,
contact the Mitsubishi System
Department.
When executing "Write to Edit the sequence program in
PLC": the list mode to delete END
Multiple END instructions instructions except only one at
were found in the designated the last line.
sequence program file.
8201 Cannot communicate with the The serial communication Check the serial port setting
PLC. Execute again after cable is faulty. and cable connection.
checking the connections with • Not connected
the PLC. • DTR signal off
840b Cannot communicate with PLC There is no response from the Check the following.
for one of the following NC. • CNC side status
reasons. • The CNC has not started • Cable connection
Communications timeout properly. • Bit selection:
Cable error • The connection channel of GPP communication valid
Specified baud rate not the CNC side serial port is • Set the Ethernet address
supported for connected PLC different.
Monitor condition set status is • The serial cable outside the
read by device specifications is used for
The project PLC and the signal connection.
connected PLC are different. • An incorrect Ethernet
address is set on the NC
side

- 56 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

APPENDIX 1. OPERATION METHODS USING GPPQ

This section explains the GPPQ proper operation method of the function explanation and the PLC
program development procedure when "MELSEC QnA Series GPP Function Software Package
(GPPQ)" is used as development tool.

Appendix 1.1 GPPQ Function Outline and Functions Supported by the M600,
M60/60S Series
The GPPQ functions explained here are those supported by the M600, M60/60S Series in the "off-
line functions" operated with the GPPQ independently and "on-line functions" carried out connected
to the CNC controller.
Refer to the enclosed Operating Manual (off-line section and on-line section) for function details.

Appendix 1.1.1 Function support conditions (general section)

The following shows a list of GPPQ outline functions supported by the M600, M60/60S Series.
A mark indicates functions that can be used by the M600, M60/60S Series. An r mark indicates
that the function cannot be used because it is related to "MELSEC Series" characteristic functions.
The function details during on-line are described in the next section.

List of general section functions (1) : Possible, r : Support not possible/not determined
Mode Function Support Remarks
Initialization New creation
File new read
PLC new read → Refer to the List of on-line section functions
File quit
PLC type change r Q4ACPU only
Option Environment setting
Display and operation option
Startup setting
Circuit Write → Refer to the List of on-line section functions
Read → Refer to the List of on-line section functions
Monitor → Refer to the List of on-line section functions
Test → Refer to the List of on-line section functions
Debug → Refer to the List of on-line section functions
File access → Refer to the List of on-line section functions
PLC access → Refer to the List of on-line section functions
Program search → Refer to the List of on-line section functions
Comment display → Refer to the List of on-line section functions
Program edit → Refer to the List of on-line section functions
Monitor and test → Refer to the List of on-line section functions
Window changeover → Refer to the List of on-line section functions
Option → Refer to the List of on-line section functions
List Write
Read
File access
PLC access → Refer to the List of on-line section functions
Program search
Comment display
Program edit
Window changeover
Option

- 57 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of general section functions (2) : Possible, r : Support not possible/not determined
Mode Function Support Remarks
Parameter PLC name setting r
PLC system setting r
PLC file setting r
Device setting r
PLC RAS setting r
I/O assignment r
MELSECNET (II,10)/Ethernet setting r
MELSECNET/MINI setting r
MELSECNET/J setting r
Miscellaneous setting r
Duplex PLC setting r
SFC r
X/Y assignment confirmation r
File access r
PLC access r
Parameter search r
Parameter edit r
Miscellaneous setting r
Window changeover r
Option r
Device Device value input → Refer to the List of on-line section functions
Device initialization → Refer to the List of on-line section functions
Buffer memory simulation → Refer to the List of on-line section functions
File access
PLC access → Refer to the List of on-line section functions
Device search
Device display
Device edit → Refer to the List of on-line section functions
Window changeover
Option
On-line Drive name selection → Refer to the List of on-line section functions
File name selection → Refer to the List of on-line section functions
File access → Refer to the List of on-line section functions
PLC access → Refer to the List of on-line section functions
Data search → Refer to the List of on-line section functions
Trace → Refer to the List of on-line section functions
Trace device edit → Refer to the List of on-line section functions
Device test → Refer to the List of on-line section functions
Window changeover → Refer to the List of on-line section functions
PLC Diagnosis target selection r
diagnosis Current error display r
Fault history display r
CPU message r
Unit detailed display r
File access r
PLC access → Refer to the List of on-line section functions
Data search r
Error display r
Network monitor and test r
Window changeover r
Option r

- 58 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of general section functions (3) : Possible, r : Support not possible/not determined
Mode Function Support Remarks
Text Device comment
creation Pointer statement
Interlinear statement
Note
Print statement
File access
PLC access → Refer to the List of on-line section functions
Comment search
Comment edit
Window changeover
Option
Printer Printer data setting
Print execution
Printer setting
Paper size change
Edit
Window changeover
Option
File Machine name/File name selection
maintenance File access
PLC access → Refer to the List of on-line section functions
File search
Display
IC memory card r
Window changeover
Option
Program Label name definition
generation File access
Program generation
Label display
Display
Label edit
Window changeover
Option
SFC r
Quit

- 59 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

Appendix 1.1.2 Function support conditions (on-line section)

The following shows a list of GPPQ on-line functions supported by the M600, M60/60S Series.
A mark indicates functions that can currently be used by the M600, M60/60S Series. An r mark
indicates that the function cannot be used because it is related to "MELSEC Series" characteristic
functions.

List of on-line section functions (1) : Possible, r : Support not possible/not determined
Mode Function Menu Detailed function Support Remarks
6.2 Circuit write 6.2.1 Write during run r
6.3 Circuit read 6.3.1 Step No. read
6.3.2 Instruction read
6.3.3 Device read
6.3.4 Contact and coil designation
read
6.3.5 Statement and note
designation read
6.3.6 Last circuit designation read
6.4 Monitor 6.4.1 Monitor screen common
display Monitor destination CPU name
No. of Monitor program steps
Monitor program name
Scan time r
Monitor interval
CPU operation status
Monitor destination
Flicker during communication
6.4.2 Circuit monitor
Bit device monitor display
Word device monitor display
Digit designation monitor display
Timer/counter monitor display
Double word monitor display
Index modification monitor display
Circuit
mode Monitor step changeover
Changeover to next circuit block
Changeover to previous circuit block
Monitor stop
Monitor column numeric value/No. of
display levels changeover
6.4.3 Device registration monitor
Bit device monitor display
Word device monitor display
Digit designation monitor display
Timer/counter monitor display
Double word monitor display
Index modification monitor display
16-bit integer designation
32-bit integer designation
Real number designation r
Character designation r
Registration device erase
6.4.4 ON/OFF cause automatic
search
6.5 Test 6.5.1 Monitor trigger stop
Stop at bit device rising edge r
Stop at bit device falling edge r
Stop at word device designation
value r
Monitor restart r
- 60 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of on-line section functions (2) : Possible, r : Support not possible/not determined
Mode Function Menu Detailed function Support Remarks
6.5 Test 6.5.2 Forced ON/OFF
Forced ON r
Forced OFF r
6.5.3 Current value change
16-bit change r
32-bit change r
6.5.4 Setting value change
Timer r
Counter r
6.6 Debug 6.6.1 Step execution r
6.6.2 Partial execution r
6.7 File menu 6.7.1 Read
6.7.2 Write
6.7.3 Compare
6.8 PLC menu 6.8.1 Read
6.8.2 Write
Parameter r
Sequence program
Entire range
Range designation r
Device comment
Device default value r
Simulation data r
File register r
Device memory r
Entire range r
Range designation r
6.8.3 Compare
Circuit
mode 6.8.4 New edit target read r
6.8.5 List of files
File name
Classification
Size
Date
Time
Header statement
No. of files
Continuous max. open capacity
Entire open capacity
6.8.6 Connection designation
Peripheral side interface
PLC side interface r Fixed
Target CPU r Fixed
Target memory r Fixed
6.8.7 Remote operation CPU status display
RUN
STOP
PAUSE r
STEP-RUN r
Latch clear r
Reset r
Operation during RUN, STEP-RUN r
Execution destination designation r
Execution unit designation r
6.8.8 Write option For write
r during run

- 61 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of on-line section functions (3) : Possible, r : Support not possible/not determined
Mode Function Menu Detailed function Support Remarks
6.9 Display 6.9.1 Circuit display changeover
menu Device name display
Comment display
Statement display
Display with note
6.10 Monitor 6.10.1 Device batch monitor
and test Bit device monitor display
menu Word device monitor display
Bit and word monitor
Bit multipoint monitor
Word multipoint monitor
Timer/counter mulipoint monitor
Target device change
Decimal/hexadecimal display
changeover
Integer/real number display
changeover
0 → F/F → 0 display changeover
Forced ON
Forced OFF
6.10.2 Multiple device batch monitor
Bit device monitor display
Word device monitor display
Decimal/hexadecimal display
changeover
Integer/real number display
changeover
Registration device erase
Forced ON
Forced OFF
Circuit
6.10.3 ON/OFF cause automatic
mode
search
6.10.4 Scan time measure r
6.10.5 Device registration monitor Bit device monitor display
Word device monitor display
Digit designation monitor display
Timer/counter monitor display
Double word monitor display
Index modification monitor display
16-bit integer designation
32-bit integer designation
Real number designation
Character designation
Registration device erase
6.10.6 Monitor and test menu
Constant monitoring r
Word device condition
Bit device condition
Step No. r
6.10.7 Monitor stop condition setting
Monitoring does not stop
Word device condition
Bit device condition
Operation status r
6.10.8 Monitor data
registration/application
6.10.9 Device test
Forced ON
Forced OFF
Forced ON/OFF reverse
Current value change

- 62 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of on-line section functions (4) : Possible, r : Support not possible/not determined
Mode Function Menu Detailed function Support Remarks
6.10 Monitor 6.10.10 Sampling/monitoring trace U
and test 6.10.11 Step execution U
menu 6.10.12 Partial execution U
6.10.13 Skip execution U
6.10.14 Simulation U
Circuit 6.10.15 Monitor column numeric
mode value display changeover Numeric value display format
No. of display level
6.10.16 Program execution status U
monitor
6.11 Option 6.11.1 Monitor destination setting U
menu
8.2 PLC menu
Para-
meter Refer to 6.8
mode →
PLC menu

9.2 Device U
value input
9.3 Default
value U
range
setting
Device
mode 9.4 Buffer
memory U
simulation

9.5 PLC menu → Refer to 6.8

PLC menu
9.6 Edit menu 9.6.1 Simulation range U
10.2 Drive Internal RAM Fixed
name IC memory card Fixed
selection U
10.3 File
selection
10.4 File menu 10.4.1 Read
10.4.2 Write
10.4.3 Compare
10.4.4 New edit target read
10.4.5 List of files r
10.4.6 Delete
10.4.7 File quit
10.5 PLC 10.5.1 Read
menu 10.5.2 Write
Parameter U
On- Sequence program
line Entire range
mode
Range designation U
Device comment
Device default value U
Simulation data U
File register U
Device memory U
Entire range U
Range designation U
10.5.3 Compare
10.5.4 New edit target read
10.5.5 List of files
File name
Classification
Size
Date
Time
Header statement
No. of files
Continuous max. open capacity
Entire open capacity
10.5.6 Connection designation
Peripheral side interface
PLC side interface U Fixed
Target CPU U Fixed
Target memory U Fixed
- 63 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.1 GPPQ Function Outline and Functions Supported by the M600, M60/60S Series

List of on-line section functions (5) : Possible, r : Support not possible/not determined
Mode Function Menu Detailed function Support Remarks
10.5 PLC 10.5.7 Remote operation CPU status display
menu RUN
STOP
PAUSE U
STEP-RUN U
Latch clear U
Reset U
Operation during RUN, STEP-RUN U
Execution destination designation U
Execution unit designation U
10.5.8 Write option U For write
during run
10.5.9 Key word registration U
10.5.10 Device memory operation U
10.5.11 PLC memory batch U
operation
On- 10.5.12 Delete
line 10.5.13 Header statement creation U
mode
10.6 Search 10.6.1 Head/end search U
menu 10.6.2 File search U
10.6.3 Frequency search U
10.6.4 Time search U
10.6.5 Data search U
10.7 Trace 10.7.1 Sampling trace U
menu 10.7.2 Monitoring trance U
10.7.3 Status latch U
10.7.4 Program trace U
10.8 Edit menu 10.8.1 Cut/copy/paste U
10.9 Test menu 10.9.1 Device test U
Forced ON
Forced OFF
Forced ON/OFF reverse
Current value change
10.10 Window 10.10.1 Display window change
menu
11.2 Diagnosis
target U
selection
11.3 Current
error U
display
11.4 Fault
history U
display
11.5 CPU U
message
11.6 Unit
PLC detailed U
diagno- display
sis 11.7 File menu U
mode
11.8 PLC U
menu
11.9 Search U
menu
11.10 Display U
menu
11.11 Network U
menu
11.12 Window U
menu
11.13 Option U
menu

File 13.2 PLC Refer to 6.8

menu → PLC menu
mainte-
nance 13.3 IC card
mode U
menu

- 64 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.2 Ladder Transfer to the CNC Controller

Appendix 1.2 Ladder Transfer to the CNC Controller

The method of transferring a ladder to the CNC controller with the GPPQ (especially the restrictions
and M600, M60/60S characteristic operations) is explained below.

Appendix 1.2.1 Menu selection

The screen is selected from the menu using the following GPPQ basic operation.

PLC menu PLC write

Mode screen Alt ( GRPH ) 2 2
window screen
Menu PC Write

Appendix 1.2.2 Screen operation

The required options are selected and executed on the following screen.

[Write to PLC]
Interface RS232C <---> QnACPU
Target PLC Network : 0 Station : FF PLC Type : Q4A
Target Mem Internal RAM Title [ ]
1. File 1. File Name [ ] Title [ ]
2. Tgt 1. [ * ] Parameter
2. [ * ] Seq/SFC Prog 1. ( * ) Whole Range
2. ( ) Step Range [ ]–[ ]
3. [ ] Device Comment 3. ( ) Step Range P[ ] – [ ]
4. [ ] Dev Init Value 4. ( ) Block Range [ ]–[ ]
5. [ ] Simulation Data
6. [ ] File Register 1. ( * ) Whole Range
2. ( ) Specify ZR[ ]–[ ]
2. Device Mem 1. [ ] Internal 1. ( * ) Whole Range
2. ( ) Specify Detail Range

Execute(Y) Cancel(N)

Ctrl+L : filelist Ctrl+D : directo Space : sele Esc : close

[Restrictions]
The following options of [2. Tgt] under [1. File] can be selected.
[1. Parameter]
[2. Seq/SFC Prog] and [1. Whole Range]
[3. Device Comment]
Note that nothing will be transferred even if [1. Parameter] is selected.

- 65 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.2 Ladder Transfer to the CNC Controller

Appendix 1.2.3 Operation during a transfer error

The ladder data is converted to the ladder machine code characteristic to the CNC controller
simultaneously with the ladder transfer from the GPPQ to the CNC controller. A conversion error will
occur if devices or instruction formats are used that are not supported by the M600, M60/60S Series.
During a conversion error, the following message appears at the bottom of the GPPQ screen after
the M600 ladder machine code is converted to an "NOP code" and transferred to the last step.

Cannot communicate with PLC. Error No.=4070

The following warning statement appears in the header statement item when the file having the
conversion error is displayed with the PLC file list function.

[List]
:
File Type Size Data Time Title
PLCTEST QnA Seq 12345 97-11-18 10:34 [∗∗WARNING: Checksum ERROR!!∗∗]
:

If an attempt is made to run the PLC in this status, the following alarm message will appear on the
NC side, and the PLC will not run.

SY0002 User ladder code error

Appendix 1.2.4 Error step No. confirmation method

The error step can be confirmed using the PLC compare function. The mismatched contents appear
as in the following example when the PLC comparison is executed. Refer to "Appendix 1.4 Ladder
comparison with the CNC controller" for details.
[Sequence Program Diff List]

[Sequence Program Diff List]

<Memory> <PLC>
Step Ins I/O Step Ins I/O
15 AND= R4918 15 NOP
K106
18 + R4916 16 NOP
K10000
D87
22 END 17 NOP
No Data exists. 18 + R4916
K10000
D87
No Data exists. 22 END
PgDn : Next page Esc: Close

- 66 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
APPENDIX 1.3 Ladder Read from the CNC Controller

Appendix 1.3 Ladder Read from the CNC Controller

The method of reading a ladder from the CNC controller to the GPPQ is explained below.

Appendix 1.3.1 Menu selection

The screen is selected from the menu using the following GPPQ basic operation.

PLC menu PLC read

Mode screen Alt ( GRPH ) 2 1
window screen
Menu PC Read

Appendix 1.3.2 Screen operation

The file names are designated and executed on the following screen.
File name designation method
Input the file name stored in the read target memory.
Display the read target memory list screen by pressing Ctrl + D .
Display the file list screen by pressing Ctrl + L .
After selecting the file using ↑ and ↓ , display the file name selected in the file name
designation column by pressing Enter .

[Read from PLC]

Interface RS232C <---> QnACPU
Target PLC Network : 0 Station : FF PC Type : Q4A
Target Mem Internal RAM Title [ ]
1. File 1. File Name [ ] Title [ ]
2. Tgt 1. [ * ] Parameter
2. [ * ] Seq/SFC Prog 1. ( * ) Whole Range
2. ( ) Step Range [ ]–[ ]
3. [ ] Device Comment 3. ( ) Step Range P[ ] – [ ]
4. [ ] Dev Init Value 4. ( ) Block Range [ ]–[ ]
5. [ ] Simulation Data
6. [ ] File Register 1. ( * ) Whole Range
2. ( ) Specify ZR[ ]–[ ]
2. Device Mem 1. [ ] Internal 1. ( * ) Whole Range
2. ( ) Specify Detail Range

Execute(Y) Cancel(N)

Ctrl+L : filelist Ctrl+D : directo Space : sele Esc : close

[Restrictions]
The following options of [2. Tgt] under [1. File] can be selected.
[2. Seq/SFC Prog] and [1. Whole Range]
[3. Device Comment]

- 67 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.4 Ladder Comparison with CNC Controller

Appendix 1.4 Ladder Comparison with CNC Controller

The method of comparing the ladders between the CNC controller and GPPQ is explained below.

Appendix 1.4.1 Menu selection

The screen is selected from the menu using the following GPPQ basic operation.

PLC menu PLC compare

Mode screen Alt ( GRPH ) 2 3
window screen
Menu PC Compare

Appendix 1.4.2 Screen operation

The file names are designated and executed on the following screen. The options that can be
selected are the same as those of the ladder read.
File name designation method
Input the file name stored in the read target memory.
Display the read target memory list screen by pressing Ctrl + D .
Display the file list screen by pressing Ctrl + L .
After selecting the file using ↑ and ↓ , display the file name selected in the file name
designation column by pressing Enter .

[PLC compare]
Interface RS232C <---> QnACPU
Target PLC Network : 0 Station : FF PC Type : Q4A
Target Mem Internal RAM Title [ ]
1. File 1. File Name [ ] Title [ ]
2. Tgt 1. [ * ] Parameter
:
:
:

Execute(Y) Cancel(N)

Ctrl+L : filelist Ctrl+D : directo Space : sele Esc : close

When the comparison contents do not match, a screen with the mismatched contents appears.

[Sequence Program Diff List]

<Memory> <PLC>
Step Ins I/O Step Ins I/O
15 AND= R4918 15 NOP
K106
18 + R4916 16 NOP
K10000
D87
22 END 17 NOP
No Data exists. 18 + R4916
K10000
D87
No Data exists. 22 END
PgDn : Next page Esc : Close

- 68 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

Appendix 1.5 PLC-Related Data Development Procedure

This section explains a procedure for developing PLC-related data such as alarm messages,
operator messages, PLC switches. The following items are the same as those of GX Developer.
Refer to the GX Developer side.

File name, development procedure, message data description method

Appendix 1.5.1 Conversion to GPPQ data

Use the "CNVQ (data conversion software package)" for conversion from text data to GPPQ data.
Instead of text data, spreadsheet software data can also be converted to GPPQ data. Refer to the
Operating Manual for details.

(1) Initialization

After CNVQ is started, the project file (file for setting the drive/path name, system name,
machine name, file name, etc.) is read or newly created.
Refer to the Operating Manual for the operation method.

(2) Conversion Format Setting

The screen is selected from the menu using the following CNVQ basic operation.

Mode Conversion
F11 ( HOME CLR ) selection 3 format set- Alt ( GRPH ) 2
Mode menu screen Conversion ting screen
Menu Conversion
format setting format change

Conversion Command Command list

format change 7 list menu 2 (text format
menu window window setting) screen
Command Text format
list setting

The conversion format is set on the following screen. Select the "Statement" item shown by the
arrow (1) when converting message data.
Refer to the CNVQ Operating Manual for details.

[Instruction list (text format setting)]

1. Delimter
1. ( * ) Tab 1. ( * ) Auto Adjust (1Tab [ 8]Column)
2. ( ) Left Align
3. ( ) Specify [ 1]Tab
2. ( * ) Space 1. ( * ) Auto Adjust
2. ( ) Left Align
3. ( ) Specify [ 1]Column
2. Input Conditions
1. ( ) Step #
2. ( ) Device Comment
3. ( * ) Statement (1)
4. ( ) Note
5. ( ) Device Label
6. ( ) Without NOP

Execute(Y) Cancel(N)

Space : Select Esc : Close

- 69 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

Appendix 1.5.2 Commercially available software QnA conversion setting

The screen is selected from the menu using the following CNVQ basic operation.

Mode Commercially
F11 ( HOME CLR ) selection 1 available software
menu screen -> QnA conversion
Mode Com mercially setting screen
available software
-> QnA conversion

The conversion source/destination directory path and conversion file name, etc., are set on the
following screen. Refer to the Operating Manual for details.

Other --> QnA Convert C:M600\TEST\SETUPM1 <Ins> F11:Mode

Conversion Destination File
Drive/Path[C:\GPPQ\USR
Conversion Source File
Drive/Path[C:\CNVQ\USR\M600\TEST

# Conv SourceFile DestFile Data # FileType ConvType Another

000 [ ] [M1TEST ] [M600\TEST\M1TEST ] [ 1] <Text> < List > [ ]
001 [ ] [ ] [ ] [ ] < > < > [ ]
002 [ ] [ ] [ ] [ ] < > < > [ ]
003 [ ] [ ] [ ] [ ] < > < > [ ]
004 [ ] [ ] [ ] [ ] < > < > [ ]
005 [ ] [ ] [ ] [ ] < > < > [ ]
006 [ ] [ ] [ ] [ ] < > < > [ ]
007 [ ] [ ] [ ] [ ] < > < > [ ]
008 [ ] [ ] [ ] [ ] < > < > [ ]
009 [ ] [ ] [ ] [ ] < > < > [ ]
010 [ ] [ ] [ ] [ ] < > < > [ ]

PgUp : Prev Page PgDn : Next Page Ctrl+P :Drive/Path Enter : Decide

Appendix 1.5.3 Conversion execution

The screen is selected from the menu using the following CNVQ basic operation.

Commercially Project Conversion

available software 1 execution
Alt ( GRPH ) menu 4
-> QnA conversion confirmation
setting screen Menu Project window Execution screen

The conversion status appears at the bottom of the screen. If "There were n conversion errors"
appears when the conversion is finished, display the conversion error edit screen from the menu
using the following CNVQ basic operation to confirm the error contents.

Commercially Conversion Conversion

available software 2 1
Alt ( GRPH ) error menu error edit
-> QnA conversion
setting screen Menu window Edit window
Conversion
error

- 70 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

Appendix 1.5.4 Operation with the GPPQ

Message data in the GPPQ is handled as "Integrated type interlinear statements" in the PLC
program. "Integrated type interlinear statements" are interlinear comments to help in understanding
the PLC program. Interlinear comments transferred with the PLC program to the controller are
called "integrated type".
"Interlinear statements" can be displayed in the "Circuit mode", and edited on the "Interlinear
statement edit screen".

(1) Interlinear Statement Display in the Circuit Mode

The screen is selected from the menu using the following GPPQ basic operation.

Display Interlinear
Circuit mode Alt ( GRPH ) 4 menu 3 statement
screen display
Menu Display window Interlinear screen
statement

The following appears. At that time, the page break code and end code appear as normal
ladder codes.

$, A, 32, 200
$, 0, 40, 200
$, P, 12, 32
$, M, 60, 20
12 NOPLF
A, 0, 0, EMERGENCY STOP
A, 11, 1, SPINDLE ALARM
:
:
:
:
98 NOPLF
:
:
:
:

- 71 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

(2) Interlinear Statement Editing

The screen is selected from the menu using the following GPPQ basic operation.

Mode Device
F11 ( HOME CLR ) selection 7 comment Alt ( GRPH ) 5
Mode menu screen Text creation edit screen Menu Edit

Edit menu
screen 6 Step No. Interlinear
Interlinear designation [ Step ] Enter Y statement
statement
screen Execution edit screen
Ctrl + F7
Statement

The message data can be edited on the following screen. The GPPQ data can be converted to
text data using the CNVQ to save the edited data as text data. Refer to the CNVQ Operating
Manual for details.

Document Statmnt CPU: Q4A

Step
Level 1234567890123456789012345678901234567890123456789012345678901234
[ 0] [$, A, 32, 200 ]
[ 3] [$, 0, 40, 200 ]
[ 6] [$, P, 12, 32 ]
[ 9] [$, M, 60, 20 ]
[ 12] [A, 0, 0, EMERGENCY STOP ]
[ 15] [A, 11, 1, SPINDLE ALARM ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]
[ ] [ : ]

- 72 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

Appendix 1.5.5 Transfer to the controller

The following shows the method of transferring a message from the GPPQ to the CNC controller.
The transfer method is the same as that of the ladder code. Ladder codes and message data are
distinguished by their file names only.

(1) Menu Selection

The screen is selected from the menu using the following basic operation.

PLC menu PLC write

Mode screen Alt ( GRPH ) 2 2
window screen
Menu PC Write

(2) Screen Operation

Transfer is executed in the following screen.

An example of transferring a message 1st language file "M1TEST.GPG" is shown here.

[Write to PLC]
Interface RS232C <---> QnACPU
Target PLC Network : 0 Station : FF PC Type : Q4A
Target Mem Internal RAM Title [ ]
1. File 1. File Name [ M1TEST ] Title [ message 1st language test ]
2. Tgt 1. [ ] Parameter
2. [ * ] Seq/SFC Prog 1. ( * ) Whole Range
2. ( ) Step Range [ ]–[ ]
3. [ ] Device Comment 3. ( ) Step Range P[ ] – [ ]
4. [ ] Dev Init Value 4. ( ) Block Range [ ]–[ ]
5. [ ] Simulation Data
6. [ ] File Register 1. ( * ) Whole Range
2. ( ) Specify ZR[ ]–[ ]
2. Device Mem 1. [ ] Internal 1. ( * ) Whole Range
2. ( ) Specify Detail Range

Execute(Y) Cancel(N)

Ctrl+L : filelist Ctrl+D : directo Space : sele Esc:close

Appendix 1.5.6 Reading and comparing from the controller

The following describes the method of reading and comparing a message from the CNC controller
to the GPPQ. The method of reading and comparing is the same as that of ladder codes. Ladder
codes and message data are distinguished by their file names only.

(1) Menu Selection/Screen Operation

Refer to the following sections for operation methods.

For reading : "Appendix 1.3 Ladder Read from the CNC Controller"
For comparing : "Appendix 1.4 Ladder Comparison with CNC Controller"

- 73 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.5 PLC-Related Data Development Procedure

(2) Message Read Format

The message description format was shown in "5.3.1 Description format", but there are no
special rules concerning provision of descriptions in the setting area or the order of message
description in the message area. For that reason, the description format may differ between
transfer and reading of the message data.
The following shows the format during reading as the "Standard description format".

Standard description format of message data

Alarm message setting … (a)

Operator message setting
PLC switch setting
Comment message setting
Alarm messages … (b)
Operator messages … (c)
PLC switches … (d)
Comment messages … (e)
NOPLF
END

(a) Setting area

The settings are described in order of alarm, operator, PLC switch and comment.
The maximum value is described if the setting is abbreviated.

(b) Alarm messages

Each message data is described in order of the index Nos.

(c) Operator messages

The same as the alarm messages.

(d) PLC switches

Each message data is described in order of the switch Nos.

(e) Comment messages

These messages are described in the same order as described before transfer.

(f) Others
• Spaces and tabs are not included before and after the comma(,) separating the message
data factors.
• The message character string is handled the same as normal data even when blank.
• The NOPLF code between messages is described to the position to which the message
data following the NOPLF code during transfer moved.

(3) Message Data Comparison

Message data comparison can be executed in the same manner as the ladder program,
however, note that the target compared is the ladder code (NOPLF, END) only. Therefore,
message data described as "Integrated type interlinear statements" are not compared.
When comparing, read the data to the GPPQ side using the read function, then compare using
the master file and file comparison function.

- 74 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.6 Procedure for ROM Writing

Appendix 1.6 Procedure for ROM Writing

The procedure to write the developed PLC program and PLC related data to ROM is explained here.
The following item are the same as that of GX Developer. Refer to the GX Developer side.
• Target Data to be written to ROM

Appendix 1.6.1 Procedure to write to ROM

The following shows the procedure to write to ROM.

ROM cassette insertion ... Insert the ROM cassette in the CBUS1 slot.

... Contents are read if PLC data already exists on the ROM cassette.
Power turned ON

PLC data region formatted ... The PLC data region is formatted with the GPPQ.
Already existing PLC data is erased.
PLC (Ladder programs are not erased.)
stop
PLC data transfer ... The required PLC data is transferred from the GPPQ.

Operation confirmation ... The operation of the transferred PLC data is confirmed.

ROM write ... ROM writing is carried out with the GPPQ.

NC restart ... The PLC data is read from the ROM cassette.

Operation reconfirmation ... The operation of the PLC data is confirmed again.

- 75 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.6 Procedure for ROM Writing

Appendix 1.6.2 PLC data region formatting

It is recommended to initialize the data region before ROM writing. (This is not absolutely
required, however.)
The difference from file deletion is that the file control region is initialized.
The screen is selected from the menu using the following basic operation.

Mode On-line
F11 ( HOME CLR ) selection 5 mode Alt ( GRPH ) 2
Mode menu screen On-line screen Menu PC

PLC memory
PLC menu batch 2
B
window operation
PLC memory window PLC memory
batch operation format

The PLC related data (excluding ladder programs) is completely erased by the above operation.

Appendix 1.6.3 ROM writing from the GPPQ

(1) On-line mode

ROM writing operations are carried out on the On-line mode screen.
The mode is selected from the menu using the following basic operation.

Mode On-line
F11 ( HOME CLR ) selection 5 mode
Mode menu screen On-line screen

The following drive name selection screen or file name selection screen appears. If the file
name selection screen appears, it can be returned to the drive name selection screen with the
Escape [esc] key.

On-Line CPU:Q4A NW:Local C:TEST\M1TEST

Interface RS232Cport <---> QnACPU

Target PLC Network : 0 Station : FF PLC Type : Q4A

Target Memory Contents Title

<Drive>
0. Internal RAM [ ON BOARD S-RAM + (D-RAM) ]
1. IC Card A(RAM) [ ON BOARD D-RAM ]
2. IC Card A(ROM) [ ]
3. IC Card B(RAM) [ ]
4. IC Card B(ROM) [ ]

- 76 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.6 Procedure for ROM Writing

(2) Drive name selection screen

The drive mounted on the CNC controller can be selected, and the following operations carried
out, on the drive name selection screen.
• Copying between drives (Including flash ROM writing)
• Displaying the drive details (date of creation, size)
• Confirmation of the drive open capacity, etc.
The mounting and PLC data availability is checked for each drive. The header statement
appears when PLC data exists. There are sections in which the drive target memory and the
actual CNC controller drive meaning differ, so confirm with the header statement.
The following shows the meanings in the CNC controller of each drive.

Drive Screen display Meaning in the M600 Header statement display

0 Internal RAM Internal S-RAM ON BOARD S-RAM + (D-RAM)
(ladder programs)
1 IC memory card A (RAM) Internal D-RAM ON BOARD D-RAM
(other than ladder programs)
2 IC memory card A (ROM) Internal F-ROM ON BOARD F-ROM
3 IC memory card B (RAM) Expansion S-RAM
(for future use)
4 IC memory card B (ROM) Expansion F-ROM ADD ON F-ROM

• Drive 0
This refers to the file groups stored in the internal S-RAM (ladder programs) and internal D-
RAM (other than ladder programs).
File transfer with GPPQ is carried out in this drive 0.
Only internal S-RAM information is displayed for the drive capacity.

• Drive 1
This refers to the file groups stored in the internal D-RAM (other than ladder programs).
Only internal D-RAM information is displayed for the drive capacity.

• Drive 2
This refers to the file groups stored in the internal F-ROM. The ladder related data storage
availability to the internal F-ROM differs depending on the system.
Approx. 30 seconds are required until the finish of the writing (copying to drive 2) process to the
internal F-ROM.

• Drive 4
This refers to the file group stored in the cassette F-ROM inserted in the expansion bus. The
expansion bus insertion position is automatically judged.
Approx. 10 seconds are required until the finish of the writing (copying to drive 4) process to the
cassette F-ROM.

- 77 -
 APPENDIX 1. OPERATION METHODS USING GPPQ
Appendix 1.6 Procedure for ROM Writing

(3) Copying operation between drives (flash ROM writing operations)

↑ , ↓ F8 ↑ , ↓ Enter
File selection Copy source Copy destination Copy
selection selection

Select the copy source target memory using ↑ and ↓ , and press F8 .
Set the band cursor to the copy destination target memory drive. The following dialog box appears
when Enter is pressed.

Do you want to copy from Internal RAM to IC Card B(ROM)?

Yes(Y) No(N)

Press Y to execute.
The copy process between drives is executed in the background. The write process starting
message is displayed immediately after execution, and the next operation is not accepted during the
copy process. The copy process time differs depending on the copy target.
A message will appear at the first operation after the copy process is finished if an error occurred in
the copy process. No message will appear if the copy process finished normally.
The following shows the meanings of the messages during and after execution.

Cannot communicate with PLC. The drive background writing process has
Error No. = 4068 started.

Cannot communicate with PLC. Other processes cannot be accepted

Error No. = 4008 during drive writing process. Wait a few
seconds and execute again.

Cannot write correctly to the ROM The flash ROM writing was unsuccessful.

- 78 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.1 Development Tools, etc.

APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT

BETWEEN PLC4B AND M600, M60/60S
This section explains differences between the PLC4B development environment and M600,
M60/60S series PLC development environment.

Appendix 2.1 Development Tools, etc.

In the M600, M60/60S, a user PLC development environment that used the MELSEC PLC
development tool was constructed. Consequently, the tools used at each development process
differ. A comparison of each process is shown in "Table 2.1 List of development tool comparisons".
Refer to the respective lnstruction Manuals for details on each tool.

Table 2.1 List of development tool comparisons

Development MELSEC PLC development
PLC4B development environment
process environment
Application from the Tool Ladder and message conversion tool Ladder list converter (CLST6L)
old model (CHG4PB)
Hardware PC9801/PC-AT PC-AT
List -> ladder Tool PLC development software GX Converter
conversion (list section) (LIST4B)
Hardware PC9801/PC-AT PC-AT
Ladder creation Tool PLC development software GX Developer
(ladder section) (PLC4B)
Hardware PC9801/PC-AT PC-AT
Message creation Tool PLC development software Text editor -> GX Converter ->
(ladder section) (PLC4B) GX Developer
Hardware PC9801/PC-AT PC-AT
Transfer to the CNC Tool PLC4B <-> FLD <-> M500 controller GX Developer <-> RS232C <->
CNC controller
Hardware Via FLD Via RS-232C
Monitor Tool (1) GX Developer
Hardware PC-AT <-> CNC controller
Tool (2) PLC onboard (ONBD) PLC onboard
Hardware M500 controller CNC controller
ROM writing Tool PLC onboard -> F-ROM I/O screen -> F-ROM
Hardware M500 controller CNC controller
Print output Tool (1) PLC development software GX Developer
(ladder section) (PLC4B)
Hardware PC9801/PC-AT PC-AT
Tool (2) PLC onboard (ONBD)
Hardware M500 controller

- 79 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.2 Devices and Device Assignments

Appendix 2.2 Devices and Device Assignments

In the M600 M60/60S, the device types and assignments have been reconsidered by supporting the
user PLC development environment that used the MELSEC PLC development tool.
A comparison of the differences of each device is shown in the following tables "List of device
differences".
Refer to the "List of M600 PLC I/F" for details on assignments.

Table 2.2.1 List of device differences (M600M series)

Device M500 device No. M600 device No. Remarks
X X0 to X4FF
Integrated to X and assignment
U U0 to U17F X0 to XAFF
changed.
I I0 to I4BF
Y Y0 to Y57F
Integrated to Y and assignment
W W0 to W1FF Y0 to YDFF
changed.
J J0 to J63F
S S0 to S1FF Divided to X and Y and assignment
⎯⎯⎯
changed.
Integrated to M and assignment
M M0 to N5119 M0 to N5119
changed.
G G0 to G3071 M5120 to M8191
F F0 to F127 F0 to F255
L L0 to L255 ←
E E0 to E127 SM0 to SM127
T0 to T15 T0 to T15
Q0 to Q39 T16 to T55
T16 to T95 T56 to T135 Integrated to T and assignment
T/Q
Q40 to Q135 T136 to T231 changed.
T96 to T103 T232 to T239
Q136 to Q151 T240 to T255
C C0 to C23 C0 to C23 Integrated to C and assignment
B B0 to B103 C24 to C127 changed.

D D0 to D1023 ←
R R0 to R8191 ← Assignment changed.
A0, A1 Discontinued
A ⎯⎯⎯
(replaced by D and R registers).
Z Z Z0
V V Z1 Discontinued (replaced by Z1).
N N0 to N17 ←
P P0 to P255 ←
K-32768 to K32767
K K-2147483648 to ←
K2147483647
H0 to HFFFF
H ←
H0 to HFFFFFFFF

- 80 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.2 Devices and Device Assignments

Table 2.2.2 List of device differences (M600L series)

M500 device No. M600 device No. Remarks
X X0 to X4BF -> X0 to X4BF
U U0 to U17F -> X4C0 to X63F Input for 2nd part system
I I0 to I3FF -> X640 to XA3F X Input for 3rd to 8th part system
S S0 to S3F -> XA40 to XA7F Input for 3rd and 4th spindle
S S80 to SBF -> XA80 to XABF Input for 5th and 6th spindle
Y Y0 to Y53F -> Y0 to Y53F
W W0 to W1FF -> Y540 to Y73F Output for 2nd part system
J J0 to J63F -> Y740 to YD7F Y Output for 3rd to 8th part system
S S40 to S7F -> YD80 to YDBF Output for 3rd and 4th spindle
S SC0 to SFF -> YDC0 to YDFF Output for 5th and 6th spindle
M M0 to M5119 -> M0 to M5119 M
G G0 to G3071 -> M5120 to M8191
F F0 to F127 -> F0 to F127 F
L L0 to L255 -> L0 to L255 L
E E0 to E127 -> SM0 to SM127 SM
T T0 to T15 -> T0 to T15 10ms timer
Q Q0 to Q39 -> T16 to T55 10ms timer (fixed timer)
T T16 to T95 -> T56 to T135 100ms timer
T
Q Q40 to Q135 -> T136 to T231 100ms timer (fixed timer)
T T96 to T103 -> T232 to T239 100ms integrated timer
Q Q136 to Q151 -> T240 to T255 100ms integrated timer (fixed timer)
C C0 to C23 -> C0 to C23
C
B B0 to B103 -> C24 to C127
D D0 to D1023 -> D0 to D1023 D
R R0 to R8191 -> R0 to R8191 R
A A0, A1 -> Discontinued
(replaced by D and R registers).
Z Z -> Z0
Z
V V -> Z1
N N0 to N7 -> N0 to N7 N
P P0 to P255 -> P0 to P255 P
K K-32768 to K32767 K-32768 to K32767
K-2147483648 to -> K-2147483648 to K
K2147483647 K2147483647
H H0 to HFFFF H0 to HFFFF
-> H
H0 to HFFFFFFFF H0 to HFFFFFFFF

- 81 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.2 Devices and Device Assignments

Table 2.2.3 List of device differences (M60 series)

PLC4B device No. GX Developer device No. Remarks
X X0 to X4BF -> X0 to X4BF
X
U U0 to U17F -> X4C0 to X63F Input for 2nd part system
Y Y0 to Y53F -> Y0 to Y53F
Y
W W0 to W1FF -> Y540 to Y73F Output for 2nd part system
M M0 to M5119 -> M0 to M5119 M
G G0 to G3071 -> M5120 to M8191
F F0 to F127 -> F0 to F127 F
L L0 to L255 -> L0 to L255 L
E E0 to E127 -> SM0 to SM127 SM
T T0 to T15 -> T0 to T15 10ms timer
Q Q0 to Q39 -> T16 to T55 10ms timer (fixed timer)
T T16 to T95 -> T56 to T135 100ms timer
T
Q Q40 to Q135 -> T136 to T231 100ms timer (fixed timer)
T T96 to T103 -> T232 to T239 100ms integrated timer
Q Q136 to Q151 -> T240 to T255 100ms integrated timer (fixed timer)
C C0 to C23 -> C0 to C23
C
B B0 to B103 -> C24 to C127
D D0 to D1023 -> D0 to D1023 D
R R0 to R8191 -> R0 to R8191 R
A A0, A1 -> Discontinued
(replaced by D and R registers).
Z Z -> Z0
Z
V V -> Z1
N N0 to N7 -> N0 to N7 N
P P0 to P255 -> P0 to P255 P
K K-32768 to K32767 K-32768 to K32767
K-2147483648 to -> K-2147483648 to K
K2147483647 K2147483647
H H0 to HFFFF H0 to HFFFF
-> H
H0 to HFFFFFFFF H0 to HFFFFFFFF

- 82 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.2 Devices and Device Assignments

Table 2.2.4 List of device differences (M60S series)

PLC4B device No. GX Developer device No. Remarks
X X0 to X4BF -> X0 to X4BF
U U0 to U17F -> X4C0 to X63F Input for 2nd part system
I I0 to I3FF -> X640 to XA3F Input for 3rd to 8th part system
S S0 to S1F -> XA40 to XA5F X Input for 3rd spindle
S S40 to S5F -> XA60 to XA7F Input for 4th spindle
S S80 to S9F -> XA80 to XA9F Input for 5th spindle
S SC0 to SDF -> XAA0 to XABF Input for 6th spindle
Y Y0 to Y53F -> Y0 to Y53F
W W0 to W1FF -> Y540 to Y73F Output for 2nd part system
J J0 to J63F -> Y740 to YD7F Output for 3rd to 8th part system
S S20 to S3F -> YD80 to YD9F Y Output for 3rd spindle
S S60 to S7F -> YDA0 to YDBF Output for 4th spindle
S SA0 to SBF -> YDC0 to YDDF Output for 5th spindle
S SE0 to SFF -> YDE0 to YDFF Output for 6th spindle
M M0 to M5119 -> M0 to M5119 M
G G0 to G3071 -> M5120 to M8191
F F0 to F127 -> F0 to F127 F
L L0 to L255 -> L0 to L255 L
E E0 to E127 -> SM0 to SM127 SM
T T0 to T15 -> T0 to T15 10ms timer
Q Q0 to Q39 -> T16 to T55 10ms timer (fixed timer)
T T16 to T95 -> T56 to T135 100ms timer
T
Q Q40 to Q135 -> T136 to T231 100ms timer (fixed timer)
T T96 to T103 -> T232 to T239 100ms integrated timer
Q Q136 to Q151 -> T240 to T255 100ms integrated timer (fixed timer)
C C0 to C23 -> C0 to C23
C
B B0 to B103 -> C24 to C127
D D0 to D1023 -> D0 to D1023 D
R R0 to R8191 -> R0 to R8191 R
A A0, A1 -> Discontinued (replaced by D, R registers)
Z Z -> Z0
Z
V V -> Z1
N N0 to N7 -> N0 to N7 N
P P0 to P255 -> P0 to P255 P
K K-32768 to K32767 K-32768 to K32767
K-2147483648 to -> K-2147483648 to K
K2147483647 K2147483647
H H0 to HFFFF H0 to HFFFF
-> H
H0 to HFFFFFFFF H0 to HFFFFFFFF

- 83 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.3 PLC Instructions

Appendix 2.3 PLC Instructions

As for types and numbers of the PLC instructions, those of the PLC4B development environment
and of the MELSEC PLC development environment are not different basically. However, some
instructions have been changed because the user PLC development environment using the
MELSEC PLC development tool has been supported in M600, M60/60S.

The instruction range that can be used in the MELSEC-QnA Series PLC program differs from the
instruction range that can be used by the MELDAS Series. Because of this, some instructions that
can be used by the M600, M60/60S cannot be handled with the GX Developer. There are also
instructions that can be used by the GX Developer but cannot be used by the M600, M60/60S.
When these are arranged, they are classified into the three following types.
• M600, M60/60S instructions that cannot be handled with the GX Developer
• M600, M60/60S instructions that the format differs from that of the GX Developer
• Instructions that can be used by the GX Developer, but cannot be used by the M600,
M60/60S

Appendix 2.3.1 Instructions that cannot be handled with the GX Developer

Instructions that cannot be handled with the GX Developer are substituted with alternate instructions
that can be handled with the GX Developer. Instructions that can be alternated are shown in "Table
2.3.1 Table of alternate instruction correspondence".
When some instructions described in "Table 2.3.1 Table of alternate instruction correspondence"
are created with the GX Developer with the M600, M60/60S instruction sign left as is, an error
results and creation cannot be carried out. Create the instructions using the GX Developer
instruction sign described in the correspondence table.
When PLC programs containing alternate instructions are written from the GX Developer to the
M600, M60/60S, they are rewritten to the original MELDAS Series instructions.

Table 2.3.1 Table of alternate instruction correspondence

Original MELDAS Series instruction GX Developer instruction
Instruction Instruction
Classification Symbol Symbol
sign sign
D
Bit DEFR ⎯[ DEFR D ]⎯ ANDP
⎯ ↑ ⎯
Average value AVE ⎯[ AVE S D n ] S.AVE ⎯[ S.AVE S D n ]
Carry flag set STC ⎯[ STC ] S.STC ⎯[ S.STC ]
Carry flag reset CLC ⎯[ CLC ] S.CLC ⎯[ S.CLC ]
ATC ATC ⎯[ ATC Kn Rn Rm ]-< Mm > S.ATC ⎯[ S.ATC Kn Rn Rm Mm ]
ROT ROT ⎯[ ROT Kn Rn Rm ]-< Mm > S.ROT ⎯[ S.ROT Kn Rn Rm Mm ]
TSRH TSRH ⎯[ TSRH Rm Rn ]-< Mn > S.TSRH ⎯[ S.TSRH Rm Rn Mn ]
DDBA DDBA ⎯[ DDBA Rn / Dn ] S.DDBA ⎯[ S.DDBA Rn / Dn ]
DDBS DDBS ⎯[ DDBS Rn ] S.DDBS ⎯[ S.DDBS Rn ]
CAL1 CAL1 ⎯[ CAL1 Pn ] S.CAL1 ⎯[ S.CAL1 Pn ]
LDBIT [ BIT S1 n ]⎯ LD<= [ < = S1 n ]⎯
ANDBIT ⎯[ BIT S1 n ]⎯ AND<= ⎯[ < = S1 n ]⎯
ORBIT [ BIT S1 n ] OR<= [ < = S1 n ]
BIT
LDBII [ BII S1 n ]⎯ LD<> [ < > S1 n ]⎯
ANDBII ⎯[ BII S1 n ]⎯ AND<> ⎯[ < > S1 n ]⎯
ORBII [ BII S1 n ] OR<> [ < > S1 n ]
[Note] Among the above instructions, the ranges of the usable instructions depends on the model.

- 84 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.3 PLC Instructions

Appendix 2.3.2 Instructions with the format that differs from that of the GX Developer

The device types and assignments have been reconsidered as "Appendix 2.2 Devices and Device
Assignments".
The format of conventional "instructions used by inputting or outputting an accumulator (A0, A1)" is
changed so that the general word register can be designated with arguments without fixing by A0 or
A1 input or output because of the discontinuance of accumulator (A0, A1).
Format-changed instructions are shown in "Table 2.3.2 Table of format-changed instruction
correspondence".
When some instructions described in "Table 2.3.2 Table of format-changed instruction
correspondence" are created with the GX Developer with the conventional instruction sign left as is,
an error results and creation cannot be carried out. Create the instructions using the GX Developer
instruction sign described in the correspondence table.

Table 2.3.2 Table of format-changed instruction correspondence

Original MELDAS Series
Format-changed instruction
instruction
Remarks
Instruction Instruction
Classification Symbol Symbol
sign sign
Right rotation ROR ⎯[ ROR n ] ROR ⎯[ ROR D n ] ∗1
RCR ⎯[ RCR n ] RCR ⎯[ RCR D n ]
DROR ⎯[ DROR n ] DROR ⎯[DROR D n ]
DRCR ⎯[ DRCR n ] DRCR ⎯[ DRCR D n]
Left rotation ROL ⎯[ ROL n ] ROL ⎯[ ROL D n ]
RCL ⎯[ RCL n ] RCL ⎯[ RCL D n ]
DROL ⎯[ DROL n ] DROL ⎯[ DROL D n ]
DRCL ⎯[ DRCL n ] DRCL ⎯[ DRCL D n ]
Search SER ⎯[ SER S1 S2 n ] SER ⎯[ SER S1 S2 D n ] ∗2
Quantity of 1 SUM ⎯[ SUM S ] SUM ⎯[ SUM S D ] ∗3
∗1 : D is the head No. of the rotation device (word 16-bit device)
∗2 : D is the head No. of the device that stores the search results (word bit device)
∗3 : D is the head No. of the device that stores the total No. of bits (word bit device)

- 85 -
 APPENDIX 2. DIFFERENCES IN DEVELOPMENT ENVIRONMENT BETWEEN PLC4B
AND M600, M60/60S
Appendix 2.3 PLC Instructions

Appendix 2.3.3 Instructions that can be used with the GX Developer, but cannot be used
by the M600, M60/60S

When instructions that cannot be used by the M600, M60/60S are written from the GX Developer to
the M600, M60/60S, they are rewritten to "NOP" instructions, and if they are run, an alarm will occur.
(Note that instructions described in "Table 2.3.1 Table of alternate instruction correspondence" are
rewritten to the corresponding M600, M60/60S instructions.)
"Instructions that can be used by the GX Developer, but cannot be used in the M600, M60/60S " are
defined by the following expression.

"Instructions that can be used by the GX Developer, but cannot be used in the M600, M60/60S"
= "All instructions described in the QnA Programming Instruction Manual"
- ("All instructions described in the M600, M60/60S PLC Programming Instruction
Manual"
+ "Table 2.3.1 Table of alternate instruction correspondence"
+ "Table 2.3.2 Table of format-changed instruction correspondence")

Refer to "Appendix 3. MELSEC QnA Series Instructions Lists."

- 86 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.1 Sequence Instructions

APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER

The following instruction lists are excerpts from the "QnACPU Programming Manual (Common
Instructions)" (model name: QNACPU-P (KYOUTU) 13J522).
In these lists, the instructions "marked U" are unavailable for the M600, M60/60S series. (When
written from GX Developer to the M600, M60/60S series, they are replaced by "NOP" instructions.)

Appendix 3.1 Sequence Instructions

Contact instructions Coupling instructions
Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
Contact Coupling
LD ANB ANB

LDI
ORB ORB
AND
MPS MPS
ANI MRD MRD

OR MPP MPP

INV
ORI
LDP MEP

MEF
LDF
Vn
EGP
ANDP
Vn
EGF
ANDF

ORP

ORF

Output instructions Shift instructions

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
Output Shift
OUT SFT SFT D

SET SET D SFTP SFTP D

RST RST D
Master control instructions
PLS PLS D
Classifi- Instruction
Symbol
PLF PLF D cation sign
Master
MC n D
FF FF D control MC
MCR MCR n
DELTA DELTA D

DELTAP DELTAP D

- 87 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.2 Comparison Operation Instructions

End instructions Other instructions

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
Stop
Program FEND FEND STOP STOP
end No
END END NOP
opera-
tion NOPLF NOPLF

PAGE PAGE n

Appendix 3.2 Comparison Operation Instructions

Comparison operation instructions Comparison operation instructions (Continued)

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign

16-bit LD S1 S2 32-bit LDD D S1 S2

data S1 S2 data D S1 S2
AND ANDD
compar- compar-
ison OR S1 S2
ison ORD D S1 S2

LD S1 S2 LDD D S1 S2

AND S1 S2 ANDD D S1 S2

OR S1 S2 ORD D S1 S2

LD S1 S2 LDD D S1 S2

AND S1 S2 ANDD D S1 S2

OR S1 S2 ORD D S1 S2

LD S1 S2 LDD D S1 S2

AND S1 S2 ANDD D S1 S2

OR ORD D S1 S2
S1 S2

LD S1 S2 LDD D S1 S2

AND S1 S2 ANDD D S1 S2

OR ORD D S1 S2
S1 S2

LD S1 S2 LDD D S1 S2

AND S1 S2 ANDD D S1 S2

OR S1 S2
ORD D S1 S2

- 88 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.2 Comparison Operation Instructions

Comparison operation instructions (Continued) Comparison operation instructions (Continued)

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
Real E S1 S2 Charac- $ S1 S2
LDE LD$
number ter
data ANDE E S1 S2 string AND$ $ S1 S2
compar-i data
son compar-
ORE E S1 S2 ison OR$ $ S1 S2

LDE E S1 S2 LD$ $ S1 S2

ANDE E S1 S2 AND$ $ S1 S2

ORE E S1 S2 OR$ $ S1 S2

LDE E S1 S2 LD$ $ S1 S2

ANDE E S1 S2 AND$ $ S1 S2

ORE E S1 S2 OR$ $ S1 S2

LDE E S1 S2 LD$ $ S1 S2

ANDE E S1 S2 AND$ $ S1 S2

ORE E S1 S2 OR$ $ S1 S2

LDE E S1 S2 LD$ $ S1 S2

ANDE E S1 S2 AND$ $ S1 S2

ORE E S1 S2 OR$ $ S1 S2

LDE E S1 S2 LD$ $ S1 S2

ANDE E S1 S2 AND$ $ S1 S2

ORE E S1 S2 OR$ $ S1 S2
Block BKCMP S1 S2 D n
BKCMP
data
compar- BKCMP BKCMP S1 S2 D n
ison
BKCMP BKCMP S1 S2 D n

BKCMP BKCMP S1 S2 D n

BKCMP BKCMP S1 S2 D n

BKCMP BKCMP S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

BKCMP P BKCMP P S1 S2 D n

- 89 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.2 Comparison Operation Instructions

Arithmetic operation instructions Arithmetic operation instructions (Continued)

Classifi- Instruction Classific Instruction
Symbol Symbol
cation sign ation sign
BIN + S D
BCD B+ S D
+ B+
16-bit 4-digit
addition/ +P +P S D addition/ B+P B+P S D
subtrac- subtracti
tion + + S1 S2 D on B+ B+ S1 S2 D

+P +P S1 S2 D B+P B+P S1 S2 D

S D B B S D

P P S D B P B P S D

S1 S2 D B B S1 S2 D

P P S1 S2 D B P B P S1 S2 D
BIN D+ S D BCD DB+ S D
D+ DB+
32-bit 8-digit
addition/ D+P D+P S D addition/ DB+P DB+P S D
subtrac- subtracti
tion D+ D+ S1 S2 D on DB+ DB+ S1 S2 D

D+P D+P S1 S2 D DB+P DB+P S1 S2 D

D D S D DB DB S D

D P D P S D DB P DB P S D

D D S1 S2 D DB DB S1 S2 D

D P D P S1 S2 D DB P DB P S1 S2 D
BIN S1 S2 D BCD B S1 S2 D
B
16-bit 4-digit
multipli- P P S1 S2 D multipli B P B P S1 S2 D
cation/ cation/
division / / S1 S2 D division B/ B/ S1 S2 D

/P /P S1 S2 D B/P B/P S1 S2 D
BIN D S1 S2 D BCD DB S1 S2 D
D DB
32-bit 8-digit
multipli- D P D P S1 S2 D multipli DB P DB P S1 S2 D
cation/ cation/
division D/ D/ S1 S2 D division DB/ DB/ S1 S2 D

D/P D/P S1 S2 D DB/P DB/P S1 S2 D

- 90 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.2 Comparison Operation Instructions

Arithmetic operation instructions (Continued) Data conversion instructions (Continued)

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
E+ S D BIN BIN S D
E+ BIN
conver-
E+P E+P S D sion BINP BINP S D

Floating- E+ E+ S1 S2 D DBIN DBIN S D

point
data E+P E+P S1 S2 D DBINP DBINP S D
addition/ BIN ->
E S D FLT FLT S D
subtrac- E floating-
tion E P S D point FLTP S D
E P FLTP
conver-
E E S1 S2 D sion DFLT DFLT S D

E P E P S1 S2 D DFLTP DFLTP S D

E S1 S2 D Floating- INT S D
Floating- E INT
point ->
point
E P E P S1 S2 D BIN INTP INTP S D
data
conver-
multiplic-
E/ E/ S1 S2 D sion DINT DINT S D
ation/
division E/P E/P S1 S2 D DINTP DINTP S D

BK+ S1 S2 D n BIN DBL S D

BK+ DBL
BIN block 16-bit <->
addition/ BK+P BK+P S1 S2 D n 32-bit DBLP DBLP S D
subtrac- conver-
tion BK BK S1 S2 D n sion WORD WORD S D

BK P BK P S1 S2 D n WORDP WORDP S D

$+ S D BIN -> GRY S D

$+ GRY
Charac- gray code
ter $+P $+P S D conver- GRYP GRYP S D
string sion
data $+ $+ S1 S2 D DGRY DGRY S D
coupling
$+P $+P S1 S2 D DGRYP DGRYP S D
BIN data INC D Gray GBIN S D
INC GBIN
incre- code ->
ment INCP INCP D BIN GBINP GBINP S D
conver-
DINC DINC D sion DGBIN DGBIN S D

DINCP DINCP D DGBINP DGBINP S D

DEC D 2's NEG D

DEC NEG
comple-
DECP DECP D ment NEGP NEGP D

DDEC DDEC D DNEG DNEG D

DDECP DDECP D DNEGP DNEGP D

Data conversion instructions ENEG ENEG D

Classifi- Instruction
Symbol ENEGP ENEGP D
cation sign
BCD Block BKBCD S D n
BCD BCD S D BKBCD
conver- conver-
sion BCDP S D
sion BKBCDP BKBCDP S D n
BCDP
DBCD S D BKBIN BKBIN S D n
DBCD
DBCDP S D BKBINP BKBINP S D n
DBCDP

- 91 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.2 Comparison Operation Instructions

Data transfer instructions Program branch instructions

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
16-bit Jump CJ Pn
MOV MOV S D CJ
data
transfer MOVP MOVP S D SCJ SCJ Pn

32-bit DMOV S D JMP JMP Pn

DMOV
data
transfer DMOVP DMOVP S D GOEND GOEND

Floating- EMOV S D
EMOV Program execution control instructions
point
data EMOVP S D Classifi- Instruction
transfer EMOVP Symbol
cation sign
Charac- $MOV S D Interrupt
$MOV DI DI
ter string disable
data $MOVP S D
$MOVP Interrupt
transfer EI EI
enable
16-bit CML CML S D Interrupt
data NOT disable/
transfer CMLP CMLP S D IMASK IMASK S
enable
32-bit setting
DCML DCML S D
data NOT Return IRET IRET
transfer DCMLP DCMLP S D

Block BMOV S D n I/O refresh instructions

BMOV
transfer
Classifi- Instruction
BMOVP BMOVP S D n Symbol
cation sign
Same FMOV S D n I/O
FMOV RFS RFS D n
data refresh
block FMOVP FMOVP S D n
transfer Other useful instructions
16-bit XCH S D
XCH Classifi- Instruction
data Symbol
change S D
cation sign
XCHP XCHP
Up/down UDCNT1 UDCNT1 S D n
32-bit DXCH S D
DXCH counter
data UDCNT2 S D n
UDCNT2
change DXCHP DXCHP S D
Teaching
Block TTMR TTMR D n
BXCH BXCH S D n timer
data Special
change BXCHP S D n STMR STMR S n D
BXCHP timer
Nearest
Upper/ SWAP D
SWAP access ROTC ROTC S n1 n2 D
lower
control
byte SWAPP D
change SWAPP Ramp
RAMP RAMP n1 n2 D1 n3 D2
signal
Pulse
SPD SPD S n D
density
Pulse
PLSY PLSY n1 n2 D
output
Pulse
width
PWM PWM n1 n2 D
modula-
tion
Matrix
MTR MTR S D1 D2 n
input

- 92 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.3 Application Instructions

Appendix 3.3 Application Instructions

Logical operation instructions Logical operation instructions (Continued)

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
AND WAND S D NOT- WXNR S D
WAND WXNR
exclusive
WANDP WANDP S D OR WXNRP WXNRP S D

WAND WAND S1 S2 D WXNR WXNR S1 S2 D

WANDP WANDP S1 S2 D WXNRP WXNRP S1 S2 D

DAND DAND S D DXNR DXNR S D

DANDP DANDP S D DXNRP DXNRP S D

DAND DAND S1 S2 D DXNR DXNR S1 S2 D

DANDP DANDP S1 S2 D DXNRP DXNRP S1 S2 D

BKAND BKAND S1 S2 D n BKXNOR BKXNOR S1 S2 D n

BKANDP BKANDP S1 S2 D n BKXNORP BKXNORP S1 S2 D n

OR WOR S D
WOR

WORP WORP S D Rotation instructions

Classifi- Instruction
WOR WOR S1 S2 D Symbol
cation sign
WORP WORP S1 S2 D Right ROR D n
ROR
rotation
DOR DOR S D RORP RORP D n

DORP DORP S D RCR RCR D n

DOR DOR S1 S2 D RCRP RCRP D n

DORP S1 S2 D Left ROL D n

DORP ROL
rotation
BKOR BKOR S1 S2 D n ROLP ROLP D n

BKORP BKORP S1 S2 D n RCL RCL D n

Exclusive WXOR S D RCLP D n
WXOR RCLP
OR
Right DROR D n
WXORP WXORP S D DROR
rotation
WXOR S1 S2 D DRORP DRORP D n
WXOR
DRCR DRCR D n
WXORP WXORP S1 S2 D

DRCRP DRCRP D n
DXOR DXOR S D
Left DROL D n
DROL
DXORP DXORP S D rotation
DROLP DROLP D n
DXOR S1 S2 D
DXOR
DRCL DRCL D n
DXORP S1 S2 D
DXORP DRCLP D n
DRCLP
BKXOR S1 S2 D n
BKXOR
BKXORP S1 S2 D n
BKXORP

- 93 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.3 Application Instructions

Shift instructions Data processing instructions

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
n-bit shift SFR SFR D n Data SER S1 S2 D n
SER
search
SFRP SFRP D n
SERP SERP S1 S2 D n
SFL SFL D n
DSER DSER S1 S2 D n
SFLP SFLP D n
1-bit shift BSFR DSERP DSERP S1 S2 D n
BSFR D n
Bit check SUM S D
BSFRP D n
SUM
BSFRP
SUMP SUMP S D
BSFL BSFL D n
DSUM DSUM S D
BSFLP BSFLP D n
DSUMP DSUMP S D
1-word
DSFR DSFR D n Decode
shift DECO DECO S D n
DSFRP DSFRP D n
DECOP DECOP S D n

DSFL DSFL D n Encode ENCO S D n

ENCO
DSFLP DSFLP D n ENCOP S D n
ENCOP
7- SEG S D
SEG
segment
Bit processing instructions decode SEGP SEGP S D
Classifi- Instruction
Symbol Dissocia-t DIS S D n
cation sign DIS
ion
Bit • DISP S D n
BSET D n
set/reset BSET Associa-
DISP

BSETP D n tion UNI UNI S D n

BSETP
UNIP UNIP S D n
BRST BRST D n

BRSTP D n NDIS NDIS S1 D S2

BRSTP
Bit test TEST TEST S1 S2 D NDISP S1 D S2
NDISP
TESTP TESTP S1 S2 D
NUNI NUNI S1 D S2
DTEST DTEST S1 S2 D
NUNIP NUNIP S1 D S2

DTESTP DTESTP S1 S2 D WTOB S D n

WTOB
Bit device BKRST
BKRST S n WTOBP WTOBP S D n
Batch
reset BTOW S D n
BTOW
BKRSTP BKRSTP S n
BTOWP BTOWP S D n

- 94 -
 APPENDIX 3. LIST OF INSTRUCTIONS USABLE WITH GX DEVELOPER
Appendix 3.3 Application Instructions

Data processing instructions (Continued) Structuring instructions

Classifi- Instruction Classifi- Instruction
Symbol Symbol
cation sign cation sign
Retrieval MAX S D n Repeat FOR
MAX FOR n

MAXP MAXP S D n NEXT NEXT

MIN MIN S D n BREAK BREAK D Pn

MINP MINP S D n BREAKP BREAKP D Pn

DMAX S D n Sub- CALL Pn S1～Sn

DMAX CALL
routine
DMAXP DMAXP S D n program CALLP CALLP Pn S1～Sn
call
DMIN DMIN S D n RET RET

DMINP DMINP S D n FCALL FCALL Pn S1～Sn

Sort SORT S1 n S2 D1 D2 FCALLP Pn S1～Sn
FCALLP
S2:Number of data blocks to
be compared at a time. SORT * Pn S1~Sn
SORT D1:Device to be forced ON
ECALL * : Program name
at sort completion
D2:Used by system ECALLP * Pn S1~Sn
ECALLP * : Program name
DSORT S1 n S2 D1 D2
S2:Number of data blocks to EFCALL * Pn S1~Sn
be compared at a time. EFCALL * : Program name
DSORT D1:Device to be forced ON
at sort completion EFCALLP * Pn S1~Sn
D2:Used by system EFCALLP * : Program name
Total WSUM S D n
WSUM
value COM COM
calcula- WSUMP WSUMP S D n Fixed
tion IX S
DWSUM S D n
index
DWSUM qualifica- IX Device qualification circuit
DWSUMP S D n tion IXEND
DWSUMP
IXEND
Table operation instructions IXDEV IXDEV
Classifi- Instruction IXSET Pn D
Symbol
cation sign
Table FIFW S D IXSET
FIFW Designation of qualification
process-
ing FIFWP S D value
FIFWP

FIFR FIFR S D

FIFRP FIFRP S D

FPOP FPOP S D

FPOPP FPOPP S D

FINS S D n
FINS
FINS S D n
FINSP
FDEL S D n
FDEL
FDELP S D n
FDELP

- 95 -
 Revision History

Date of revision Manual No. Revision details

Aug. 2002 BNP-B2252B First edition created.

Sept. 2004 BMP-B2252C • Order of item configuration changed.

• Matters related to program development added to "Safety Precautions".
• Section "1. PLC Development Environment" totally reviewed.
• Mistakes, etc., corrected.
Notice
Every effort has been made to keep up with software and hardware revisions in the contents
described in this manual. However, please understand that in some unavoidable cases
simultaneous revision is not possible.
Please contact your Mitsubishi Electric dealer with any questions or comments regarding
the use of this product.

Duplication Prohibited
This manual may not be reproduced in any form, in part or in whole, without written
permission from Mitsubishi Electric Corporation.

©2002-2004 MITSUBISHI ELECTRIC CORPORATION

ALL RIGHTS RESERVED
 MITSUBISHI ELECTRIC CORPORATION
HEAD OFFICE : MITSUBISHI DENKI BLDG., 2-2-3, MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN

MODEL M600 60/60S Series

MODEL
CODE 008-244

Manual No. BNP-B2252C(ENG)

Specifications subject to change without notice.
(0409) MEE Printed in Japan on recycled paper.