empowering communication

Reliable and highly available automation systems: PROFINET S2 system redundancy with Hilscher

What do I need system redundancy for?

Depending on the industry sector and specific application, industrial networks place very different demands on the reliability and availability of automation systems. The higher these requirements are, the more the keyword redundancy plays a decisive role: in other words, the additional availability of functionally identical or comparable resources that enable a technical system to continue to function without disruption if individual system components fail.

In the following blog post, you will learn everything you need to know about common redundancy mechanisms, S2 system redundancy in particular and how Hilscher can support you in implementing them in PROFINET networks.

Which redundancy mechanisms does PROFINET offer?
A PROFINET controller icon on top, a PROFINET device icon on the bottom. In the middle is a PROFINET icon.
S1 redundancy:

PROFINET S1 does not actually describe a special redundancy configuration, but rather the conventional PROFINET standard. This means that one IO device has a PROFINET interface that can establish a communication relationship with one controller.

Two PROFINET controller icons on top, a PROFINET device icon on the bottom. In the middle is a PROFINET icon.
S2 redundancy:

With S2 redundancy, an IO device also has exactly one PROFINET interface, which can however establish up to two communication relationships with two redundant IO controllers. Data is usually exchanged via the primary connection. However, if this connection is faulty, data is exchanged via the backup controller.

Two PROFINET controller icons on top, a PROFINET device icon on the bottom. In the middle is a PROFINET icon.
R1 redundancy:

In this configuration, an IO device has two PROFINET interfaces, each of which is connected to a controller. If the primary connection fails, the same interface does not switch to the second controller, but the IO device switches to the second interface.

Two PROFINET controller icons on top, a PROFINET device icon on the bottom. In the middle is a PROFINET icon.
R2 redundancy:

R2 system redundancy combines the approaches of S2 and R1. The IO device therefore has two PROFINET interfaces, each of which has two communication relationships to redundant controllers. Depending on the type of system error, the connection is always restored via the fastest possible communication relationship.

S2 system redundancy: the efficient all-rounder

S2 system redundancy describes a redundancy at the control level in which two redundant controllers are used to ensure the continuous operation of a system. If one of the controllers fails, the second controller automatically takes over control without any downtime. This is particularly important in industrial applications where smooth and uninterrupted operation is critical. These include:

  • Critical process automation: Industries such as oil and gas, chemicals and pharmaceuticals require high reliability and availability. PROFINET S2 redundancy ensures that in the event of a controller failure, the backup controller can take over immediately. This guarantees the continuity of critical processes without interruptions.
  • Production with high availability requirements: In the high-performance production facilities used in automotive manufacturing or semiconductor manufacturing, for example, any unplanned downtime can lead to significant losses. S2 redundancy helps to maintain a smooth production flow by seamlessly changing the controller in the event of a fault.
  • Utilities and energy sector: Power plants, water treatment plants and other utility services rely on continuous operation. S2 system redundancy ensures that even if a control unit fails, operations can continue without noticeable interruption.

Compared to the R redundancies, which enable completely separate network segments, a redundant system can be achieved using S2 system redundancy with relatively straightforward means. In this case, a device only requires one network interface, i.e. just one communication controller. This makes it possible to connect a compact field device to a high-availability system without additional hardware. This type of redundancy is already sufficient for most application scenarios in factory automation and even applies to large parts of process automation. S2 redundancy can therefore be described as the efficient all-rounder among redundancy mechanisms.

PROFINET S2 system redundancy with Hilscher

Hilscher offers a netX PROFINET firmware for device applications that require PROFINET S2 system redundancy. This means that devices that use the netX 51, netX 90 and netX 100 communication controllers and products based on them (e.g. PC cards from the cifX family or embedded modules such as netJACK or comX) as network interfaces can be integrated into redundant systems with minimal effort.

In relation to the low investment, companies benefit in many ways from upgrading their standard devices to redundant counterparts. The advantages include

  • Increased system availability: Redundancy minimizes downtime as the system automatically switches to the secondary controller if one controller fails.
  • Reduced maintenance costs: As the systems are still operational, maintenance work can be carried out without haste, reducing the cost and effort of emergency maintenance.
  • Fast recovery from faults: The automatic switchover to the secondary controller enables fast recovery from faults, which increases productivity and reduces downtime.
  • Increased safety and reliability: The use of system redundancy minimizes the risk of a complete system failure, which is particularly important in safety-critical applications.
  • Flexible adaptation to network requirements: S2 redundancy allows networks to be flexibly adapted to specific requirements and environments, providing a customized solution for various industrial applications.

By using PROFINET S2 system redundancy, companies can therefore significantly improve the availability and reliability of their production systems, leading to an increase in efficiency and a reduction in downtime costs.

 

 

 

A tray of embedded modules with a netX chip onboard in a production machine. A red gleam is seen in the background. A small golden needle for testing comes from the top pointing at the tray.
Our PROFINET controllers

这是用于现场总线和实时以太网从站的,配备存储器控制器的网络控制器

 

最小的多协议SoC

 

用于现场总线和实时以太网(主站和从站)的网络控制器

 

Our PROFINET PC cards

PCI Express- 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

用于扩展温度范围 PCI Express - 实时以太网的 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍半尺寸 MiniPCI Express- 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

‍实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

M.2 2230 Key A+E 实时以太网 PC 板卡

用于基于 PC 的自动化通讯板卡

M.2 3042 Key B+M 实时以太网 PC 板卡

用于基于 PC 的自动化通讯板卡

‍实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

带 M12 连接器的实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

M.2 2242 Key B+M 实时以太网 PC 板卡

用于基于 PC 的自动化通讯板卡

‍Low Profile CI Express- 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍‍带有 NVRAM Low Profile CI Express- 实时以太网的 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍‍带有 NVRAM Mini PCI Express - 实时以太网的 PC ‍板卡

用于基于 PC 的自动化通讯板卡

MiniPCI Express- 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

带 M12 连接器的实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

配有 NVRAM 和扩展温度 Mini PCI Express 实时以太网的 PC 板卡

用于基于 PC 的自动化通讯板卡

不带散热器 Mini PCI Express - 实时以太网的 PC ‍板卡

用于基于 PC 的自动化通讯板卡

用于扩展温度范围 MiniPCI Express - 实时以太网的 PC ‍板卡

用于基于 PC 的自动化通讯板卡

PCI - 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

CompactPCI- 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

MiniPCI - 实时以太网 PC ‍板卡

用于基于 PC 的自动化通讯板卡

‍实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

带 M12 连接器的实时以太网独立网络接口

用于基于 PC 的自动化通讯板卡

Our embedded modules for PROFINET

通讯模块双端口内存 实时以太网

用于自动化的灵活通讯模块

SPI - 实时以太网从站通讯模块

用于自动化的灵活通讯模块

通讯模块双端口内存 实时以太网

用于自动化的灵活通讯模块

SPI - 实时以太网从站通讯模块

用于自动化的灵活通讯模块

comX 评估板

适用于所有 comX 类型的开发平台

‌netX 90 芯片载体 - 预加载协议栈

经过全面测试和加载的超紧凑 netX 90 设计

NetX 90 芯片载体,具有额外的存储器 预加载协议栈

经过全面测试和预加载的超紧凑 netX 90 设计

netRAPID H90 评估板 - 实时以太网和现场总线

配备 NRP H90-RE\F8D8

具有附加存储器的netx51芯片载体 - 实时以太网从站

即可焊锡的 netX 设计,邮票大小

netRAPID 51 评估板 - 实时以太网

配备 NRP 51-RE

具有变压器的‌netX 52芯片载体 - 实时以太网从站

即可焊锡的 netX 设计,邮票大小

netRAPID 52 评估板 - 实时以太网

 

PCI Express- 实时以太网可交换模块

可随时安装在输送链中

SPI - 实时以太网从站可交换模块

可随时安装在输送链中

可交换模块双端口内存 实时以太网

可随时安装在输送链中

netJACK 评估板双端口内存

适用于具有双端口内存或SPI的每个netJACK

netJACK 评估板 PCI Express

适用于任何带有 PCI Express 的 netJACK

用于光纤电缆的DIL-32通讯IC - PROFINET IO 设备

用于带有光纤电缆连接的简单从站设备的通讯

‌不带散热器的 DIL-32 通讯 IC - 实时以太网从站

用于无自带主处理器的简单从站设备的通讯

‌DIL-32 通讯 IC - 实时以太网从站

用于无自带主处理器的简单从站设备的通讯

带光纤电缆的 netIC 评估板 - PROFINET IO 设备

带光纤电缆的评估平台netIC

用于光纤电缆的DIL-32通讯IC - PROFINET IO 设备

用于带有光纤电缆连接的简单从站设备的通讯

netIC 评估板 - 实时以太网从站

单个评估平台,适用于所有实时以太网协议

‌DIL-32 通讯 IC - 实时以太网从站

用于无自带主处理器的简单从站设备的通讯

Our gateways for PROFINET

媒体交换机 SPE 至 RTE

使用实时以太网协议连接单对以太网网络

CANopen 到以太网的网关

经济的入门级网关,用于简单转换

CC-Link IE Field从站到 PROFINET IO 设备的网关

CC-Link IE Field与PROFINET之间的数据耦合

实时以太网到 DeviceNet 的网关

用于高要求转换的高端网关

PROFIBUS DP 到以太网的网关

经济的入门级网关,用于简单转换

网关实时以太网到实时以太网

两个实时以太网网络之间的数据传输

网关实时以太网到Modbus RTU、3964R或串行(ASCII /可编程)

用于高要求转换的高端网关

DeviceNet 到 以太网的网关

经济的入门级网关,用于简单转换

连接头形式的 PROFINET / PROFIBUS 代理服务器

升级 PROFIBUS 从站到 PROFINET

网关串行(ASCII)或Modbus RTU至以太网

经济的入门级网关,用于简单转换

实时以太网到 CC-Link 从站的网关

用于高要求转换的高端网关

CC-Link 从站到以太网的网关

经济的入门级网关,用于简单转换

实时以太网到以太网的网关

用于高要求转换的高端网关

实时以太网到 PROFIBUS DP 的网关

用于高要求转换的高端网关

实时以太网到 CANopen 的网关

用于高要求转换的高端网关

以太网 LAN PROFINET IO 控制器

用于 DIN 导轨的 LAN 控制 PROFINET IO 控制器

以太网LAN实时以太网多协议

用于DIN导轨的局域网控制实时以太网主站

PROFINET IO 设备到 SmartWire-DT 的网关

SmartWire-DT 连接到实时以太网 PROFINET 系统

Related links
A photo collage showcasing various Hilscher products

从交钥匙产品到高度集成的解决方案和补充软件,赫优讯是您工业通讯的合作伙伴。了解我们如何帮助您将您的机器联网提升到一个全新的水平!

The inside of a factory with a conveyor belt and grey boxes. On the right side is the PROFINET logo.

PROFINET IRT not only requires short cycle times, but also deterministic behavior. Industrial networks must therefore meet certain requirements. Find out more about PROFINET IRT with netX from Hilscher here!

A photo of the male and female customer support phone operator with different internationality
Customer Center / Sales: Hilscher Systemautomation (Shanghai) Co. Ltd.

You've got questions? We've got the answers!