Concepts and Elements ¶ The CODESYS library development and maintenance system is defined by a set of guidelines . To understand these guidelines, it is useful to describe some basic, but important co

Library Types ¶ In CODESYS, a differentiation is made between the following types of libraries: Common libraries Container libraries Interface libraries End User libraries For each type, there is a ch

How to change a library ¶ Note Compatibility: Compatibility of two libraries usually means that they react in the same way according to the requirements of an application. Important After changing a l

Placeholder ¶ A placeholder in the Library Manager is a reference on a definite library version. Placeholders simplify the maintenance of library hierarchies. In the CODESYS environment there are the

Library Prefix ¶ Before the introduction of the Namespace , the prefix used to identify world-wide uniquely a certain library. With the conversion from CODESYS V2 to V3 the prefix was substituted by t

Library Categories ¶ Using Library Categories in the Library Repository, besides sorting according to the Company Name allows to structure the huge set of libraries. The library categories are an impo

Library Properties ¶ Library properties serve for managing the meta data of a library. They are accessible via the Project Information . As from CODESYS 3.5.5.0 these properties have the following mea

Behaviour Model and Interface Design ¶ Note With CODESYS 3.5.11.0 a new library was introduced. The Common Behaviour Model replaces the CAA_Bahaviour.library . Please take a look to the documentation

Different Output Formats for Library Documentation ¶ HTML Output Format ¶ The libdoc transform html <struct> script uses the Sphinx module “ StandaloneHTMLBuilder ” for generating a discrete hypertext

Documentation in Different Languages ¶ There are various ways of providing documentation in different languages. The entire Sphinx project is copied with all associated *.rst files, which are translat