Annex
281/299
PC Cards cifX Compact PCI, Mini PCI, Mini PCIe, PCI-104 | Installation, Operation and Hardware Description
DOC120205UM53EN | Revision 53 | English | 2019-03 | Released | Public
© Hilscher, 2008-2019
References referring to the Standard Bus Specifications for Compact PCI,
Mini PCI, Mini PCI Express and PCI-104 are listed separately
on page 166.
11.10 EtherCAT Summary over Vendor ID, Conformance test,
Membership and Network Logo
11.10.1 Vendor ID
The communication interface product is shipped with Hilscher’s secondary vendor ID, which
has to be replaced by the Vendor ID of the company shipping end products with the
integrated communication interface. End Users or Integrators may use the communication
interface product without further modification if they re-distribute the interface product (e.g.
PCI Interface card products) only as part of a machine or machine line or as spare part for
such a machine. In case of questions, contact Hilscher and/or your nearest ETG
representative. The ETG Vendor-ID policies apply.
11.10.2 Conformance
EtherCAT Devices have to conform to the EtherCAT specifications. The EtherCAT
Conformance Test Policies apply, which can be obtained from the EtherCAT Technology
Group (ETG,
www.ethercat.org
).
Hilscher range of embedded network interface products are conformance tested for network
compliance. This simplifies conformance testing of the end product and can be used as a
reference for the end product as a statement of network conformance (when used with
standard operational settings). It must however be clearly stated in the product
documentation that this applies to the network interface and not to the complete product.
Conformance Certificates can be obtained by passing the conformance test in an official
EtherCAT Conformance Test lab. Conformance Certificates are not mandatory, but may be
required by the end user.
11.10.3 Certified Product vs. Certified Network Interface
The EtherCAT implementation may in certain cases allow one to modify the behavior of the
EtherCAT network interface device in ways which are not in line with EtherCAT
conformance requirements. For example, certain communication parameters are set by a
software stack, in which case the actual software implementation in the device application
determines whether or not the network interface can pass the EtherCAT conformance test.
In such cases, conformance test of the end product must be passed to ensure that the
implementation does not affect network compliance.
Generally, implementations of this kind require in-depth knowledge in the operating
fundamentals of EtherCAT. To find out whether or not a certain type of implementation can
pass conformance testing and requires such testing, contact EtherCAT Technology Group
(“ETG”,
www.ethercat.org
) and/or your nearest EtherCAT conformance test centre.
EtherCAT may allow the combination of an untested end product with a conformant network
interface. Although this may in some cases make it possible to sell the end product without
having to perform network conformance tests, this approach is generally not endorsed by
Hilscher. In case of questions, contact Hilscher and/or your nearest ETG representative.
