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

Importing PLC Configuration Files

In EPLAN, PLC configuration files generated or edited with external PLC configuration programs can be imported. These configuration files contain the rack structures and - in as far as they exist - the network structures. The format of the import file can be selected from a drop-down list in the Import PLC data dialog for many common PLC configuration programs . The data from the import file is assigned to the EPLAN properties based on the selected format.

During importing EPLAN supplements item data such as unused inputs / outputs from the parts data. A well-maintained parts database facilitates the further usage of the imported data.

Part allocation

When importing PLC configuration files, a part is entered at the main functions that are created, if a suitable part is found in the parts database. If no suitable part is found, a simple PLC box is generated and a corresponding message is output.

A part is suitable for a device if either the PLC type designation property or the Device description: File name property in the import file and the parts management match. The PLC type designation property is compared if no Device description file is specified. In the simplest case the PLC type designation corresponds to the order number. After the import, the parts data is automatically synchronized with the parts database. In the process parts that exist in the parts database, but not yet in the project, are inserted into the project.

Supporting of placeholder characters during the part allocation

The PLC configuration files can contain similar devices that only differ in certain characteristics, such as their use in different environmental conditions. The programming of the PLC software is identical for these devices. Only the part to be used respectively differs depending on the field of use. The order numbers, type designations or similar data of these parts often only differ in one or a few positions. Placeholders such as "*" and "?" are often to this purpose in the PLC configuration files of various manufacturers. During the import these data are compared with the PLC type designation - depending on the selected format. If several parts with suitable PLC type designations are found in the parts database, the first one found is assigned automatically. The messages generated during the import of the module-specific check run 004057 can be used to find the corresponding functions in order to assign these to a different part.

Assignment of connection point designations

In many cases, the addresses are identifying in the PLC configuration files and not the PLC connection point designations as in EPLAN. If a PLC configuration file does not contain connection point designations then, on import, connection point designations with leading question marks are assigned. In this process, the connection points are sequentially numbered from "?1" to "?n" for each PLC card.

If the PLC configuration file contains the PLC type designation and the corresponding parts exist in the parts management, the connection point designations from the function templates are automatically assigned to the Signal connection points (i.e., the digital or analog inputs and outputs). The connection point designations are assigned in the same sequence as the function templates are sorted in the parts management. The function templates must therefore be sorted in the parts management according to the channel sequence. Power supply connection points are not taken into account by the assignment process and may need to be manually assigned.

PLC connection points that could not be assigned to a part retain the question mark in their designation and must be subsequently manually assigned.

Assignment of properties for different representation types

The following behavior applies to the Symbolic address and Symbolic address (automatic) properties:

The same behavior also applies to the following properties:

The following behavior applies to the Function text and Function text (automatic) properties:

See also