Filter
Top Products
3 - 2 3 - 2
3 COMMON OPERATIONS
MELSOFT
3.2 Precautions for Management
(1) Precautions for project data management
Be sure to read the Safety Application Guide for correct management/operation
of project data.
A system manager has to back up the project and save the backup data so that
the data restoration is always possible.
(2) Precautions for password management
A system manager has to manage the user information (e.g. user name, login
password, and CPU access password) registered to a project with attention.
If losing a login password or CPU access password, either of the following
actions is required.
(a) Losing a login password
The project cannot be opened.
If a system manager has lost the password, re-creating a project is
required.
(b) Losing a CPU access password
When a CPU access password has been set to a safety CPU, "Write to
PLC" cannot be performed unless the same password is set to the project.
Note that the CPU access password that has been set to a safety CPU
cannot be changed.
If losing a CPU access password, initialize the safety CPU by using "PLC
memory initialization" and then rewrite the project to the programmable
controller.
(For "PLC memory initialization"
Section 5.2.4)
(3) Precautions for ROM information management
A system manager has to record and store "ROM information" each time
program memory is written to ROM.
When the ROM information in a safety CPU matches with the previously saved
one, a system manager can judge that the data have not been changed.
(For "ROM information confirmation"
Section 5.2.2)
(Main display contents of ROM information)
• The year/month/day/hour/minute/second when program memory is written to
ROM.
• The parameters and program ID when program memory is written to ROM.
• The user who wrote program memory to ROM.
3