Explainer
Why an EDS file will not add EtherNet/IP to a terminal server
Short answer
No EDS file will make a Digi PortServer TS terminal server speak EtherNet/IP: an EDS only describes the CIP objects a device already implements, and none is published for it. Keep the TS and tunnel Host Link, use its documented Modbus-to-Modbus/TCP conversion, or put a protocol-aware gateway where the serial data has to meet EtherNet/IP.
On this page
- What an EDS file is and what it declares
- Why a description cannot become an implementation
- What the PortServer TS firmware actually serves
- The paths that connect the controller to the serial side
- What the serial side costs you in numbers
- Decisions at a glance
- Proving the link before you call it done
- Questions asked
An EDS file cannot give a Digi TS4W terminal server EtherNet/IP, so the file you were sent looking for does not exist and cannot be written usefully. An EDS is a text description of the CIP objects, parameters and I/O assemblies that a device's firmware already serves; importing one on the Omron NJ501-1300 side does not put a CIP stack on the far end. The terminal server's own datasheet offers tunnels and a Modbus conversion, and no CIP service. The link still gets built — by converting Modbus, tunneling Host Link, or putting a real EtherNet/IP gateway in the path — and this article says which one to commit to.
What an EDS file is and what it declares #
An Electronic Data Sheet is a plain text file defined in the ODVA specifications as part of CIP. It predates EtherNet/IP, since EDS files have been in common use since the DeviceNet days of CIP, and configuration tools read them to identify a product and commission it on the network. The file carries the device identity, the parameter table, and an [Assembly] section that defines the input and output data structures a scanner maps its tags onto.
Vendors generate the file from the firmware they ship; Siemens, for example, publishes a generic EDS for its MultiFieldbus devices precisely so EtherNet/IP tools can integrate them. ODVA conformance testing stands behind the objects the file declares, and that is the requirement that matters here: every object, parameter and assembly an EDS lists must already be implemented in the device before the file is true.
Why a description cannot become an implementation #
EtherNet/IP is CIP messaging over TCP port 44818 for explicit requests and UDP port 2222 for cyclic I/O connections. Answering on those ports takes firmware: a CIP object model with identity, parameter and assembly instances, and connection management for the UDP exchange. The EDS describes that firmware; it is not a substitute for it.
That is also where a hand-made file fails. An import tool checks file grammar, so an EDS you write yourself imports cleanly, and the scanner then opens a connection to the assemblies it declares — and the terminal server, having no CIP stack, never answers. You see a connection timeout, not an import error, which is why the failure reads as misleading. No file anyone sends you changes this: there is nothing in the box for an EDS to describe.
What the PortServer TS firmware actually serves #
The PortServer TS datasheet, which covers the 1-, 2- and 4-port models the TS4W belongs to, lists the box's network services: reverse Telnet and reverse SSH tunneling of a serial port over TCP, SSHv2 and SSL/TLS, the Realport driver that presents the serial ports as COM ports on a PC, and Modbus to Modbus/TCP protocol conversion. Every one is a tunnel or a translator between a serial port and TCP. None is a CIP service, and no EtherNet/IP implementation or EDS appears in the product documentation. The absent file and the absent feature are the same fact — the feature list is the verification.
The paths that connect the controller to the serial side #
Modbus conversion first #
Enable the Modbus profile on the ports that face your Modbus RTU slaves. The terminal server terminates Modbus/TCP sessions on its Ethernet address and forwards each request as an RTU frame, with the TCP unit ID carrying through to the RTU slave address. Your controller polls it as an ordinary Modbus/TCP server. This is the path to commit to when the serial devices are Modbus: it uses a documented feature of the hardware you own, and the controller side needs only Modbus/TCP client capability, which you settle in one look at the CPU's communication options.
Host Link through the tunnel #
When the far end is an Omron serial device, keep the terminal server as a plain TCP tunnel and let the controller send Host Link frames through it. The framing, station addressing and checksum handling are the same work as commissioning Host Link serial reads to SCADA; only the physical layer changes from RS-232 or RS-422 to TCP. The controller has to open a raw TCP connection and treat it as a serial pipe — that one capability decides this path, and it is a line item in the CPU's communication function list, not a protocol question.
A real EtherNet/IP gateway in the path #
This is the only architecture that keeps CIP end to end, and it means hardware in place of the terminal server. The Digi One IAP carried EtherNet/IP awareness, but its implementation targeted Allen-Bradley ControlLogix behavior around 2008, and a modern originator exercising richer ODVA objects can fall outside what it maps — do not build a new NJ integration on it without written confirmation of the assembly mapping. Any replacement gateway must publish an EDS and document how its serial data lands in the assemblies; the NJ-side connection and tag mapping then follow the same steps as configuring an EtherNet/IP drive from an Omron NJ.
If you would rather bridge in software, an industrial mini PC beside the controller can host the Modbus/TCP-to-RTU conversion or serve the serial data to higher layers, and the terminal server drops out of the path.
What the serial side costs you in numbers #
Worked example with illustrative settings typical of a retrofit: a Modbus RTU read of 10 holding registers, function 03, at 9600 bit/s with 8 data bits, even parity and 1 stop — 11 bits per character.
- Character time: 11 bits ÷ 9600 bit/s = 1.146 ms
- Request, 8 bytes (address, function, start, quantity, CRC): 8 × 1.146 ms = 9.17 ms
- Response, 25 bytes (address, function, byte count, 20 data bytes, CRC): 25 × 1.146 ms = 28.65 ms
- End-of-frame silence, 3.5 character times: 3.5 × 1.146 ms = 4.01 ms
- One transaction: 9.17 + 28.65 + 4.01 = 41.8 ms of wire time, before the slave's own turnaround
Eight slaves in one sweep: 8 × 41.8 ms = 334 ms per scan before turnarounds. That is the budget the EDS question never touches, and it is why Modbus RTU polling on one serial port is slow once the poll list grows. At 115200 bit/s the character time drops twelve-fold to 0.0955 ms, but the Modbus specification fixes the interframe silence at 1.75 ms above 19200 bit/s: 0.76 + 2.39 + 1.75 ≈ 4.9 ms per read, about 39 ms for the same eight slaves. Commit accordingly — a 500 ms poll period at 9600 bit/s carries the eight-slave sweep with margin, and if you need faster, raise the baud, because above 19200 bit/s the delimiter stops shrinking and the characters are the only thing left to win.
Decisions at a glance #
| Situation | Commit to | Basis |
|---|---|---|
| You were sent looking for a TS4W EDS | Stop; no EDS can work | The firmware has no CIP stack for a file to describe |
| Serial devices are Modbus RTU | Modbus-to-Modbus/TCP conversion on the TS, controller as client | Documented feature of the box you own |
| The far end speaks Host Link | A plain TCP tunnel carrying the Host Link frames | Tunneling is what the box is built for |
| EtherNet/IP must reach the serial port | A gateway with a published EDS, replacing the TS | The only path that keeps CIP end to end |
| The CPU offers neither Modbus client nor sockets | Host the bridge on a PC in the cabinet | Software path when the controller options are missing |
Proving the link before you call it done #
Read one register whose value you can force at the device — a resettable counter or a known constant — and watch the controller tag track it. Map a second point to prove addressing beyond register zero of slave one. Pull the Ethernet cable and then the serial line, one at a time, and confirm the controller retries and recovers instead of latching a fault. And because a serial tunnel is a remote door onto whatever the port touches, keep the SSH tunnel rather than plain reverse Telnet when the box sits on a shared plant network.
Questions asked
Can I write my own EDS file for the terminal server?
You can write a syntactically valid file and the import tool will accept it, but the scanner will then try to open connections to assembly objects the terminal server has never implemented, and every connection will time out. An EDS grammar check parses the file alone; it never queries the device. Hand-building one for hardware with no CIP stack only moves the failure from the import dialog to the connection log.
The EDS import succeeded, so why is there still no data?
Import success only means the configuration tool parsed the file. Communication starts when the scanner opens a connection to the instances the file declares, and that is where a device without a CIP stack fails, as a connection timeout rather than an import error. Prove any integration by reading a register with a known value and checking it against the physical process before you call the link done.
Does a missing EDS file always mean the device has no EtherNet/IP?
For a shipping product, yes: vendors generate the EDS from the implementation they test, and a device with no published file has no implementation to describe. The exception is a CIP device whose file you simply have not loaded yet. A quick check that asks the device for its CIP identity over the network separates the two cases: an answer means the stack exists, a silent timeout means it does not.
What should I check before reusing a Digi One IAP with an NJ controller?
Its EtherNet/IP firmware was written around Allen-Bradley ControlLogix behavior from about 2008, and a modern originator using richer ODVA objects can fall outside what it maps. Get written confirmation of the assembly mapping for your NJ configuration before you order anything. The Modbus conversion on the terminal server you already own is the lower-risk path.
Which path do I take when some serial devices are Modbus RTU and one speaks Host Link?
Split the ports. The four-port model runs the Modbus-to-Modbus/TCP conversion on the ports facing Modbus RTU slaves and a plain TCP tunnel on the port facing the Host Link device. The controller then opens one Modbus/TCP session to the first group and one raw socket to the tunnel port, and both run independently.