IPCOMM, ipConvOPC Use Cases

Both servers communicate simultaneously with the substations, so that both systems have an identical database. The OPC client can decide which server to access for data.

ipConvOPC as Node

ipConvOPC can also assume the tasks of a node. On the one hand, an HMI system is supplied with data via the OPC interface. On the other hand, a superior control station can be supplied with data via a different protocol (e.g. SEAB 1F, Sinaut ST1 etc.).

This concept is particularly attractive if obsolete control systems that need to be replaced by more modern ones. Especially during the transition stage, it is very important that both systems can be supplied with data.

Coupling of IEC 870-5-101 substations over ipEther232 to ipConvOPC

Combining ipConvOPC with ipEther232 - The RS232/Ethernet Converter permits the implementation of an interesting solution where remote IEC 60870-5-101 substations are connected via TCP/IP.

With {{ipEther232}, a dedicated point-to-point line is no longer necessary as all communication is effected via the network. This concept was implemented in the BLS AlpTransit - Lötschbergtunnel project.

Coupling of IEC 870-5-101 substations over ipRoute to ipConvOPC

The combination of ipRoute and ipConvOPC offers a smart solution for connecting visualization systems to IEC 60870-5-101 substations.

With ipRoute, the usually redundant servers can still be simultaneously supplied with data, should there be only one line for each substation.

Communication between server and ipRoute is implemented via IEC 60870-5-104 (TCP/IP). This means your server needs no extra upgrade with serial interfaces (which again might reduce server availability).

Of course, ipRoute can also be operated in redundant mode, meeting even the highest demands on availability.