EtherCAT Devices tab

The EtherCATClosed Ethernet ofr Control Automation Technology. EtherCAT® is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT is to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs. Devices tab lists all the EtherCAT devices and provides for the ability to discover and map their use.

EtherCAT Summary Form

Figure 1: EtherCAT Devices Summary Form

First generation AKD drives support one axis per drive, while AKD2G drives support two axes per drive.
When configuring drives in the EtherCAT Devices tab, you need to designate which motion axis applies to each drive axis, which is the actual axis the drive controls.

EtherCAT Devices
Item Description
Show only drives

This option hides all EtherCAT slaves from the list that are not drives.

Scan Devices

The KASClosed Kollmorgen Automation Suite RuntimeClosed In computer science, runtime (or run-time) describes the operation of a computer program, the duration of its execution, from beginning to termination (compare compile time). In KAS, runtime refers to the virtual machine that manage the program written in a computer language while it is running. sends EtherCAT messages to discover the physical devices and modules present in the network.

See Scan Devices.

Name, Vendor, Product, and Model
FWClosed Firmware Version
  • For Kollmorgen drives, the firmware version is displayed on the conditions that: 
  • For other devices, the firmware version is displayed if the Scan Devices routine was successfully run and the device supports reading this information over EtherCAT (i.e., it uses CoE object 0x100A:0).
  • Otherwise (Unknown) is displayed.
  •  
  • If a Kollmorgen drive is showing the firmware version as "Unknown", the drive has valid resident firmware (from which to boot), but does not have valid operational firmware.
    Download and install the latest operational firmware and reboot the AKD / AKD2G.
Drive Axis Number
  • This number designates which axis, of those available on a drive, is being defined.
  • For most drives, this number is a "1", but for AKD2Gs, there are two entries:
    • Drive Axis Number 1
    • Drive Axis Number 2
Mapped to Axis

For each drive, it is displayed if it is:

Simulated

Used to simulate the device, which means that the device is not used and no communication to this device is performed through the fieldbusClosed An industrial network system for real-time distributed control (e.g., CAN or PROFIBUS, Sercos®). It is a way of connecting instruments in a plant design..

Save parameters to NV memory
Upgrade Firmware
  • This command triggers a firmware upgrade for the selected drives.
  • Use Ctrl+A shortcut to select all drives.
  • For more details, see the FAQ Setup section.

Scan Devices

The scan process allows these tasks:

Figure 2: EtherCAT Network - Physical View

EtherCAT Network - Logical View

K-Bus

E-Bus

Figure 3: EtherCAT Network - Logical View

During the scan operation, all physical devices connected to the EtherCAT network are discovered and identified.

The status of devices can be determined by their icon in the logical view.

EtherCAT device icon descriptions
Icon Meaning Description
(device icon) Normal

The device has been added by scanning the system.

The associated ESI file has been found.

The icon varies by device, but is the icon set by the manufacturer in the ESI file.

Excluded

The device has been added manually or has been disassociated from a discovered device.

ESI missing

The ESI file is missing.

Error

For AKD, shown when there is an error.

Scan Limitations

  • I/O slices for Standard I/O Coupler do not reveal their Device IDs.
  • The discovery feature does not differentiate between AKT-DN-004-000 and AKT-DNH-004-000 I/O terminals.
    • Nor between AKT-DN-008-000 and AKT-DNH-008-000.
  • Devices other than those made by Kollmorgen are identified by the Vendor Name (or ID number) and Product Name (or ID number).
    • If the device is missing an ESI file, the ESI file supplied by the device Vendor must be imported.
    • The ESI file is required by the IDE to decode and display the Product Name, Device Description, and other details.
  • ESI files for any MDP devices connected to the network should be added to KAS-IDE's ESI library before starting a scan.
    • If the ESI file for an MDP device is not available, then the scan cannot identify the device and cannot discover any physical or logical modules under the device.

Concept Link IconSee Also