MX Component Version 4 Programming Manual

1 MX Component Version 4 Programming Manual -SW4 DNC-ACT-E1 SAFETY PRECAUTIONS(Read these precautions before using this product.)Before using this product, please read this Manual and the relevant manuals carefully and pay full attention to safety to handle the product this Manual , the safety precautions are classified into two levels: " WARNING" and " CAUTION".Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious the precautions of both levels because they are important for personal and system sure that the end users read this Manual and then keep the Manual in a safe place for future reference.[Design Precautions][Design Precautions][Security Precautions]WARNING When data change, program change, or status control is performed from a personal computer to a running programmable controller, create an interlock circuit outside the programmable controller to ensure that the whole system always operates , for the online operations performed from a personal computer to a programmable controller CPU, the corrective actions against a communication error due to such as a cable connection fault should be predetermined as a The online operations performed from a personal computer to a running programmable controller CPU (forced output and operating status changes) must be executed after the Manual has been carefully read and the safety has been operation failure may cause the injury or machine To maintain the security (confidentiality, integrity, and availability) of the programmable controller and the system against unauthorized access, denial-of-service (DoS)

2 Attacks, computer viruses, and other cyberattacks from external devices via the network, take appropriate measures such as firewalls, virtual private networks (VPNs), and antivirus that incorrect handling may cause hazardous conditions, resulting in death or severe injury. CAUTIONI ndicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property OF USE FOR THE PRODUCT(1) MELSEC programmable controller ("the PRODUCT") shall be used in conditions;i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.(2) The PRODUCT has been designed and manufactured for the purpose of being used in general ELECTRIC SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI ELECTRIC USER'S, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.

3 ("Prohibited Application")Prohibited Applications include, but not limited to, the use of the PRODUCT in; Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the public could be affected if any problem or fault occurs in the PRODUCT. Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality assurance system is required by the Purchaser or End User. Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other applications where there is a significant risk of injury to the public or the above restrictions, Mitsubishi Electric may in its sole discretion, authorize use of the PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi Electric and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required.

4 For details, please contact the Mitsubishi Electric representative in your region.(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and system trouble caused by DoS attacks, unauthorized access, computer viruses, and other CONSIDERATIONSThis section explains the considerations in the following of operating system and personal computer to be used Restrictions applied when a user without Administrator's authority operates MX ComponentNote that the following restrictions are applied when a user without Administrator's authority operates MX Component .*1 If the following error message is displayed, start up and close the utility as a user with Administrator's operation enables a user without Administrator's authority to start up the utility. Resume and other functions of personal computerA communication error may occur when communicating with the programmable controller CPU after setting the resume function, suspend setting, power-saving function, and/or standby mode of the personal , do not set the above functions when communicating with the programmable controller of operating system and personal computer to be usedConsiderations of installation and uninstallationProgrammable controller CPU-related considerationsConsiderations for using other MELSOFT productsConsiderations for using Ethernet modulesConsiderations for using CC-Link modulesConsiderations for using serial communication modulesConsiderations of modem communicationConsiderations of programmingConsiderations for using Microsoft Excel Considerations for using Microsoft Access Considerations for using VBScriptConsiderations for using Robot controllerItemRestrictionsCommunication Setup UtilityThe logical station number cannot be created.

5 Changed, or settings cannot be utility cannot be started up if the communication settings are set using MX Component earlier than Version *1 PLC Monitor UtilityThis utility cannot be started up if the communication settings are set using MX Component earlier than Version *1 Device registration cannot be performed on the [Entry Device] boardVarious settings cannot be set on the CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, and CC-Link board of installation and uninstallation InstallationWhen performing overwrite installation, install the software in the same folder where it is installed previously. Start menuWhen MX Component is uninstalled, the item may remain in the start this case, restart the personal computer. When downloading the installerWhen downloading the installer, save the installer to a directory which does not include any space and execute controller CPU-related considerations Considerations for performing USB communicationA communication error may occur and it may not be recovered if connecting and disconnecting a USB cable, resetting the a programmable controller CPU, or turning the power ON or OFF is performed frequently during communication with a programmable controller it is not recovered, completely disconnect the USB cable and then reconnect it after 5 or more seconds.

6 (If this error occurs at the initial communication after the above operation, the function will be performed properly in and after the second communications.) Clock data of programmable controller CPU For QCPUs (Q mode), LCPUs, and FXCPUs, the clock data setting can be set if the programmable controller CPU is in the RUN status. For QCPU (Q mode) and LCPU, the setting can be set regardless of the ON/OFF status of the time setting device "SM1028". The clock data can be set on FXCPUs with the built-in clock or FXU/FX2C/FX2NC with the RTC cassette. Note that an error for transfer time occurs in the time setting. Restrictions on using FXCPU When an FXCPU is used, the TN devices (timer present values) or CN devices (counter present values) cannot be accessed if the device numbers specified are split across 199 or lower and 200 or higher. Since FXCPUs do not feature the PAUSE switch as the programmable controller CPU, an error is returned if remote pause is specified in SetCpuStatus.

7 Note that specifying the first I/O number of a non-existing module and executing the WriteBuffer() method will not return an error. For the index registers (Z, V) of FXCPUs, data cannot be written to 2 or more consecutive points using WriteDeviceBlock(). (Data may be written to only one point.) serial communication function of Q00UJ/Q00/Q00U/Q01/Q01U/Q02 UCPUIn this section, " serial communication function compatible CPU" indicates Q00UJ/Q00/Q00U/Q01/Q01 the following conditions are all satisfied, communication between the personal computer and the serial communication function compatible CPU is set at 9600bps speed. The serial communication function of the connected CPU is valid. The transmission speed settings differ between the personal computer and the serial communication function compatible CPU increase the communication speed, match the transmission speed of personal computer with that of serial communication function compatible Considerations for using built-in Ethernet CPU When resetting the programmable controller CPU during TCP/IP connection establishment (during opening) using MX Component , a communication error or receive error occurs at subsequent this case, perform the close processing in the application that uses MX Component , and perform the open processing again.

8 The communication error may occur while establishing the Ethernet direct connection for the CPU, which communicates using Ethernet direct connection with another personal computer. In such case, retry the communication by resetting the CPU. Considerations for using RnSFCPUIn order to protect the safety programmable controller system, the "write to buffer memory" and "write to safety devices in safety mode" functions cannot be executed. Considerations for using QSCPUIn order to protect the safety programmable controller system, functions to write data to buffer memory, to write/set devices, and to write clock data cannot be executed. Considerations for using FX5 CPU Since FX5 CPUs do not feature the PAUSE switch as the programmable controller CPU, an error is returned if remote pause is specified in SetCpuStatus. Multiple simultaneous communications cannot be established via the route specified by a different adapter when an adapter to be used for Ethernet direct connection is specified to establish a communication .

9 Personal computer-side adapter information of communication settings may need to reset depending on the change in personal computer environment or other MELSOFT application for using other MELSOFT products Considerations for performing GX Simulator communicationBefore executing PLC Monitor Utility, communication Setup Utility, or a user program, check that GX Simulator and GX Developer are operating. Do not terminate GX Simulator and GX Developer while executing the user , the user program will not be terminated normally. Considerations for performing MT Simulator2 communication After installing MX Component , install MT Developer2. The maximum number of connections to MT Simulator2 is Developer2 is included in the maximum number of two MT Developer2s and one MT Simulator2 are activated, three connections can be established from MX for using Ethernet modules Resetting programmable controller CPU during TCP/IP connection establishmentWhen resetting the programmable controller CPU during TCP/IP connection establishment (during opening) using MX Component , a communication error or receive error occurs at subsequent this case, perform the close processing in the application that uses MX Component , and perform the open processing again.

10 Target existence check starting interval of Ethernet moduleIf the close processing (Close) is executed from the personal computer, the Ethernet module may not perform the close processing (Close). One of its causes is the cable the open processing (Open) is executed from the personal computer with the Ethernet module not executing the close processing (Close), the open processing (Open) from the personal computer is not terminated normally until the Ethernet module performs a target existence check and executes the close processing (Close).When terminating the open processing (Open) early from the personal computer, shorten the target existence check starting interval setting of the Ethernet module .(The default setting of target existence check starting interval of the Ethernet module is 10 minutes.) Replacement of Ethernet moduleIf the Ethernet modules are changed during Ethernet communication due to debugging, failure or the like, the other node (personal computer) must be restarted.