Section I – Technology
(Online at http://www.beckhoff.com)
Section II – Register Description
(Online at http://www.beckhoff.com)
Section III – Hardware Description
Pinout, Interface description, electrical
and mechanical specification, ET1200
features and registers
Version 1.8
Date: 2014-07-07
DOCUMENT ORGANIZATION
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, Safety over EtherCAT®, TwinSAFE® and XFC® are registered trademarks of and licensed by
Beckhoff Automation GmbH. Other designations used in this publication may be trademarks whose use by third parties for their
own purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following German patent applications and patents:
DE10304637, DE102004044764, DE102005009224, DE102007017835 with corresponding applications or registrations in
various other countries.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under development. For that
reason the documentation is not in every case checked for consistency with performance data, standards or other
characteristics. In the event that it contains technical or editorial errors, we retain the right to make alterations at any time and
without warning. No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
The Beckhoff EtherCAT Slave Controller (ESC) documentation covers the following Beckhoff ESCs:
ET1200
ET1100
EtherCAT IP Core for Altera® FPGAs
EtherCAT IP Core for Xilinx® FPGAs
ESC20
The documentation is organized in three sections. Section I and section II are common for all Beckhoff
ESCs, Section III is specific for each ESC variant.
The latest documentation is available at the Beckhoff homepage (http://www.beckhoff.com).
Section I – Technology (All ESCs)
Section I deals with the basic EtherCAT technology. Starting with the EtherCAT protocol itself, the
frame processing inside EtherCAT slaves is described. The features and interfaces of the physical
layer with its two alternatives Ethernet and EBUS are explained afterwards. Finally, the details of the
functional units of an ESC like FMMU, SyncManager, Distributed Clocks, Slave Information Interface,
Interrupts, Watchdogs, and so on, are described.
Since Section I is common for all Beckhoff ESCs, it might describe features which are not available in
a specific ESC. Refer to the feature details overview in Section III of a specific ESC to find out which
features are available.
Section II – Register Description (All ESCs)
Section II contains detailed information about all ESC registers. This section is also common for all
Beckhoff ESCs, thus registers, register bits, or features are described which might not be available in
a specific ESC. Refer to the register overview and to the feature details overview in Section III of a
specific ESC to find out which registers and features are available.
Section III – Hardware Description (Specific ESC)
Section III is ESC specific and contains detailed information about the ESC features, implemented
registers, configuration, interfaces, pinout, usage, electrical and mechanical specification, and so on.
Especially the Process Data Interfaces (PDI) supported by the ESC are part of this section.
Additional Documentation
Application notes and utilities like pinout configuration tools for ET1200 can also be found at the
Beckhoff homepage.
Register overview, PDI, Electrical and mechanical spec
0.4
Abbreviations, editorial changes
0.5
Removed RJ45 description (will become part of Section I)
EEPROM_LOADED pull-down resistor recommendation added
Frame processing order example corrected
I2C EEPROM interface description added
MII management interface description added
Corrected Process RAM size in Register Overview
Revision/Build information added
Recommendations for unused input pins added (should not be left open)
EEPROM_SIZE description corrected from Kbyte to Kbit, possible EEPROM
sizes range from 16 Kbit to 4 Mbit
RoHS compliance added
Autonegotiation is mandatory for ESCs
Description of power supply options added
Electrical characteristics added
SPI_IRQ delay added
TX Shift timing diagram and description added
Pin overview table corrected
Internal 27 kΩ PU/PD resistors at EBUS-RX pins added
LED polarity depending on configuration pin setting described
Recommendation for voltage stabilization capacitors added
Description of Digital I/O behavior on watchdog expiration enhanced
EBUS ports are open failsafe
Reset example schematic added
Ethernet PHY requirements and PHY connection schematic added
MI_DATA pull-up requirement added
Editorial changes
1.0
RUN, LINKACT/x) and PERR(x) LED activity level corrected: active high if
pulled down, active low if pulled up
TX Shift description: timing figures corrected, minor changes, moved to MII
Interface chapter
Pin/Signal description overview added
PERR(x) LEDs are only for testing/debugging
Electrical characteristics enhanced
DC Characteristics enhanced: added V
Reset Core
, VID, VIC
Digital I/O and SPI timing characteristics revised
DC SYNC/LATCH signal description and timing characteristics added
MII Interface chapter and MII timing characteristics added
EBUS Interface chapter added
PHY requirements, EEPROM Interface description and MII Management
Interface description moved to Section I
Ambient temperature range instead of junction temperature range
Editorial changes
Clarified I/O voltage with respect to I/O power supply (only 3.3V I/O with
V
CCI/O
=3.3V, and no 5V input tolerance unless V
CCI/O
=5V)
Update to ET1200 stepping 1
Added/revised OSC_IN, CLK25OUT, and MII TX signal timings
Added soldering profile
PHY address configuration changed
Added feature detail overview, removed redundant feature details
PDI and DC SYNC/LATCH signals are not driven until EEPROM is loaded
Editorial changes
1.2
PHY address configuration chapter added, configuration revised
Enhanced link detection for MII available depending on PHY address
configuration
Ethernet Management Interface: read and write times were interchanged
Editorial changes
1.3
Added reset timing figure and power-on value sample time
Direction of Distributed Clocks SYNC/LATCH signals is configurable
Information on CLK25OUT/CPU_CLK clock output during reset added
Description of internal PU/PD resistors at EBUS_RX pins enhanced
Power supply example schematic clarified
Enhanced package information: MSL and plating material
Digital I/O PDI: added SOF/OUTVALID description
SPI PDI: Read busy signaling not recommended
Editorial changes
1.4
OSC_IN/OSC_OUT pin capacitance added, crystal connection note extended
Release Notes added
Input threshold voltage for OSC_IN added
Renamed Err(x) LED to PERR(x)
Digital I/O PDI: OE_CONF functionality in bidirectional mode corrected
Digital I/O PDI: output event description corrected (EOF mode and WD_TRIG
mode)
SPI PDI: access error if SPI_DI not 1 in the last read byte (not SPI_DO)
AC timing: forwarding delay figures added
Editorial changes
1.5
AC timing: forwarding delay figures MII to MII added
Reset timing figure corrected
Maximum soldering profile added
SPI PDI updated
SII EEPROM interface is a point-to-point connection
Editorial changes
1.6
Update to ET1200-0002
Editorial changes
1.7
Enhanced Link Detection must not be activated if EBUS ports are used
Enhanced Link Detection for MII ports requires PHY address offset = 0
Digital Output principle schematic updated
Chip label updated
Editorial changes
1.8
Update to ET1200-0003
Enhanced Link Detection for MII ports supports PHY address offset 0 and 16
Enhanced Link Detection for MII ports can be disabled at any time
Enhanced Link Detection for EBUS ports is always disabled
MII management interface issues additional MCLK cycle after write accesses
Remote link down signalling time configurable 0x0100[22]
Editorial changes
III-IV Slave Controller – ET1200 Hardware Description
CONTENTS
CONTENTS
1 Overview 1
1.1 Frame processing order 2
1.2 Scope of this document 3
1.3 Revision/Build History 3
2 Features and Registers 4
2.1 Features 4
2.2 Register Overview 7
3 Pin Description 10
3.1 Overview 10
3.1.1 Pin Overview 10
3.1.2 Signal Overview 11
3.1.3 PDI Signal Overview 12
3.2 Configuration Pins 13
3.2.1 Chip mode 13
3.2.2 CPU_CLK MODE 13
3.2.3 TX Shift 13
3.2.4 CLK25OUT Enable 14
3.2.5 PHY Address Offset 14
3.2.6 SII EEPROM Size 14
3.3 General ET1200 Pins 15
3.4 SII EEPROM Interface Pins 15
3.5 Distributed Clocks SYNC/LATCH Pins, MII Management Data 16
3.6 LED Signals 16
3.7 Physical Ports and PDI Pins 17
3.7.1 MII Interface 18
3.7.2 EBUS Interface 18
3.7.3 PDI Pins 18
3.7.4 Port 0/1 and PDI[17:8] Signals 19
3.7.5 PDI[7:0] Signals 20
3.8 PDI Signal Pinout depending on selected PDI 20
2 permanent ports, optional one additional bridge port (each EBUS or
MII, max. one MII port)
FMMUs
3
SyncManagers
4
RAM
1 Kbyte
Distributed Clocks
Yes, 64 bit
Process Data Interfaces
16 Bit Digital I/O (unidirectional/bidirectional)
SPI Slave
Power supply
Two integrated voltage regulators (LDO) for I/O (5V to 3.3V) and logic
core/PLL (5V/3.3V to 2.5V), optional external power supply for I/O and
logic core/PLL.
The ET1200 ASIC is an EtherCAT Slave Controller (ESC). It takes care of the EtherCAT
communication as an interface between the EtherCAT fieldbus and the slave application. The ET1200
supports different applications, from simple digital I/O nodes without external logic up to designs with a
µController and Distributed Clocks.
Table 1: ET1200 Main Features
The general functionality of the ET1200 EtherCAT Slave Controller (ESC) is shown in Figure 1:
The ET1200 supports two ports (logical ports 0 and 1) or three ports (logical ports 0, 1, and 3). The
frame processing order of the ET1200 depends on the number of ports (logical port numbers are
used):
An EtherCAT Slave Controller (ESC) has an address space of 64 Kbyte. The first block of 4 Kbyte
(0x0000:0x0FFF) is dedicated for registers. The process data RAM starts at address 0x1000, its size
is 1 Kbyte (end address 0x13FF).
Table 7 gives an overview of the available registers.
For pin configuration there is a table calculation file (ET1200 configuration and pinout V<version>.xls)
available to make pin configuration easier. This file can be downloaded from the Beckhoff homepage
(http://www.beckhoff.com). This documentation supersedes the table calculation file.
Input pins should not be left open/floating. Unused input pins (denoted with direction UI) without
external or internal pull-up/pull-down resistor should not be left open. Unused configuration pins
should be pulled down if the application allows this (take care of configuration signals in the PDI[17:0]
area when bidirectional Digital I/O is used). Unused PDI[17:0] input pins should be pulled down, all
other input pins can be connected to GND directly.
Pull-up resistors must connect to V
be powered via the resistors and the internal clamping diodes as long as V
, not to a different power source. Otherwise the ET1200 could
CC I/O
is below the other
CC I/O
power source.
Internal pull-up/pull-down resistor values shown in the pinout tables are nominal.
3.1 Overview
3.1.1 Pin Overview
Table 8: Pin Overview
NOTE: EP is the exposed center pad at the bottom of the ET1200.
00 = off, PDI[7]/CPU_CLK available for PDI
01 = 25 MHz clock output at PDI[7]/CPU_CLK
10 = 20 MHz clock output at PDI[7]/CPU_CLK
11 = 10 MHz clock output at PDI[7]/CPU_CLK
CLK_MODE[1
PERR(1)/CLK_MODE(1)
0x0E00[3]
Description
Config signal
Pin name
Register
Values
TX Shift
C25_SHI[0]
PDI[10]/TX_D[2]/C25_SHI[0]
0x0E00[4]
00 = MII TX signals not delayed
01 = MII TX signals delayed by 10 ns
10 = MII TX signals delayed by 20 ns
11 = MII TX signals delayed by 30 ns
C25_SHI[1]
PDI[11]/TX_D[3]/C25_SHI[1]
0x0E00[5]
4
3.2 Configuration Pins
The configuration pins are used to configure the ET1200 at power-on with pull-up or pull down
resistors. At power-on the ET1200 uses these pins as inputs to latch the configuration4. After poweron, the pins have their operation functionality which has been assigned to them, and therefore pin
direction changes if necessary. The power-on phase finishes before the nRESET pin is released. In
subsequent reset phases without power-on condition, the configuration pins still have their operation
functionality, i.e., the ET1200 configuration is not latched again and output drivers remain active.
The configuration value 0 is realized by a pull-down resistor, a pull-up resistor is used for a 1. Since
some configuration pins are also used as LED outputs, the polarity of the LED output depends on the
configuration value.
3.2.1 Chip mode
Chip mode configures the type of the two permanent ports 0 and 1. It is shown in Table 11. The Chip
mode affects the number of available PDI signals.
Chip mode is shown in Table 11.
Table 11: Chip Mode
3.2.2 CPU_CLK MODE
CLK_MODE is used to provide a clock signal to an external microcontroller. If CLK_MODE is not 00,
CPU_CLK is available on PDI[7], thus this pin is not available for PDI signals anymore.
The CPU_CLK MODE is shown in Table 12.
Table 12: CPU_CLK Mode
3.2.3 TX Shift
Phase shift (0/10/20/30ns) of MII TX signals (TX_ENA, TX_D[3:0]) can be attained via the C25_SHI[x]
signals. TX Shift settings are explained in Table 13. It is recommended to support all C25_SHI[1:0]
configurations by hardware options to enable later adjustments.
Table 13: TX Shift
Take care of proper configuration: External devices attached to dual-purpose configuration pins might interfere
sampling the intended configuration if they are e.g. not properly powered at the sample time (external device
keeps configuration pin low although a pull-up resistor is attached). In such cases the ET1200 power-on value
sampling time can be delayed by delaying power activation.
A 25MHz clock for the Ethernet PHY can be made available by the ET1200 on pin PDI[6]. This is only
relevant for MODE 10 or 11. For MODE 00 with MII bridge port 3, CLK25OUT is available at PDI[6]
anyway. CLK25OUT is not available in MODE 00 if MII bridge port 3 is not configured, CLK25OUT
Enable is ignored.
CLK_25OUT Enable is explained in Table 14.
Table 14: CLK_25OUT Enable
3.2.5 PHY Address Offset
The ET1200 supports two PHY address offset configurations, either 0 or 16. Refer to chapter 4.2 for
details on PHY address configuration.
PHY Address Offset is explained in Table 15.
Table 15: PHY Address Offset
3.2.6 SII EEPROM Size
EEPROM_SIZE determines the size of the EEPROM (and the number of I²C address bytes).
EEPROM_SIZE is sampled at the beginning of the EEPROM access. EEPROM_ SIZE is shown in
Table 16.
Connection to external crystal or oscillator input (25 MHz). An oscillator as the clock source for both
ET1200 and the Ethernet PHY is mandatory if an MII port is used and CLK25OUT cannot be used as
the clock source for the PHY. The 25 MHz clock source should have an initial accuracy of 25ppm or
better.
OSC_OUT
Connection to external crystal. Should be left open if an oscillator is connected to OSC_IN.
RESET
The open collector RESET input/output (active low) signals the reset state of ET1200. The reset state
is entered at power-on, if the power supply is to low, or if a reset was initiated using the reset register
0x0040. ET1200 also enters reset state if RESET pin is held low by external devices.
RBIAS
Bias resistor for LVDS TX current adjustment, should be 11 kΩ connected to GND.
3.5 Distributed Clocks SYNC/LATCH Pins, MII Management Data
Table 19: DC SYNC/LATCH and MII Management pins
SYNC/LATCH[x]/MI_DATA
SYNC/LATCH[x] are Distributed Clocks SyncSignal output or LatchSignal input, depending on SII
EEPROM configuration. If an MII port is used, SYNC/LATCH[1]/MI_DATA becomes MI_DATA, which
is the Ethernet PHY management interface data signal. SYNC/LATCH signals are not driven (high
impedance) until the EEPROM is loaded (MI_DATA is independent of the EEPROM loaded state).
NOTE: MI_DATA must have a pull-up resistor (4.7kΩ recommended for ESCs).
3.6 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 20: LED pins
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, usually. 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)/MODE(x)
Chip MODE configuration pin at power-on, Link/Activity LED output (off=no link, on=link without
activity, blinking=link and activity) for logical port x afterwards. 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)/CLK_MODE(x)
CPU_CLK Mode configuration pin at power-on, Error LED output for logical port x afterwards.
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.
The ET1200 pin out is optimized in order to achieve an optimum of size and features. To obtain this,
there is a number of pins where either communication or PDI functionality can be assigned to,
depending on the chip mode. The selected chip mode might reduce PDI possibilities
The ET1200 has 18 PDI pins, PDI[17:0]. They are structured in two groups: PDI[7:0] and PDI[17:8].
PDI[7:0] are always available for PDI signals, PDI[17:8] are available for PDI signals in MODE 00, in
MODE 10/11 they are used for MII signals.
Input signal provided by the PHY if a 100 Mbit/s (Full Duplex) link is established. LINK_MII(x) is active
low.
RX_CLK(x)
MII Receive Clock.
RX_DV(x)
MII receive data valid.
RX_D(x)[3:0]
MII receive data.
RX_ERR(x)
MII receive error.
TX_ENA(x)
MII transmit enable output.
TX_D(x)[3:0]
MII transmit data.
MI_CLK
PHY Management Interface clock.
3.7.1.1 CLK25OUT Signal
CLK25OUT
The ET1200 has to provide an Ethernet PHY with a 25 MHz clock signal (CLK25OUT) if a 25 MHz
crystal is used for clock generation. In case a 25 MHz oscillator is used, CLK25OUT is not necessary,
because the Ethernet PHY and the ET1200 can share the oscillator output. CLK25OUT is not
available at PDI[6]/CLK25OUT in chip mode 00 unless the MII bridge port is configured via SII
EEPROM. With the MII bridge port, CLK25OUT is available regardless of C25ENA. For chip modes
10/11, PDI[7] may be configured to deliver CLK25OUT by pulling up the PDI[9]/TX_D[1]/C25ENA
configuration signal.
CLK25OUT provides a clock signal – if configured – during external or ECAT reset, clock output is
only turned off during power-on reset.
3.7.2 EBUS Interface
The EBUS ports of the ET1200 are open failsafe, i.e., the ET1200 detects if an EBUS port is
unconnected and closes the port internally (no physical link).
EBUS(x)-RX+/EBUS(x)-RX-
EBUS LVDS receive signals. EBUS_RX+ pins incorporate a pull-down resistor R
pins incorporate a pull-up resistor R
, even if the pins are not configured for EBUS.
LI-
and EBUS_RX-
LI+
EBUS(x)-TX+/EBUS(x)-TX-
EBUS LVDS transmit signals.
3.7.3 PDI Pins
PDI[x]
The function of PDI[x] signals depends on the configuration stored in the device SII EEPROM. PDI
signals are not driven (high impedance) until the EEPROM is loaded. This has to be taken into
account especially for Digital Outputs.
PDI signals are not driven (high impedance) if no PDI is configured (PDI Control register
0x0140=0x00).
The ET1200 can provide a clock signal for µControllers on pin PDI[7]/CPU_CLK. The CPU_CLK
output setting is controlled by the CLK_MODE configuration pin. If CPU_CLK is enabled, PDI[7] is not
available for the PDI, i.e., I/O[7] is not available for Digital I/O PDI.
CPU_CLK provides a clock signal – if configured – during external or ECAT reset, clock output is only
turned off during power-on reset.
3.7.4 Port 0/1 and PDI[17:8] Signals
Table 22 and Table 23 show the port 0/1 and PDI signals used for ports 0 and 1.
Table 22: Port 0/1 and PDI signals (Configuration and chip mode 00)
Table 23: Port 0/1 and PDI signals (chip modes 10/11)
Table 24 shows the PDI[7:0] signals. The direction of all PDI pins depends on the PDI configuration
stored in the SII EEPROM.
Table 24: PDI pins
3.8 PDI Signal Pinout depending on selected PDI
The PDI signal pinout depends on the selected PDI (SII EEPROM). The PDI selection and PDI signal
pinout is subject to restrictions introduced by the port configuration. Digital I/O and SPI PDI are
available in any configuration – although the I/O width can be reduced depending on the configuration.
The MII bridge port PDIs is only available in chip mode 00.
Refer to PDI descriptions for further PDI and PDI signal descriptions.
The SPI PDI supports additional general purpose output signals, which are not part of the SPI PDI
The bridge port is an additional port with logical number 3, it is configured via SII EEPROM, thus it is
not available directly after power-on. The bridge port becomes available once the EEPROM is loaded
successfully. The loop at this port is initially closed and has to be opened by the master explicitly. The
bridge port may be either EBUS or MII. The MII bridge port is only available in chip mode 00.
The polarity of PERR(3) and LINKACT(3) is active high.
The ET1200 supports different power supply and I/O voltage options with 3.3V (or 5V I/O, not
recommended) and optionally single or dual power supply.
The V
V
CCI/O
supply voltage directly determines the I/O voltages for all inputs and outputs, i.e., with 3.3V
CCI/O
, the inputs are 3.3V I/O compliant and they are not 5V tolerant (V
has to be 5V if 5V tolerant
CCI/O
I/Os are required).
Two internal LDOs generate the I/O supply voltage V
V
CC Core/VCC PLL
than V
CC I/O
(nom. 2.5V) from the ET1200 power supply input VCC. VCC must be equal or greater
, and V
is always equal to V
CC PLL
. The internal LDOs cannot be switched off, they
CC Core
(nom. 3.3V) and the core supply voltages
CC I/O
stop operating if the external supply voltage is higher than the internal LDO output voltage, thus
external supply voltages have to be higher (at least 0.1V) than the internal LDO output voltages.
Using the internal LDOs increases power dissipation, and power consumption for 5V I/O voltage is
significantly higher than power consumption for 3.3V I/O. It is highly recommended to use 3.3V I/O
voltage and the internal LDO for V
CC Core/VCC PLL
For 3.3V I/O with external 3.3V power supply, both VCC and V
external 3.3V supply voltage, and for 5V I/O voltage, both VCC and V
.
have to be connected to the
CCI/O
have to be connected to the
CCI/O
external 5V supply voltage.
Voltage stabilization capacitors at all power pairs are necessary.
Table 29: Power supply options (all voltages nomal)
The ET1200 is connected with Ethernet PHYs using the MII interface. The MII interface of the ET1200
is optimized for low processing/forwarding delays by omitting a transmit FIFO. To allow this, the
ET1200 has additional requirements to Ethernet PHYs, which are easily accomplished by several PHY
vendors.
Refer to “Section I – Technology” for Ethernet PHY requirements.
Additional information regarding the ET1200:
The clock source of the PHYs is either CLK25OUT of the ET1200, or the clock signal that is
connected to OSC_IN if a quartz oscillator is used.
The signal polarity of LINK_MII is not configurable, LINK_MII has to be active low.
The TX_CLK signal of the PHYs is not connected to the ET1200. The ET1200 does not use the
MII interface for link detection or link configuration.
For details about the ESC MII Interface refer to Section I.
4.1 MII Interface Signals
The MII interface of the ET1200 has the following signals:
Input signal provided by the PHY if a 100 Mbit/s
(Full Duplex) link is established
RX_CLK
IN
Receive Clock
RX_DV
IN
Receive data valid
RX_D[3:0]
IN
Receive data (alias RXD)
RX_ERR
IN
Receive error (alias RX_ER)
TX_ENA
OUT
Transmit enable (alias TX_EN)
TX_D[3:0]
OUT
Transmit data (alias TXD)
MI_CLK
OUT
Management Interface clock (alias MCLK)
MI_DATA
BIDIR
Management Interface data (alias MDIO)
PHYAD_OFF
IN
Configuration: PHY address offset
Table 31: MII Interface signals
MI_DATA must have an external pull-up resistor (4.7 kΩ recommended for ESCs). MI_CLK is driven
rail-to-rail, idle value is High.
4.2 PHY Address Configuration
The ET1200 addresses Ethernet PHYs using logical port number (or PHY address register value) plus
PHY address offset. Typically, the Ethernet PHY addresses should correspond with the logical port
number, so PHY addresses 0-3 are used.
A PHY address offset of 16 can be applied which moves the PHY addresses to 16-19 by inverting the
MSB of the PHY address internally.
If both alternatives cannot be used, the PHYs should be configured to use an actual PHY address
offset of 1, i.e., PHY addresses 1-4. The PHY address offset configuration of the ET1200 remains 0.
Refer to Section I for more details about PHY addressing.
CLK25OUT delay after OSC_IN (refer to AC characteristics)
t
TX_delay
TX_ENA/TX_DATA[3:0] delay after rising edge of OSC_IN (refer to AC
characteristics)
t
PHY_TX_CLK_delay
Delay between PHY clock source CLK25OUT and TX_CLK output of the
PHY, PHY dependent
t
PHY_TX_CLK_delay_OSC
Delay between PHY clock source OSC_IN and TX_CLK output of the PHY,
PHY dependent
t
PHY_TX_setup
PHY setup requirement: TX_ENA/TX_DATA with respect to TX_CLK (PHY
dependent, IEEE802.3 limit is 15 ns)
t
PHY_TX_hold
PHY hold requirement: TX_ENA/TX_DATA with respect to TX_CLK (PHY
dependent, IEEE802.3 limit is 0 ns)
4.3 TX Shift Compensation
Since ET1200 and the Ethernet PHY share the same clock source, TX_CLK from the PHY has a fixed
phase relation to TX_ENA/TX_D[3:0]from the ET1200. Thus, TX_CLK is not connected and the delay
of a TX FIFO inside the ET1200 is saved. The phase shift between TX_CLK and TX_ENA/TX_D[3:0]
can be compensated by an appropriate value for TX Shift, which will delay TX_ENA/ TX_D[3:0] by 0,
10, 20, or 30 ns.
NOTE: TX Shift can be adjusted by displaying TX_CLK of a PHY and TX_ENA/TX_D[3:0] on an oscilloscope.
TX_ENA/TX_D is allowed to change between 0 ns and 25 ns after a rising edge of TX_CLK (according to
IEEE802.3 – check your PHY’s documentation, it may contain relaxed timing requirements). Configure TX Shift so
that TX_ENA/TX_D[3:0] change near the middle of this range. It is sufficient to check just one of the
TX_ENA/TX_D[3:0] signals, because they are nearly generated at the same time.
For details about the ESC EBUS Interface refer to Section I.
5.1 EBUS Interface Signals
The EBUS interface of the ET1200 has the following signals:
Figure 6: EBUS Interface Signals
Table 34: EBUS Interface signals
NOTE: An external LVDS termination with an impedance of 100 Ω between EBUS-RX+ and EBUS-RX- is
necessary for EBUS ports. EBUS-RX+ incorporates a pull-down resistor and EBUS-RX- incorporated a pull-up
resistor.
Output data is valid/Output event or
Watchdog Trigger
act. high
6.2 Digital I/O Interface
6.2.1 Interface
The Digital I/O PDI is selected with PDI type 0x04. The signals of the Digital I/O interface are:
Figure 7: ET1200 Digital I/O Signals
Table 36: ET1200 Digital I/O signals
NOTE: Unsupported control signals OE_EXT and OE_CONF are assumed to be high.
6.2.2 Configuration
The Digital I/O interface is selected with PDI type 0x04 in the PDI control register 0x0140. It supports
different configurations, which are located in registers 0x0150 – 0x0153.
6.2.3 Digital Inputs
Digital input values appear in the process memory at address 0x1000:0x1003. EtherCAT devices use
Little Endian byte ordering, so I/O[7:0] can be read at 0x1000 etc. Digital inputs are written to the
process memory by the Digital I/O PDI using standard PDI write operations.
Digital inputs can be configured to be sampled by the ESC in four ways:
Digital inputs are sampled at the start of each Ethernet frame, so that EtherCAT read commands
to address 0x1000:0x1003 will present digital input values sampled at the start of the same frame.
The SOF signal can be used externally to update the input data, because the SOF is signaled
before input data is sampled.
The sample time can be controlled externally by using the LATCH_IN signal. The input data is
sampled by the ESC each time a rising edge of LATCH_IN is recognized.
Digital inputs are sampled at Distributed Clocks SYNC0 events.
Digital inputs are sampled at Distributed Clocks SYNC1 events.
For Distributed Clock SYNC input, SYNC generation must be activated (register 0x0981). SYNC
output is not necessary (register 0x0151). SYNC pulse length (registers 0x0982:0x0983) should not be
set to 0, because acknowledging of SYNC events is not possible with Digital I/O PDI. Sample time is
the beginning of the SYNC event.
Digital Output values have to be written to register 0x0F00:0x0F03 (register 0x0F00 controls I/O[7:0]
etc.). Digital Output values are not read by the Digital I/O PDI using standard read commands,
instead, there is a direct connection for faster response times.
The process data watchdog (register 0x0440) has to be either active or disabled; otherwise digital
outputs will not be updated. Digital outputs can be configured to be updated in four ways:
Digital Outputs are updated at the end of each EtherCAT frame (EOF mode).
Digital outputs are updated with Distributed Clocks SYNC0 events (DC SYNC0 mode).
Digital outputs are updated with Distributed Clocks SYNC1 events (DC SYNC1 mode).
Digital Outputs are updated at the end of an EtherCAT frame which triggered the Process Data
Watchdog (with typical SyncManager configuration: a frame containing a write access to at least
one of the registers 0x0F00:0x0F03). Digital Outputs are only updated if the EtherCAT frame was
correct (WD_TRIG mode).
For Distributed Clock SYNC output, SYNC generation must be activated (register 0x0981). SYNC
output is not necessary (register 0x0151). SYNC pulse length (registers 0x0982:0x0983) should not be
set to 0, because acknowledging of SYNC events is not possible with Digital I/O PDI. Output time is
the beginning of the SYNC event.
An output event is always signaled by a pulse on OUTVALID even if the digital outputs remain
unchanged.
For output data to be visible on the I/O signals, the following conditions have to be met:
SyncManager watchdog must be either active (triggered) or disabled.
Output values have to be written to the registers 0x0F00:0x0F03 within a valid EtherCAT frame.
The configured output update event must have occurred.
Figure 8: Digital Output Principle Schematic
NOTE: The Digital Outputs are not driven (high impedance) until the EEPROM is loaded. The Digital Outputs are
also not driven if the Watchdog is expired. This behavior has to be taken into account when using digital output
signals.
In bidirectional mode, all DATA signals are bidirectional (individual input/output configuration is
ignored). Input signals are connected to the ESC via series resistors, output signals are driven actively
by the ESC. Output signals are permanently available if they are latched with OUTVALID (Flip-Flop or
Latch).
Input sample event and output update event can be configured as described in the Digital
Inputs/Digital Outputs chapter.
An output event is signaled by a pulse on OUTVALID even if the digital outputs remain unchanged.
Overlapping input and output events will lead to corrupt input data.
6.2.6 Output Driver
The output drivers for the digital I/O signals of the ET1200 are active while the SyncManager
watchdog is active (triggered) or disabled, otherwise the output driver is disabled (high impedance).
6.2.7 SyncManager Watchdog
The SyncManager watchdog (registers 0x0440:0x0441) must be either active (triggered) or disabled
for output values to appear on the I/O signals. The SyncManager Watchdog is triggered by an
EtherCAT write access to the output data registers.
If the output data bytes are written independently, a SyncManager with a length of 1 byte is used for
each byte of 0x0F00:0x0F03 containing output bits (SyncManager N configuration: buffered mode,
EtherCAT write/PDI read, and Watchdog Trigger enabled: 0x44 in register 0x0804+N*8). Alternatively,
if all output data bits are written together in one EtherCAT command, one SyncManager with a length
of 1 byte is sufficient (SyncManager N configuration: buffered mode, EtherCAT write/PDI read, and
Watchdog Trigger enabled: 0x44 in register 0x0804+N*8). The start address of the SyncManager
should be one of the 0x0F00:0x0F03 bytes containing output bits, e.g., the last byte containing output
bits.
The SyncManager Watchdog can also be disabled by writing 0 into registers 0x0440:0x0441.
The Watchdog Mode configuration bit is used to configure if the expiration of the SyncManager
Watchdog will have an immediate effect on the I/O signals (output reset immediately after watchdog
timeout) or if the effect is delayed until the next output event (output reset with next output event). The
latter case is especially relevant for Distributed Clock SYNC output events, because any output
change will occur at the configured SYNC event.
Immediate output reset after watchdog timeout is not available if OUTVALID mode set to watchdog
trigger (0x0150[1]=1).
For external watchdog implementations, the WD_TRIG (watchdog trigger) signal can be used. A
WD_TRIG pulse is generated if the SyncManager Watchdog is triggered. In this case, the internal
SyncManager Watchdog should be disabled. For devices without the WD_TRIG signal, OUTVALID
can be configured to reflect WD_TRIG.
Input data valid after SOF, so that Inputs
can be read in the same frame
t
SOF_to_DATA_hold
1,6 µs
Input data invalid after SOF
t
input_event_delay
440 ns
Time between consecutive input events
t
OUTVALID
75 ns
85 ns
OUTVALID high time
t
DATA_to_OUTVALID
65 ns
Output data valid before OUTVALID
t
WD_TRIG
35 ns
45 ns
WD_TRIG high time
t
DATA_to_WD_TRIG
35 ns
Output data valid after WD_TRIG
t
OE_EXT_to_DATA_invalid
- - Not applicable for ET1200
t
output_event_delay
320 ns
Time between consecutive output events
t
BIDIR_DATA_valid
65 ns
Bidirectional mode: I/O valid before
OUTVALID
t
BIDIR_DATA_invalid
65 ns
Bidirectional mode: I/O invalid after
OUTVALID
t
BIDIR_event_delay
440 ns
Bidirectional mode: time between
consecutive input or output events
6.2.8 SOF
SOF indicates the start of an Ethernet/EtherCAT frame. It is asserted shortly after RX_DV=1 or EBUS
SOF. Input data is sampled in the time interval between t
SOF_to_DATA_setup
and t
SOF_to_DATA_setup
after the
SOF signal is asserted.
6.2.9 OUTVALID
A pulse on the OUTVALID signal indicates an output event. If the output event is configured to be the
end of a frame, OUTVALID is issued shortly after RX_DV=0 or EBUS EOF, right after the CRC has
been checked and the internal registers have taken their new values. OUTVALID is issued
independent of actual output data values, i.e., it is issued even if the output data does not change.
6.2.10 Timing specifications
Table 37: Digital I/O timing characteristics ET1200
An EtherCAT device with PDI type 0x05 is an SPI slave. The SPI has 5 signals: SPI_CLK, SPI_DI
(MOSI), SPI_DO (MISO), SPI_SEL and SPI_IRQ:
Figure 14: SPI master and slave interconnection
Table 38: SPI signals
6.3.2 Configuration
The SPI slave interface is selected with PDI type 0x05 in the PDI control register 0x0140. It supports
different timing modes and configurable signal polarity for SPI_SEL and SPI_IRQ. The SPI
configuration is located in register 0x0150.
NOTE: The maximum SPI_CLK frequency depends on the SPI mode (ET1200 only).
6.3.3 SPI access
Each SPI access is separated into an address phase and a data phase. In the address phase, the SPI
master transmits the first address to be accessed and the command. In the data phase, read data is
presented by the SPI slave (read command) or write data is transmitted by the master (write
command). The address phase consists of 2 or 3 bytes depending on the address mode. The number
of data bytes for each access may range from 0 to N bytes. The slave internally increments the
address for the following bytes after reading or writing the start address. The bits of both
address/command and data are transmitted in byte groups.
The master starts an SPI access by asserting SPI_SEL and terminates it by taking back SPI_SEL
(polarity determined by configuration). While SPI_SEL is asserted, the master has to cycle SPI_CLK
eight times for each byte transfer. In each clock cycle, both master and slave transmit one bit to the
other side (full duplex). The relevant edges of SPI_CLK for master and slave can be configured by
selecting SPI mode and Data Out sample mode.
The most significant bit of a byte is transmitted first, the least significant bit last, the byte order is low
byte first. EtherCAT devices use Little Endian byte ordering.
A[15:13] address bits [15:13]
CMD1[2:0] read/write command
res[1:0] two reserved bits, set to 00b
3
D1[7:0] data byte 1
D0[7:0] data byte 0
4 ff.
D2[7:0] data byte 2
D1[7:0] data byte 1
Byte
2 Byte address mode
3 Byte address mode
SPI_DI
(MOSI)
SPI_DO
(MISO)
SPI_DI
(MOSI)
SPI_DO
(MISO)
0
A[12:5]
I0[7:0] interrupt request
register 0x0220
A[12:5]
I0[7:0] interrupt request register
0x0220
1
A[4:0]
CMD0[2:0]
I1[7:0] interrupt request
register 0x0221
A[4:0]
CMD0[2:0]
I1[7:0] interrupt request register
0x0221
2
(Data phase)
A[15:13]
CMD1[2:0]
I2[7:0] interrupt request register
0x0222
6.3.4 Commands
The command CMD0 in the second address/command byte may be READ, WRITE, NOP, or Address
Extension. The command CMD1 in the third address/command byte may have the same values:
Table 39: SPI commands CMD0 and CMD1
6.3.5 Address modes
The SPI slave interface supports two address modes, 2 byte addressing and 3 byte addressing. With
two byte addressing, the lower 13 address bits A[12:0] are selected by the SPI master, while the upper
3 bits A[15:13] are assumed to be 000b inside the SPI slave, thus only the first 8 Kbyte in the
EtherCAT slave address space can be accessed. Three byte addressing is used for accessing the
whole 64 Kbyte address space of an EtherCAT slave.
During the address phase, the SPI slave transmits the PDI interrupt request registers 0x0220-0x0221
(2 byte address mode), and additionally register 0x0222 for 3 byte addressing on SPI_DO (MISO):
In the data phase of a write access, the SPI master sends the write data bytes to the SPI slave
(SPI_DI/MOSI). The write access is terminated by taking back SPI_SEL after the last byte. The
SPI_DO signal (MISO) is undetermined during the data phase of write accesses.
6.3.8 Read access
In the data phase of a read access, the SPI slave sends the read data bytes to the SPI master
(SPI_DO/MISO).
6.3.8.1 Read Wait State
Between the last address phase byte and the first data byte of a read access, the SPI master has to
wait for the SPI slave to fetch the read data internally. Subsequent read data bytes are prefetched
automatically, so no further wait states are necessary.
The SPI master can choose between these possibilities:
The SPI master may either wait for the specified worst case internal read time t
after the last
read
address/command byte and before the first clock cycle of the data phase.
The SPI master may use the BUSY signaling of the SPI slave to achieve faster read times. The
SPI slave presents its state on SPI_DO (MISO) after SPI_DI (MOSI) is set high between address
and data phase (Busy Out enable) until SPI_DI is set to low (Busy Out enable is edge sensitive) .
While the SPI slave is busy, it will drive SPI_DO high. Once it has finished, SPI_DO is set to low
and the master may start with the next clock cycle for the first read data byte.
BUSY signaling is not available in SPI mode 0/2 with normal data out sample.
6.3.8.2 Read Termination
The SPI_DI signal (MOSI) is used for termination of the read access by the SPI master. For the last
data byte, the SPI master has to set SPI_DI to high (Read Termination byte = 0xFF), so the slave will
not prefetch the next read data internally. If SPI_DI is low during a data byte transfer, at least one
more byte will be read by the master afterwards.
6.3.9 SPI access errors and SPI status flag
The following reasons for SPI access errors are detected by the SPI slave:
The number of clock cycles recognized while SPI_SEL is asserted is not a multiple of 8
(incomplete bytes were transferred).
For a read access, the data phase was not terminated by setting SPI_DI to high for the last byte.
For a read access, additional bytes were read after termination of the access.
A wrong SPI access will have these consequences:
Registers will not accept write data (nevertheless, RAM will be written).
Special functions are not executed (e.g., SyncManager buffer switching).
A status flag will indicate the error until the next access (not for SPI mode 0/2 with normal data out
sample)
A status flag, which indicates if the last access had an error, is available in any mode except for SPI
mode 0/2. The status flag is presented on SPI_DO (MISO) after the slave is selected (SPI_SEL) and
until the first clock cycle occurs. So the status can be read either between two accesses by assertion
of SPI_SEL without clocking, or at the beginning of an access just before the first clock cycle. The
status flag will be high for a good access, and low for a wrong access.
6.3.10 EEPROM_LOADED
The EEPROM_LOADED signal indicates that the SPI Interface is operational. Attach a pull-down
resistor for proper function, since the PDI pin will not be driven until the EEPROM is loaded.
SPI_CLK frequency
a) SPI mode 1/3 with Normal Data Out
Sample or SPI mode 0/1/2/3 with Late
Data Out Sample (f
CLK
≤ 20 MHz)
b) SPI mode 0/2 with Normal Data Out
Sample (f
CLK
≤ 6 MHz)
b) SPI mode 0/2 with Normal Data Out
Sample and Address Extension (f
CLK
≤ 15
MHz)
t
SEL_to_CLK
7 ns
First SPI_CLK cycle after SPI_SEL
asserted
t
CLK_to_SEL
a)5 ns
b) t
CLK
/2+5 ns
De-assertion of SPI_SEL after last
SPI_CLK cycle
a) SPI mode 0/2, SPI mode 1/3 with
normal data out sample
b) SPI mode 1/3 with late data out sample
t
read
a) 240 ns
b) 0 ns
Only for read access between
address/command and first data byte.
Can be ignored if BUSY or Wait State
Bytes are used.
a) SPI mode 1/3, or SPI mode 0/2 with
Late Data Out Sample
b) SPI mode 0/2 with Normal Data Out
Sample
t
C0_to_BUSY_OE
t
CLK
BUSY OUT Enable assertion after sample
time of last command bit C0.
t
BUSY_valid
15 ns
BUSY valid after BUSY OUT Enable
t
SEL_to_DO_valid
15 ns
Status/Interrupt Byte 0 bit 7 valid after
SPI_SEL asserted
t
SEL_to_DO_invalid
0 ns
Status/Interrupt Byte 0 bit 7 invalid after
SPI_SEL de-asserted
t
STATUS_valid
12 ns
Time until status of last access is valid.
Can be ignored if status is not used.
t
access_delay
a) 15 ns
b) 240 ns
Delay between SPI accesses
a) typical
b) If last access was shorter than 2 bytes,
otherwise Interrupt Request Register
value I0_[7:0] will not be valid.
t
DI_setup
8 ns
SPI_DI valid before SPI_CLK edge
t
DI_hold
3 ns
SPI_DI valid after SPI_CLK edge
t
CLK_to_DO_valid
15 ns
SPI_DO valid after SPI_CLK edge
t
CLK_to_DO_invalid
0 ns
SPI_DO invalid after SPI_CLK edge
t
EEPROM_LOADED_to_acce
ss
300 ns
Time between EEPROM_LOADED and
first access
t
IRQ_delay
160 ns
Internal delay between AL event and
SPI_IRQ output to enable correct reading
of the interrupt registers.
Read access time (without errors):
a) 4 words
b) configuration (8 Words)
t
Delay
~ 168 ms
Time until configuration loading begins after
Reset is gone
8 SII EEPROM Interface (I²C)
For details about the ESC SII EEPROM Interface refer to Section I. The SII EEPROM Interface is
intended to be a point-to-point interface between ET1200 and I²C EEPROM. If other I²C masters are
required to access the I²C bus, the ET1200 must be held in reset state (e.g. for in-circuit-programming
of the EEPROM), otherwise access collisions will be detected by the ET1200.
8.1 Signals
The EEPROM interface of the ET1200 has the following signals:
Figure 22: I²C EEPROM signals
Table 46: I²C EEPROM signals
The pull-up resistors for EEPROM_CLK and EEPROM_DATA are integrated into the ET1200.
EEPROM_CLK must not be held low externally, because the ET1200 will detect this as an error.
The layout of the clock source has the biggest influence on EMC/EMI of a system design.
Although a clock frequency of 25 MHz requires not extensive design efforts, the following rules shall
help to improve system performance:
Keep clock source and ESC as close as possible close together.
Ground Layer should be seamless in this area.
Power supply should be of low impedance for clock source and ESC clock supply.
Capacitors shall be used as recommended by the clock source component.
Capacities between clock source and ESC clock supply should be in the same size (values
depend upon geometrical form of board).
The initial accuracy of the ET1200 clock source has to be 25ppm or better.
Figure 23: Quartz crystal connection
NOTE: The value of the load capacitors depends on the load capacitance of the crystal, the pin capacitance C
of the ESC pins and the board design (typical 12pF each if CL = 10pF).
Figure 24: Quartz crystal Clock source for ET1200 and Ethernet PHYs
Figure 25: Oscillator clock source for ET1200 and Ethernet PHYs
9.2 Power supply
Recommendation for voltage stabilization capacitors: 220pF and 100nF ceramic capacitors for each power pin
pair, additional 10µF tantalum electrolytic capacitor for VCC, V
capacitors.
GND, GND
The internal LDOs are self-deactivating if the actual V
The LVDS termination with an impedance of 100 Ω is typically achieved by a resistor R
only necessary for EBUS ports and should be placed adjacent to the EBUS_RX inputs.
cannot be used externally, their full effectiveness appears only inside the ET1200 (realized as
Electrical Specifications and Timings
Configuration
External supply voltage
Supply current (typical)
VCC
V
CC I/O
V
CC Core
ICC
I
CC I/O
I
CC Core
2 EBUS ports
3.3V
3.3V
Int. LDO
70 mA
17 mA - 5V
Int. LDO
Int. LDO
87 mA - -
5V
5V
Int. LDO
72 mA
36 mA
-
3.3V
3.3V
2.5V
1 mA
17 mA
75 mA
5V
Int. LDO
2.5V
16 mA
-
75 mA
5V
5V
2.5V
1 mA
40 mA
75 mA
3 EBUS ports
3.3V
3.3V
Int. LDO
74 mA
24 mA - 5V
Int. LDO
Int. LDO
97 mA - -
5V
5V
Int. LDO
76 mA
43 mA
-
3.3V
3.3V
2.5V
1 mA
24 mA
79 mA
5V
Int. LDO
2.5V
23 mA
-
79 mA
5V
5V
2.5V
1 mA
43 mA
79 mA
1 EBUS port, 1 MII
port
3.3V
3.3V
Int. LDO
68 mA
10 mA - 5V
Int. LDO
Int. LDO
78 mA - -
5V
5V
Int. LDO
69 mA
25 mA
-
3.3V
3.3V
2.5V
1 mA
10 mA
72 mA
5V
Int. LDO
2.5V
10 mA
-
72 mA
5V
5V
2.5V
1 mA
26 mA
72 mA
2 EBUS ports, 1 MII
port
3.3V
3.3V
Int. LDO
71 mA
18 mA - 5V
Int. LDO
Int. LDO
89 mA - -
5V
5V
Int. LDO
73 mA
34 mA
-
3.3V
3.3V
2.5V
1 mA
18 mA
76 mA
5V
Int. LDO
2.5V
17 mA
-
76 mA
5V
5V
2.5V
1 mA
37 mA
76 mA
Table 51: DC Characteristics (Supply current)
NOTE: Int. LDO means internal LDO is used, otherwise power is supplied externally. Supply current does not
include output driver current for PDIs and LEDs.
Average difference processing delay minus
forwarding delay (without RX FIFO jitter)
between any two ports
20
ns
t
EE
EBUS port to EBUS port delay (FIFO size 7):
a) Through ECAT Processing Unit
(processing), Low Jitter off
b) Alongside ECAT Processing Unit
(forwarding), Low Jitter off
c) Through ECAT Processing Unit
(processing), Low Jitter on
d) Alongside ECAT Processing Unit
(forwarding), Low Jitter on
a) 140
b) 120
c) 150
d) 130
a) 150
b) 130
c) 155
d) 135
a) 160
b) 140
c) 160
d) 140
ns
t
EM
EBUS port to MII port delay (FIFO size 7):
a) Through ECAT Processing Unit
(processing)
b) Alongside ECAT Processing Unit
(forwarding)
a) 145
b) 125
a) 170
b) 150
a) 195
b) 175
ns
t
ME
MII port to EBUS port delay (FIFO size 7):
a) Through ECAT Processing Unit
(processing), Low Jitter off
b) Alongside ECAT Processing Unit
(forwarding), Low Jitter off
c) Through ECAT Processing Unit
(processing), Low Jitter on
d) Alongside ECAT Processing Unit
(forwarding), Low Jitter on
a) 255
b) 235
c) 265
d) 245
a) 280
b) 260
c) 290
d) 270
a) 305
b) 285
c) 315
d) 295
ns
t
MM
MII port to MII port delay
(FIFO size 7, TX Shift=00):
Through ECAT Processing Unit (processing)
280
305
335
ns
Table 53: Forwarding Delays
NOTE: Average timings are used for DC calculations.
The ET1200 is shipped in a sealed moisture barrier bag (dry-pack). There is a “caution” label on the
dry-pack which contains all necessary information required for handling the devices. Refer to the
JEDEC standards J-STD-020 and J-STD-033 for more details (http://www.jedec.org).
The information on the dry-pack takes precedence over information in this chapter.
The moisture sensitivity level of the ET1200 is MSL 3. The maximum shelf-life of the ET1200 packed
in a dry-pack is one year after bag seal date. If the ET1200 is stored longer than one year, drying
(baking) is required before soldering.
Drying and re-packaging can have negative effects on solderability and conducting surfaces. To
minimize issues, the following steps should be taken:
Visual inspection of the ET1200 devices
solderability tests with some samples of the ET1200
final test of the product using the ET1200 with focus on the ET1200 connections
The following soldering profile is a maximum soldering profile. For the actual soldering profile many
factors have to be taken into consideration, e.g., solder paste characteristics, the PCB, other
components, materials, and process type. An example soldering profile is shown below.
The ordering codes for the ET1200 devices are composed like this:
ET1200-0000-NNNN
The code part NNNN identifies the size of the packing unit. Do not confuse the ordering codes with the
stepping code ET1200-0000. You will always get the latest stepping while the ordering codes are
unchanged.
Beckhoff and our partners around the world offer comprehensive support and service, making
available fast and competent assistance with all questions related to Beckhoff products and system
solutions.
12.1.1 Beckhoff’s branch offices and representatives
Please contact your Beckhoff branch office or representative for local support and service on Beckhoff
products!
The addresses of Beckhoff's branch offices and representatives round the world can be found on her
internet pages: http://www.beckhoff.com
You will also find further documentation for Beckhoff components there.
Support offers you comprehensive technical assistance, helping you not only with the application of
individual Beckhoff products, but also with other, wide-ranging services:
world-wide support
design, programming and commissioning of complex automation systems
and extensive training program for Beckhoff system components