Static Analysis ¶ Note The CODESYS Professional Developer Edition provides a tool for static code analysis . A rule set is included for automatically checking the naming convention described above. Un

Parameterization with parameter lists ¶ Implementation Details The language model of a certain library in a certain version is loaded only once in a project. This means that if, for example, the libra

Parameter Handling ¶ There are several ways for supplying values (from the caller) to a function, a function block or its methods (the callee). These values are necessary to influence the implemented

Visibility Control ¶ Visibility modifiers also none as access modifiers can be applied to some elements of CODESYS project or library. CODESYS will provide two groups of these modifiers. Attributes fo

Advanced Topic’s ¶ Duration, Date and Time Dynamic Generation of FB Instances Segmented Buffers Synchronization of Concurrent Execution Asynchronous Job Execution Multicore - Tools Providing libraries

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

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.