Library Object Manager overview

Use
Library Object Manager
to publish library objects to the ACM database or to a file in HSL4 format. HSL4 files can be distributed individually or as part of a repository.
After publishing a library object, use
Library Object Manager
to add HMI displays (
FactoryTalk® View Site Edition (SE)
or
FactoryTalk® View Machine Edition (ME)
) and Historian (
FactoryTalk® Historian Site Edition
) components to support requirements. Features added in the
Library Object Manager
application save to the individual HSL4 file or database entry for the Library object and do not save to the original ACD file.
Each library object file saved from the
Library Object Manager
application is classified within a four-level hierarchy:
Solution -> Library Type -> Category -> Catalog Number
Each library object file must have a distinct version number per solution. Just as the same Logix object can be used to create one or many library objects within the
Library Designer
, the same Library object can be used to create one or many distinct library object files within the
Library Object Manager
application.
Library objects can be quickly distributed, then registered into and configured for multiple projects in multiple locations. Library objects are available to any project that requires the functionality the library object provides.
Using
Library Object Manager
projects can be built and executed without high-level programming support.
Use the
Library Object Manager
application to perform these tasks:
  • Save library objects as individual files or entities in a database.
  • Add non-Logix components to library objects, including
    FactoryTalk View
    SE/ME Symbols,
    FactoryTalk View SE
    VBA code items,
    FactoryTalk®
    Historian Tags,
    FactoryTalk® Alarms and Events
    (FTAE) Digital Alarms, and
    FactoryTalk View ME
    (FTVME) Digital Alarms.
  • Create repositories for storing and distributing library object files.
Rockwell Automation®
recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal