                                                                                                                                                                                  | |
Contents
| 
5.18 Extended know-how protectionBesides the "standard" Know-how protection the SPEED7 CPUs from VIPA provide an"extended" know-how protection that serves a secure block protection for accesses of 3.persons.n Standard protection– The standard protection from Siemens transfers also protected blocks to the PGbut their content is not displayed.– But with according manipulation the know-how protection is not guaranteed.n Extended protection– The "extended" know-how protection developed by VIPA offers the opportunity tostore blocks permanently in the CPU.– With the "extended" protection you transfer the protected blocks to a memory cardinto a WLD-file named protect.wld.– By plugging the memory card and then an overall reset the blocks in the pro-tect.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 headerare loaded. The block code that is to be protected remains in the CPU and cannotbe read.1. Create a new wld file in your project engineering tool with ‘File è Memory Card fileè New’.2. Rename the wld file to "protect.wld".3. Transfer the according blocks into the file by dragging them with the mouse fromthe project to the file window of protect.wld.4. Transfer the file protect.wld to a memory card.5. Plug the memory card into the CPU and execute an overall reset.Ä Chapter 5.14‘Overall reset’ on page 67ð The overall reset stores the blocks in protect.wld permanently in the CPU pro-tected from accesses of 3. persons.Protected blocks are overwritten by a new protect.wld. Using a PG 3. persons mayaccess protected blocks but only the block header is transferred to the PG. The blockcode that is to be protected remains in the CPU and cannot be read.Protected blocks in the RAM of the CPU may be substituted at any time by blocks withthe same name. This change remains up to next overall reset. Protected blocks may per-manently be overwritten only if these are deleted at the protect.wld before. By transferringan empty protect.wld from the memory card with an overall reset, you may delete all pro-tected blocks in the CPU.Due to the fact that reading of a "protected" block from the CPU monitors no symbollabels it is convenient to provide the "block covers" for the end user. For this, create aproject of all protected blocks. Delete all networks in the blocks so that these only containthe variable definitions in the according symbolism.OverviewProtect blocks with pro-tect.wldProtection behaviourChange respectivelydelete protected blocksUsage of protected blocksVIPA System 300S+ Deployment CPU 317-2AJ23Extended know-how protectionHB140 | CPU | 317-2AJ23 | en | 17-25 73 |
This manual is suitable for:
manualsdatabase
Your AI-powered manual search engine