Updating CAP-XCR-E (EtherCAT option)

FoE (File over EtherCAT)

EtherCAT summit devices include the File over EtherCAT (FoE) mailbox which allows to update the firmware of summit devices.

Follow the next steps to update a summit device:

  1. Open Twincat and scan the network to discover the summit device.

    Copy the available ESI file of the downloaded firmware package into TwinCAT\3.1\Config\Io\EtherCAT folder before opening TwinCAT.

  2. Entering to FoE bootloader differs between Summit devices.

    If using an Everest series device:

    1. Open the online tab and set the drive into the Init state.
    2. Then set the drive into bootstrap state. The RUN LED will be blinking green and fast.

    If using a Capitan series device:

    1. Open the CoE Online tab and search for register Boot Mode (Index 0x5EDE) and write the boot password 0x424F4F54.

    2. Move to Online tab and set the drive into bootstrap state. The drive will restart (few seconds) and the bootloader will boot up in ERR INIT state. A message of "no valid firmware" will be seen, this message notifies the entrance in bootloader mode.
      Force a second time the Bootstrap state. The RUN LED will be blinking green and fast.

    For Daisy Chain drives

    If you have drives in Daisy Chain, drives that are not on the first position, will need to be reloaded (reload device ) in order to get ERR INIT state.

  3. Now the device is in FoE bootloader mode.
    Click on the Download button, and look for the appropriate firmware file. Click on all files option to be able to see the file.

    firmware files

    Everest series use .sfu firmware files. Nevertheless, Capitan series use .lfu firmware files, and they are not compatible.

  4. Write the password 0x70636675 and finally click on OK button.

  5. A downloading message will appear on the bottom progress bar. Wait until the message changes to ready.
  6. Come back to the INIT state. Then the drive will finish the updating process and it will restart.
    Wait until a message of communication re-initialization appears on the TwinCAT log.