Mitsubishi Electric Version 1 GX Converter Operating Manual
Below you will find brief information for GX Converter GX Converter Version 1. This document covers the installation, uninstallation and operation of the GX Converter, a software tool that can convert data between TEXT, CSV formats and the GX Developer format. The GX Converter can be used to convert data for lists and device comments, import and export data from the GX Developer, and to convert data for use with a wide variety of applications.
advertisement
Assistant Bot
Need help? Our chatbot has already read the manual and is ready to assist you. Feel free to ask any questions about the device, but providing details will make the conversation more productive.
MITSUBISHI ELECTRIC
MELSOFT
Programmable Logic Controllers
Operating Manual
GX Converter Version 1
SW0D5C-CNVW-E
Art. no.: 141235
01 02 2003
IB (NA)-0800004-D
MITSUBISHI ELECTRIC
INDUSTRIAL AUTOMATION
•
SAFETY INSTRUCTIONS
•
(Always read these instructions before using this equipment.)
When using this product, please thoroughly read this manual as well as GX Developer Operating Manual.
Also, please exercise adequate safety precautions and handle the product correctly.
A - 1 A - 1
REVISIONS
* The manual number is given on the bottom left of the back cover.
Print Date * Manual Number
Apr., 1999 IB (NA)-0800004-A First edition.
Revision
Jun., 2001 IB (NA)-0800004-B CNVW corrected to be GX Converter
GPPW corrected to be GX Developer
Modifications
Chapter 2, Chapter 3
Sep., 2001
Feb., 2003
Deletions
Appendix 5
IB (NA)-0800004-C Modifications
Chapter 3
IB (NA)-0800004-D Modifications
SOFTWARE USER REGISTRATION, INTRODUCTION, CONTENTS,
About Manuals, Section 2.1, Chapter 3, Section 3.2
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.
1999 MITSUBISHI ELECTRIC CORPORATION
A - 2 A - 2
—— SOFTWARE USER REGISTRATION ——
After agreeing to the terms of the Software License Agreement included in the package, please access the
MELFANSweb Home Page (http://www.nagoya.melco.co.jp/) and make a software user registration. (User registration is free of charge.)
You can also make a registration by faxing or mailing the "Software Registration Card" packed with the product.
1. Software Registration
You can make a software registration by accessing the MELFANSweb Home Page or faxing or mailing the
"Software Registration Card" packed with the product.
After you have made a software registration, we will register the user and send the "Software registration confirmation" together with the user ID.
We will also provide the latest information, such as the new product release, version upgrade information and event information, by direct mail.
2. Notes on Contact
Please ask questions concretely and clearly using terms listed in the manual.
When requesting us to solve a problem, provide us with detailed information for reproducing the problem.
In addition, contact the respective manufacturers when asking questions about the operating system (OS) or the other vender's software products
User registration is valid only in Japan.
A - 3 A - 3
Usage Precautions
The following describes precautions when using GX Converter.
(1) First, please read the "Safety Precautions."
(2) About installation
The GX Converter start by add-in to GX Developer Version 3 (SW3D5-GPPW-E) or later. Therefore, please install the GX Converter on Personal computer that have GX Developer Version 3 (SW3D5-GPPW-E) or later preinstalled.
The GX Converter cannot be added in to GX Developer Version 2 (SW2D5-
GPPW-E) or earlier.
(3) Multithreading communication
There are some cases where the screen will not be properly displayed while using GX Converter due to the lack of system resources.
If this occurs, close GX Converter and then close GX Developer (Programs,
Comment, etc.) and other applications, then restart GX Developer and GX
Converter.
(4) About CPU types
Depending on type of CPU used for the GX Developer project, there are some cases where Instruction or I/O (Device) cannot be correctly converted during data conversion.
See " GX Developer Operating Manual" for details.
(5) About the file format when TEXT, CSV format files are being read by the GX
Developer
The file format is fixed when export List or Device comments to a TEXT, CSV format file.
Therefore, create List or Device comments using commercial software using the file formats specified above as much as possible.
A - 4 A - 4
INTRODUCTION
Thank you for choosing the Mitsubishi MELSOFT Series Integrated FA software.
Read this manual and make sure you understand the functions and performance of MELSOFT series thoroughly in advance to ensure correct use.
CONTENTS
SAFETY INSTRUCTIONS.............................................................................................................................A- 1
REVISIONS ....................................................................................................................................................A- 2
SOFTWARE USER REGISTRANTION ........................................................................................................A- 3
Usage Precautions.........................................................................................................................................A- 4
INTRODUCTION............................................................................................................................................A- 5
CONTENTS....................................................................................................................................................A- 5
About Manuals ...............................................................................................................................................A- 7
How to read this manual ................................................................................................................................A- 8
About the generic terms and abbreviations used in this manual..................................................................A- 9
Product Components .....................................................................................................................................A-10
1. OVERVIEW 1-1 to 1-2
1.1 Features .................................................................................................................................................. 1- 1
2. SYSTEM CONFIGURATION AND SPECIFICATIONS 2-1 to 2-2
2.1 Operating Environment........................................................................................................................... 2- 1
2.2 Overall Configuration .............................................................................................................................. 2- 2
3. INSTALLATION AND UNINSTALLATION 3-1 to 3-3
3.1 Installation ............................................................................................................................................... 3- 1
3.2 Uninstallation........................................................................................................................................... 3- 3
4. CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT DATA 4-1 to 4-23
4.1 Converting TEXT Format Data to GX Developer Format Data............................................................. 4- 1
4.1.1 Converting TEXT format data to a list ............................................................................................. 4- 1
4.1.2 Converting TEXT Format Data to Device Comments..................................................................... 4- 7
4.2 Converting CSV Format Data to GX Developer Format Data............................................................... 4-12
4.2.1 Converting CSV format data to a list ............................................................................................... 4-12
4.2.2 Converting CSV Format Data to Device Comments ...................................................................... 4-17
4.3 Handling of conversion errors................................................................................................................. 4-22
5. CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT DATA 5-1 to 5-4
5.1 Converting GX Developer Format Data to Text, CSV Format Data ..................................................... 5- 2
A - 5 A - 5
6. FILE FORMATS 6-1 to 6-10
6.1 About TEXT CSV format files ................................................................................................................. 6- 1
6.2 File formats when the GX Developer import a TEXT, CSV format file ................................................. 6- 3
6.2.1 When a List is import by the GX Developer .................................................................................... 6- 3
6.2.2 When device comments are import by the GX Developer ............................................................. 6- 7
6.3 File Formats When The GX Developer Format Data is Export to a Text, CSV Format File ................ 6- 8
6.3.1 When a List is export to a text, csv format file................................................................................. 6- 8
6.3.2 When device comments are export to a text, csv format file .......................................................... 6-10
APPENDICES App-1 to App-5
Appendix 1. Limitations and Precautions .................................................................................................App- 1
Appendix 2. Conversion Error Message List............................................................................................App- 3
Appendix 3. Converting CADIF Character-string Data ............................................................................App- 5
Appendix 4. Performance Specifications..................................................................................................App- 5
INDEX Index-1 to Index-2
A - 6 A - 6
About Manuals
The following manuals are also related to this product.
In necessary, order them by quoting the details in the tables below.
Related Manuals
Manual Name
GX Developer Version 8 Operating Manual
This manual contains information on creating programs, printing procedures, monitoring procedures, debugging procedures, and other on-line functions using the GX Developer.
(Sold separately)
Manual Number
(Model Code)
SH-080373E
(13JU41)
A - 7 A - 7
How to read this manual
"How to read this manual" lists the sections in this manual by the objective while using the GX Converter. Please read this manual using the contents below as a reference.
(1) When you want to know the features of GX Converter (Section 1.1)
Section 1.1 describes the features of GX Converter.
(2) When you want to know the structure of GX Converter (Chapter 2)
Chapter 2 describes the operating environment and overall configuration of GX
Converter.
(3) When performing Installation and Uninstallation of GX Converter (Chapter 3)
Chapter 3 describes the operating procedures when performing Installation or
Uninstallation of GX Converter.
(4) When converting TEXT, CSV format data to GX Developer format data (Chapter 4)
Chapter 4 describes the operating procedures when converting TEXT, CSV format data to GX Developer format data.
(5) When converting GX Developer format data to TEXT, CSV format data (Chapter 5)
Chapter 5 describes the operating procedures when converting GX Developer format data to TEXT, CSV format data.
(6) When you want to know about file formats (Chapter 6)
Section 6.1 describes the TEXT, CSV format file.
Section 6.2 describes how to write the data when TEXT, CSV format data is
Import by the GX Developer.
Section 6.3 describes the data types used when export GX Developer format data as TEXT, CSV format data.
(7) When you want to know about limitations and precautions for GX Converter
(Appendix 1)
Appendix 1 describes the limitations and precautions when performing
Installation, Uninstallation or various types of conversion.
(8) When you want to know about GX Converter conversion error messages
(Appendix 2)
Appendix 2 describes the error messages generated during data conversion.
(9) When you want to know about CADIF character-string data conversion (Appendix 3)
Appendix 3 describes the conversion of CADIF character-string data.
(10) When you want to know about the performance specifications for the GX
Converter (Appendix 4)
Appendix 4 describes the performance specifications for the GX Converter.
A - 8 A - 8
About the generic terms and abbreviations used in this manual
This manual uses the following generic terms and abbreviations to describe the GX
Converter unless otherwise specified.
Generic term/abbreviation
GX Converter
GX Developer
GX Developer Version n
(SWnD5-GPPW-E) or earlier
GX Developer Version n
(SWnD5-GPPW-E) or later
CADIF character-string data
GX Simulator
Description of generic term/abbreviation
Abbreviation for GX Converter Version 1 (SW0D5C-CNVW-E)
Generic term for GX Developer Version 3 (SW3D5-GPPW-E) or later
When limited to earlier than the major version (n denotes the version number)
When limited to later than the major version (n denotes the version number)
Abbreviation for the character-string data converted by SW1IVD-CADIF.
Generic term for GX Simulator Version 2 (SW2D5-LLT-E) or later
A - 9 A - 9
Product Components
The components of this product are shown below.
Type
SW0D5C-CNVW-E
SW0D5C-CNVW-EA
Product Name
GX Converter Version 1 (1-license product)
End-user softwere license agreement
Software registration Card
License agreement
GX Converter Version 1 (Multiple license product)
End-user softwere license agreement
Software registration Card
License agreement
(CD-ROM)
(CD-ROM)
1: The same number of software registration cards as that of licenses are packed with the product.
Quantity
1
1 n 1
1
1
1
1
1
NOTICES
•
We don't guarantee the commercially-available Windows
R
-based software products that have been introduced in this manual.
•
We hold the copyrights of this software package.
•
No part of this manual may be transcribed or duplicated in any form without prior permission by Mitsubishi Electric Corporation.
•
We have attempted to cover all the revisions of software and hardware, but this manual may not contain the latest revisions.
•
The software of this product requires one license to be purchased per computer.
•
We permit the user to use this software package (including this manual) based on the Software License Agreement.
•
We are not liable for consequences or influences due to this software package
(including this manual).
•
The specifications of this software package and the descriptions in this manual may be altered in future without prior notice.
A - 10 A - 10
1 OVERVIEW
MELSOFT
1. OVERVIEW
This chapter explains the overview of GX Converter and this manual.
This manual describes the GX Converter, a product capable of converting TEXT, CSV format data into List or Device comments so that the GX Developer can handle, and converting List and Device comments into TEXT, CSV format data.
1
1.1 Features
(1) Conversion can be processed as a GX Developer function.
Conversion can be performed without closing the GX Developer because it is an add-on function for the GX Developer.
(2) Data can be converted by file.
Conversions can be performed between commercial software (TEXT, CSV format data) and the GX Developer (List or Device comments) at the file level.
(There is no need for copying and pasting.)
(3) Sequence programs can be created using commercial software.
When a program created using the TEXT,CSV format is converted to a List via
GX Converter, it may be used as an actual sequence program.
(4) Data can be created in any file format.
When creating a List or Device Comments using the TEXT,CSV format, the file format can be created freely.
TEXT editor,
Spreadsheet software
TEXT File
CSV File
GX Converter
Comment
GX Developer
List
1 - 1 1 - 1
1 OVERVIEW
1
MEMO
MELSOFT
1 - 2 1 - 2
2 SYSTEM CONFIGURATION AND SPECIFICATIONS
MELSOFT
2. SYSTEM CONFIGURATION AND SPECIFICATIONS
This chapter explains the operating environment and overall configuration of the GX
Converter.
2.1 Operating Environment
The operating environment of GX Converter is explained.
Item
Installation (Add-in) destination
1
Description
Add-in to GX Developer Version 3 (SW3D5C-GPPW-E or later).
Language 2
Computer main unit
Free space
CPU
Required memory
For installation
For operation
(Virtual memory) 3
Disk drive
Display
Install GX Converter into the English version of GX Developer (SW3D5C-GPPW-E or later).
Personal computer on which Windows R operates.
Refer to the following table "Used operating system and performance required for personal computer".
25MB or more
10MB or more
Operating system
CD-ROM disk drive
800 600 dot or more resolution 4
Microsoft R Windows R 95 Operating System (English version)
Microsoft
Microsoft
Microsoft R
R
R
Windows R 98 Operating System (English version)
Windows
R
Millennium Edition Operating System (English version)
Windows NT R Workstation Operating System Version 4.0 (English version)
Microsoft R Windows R 2000 Professional Operating System (English version)
Microsoft R
Microsoft R
Windows R XP Professional Operating System (English version)
Windows R XP Home Edition Operating System (English version)
1: GX Converter cannot be installed into GX Developer (SW0D5-GPPW-E, SW1D5-GPPW-E, SW2D5-GPPW-E). GX
Converter becomes unusable if the version (SW0D5-GPPW-E, SW1D5-GPPW-E, SW2D5-GPPW-E) of GX Developer
(SW2D5C-GPPW-E or earlier) is reinstalled in the environment where GX Converter has already been installed into GX
Developer (SW3D5C-GPPW-E or later).
2: Install GX Converter into the software package of the same language.
GX Converter (English version) cannot be installed into GX Developer of other than the English version.
3: Free space of at least twice the size of the TEXT, CSV format file that will be read is required in the
Windows
R temporary drive.
4: When Windows R XP Professional or Windows R XP Home Edition is used, Large Fonts are not supported.
2
Used operating system and performance required for personal computer
Operating system
Windows R
Windows R
95
98
Windows R Me
Windows NT R Workstation 4.0
Windows
R
2000 Professional
Performance Required for Personal Computer
CPU Required memory
Pentium
Pentium
Pentium
Pentium
Pentium
R
R
R
R
R
133MHz or more
133MHz or more
150MHz or more
133MHz or more
133MHz or more
32MB or more
32MB or more
32MB or more
32MB or more
64MB or more
Windows R XP Professional
Windows
R
XP Home Edition
"XP compatibility mode" and "Fast User
Switching" are not supported.
Pentium R 300MHz or more
Pentium
R
300MHz or more
128MB or more
128MB or more
2 - 1 2 - 1
2
2 SYSTEM CONFIGURATION AND SPECIFICATIONS
2.2 Overall Configuration
This section explains the overall configuration of the GX Converter.
MELSOFT
GX Converter
Peripheral device
A personal computer with
GX Developer preinstalled
2 - 2 2 - 2
3 INSTALLATION AND UNINSTALLATION
MELSOFT
3. INSTALLATION AND UNINSTALLATION
• When installing multiple products, install the GX Developer first.
• When using Microsoft
R
Windows
R
XP Professional Operating System,
Microsoft
R
Windows
R
XP Home Edition Operating System,
Microsoft
NT
R
R
Windows
R
2000 Professional Operating System or Microsoft
R
Windows
Workstation Operating System Version 4.0, log on as the user who has the administrator attributes.
• Also use the manual for the CD-ROM provided with the component to learn about the procedures for installing and uninstalling.
3
3.1 Installation
(1) Installation procedure
Begin installing
(Screen 1))
1) Start Windows
Explorer, then click
on the drive where the CD-ROM
supplied with the component has
been inserted.
Double-click on "Setup.exe" in the
CD-ROM.
*
2) Enter name and company
(Screen 1)).
3) Register the product ID for the
purchased product (Screen 2)).
(Screen 2))
Running the software package
· Check that the product has been
installed correctly.
Completion
3 - 1 3 - 1
3
3 INSTALLATION AND UNINSTALLATION
MELSOFT
• Screen 3) may be displayed during the installation process to arrange the installation preparations.
If Screen 3) is displayed, execute the specified exe file in accordance with the screen prompts, and then install the product again. If this product is not installed properly at this time, reboot the personal computer.
(Screen 3))
If the right screen appears, execute "\Update\dcom95.exe" on the CD-ROM.
(Screen 4))
If the right screen appears, execute "\Update\Axdist.exe" on the CD-ROM.
(Screen 5))
If the right screen appears, execute "\EnvMEL\Setup.exe" on the CD-ROM.
• The following screen may appear to ensure proper completion of installation.
Follow the screen prompts and reboot the computer.
3 - 2 3 - 2
3 INSTALLATION AND UNINSTALLATION
MELSOFT
3.2 Uninstallation
(1) Uninstallation procedure
Begin uninstalling
(Screen 1))
1) Display the Control Panel by clicking [Start] -
[Settings] - [Control Panel], then select "Add/
Remove Programs." *
1
2) Click on "Install/Uninstall" tab.
After selecting the name of this product, click on
the "Add/Remove" button. (Screen 1)) *
2
Completion
R R
XP Home Edition, select "Add or Remove Programs"
from the Control Panel.
To display the Control Panel, click [Start] - [Control
Panel].
R 2000 Professional, Windows R
R
XP Professional and Windows XP Home Edition,
carry out Uninstall using the following procedure.
(a) Click "Change or Remove Programs."
(b) Click "GX Converter"
(c) Click the Change/Remove button.
R
Screen when using Windows 98.
• If the following screen has appeared during uninstallation, click the "No To All" button.
3 - 3 3 - 3
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4
4. CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
This function converts TEXT,CSV format data to List or Device comments, which are the formats that can be handled by GX Developer.
The following illustrates the operation procedure for converting TEXT,CSV format data to a List or Device comments so that the GX Developer can use.
• Start GX Developer
• Open project
• Start GX Converter
Select Menu
[Import file]
[Import from TEXT, CSV format file]
• • • • • Open the project that contains the data to be
converted or a new project in GX Developer and select
[Import from TEXT, CSV format file].
• Open file
• Set conversion source data
• Set delimiter location
When converting
TEXT data
• Set delimiter
When converting
CSV data
• • • • • See Section 4.1, "Converting TEXT data to GX Developer
format data" for details on the conversion of TEXT files.
See Section 4.2, "Converting CSV data to GX Developer
format data" for details on the conversion of CSV files.
• Set column data
• Set export destination data
• Close GX Converter
dialog box to end GX Converter.
REMARK
See Appendix 3, "Converting CADIF character-string data" for information on reading CADIF character-string data.
4 - 1 4 - 1
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4.1 Converting TEXT Format Data to GX Developer Format Data
This section explains the operation of converting TEXT format data to a List or Device comments, which are the formats the GX Developer can use.
4.1.1 Converting TEXT format data to a list
The following explains the operation of converting TEXT format data to a List, which can be used by the GX Developer.
POINT
• See Section 6.2.1, "When a List is import by the GX Developer" for details on file formats.
• There may be some cases where Instruction, I/O (Device), etc. cannot be converted, depending on the CPU type of the project opened in the GX Developer.
See "GX Developer Operating Manual" for details.
4
(1) Start GX Developer
Start GX Developer
Open project
Start GX Developer and open the project containing the TEXT format data you wish to import.
(2) Start GX Converter
Start GX Converter.
1)
1) Start GX Converter by clicking on
[Project] —
[Import file] —
[Import from TEXT, CSV format file].
(Continued on the next page)
4 - 2 4 - 2
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
Select the TEXT format file you wish to convert to a GX Developer List.
(4) Set conversion source data
1)
Set the format and conversion range of the data to be converted.
2)
Caution
• About characters that cannot be displayed in the Data
Preview area
Characters not displayed will be displayed with " · ".
• When setting conversion row
The program cannot proceed if conversion rows are set
as "Start Import at Row > End Import at Row."
• About tabs
Select "CSV" in step 1) for files whose contents are
separated by tabs.
See Section 6.1, " About TEXT,CSV format files" for
details.
5)
3)
4)
1) Select " TEXT."
2) Select "List."
3) Enter the Start Import at Row.
4) Enter the End Import at Row.
If the number of rows to be converted is not
entered, conversion will take place until the end
of the file is reached.
5) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(Continued on the next page)
4 - 3 4 - 3
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(5) Set delimiter location
1)
Separate the data to be converted into columns.
2)
1) Separate the data in the Data Preview area.
(Can be separated at a maximum of 16 locations.)
• Separating procedure
Click on the location to be separated.
An arrow is displayed in the delimiter location.
• Changing delimiter locations
Drag the arrow to change the delimiter
location.
• Deleting delimiter
Double-click the arrow to clear the delimiter.
2) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(6) Set column data
Set the data types for the columns.
1)
Click !
2)
Caution
• When setting data format
When data format are overlapped, the program cannot
proceed to the next step if the overlapping data format is
other than Instruction, Statement, or Note.
When "Do not Import (Skip)" is selected, conversion will
not take place even if data is present in the column.
1) Set data types in the Data Preview area.
Select a column (the selected column becomes
highlighted in black) by clicking the Data
Preview area of each data column.
Next, select a column data format from
"Column Data Format" in the upper-right area.
To select multiple settings, repeat this
operation.
2) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(Continued on the next page)
4 - 4 4 - 4
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(7) Set export destination data
Set which project data within the GX Developer the converted data is to be export.
1)
2)
3)
4)
Caution
• When entering a data name
If the PLC series for the project is a QnA Series, the data
name must be 8 characters or less. If the PLC series for
the project is A Series,FX Series, or Motion (SCPU), only
the predetermined names such as MAIN and SUB1 can
be used.
See "
GX Developer
Operating Manual" for details.
• When an existing data name is entered or selected
An overwrite verification dialog box is displayed.
Click on the Yes button to discard and overwrite the old
data.
Click on the No button to end
GX Converter
.
• When selecting a conversion method
When a conversion error is generated, the content of the
conversion error will be displayed after "(8) Conversion
proces" , regardless of selecting of the Conversion
type for wrong instruction.
1) Specify a data name for the data to be converted.
Enter or select a data name.
The entered data name is export to the project that is currently open in the GX Developer.
2) Enter a Title for the data to be converted.
3) Select a Conversion type for wrong instruction.
• Do not Import (Skip)
Invalid instructions are disregarded and no
conversion takes place.
• To line statements
Invalid instructions are converted to line
statements.
• To invalid instructions
Invalid instructions are converted as
instruction code errors.
4) When the setting is complete, execute the conversion processing by clicking the Finish button.
(Continued on the next page)
4 - 5 4 - 5
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(8) Conversion proces
This processing converts TEXT format data to a
List and registers it.
When each Cancel button is pressed, the corresponding conversion processing will be aborted.
Caution
• When a Cancel button is clicked
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
No data will be created in the
GX Developer
.
When overwriting, the previous data remains.
Clicking the No button continues the conversion
processing.
(9) Close GX Converter
Conversion error generated
• See Section 4.3,
"Handling of conversion
errors."
Clicking the OK button ends the conversion processing and closes GX Converter.
If a conversion error is displayed, see to Section
4.3, "Handling of conversion errors" for details.
4 - 6 4 - 6
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4.1.2 Converting TEXT Format Data to Device Comments
The following explains the operation of converting TEXT format data to Device comments, which are the formats the GX Developer can use.
POINT
• See Section 6.2.2, "When Device comments are import by the GX Developer" for details on file formats.
• There may be some cases where Instruction, I/O (Device), etc. cannot be converted, depending on the CPU type of the project opened in the GX Developer.
See "GX Developer Operating Manual" for details.
(1) Start GX Developer
Start GX Developer
Open project
Start GX Developer and open the project containing the TEXT format data you wish to import.
(2) Start GX Converter
Start GX Converter.
1)
1) Start GX Converter by clicking on
[Project] —
[Import file] —
[Import from TEXT, CSV format file].
(Continued on the next page)
4 - 7 4 - 7
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(3) Open file
Select the TEXT format file you wish to convert to a GX Developer Device comments.
(4) Set conversion source data
1)
Set the format and conversion range of the data to be converted.
2)
Caution
• About characters that cannot be displayed in the Data
Preview area
Characters not displayed will be displayed with " · ".
• When setting conversion row
The program cannot proceed if conversion rows are set
as "Start Import at Row > End Import at Row."
• About tabs
Select "CSV" in step 1) for files whose contents are
separated by tabs.
See Section 6.1, "About TEXT,CSV format files" for
details.
5)
3)
4)
1) Select "TEXT."
2) Select "Comment."
3) Enter the Start Import at Row.
4) Enter the End Import at Row.
If the number of rows to be converted is not entered, conversion will take place until the end of the file is reached.
5) When the setting is complete, proceed to the next step by clicking the NEXT> button.
(Continued on the next page)
4 - 8 4 - 8
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(5) Set delimiter location
1)
Separate the data to be converted into columns.
2)
1) Separate the data in the Data Preview area.
(Can be separated at a maximum of 16 locations.)
• Separating procedure
Click on the location to be separated.
An arrow is displayed in the delimiter location.
• Changing delimiter locations
Drag the arrow to change the delimiter
location.
• Deleting delimiter
Double-click the arrow to clear the delimiter.
2) When the setting is complete, proceed to the next step by clicking the NEXT> button.
(6) Set column data
Set the data types for the columns.
1)
Click !
2)
Caution
• When setting data format
When data format are overlapped, the program cannot
proceed to the next step if the overlapping data format is
other than Device number.
When "Do not Import (Skip)" is selected, conversion will
not take place even if data is present in the column.
1) Set data types in the Data Preview area.
Select a column (the selected column becomes
highlighted in black) by clicking the Data
Preview area of each data column.
Next, select a column data format from
"Column Data Format" in the upper-right area.
To select multiple settings, repeat this
operation.
2) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(Continued on the next page)
4 - 9 4 - 9
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(7) Set export destination data
Set which project data within the GX Developer the converted data is to be export.
1)
2)
3)
4)
Caution
• When entering a data name
If the PLC series for the project is a QnA Series, the data
name must be 8 characters or less. If the PLC series for
the project is A Series, FX Series, or Motion (SCPU), only
the predetermined names such as MAIN and SUB1 can
be used.
See "
GX Developer
Operating Manual" for details.
• When an existing data name is entered or selected
An overwrite verification dialog box is displayed.
Click on the Yes button to discard and overwrite the
old data.
Click on the No button to end
GX Converter
.
1) Select the data type for the data to be export.
2) Specify a data name for the data to be converted.
Enter or select a data name.
The entered data name is export to the project that is currently open in the GX Developer.
3) Enter a Title for the data to be export.
4) When the setting is complete, execute the conversion processing by clicking the Finish button.
(Continued on the next page)
4 - 10 4 - 10
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(8) Conversion proces
This processing converts TEXT format data to
Device comments and registers them.
When each Cancel button is pressed, the corresponding conversion processing will be aborted.
Caution
• When a Cancel button is clicked during Converting
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
No data will be created in the
GX Developer
.
When overwriting, the previous data remains.
Clicking the No button continues the conversion
processing.
• When a Cancel button is clicked during Registering
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
The data registered until immediately before the
cancellation are created in the
GX Developer
.
When overwriting, the previous data are discarded.
Clicking the No button continues the conversion
processing.
Conversion error generated
• See Section 4.3,
"Handling of conversion
errors."
Clicking the OK button ends the conversion processing and closes GX Converter.
If a conversion error is displayed, see Section 4.3,
"Handling of conversion errors" for details.
4 - 11 4 - 11
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4.2 Converting CSV Format Data to GX Developer Format Data
This section explains the operation of converting CSV format data to a List or Device comments, which are the formats the GX Developer can use.
4.2.1 Converting CSV format data to a list
The following explains the operation of converting CSV format data to a List, which can be used by the GX Developer.
POINT
• See Section 6.2.1, "When a List is import by the GX Developer " for details on file formats.
• There may be some cases where Instruction, I/O (Device), etc. cannot be converted, depending on the CPU type of the project opened in the GX Developer.
See " GX Developer Operating Manual" for details.
(1) Start GX Developer
Start GX Developer
Open project
Start GX Developer and open the project containing the CSV format data you wish to import.
(2) Start GX Converter
Start GX Converter.
1)
1) Start GX Converter by clicking on
[Project] —
[Import file] —
[Import from TEXT, CSV format file].
(Continued on the next page)
4 - 12 4 - 12
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
Select the CSV format file you wish to convert to a
GX Developer List.
(4) Set conversion source data
Set the format and conversion range of the data to be converted.
1)
2)
3)
4)
Caution
• About characters that cannot be displayed in the Data
Preview area
Characters not displayed will be displayed with " · ".
• When setting conversion row
The program cannot proceed if conversion rows are set
as "Start Import at Row > End Import at Row."
• About tabs
Select "CSV" in step 1) for files whose contents are
separated by tabs.
See Section 6.1, "About TEXT,CSV format files" for
details.
5)
1) Select "CSV."
2) Select "List."
3) Enter the Start Import at Row.
4) Enter the End Import at Row.
If the number of rows to be converted is not entered, conversion will take place until the end of the file is reached.
5) When the setting is complete, proceed to the next step by clicking the NEXT> button.
(Continued on the next page)
4 - 13 4 - 13
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(5) Set delimiter location
Separate into columns by setting delimiters.
1)
2)
Caution
• About data created using spreadsheet software
Commas are used as the delimiters in the data created
and edited using spreadsheet software.
3)
1) Select a delimiter for each data. (Multiple
delimiters can be selected.)
• Tab
Select it when using tabs as delimiters.
• Semicolon
Select it when using semicolons as delimiters.
• Comma (default)
Select it when using commas as delimiters.
• Space
Select it when using spaces as delimiters.
• Other
When using a character other than above as
the delimiter, check the checkbox and enter
the character.
2) Verify the separated data in the Data Preview
area.
3) After the setting is complete, click on the
NEXT> button and proceed to the next step.
(6) Set column data
Set the column data format.
1)
Click !
Caution
• When setting data format
When data format are overlapped, the program cannot
proceed to the next step if the overlapping data format is
other than Instruction.
When "Do not Import (Skip)" is selected, conversion will
not take place even if data is present in the column.
2)
1) Set data types in the Data Preview area.
Select a column (the selected column becomes
highlighted in black) by clicking the Data
Preview area of each data column.
Next, select a column data format from
"Column Data Format" in the upper-right area.
To select multiple settings, repeat this
operation.
2) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(Continued on the next page)
4 - 14 4 - 14
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(7) Set export destination data
Set which project data within the GX Developer the converted data is to be export.
1)
2)
3)
4)
Caution
• When entering a data name
If the PLC series for the project is a QnA Series, the data
name must be 8 characters or less. If the PLC series for
the project is A Series, FX Series, or Motion (SCPU), only
the predetermined names such as MAIN and SUB1 can
be used.
See "
GX Developer
Operating Manual" for details.
• When an existing data name is entered or selected
An overwrite verification dialog box is displayed.
Click on the Yes button to discard and overwrite the old
data.
Click on the No button to end
GX Converter
.
• When selecting a conversion method
When a conversion error is generated, the content of the
conversion error will be displayed after "(8) Conversion
proces", regardless of the selecting of Conversion type
for wrong instruction.
1) Specify a data name for the data to be converted.
Enter or select a data name.
The entered data name is export to the project that is currently open in the GX Developer.
2) Enter a Title for the data to be export.
3) Select a Conversion type for wrong instruction.
• Do not Import (Skip)
Invalid instructions are disregarded and no
conversion takes place.
• To line statements
Invalid instructions are converted to line
statements.
• To invalid instructions
Invalid instructions are converted as
instruction code errors.
4) When the setting is complete, execute the conversion processing by clicking the Finish button.
(Continued on the next page)
4 - 15 4 - 15
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
This processing converts CSV format data to a
List and registers it.
When each Cancel button is pressed, the corresponding conversion processing will be aborted.
Caution
• When a Cancel button is clicked
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
No data will be created in the
GX Developer
.
When overwriting, the previous data remains.
Clicking the No button continues the conversion
processing.
Conversion error generated
• See Section 4.3,
"Handling of conversion
errors."
Clicking the OK button ends the conversion processing and closes GX Converter.
If a conversion error is displayed, see Section 4.3,
" Handling of conversion errors" for details.
4 - 16 4 - 16
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4.2.2 Converting CSV Format Data to Device Comments
The following explains the operation of converting CSV format data to Device comments, which are the formats the GX Developer can use.
POINT
• See Section 6.2.2, "When Device comments are import by the GX Developer " for details on file formats.
• There may be some cases where Instruction, I/O (Device), etc. cannot be converted, depending on the CPU type of the project opened in the GX Developer.
See " GX Developer Operating Manual" for details.
(1) Start GX Developer
Start GX Developer
Open project
Start GX Developer and open the project containing the CSV format data you wish to import.
(2) Start GX Converter
Start GX Converter.
1)
1) Start GX Converter by clicking on
[Project] —
[Import file] —
[Import from TEXT, CSV format file].
(Continued on the next page)
4 - 17 4 - 17
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
Select the CSV format file you wish to convert to a
GX Developer Device comments.
(4) Set conversion source data
1)
Set the format and conversion range of the data to be converted.
2)
3)
4)
Caution
• About characters that cannot be displayed in the Data
Preview area
Characters not displayed will be displayed with " · ".
• When setting conversion row
The program cannot proceed if conversion rows are
set as "Start Import at Row > End Import at Row."
• About tabs
Select "CSV" in step 1) for files whose contents are
separated by tabs.
See Section 6.1, " About TEXT,CSV format files" for
details.
5)
1) Select "CSV."
2) Select "Comment."
3) Enter the Start Import at Row.
4) Enter the End Import at Row.
If the number of rows to be converted is not entered, conversion will take place until the end of the file is reached.
5) When the setting is complete, proceed to the next step by clicking the NEXT> button.
(Continued on the next page)
4 - 18 4 - 18
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
Separate into columns by setting delimiters.
1)
2)
Caution
• About data created using spreadsheet software
Commas are used as the delimiters in the data created
and edited using spreadsheet software.
3)
1) Select a delimiter for each data. (Multiple
delimiters can be selected.)
• Tab
Select it when using tabs as delimiters.
• Semicolon
Select it when using semicolons as delimiters.
• Comma (default)
Select it when using commas as delimiters.
• Space
Select it when using spaces as delimiters.
• Other
When using a character other than above as
the delimiter, check the checkbox and enter
the character.
2) Verify the separated data in the Data Preview
area.
3) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(6) Set column data
Set the column data format.
1)
Click !
Caution
• When setting data format
When data format are overlapped, the program cannot
proceed to the next step if the overlapping data format
is other than Device number.
When "Do not Import (Skip)" is selected, conversion
will not take place even if data is present in the column.
2)
1) Set data types in the Data Preview area.
Select a column (the selected column becomes
highlighted in black) by clicking the Data
Preview area of each data column.
Next, select a column data format from
"Column Data Format" in the upper-right area.
To select multiple settings, repeat this
operation.
2) When the setting is complete, proceed to the
next step by clicking the NEXT> button.
(Continued on the next page)
4 - 19 4 - 19
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(7) Set export destination data
Set which project data within the GX Developer the converted data is to be export.
1)
2)
3)
Caution
• When entering a data name
If the PLC series for the project is a QnA Series, the data
name must be 8 characters or less. If the PLC series for
the project is A Series, FX Series, or Motion (SCPU), only
the predetermined names such as MAIN and SUB1 can
be used.
See "
GX Developer
Operating Manual" for details.
• When an existing data name is entered or selected
An overwrite verification dialog box is displayed.
Click on the Yes button to discard and overwrite the old
data.
Click on the No button to end
GX Converter
.
4)
1) Select the data type for the data to be export.
2) Specify a data name for the data to be converted.
Enter or select a data name.
The entered data name is export to the project that is currently open in the GX Developer.
3) Enter a Title for the data to be export.
4) When the setting is complete, execute the conversion processing by clicking the Finish button.
(Continued on the next page)
4 - 20 4 - 20
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
Caution
• When a Cancel button is clicked during Converting
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
No data will be created in the
GX Developer
.
When overwriting, the previous data remains.
Clicking the No button continues the conversion
processing.
• When a Cancel button is clicked during Registering
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
The data registered until immediately before the
cancellation are created in the
GX Developer
.
When overwriting, the previous data are discarded.
Clicking the No button continues the conversion
processing.
This processing converts CSV format data to
Device comments and registers them.
When each Cancel button is pressed, the corresponding conversion processing will be aborted.
Conversion error generated
• See Section 4.3,
"Handling of conversion
errors."
Clicking the OK button ends the conversion processing and closes GX Converter.
If a conversion error is displayed, see Section 4.3,
"Handling of conversion errors" for details.
4 - 21 4 - 21
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
4.3 Handling of conversion errors
This section explains the corrective actions when a conversion error is generated when data in TEXT, CSV format is import by the GX Developer.
(1) Conversion error display
Verify or save the conversion error.
First perform the following operations, then correct the conversion error.
3)
1) 2)
Caution
• About the error line for an Instruction or I/O (Device)
error
If an I/O (Device) error occurs when multiple I/O (Device)
exist for a single instruction, the line number for the
Instruction will be displayed as the error line number.
1) To save the conversion errors
Save the conversion error contents to a
specified file by clicking on the Save button.
Up to 100 occurrences (lines) of errors can be
saved.
2) To discard conversion errors
Click the OK button to end the conversion
processing and then close the GX Converter.
3) Up to 100 occurrences (lines) of conversion
errors will be displayed.
When the number of conversion errors
exceeds 100 occurrences (lines), the message
"Convert error counter is over 100. Cancelled
over 100 errors" will be displayed on line
number 101.
See Appendix 2, "Conversion error message
List" for detailed explanations of error
messages.
(Continued on the next page)
Ends the conversion processing and closes the GX Converter.
4 - 22 4 - 22
4 CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT
DATA
MELSOFT
(From the previous page)
(2) Save conversion errors
Save the conversion error contents to a file.
The conversion error contents can be saved to a file with the desired file format (extension).
4 - 23 4 - 23
5 CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT
DATA
MELSOFT
5. CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT
DATA
List and Device comments created by GX Developer can be converted to TEXT, CSV format data, which can be read by other commercial software.
This section describes the operation procedure for converting List and Device comments created by GX Developer to TEXT, CSV format data, which can be read by other commercial software.
• Start GX Developer
• Open a project
• Start GX Converter
Select Menu
[Export file]
[Export to TEXT, CSV format file]
• Set conversion source data
• Set export destination file
• Close GX Converter
• • • • • Open the project that contains the data you wish to
convert in GX Developer, then select [Export to
TEXT, CSV format file].
dialog box to end GX Converter.
5
5 - 1 5 - 1
5 CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT
DATA
MELSOFT
5.1 Converting GX Developer Format Data to Text, CSV Format Data
This section explains the operation procedures for converting List and Device comments to TEXT, CSV format data, which can be read by other commercial software.
POINT
See Section 6.3, "File formats when the GX Developer format data is export to a
TEXT, CSV format file" for details on file formats.
(1) Start GX Developer
Start GX Developer
Open project
Start GX Developer and open the project that contains the List or Device comments you wish to convert to TEXT, CSV format data.
5
(2) Start GX Converter
1)
Start GX Converter.
1) Start GX Converter by clicking on
[Project] —
[Export file] —
[Export to TEXT, CSV format file].
(Continued on the next page)
5 - 2 5 - 2
5 CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT
DATA
MELSOFT
(From the previous page)
(3) Set conversion source data
1)
2)
3)
Perform settings for the data to be converted.
1) Select the data type for the data to be converted.
2) Select the name of the data to be converted.
Select from the data within the project that is currently open.
3) Select the file format after the conversion.
4) When the setting is complete, proceed to the next step by clicking the Finish button.
4)
Data selection by conversion format
List
Device comment
Convert to TEXT format
Set 1) to "Program."
Select the data name 2).
Set 3) to " TEXT file."
Set 1) to "Common comment" or "Program comment."
Select the data name 2).
Set 3) to " TEXT file."
Convert to CSV format
Set 1) to "Program."
Select the data name 2).
Set 3) to "CSV file."
Set 1) to "Common comment" or "Program comment."
Select the data name 2).
Set 3) to "CSV file."
(4) Select export destination file
Enter or select the filename in which to export the converted data.
(Continued on the next page)
5 - 3 5 - 3
5 CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT
DATA
MELSOFT
(From the previous page)
Read the List or Device comments and convert to
TEXT, CSV format data.
When each Cancel button is pressed, the corresponding conversion processing will be aborted.
Caution
• When a Cancel button is clicked
A cancel verification dialog box is displayed.
Clicking the Yes button stops the conversion
processing.
No data will be created in the
GX Developer
.
When overwriting, the previous data remains.
Clicking the No button continues the conversion
processing.
Clicking the OK button ends the conversion processing and closes GX Converter.
5 - 4 5 - 4
6 FILE FORMATS
MELSOFT
6. FILE FORMATS
This chapter explains the formats of TEXT, CSV format file, which can be used for GX
Converter conversion.
6.1 About TEXT CSV format files
(1) TEXT format files (delimited by spaces)
This is a file format in which data are separated by spaces.
(a) Necessary commercial software
Use a TEXT editor to create or edit List or Device comments.
(b) About the use of tabs
Do not use tabs in TEXT format files.
The GX Converter recognizes data which are separated by tabs as CSV format data.
In the CSV format, a single tab is recognized as a delimiter, so caution is necessary.
When reading data separated by tabs using GX Developer, perform conversion by selecting " TEXT format" for "Set conversion source data."
(2) CSV format files (delimited by commas)
This is a file format in which data are separated by commas.
The GX Converter supports conversion of data separated by delimiters other than commas.
(a) Necessary commercial software
List and Device comments can be created and edited using a spreadsheet.
Alternatively, a TEXT editor may be used.
(b) About commas within data
1) When spreadsheet software is used
Commas may be used within strings such as Statement and Comment.
2) When a TEXT editor is used
Insert double quotations before and after the string in which commas are
used, when import the string to GX Developer.
When the GX Developer export strings that include commas, it will insert double quotations before and after the strings.
(c) About double quotations
The GX Converter recognizes and converts string data as shown below:
CSV file
(within file)
AB
"A,B"
""AB""
"""AB""C"""
GX Developer
(Statement, Comment, etc.)
AB
A,B
"AB"
"AB"C"
6
6 - 1 6 - 1
6
6 FILE FORMATS
MELSOFT
CAUTION
About double quotations in CSV format
There may be some cases in which strings in CSV files created using GX Converter are not correctly recognized or converted by some spreadsheet products available on the market.
When this happens, perform necessary actions by referring to the manual of the spreadsheet software.
Or, this problem can be resolved by opening the CSV file using a TEXT editor and adding or removing double quotations as necessary.
POINT
(1) When the TEXT, CSV format file is being import by GX Developer
• Using the same file formats for import a TEXT, CSV format file using GX
Developer and export to TEXT, CSV format file will make the subsequent operations easier.
• When creating a List using commercial software, the Step number need not
be input, since the GX Developer adds new Step number each time is r import data.
(2) When export a List or Device comments to a TEXT, CSV format file
• The file format cannot be changed at this time.
Change the file format using a commercial software package after the data
export to the TEXT, CSV format file has been completed.
6 - 2 6 - 2
6 FILE FORMATS
MELSOFT
6.2 File formats when the GX Developer import a TEXT, CSV format file
This section explains the file formats used when the GX Developer import a TEXT,
CSV format file.
POINT
GX Converter recognizes up to 17 columns of data and will not recognize data in the 18th column and beyond.
Therefore, when creating data using a TEXT editor or spreadsheet, create it using
17 columns or less.
GX Converter recognizes up to 524288 lines.
6.2.1 When a List is import by the GX Developer
The following explains how to describe each column data format.
Column data format
Step number
Description
(1) No description necessary
(Automatically added when performing conversion to GX Developer format.)
(1) Describe Statement strings only.
• Describe only the Statement; e.g. "Master Station Initialization setting".
A conversion error will occur if a semicolon (;) is inserted before a Statement string.
Describe a Line statement only.
Line statement
(2) Up to 64 characters can be used.
(3) When the CPU type of the GX Developer project is A Series, FX Series or Motion (SCPU)
• All descriptions become Separate statement.
A conversion error will occur if a " * " is inserted before a Statement string.
(4) When the CPU type of the GX Developer project is QnA Series
• Enter an " * " in front of a Statement string to make it a Separate statement; e.g. "Master
Station Initialization setting".
The " * " in front of strings that denotes a Separate statement is not counted as the number of
characters.
(5) If there is a mixture of Line statement, P/I statement and Note in the same line, a conversion error will occur.
6 - 3 6 - 3
6 FILE FORMATS
MELSOFT
Column data format Description
(1) Describe Instruction.
• Conversion cannot be performed if data to be the Instruction does not exist. Do not omit
Instruction.
Describe Instruction only in the same column.
Instruction
(CSV format)
(2) Instruction and I/O (Device) can be described in the same column.
(When performing conversion, set the column data format to "Instruction" in the "Set column data.")
Describe Instruction and I/O (Device) separated by a space.
(1) Describe Instruction, Statement (Line, P/I) and Note in the same column.
• Conversion cannot be performed if data to be the instruction does not exist. Do not omit
Instruction.
(Description as shown in (2) in the Instruction section above is not allowed.)
• Insert " ; " for Line statement, " [ ] " for P/I statement, and " < > " for Note in before each data or
before and after each data (to identify each data).
Instruction,
Statement (Line, P/I),
Note
(Text format)
Describe Instruction, Statement (Line, P/I), and Note in the same column.
If the string for the Statement (Line, P/I) or Note is long, describe the part that includes the Instruction column and I/O (Device) column.
(2) Number of characters allowed for description (" ; ", " [ ] " and " < > " are excluded from the number of characters used.)
• Up to 64 characters may be used for a Line statement.
• Up to 64 characters may be used for a P/I statement.
• Up to 32 characters may be used for a Note.
(3) When the CPU type of the GX Developer project is A Series, FX Series or Motion (SCPU)
• All descriptions become Separate statement (Line, P/I) or Separate note.
A conversion error will occur if a " * " is inserted before a Statement (Line, P/I) string or Note
string.
(4) When the CPU type of the GX Developer project is QnA Series
• Enter an " * " in front of each string to make it a Separate statement (Line, P/I) or Separate note.
The " * " in front of strings that denotes a Separate statement (Line, P/I) or Separate note is not
counted as the number of characters.
6 - 4 6 - 4
6 FILE FORMATS
MELSOFT
Column data format
(1) Describe I/O (Device) only.
Description
One Instruction
I/O (Device)
If multiple I/O (Device) exist for a single instruction, leave the next Instruction area blank to denote the I/O (Device).
Describe a I/O(Device) only.
(2) Multiple I/O (Device) can be described in the same line.
I/O (Device) are separated by spaces on the same line, same column.
(3) I/O (Device) can be described in the Instruction column.
• See (2) in the description for Instruction shown above.
(1) Describe P/I statement strings only.
• Describe P/I statement only; e.g. "Switch to bank 2."
Describe only P/I statement using carriage returns.
P/I statement
(2) Up to 64 characters can be used.
(3) When the CPU type of the GX Developer project is A Series, FX Series or Motion (SCPU)
• All descriptions become Separate P/I statements.
A conversion error will occur if a " * " is inserted before a Statement string.
(4) When the CPU type of the GX Developer project is QnA Series
• Insert an " * " in front of each string to make it a Separate P/I statement; e.g. "*Switch to bank
2." The " * " in front of strings that denotes a Separate P/I statement is not counted as the
number of characters.
(5) About P/I statement errors
If there is no corresponding Instruction in the previous line of the P/I statement, a conversion error will occur.
Also, if the Conversion type for wrong instruction is set to "To invalid instructions" in the "Set export destination data", they will not be converted to invalid instructions.
(6) If there is a mixture of Line statement, P/I statement and Note in the same line, a conversion error will occur.
6 - 5 6 - 5
6 FILE FORMATS
MELSOFT
Column data format Description
(1) Describe Note strings only.
• Describe Note only; e.g. "Send Buffer size setting."
Describe only Note using carriage returns.
Note
(2) Up to 32 characters can be used.
(3) When the CPU type of the GX Developer project is an A Series, FX Series or Motion (SCPU)
• All descriptions become Separate note.
A conversion error will occur if a " * " is inserted before a Note string.
(4) When the CPU type of the GX Developer project is a QnA Series
• Insert an " * " in front of each string to make it a Separate note; e.g. "*Send Buffer size setting."
The " * " in front of strings that denotes a Separate note is not counted as the number of
characters.
(5) About Note errors
If there is no corresponding Instruction in the previous line of the Note, a conversion error will occur.
Also, if the Conversion type for wrong instruction is set to "To invalid in striation" in the " Set export destination data ", they will not be converted to invalid instruction.
(6) If there is a mixture of Line statement, P/I statements and Note in the same line, a conversion error will occur.
6 - 6 6 - 6
6 FILE FORMATS
6.2.2 When device comments are import by the GX Developer
The following explains how to describe each column data format.
MELSOFT
Describe a Device number, Label and Comment in the same line.
Column with
Device number only
Column with
Label only
Column with
Comment only
Column data format
Device number
Comment
Label
Description
(1) Describe Device number.
Conversion cannot be performed if a Device number is not listed. Always enter this field.
(1) Describe Comment.
•
If the Device number area is left blank or invalid device is input, the line will not be registered.
(2) Up to 32 characters can be entered.
(1) Describe Labels.
•
If the Device number area is left blank or invalid device is input, the line will not be registered.
(2) Up to 8 characters can be entered.
CAUTION
Always enter a Device number.
Use one of the following combinations:
1) Device number, Label, Comment
2) Device number, Comment
3) Device number, Label
6 - 7 6 - 7
6 FILE FORMATS
MELSOFT
6.3 File Formats When The GX Developer Format Data is Export to a Text, CSV Format File
This section explains the file formats used when the GX Developer data is export to a
TEXT, CSV format file.
6.3.1 When a List is export to a text, csv format file
POINT
If the CPU type of the GX Developer project is A Series, FX Series or Motion
(SCPU), a
" * " is displayed for Statement (Line, P/I) and Note in the GX Developer. However, when the data is export to a TEXT, CSV format file, the " * " is eliminated.
(1) TEXT format file (delimited by spaces)
A List is export to a TEXT format file using the format shown below:
Line statement
If the string is long, the part including the Instruction column and I/O (Device) column will be export.
Note is export after a carriage return
If the string is long, the part including the Instruction column and I/O (Device) column will be export.
P/I statement is export after a carriage return
If the string is long, the part including the Instruction column and I/O (Device) column will be export.
1) 2)
Export locations of data types for each line
1) 2) 3)
Step number, Instruction, I/O (Device)
3)
REMARK
For Line statement, P/I statements and Note, " ; ", " [ ] " or " < > " is inserted before each string or before and after each string.
They are export in the Instruction column 2).
6 - 8 6 - 8
6 FILE FORMATS
(2) CSV format file (delimited by commas)
A List is export to a CSV format file using the format shown below:
Line Statements
MELSOFT
Note is export after a carriage return
P/I statement is export after a carriage return
1)
2)
3) 4) 5) 6) 7)
Export locations of data types for each line
1) 2) 3) 4) 5) 6) 7) 8) 9)
Step number, Line statement, Instruction, I/O (Device), Blank, P/I statement, Note, Blank, Blank
8) 9)
6 - 9 6 - 9
6 FILE FORMATS
MELSOFT
6.3.2 When device comments are export to a text, csv format file
(1) TEXT format file (delimited by spaces)
Device comments are export to a TEXT format file using the format shown below:
A name for column data format will be added and export.
The Device number, Label and
Comment are export in this order in the same line.
1) 2) 3)
4)
Export locations of data types for each line
1) 2) 3) 4)
Device number (16 characters), Label (8 characters), Blank (8 spaces), Comment (32 characters)
(2) CSV format file (delimited by commas)
Device comments are export to a CSV format file using the format shown below:
A name for column data format will be added and export.
The Device number, Label and Comment are export in this order in the same line.
1)
2)
3)
Export locations of data types for each line
1) 2) 3) 4)
Device number, Label, Comment
6 - 10 6 - 10
APPENDICES
MELSOFT
APPENDICES
Appendix 1. Limitations and Precautions
(1) The following explains the limitations and precautions when import
TEXT, CSV format data to the GX Developer.
Item
While GX Converter is running
CPU type
Data name
Description
Conversion cannot be performed during monitoring using GX Developer.
Conversion cannot be performed while GX Simulator is running in GX Developer.
Conversion cannot be performed when the GX Converter is running without any open project.
When the GX Developer import TEXT, CSV format data, there may be some cases in which
Instruction and I/O (Device) cannot be converted, depending on the CPU type of the project opened in GX Developer.
See "GX Developer Operating Manual" for details.
There is a limitation in data names when the PLC type of the GX Developer project is A Series,
FX Series, or Motion (SCPU).
See "GX Developer Operating Manual" for details.
When converting a List, the data type of the Instruction must be present within the conversion data. Otherwise, conversion cannot be performed.
Column data format
When converting Device comments, the data type of the Device number must be present within the conversion data. Otherwise, conversion cannot be performed.
In addition, describe Device number and either Comment or Label.
Device comments
Conversion row setting
Data Preview area
To save the conversion processing time, describe the Device number in ascending order within the TEXT, CSV format data.
Conversion is also possible when they are not in the ascending order. When Device numbers are entered randomly, it takes longer to read Device comments compared to when they are entered in ascending order.
The input range for Start import at row and End import at row is 1 to 524288.
The default End import at row is blank. When the End import at row is blank, conversion is performed up to the last row.
When CSV format is specified, the data for the 18th column and beyond will be displayed as " , " in the Data Preview area.
APP
APP - 1 APP - 1
APP
APPENDICES
MELSOFT
(2) The following explains the limitations and precautions when export
GX Developer format data to TEXT, CSV format data.
Item
While GX Converter is running
Delimiter
Description
Conversion is possible even during monitoring using the GX Developer.
Conversion is possible even while GX Simulator is running in GX Developer.
Conversion cannot be performed when GX Converter is running without any open project.
The delimiter is a comma when export using TEXT format, and a space when export using CSV format.
APP - 2 APP - 2
APPENDICES
MELSOFT
Appendix 2. Conversion Error Message List
The following explains conversion error messages when the GX Developer is import
TEXT, CSV format data.
While converting a List
Message
The specified data cannot be created.
The program capacity has been exceeded.
The instruction or device is incorrect. (nth Line)
The device is incorrect. (nth Line)
The device number exceeds the usable range.
(nth Line)
A Statements should be 64 characters or less.
(nth Line)
A Note should be 32 characters or less. (nth Line)
Corrective action
Verify the CPU type and parameter settings.
<Cause>
• The program capacity was not set for the specified program
name.
• An addition was attempted exceeding the maximum number of
programs.
Verify the data being converted.
(The converted data is stored while the capacity allows.)
Correct the data being converted and retry.
(When an Instruction uses multiple lines, the line number within the parentheses indicates the first line.)
Correct the data being converted and retry.
(When an Instruction uses multiple lines, the line number within the parentheses indicates the first line.)
<Cause>
• A Device that cannot be used is specified.
• There is an error in the index qualification or digit specification.
• There is an error in the setting for a special function module
device or link direct device.
Correct the data being converted and retry.
(When an Instruction uses multiple lines, the line number within the parentheses indicates the first line.)
Verify the position in which the number of characters has been exceeded.
(Characters up to the 64th character have been recorded.)
Verify the position in which the number of characters has been exceeded.
(Characters up to the 32nd character have been recorded.)
A Comment should be less than 16 or 32 characters.
(nth Line)
Verify the position in which the number of characters has been exceeded.
(Characters up to the 32nd (16th) character have been recorded.
The maximum number of allowable characters will differ depending on the option information in the GX Developer.)
Statement or note cannot be converted. (nth Line)
Separate statement or note cannot be converted.
(nth Line)
Correct the data being converted and retry.
If the header character is an " * ", change it to " ** " and retry.
Convert error counter is over 100. Cancelled over 100 errors.
Correct the conversion errors and retry.
APP - 3 APP - 3
APPENDICES
MELSOFT
While converting Device comments
Message
The device comment already exists. (nth Line)
The device is incorrect. (nth Line)
Comments should be less than 16 or 32 characters.
(nth Line)
Labels should be 8 characters or less. (nth Line)
Convert error counter is over 100.
Cancelled over 100 errors.
Corrective action
Correct the duplicate comments and retry.
(The last Device will be valid.)
Correct the invalid Device and retry.
Verify the position in which the number of characters has been exceeded.
(Characters up to the 32nd (16th) character have been recorded.
The maximum number of allowable characters will differ depending on the option information in the GX Developer.)
Verify the position in which the number of characters has been exceeded.
(Characters up to the 8th character have been recorded.)
Correct the conversion errors and retry.
APP - 4 APP - 4
APPENDICES
MELSOFT
Appendix 3. Converting CADIF Character-string Data
This section explains the operation to import the character-string data file that has been converted via SW1IVD-CADIF, to the GX Developer.
(1) When converting a List
Convert a List using TEXT format while taking care of the following settings:
• Separate between the number column and Instruction column in "Set delimiter
location."
• In "Set column data," set the first column to "Do not Import (Skip)" and the
second column to "Instruction."
(2) When converting Device comments
Convert Device comments using CSV format while taking care of the following settings:
• Decrease the End import at row by 1 using the spin button in the "Set
conversion source data."
• Set " ; " (semicolon) as the column delimiter in "Set delimiter location."
• In "Set column data," set the first column to "Device number" and the second
column to "Comment."
Appendix 4. Performance Specifications
The following explains the performance specifications for GX Converter.
Conversion element Conversion time
TEXT fomat data to GX Developer fomat data
CSV fomat data to GX Developer fomat data
GX Developer fomat data to TEXT d fomat ata
GX Developer fomat data to CSV fomat data
List
Device comments
List
Device comments
List
Device comments
List
Device comments
5 seconds
5 seconds
5 seconds
5 seconds
The computer used for the measurements above
CPU: Pentium R 133 MHz, RAM: 32 MB, Free hard disk space: More than 50 MB,OS: Windows R 95
Conversion data List : 1001 steps (LD X0 OUT M0 x 500 times, END)
Device comments : 1000 Device equivalent
(Comment 32 characters, Label 8 characters)
APP - 5 APP - 5
INDEX
Ind
[C]
Commas (within strings) ................................. 6-1
Comment (how to describe the data) ............. 6-7
Conversion
CSV data (Device comments) to GX Developer data................................ 4-17
CSV data (List) to GX Developer data...... 4-12
GX Developer data (Device comments)
To TEXT data .............................................. 5-2
GX Developer data (List) to TEXT data...... 5-2
GX Developer data (Device comments)
To CSV data ................................................ 5-2
GX Developer data (List) to CSV data........ 5-2
TEXT data (Device comments)
To GX Developer data................................. 4-7
TEXT data (List) to GX Developer data...... 4-2
Conversion error message List
Device comments................................... APP-4
List........................................................... APP-3
Converting CADIF character-string data ... APP-5
Converting CSV data to GX Developer data
Device comments...................................... 4-17
File format (Device comments) ................... 6-7
File format (List)........................................... 6-3
List.............................................................. 4-12
Converting GX Developer data to CSV data
Device comments........................................ 5-2
File format (Device comments) ................ 6-10
File format (List)........................................... 6-9
List................................................................ 5-2
Converting GX Developer data to TEXT data
Device comments........................................ 5-2
File format (Device comments) ................. 6-10
File format (List)........................................... 6-8
List................................................................ 5-2
Converting TEXT data to GX Developer data
Device comments........................................ 5-2
File format (Device comments) .................. 6-7
File format (List)........................................... 6-3
List................................................................ 4-2
CSV files .......................................................... 6-1
[D]
Double quotations (within strings) ...................6-1
[F]
Features ...........................................................1-1
File
CSV file.........................................................6-1
TEXT file.......................................................6-1
File formats when the GX Developer data is converted to a TEXT, CSV format file
Device comments(SCV) ............................6-10
Device comments(TEXT) ..........................6-10
List(SCV) ......................................................6-9
List(TEXT) ....................................................6-8
[H]
Handling of conversion errors .......................4-22
How to describe the data (reading to GX Developer)
Comment......................................................6-7
Device...........................................................6-7
Instruction (CSV)..........................................6-4
Instruction, Statement, Note (TEXT) ...........6-4
I/O (Device) ..................................................6-5
Label .............................................................6-7
Line statement (how to describe the data) ..6-3
Note ..............................................................6-6
P/I statement ................................................6-5
Step number.................................................6-3
[ I ]
I/O (Device) (how to describe the data) ..........6-5
Installing the GX Converter..........................3-1
Instruction
Instruction
(how to describe the data when CSV).........6-4
Instruction, Statement, Note
(how to describe the data when TEXT).......6-4
Index - 1 Index - 1
[L]
Label ................................................................ 6-7
Limitations................................................... APP-1
Line statement (how to describe the data) ..... 6-3
[N]
Note (how to describe the data)...................... 6-6
[O]
Operating environment.................................... 2-1
Overall configuration ....................................... 2-1
Overview.......................................................... 1-1
[P]
P/I statement (how to describe the data)........ 6-5
Performance specifications........................ APP-5
Precautions................................................. APP-1
[S]
Statement
Line statement (how to describe the data) 6-3
P/I statement (how to describe the data).... 6-5
Step number (how to describe the data) ........ 6-3
[T]
Tab (delimiter) ................................................. 6-1
TEXT files ........................................................ 6-1
[U]
Uninstallation
Uninstalling the GX Converter .................... 3-3
Index - 2 Index - 2
Ind
Microsoft, Windows, Windows NT are registered trademarks of Microsoft Corporation in the United States and other countries.
Pentium is a registered trademark of Intel Corporation in the United States and other countries.
Other company and product names herein are either trademarks or registered trademarks of their respective owners.
SPREAD
Copyright (C) 1996 Farpoint Technologies, Inc.
MITSUBISHI ELECTRIC
HEADQUARTERS
EUROPE B.V.
Gothaer Straße 8
D-40880 Ratingen
Phone: +49 (0) 21 02 / 486-0
EUROPE
Fax: +49 (0) 21 02 / 4 86-11 20 e mail: [email protected]
FRANCE
EUROPE B.V.
25, Boulevard des Bouvets
F-92741 Nanterre Cedex
Phone: +33 1 55 68 55 68
EUROPE B.V.
Travellers Lane
GB-Hatfield Herts. AL10 8 XB
Phone: +44 (0) 1707 / 27 61 00
Fax: +44 (0) 1707 / 27 86 95
MITSUBISHI ELECTRIC
EUROPE B.V.
Via Paracelso 12
I-20041 Agrate Brianza (MI)
UK
ITALY
Fax: +39 039 6053 312 e mail: [email protected]
MITSUBISHI ELECTRIC
EUROPE B.V.
Carretera de Rubí 76-80
E-08190 Sant Cugat del Vallés
SPAIN
Fax: +34 9 3 / 589 2948 e mail: [email protected]
MITSUBISHI ELECTRIC
CORPORATION
JAPAN
8-12,1 chome, Harumi Chuo-Ku
Tokyo 104-6212
Phone: +81 3 6221 6060
Fax: +81 3 6221 6075
MITSUBISHI ELECTRIC
AUTOMATION
Vernon Hills, IL 60061
Fax: +1 847 / 478 22 83
USA
EUROPEAN REPRESENTATIVES
Wiener Straße 89
A-2500 Baden
Fax: +43 (0) 2252 / 488 60 e mail: [email protected]
AUSTRIA
BELARUS
BY-220030 Minsk
Phone: +375 (0) 17 / 22 75 704
Fax: +375 (0) 17 / 22 76 669 e mail: [email protected]
Getronics b.v.
Control Systems
B-1731 Asse-Zellik
BELGIUM
Fax: +32 (0) 2 / 467 17 45 e mail: [email protected]
BULGARIA
BG-1756 Sofia
Phone: +359 (0) 2 / 97 44 05 8
Fax: +359 (0) 2 / 97 44 06 1 e mail: —
INEA CR d.o.o.
Drvinje 63
CROATIA
Phone: +385 (0) 1 / 36 67 140 e mail: —
CZECHIA
Control Systems s.r.o.
Nemocnicni 12
CZ-702 00 Ostrava 2
Phone: +420 59 / 6152 111
EUROPEAN REPRESENTATIVES
EUROPE B.V. – Irish Branch
Westgate Business Park
IRL-Dublin 24
Phone: +353 (0) 1 / 419 88 00
IRELAND
Fax: +353 (0) 1 / 419 88 90 e mail: [email protected]
LATVIA
Lienes iela 28
LV-1009 Riga
Phone: +371 784 / 22 80
Fax: +371 784 / 22 81 e mail: [email protected]
UAB UTU POWEL
Savanoriu pr. 187
LT-2053 Vilnius
Phone: +370 (0) 52323-101
Fax: +370 (0) 52322-980 e mail: [email protected]
LITHUANIA
MOLDOVA, REPUBLIC OF
MD-2061 Chisinau
Phone: +373 (0)2 / 562 263
Fax: +373 (0)2 / 562 263 e mail: [email protected]
Getronics b.v.
Control Systems
Donauweg 2 B
NL-1043 AJ Amsterdam
NETHERLANDS
Phone: +31 (0) 20 / 587 67 00
Fax: +31 (0) 20 / 587 68 39 e mail: [email protected]
Beijer Electronics AS
Teglverksveien 1
N-3002 Drammen
Phone: +47 (0) 32 / 24 30 00
NORWAY
EUROPEAN REPRESENTATIVES
Darülaceze Cad. No. 43 KAT: 2
TURKEY
TR-80270 Okmeydani-Istanbul
Fax: +90 (0) 212 / 320 1649 e mail: [email protected]
UKRAINE
UA-02002 Kiev
Phone: +380 (0) 44 / 238-83-16
Fax: +380 (0) 44 / 238-83-17 e mail: [email protected]
AFRICAN REPRESENTATIVE
Private Bag 2016
ZA-1600 Isando
Fax: +27 (0) 11/ 392 2354 e mail: [email protected]
SOUTH AFRICA
MIDDLE EAST REPRESENTATIVE
Box 6272
IL-42160 Netanya
ISRAEL
Phone: +972 (0) 9 / 863 08 91 e mail: [email protected]
EURASIAN REPRESENTATIVE
AVTOMATIKA SEVER
Krapivnij Per. 5, Of. 402
Phone: +7 812 / 1183 238
RUSSIA
louis poulsen industri & automation
DK-2670 Greve
Phone: +45 (0) 43 / 95 95 95
Fax: +45 (0) 43 / 95 95 91 e mail: [email protected]
UTU Elektrotehnika AS
Pärnu mnt.160i
EE-11317 Tallinn
Phone: +372 (0) 6 / 51 72 80
DENMARK
ESTONIA
MPL Technology Sp. z o.o.
POLAND
Phone: +48 (0) 12 / 632 28 85
Fax: +48 (0) 12 / 632 47 82 e mail: [email protected]
Sirius Trading & Services srl
ROMANIA
Bd. Lacul Tei nr. 1 B
RO-72301 Bucuresti 2
Phone: +40 (0) 21 / 201 7147
Fax: +40 (0) 21 / 201 7148 e mail: [email protected]
ACP Autocomp a.s.
Chalupkova 7
SLOVAKIA
SK-81109 Bratislava
Phone: +421 (02) / 5292-22 54, 55
Beijer Electronics OY
Ansatie 6a
FINLAND
Phone: +358 (0) 9 / 886 77 500 e mail: [email protected]
FINLAND
Teljänkatu 8 A 3
FIN-28130 Pori
Phone: +358 (0) 2 / 522 3300 e mail: —
GREECE
5, Mavrogenous Str.
GR-18542 Piraeus
Fax: +302 (0) 10 / 42 12 033 e mail: [email protected]
Meltrade Automatika Kft.
HUNGARY
H-1105 Budapest
Phone: +36 (0)1 / 2605 602
Fax: +36 (0)1 / 2605 602 e mail: [email protected]
INEA d.o.o.
Stegne 11
Phone: +386 (0) 1-513 8100 e mail: [email protected]
Beijer Electronics AB
Box 426
Phone: +46 (0) 40 / 35 86 00
Fax: +46 (0) 40 / 35 86 02 e mail: [email protected]
SWITZERLAND
Postfach 282
CH-8309 Nürensdorf
Fax: +41 (0) 1 / 838 48 12 e mail: [email protected]
SLOVENIA
SWEDEN
Promyshlennaya St. 42
RU-198099 St Petersburg
Phone: +7 812 / 325 36 53 e mail: [email protected]
Fax: +7 095/ 261 3808 e mail: —
Fax: +7 095 / 786 21 01
RUSSIA
Ul Garschina 11
RUSSIA
RU-140070 Moscowskaja Oblast
RUSSIA
Ryazanskij Prospekt 8a, Office 100
RU-109428 Moscow
Phone: +7 095 / 232 - 0207 e mail: [email protected]
RUSSIA
Sverdlova 11a
RU-620027 Ekaterinburg
Fax: +7 34 32 / 53 27 45 e mail: [email protected]
RU-107005 Moscow
Phone: +7 095 / 786 21 00 e mail: [email protected]
RUSSIA
MITSUBISHI ELECTRIC
INDUSTRIAL AUTOMATION
Gothaer Straße 8 Phone: +49 2102 486-0 Fax: +49 2102 486-7170 www.mitsubishi-automation.de
D-40880 Ratingen Hotline: +49 1805 000-765 [email protected] www.mitsubishi-automation.com
advertisement
Key Features
- Conversion can be processed as a GX Developer function
- Data can be converted by file
- Sequence programs can be created using commercial software
- Data can be created in any file format
Frequently Answers and Questions
What is the purpose of GX Converter?
What are the system requirements for installing GX Converter?
How do I convert TEXT format data to a GX Developer list?
Related manuals
advertisement
Table of contents
- 2 SAFETY INSTRUCTIONS
- 3 REVISIONS
- 4 SOFTWARE USER REGISTRATION
- 5 Usage Precautions
- 6 INTRODUCTION
- 6 CONTENTS
- 8 About Manuals
- 9 How to read this manual
- 10 About the generic terms and abbreviations used in this manual
- 11 Product Components
- 12 1. OVERVIEW
- 12 1.1 Features
- 14 2. SYSTEM CONFIGURATION AND SPECIFICATIONS
- 14 2.1 Operating Environment
- 15 2.2 Overall Configuration
- 16 3. INSTALLATION AND UNINSTALLATION
- 16 3.1 Installation
- 18 3.2 Uninstallation
- 19 4. CONVERTING TEXT,CSV FORMAT DATA TO GX Developer FORMAT DATA
- 20 4.1 Converting TEXT Format Data to GX Developer Format Data
- 20 4.1.1 Converting TEXT format data to a list
- 25 4.1.2 Converting TEXT Format Data to Device Comments
- 30 4.2 Converting CSV Format Data to GX Developer Format Data
- 30 4.2.1 Converting CSV format data to a list
- 35 4.2.2 Converting CSV Format Data to Device Comments
- 40 4.3 Handling of conversion errors
- 42 5. CONVERTING GX Developer FORMAT DATA TO TEXT, CSV FORMAT DATA
- 43 5.1 Converting GX Developer Format Data to Text, CSV Format Data
- 46 6. FILE FORMATS
- 46 6.1 About TEXT CSV format files
- 48 6.2 File formats when the GX Developer import a TEXT, CSV format file
- 48 6.2.1 When a List is import by the GX Developer
- 52 6.2.2 When device comments are import by the GX Developer
- 53 6.3 File Formats When The GX Developer Format Data is Export to a Text, CSV Format File
- 53 6.3.1 When a List is export to a text, csv format file
- 55 6.3.2 When device comments are export to a text, csv format file
- 56 APPENDICES
- 56 Appendix 1. Limitations and Precautions
- 58 Appendix 2. Conversion Error Message List
- 60 Appendix 3. Converting CADIF Character-string Data
- 60 Appendix 4. Performance Specifications
- 61 INDEX