Download Print this page
Beckhoff EK9500 Documentation
Beckhoff EK9500 Documentation

Beckhoff EK9500 Documentation

Ethernet/ip bus coupler for ethercat terminals
Hide thumbs Also See for EK9500:

Advertisement

Quick Links

Documentation | EN
EK9500
EtherNet/IP™-Bus Coupler for EtherCAT Terminals
2025-05-06 | Version: 1.6.0

Advertisement

loading
Need help?

Need help?

Do you have a question about the EK9500 and is the answer not in the manual?

Questions and answers

Summary of Contents for Beckhoff EK9500

  • Page 1 Documentation | EN EK9500 EtherNet/IP™-Bus Coupler for EtherCAT Terminals 2025-05-06 | Version: 1.6.0...
  • Page 3 Configuration via the HTML pages (Device Manager) of the Bus Coupler ........ 36 EtherCAT configuration ........................ 38 EtherNet/IP™ Configuration...................... 41 EtherNet/IP™ Mapping ........................ 44 EK9500 - EtherCAT configurations .................... 45 6 Acyclic communication via CIA ...................... 48 EK9500-CoE data access via CIP .................... 48 EK9500 Version: 1.6.0...
  • Page 4 Update Bus Coupler image ...................... 55 Setting up the EK9500 in RS Logix Studio 5000 via EDS File ............ 55 Setting up an EK9500 as a Generic Device in RS Logix Studio 5000 .......... 59 Using the CtrlStatus DWORD ...................... 61 Supported CIP objects ........................
  • Page 5 , XTS and XPlanar 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. ®...
  • Page 6 Further components of documentation This documentation describes device-specific content. It is part of the modular documentation concept for Beckhoff I/O components. For the use and safe operation of the device / devices described in this documentation, additional cross-product descriptions are required, which can be found in the following table.
  • Page 7 Foreword Notes on information security The products of Beckhoff Automation GmbH & Co. KG (Beckhoff), insofar as they can be accessed online, are equipped with security functions that support the secure operation of plants, systems, machines and networks. Despite the security functions, the creation, implementation and constant updating of a holistic security concept for the operation are necessary to protect the respective plant, system, machine and networks against cyber threats.
  • Page 8 All the components are supplied in particular hardware and software configurations appropriate for the application. Modifications to hardware or software configurations other than those described in the documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG. Personnel qualification This description is only intended for trained specialists in control, automation and drive engineering who are familiar with the applicable national standards.
  • Page 9 • Update structure 1.1.1 • Update chapter “Technical data” • Update structure 1.1.0 • Update chapter “Technical data” • Update structure 1.0.0 • 1 Public issue EK9500 • Addenda 0.0.4 • Corrections 0.0.3 • Addenda CIP objects 0.0.2 • Addenda, corrections 0.0.1 •...
  • Page 10 Associated and synonymous with each revision there is usually a description (ESI, EtherCAT Slave Information) in the form of an XML file, which is available for download from the Beckhoff web site. From 2014/01 the revision is shown on the outside of the IP20 terminals, see Fig. “EL2872 with revision 0022 and serial number 01200815”.
  • Page 11 Version identification of EK Couplers The serial number/ data code for Beckhoff IO devices is usually the 8-digit number printed on the device or on a sticker. The serial number indicates the configuration in delivery state and therefore refers to a whole production batch, without distinguishing the individual modules of a batch.
  • Page 12 1.6.3 Beckhoff Identification Code (BIC) The Beckhoff Identification Code (BIC) is increasingly being applied to Beckhoff products to uniquely identify the product. The BIC is represented as a Data Matrix Code (DMC, code scheme ECC200), the content is based on the ANSI standard MH10.8.2-2016.
  • Page 13 Fig. 3: Example DMC 1P072222SBTNk4p562d71KEL1809 Q1 51S678294 An important component of the BIC is the Beckhoff Traceability Number (BTN, position 2). The BTN is a unique serial number consisting of eight characters that will replace all other serial number systems at Beckhoff in the long term (e.g.
  • Page 14 Electronic access to the BIC (eBIC) Electronic BIC (eBIC) The Beckhoff Identification Code (BIC) is applied to the outside of Beckhoff products in a visible place. If possible, it should also be electronically readable. The interface that the product can be electronically addressed by is crucial for the electronic readout.
  • Page 15 • The following auxiliary functions are available for processing the BIC/BTN data in the PLC in Tc2_Utilities as of TwinCAT 3.1 build 4024.24 ◦ F_SplitBIC: The function splits the Beckhoff Identification Code (BIC) sBICValue into its components using known identifiers and returns the recognized substrings in the ST_SplittedBIC structure as a return value ◦...
  • Page 16 The variants from the EKxxxx series differ from one another by the interface for the higher-level fieldbus system. An overview of the various Beckhoff Bus Couplers covering the most important fieldbus systems can be found on the Beckhoff Website. Embedded PCs with fieldbus interface and decentralized control The TwinCAT-programmable variant is the CX80xx Embedded PC series.
  • Page 17 The coupler supports the EtherNet/IP™ protocol and therefore fits seamlessly into EtherNet/IP™ networks. Configuration The EK9500 is configured based on HTML pages provided by the Bus Coupler or via the EtherNet/IP™ interface. EK9500 Version: 1.6.0...
  • Page 18 E-Bus current/mounting positions ***) - for -25 °C..+60 °C only horizontal mounting position, E-bus current 1 A max. - for -25 °C...+55 °C mounting position any, E-bus current 2 A max. System data EtherNet/IP™ (EK9500) Number of I/O modules depending on controller Number of I/O points...
  • Page 19 80°C at the wire branching points, then cables must be selected whose temperature data correspond to the actual measured temperature values! • Observe the permissible ambient temperature range of 0 to 55°C for the use of Beckhoff fieldbus components standard temperature range in potentially explosive areas! •...
  • Page 20 80°C at the wire branching points, then cables must be selected whose temperature data correspond to the actual measured temperature values! • Observe the permissible ambient temperature range of -25 to 60°C for the use of Beckhoff fieldbus components with extended temperature range (ET) in potentially explosive areas! •...
  • Page 21 • EN 60079-31:2013 (only for certificate no. IECEx DEK 16.0078X Issue 3) Marking Beckhoff fieldbus components that are certified in accordance with IECEx for use in areas subject to an explosion hazard bear the following markings: Marking for fieldbus components of certificate IECEx DEK 16.0078 X...
  • Page 22 Pay also attention to the continuative documentation Ex. Protection for Terminal Systems Notes on the use of the Beckhoff terminal systems in hazardous areas according to ATEX and IECEx, that is available for download within the download area of your product on the Beckhoff homepage www.beckhoff.com!
  • Page 23 Beckhoff EtherCAT modules are intended for use with Beckhoff’s UL Listed EtherCAT System only. CAUTION Examination For cULus examination, the Beckhoff I/O System has only been investigated for risk of fire and electrical shock (in accordance with UL508 and CSA C22.2 No. 142). CAUTION For devices with Ethernet connectors Not for connection to telecommunication circuits.
  • Page 24 • Each bus station must be terminated on the right-hand side with the EL9011 or EL9012 end cap to ensure the degree of protection and ESD protection. Fig. 6: Spring contacts of the Beckhoff I/O components Version: 1.6.0 EK9500...
  • Page 25 3.3.2 Dimensions The following illustrations show the dimensions of the Bus Couplers. Drawings in DWF and STEP format can be found in the Download section of the Beckhoff website. Fig. 7: EK9xxx – dimensions taking the EK9300 as an example EK9500...
  • Page 26 Observe the installation position of the EtherCAT terminals used – not all of them have an arbitrary installation position. Pay attention to the respective EtherCAT infrastructure components and installation instructions. Fig. 9: Recommended distances for standard installation position Version: 1.6.0 EK9500...
  • Page 27 We recommend the installation in the horizontal position for optimum ventilation. Furthermore, it is not necessary with this installation position to check whether there are terminals present that may only be installed horizontally. Other installation positions are allowed, but not recommended. Fig. 10: Other installation positions EK9500 Version: 1.6.0...
  • Page 28 Wiring 3.4.1 Power supply The power supply unit is equipped with an I/O interface, which permits connection of the Beckhoff Bus Terminals. The power is supplied via the upper spring-loaded terminals with the designations "24 V and "0 V". The supply voltage supplies the EK system and, via the terminal bus, the Bus Terminals with a voltage of 24 (-15%/+20 %).
  • Page 29 Ethernet connections Fig. 12: RJ45 interface Assignment of the RJ45 interface, port (switched) EK9xxx: X001 / X002 Signal Description TD + Transmit + TD - Transmit - RD + Receive + connected reserved RD - Receive - connected reserved EK9500 Version: 1.6.0...
  • Page 30 Twisted pair cable for 100 Mbit/s. It is necessary to use a higher cable quality and to employ appropriate hubs or switches in order to achieve the higher data rate. 10BaseF The 10BaseF standard describes several optical fiber versions. Version: 1.6.0 EK9500...
  • Page 31 This identification refers to a cable with a shield for each of the two wires as well as an overall shield. Industrial Twisted-Pair The structure is similar to that of S/STP, but, in contrast to S/STP, it has only one pair of conductors. EK9500 Version: 1.6.0...
  • Page 32 EK9500 EtherNet/IP™ topology sample EK9500 The construction of the EK9500 can take place in a line, with adherence to the following points:   - Maximum 20 couplers one behind the other   - No switches should be used in the line Fig. 13: EtherNet/IP™...
  • Page 33 Products marked with a crossed-out wheeled bin shall not be discarded with the normal waste stream. The device is considered as waste electrical and electronic equipment. The national regulations for the disposal of waste electrical and electronic equipment must be observed. EK9500 Version: 1.6.0...
  • Page 34 This can be used, for example, to test a firmware before copying it to the EK’s internal Flash. USB interface  The USB interface can only be used if the “red” DIP switch has been set accordingly. See “Red DIP switch”. Version: 1.6.0 EK9500...
  • Page 35 The EK starts in Config Mode; the internal Flash memory can be accessed via the USB interface (for example for an image update). 1 off and 2 on Factory setting 1 on and 2 on No function so far EK9500 Version: 1.6.0...
  • Page 36 Fig. 16: Configuration via HTML pages - information diagnostic page Boot Opt The Boot Opt allows you to enable/disable Remote Display. You can also restore the factory settings and trigger a manual reboot of the device. Version: 1.6.0 EK9500...
  • Page 37 Fig. 17: Configuration via HTML pages – Boot Options Network-Interface The network interface enables you to set the IP address. Please note that the DIP switch of the EK9500 takes precedence and its setting applies regardless of what you set in the dialog Fig. 18: Configuration via HTML pages - network interface...
  • Page 38 Configuration EtherCAT configuration EtherCAT Terminals can be configured and parameterized via the HTML page Beckhoff Device Manager. Fig. 19: Configuration via HTML pages - EtherCAT configuration EtherCAT Master The current state of the EtherCAT Master on the EK coupler is displayed here. It should usually be in the OP state.
  • Page 39 Restore file overwrites Modbus modifications If the Restore File is used, the object parameters are always loaded into the terminal on starting the coupler. This will overwrite changes that you have made by Modbus Interface or web page. EK9500 Version: 1.6.0...
  • Page 40 Configuration Fig. 21: Configuration via HTML pages - parameterizing the EtherCAT Terminals Version: 1.6.0 EK9500...
  • Page 41 Configuration EtherNet/IP™ Configuration EtherNet/IP™ Slave: Fig. 22: Configuration via HTML pages – EtherNet/IP™ configuration EtherNet/IP™ Device (Slave) - Device Info All Parameters are “read only” and are for diagnostic purposes EK9500 Version: 1.6.0...
  • Page 42 Enable/Disable UDP Checksum – Multicast (Copies of Frames sent to Multiple Destinations). Checksum is a digit representing the sum of the transmitted data used for error checking. Ethernet Statistics Fig. 23: EtherNet Statistics Ethernet Rx Frames: Received Frames Ethernet Tx Frames: Transmitted Frames Version: 1.6.0 EK9500...
  • Page 43 Create EDS File: Create an Electronic Data Sheet for Use with an EIP Master Create L5X File: Create UDTs for Input and Output Data (For use with RSLogix 5000 Import Only) Fig. 25: Pulldown menu "Create generic description (valid for all configurations") EK9500 Version: 1.6.0...
  • Page 44 Configuration EtherNet/IP™ Mapping Fig. 26: EtherNet/IP™ Mapping Config Instance: 128 Input Instance: 129 Output Instance: 130 Byte Size refers to the size of the process image (Input and Output Data Configuration) Version: 1.6.0 EK9500...
  • Page 45 EtherCAT devices are then invalid and the output data are no longer accepted. This also applies to the devices that are still in operation on the EK9500. If you wish to use the option to plug in or unplug devices during the runtime, a further “Sync Unit”...
  • Page 46 If EtherCAT junction 1 on the EP1122 is connected, then the EtherCAT frame is forwarded here first (1); if junction 1 is not connected, the frame on junction 2 is sent (2), only after that does the sequence continue with the EtherCAT connection on the right-hand side (3). Version: 1.6.0 EK9500...
  • Page 47 No Hot Swap during operation You cannot use the EP1122 and EK1122 on an EKxxxx for Hot Swap and also not for connection and disconnection during operation. EP1122 and EK1122 are suitable only for topology extensions (star) on an EKxxxx. EK9500 Version: 1.6.0...
  • Page 48 As of firmware version v1.23, it is possible to view and adjust CoE data acyclically via the CIP protocol and ADS. Requirement: • Software-Version des EK9500, min. 02 (V00.40) • Image Version des EK9500, min. 2.87 Class/Instance/Attribute definitions for CoE 1.
  • Page 49 Examples for CoE over CIP (EK9500+EL4134+EL3104+EL2004+EL2024+EL3061+EL6090) 1. Device Name, EK9500 ◦ Index 0x1008, SubIndex 0x0 of EK9500 at Slot 0      →       result: „EK9500“ GetAttributeSingle (Class: 0x300, Intance: 0x1008, Attribute: 0x100) 2. Device Name, EL3104 ◦ Index 0x1008, SubIndex 0x0 of EL3104 at Slot 3      →       result: „EL3104-0000“...
  • Page 50 Acyclic communication via CIA Fig. 32: Example Allen Bradley (Studio5000), 4th DIS CHR settings → Row 1 (EL6090) Version: 1.6.0 EK9500...
  • Page 51 (Source: The CIP Networks Library Volume 1: Common Industrial Protocol, Edition 3.22) The following objects are used internally by Beckhoff and are therefore reserved: 1. Identity Object → Class 0x1 2. Message Router Object → Class 0x2 3.
  • Page 52 Error handling and diagnosis Error handling and diagnosis LED indicators Fig. 33: EK9500 LEDs Ethernet interface Interface X001/X002 Ethernet Meaning LED green On/flickering (blinking) Link available/activity LED yellow is not used LED on the coupler Labelling Meaning Color Meaning Indicates the...
  • Page 53 Flashing fast: EtherCAT Scanning; time: different (depending on the number and type of EtherCAT participants) Red/green Yellow Flashing slow: EtherCAT COE reading; time: different (depending on the number and type of EtherCAT participants) Green Start up is finished EK9500 Version: 1.6.0...
  • Page 54 2 Up 24 V (top right, 1 row) Power contacts supply on: connected to: 24 V voltage 3 L/A (left center,  2 row) EtherCAT LED flashing green: EtherCAT communication active on: E-bus connected / no data traffic off: E-bus not connected Version: 1.6.0 EK9500...
  • Page 55 ð The image has been updated successfully. After the update, the Bus Coupler may take a little longer to start up. Setting up the EK9500 in RS Logix Studio 5000 via EDS File Fig. 35: Setting up the EK9500 in RS Logix Studio 5000 via EDS File - Create generic description EK9500 Version: 1.6.0...
  • Page 56 • Create detailed description (only valid for current configuration) – using only one coupler in your project This is an example of how to set up the EK9500 in RS Logix Studio 5000 using the EDS File that can be exported from the Device Manager: Click on the “Create EDS File”...
  • Page 57 Appendix Fig. 38: Search for the EK9500 in RS Logix Studio 5000 Enter the IP Address that was configured for the EK9500 and then click on Change: Fig. 39: Set the IP Address of the EK9500 in RS Logix Studio 5000 Set the data size according to what is shown in the EIP Mapping [} 44]: EK9500 Version: 1.6.0...
  • Page 58 Create L5X File For RS Logix Studio it is possible to generate a data structure for in and output to get a easier mapping information about the connected EtherCAT terminals or modules (“module-defined”). Version: 1.6.0 EK9500...
  • Page 59 Enter a name for your Generic Module (EK9500_1 in the example). Enter the IP Address that was set on the EK9500. The Data type can be set to SINT, INT, DINT or any other optional data type as long as the total number of BYTES is equal to what is shown in the Device Manager EtherNet/IP™...
  • Page 60 Appendix In RS Logix Studio 5000, click to go online and download the configuration to the controller. Communication between the Rockwell hardware and the EK9500 will start up automatically. Version: 1.6.0 EK9500...
  • Page 61 0x10 E-bus fixed after error. Outputs are disabled and have to be reset manually with the control DWORD. 0x04 E-bus error. In the event of an E-bus error, the EK9500 Bus Coupler continues to exchange data with the EtherNet/IP™ scanner (master). However, the input data are invalid. The cause of the error is coded in the high byte, the position in the low byte of the counter.
  • Page 62 Appendix Supported CIP objects Identity Object Class code :  0x01 There is one instance(=1) of this object in EK9500. Class Attribute List no class attributes implemented Instance Attribute List Attr ID Access Name (Struct.) Data Type Description Rule Vendor ID UINT (16) 106, the vendor ID of Beckhoff.
  • Page 63 Set Attribute Single Class 0x300 Instance 0xFFFF Attribute 0x103 Send 4 Byte Data, 01 00 00 00 4. Unlock Restore File Set Attribute Single Class 0x300 Instance 0xFFFF Attribute 0x103 Send 4 Byte Data, 00 00 00 00 EK9500 Version: 1.6.0...
  • Page 64 Appendix 5. Read Status of Restore File Get Attribute Single Class 0x300 Instance 0xFFFF Attribute 0x103 Rec 4 Byte Data, 00 00 00 00 unlock, 01 00 00 00 lock Version: 1.6.0 EK9500...
  • Page 65 No, devices from other vendors can only be used with a CX (see CX8095 or similar products). I would like to operate the drive terminals/drives on the EK9500. Is that possible? No, use a CX with a suitable performance for this, e.g. CX9020 or higher.
  • Page 66 Configuration software for Bus Terminals, Bus Couplers, Bus Terminal Controllers, fieldbus box modules, etc. The PE power contact can be used as a protective earth. TwinCAT The Windows Control and Automation Technology, programmer and configuration tool from the BECKHOFF Automation. Version: 1.6.0 EK9500...
  • Page 67 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: www.beckhoff.com You will also find further documentation for Beckhoff components there.
  • Page 68 TwinSAFE , XFC , XTS and XPlanar are registered trademarks of and licensed by Beckhoff Automation GmbH. Third-party trademark statements Chrome, Chromium and Google are trademarks of Google LLC. DeviceNet and EtherNet/IP are trademarks of ODVA, Inc. Microsoft, Microsoft Azure, Microsoft Edge, PowerShell, Visual Studio, Windows and Xbox are trademarks of the Microsoft group of companies.
  • Page 69 More Information: www.beckhoff.com/EK9500 Beckhoff Automation GmbH & Co. KG Hülshorstweg 20 33415 Verl Germany Phone: +49 5246 9630 info@beckhoff.com www.beckhoff.com...