This functionality is only available for certain module packages. Info / Copyright

Exporting PLC Configuration Files

Preparation for the export in the EPLAN project

Requirements for the export of the hardware data:

  • The PLC configuration is defined via a configuration project. The configuration project must be specified at all the associated PLC boxes and can be specified at the 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.
  • For PLC boxes that represent a CPU the CPU check box is activated and the CPU: Name property is filled (PLC structure data tab in the property dialog).
  • For an optimum PLC data exchange always configure all I/O connection points and bus ports of a device, even when they are not connected.
  • PLC connection points of the categories "Power supply", "Card power supply", "General" and "2 connection points" are not replaced.

Note:

If you only want to export a part of a network, the Configuration project field at the PLC boxes which are not to be exported should be filled nevertheless. You can enter any value here. If the PLC cards with empty configuration projects are connected within a network this can result in errors during the export.

Requirements for the export of the network structures:

  • The bus ports are represented in single-line and are connected with each other. During the PLC data exchange in the AutomationML AR APC format, multi-line representations and bus ports connected to each other are also taken into consideration.
  • At the single-line or multi-line bus ports the fields relevant for the PLC data exchange in the Bus data tab of the property dialog are filled (Physical network: Name 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.

Tips:

  • The logical network is a subset of the physical network. Therefore all bus ports of a logical network must also be assigned to the same physical network. With the cleaning up of projects you can use the Synchronize names of physical networks setting to transfer the name of the physical network from the bus master to the associated bus slaves within the same logical network.
  • For error-free export of network structures all bus ports of a physical network must be displayed as single-line or multi-line and must be connected to each other. With the check runs 004103 and 004104 you can check whether bus master and bus slave have the same value of the property Physical network: Name and if all bus ports of a physical network are connected to each other.

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. With the project correction you can use the Set data types setting to automatically set the data type on the basis of the identifier if the respective field is empty. Existing values are not overwritten.

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 pre-defined schemes are available in the dialog Settings: Messages and checks.
  • 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".

See also