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
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
SAFETY CERTIFICATION Please note that the documentation on the following pages is provided for informational purpose only. For limitations and information regarding safety or certification, please con
CODESYS Safety Extension CODESYS Safety Extension is software for programming safety controllers. CODESYS Safety Extension is suitable for the development of safety applications as application softwar
Access Protection In order to ensure access protection to the standard controller and the safety controller, the notices shown below and the notices in the CODESYS Safety User Manual (chapter: "IT Sec
