Skip to main content
Skip table of contents

How to interpret drive LEDs

Before starting

This tutorial assumes that the Everest XCR has been powered within the accepted power supply range (check Product Description of the drive if in doubt) and that and Ethernet cable has been connected to port ECAT0 (J connector of the Everest XCR).

An easy way to know which type of firmware has been installed in your Everest XCR drive can be deduced by checking the state of LEDs of the interface board. If you are not familiar with these LEDs, you can check the following link for a deeper explanation of the different LEDs and the functionalities that each one implements: Signalling LEDs.

The drive provides information through 6 signalling LEDs:

LEDTypeColorDescription
LED6SingleGreenEtherCAT / Ethernet 0 link (ECAT 0 Link or LINK0)
LED1SingleGreenEtherCAT / Ethernet 1 link (ECAT 1 Link or LINK1)
LED2/3Bi-colorGreen / Red

Driver Status. Two LEDs indicate the driver status.

  • LED2 (Green). Reserved.
  • LED3 (Red). FAULT LED.
LED4/5Bi-colorGreen / Red

EtherCAT / CANopen Status (ECAT Status). Two LEDs indicate the EtherCAT or CANopen status.

  • LED4 (Green). RUN LED.
  • LED5 (Red). ERROR LED.

The meaning of the signaling depends on the product variant, see LED signals reference for details.

LEDs at start-up & Troubleshooting

After powering on, some of the LED signals can help troubleshoot.

EtherCAT

Typical behaviour

If EtherCAT cables are connected on Port 0/1, Link LEDs will light according to the definition.

EtherCAT firmware will start with no other LED because the slave will stay in INIT State after power-up until an EtherCAT master forces it to transition to another state.


LED signalStart-up behaviour
RUN LED (Green)
  • Off.
    The slave will stay in INIT State after power-up until an EtherCAT master forces it to transition to another state.
ERROR LED (Red)
  • Off.
    The slave will stay in INIT State after power-up until an EtherCAT master forces it to transition to another state. Then, some errors may appear.
RUN & ERROR LED
  • Both alternating On-Off (Orange) at 1 Hz.
    Drive is in FTP bootloader mode, in standby.
FAULT LED (Red)
  • Off.
    Off if initialization is correct, On otherwise.

The rest of the LED signals follow the standard behavior.

CANopen

LED signalStart-up behavior
RUN LED (Green)
  • Off during initialization.
  • Blinking (PRE-OPERATIONAL signaling) when initialization is done.
ERROR LED (Red)
  • Off.
    Indicates that CAN network is connected and working properly.

    Start-up LEDs

  • Single flash.
    If a problem occurs during the transmission of the CAN boot-up message (a NMT message used to notify to the master the presence of the slave), the driver will signal it as shown below. This happens if CAN network is disconnected.

    Start-up LEDs with CAN error

  • On.
    This indicates a CAN Bus Off error, most probably generated by a short between CAN high and CAN low lines.
RUN & ERROR LED
  • Both alternating On-Off (Orange) at 1 Hz.
    Drive is in FTP bootloader mode, in standby.
FAULT LED (Red)
  • Off.
    Off if initialization is correct, On otherwise.

The rest of the LED signals follow the standard behaviour

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.