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

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

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

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

Error Handling ¶ Rule #6: Implement an user friendly Error Handling ( Required ) Return only error codes which are documented within your library. Never simply return the original error code from sub

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

Templates ¶ Rule #8: Not from scratch - Use Templates ( Optional ) CODESYS provides a rich set of project templates. They are a good starting point for successful library design. See: Common Behaviour

Project Structure ¶ Rule #9: Reuse a well-known Project Structure ( Optional ) Every one find parts of the project much easier, if you use a well known project structure. In order to make orientation

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