GX Developer Version 8 Operating Manual (Special
Contents
1. MELSOFT For importing data from MXChange server to GX Developer the data names correspond as indicated below MXChange tag GX Developer Project Tag name gt Alias Device 25 gt Comment For exporting data from GX Developer to MXChange server the data names correspond as indicated below GX Developer Project MXChange tag Device Device Comment Comment Label Tag name e When the Alias created on GX Developer is exported to the MXChange data base do not use any characters other than the alphabets numerals and _ In addition do not enter a space or numeral at the beginning of the Label f nothing has been set to the Alias of GX Developer at the time of Export Device changes to Tag name 4 CONVERSION FUNCTIONS 4 6 Importing from MXChange Tags O O x O Purpose Reads comment data in the MXChange server Operating Procedure Select Project Import file Import from MXChange tags Dialog Box from MXChange tags The data of M Change Project node will be imported into GX Developer Project Data name MxChange Project node GX Developer Project Data COMMENT After importing the MXChange tags will be written to the GX Developer project as shown below MxChange tag GX Developer Project Tag Name gt Alias Device gt Device name Comment gt2. Personal computer 1 GENERAL DESCRIPTION MELSOFT 2 Featured with the MXChange conversion functions Device comment data created in the GX Developer project can be shared with other applications by using the MXChange conversion functions GPPW Project MXChange structure eo Automation p roject na TE Ls T me H i dh X0 Sample1 sw1 T d YO Sample2 out F E A project COMMENT DO Sample3 value1 HB Device comment WO Sample4 amount1 MA XO swi Sample1 MO Sample initial v0 outi Sample2 Bl 0 valuel 1 Samples WO amount1 Sampled BH 0 initiall Samples I MAIN Elen A project WAIN MO Samplet initial2 Device comment XO 2 sw2 Bl m0 initial2 1 Samplet iis Made pog e Wil X0 sw2 Sample ample i WO ind i vo min i asia B ME LLL H D0 value2 Sample4 WO amount2 Samples Q Project Efl Q project COMMENT Device Comment et Device comment cu EET BH initiali Samplet MO Sample initial1 BH X0 iwl Sample2 X0 Sample2 Sw1 yo Sampled YO Sample3 out1 DO 4 yaluet W D0 valuel Sampled WO Sample5 amount A WO amount Sample5 EE Ef Q project MAIN HB Device c
3. 4 3 4 3 bogging iri to Server enano eeu v eno sev v DB o D Dd ep eni Oe ed 4 4 4 4 Logging tie Server ite re een due cand ee re cane 4 6 4 5 MXChange Data Base 4 7 4 6 Importing from MXChange 4 9 4 7 Exporting to MXChange 4 11 4 8 MXChange 4 15 APPENDIX App 1to App 4 Appendix 1 Restrictions on Using SX App 1 Appendix 2 Accessing to App 2 Appendix Restrictions When Changing CPU App 3 Manuals The following lists the manuals for this software package Refer to the following table when ordering manuals Related Manuals Manual Number Manual Name Model Code GX Developer Version 8 Operating Manual Explains the online functions of GX Developer such as the programming printout monitoring and debugging methods GX Developer Version 8 Operating Manual Startup SH 080372E Describes the system configuration installation method and start up procedure of GX Develop
4. FX1s FXtN FX3u and FX3uc A series For GX Developer CPU type selection by ACPU GOT Generic term for Mitsubishi Graphic Operation Terminal GOT 1000 series GOT A900 series and GOT F900 series Generic product name of the product types SWnPNC Q25SS E n denotes the version number When limited to earlier than the major version n denotes the version number SX Controller 1 GENERAL DESCRIPTION MELSOFT 1 GENERAL DESCRIPTION This manual explains the special functions of GX Developer designed exclusively for Overseas use 1 1 Features The following explains the features of GX Developer designed exclusively for overseas use 1 Accessibility to SX Controller SX Controller is software designed to operate on a PC CPU module By executing the program written with GX Developer SX Controller makes Q bus access and achieves sequence control using the device data that the software itself has User appliation Microsoft Visual Basic Microsoft Visual MELSEC commucation function Parameter QSS function Interpreting Sequence execution N Pa program Device IET E Er aT SX Controller Fae rf frie EP Q bus access sil Hard disk unit Ea 0338 E PC CPU module
5. ee p Os ie a Joe Sexe e Word devices Q02 H Q06 Q12H Q25HCPU Q01CPU awceu o o Ex aC EIE RECS ei Oe ox e Porn SC CS 1 R and ZR cannot be used for the QOOJCPU 4 MXChange CONVERSION FUNCTIONS 4 2 General Procedure for Using the MXChange Conversion Functions O O x O Refer to the Startup manual for GPPW installation pee Refer to the manual supplied with MXChange 1 1b for MXChange 1 1b installation Start the MXChange server Start from the MXChange group in the Start menu of Windows After starting GPPW log in to the MXChange server e Set the server name Refer to Section 4 3 e Set the password Install GPPW s MXChange conversion functions and MXChange 1 1b Make the Import from MXChange tags setting Make the Export to MXChange tags setting HIE Refer to Section 4 6 Refer to Section 4 7 Log off the server Refer to Section 4 4 Exit from GPPW 4 CONVERSION FUNCTIONS MELSOFT 4 3 Logging in to the Server O O x Purpose Enables use of the MXChange data base conversion functions Menu selection cannot be made unless the project is open on GX Developer Operating Procedure Select Tool MXChange actions Login Dialog Box Connection Server Name Use Local
6. 1 Select RS 232C and click the button on the PC side I F Serial setting of the Transfer Setup screen PC side I F Serial setting xj USB Cancel port COM 1 x Transmission speed 115 2Kbps 2 Set Parity Data Bits and Stop Bits on the Transfer Setup PC side I F Serial Setting screen Transfer Setup PC side I F Serial Set xj Paty pou J Data Bits Bbits z Cancel Stop Bits Thit Default Note that if the project with this setting is opened by GX Developer Version 8 04E or earlier the setting is discarded If the project created by GX Developer Version 8 04E or earlier is opened by GX Developer Version 8 05F or later the default setting is displayed POINT e Set via MAC MTA transparent mode on the PLC side I F Detailed setting of PLC module screen only when MAC MTA is used PLC side I F Detailed setting of PLC mod PLC mode via MAC MTA transparent mode via GOT Bus transparent mode via GOT direct coupled transparent mode via ASTEL GBTEL A mode converter mode Can not select both button at the same time Appendix 2 Appendix 2 App APPENDIX MELSOFT Appendix 3 Restrictions When Changing CPU Types The following table shows the restrictions when changing CPU types between QCPU Q mode and Q25SS Item Restrictions QCPU mode Q25SS Q25SS QCPU Q mode Instructions Incompatible instructions are converted
7. Command button in dialog box button Abbreviations and Terms in This Manual This manual uses the abbreviations and terms listed in the following table to discuss the GX Developer software package and programmable controller CPU module In addition the following table lists the names of modules whose names must be indicated explicitly Abbreviation Generic term Description Target module GX Developer Generic product name of the product types SW8D5C GPPW E SW8D5C GPPW p EA SW8D5C GPPW EV and SW8D5C GPPW EVA GX Developer Version n s SWnD5C GPPW E When limited to the major version n denotes the version number GX Developer Version n SWnD5C GPPW E or earlier iat When limited to later than the major version n denotes the version number Generic term for programmable controller CPU available with MELSEC A ACPU Including MOTION SCPU However GX Developer does not support A1 A2 A3 A3H A52G A73 A0J2 and QCPU A mode Generic term for Q02 H A and Q06H A QnACPU Generic term for programmable controller CPU available with MELSEC QnA QCPU Q mode Generic term for Q00J Q00 Q01 Q02 H Q02U Q04UDH Q06H QOGUDH Q12H Q12PH Q12PRH Q25H Q25PH and Q25PRHCPU QSCPU Abbreviation for a safety CPU module QS001CPU Generic term for programmable controller CPU available with MELSEC F The target FXCPU programmable controller CPUs are FXo FXos FXon FX1 FX2 2
8. i Mxchange tags Device Comment 8 550 database Comment New Folder MAIN Samplet eee er MAIN YO Sample2 out1 Elgin A project COMMENT DO Sample3 value1 51 88 Device comment WO Sample4 amount1 XO swl Sample1 MO Sample5 initial Bl YO outi Sample2 BH D0 valuel Sample3 B WO omountl Sampled BH 0 linitiall Samples I MAIN A project MAIN MO Sample initial2 E Device comment Sample2 sw2 E 0 initial2 1 Samplet YO Sample3 out2 Bl X0 sw2 Sample2 DO Sample value2 E v0 out2 1 Sample3 WO Sample5 amount2 i MED E O0 valuez2 Sample4 a wo amount Sample5 Q Project CE Q project COMMENT Device Comment Device comment fo ee BH M0 linitiali Sampler Samplet initial1 BB X0 swi ae Sample2 X0 Sample2 swt 1 1 19 le3 YO Sample3 out1 i vo d DO Sample4 valuei BH D0 valel Sampled WO Samples amount W0 amount Sample5 EE Q project MAIN El Device comment mH o nifial2 Samplet L MAIN E XO sw MO 1 Sample1 initial2 In the MXChange data base the comment types of the GX Developer device comments correspond to the respective project nodes FX Project COMMENT Q Project MAIN etc 4 MXChange CONVERSION FUNCTIONS
9. of GX Developer at the time of Export the device changes to the tag name 4 CONVERSION FUNCTIONS Exporting the data in the preceding table shows the following dialog box The following dialog box appears since Tag5 D64 Sample2 exists in the GX Developer data and Tag5 D64 Sampled exists in the MXChange data GX Developer Overwrite declaration GX Developer wants to create a new declaration with name still existing in Overwrite the existing device Tag5 D64 Sample5 with the one Tag5 D64 Sample2 No all No Since more than one SW2 exists as the Alias of the GX Developer data the following dialog box appears GX Developer Overwrite declaration GX Developer wants MXChange to create a new declaration with a name still existing in Overwrite the existing device with the one SW WO Sample3 No all No 4 MXChange CONVERSION FUNCTIONS 4 8 MXChange Troubleshooting The following table shows error messages and their corrective actions The connection to the MXChange server timed out Increase the time out value in the Login dialog box The server has been disconnected Start the a server or log in again Not Not logged in or insufficient right to perform the action in or insufficient right to perform the action the passwo
10. 712 E712 added LUMPI E712 added E712 added sw2 E712 added Ba Item Description Any of the following is displayed When changes were made to the project node MELSEC project MELSEC project QnA Class Name e MELSEC project Q MELSEC project Motion MELSEC project FX When changes were made to the tag e MM I O Reference Displays node names of GX Developer that are changed MXChange Project Name Displays project names that are changed Any of the following is displayed Node Name deleted The displayed node or tag was erased from another application modified Comment data of the displayed node or tag that was erased from another application are changed Changes added Additions were made to the displayed node or tag from another application 4 Change CONVERSION FUNCTIONS MELSOFT 4 4 Logging off the Server O O x O Purpose Stops connection to the MXChange server Operating Procedure Select Tool MXChange actions Logoff 4 CONVERSION FUNCTIONS MELSOFT 4 5 MXChange Data Base Conversion This section explains correspondences between the GX Developer project data and MXChange data base data for execution of MXChange data base conversion GPPW Project MXChange structure Automation project navigato A Project Comment Alias
11. ADA MINAMI 5 CHOME HIGASHI KU NAGOYA JAPAN When exported from Japan this manual does not require application to the Ministry of Economy Trade and Industry for service transaction permission Specifications subject to change without notice
12. Address Browse Time Qut 3000 mSec r Login po User Name Password Dption Show Message if data has been modified by other Applications Login Cancel Description 1 Server Name Type the MXChange server name or IP address to which GX Developer is connected Use Local Address button The computer name in current use is set as the Server Name Browse button A connectable server list is displayed Select the Server Name and click the button Time Out Set the time out value when making connection to the server The range setting is 0 to 200000ms User Name Defaults to Admin The User Name cannot be changed 4 CONVERSION FUNCTIONS MELSOFT 6 Password 7 Set the password max 1024 characters used when making connection to the server with the specified login name How to set the password change 1 Select Tool MXChange actions Password 2 n Old Password set the password currently used In New Password and Retype set a new password 3 Click the OK button Option When any change has been made to the data of the MXChange data base GX Developer receives that change and you can confirm it in the following dialog box MoXChange Another application has made some changes in the MXChange database Show Changes MXChange Project Name E
13. CCESSING TO SX Controller Compatible with the Q25SS This chapter explains the method for accessing to the SX Controller from the personal computer and GX Developer that operates on a PC CPU module Accessing from personal computer 3 MELSECNET H Accessing from GX Developer that operates on PC CPU module PC CPU module GX Developer MELSECNET H ELM CC Link SX Controller MELSECNET H QCPU CC Link 3 ACCESSING SX Controller MELSOFT 3 1 Accessing from Personal Computer Compatible with the Q25SS Purpose For the access to the SX Controller connection can be made in any of the following routes 1 Connect through the QCPU Q mode module 3 2 Connect from a personal computer to the SX Controller 3 Connect via MELSECNET H or CC Link on another station SX Controller MELSECNET H Operating Procedure Select Online gt Connection setup Dialog Box When the personal computer is connected to the RS 232 port of the PC CPU module In the case of 2 Connection Setup PC side PLC board board board board board net EB sons V C24 G4 Bus module module module module module HB PLC mode QCPU Qmode en Connection channel ist gation Other stalionfSing
14. Comment Import Cancel Description 1 MXChange Project Node Set the MELSEC project node Set the item from the LJ button 2 GX Developer Project Data name Select from the displayed data names that exist in the currently opened GX Developer project 4 CONVERSION FUNCTIONS 3 button Deletes all comment data exist on GX Developer and reads comment data from the MXChange server to GX Developer The following dialog box appears if the same data device number exist in the devices within the imported tag GX Developer Overwrite declaration MxChange database wants GX Developer to create a new declaration with name still existing in GX Developer Overwrite the existing device 501000 501000 Blown Fuse with the one 6501002 SD1000 1 0 Module Comparison Error No all No Yes Replaces the device comment displayed in Overwrite the existing declaration with the data displayed in with the new one Yes all Replaces all data with the newly read data No all Does not replace data if the tag name read from MXChange exists the Alias of the GX Developer comment data No Does not replace the device comment displayed in Overwrite the existing declaration with the data displayed in with the new one Selecting Yes or Yes all performs the following process After Import MXChange Data GX
15. Developer Data COMMENT COMMENT p TAG1 D100 Sample1 is overwritten by TAG3 D100 Sample3 When importing the MXChange data different in CPU type on GX Developer the data within the CPU type range of the GX Developer project is imported When importing the MXChange tag 64 characters to GX Developer the first 8 characters of the MXChange data are read to the GX Developer Alias When importing the comment 64 characters of the MXChange tag to GX Developer the first 32 characters of the MXChange data are read to the GX Developer comment 4 CONVERSION FUNCTIONS 4 7 Exporting to MXChange Tags O O x O Purpose Writes the device comments and Alias created on GX Developer to the MXChange data base server Operating Procedure Select Project Export file Export to MXChange tags Dialog Box Export Setting The data in the Data name of GX Developer project will be exported into Data name in Project node GX Developer Project Data name 4 sae se M amp XChange Project node Sample 5 CCIMMENT After exporting the GX Developer project data will be written to the database as shown below GX Developer Project MxXChange tag Device name gt Device Comment gt Comment Alias gt Tag name Esport Cancel Description 1 GX Developer Project Data name Displays the data name of the project cur
16. GX Developer Version 8 MITSUBISHI Special Functions for Overseas MELSOFT ww O eration Mh untenance rogramming MELSOFT Integrated FA Software SW8D5C GPPW E e SAFETY PRECAUTIONS Always read these instructions before using this equipment Before using this product please read this manual and the relevant manuals introduced in this manual carefully and pay full attention to safety to handle the product correctly The instructions given in this manual are concerned with this product For the safety instructions of the programmable controller system please read the CPU module user s manual In this manual the safety instructions are ranked as DANGER and CAUTION N Indicates that incorrect handling may cause hazardous conditions lt gt resulting in death or severe injury Indicates that incorrect handling may cause hazardous conditions resulting in medium or slight personal injury or physical damage Note that the CAUTION level may lead to a serious consequence according to the circumstances Always follow the instructions of both levels because they are important to personal safety Please save this manual to make it accessible when required and always forward it to the end user Design Instructions lt gt DANGER e When data change program change or status control is to be made from a personal computer to the running programmable controller CPU c
17. Operating Procedure Select Online Connection setup Dialog Box When accessing to another station through SX Controller via MELSECNET H eries Sx controller et us C24 G4 Bus module PLC mode 0 CC Link Ethernet module module No specification Other network Other station Co existence network PLC direct coupled setting Time out 30 Retry times pc Connection test Ea 5 PLC No C24 ETOH NET II CC Link Ethernet Mutiple CPU setting ne eee Network No T StationNo 0 _ System image P P SP P Line Connected Q AGTEL C24 112 3 C24 NET IUH CCUmk Elhemet Accessing other station Target PLC Nechace made Close Description You cannot select the Q compatible C24 or Q compatible E71 route of the module controlled by the SX Controller 4 MXChange CONVERSION FUNCTIONS 4 MXChange CONVERSION FUNCTIONS The MXChange conversion functions are designed to share the device comment data of GX Developer project among applications Programs device memory and others cannot be converted 4 1 Function List The following functions can be performed on GX Developer The tag information of the MXChange data base is read onto GX Developer and converted into GX Developer device comments Refer to Section 4 6 GX Developer device comments are converted into the tag informatio
18. ect use Please make this manual available to the end user CONTENTS SAFETY PREGAUTIONS rte net eerie e e ree eA A 1 REVISIONS E M A 2 INTRODUCTION e ETE A 3 CONTENDS nette unten Edu neu ue A 3 Manuals ate ee uere se eiie ee Lise A 4 How the manual describes the explanation is shown below sse 5 Abbreviations and Terms in This A 7 1 GENERAL DESCRIPTION 1 1to 1 3 UNI IP 1 1 12 E unction EISE eth be be e e e a teh Ei et ETE 1 3 2 SYSTEM CONFIGURATION 2 1to2 2 2 1 Connecting from the Serial Port 2 1 2 2 System Equilpmeht e eee ede tert E Re 2 1 ls ACCESSING TO SX Controller 3 1 3 4 3 1 Accessing from Personal 3 2 3 2 Accessing from GX Developer that Operates on PC CPU Module 3 4 4 MXChange CONVERSION FUNCTIONS 4 1to4 15 As FUNCION me 4 1 4 2 General Procedure for Using the MXChange Conversion Functions
19. er 13JU40 REMARKS Manuals in printed form are sold separately for single purchase Order a manual by quoting the manual number model code listed in the table above How the manual describes the explanation is shown below Indicates the QnA series and QCPU Q mode Indicates the A series QCPU A mode and Motion Controller SCPU Indicates 4 6 Importing from MXChange Tags x gt Reads comment data in the MXChange server Operati elect Project Import file Import from MXChange tags e Dialog Box The data of Data name in MXChange GPPW Project node wil be imported into GPPW Project Data name MxXChange Project Node Select GPPW ProjectDataName COMMENT E After importing the MXChange tags wil be written to the GPPW project as shown below Indicates the QSCPU the FX series O The function is available wa x The function is unavailable Items which are set in the section are explained r The desired window opens by selecting the items in the specified order tag GPPW Project Tag Name Label Device Device Comment Description Project Node Set the MELSEC project node Set the item from the button 2 GX Developer Project Data name Select from the displayed data names that exist in the currently opened GX Developer project T
20. he dialog boxes set in the section are explained The contents of the items and buttons are explained The numbers correspond to those specified in the window shown under the title of Dialog box e When importing the MXChange tag 64 characters to GX Developer the first 8 characters of the MXChange data are read to the GX Developer Alias e When importing the comment 64 characters of the MXChange tag to GX Developer the first 32 characters of the MXChange data are read to the GX Developer comment This gives the information related to the topic discussed and also the helpful information Symbols used in this manual and the contents and examples of them are shown below ie MELSEC series GPP C MELSEC GPPW Sample LD Edit mode MAIN 1 Step nf x Project Edit Find Replace Convert View Online Diagnostics Tools Window Help 1 amp ES 2 D as e S AAL 21 ele Bll 88 1 TH t Fs sts eno Emi 1 TA 211 EE ET FIT sal ss Options Ea 3 Program common Each program Whole data Copy source display source of reference during comment edit device monitor Program name MAIN Monitor 7 Device type Device comment _ Contents Example Menu name of menu bar Project Icon in toolbar amp Tab name of dialog box Program common
21. input an appropriate tag name It is allowed to use Alphabets Numerals and abc SP D 9001 abc gt j Cancel 4 CONVERSION FUNCTIONS The following dialog box appears if the same tag name already exists in MXChange data base or if overlapping data exist in the device comments or aliases of GX Developer GX Developer Overwrite declaration GX Developer wants to create a new declaration with a name still existing in Overwrite the existing device SM246 PLC Module 3 Stop Error Flag with the one SM246 SMf5 PLC Module 2 Stop Error Flag No all No Yes Replaces the tag displayed in Overwrite the existing declaration with the tag displayed in with the new one Yes all Replaces all data with new data No all Does not replace data if the same tag name exists at the write destination No Does not replace the tag displayed in Overwrite the existing declaration with the tag displayed in with the new one Selecting Yes or Yes all performs the following process Before Export GX Developer Data MXChange Data COMMENT COMMENT D64 MO YO D64 Sample Des wo Sample2 L Yo Sample Sample6 Y50 of GX Developer is not exported since it has no COMMENT and Alias f there is no data set in Alias
22. into SM999 Incompatible devices SM1024 SD1024 and later No restrictions are converted into SD999 Since Q25SS dedicated instructions if converted do Devices When the program is converted into Q00J not result in errors perform a program check and program file registers R ZR are converted into correct the program after conversion Programs SD999 Device memo n y No restrictions No restrictions Device comments PLC parameters e Remote password is deleted Network parameters MELSECNET H No restrictions No restrictions MELSECNET 10 CC Link Norestrictions No restrictions Appendix 3 Appendix 3 APPENDIX MELSOFT MEMO Appendix 4 Appendix 4 Microsoft Windows Microsoft Windows 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 1998 Farpoint Technologies Inc SH NA 080760ENG A GX Developer Version 8 Operating Manual Special Functions for Overseas MODEL GXDEV8 O FO E MODEL 13JU60 SH NA 080 760ENG A 080 1 MEE s MITSUBISHI ELECTRIC CORPORATION HEAD OFFICE TOKYO BUILDING 2 7 3 MARUNOUCHI CHIYODA KU TOKYO 100 8310 JAPAN NAGOYA WORKS 1 14 Y
23. le network Other station Co esistence network PLC direct coupled setting Time out Sec Retytimes 0 cesar PLC type PLC No C24 CCLrk Elheme ii CPU setting System image 3333 Line Connected Q AGTEL C24 12 4 l C24 CC Link Ethemet Accessing host station Target PLC Choice made Close 3 ACCESSING SX Controller MELSOFT Description For PC side I F select the port interface board or the like used with the personal computer For PLC side I F select the module to be connected to the personal computer Refer to the GX Developer Operating Manual for setting Other station Network route and Co existence network route You cannot select the following route You cannot select the Q compatible C24 or Q compatible E71 route of the module controlled by the SX Controller SS PC CPU module Q compatible C24 Q compatible E71 SX Controller Q compatible C24 Q compatible E71 3 ACCESSING SX Controller MELSOFT 3 2 Accessing from GX Developer that Operates on PC CPU Module Compatible with the Q25SS Purpose When GX Developer is installed in the PC CPU module data can be accessed to the SX Controller or to another station through SX Controller via MELSECNET H or CC Link PC CPU module GX Developer MELSECNET H CC Link SX Controller MELSECNET H CC Link QCPU
24. n of the MXChange data base and the results are written to the MXChange data base Refer to Section 4 7 Among multiple MXChange data bases specify the data base MXChange server designation server which reads writes the device comment data of GX Developer Refer to Section 4 3 MXChange data base GX Developer device comment read MXChange data base GX Developer device comment write When the MXChange data base is updated from another Tag change notice application it can be confirmed that the tag information has been changed Refer to Section 4 3 Password s ttih Set the password used when you log in to the MXChange server 9 Refer to Section 4 3 The following table lists the devices supported For MXChange 1 1b e Bit devices apu O O x 1 acu ESSE SEN RE AES Ee 1 x Word devices Se E O o x ean o Ewe AF x TEESEEISE 4 MXChange CONVERSION FUNCTIONS For MXChange 2 1 e Bit devices aun Q02 H Q06 Q12H Q25HCPU Q00J Q00 Q01CPU anacru 0 er aol or odd
25. omment Wil AAO initial Samplet MAIN Wixo 2 MO inia 3 Accessibility to MAC MAC can be accessed by using the RS 232C serial communications 1 GENERAL DESCRIPTION MELSOFT 1 2 Function List The following table shows the function menus for GX Developer designed exclusively for overseas use Tool Common functions MXChange actions Log into MXChange Server Log of MXChange Server Change Password Changes password in MXChange Server 435 2 SYSTEM CONFIGURATION MELSOFT 2 SYSTEM CONFIGURATION The following figure shows the system configuration of GX Developer designed exclusively for overseas use 2 1 Connecting from the Serial Port GX Developer SW8D5C GPPW Programmable controller direct coupled USB communication RS 232 Ed SX Controller PC CPU module 1 PC CPU module compatible RS 232 cable Personal Cable connection and signal direction computer Signal name RD RXD RD RXD somo DTRER CD DSR DR DSR DR RS RTS RS RTS CS CTS CS CTS 2 2 System Equipment The following table shows the module that can be accessed to from GX Developer designed exclusively for overseas use Programmable controller Module name Module model CPU series Programmable controller CPU module 92555 2 SYSTEM CONFIGURATION MELSOFT MEMO 3 ACCESSING SX Controller MELSOFT 3 A
26. onfigure up an interlock circuit in the outside of the programmable controller system to ensure that the whole system will always operate safely Also determine corrective actions to be taken for the system when a communication error occurs due to a cable connection fault or the like in online operation performed from the personal computer to the programmable controller CPU N CAUTION e Online operation performed with a personal computer connected to the running CPU module especially program change forced output or operating status change should be started after carefully reading the manual and fully ensuring safety Not doing so can cause machine damage or accident due to miss operation REVISIONS The manual number is given on the bottom left of the back cover Print Date Manual Number Jan 2008 SH NA 080760ENG A First edition 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 2008 MITSUBISHI ELECTRIC CORPORATION 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 MELSEC series programmable controller thoroughly in advance to ensure corr
27. rd correctly the password correctly Logoff incorrect Make sure that the server has been started confirmed error code number Close Connection unsuccessful Make sure that the server has been started confirmed error code number The old password was incorrect Set a correct password Licencing limits exceeded Export within the permitted number of tags The PLC type of the exporting project node differs with the PLC type of the actual project Please create a new Project node or specify the project node having the PLC type same as the project MXChange server Disconnect Start the EA server or log in again Bad 1st character of MXChange tag name Using correct characters re set the tag correct characters re set the tag name The connection is broken Processing is canceled Log in to the server again A partial data was Exported Project is already used by user Execute after logging off MXChange in the corresponding application Project node is not exist in MXChange server Perform operation after create the MELSEC project node An attempt was made to export the comment data of the CPU type of the GX Developer project not supported by This PLC type is not available in MXChange MXChange Choose the MXChange Project node of the same CPU type as that of GX Developer Project at Export Create a new project of the export destination separately or choose the project of the same CPU t
28. rently edited Set the data name to be written to the MELSEC data base 2 MXChange Project node Set the MELSEC project node at the export destination of MXChange When selecting the existing project node setting be made from the 4 CONVERSION FUNCTIONS MELSOFT 3 button Converts the comment data of the MXChange data base The following dialog box appears if the MELSEC project node set on the Export Settings screen does not exist Create Project Node Node test is not exist Are you sure to create test node Create Clicking the Create button creates a new MXChange node MELSEC project node comment node with the input node name The following dialog box appears if the CPU type set for the selected project node differs from the CPU type of the GX Developer project to be exported Perform operation in accordance with the message of the following dialog box MXChange actions The PLE type of the exporting project node differs with the type of the actual project e Please create a new project node or specify the project node having the PLC type same as the project The following dialog box appears if the Alias of the GX Developer project includes any character other than the alphabets numerals and or if the first character is a space or numeral Export to MXChange tags The tag name 1 abc contains some illegal characters Please
29. ype as that of GX Developer for the export destination APPENDIX MELSOFT APPENDIX Appendix 1 Restrictions on Using SX Controller This chapter explains the restrictions on functions of GX Developer when using SX Controller 1 Restrictions on PLC parameter Compatibility with A PLC lt lt PLC system gt gt cannot be set Low speed program execution time on lt lt PLC gt gt cannot be set 2 Restriction on network parameter Ethernet parameter cannot be set 3 Restrictions on program list monitor Monitor time fields of Total scan time are masked Low speed program field of Scan execution part detailed scan time is masked 4 Restriction on sampling trace The setting range when Interval is selected for the Trace point setup is as follows CPU ype SX Controller 1 to 5000ms 5 Restriction on Ethernet diagnostics Ethernet diagnostics cannot be executed when Q25SS is selected for CPU type 6 Restrictions on system monitor Installed status The CPU type name is not displayed when SX Controller is not operated on a PC CPU The field is displayed blank PLC diagnostics button Ethernet diagnostics cannot be executed when SX Controller is selected as a CPU type on GX Developer Appendix 1 Appendix 1 APPENDIX MELSOFT Appendix 2 Accessing to MAC The following shows the setting when accessing to MAC by using RS 232C serial communications
Download Pdf Manuals
Related Search