remove the protection in V19

open/Upgrade after that to V20 

set protection again in v20

Hi,

it´s a system behaviour and you can read this in manual of V20:

Upgrading know-how protected blocks

Regards,

Towome

If you are the FB creator, this is fairly standard practice.

However, the technology exists that enables know-how protected (KHP) blocks to stay protected and cross version boundaries - with limitations.

What are the limitations?  I have no idea, but I have seen evidence of this capability from Siemens provided libraries and applications where at least 1 KHP block would upgrade to the next version of Portal without requiring unprotecting prior to upgrading a project.

If Portal V19/20 do not allow end-users this capability, nothing says you cannot submit your created KHP blocks to Siemens requesting they be similarly upgrade enabled - Example use case: Selling KHP code rather than full systems.

I suspect Siemens would require some way to confirm you know the password, but that you wish to keep those KHP blocks the same in V19 and V20.

I suspect that's when you find out the limitations of that technology.

Or, you can look in the F1-Help of TIA Portal and see how to configure block attributes such that KHP blocks can upgrade across projects.

dev_1960

Hello everybody,

I am trying the new v20 but I am having a problem with a password protected FB in my project library.

If I want to edit the FB to create a new release (or just open it) I have this message: "The block 'name' cannot be processed because the know-how protection was set up with an older version of Tia Portal..."

How can I solve?

The FB was create and know-how protected with the v19