BECKHOFF ET1100 - Manual (Page 37)

Pin Description
Slave Controller – ET1100 Hardware Description III-23
3.7 LED Signals
All LED signals are also used as configuration signals. The polarity of each LED signal depends on
the configuration: LED is active high if pin is pulled down for configuration, and active low if pin is
pulled up. Refer to the example schematics for LED connection details.
Table 30: LED pins
Pin
Pin Signal Configuration
Signal Internal
PU/PD
Name Dir. Signal Dir.
H11 RUN/EEPROM_SIZE BD RUN O EEPROM_SIZE
NOTE: The pin locations for LINKACT(x) and PERR(x)/TRANS(x) are described in the Physical Port 0-3 chapters.
RUN/EEPROM_SIZE
SII EEPROM Size configuration (either 1 Kbit-16 Kbit or 32 KBit-4 Mbit) sampled at the beginning of
the EEPROM access. Otherwise RUN LED signal. RUN is active high if pin is pulled down, and active
low if pin is pulled up. Refer to example schematics for connection details. RUN LED should be green.
LINKACT(x)
Link/Activity LED output (off=no link, on=link without activity, blinking=link and activity) for physical port
x. LINKACT(x) is active high if pin is pulled down, and active low if pin is pulled up. Refer to example
schematics for connection details. Link/Activity LED should be green.
PERR(x)/TRANS(x)
Error LED output of physical port x for EBUS ports, and for MII ports if TRANS_MODE_ENA=0. If
TRANS_MODE_ENA=1, PERR(x)/TRANS(x) is used as TRANS(x) for MII physical port x, which puts
port x into isolate/transparent operation. PERR(x) is not available in this case. PERR(x) is active high
if pin is pulled down, and active low if pin is pulled up. Refer to example schematics for connection
details.
NOTE: PERR(x) LEDs are not part of the EtherCAT indicator specification. They are only intended for testing and
debugging. The PERR(x) LED flashes once if a physical layer receive error occurs. Do not confuse PERR(x)
LEDs with application layer ERR LED, this is not supported by the ESCs and has to be controlled by a
µController.