
Chapter 4 Deployment CPU 313SC/DPM
Manual VIPA System 300S SPEED7
4-38
HB140E - CPU SC - RE_313-6CF03 - Rev. 07/45
Transfer the file protect.wld to a MMC storage module, plug the MMC into
the CPU and execute an overall reset with the following approach:
PWR
RUN
STOP
SF
FRCE
MCC
PLC
PWR
RUN
STOP
SF
FRCE
MCC
PLC
PWR
RUN
STOP
SF
FRCE
MCC
PLC
PWR
RUN
STOP
SF
FRCE
MCC
PLC
1
2
3
4
3 Sec.
3 Sec.
RUN
STOP
MRES
RUN
STOP
MRES
RUN
STOP
MRES
RUN
STOP
MRES
The overall reset stores the blocks in protect.wld permanently in the CPU
protected from accesses of 3. persons.
Protected blocks are overwritten by a new protect.wld.
Using a PG 3
rd
persons may access protected blocks but only the block
header is transferred to the PG. The block code that is to protect remains
in the CPU and can not be read.
Protected blocks in the RAM of the CPU may be substituted at any time by
blocks with the same name. This change remains up to next overall reset.
Protected blocks may permanently be overwritten only if these are deleted
at the protect.wld before.
By transferring an empty protect.wld from the MMC you may delete all
protected blocks in the CPU.
Due to the fact that reading of a "protected" block from the CPU monitors
no symbol labels it is convenient to provide the "block covers" for the end
user.
For this, create a project out of all protected blocks. Delete all networks in
the blocks so that these only contain the variable definitions in the
according symbolism.
Transfer
protect.wld to CPU
with overall reset
Protection
behavior
Change respectively
delete protected
blocks
Usage of
protected blocks
Summary of Contents for 313-6CF03
Page 2: ...Lerrzeichen ...