Universal protocol converter for highest degree of flexibility
ipConv is a universal protocol conversion solution for coupling a
wide range of different protocols. Its architecture (ipConv Architecture)
ensures maximum independence between the different protocols used. As protocols
are kept completely separate with respect to data transmission methods and
information representation, the solution greatly facilitates system planning and commissioning. For instance, the different protocols can be tested separately.
ipConv provides the foundation for specialized products such as ipConvLite
and ipConvOPC. ipRoute and ipRouteDialup too are based on
ipConv. The universal solution ipConv has been designed for cases where
special project-specific requirements exceed the capabilities of these
ipConv is available as a software package or together with the
appropriate hardware. The MEC2 system supports decentralized applications and IPC191V4 19" 1U
has been designed for centralized use.
For customers who already have the necessary hardware, we offer ipConv as a
pure software solution. ipConv runs in the Windows and various Linux environments.
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 first page 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
Excel Import The Excel file can be imported directly (Generation and import of CVS files is no longer necessary)
SNMP agent Transmission of system and status messages to the SNMP client
The following information are now also displayed in the history: failed logins, change of operating mode, software update, recognized power outages, system stops due to security functions (e.g. device temperature)
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
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 on the first page. 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
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, Slave protocol stack.
Data is stored directly in the easy to read ASCII format. Logfiles can be
downloaded via a web interface for offline diagnosis. Or you can keep
track of the communication online via the TCP/IP "telnet" service.
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.
A command-oriented interactive tool enables users to access all information
pertaining to protocol-specific addressing. This expert access mode is always
possible and requires no explicit configuring.
Implemented Protocol Stacks
ANSI X3.28, Master
CDC Type II, Slave
CDC Type I, Slave
DNP V3.00, Master
DNP V3.00, Slave
ELCOM-90 Initiator, Client
ELCOM-90 Responder, Server
Simatic Fetch/Write, Master
Dr. Graband & Partner GmbH, Master
HN Z 66 S 11/15, T63, Master
HN Z 66 S 11/15, T63, Slave
HITACHI HC4300, Master
HITACHI HC4300, Slave
Indactic 21, Master
Indactic 23, Master
Indactic 23, Slave
Indactic 33/41, 2033, Master
Indactic 33/41, 2033, Slave
IEC 60870-5-101, Dialup Master
IEC 60870-5-101, Master
IEC 60870-5-101, Slave
IEC 60870-5-103, Master
IEC 60870-5-103, Slave
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 DAXML 1.01, Server
OPC UA 1.02, Server
Profibus-DP, Slave (ORSI)
Profibus-DPV0, Slave (Extended Version)
SISA, QD2 Slave
RP 570, Master
RP 570, Slave
Sinaut 8FW (PCM), Slave
SEAB 1F, Master
SEAB 1F, Slave
Sinaut ST1, Slave
Simatic TDC, Master
Telegyr 065, Master
Telegyr 102, Master
Telegyr 809, Master
Telegyr 809, Slave
Tracec 32, 62, 92, 92P, 122, 130 & 142 Master
IPC191V4 19" 1U
Successor of the industrial PC IPC191V3 19" 1U - up to three times faster and many more interfaces