02.09.2014 Views

ISPSoft User Manual

ISPSoft User Manual

ISPSoft User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ISPSoft</strong> <strong>User</strong> <strong>Manual</strong><br />

15.1 Password Protection Mechanisms Provided by<br />

<strong>ISPSoft</strong><br />

To protect the programs or the core techniques developed by users, <strong>ISPSoft</strong> provides multiple<br />

protection mechanisms for the projects developed by the users. The password protection<br />

mechanisms provided by <strong>ISPSoft</strong> are shown below. <strong>User</strong>s can set or unlock the passwords, and<br />

adopt different data protection mechanisms according to their needs.<br />

Password type<br />

<strong>ISPSoft</strong><br />

project<br />

PLC<br />

Program ID<br />

Project<br />

password<br />

POU<br />

password<br />

Subroutine<br />

password<br />

PLC ID<br />

PLC<br />

password<br />

Description<br />

This is the first authentication information which needs to be checked<br />

on. If users want to download a project to a PLC, the program ID set in<br />

the project must be the same as the PLC ID set in the PLC. A specific<br />

project can only be downloaded to a specific PLC.<br />

The project password set in a project is used to protect the program in<br />

the project. If users want to open the POUs in a project protected by a<br />

project password, the system will require the users to type the correct<br />

password.<br />

The POU password set in a POU is used to protect the POU. <strong>User</strong>s<br />

can set a password in a POU to protect the source code or the core<br />

technique in the POU.<br />

A subroutine password set in a subroutine is used to protect the<br />

subroutine. It prevents the programs in the function blocks from being<br />

analyzed after the programs are uploaded. This function only supports<br />

DVP series PLCs. AH500 series CPU modules adopts another<br />

mechanism.<br />

This is the first authentication information which needs to be checked<br />

on. If users want to download a project to a PLC, the program ID set in<br />

the project must be the same as the PLC ID set in the PLC. A specific<br />

project can only be downloaded to a specific PLC.<br />

The PLC password set in a PLC is used to protect the data in the PLC.<br />

If users want to download the data protected by a PLC password to a<br />

PLC, or upload the data protected by a PLC password from a PLC,<br />

they have to type the correct password.<br />

15-2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!