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

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

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

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

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

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

Dynamic Generation of FB Instances ¶ In CODESYS there are two possibilities of dynamically creating an FB instance: A.) By using the operators __NEW and __DELETE and a MemoryPool which has to be param

Interface Design ¶ Rule #5: Design smart Interfaces ( Required ) External Interfaces require a reduced set of parameter types (e.g. no POINTER). They should be optimized for the use with CFC. They sho

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