Step 3: Create Submodule "Switch Simple" The second switch module, which we want to declare, is a simplified one with only two states: on and off. Therefore a module declaration and a function block h

Step 4: Create Submodule "Light" As it was done before for the Switch and the SwitchSimple , for the module Light , a module declaration Light , a function block Light and an interface ILight have to

Step 5: Create Submodule "Light simple" The simple light, which is created now, will work together with a simple switch, but can be adapted from Light above, anyways. Therefore a new module declaratio

Step 6: Implementation Switches For the implementation of the functionality of the module Switch we use the method CallPrioMediumStart from Module by overriding it with our own implementation. We choo

Step 7: Compose Modules After successful scanning the declarations, all modules are available for further use, so that an example application can be composed. Therefore the modules are added to the mo

Library: Mechatronics Tip The Mechatronics library is meant to be an example for a simple (and not complete) implementation of a mechatronic unit with sequential execution. It does not meet all the re

Module Declaration Editor A module typically represents a mechatronic component but can also be a pure software function. It contains all engineering aspects covered by CODESYS . A module has a functi

Module Declaration The declaration of modules is done with an own description language which is similar to the declaration of variables in structured text (ST) code. Format of the module declaration A

Initialization of Module Instances (Online Change) Initialization and reinitialization of module instances and proxy instances (online change) The method IBaseInstance.Init(bOnlineChange : BOOL) ) is

Section: MetaData The section MetaData contains the description, category and icons (with size 16x16 pixel and 32x32 pixel). SEC MetaData //optional: yes, modifier: [UPDATE]] Desc := <description>; //