10/21/2024 1:14 PM | |
Joined: 10/21/2024 Last visit: 8/27/2025 Posts: 3 Rating:
|
What options do we have in PCS7 environment to protect a custom FB from copying? |
10/21/2024 3:54 PM | |
Joined: 3/14/2008 Last visit: 9/4/2025 Posts: 2216 Rating:
|
Hi, Maybe this post will help you: Access protection in PCS 7 plants You can also protect the block if it's generated from a SCL source. You can insert the code under the block call and delete the source from the multiproject after compiling. It does not prevent the use of the block, but at least the user cannot read the block code.
|
Last edited by: Moderator_Lan at: 10/21/2024 21:40:29link optimized If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to
2 thankful Users |
10/29/2024 8:40 PM | |
Joined: 2/1/2010 Last visit: 9/4/2025 Posts: 212 Rating:
|
Agree with Oreca. 99% of the time all of that is good enough. But, also be advised that KNOW_HOW_PROTECT is vulnerable to several nefarious methods. If you need to protect trade secrets contained in a function block you may decide to not trust this security method. You can alternatively use Encrypted block protection from Step7 5.5 (including PCS7 versions 8.0 and higher which include Step7 5.5+) These are the blocks with red key icon in the blocks folder. Encrypted block protection for FBs and FCs from STEP 7 V5.5 This is an additional install step you have to do manually aside from the base install of PCS7. You can typically find it on the PCS7 install media in the "Additional_Products" folder. |
If my post helped you, please rate. Thanks. |
|
This contribution was helpful to
2 thankful Users |
Follow us on