TechTip Configuring PLC Devices With Device Description Files
TechTip Configuring PLC Devices With Device Description Files
TechTip Configuring PLC Devices With Device Description Files
A PLC configuration program cannot recognize on the basis of the structure of the device de-
scription file that it is a single device. For this reason two (apparently) independent devices
are exported.
EPLAN cannot detect that the devices are related during the data import from the AML file.
Since Version 2.9 this relation can be stored in the parts management. You can also find a
description in the TechTip "TechTip-Preparation-of-master-data-for-PLC-data-exchange".
Previously both devices were configured independently in EPLAN. Thus structure data could
be stored at the integrated module, amongst others:
PLC card is placed on rack ID
Position (slot / module)
Device description: File name and Device description: Index in file
The disadvantage here is that the integrated modules have their own DT even though they
are not real devices.
1
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
Since EPLAN Version 2.9 it is possible to combine the apparently independent devices via
the parts management as one device with PLC subdevices. To do this all other integrated
modules are entered as PLC subdevices at the part of the main device. You can also find the
details in the TechTip "TechTip-Preparation-of-master-data-for-PLC-data-exchange".
Advantages:
The integrated modules do not require their own DT.
The parts data and the configuration in the schematic correspond with the real devices.
Disadvantage:
An import in EPLAN requires corresponding parts data.
Important:
If no parts data is available, the relation of the devices cannot be detected during importing.
Therefore the integrated modules are imported as separate devices!
2
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
1 Station <GSD>/D
2 Rack <GSD>/R/DIM 1
3
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
The following data has to be entered at the individual PLC boxes according to the configura-
tion suggestion:
Row Rack Is placed on Position (slot Device descrip- Bus coupler /
the rack / module) tion: Index in head station
file
3 0 DIM 1
8 0 2 137
9 0 3 137
4
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
For the bus ports the Bus interface: Name property has to be specified during the configura-
tion (for example x1). The first bus port is also to be identified as Bus interface: Main bus
port: This bus port has all relevant bus data (for example Physical network: Bus ID / item
number).
For the PLC I/O connection points the connection point designations and channel designa-
tions should be specified so that the assignment to the connection points in the project is
unique.
Tab Properties:
Property Value
Note:
For the respective PLC subdevice, the index including context must be specified.
5
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
1 Station <GSD>/D
PD Channel is the module here for transferring the Process Data, the index (here: 5) de-
pends on the used module.
The following exist here:
A head station (Head Module) [Row 3]
The integrated module [Row 7]
An unused (empty) module [line 6]
6
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
The following data has to be entered at the individual PLC boxes according to the configura-
tion suggestion:
Is placed on Position (slot Device description: Index Bus coupler /
Row Rack
the rack / module) in file head station
For the bus ports the Bus interface: Name property has to be specified during the configura-
tion (for example x1). The first bus port is also to be identified as Bus interface: Main bus
port: This bus port has all relevant bus data (for example Physical network: Bus ID / item
number).
Tab Properties:
Property Value
7
TechTip
EPLAN Platform Version 2.9
Status: October 09, 2019
Depending on the process data module (PD Channel) used the associated index is specified
in the device description file for PLC subdevice 2.
Note:
For the respective PLC subdevice, the index including context must be specified.