Product Overview

The ABB Pluto S20 v2 2TLA020070R4700 Programmable Safety Controller is a programmable safety controller for machine safety systems that require configurable monitoring and coordinated safety logic. It can process signals from safety devices and control safety-related outputs according to the programmed safety application.

As part of the Pluto safety controller family, the S20 v2 can be used where several protective functions need to be managed within a common safety-control system. Typical functions include emergency-stop monitoring, guard interlocking, safety light curtains, two-hand controls, and other machine protection devices.

The controller works alongside the machine’s standard automation equipment. Normal PLC logic can manage production sequencing and process functions, while the Pluto controller handles defined safety conditions and the corresponding safety response.

The S20 v2 is suitable for machinery where safety functions need to be coordinated rather than implemented as isolated safety relay circuits. It can also be incorporated into distributed safety architectures where multiple safety devices and controllers exchange safety-related information.

Technical Specifications

Product Features

• Programmable safety controller for machine safety applications
• Pluto S20 v2 platform for configurable safety functions
• Supports centralized handling of multiple safety conditions
• Suitable for emergency-stop and protective-device monitoring
• Can be used with safety interlocks and access protection devices
• Supports programmable safety logic instead of relying solely on fixed-function relay circuits
• Suitable for automated machinery and production equipment
• Can operate as part of a broader machine safety architecture

Working Principle

The Pluto S20 v2 evaluates signals received from connected safety devices against the configured safety logic. The controller determines whether the required safety conditions are present before allowing the associated safety outputs to remain enabled.

For example, an emergency-stop circuit or guard switch can provide a safety input to the controller. If the device changes to an unsafe state, the configured logic responds by changing the relevant safety output. That output can then be used by downstream safety equipment to remove or inhibit hazardous machine operation.

Safety Devices → Pluto S20 v2 → Programmable Safety Logic → Safety Outputs → Final Safety Switching → Machine

Multiple safety conditions can also be combined within the programmed application. This allows machine functions such as guard monitoring, emergency stopping, reset control, and safe operating permissions to be coordinated within one safety-control system.

The controller therefore acts as the decision-making element of the safety chain, while contactors, drives, or other final switching equipment perform the physical interruption or inhibition of hazardous energy or motion.

Role in a Machine Safety Control Architecture

The Pluto S20 v2 occupies the programmable safety-control layer between field safety devices and the equipment responsible for stopping or inhibiting machine motion.

Safety Devices → Pluto S20 v2 → Safety Outputs → Safety Switching Devices → Machine

This architecture separates safety logic from the machine’s normal process-control functions. The standard automation controller can continue managing sequencing and production while the Pluto system supervises the safety conditions defined for the machine.

Industrial Applications

Installation and Maintenance

1. Confirm that the 2TLA020070R4700 model matches the intended safety-control application.
2. Review the machine safety architecture before connecting field safety devices.
3. Install the controller in the designated control-panel position.
4. Verify the power supply and terminal connections before energizing the controller.
5. Connect emergency-stop devices, guard switches, and other safety inputs according to the approved circuit.
6. Connect safety outputs to the intended downstream safety switching equipment.
7. Verify that the programmed safety logic corresponds to the actual machine safety functions.
8. Test each connected safety device during commissioning.
9. Verify that the appropriate safety output changes state when a safety condition is activated.
10. Inspect wiring and terminal connections when unexpected input or output states occur.
11. Recheck the safety program and connected devices after controller replacement or maintenance.
12. Perform a complete validation of all affected safety functions before returning the machine to normal operation.

Compatible System Components

Recommended Related Models

Key Advantages

• Provides programmable safety logic for multiple machine protection functions.
• Allows several safety conditions to be coordinated within a dedicated controller.
• Supports integration with emergency stops, guards, light curtains, and other safety devices.
• Separates safety-related decision logic from normal machine sequencing.
• Can interface with downstream contactors, safety relays, and safety drives.
• Suitable for automated machinery requiring configurable safety functions.

Technical FAQs

What is the difference between the Pluto S20 v2 and a conventional safety relay?

The S20 v2 can execute configured safety logic involving multiple safety devices and conditions, whereas a conventional safety relay generally performs a more limited predefined safety function. The programmable approach is useful when several machine safety functions must interact.

How should safety outputs from the Pluto S20 v2 be integrated into a machine?

The safety outputs should be connected to the downstream equipment responsible for the actual safety response, such as suitable safety relays, contactors, or safety-related drive functions. The final arrangement depends on the machine’s safety circuit and required protective function.

What should be considered when programming the Pluto S20 v2?

The programmed logic should correspond directly to the machine’s validated safety functions, including emergency-stop behavior, guard monitoring, reset conditions, and required safety responses. Changes to the safety program should be followed by appropriate functional validation.

What should be checked if a safety function does not reset after maintenance?

Check the state of every relevant safety input, the wiring of the affected device, reset conditions, configured safety logic, and the downstream safety circuit. A safety function that remains active may be caused by an open guard circuit, an emergency-stop condition, an incorrect reset sequence, or a downstream switching problem.