Справочник Пользователя для Mitsubishi Electronics QnUCPU
5
-
33
CHAPTER5 MEMORIES AND FILES USED FOR CPU MODULE
1
2
3
4
5
6
7
8
5.
3
F
F
ile
O
O
perat
ions by G
X
D
e
veloper and
Handling Prec
aut
ions
ions
5.
3.
2
Pr
ecaut
ecaut
io
ns
fo
r handli
ng f
iles
5.3.2 Precautions for handling files
(1) Power-off or reset at file operation
When the CPU module is powered off or reset at file operation, files in each memory are held (for a memory card,
when the CPU module where a memory card has been mounted before power-off is powered on).
when the CPU module where a memory card has been mounted before power-off is powered on).
When the programmable controller is powered off during an operation in which a file is moved, the data in operation are held
in the internal memory of the CPU module.
The held data are recovered at power-on.
To hold the internal memory data, battery backup is required.
in the internal memory of the CPU module.
The held data are recovered at power-on.
To hold the internal memory data, battery backup is required.
(2) Concurrent writing from multiple GX Developers to one file
GX Developers other than the one writing data to a file cannot access the file until the writing ends.
Also, GX Developers other than the one accessing a file cannot write data to the file until the access ends.
Therefore, write data to one file from multiple GX Developers one by one.
Also, GX Developers other than the one accessing a file cannot write data to the file until the access ends.
Therefore, write data to one file from multiple GX Developers one by one.
(3) Concurrent access from multiple GX Developers to different files
Except the currently viewed GX Developer, maximum 10 GX Developers can access to different files in one CPU
module concurrently.
module concurrently.