Library Documentation ¶ Note CODESYS LibDoc Scripting Collection This section is intended to clarify the current situation regarding documentation in the CODESYS source code. The introduction of the C

Documentation Areas ¶ Project Information ¶ Folder ¶ Declaration Header ¶ Member Declaration ¶ Enums, Structures, GVL’s ¶ Some other possibilities to mark up the comments. Actions and Transitions ¶ Th

Segmented Buffers ¶ It is a constantly recurring task to fill memory areas with certain data. The following is often added as an additional requirement: Some parts always have the same content. Specia

Asynchronous Job Execution ¶ The critical factor in many applications is the cycle time of a task. The smaller this can be, the more frequently the signals of the processes can be checked, which are t

Providing libraries and device descriptions ¶ CODESYS offers the possibility to download missing libraries and device descriptions from a server. It is possible to use this functionality for your own

Usage of client certificates from an external certification authority ¶ The import of client certificates from an external certification authority can be done via a certificate signing request (CSR) o

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.