Guidelines for Library Development ¶ Select a meaningful filename Select a pragmatic library namespace Enter all project information Apply the correct method for referencing other libraries Design sma
File names ¶ Rule #1: Select a nice file name ( Required ) Common Libraries: <name>.library Container Libraries: <name>_Cnt.library Interface Libraries: <name>_Itfs.library The file name of a library
Namespace ¶ Rule #2: Select a unique library namespace ( Required ) A pragmatic sequence of Latin letters. As short as possible! For example “LAT” for a library to handle lists and trees. A group of s
Project Information ¶ Rule #3: Fill in the Project Information ( Required ) This data is important for switching off the CODESYS default behaviour. It is also important for a self-describing library.
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
Package Designer ¶ This feature will be available with CODESYS V3.5.3.0 The Package Designer is available via the CODESYS Store .
Library Development Checklist ¶ The library type is defined by one of the following Properties : “Placeholder” => Common Library , “IsContainerLibrary” => Container Library “IsInterfaceLibrary” => Int
Glossary ¶ Note This glossary is still a work in progress. We intend to provide improved explanations and additional topics in future versions of CODESYS. If you think an important term is missing, pl
Index A | C | D | E | F | G | H | I | L | M | N | O | P | Q | R | S | T A Application Composer asynchronous C Category CODESYS CODESYS Store Common Library Compatibility conditionalshow , [1] conditio