Windows software package for universal conversion between diverse standard protocols
ipConvOPC is a universal protocol converter for Windows operating systems* and is used for coupling different protocols. Based on ipConv, ipConvOPC basically offers the same functionalities. For conversion with ipConvOPC, established standard protocols are available for flexible use on existing hardware.
The following interfaces from the OPC family are offered particularly:
*) The following Windows operating systems are supported:
Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008 (R2), Windows 8, Windows 8.1, Windows Server 2012 (R2), Windows 10, Windows Server 2016
ipConvOPC can also be used in a Windows guest system in a virtual machine such as Hyper-V, VirtualBox and VMware if the required interfaces are available and the USB dongle can be passed through accordingly. Optionally ipConvOPC is also available with a soft license, which does not require a dongle.
System configuration is completely executed in a web browser. No other special configuration tools are required, a normal notebook with a network interface card and web browser are all that is needed.
ipConv in its current version 3 enables encrypted communication between web server and browser via HTTPS protocol.
The main menu provides access to all relevant functions of ipConv, showing the overall system status at a glance.
The following functions are available:
Switching operating mode OPERATIONAL (unattended station) or MAINTENANCE
(allows fully access to all ipConv functions)
Backup and restore the complete configuration
License management (ADMIN)
Installation of (DEMO-) licenses, (un-) limited and (un-) restricted licenses
This is an example configuration of a protocol stack (here IEC 60870-5-101, Master). All parameters are shown with their configured values, relevant measurement units and short descriptions.
A parameter value can be changed by clicking on the parameter name. A detailed description, if relevant, also pops up. The entered value is checked if it falls in the permissible value range or a drop down list offers a pre-selection of permissible values.
Only relevant parameters are displayed, for instance if the link layer type is set to "unbalanced", only the corresponding parameters are shown.
ipConv enables fast and efficient processing of great volumes of data points by allowing data import from tables. These tables are based on templates and may be processed with various spreadsheet programs such as Microsoft Excel. The extended use of formulae minimizes the data volume, substantially reducing the number of errors.
With protocol converters it is essential that the state of
all interfaces can be determined at a glance. This is all the more important, if
the available personnel at the facility does not have particular knowledge of the
The diagnostic data can be accessed with the "Diagnostics" button in the main menu. The most important information is given in plain text with the time in an easy to read way. Colored highlights indicate an ok / not ok state.
You can configure the type of information, descriptions and colors.
Plain messages, measured values, and also control commands such as a button for initiating a general poll can be shown.
With all communication applications, it is always essential
to know which data are transmitted via the protocol and how the data is
converted from one protocol to another. And it is even more important when
problems occur with transmission. ipConv features logging and archiving
functions for all data traffic.
ipConv allows you to keep track of the system state and information flow inside the converter by recording and archiving all information passing through a module for a given time period. This data can be recorded:
All data to/from ipConv sent and received via the relevant communication module
System messages, i.e. connection break-off, communication error messages etc.
Configuration and software error messages
The range of data recorded is defined by the logging level. This can be
changed dynamically (at runtime) or statically (in the configuration) for
The logging level defines the representation format for the sent or received information. Data can be
represented either in hexadecimal code or in decoded, symbolic form or both. This example shows the content of a logfile generated from an IEC 60870-5-101, Master protocol stack.
Data is stored directly in the easy to read ASCII format. Logfiles can be displayed, searched, or downloaded for offline diagnosis via the web interface.
All recorded data is archived cyclically, enabling you to keep track of
communication over a period of days or even weeks (depending on the data
ipConv is capable of representing and simulating all signals in a simple project-specific form, a functionality which is particularly useful for signal tests during commissioning. This greatly facilitates tracking down of wiring and configuration errors.
All data points can be shown in a hierarchical form defined by the configuration. Names, nesting depth and signal range can be freely chosen and configured for each project. This enables personnel not familiar with ipConv and the relevant protocol to access information.
The signal name, information type, value, quality identifier and time stamp (if available) are shown.
At the same time, data and commands can be simulated directly in the web browser. This functionality is very useful, if only one communication partner is connected (control station or RTU). Pretests can thus eliminate most configuration errors, even if the complete communication path is not available.
To meet even increased security requirements, ipConvOPC is fully capable of redundancy in combination with a second device.
Line redundancy (hot-standby)
Device redundancy (parallel operation)
With redundant protocol converters, reliability can be ensured, based on the "hot standby" principle. At any one time only one device assumes the active role, while the passive device monitors the active one and takes the initiative if it fails.
This minimizes downtimes due to maintenance work or component and interface outages, for example.
The redundancy coupling can be realized via Ethernet as well as over serial connections. If separate serial communication connections must be connected to both redundant devices, the CS channel switch will be applied.
Available Protocol Stacks
DNP V3.00, Master
DNP V3.00, Slave
ELCOM-90 Initiator, Client
ELCOM-90 Responder, Server
Simatic Fetch/Write, Master
HN Z 66 S 11/15, T63, Master
HITACHI HC4300, Master
IEC 60870-5-101, Dialup Master
IEC 60870-5-101, Master
IEC 60870-5-101, Slave
IEC 60870-5-103, Master
IEC 60870-5-104, Master
IEC 60870-5-104, Slave
IEC 61850, Client
IEC 61850, Server
Modbus TCP/IP, Master
Modbus TCP/IP, Slave
OPC AE 1.10, Client
OPC AE 1.10, Server
OPC DA 3.0, Client
OPC DAXML 1.01, Server
OPC DA 3.0, Server
OPC UA 1.02, Client
OPC UA 1.02, Server
RP 570, Master
RP 570, Slave
S7 Protocol, Client
SEAB 1F, Master
RWE Mosel Hydro Power Stations, Germany
OPC DA 3.0, ServerIEC 60870-5-104, Master
Andritz Hydro GmbH, A-Vienna, South Africa
IEC 60870-5-104, MasterOPC DA 3.0, Server
FHKW Linz, Austria
OPC DA 3.0, ServerIEC 60870-5-104, Master
Please note that the configurator is temporarily unavailable due to maintenance reasons.