Projects Library Lifecycle

Goal

Create a Library project, author reusable POUs and type definitions in it, and reference it from another (PLC-only or PLC-with-HMI) project.

Note

A library project cannot be built or deployed on its own — to exercise it you also need a consuming project that imports the library.

Before you start

• Prerequisites: A signed-in account that can create projects, plus a second project to consume the library.
• Required role/permission: An Editor/Admin-level role.
• Settings that affect behavior:
  • Project type = Library — chosen at creation. A library contains only POUs and type definitions (no configuration, no HMI), and per Project types cannot be built/deployed standalone.
  • Import into consuming project — a library only takes effect once it is imported and added to the consuming project’s Libraries / configuration; until then its elements are not visible there.
  • Versioning — when you change a library, re-import/update it in consumers to pick up the changes, then rebuild the consumer.

Steps

1. Open Projects at /portal/projects and create a project of type Library.
2. Open it in the IDE (/portal/workspace/ide/:id) and author your POUs (functions, function blocks) and type definitions.
3. Create or open the consuming project (PLC only or PLC with HMI).
4. In the consuming project, import the library and add it under the project’s Libraries / configuration so its elements become available.
5. Use the library’s POUs in the consuming project, then build the consuming project (Builds, /portal/workspace/builds/:id).

No captured steps yet. Run make regenerate-flows after a portal-e2e:docflow pipeline run produces docflow-output/projects-library-lifecycle.json.

Related

• Project types
• IDE overview
• PLC lifecycle
• Managing projects