From version 2.7, EPLAN P8 supports the data exchange via AutomationML (AML). If the macros provided by Beckhoff are used, most of the information required for the AML data exchange is already preset. The tabular representation “Rack” is suitable for the setting of the remaining information.
Hierarchical elements in EPLAN
In assigning the hardware to the topology, EPLAN uses a hierarchy consisting of
- ▪
- Configuration project – a configuration project includes all components that are to be exported together. Each configuration project must contain exactly one CPU for the AML data exchange with TwinCAT 3.
- ▪
- Station – a station includes all components that are located on a common terminal segment.
- ▪
- Rack – EtherCAT and KBus have exactly one rack per station. It has the number "0".
- ▪
- Position/slot – components in a rack are sorted in accordance with this specification.
The following drawing illustrates the use of these hierarchical elements in the AML data exchange with TwinCAT 3.
CPU
For IPCs and Embedded PCs, the macros can generally be used without further adjustments.
|
| Each terminal segment in the control cabinet corresponds to a station. | |
| EtherCAT has exactly one rack per station. This is defined at the head of the station (coupler/ CX/…). | |
Module is plugged into rack | One station and thus a new rack belongs to each CPU and each coupler. The entry for "plugged into rack" can therefore remain empty. | |
| This entry specifies the position in the rack. It starts in each rack with the head of the station (CPU or coupler) at "0". | |
| | |
| Exactly one CPU is intended per configuration project for the AML data exchange with TwinCAT 3. This is marked by setting the corresponding option. | |
| | |
Coupler
The property "PLC station name" must be adjusted for couplers. Otherwise the macros can be used without further adjustments.
|
| Each coupler is the head of a new station. All terminals in the same terminal segment must use the same station name. | |
| EtherCAT has exactly one rack per station. This is defined at the head of the station (CPU or coupler). | |
Module is plugged into rack | One station and thus a new rack belongs to each CPU and each coupler. The entry for "plugged into rack" can therefore remain empty. | |
| This entry specifies the position in the rack. It starts in each rack with the head of the station (CPU or coupler) at "0". | |
| | |
| | |
| Reference to the CPU via <Configuration project>.<Station name>.<CPU name> | |
| Optional: EPLAN expects the specification of a station type. It is not necessary to specify the station type for the initial import. However, if the data are transferred to EPLAN by means of an incremental export, the absence of the station type can lead to the coupler being displayed as "new". | Entered suitably e.g. Coupler, Switch, PortMultiplier |
Terminal
For terminals, the station name must correspond to that of the associated coupler. In addition, the slot in the rack must be entered.
|
| Each coupler is the head of a new station. All terminals in the same terminal segment must use the same station name. | |
| EtherCAT has exactly one rack per station. This is defined at the head of the station (CPU or coupler). This entry can therefore remain empty for the terminals. | |
Module is plugged into rack | With EtherCAT there is exactly one rack per station. All terminals are therefore plugged into rack "0". | |
| This entry specifies the position in the rack. It starts in each rack with the head of the station (CPU or coupler) at "0". | |
| | |
| | |
| Reference to the CPU via <Configuration project>.<Station name>.<CPU name> | |
Bus connections
The bus connections are generally configured completely in the macro. EPLAN expects there to be a bus connection in a PLC box and that no visible BMK is entered for the bus connection.
|
| Name of the connection according to the documentation | Entered suitably e.g. X001, X1, X2 Out |
| One configuration project is to be created per CPU for the AML data exchange with TwinCAT 3. | |
| Optional: If the option "Is Master" is selected, the master to be created is given the name specified here. | |
| If the option "Is Master" is selected, a new EtherCAT segment with an associated EtherCAT Master is opened on this bus connection. The terminal segment on a CX also opens a new EtherCAT segment, even if no explicit bus connection with the option "Is Master" exists for this. | |
| The AML data exchange is presently restricted to EtherCAT and KBus components. The setting "Other bus systems" is used for KBus. | |
| For EtherCAT components, the bus connections must be given different interface names, provided they are not EtherCAT distributors. | Entered suitably e.g. EC1, EC2, LAN1 |
| | Network/bus cable connection, general |
| If several EtherCAT segments/EtherCAT Masters are in use, the components must be assigned to their respective EtherCAT segment. This property can also be empty if only one EtherCAT segment exists. | |
PLC connections
The PLC connections are generally configured completely in the macro. EPLAN expects there to be a PLC connection in a PLC box and that no visible BMK is entered for the PLC connection.
During the AML data exchange a system task with image is generated, which contains the variables referenced via the symbolic addresses. The creation of the task variables as well as the linking between task variable and process object takes place automatically during the AML import.
|
| The channel name describes the process object for which a variable linking should be created. Various options are available for referencing. | Entered suitably e.g. Channel 1.Input |
| Optional: If the variable or the process object is to be provided with a comment, this can be stored as a function text. | |
| Optional: This property specifies the name of the variable with which the input/output is to be linked. | |
| Data type of the variable to be created. | Entered suitably e.g. Bool |
