- December 05, 2018
- Beckhoff Automation
December 5, 2018 – Beckhoff announced three I/O modules for their TwinSAFE safety controllers, which permit adaptation to the specific safety requirements of individual machine concepts. The ability to distribute the intelligence of an entire safety application across multiple TwinSAFE Logic-capable I/O modules means implementation of increasingly modular architectures. These safety architectures can adapt to varied system requirements.
With the Beckhoff safety controllers based on the established EL6910 TwinSAFE Logic terminal, it is possible to adapt the TwinSAFE system even more specifically to the exact requirements of a machine concept as well as to a broader spectrum of programmable safety applications. The I/O components include:
- EL1918 TwinSAFE EtherCAT Terminal: digital terminal with eight safe inputs
- EL2911 TwinSAFE EtherCAT Terminal: safe potential supply terminal with four safe inputs and one safe output
- EP1957-0022 TwinSAFE EtherCAT Box: IP67-protected digital combi module with eight safe inputs and four safe outputs
Just like the TwinSAFE Logic-capable I/O and motion products that are already available from Beckhoff, the three I/O modules can be used as controllers for the direct execution of customer-specific safety projects. A special feature is their communication capability. Like a dedicated controller, the safety project on the corresponding TwinSAFE I/O component can establish direct communication relationships with other safety-relevant devices and preprocess the data internally. This makes it possible to implement granular machine modules with distributed safety applications. The central safety controller, if it exists in the application scenario, only needs to process the data already accumulated.
Safety projects can be modularly designed in TwinCAT software as usual. However, the new customizing function enables each module to be configured into the following operating modes:
- temporary deactivation
- permanent deactivation
With the corresponding configuration of replacement values for the interfaces between the different modules. For example, a single safety project can be used for an entire family of machines by deactivating any modules that are not needed according to the given application requirements.