Releasing the library

Required

If there is no release of the library, the following steps for a logi.SAFEor a logi.WEB library (deploying to the project and loading on the target system) are not possible.

If you want to generate a logi.CAD 3 library, skip this instruction. Usually, a logi.CAD 3 library is deployed and installed only.

How to release the logi.SAFE or logi.WEB library:

  1. Expand the library configuration in the project explorer after the ibrary has been generated. Open the context menu for the library displayed in the sub-level.

  2. Select the command Release (PiL Tested).
    images/s/b2ic8e/9012/1ca6q62/_/images/icons/emoticons/information.svg If no PiL-test has been executed for the library yet, the command Release (SiL Tested) is provided instead of the command Release (PiL Tested). As the PiL test is another recommended step, best practice is to select the command for the release always after the executed PiL test.

  3. Check the messages within the opened dialog and make sure that the library is going to be released successfully.
    If the library is not conform to the requirements, appropriate messages within the dialog will indicate so. If you want to view the release information within the release report, click the text/link release report within the dialog.

  4. Within the dialog, click OK to actually release the library.
    Result: logi.CAD 3 generates the released library named library__version-REL.zip within the sub-folder target of the project. The release report is included within this ZIP-file.
    See "Generating and examining a library or password-protected library", if the folder target is not displayed in the project explorer and you want to display it.

Recommendations for a successful release

A library should meet the following recommendations so that it is released as logi.SAFE or logi.WEB library:

  • The →fingerprint of each →POU must be identical within the test reports of the SiL/PiL test as well as within the library generation report.

  • The fingerprint of the test suite for each POU must be identical within the test reports of the SiL/PiL test as well as within the library generation report.

  • The SiL test and the PiL test must have been executed with the same logi.CAD 3 version.

  • The generated files must not have been manipulated. (This is checked based on the generated/included checksums.)

  • The fingerprint of the library from the PiL test must be identical with the one from the library generation report.

Contact logi.cals , if you release a library that is not meeting the above-mentioned recommendations and you want to use this library along with →logi.SAFE or →logi.WEB.

Good to know

images/s/b2ic8e/9012/1ca6q62/_/images/icons/emoticons/lightbulb.svg logi.CAD 3 provides a tool for the automated release of the library .