Libraries – Load and open specialist packages

1. Library overview

Libraries in the top bar manages separately supplied specialist packages. Installed packages appear on the left; the selected package's name, version, description and activation status appear on the right.

The screenshot lists CIP / Ablaufsteuerung, Wartung & Betriebsstunden and Festplatz- und Chaoslager, all active. This is the shown installation's state; other installations and demos may have different activations.

2. Packages shown

CIP / Sequence control

Configurable CIP sequences. The selected version 1.0 describes up to 30 steps, valve identifiers Y1–Y32, requirements, setpoints, waiting conditions and maximum times per step. Its description includes an adaptable dairy or ice-cream-plant example.

Maintenance & Operating hours

Opens the maintenance and operating-hours module, distinct from an individual operating-hours display object.

Fixed-location and random-location warehouse

Opens warehouse management. Its views and booking operations are handled in that module.

The description belongs to the selected package and version. Select another entry to change the details. Adapt and validate example sequences for the actual machine before use.

3. Load a package

1. Click Load package.
2. Select the separately supplied .jvl file.
3. Read the result or error message and check the list.

A library package is neither a project file nor a CSV symbol table. The application checks its format and stores it in the library folder. A newly loaded product without activation remains locked. Loading is not activation.

Check name and version before package updates and back up project work. Use intended PamaGlawe packages.

4. Activate with a code

Select a locked package and click Activate with code. Enter the code supplied for that package. An invalid code produces an error; success saves activation and refreshes the overview.

The screenshot says Activated and ready, so activation is greyed out and Open library is available. This is expected for an already activated package.

A role name does not replace activation. A library activation code does not unlock hidden communication drivers in a demo. Do not include activation codes in public screenshots or help text.

Backup and moving to a new computer

The intended computer migration works as follows: activated libraries are backed up for transfer and restored on the new computer. Activation on the previous computer is intended to become inactive as part of that transfer.

Current status: A complete transfer workflow including automatic deactivation has not yet been confirmed for the version documented here. An ordinary file backup must therefore not be treated as a licence transfer. Arrange the migration with support beforehand; copying files alone does not guarantee deactivation on the old computer.

Back up projects and your own library content separately. Deactivation on the previous computer may prevent access to the affected modules there; plan the migration accordingly.

5. Open a library and check permissions

Open library opens the selected active module. It does not automatically start a CIP sequence or warehouse order.

With user management configured, these permissions also apply:

CIP

Open and edit CIP library.

Maintenance

Open and maintain maintenance.

Warehouse

View warehouse and stock to open it; further operations have separate permissions.

Active means activated, not unrestricted access for every user. If access is denied, check the role instead of loading the package again. See Users and roles.

6. Close and common messages

Close exits the overview without undoing loaded packages or saved activations. Save module content changes according to that module's workflow and in the project.

• No library loaded: Load the intended package.
• Locked: Supply the valid activation code.
• Invalid package format: The selected file is not a supported library package.
• Unknown module type: Package and editor version may be incompatible; obtain a matching version.
• Activation could not be saved: Check storage and write access; do not assume activation was saved permanently.