External Libraries ¶ Like any normal CODESYS library, an external CODESYS library consists of reusable library elements. The difference to normal CODESYS libraries is that some of these library elemen
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
Deployment and Licensing ¶ Rule #7: Use the right method for deployment and licensing ( Required ) Deploy libraries only in compiled format (*.compiled-library). Everyone should be able to read “Proje
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
Developers best friends ¶ Attributes for expressing intended use cases, identifying real system properties and reacting with the live cycle of your plc application. We present here a collection of att
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
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
Naming Conventions ¶ Rule #10: Use clean Naming Conventions ( Optional ) The consistent use of a naming convention is the best way for clean code. (Checked by the Static Code Analysis [ 3 ] ) These ru
Library Development Checklist ¶ The library type is defined by one of the following Properties : “Placeholder” => Common Library , “IsContainerLibrary” => Container Library “IsInterfaceLibrary” => Int
AnyType ¶ TYPE AnyType : STRUCT pValue : POINTER TO BYTE ; diSize : DINT ; TypeClass : __SYSTEM.TYPE_CLASS ; END_STRUCT END_TYPE