Importing EDS Files for S7-1200 EtherNet/IP Scanner Communication

1. Understanding EDS Files in EtherNet/IP Networks

An Electronic Data Sheet (EDS) is a text file conforming to the CIP Volume 1, Chapter 4 device-profile specification. It is the EtherNet/IP equivalent of a PROFIBUS GSD or PROFINet GSDML. The file extension is .eds and the content is structured into sections including [Device], [Device Classification], [Identity], [Connection Manager], [Assembly], [Parameter], and [Port].

The EDS file is consumed by an EtherNet/IP scanner (formerly "master") configuration tool during engineering to pre-populate the device catalog, generate connection tags, and instantiate I/O assemblies. Without an EDS, the scanner must be configured manually by entering the Class 0x04 Assembly Instance numbers and data lengths byte-by-byte.

2. Scanner vs. Adapter Architecture in CIP

Common Industrial Protocol (CIP) defines two distinct device roles on EtherNet/IP:

• EtherNet/IP Scanner (originator of connections): Opens Class 0x06 connections, initiates Forward_Open requests, and schedules cyclic I/O exchanges. The S7-1200 CPU with the LCCF_EnetScanner function block acts in this role.
• EtherNet/IP Adapter (target of connections): Responds to Forward_Open, exposes Input and Output Assembly instances, and publishes T→O (Target-to-Originator) data at the configured RPI (Requested Packet Interval).

Two messaging categories traverse the scanner-adapter pair:

• I/O Messages (Class 0x04 implicit): Cyclic UDP/IP traffic on port 2222 using Class 0/1/3 transport. Trigger types are Cyclic (most common, default RPI 10–100 ms), Change-of-State, and Application-triggered.
• Explicit Messages (Class 0x03 explicit, also called "connected" or "unconnected"): TCP/IP or UDP/IP on port 44818 for parameter read/write, Get_Attribute_Single, Set_Attribute_Single, and CIP routing diagnostics.

Only the scanner needs to import the EDS file. The adapter already embeds its identity object and assembly layouts in firmware and broadcasts them via the CIP Identity Object at runtime (CIP Class 0x01, Instance 1).

3. S7-1200 Native EtherNet/IP Limitations

Siemens S7-1200 CPUs (order numbers 6ES721x-1xxxx-xxxx, firmware V4.0 through V4.7) ship with the following PROFINET-capable interfaces:

Unlike the Allen-Bradley CompactLogix 5380 (5069-L320ERM, 5069-L340ERM) which embeds a native EtherNet/IP scanner in Logix Designer, or the Modicon M580 (BMEP58xxxx) which provides EDS import via Control Expert's DTM browser, the S7-1200 has no EDS-aware engineering dialog. TIA Portal cannot parse .eds files directly. The engineering gap is bridged by the LCCF_EnetScanner library — a Siemens partner-developed function block suite that converts EDS parameter intent into TCON, TSEND, TRCV, and TUSEND/TURCV call patterns on the S7-1200 PROFINET interface.

4. LCCF_EnetScanner Library Prerequisites

Before installing the LCCF library, verify the following engineering prerequisites:

1. CPU firmware: S7-1200 must run firmware V4.2 or higher. Earlier V4.0/V4.1 firmware lacks the TUSEND/TURCV instruction set required for UDP-based CIP implicit messaging.
2. TIA Portal version: V15.1 or higher is recommended. TIA Portal V17 (with Update 2 or later) provides the best compatibility with the current library revision (V2.1).
3. Library file: Download "LCCF_EnetScanner" from the Siemens application example 109782314. The archive contains the TIA Portal V15.1 project, V16 project, function block source, and the user documentation PDF.
4. CPU bit width support: LCCF_EnetScanner operates on 32-bit instance DBs. S7-1200 CPUs (which use the S7-1200 instruction set) are supported, but the LCCF library must be opened and re-saved in TIA Portal before it is dropped into a V17+ project to refresh the version signature.
5. PROFINET interface IP scheme: The S7-1200 PROFINET interface (X1) must have a routable IP address in the same subnet as the third-party EtherNet/IP adapter. Default TIA Portal subnet is 192.168.0.0/24. A typical scanner address is 192.168.0.1, adapter 192.168.0.50.

5. Importing EDS Files in TIA Portal for S7-1200 Scanner Operation

TIA Portal does not provide an "Import EDS" command under Devices & Networks. The EDS file from the third-party vendor must be manually translated into LCCF function block parameters. The procedure is:

1. Open the EDS file in a text editor (Notepad++ or VS Code with the EDS language extension). Identify the following mandatory parameters that the LCCF scanner expects at the function-block inputs:

2. In TIA Portal, open the project, navigate to PLC_1 → Program blocks → Add new block → LCCF_EnetScanner [FB]. Drop the function block into the cyclic OB1.
3. Open the instance DB and populate the inputs above with the values extracted from the EDS file. Use the LCCF documentation "Section 4 — Parameterization" for bit-level field definitions.
4. Compile the program, download to the S7-1200 CPU, and place the CPU in RUN.

6. Step-by-Step LCCF_EnetScanner Integration

The following procedure assumes TIA Portal V17, S7-1215C DC/DC/DC (6ES7215-1AG40-0XB0), firmware V4.5, and a third-party EtherNet/IP adapter such as a Softing epGate PN or a Turck TBEN-S block.

Step 6.1 — Load the library

Unzip the application example 109782314 archive. Open LCCF_EnetScanner_V17.ap17. In TIA Portal, Options → Global libraries → Open library and navigate to the unzipped library file. Mark LCCF_EnetScanner as a master copy and drag it into your project library.

Step 6.2 — Instantiate the FB

Inside Program blocks of the S7-1200 CPU, create an instance DB for LCCF_EnetScanner. The instance DB contains the connection parameters, status flags, and process data buffers.

Step 6.3 — Map the connection parameters

Open the instance DB, switch to the Parameters view, and populate the EDS-extracted fields from Section 5 above. Set tConnParam.tRemoteAddr.nRemotePort to 44818 for explicit messaging and 2222 for implicit I/O. The library uses separate connection blocks for each class.

Step 6.4 — Wire cyclic OB

In OB1, call LCCF_EnetScanner with the instance DB. Wire a 1-Hz clock pulse from a system clock byte (e.g., Clock_1Hz) to the bExecute input if change-of-state triggering is configured.

Step 6.5 — Compile and download

Compile the project. The LCCF library internally references the S7-1200 TCON, TDISCON, TUSEND, and TURCV instructions — these are auto-compiled into the program.

Step 6.6 — Commissioning

Download the hardware and software configuration to the CPU. Toggle the input bStart on the LCCF FB. Monitor iStatus — value 16#0000 indicates Idle, 16#8001 indicates Forward_Open pending, 16#0001 indicates established connection, and 16#8xxx indicates a CIP error. Common CIP error codes are listed in Section 10.

7. EDS File Import on Schneider Control Expert (M580/M340)

For engineers on a Schneider Electric platform who must import the same third-party EDS file, Control Expert (formerly Unity Pro) provides a DTM-driven workflow:

1. Open the Control Expert project and select the M580 (BMEP58xxxx) or M340 (BMXP3420xx) PLC.
2. Right-click on the M580 CPU in the Project Browser and select Device Menu → Additional functions → Import EDS library.
3. Navigate to the .eds file. Control Expert validates the CIP Identity Object fields and inserts a DTM entry under the EtherNet/IP scanner tree.
4. The DTM exposes Configuration, Parameters, and I/O Assembly tabs. The Input/Output Assembly instance numbers from the EDS are propagated automatically.

The procedure is documented in Schneider Electric FAQ 000261842 — "How do you import the .eds library file into Control Expert?". The supported Control Expert build is at minimum V14.0 with the EtherNet/IP DTM catalog pack 2023 or later.

8. EDS File Registration in Rockwell Studio 5000

For engineers on Allen-Bradley Logix Designer (Studio 5000 V33+) who must register the same EDS, the workflow uses the EDS Hardware Installation Tool (also called the "Device Description File Installation Tool"):

1. Launch EDS Hardware Installation Tool from the Windows Start menu under Rockwell Software → EDS Hardware Installation Tool. The installer is shipped with every Studio 5000 Logix Designer installation.
2. Select Add and navigate to the .eds file (or a directory containing multiple .eds files).
3. Review the vendor registration summary, then click Next → Finish. The device appears in the Logix Designer Select Module Type dialog under the appropriate vendor tree.
4. Add the new module to the EtherNet/IP scanner tree. Logix Designer prompts for the Connection parameters (RPI, Class 0/1/3 transport, input/output assembly instances). These defaults are pre-populated from the EDS.

The official procedure is documented in the Rockwell Automation knowledge base at knowledge-base article ID 23893 — "Registering an EDS file using the Device Description File Installation Tool". Studio 5000 Logix Designer supports .eds versions up to CIP Volume 1, Revision 3.34 without conversion; older revisions are auto-upgraded.

9. EDS vs. GSDML: Protocol File Selection

A frequent confusion arises when Siemens users encounter a third-party device file. The file extension tells you the bus type:

10. Verification, Diagnostics, and CIP Status Codes

Once the S7-1200 scanner is operational, verify connectivity with the following checks:

1. LCCF Status Word: iStatus = 16#0001 (connection established) and bConnectionActive = TRUE on the LCCF instance DB. Process data words at InputData[0..31] show non-zero counts (or whatever the default adapter publishes).
2. PROFINET interface LEDs: The X1 port "LINK" LED on the S7-1200 CPU illuminates steady; the "RX/TX" LED flickers at the configured RPI rate (e.g., 50 ms → 20 Hz nominal).
3. Wireshark capture: Filter udp.port == 2222 for implicit I/O, tcp.port == 44818 for explicit messages. A healthy cyclic I/O connection shows ENIP encapsulation packets at the RPI cadence with Command = 0x0070 (SendRRData) and a 0x04 CIP Connection path.
4. CIP Forward_Open response: General Status = 0x00 (Success). If the LCCF reports non-zero General Status, decode using the table below.

11. Troubleshooting Matrix

12. Frequently Asked Questions