Safety Logic The Safety Logic node exists for reasons of symmetry to the standard controller. It identifies the device as a PLC, but has no additional meaning in the safety controller. The Safety Logi
Application (Safety) object The objects relevant for the safety controller and its programming are located below the safety controller. Directly below them is always the symbolic node point Safety Log
Overview of Logical I/Os Principle of the logical I/Os The logical I/Os serve the exchange of data between the standard and safety controllers. Two types of data can be exchanged: global variables and
Usage Types of the Logical I/Os Logical I/O of a Safe Physical Device These logical I/Os are used for the exchange of safety-oriented I/Os between the safety PLC and the standard PLC. The safe field d
Usage of the Logical I/Os Each mapping variable (channel variables) declared in the I/O mapping of a logical I/O and all created instances of the logical I/Os of safe devices and of standard devices a
Safety POUs POUs (Program Organization Units) are the programming objects of CODESYS Safety Extension which are declared as either programs ( PROGRAM ) or function blocks ( FUNCTION_BLOCK ). The follo
Safety task Exactly one Safety Task must exist below the safety application object in the device tree. This safety task calls the programs (POUs of type PROGRAM ) of the safety application object acco
CODESYS Safety Extension CODESYS GmbH Version: 4.2.0.0, August 2024 www.CODESYS.com Last update: Fri, 9 Aug 2024 07:27:41 Please note that not all CODESYS functions are available in all countries. For
