Exporting PLC Configuration Files

Requirements for the export of the hardware data:

The bus configuration is defined via a configuration project. The configuration project has to be specified at all the associated PLC boxes and bus ports (Configuration project field in the PLC structure data and Bus data tabs in the property dialog).
The PLC type designation property or the Device description: File name property is filled at the PLC boxes that represent the main functions. The device identification is effected through these properties.
The CPU check box is activated (PLC structure data tab in the property dialog) for PLC boxes that represent a CPU.
PLC connection points of the type "Connection power supply" or "Card power supply" are not exchanged.

Requirements for the export of the network structures / bus structures:

The bus ports are represented in single-line and are connected with each other.
At the single-line bus ports all the fields in the Bus data tab of the property dialog are filled (Configuration project to Bus system and, if appropriate, Logical network: Bus port is master).
The Bus interface: Name property is filled at Ethernet-based bus systems.
The Plug designation property is filled in the PLC connection point tab of the property dialog.

Requirements for the export of the PLC connection points (input / output):

A CPU exists for the PLC connection point in the configuration project. The CPU name in the form [Configuration project].[Station ID].[CPU identifier] must be unique project-wide.
The PLC connection point has a symbolic address. The symbolic address must be unique within a CPU.
The data type (Boolean, byte, etc.) is specified at the PLC connection point.

Requirements for the export of racks:

The Rack field is filled (PLC structure data tab in the property dialog of the PLC box).
Modules on a rack are characterized by the fact that the fields PLC card is placed on rack ID and Position (slot / module) are filled.
The Position (slot / module) field remains empty at a rack or a head station.
EPLAN assumes that devices on the same rack are connected by means of a "backplane". This is not configured separately.

Tips:

Use the "edit in table" function to achieve effective editing and checking of the PLC data. There are already predefined schemes for different use cases which you can adjust to your requirements if necessary.
Check before the export whether the required data exist in the project. The check runs of the message class 004 "PLC / Bus" are available to this purpose. For selected PLC manufacturers there are predefined schemes in the Settings: Messages and checks dialog.
Before carrying out the export, check whether conflicting PLC data exists at the different representation types of a bus port. You can use check run 007010 for this purpose. To only keep the data at the single-line representation, use the compressing of projects with the compressing setting "Remove project data > Bus data at non-single-line bus ports".