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

Library Documentation ¶ Note CODESYS LibDoc Scripting Collection This section is intended to clarify the current situation regarding documentation in the CODESYS source code. The introduction of the C

Documentation Areas ¶ Project Information ¶ Folder ¶ Declaration Header ¶ Member Declaration ¶ Enums, Structures, GVL’s ¶ Some other possibilities to mark up the comments. Actions and Transitions ¶ Th

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

Tool installation ¶ Note The CODESYS LibDoc Scripting Collection is now part of the CODESYS Library Documentation Support package. With this, the installing a complete Python environment is not necess

Script your Documentation ¶ Note Please install the CODESYS Library Documentation Support package. Without the installation of this extension it is not possible to use the possibilities of the CODESYS

Page Layout Setup ¶ The appearance of the documentation that is generated with the CODESYS LibDoc Scripting Collection can be customized extensively to individual requirements. Various adjustments are

Synchronization of Concurrent Execution ¶ The less concurrent parallel running processes have to be synchronized, the better. Each synchronization means an increase in complexity and thus the probabil

Asynchronous Job Execution ¶ The critical factor in many applications is the cycle time of a task. The smaller this can be, the more frequently the signals of the processes can be checked, which are t