Table of Contents
Advertisement
VIPA System SLIO
Accessing the storage
medium
4.16
Extended know-how protection
Overview
Standard protection
Extended protection
HB300 | CPU | 013-CCF0R00 | en | 16-40
To the following times an access takes place on a storage medium:
After overall reset
The CPU checks if a VSC is inserted. If so, the corresponding optional functions are
n
enabled.
n
The CPU checks whether a project S7PROG.WLD exists. If so, it is automatically
loaded.
After PowerON
n
The CPU checks whether a project AUTOLOAD.WLD exists. If so, an overall reset is
executed and the project is automatically loaded.
The CPU checks whether a command file with the name VIPA_CMD.MMC exists. If
n
so the command file is loaded and the commands are executed.
n
After PowerON and CPU STOP the CPU checks if there is a *.pkg file (firmware file).
If so, this is shown by the CPU by blinking LEDs and the firmware may be installed by
Ä Chapter 4.13 'Firmware update' on page 80
an update request.
Once in STOP state
n
If a memory card is plugged, which contains a command file VIPA_CMD.MMC, the
command file is loaded and the containing instructions are executed.
The FC/SFC 208 ... FC/SFC 215 and FC/SFC 195 allow you to include
the memory card access into your user application. More can be found in
the manual "Operation list".
Besides the "standard" Know-how protection the CPUs from VIPA provide an "extended"
know-how protection that serves a secure block protection for accesses of 3. persons.
The standard protection from Siemens transfers also protected blocks to the PG but their
content is not displayed. But with according manipulation the Know-how protection is not
guaranteed.
The "extended" know-how protection developed by VIPA offers the opportunity to store
blocks permanently in the CPU. With the "extended" protection you transfer the protected
blocks to a memory card into a WLD-file named protect.wld. By plugging the memory
card and then an overall the blocks in the protect.wld are permanently stored in the CPU.
You may protect OBs, FBs and FCs. When back-reading the protected blocks into the
PG, exclusively the block header are loaded The block code that is to be protected
remains in the CPU and cannot be read
Deployment CPU 013-CCF0R00
Extended know-how protection
85
Advertisement
Table of Contents
