4. Graphical user interface

4.1. Overview

This section gives an overview about the graphical user interface:

../_images/overview.png
The graphical user interface is divided into five parts:
Menu/Tool/Status bar:

Shows current status or mode of the EC-Engineer and allows the user to change it.

Project Explorer:

Shows different views of the current network configuration

Device Editor:

Show information about the selected device, like process variables.

Short Info:

Show short information about selected device, like name, description or vendor.

Messages:

Shows notifications which occur e.g. when the EtherCAT Device has changed its operation state or a SubDevice has been removed from (or added to) the EtherCAT network.

4.3. Project Explorer

4.3.1. Configuration Mode

There are three topology visualisation views:

Classic View
../_images/classic-view.png

This is a tree view with multiple levels.

Flat View
../_images/flat-view.png

This view shows all SubDevices in a flat list, as they are connected in the EtherCAT network.

Topology View
../_images/topo-view.png

This view shows a graphical tree of all SubDevices, as they are connected in the EtherCAT network.

The context menu of one or more selected SubDevices has the following entries:
Append SubDevices:

Appends a new SubDevices

Remove SubDevices:

Deletes the selected SubDevices

Cut/Copy/Paste:

Extended clipboard operations, which should help the user to move or multiply existing SubDevice definitions.

Enable SubDevices:

Appends disabled SubDevices to the process image at the previous position. If this is not possible, the SubDevice will be marked as “not connected” and the user can append the SubDevice by using “cut” & “paste”.

Disable SubDevices:

Removes the SubDevices from process image and from the exported ENI file, but keeps the SubDevice as “disabled” in the project.

Reload ESI data:

Reloads ESI data which are stored in the project file from global ESI cache (after adding a SubDevice to the project the ESI data will be stored in the project file).

Export SCI:

Exports a SCI file. A SCI file is like an ESI file but preconfigured. So it is possible to create a fixed SubDevice which can be added to the configuration and is working out of the box.

Change SubDevice:

Opens the following dialog, where the user can select a compatible SubDevice (this is helpful, if the user wants to update the SubDevice to a new revision and keeps his configuration). This is also used to change from an ESI to a SCI file.

../_images/change-slave.png
Import Beckhoff SubDevice Description, to import SubDevice settings from TwinCAT (or ET9000)
Import SubDevice settings from “Beckhoff SubDevice Description” files
  • Open project in TwinCAT

  • Select SubDevice to export

  • Main menu “TwinCAT”

  • Selected Item

  • Export XML Description

  • Import the exported file (imported will be MDP configuration, PDOs, DC settings, …)

Import init commands of SubDevice from “Beckhoff Init Command Description” files
  • Open project in TwinCAT

  • Select SubDevice to export

  • Open tab “Startup”

  • Context menu: “Export to XML

  • Import the exported file (imported will be the exported init commands)

If user tries to append SubDevice he will see the following dialog:
../_images/select-slave.png
Filter

Search: Keyword to filter the SubDevices by type name. Vendors: List of all available vendors. User can filter all SubDevices by selecting the desired vendor from the list. If it makes sense, the recommended vendor is already preselected, e.g. if you try to append a SubDevice to an E-Bus. Show Hidden SubDevices: Shows also hidden SubDevices (e.g. with older revisions, if newer SubDevices are available) Show Preconfiguren SubDevices: Shows also SubDevices from SCI files

Connection

Select the port where the predecessor device is connected

List of available SubDevices

User can select the SubDevice which should be added, be expanding the three levels: vendors, groups and the SubDevices themselves. The 3rd level consists of three parts: Type name, description and the revision number.

Number of SubDevices

User can change this value to add more than one SubDevice of the same type.

Apply

Add SubDevices of the same and different type, the dialog will automatically reopen after appending the previous SubDevice. The number of SubDevices must be set at “1” to use this function.

Ok

Add SubDevices of the same type, based of the “Number of SubDevices” selected.

4.3.2. Diagnosis Mode

There are three topology visualisation views:

Classic View
../_images/diag-classic.png

This is a tree view with multiple levels.

Possible device states:

ecatstate_init Init Bootstrap

ecatstate_preop Pre-Op

ecatstate_safeop Safe-Op

ecatstate_op Op

Flat View
../_images/diag-flat.png

This view shows all SubDevices in a flat list, as they are connected in the EtherCAT network.

Possible device states:

ecatstate_init Init Bootstrap

ecatstate_preop Pre-Op

ecatstate_safeop Safe-Op

ecatstate_op Op

Topology View
../_images/diag-topo.png

This view shows a graphical tree of all SubDevices, as they are connected in the EtherCAT network.

Possible device states:

ecatstate_init Init Bootstrap

ecatstate_preop Pre-Op

ecatstate_safeop Safe-Op

ecatstate_op Op

Possible port states:

cable-quality_bad Bad Cable Quality

cable-quality_constricted Constricted Cable Quality

cable-quality_good Good Cable Quality

If cable quality is constricted or bad, please check the error counters of the SubDevice (for more information about the extended diagnosis, see Extended Diagnosis).

4.4. Device Editor

This Editor gives the user the possibility to read and write information of the selected device or SubDevice:
../_images/slave-general.png

4.5. Short Info

This window shows short information about selected device, like name, description or vendor:
../_images/short-info.png

4.6. Message Window

Shows notifications which occur e.g. when the EtherCAT MainDevice has changed its operation state or a SubDevice has been removed from (or added to) the EtherCAT network:
../_images/message-view.png