|
Due to its technical properties and the support of numerous automation
suppliers, Profinet IO is set to become the global communication
standard for realtime Ethernet. The decision of the Automatisierungs-Initiative
Deutscher Automobilhersteller (AIDA, Automation Initiative for German
Automotive Manufacturers) to use Profinet with integrated operator
safety features wherever this provides technical and commercial
benefits for a specific application will also contribute to the
further acceptance of the system across many sectors. However, for
reasons of investment protection, the introduction of Profinet IO
in automation solutions is likely to be a gradual process. It is
therefore important that existing INTERBUS systems can be integrated
effectively into the Ethernet protocol.
The Profinet IO system could also be called "Ethernet as a
fieldbus" because the user sees the fieldbus devices in the
same way as in conventional fieldbus systems. The use of Profinet
IO provides access to the following advantages of the Ethernet communication
system:
- Integration into existing networks/infrastructure
- Increased availability due to redundancy
- No additional fieldbus interface for devices with Ethernet
interface
- Use of TCP/IP parallel to realtime communication
- Continuous operation on a device failure in star topologies
- Radio paths via wireless LAN
- 100 Mbps or higher bandwidth
These advantages must be balanced against the following INTERBUS
system functions, which are popular with users but are not yet provided
by Profinet IO:
- Low connection costs for basic field devices
- Excellent network diagnostics
- Easy device replacement
- No assignment of IP addresses/device names
- Topology detection
- Fiber optic cabling with optical regulation
- Quick connection and disconnection of devices
- Comprehensive range of field devices
- Use of existing investments and INTERBUS expertise
The combination of INTERBUS and Profinet IO offers all of the listed
advantages in one automation solution. It also protects investments
in INTERBUS products and solutions, and creates a future-proof migration
path from fieldbus-based to Ethernet-based communication. However,
the entire solution must be seamless and consistent without losing
any of the key properties of the individual systems. A special device,
the proxy, has therefore been developed to provide the network transition
between INTERBUS and Profinet IO.

The INTERBUS/Profinet proxy displays
INTERBUS devices in Profinet IO systems
The Profinet IO Device Model
The Profinet IO device model helps users to understand the various
concepts involved in the integration of INTERBUS into Profinet IO.
The model describes how the functions of an actual field device
are viewed by Profinet IO. This view must be the same for all field
devices in a network to enable communication regardless of the manufacturer
or device type.

The concepts developed by members of the INTERBUS Club for the integration
of INTERBUS into Profinet IO, based on the Profinet IO device model
In the Profinet IO system, every field device is represented as
an IO device. This type of device does not necessarily correspond
to the physical component: for example, one field device can contain
several logical IO devices. The IO device in turn defines slots
in which modules can be integrated, which comprise at least one
submodule that represents the actual functions. The Profinet IO
network provides the following services:
- Cyclic process data
- Parameters
- Channel diagnostics
- Alarms
Members of the INTERBUS Club and members of the "INTERBUS
Integration" working group of the Profibus User Organization
have used the device model to develop various concepts for the optimal
mapping of the INTERBUS system in Profinet IO.
Integration Concepts
The following integration concepts are possible based on the Profinet
IO device model:
- Transparent Integration
In transparent integration, every INTERBUS device is mapped to
a virtual IO device. The advantage of this option is that all
fieldbus devices can be viewed directly in Profinet IO and can
be addressed in exactly the same way as a device connected to
the Ethernet standard. However, a separate Ethernet frame of at
least 64 bytes must be sent for every IO device, even though INTERBUS
devices generally have very little process data. This means that
large lower-level bus systems create a high network load in the
Profinet system, which makes this integration model of limited
use for the efficient exchange of process data.
- Compact Integration
The entire INTERBUS system is mapped to one IO device with only
one module and one submodule, so that the entire INTERBUS process
image can be transmitted in one telegram. Although this offers
efficient process data transfer, the INTERBUS system can no longer
be structured in Profinet IO because the individual INTERBUS devices
are not visible. In addition, a separate engineering tool is required
for configuring the INTERBUS proxy.
- Modular Integration
In a modular integration concept, every INTERBUS device is mapped
to a separate module in an IO device. This means that the data
for all modules can be transmitted in one Ethernet frame, reducing
the network load in the Profinet IO system. The properties of
the INTERBUS devices remain available in the relevant submodule.
Another advantage is that no additional configuration tool is
required for the INTERBUS proxy because the creation of a modular
device must be supported by every programming system.
Following consideration of the advantages and disadvantages of
the various integration models, the first step is to work on the
specification of the modular concept.
Modular Integration
Figure 3 provides an overview of modular integration. To simplify
the view, the submodule level has been omitted because every module
contains only one submodule.

In a modular integration concept, slot 1 is reserved for the INTERBUS
master, while the slaves are assigned to slots 2 and above
Slot 1 of the Profinet IO device model is reserved for the INTERBUS
master. The cyclic process data channel, which is used for status
messages and control registers, can be used to request the status
of the INTERBUS system and to execute a special action such as connecting
and disconnecting devices. All events, which do not affect a specific
slot, such as general parameterization errors, are mapped to the
channel diagnostics of slot 1. Every diagnostic event is sent to
the control system using a corresponding diagnostic alarm.
All INTERBUS slaves connected to the master use slots 2 and above.
The order of the slots must correspond to the structure of the INTERBUS
system. Empty slots are not permitted. The cyclic process data of
a slot is assigned directly to the input and output data of the
individual INTERBUS slaves, while the Profinet IO parameters are
used for setting device-specific data (e.g., ID code or process
data length) and for mapping device-specific PCP parameters.
A key feature of the INTERBUS system is its excellent diagnostic
properties. All diagnostic messages are therefore available as Profinet
IO channel diagnostics and sent to the control system using diagnostic
alarms. The control system then displays the diagnostic event in
plain text.
Configuration Aspects
Profinet IO devices are described in GSDML (Generic Station Description
Markup Language), which is a further development of GSD (Generic
Station Description) used in the Profibus system. The file must
include the slots of an IO device as well as all the modules, which
can be integrated in the slots. Since the slaves of the INTERBUS
system are mapped to the modules of the IO device during fieldbus
integration, the GSDML file for the proxy should also include all
INTERBUS devices available on the market. This is neither practical
nor useful. Instead, the file contains universal modules with INTERBUS
parameters that can be set by the user. In addition, modules from
the FDCML files for INTERBUS slaves can be inserted in the GSDML
file for the proxy. FDCML (Field Device Configuration Markup Language)
used for the INTERBUS system is also based on XML technology, is
multilingual, and has comprehensive description options for INTERBUS
devices.

The INTERBUS device description language FDCML can also be
used for Profinet IO networks
The GSDML file for the proxy enables the user to set up the INTERBUS
system in any programming software using the Profinet IO configurator,
by simply inserting the modules into slots 2 and above according
to the bus configuration. In PC Worx automation software from Phoenix
Contact, INTERBUS is configured directly via FDCML files. GSDML
files are not required. The INTERBUS system is parameterized during
control system startup. Separate configuration in an additional
software tool is no longer required, which makes startup much easier.
Summary
The modular integration of INTERBUS into Profinet IO offers the
user the option of combining the specific advantages of both systems
to form a single seamless solution that is tailored to the relevant
application. Key features of the concept include minimal runtime
losses, the use of standard software for configuration, and the
direct configuration of the INTERBUS system in the control system.
In addition, the comprehensive diagnostic properties of the fieldbus
system can be integrated easily into the world of Profinet IO.
Download
Brochure "Profinet Basics"
|