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.

Referencing other Libraries ¶ Rule #4: Use the right way for referencing other Libraries ( Required ) Common Libraries: Placeholder Reference Interface Libraries: Newest Constraint Container Libraries

Library Development Summary ¶ Contents Introduction Concepts and Elements Library Types Placeholder Library Prefix Library Categories Library Properties Behaviour Model and Interface Design Static Ana

Introduction ¶ This document summarizes the most important topics around the area “How to Develop CODESYS Libraries”. Reusability matters It’s a lot of work to design, build, test, and maintain a CODE

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