Transferring The System Configuration - Mitsubishi Electric WS0-CPU0 Operating Manual

11

Transferring the system configuration

Note
Note
Note
Note
Note
Transferring the system configuration
Initially, the configuration of the MELSEC-WS safety controller only exists as a
project, meaning as a MELSEC-WS configuration file. The configuration has to be
transferred to the memory plug via the CPU.
The memory plug and the CPU module communicate via an internal interface. Direct
connection of a PC to the memory plug is not possible. Data can only be loaded to
the memory plug or read from it via a compatible CPU module.
The configuration data are checked for compatibility during transfer to the memory
plug and can subsequently be verified (through reading and comparing) and
optionally have a write protection assigned to it.
With the memory plug the project data can be transferred without further processing
using the Setting and Monitoring Tool to any number of MELSEC-WS safety
controllers. The configuration data are copied exactly in the process, including the
verification and any write-protection information that were set during the
configuration of the first safety controller with these data.
Before using standby, hibernation, or sleep mode of PC, disconnect the PC from the
MELSEC-WS safety controller.
Before removing the RS-232 USB converter (WS0-UC-232A), disconnect the PC
from the MELSEC-WS safety controller.
11.1 Transferring project data to the safety controller
After the transfer, the configuration data are read back from the memory plug if the
verification has been activated in the Setting and Monitoring Tool (see Section 11.3).
The reading back of the configuration data from the memory plug requires some
time. The memory plug may not be removed during this time. The Setting and
Monitoring Tool displays a corresponding warning as long as the process takes.
11.2 Compatibility check
The configuration data contain an electronic type code and a version code for each
module that is to be configured. During the transfer each module checks whether it
is compatible with the configuration data. The compatibility check only applies to the
functional part of the respective module, not to the hardware variant, the
implementation of the terminals, for example, remains unconsidered.
If the compatibility check is negative, a corresponding error message is generated in
the respective module and in the CPU module.
In Setting and Monitoring Tool different version numbers are assigned to some
modules so that a compatible module can be selected from a list below the module.
Chapter 11
274