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
How to change a library ¶ Note Compatibility: Compatibility of two libraries usually means that they react in the same way according to the requirements of an application. Important After changing a l
MEMORY_AREA ¶ Global Enum Type __SYSTEM.MEMORY_AREA {attribute 'qualified_only'} TYPE MEMORY_AREA : ( MEM_UNKNOWN := -1 , MEM_MEMORY := 0 , MEM_INPUT := 1 , MEM_OUTPUT := 2 , MEM_RETAIN := 3 , MEM_GLO
Working with external optional Libraries ¶ Optional external libraries serve to make optional runtime system components available in IEC. Optional means here that a component cannot be integrated in a
Library Types ¶ In CODESYS, a differentiation is made between the following types of libraries: Common libraries Container libraries Interface libraries End User libraries For each type, there is a ch
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
Formatting Commands (Overview) ¶ A reStructuredText document consists of body (or block-level elements) and it can be structured in sections. Sections are indicated by the title style (underlines and
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
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
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