Mitsubishi Electric GOT2000 Series User Manual page 378

■7. Precautions for trigger backup
The following shows precautions for the trigger backup.
(1) GOT operations during trigger backup
The GOT may take a long time to monitor devices and to operate during the trigger backup.
Execute the trigger backup when the operator does not operate the GOT.
Updating data with the functions that collect device values, including the logging function, may also take a long time.
(2) Displaying device name on GOT
When the trigger device is set to [Rise], the GOT displays the device name of [??] without the device name converter
installed.
For displaying the device name correctly, install the device name converter on the GOT.
(3) First backup
The trigger backup is unavailable for the first backup.
Manually execute the first backup, and then set the password for the backup/restoration and passwords for
controllers. After the settings, set the trigger backup.
(4) Passwords for controllers
When passwords for controllers stored in the backup setting differ from current passwords for the controllers, the
backup operation is canceled.
For executing the trigger backup, check that passwords for controllers have no changes.
When the backup operation is canceled, manually execute the backup again, and then input correct passwords.
(5) Checking file register changes
When the trigger backup is frequently executed, set [Check the file register changes] to [Not execute] with the GOT
utility because data stored in file registers frequently changes.
When [Check the file register changes] is set to [Execute], the GOT backs up data stored in the file registers every
time the trigger condition is met even if the other setting data for the controller are not changed.
As a result, the number of backup data increases in the SD card. When the number of backup data exceeds the
maximum number of backup data, old backup data are deleted.
For obtaining data stored in file registers only, use the recipe function.
For how to use the ecipe function, refer to the following.
➠
(6) Backup on a motion controller CPU, robot controller or FXCPU
If the following are to be backed up, the GOT does not compare the previous backup data with the controller setting
data.
• A motion controller CPU and robot controller are mounted on the same base unit.
• FXCPU
As a result, the GOT executes the backup even if the setting data for the controllers have no changes.
For backing up setting data only when the data are changed, set the trigger type to [Rise].
Create a sequence program so that the trigger device turns on only when the setting data are changed. Therefore,
the number of backup data can be minimized.
(7) Backup on a robot controller
The robot controller is not compatible with checking changes. Therefore, if the backup is executed in the following
way, the communication speed and program execution speed may slow.
• The trigger backup is frequently executed.
• Multiple robot controllers are connected.
Backup data is large, due to the large number of programs.
(8) Screens that trigger backup can be executed
The trigger backup can be executed only when the GOT displays a monitor screen.
(a) When the trigger condition is met while the GOT displays a screen other than monitor screens,
including the utility screen and ladder monitor screen, the GOT does not execute the backup.
When a screen other than monitor screens is switched to a monitor screen, the GOT executes the backup.
(b) When a monitor screen is switched to a screen other than monitor screens during the trigger
backup, the GOT stops the backup and the GOT deletes the data in process.
When the screen is switched to a monitor screen, the GOT executes the backup again.
(c) When the following are operated, the GOT does not execute the backup even if a screen other than
monitor screens is switched to a monitor screen.
• Restarting the GOT
• Changing the trigger backup setting with the GOT utility
10 - 36
10.3 Operations for Display
GT Designer3 (GOT2000) Screen Design Manual