SENECA Z-KEY Modbus gateway: RTU to TCP modes, limits and setup

A Modbus gateway sits between an Ethernet network speaking Modbus TCP and a serial line speaking Modbus RTU or ASCII. The Z-KEY family does this in a 17.5 mm DIN-rail housing with one 10/100 Ethernet port, one RS-232/RS-485 switchable port and one dedicated RS-485 port; the R-KEY-LT is the single-port version at 32 mm.

1. Operating modes

Mode	What happens	Use it when
Modbus Ethernet → Serial gateway	The Z-KEY is a Modbus TCP server. Each TCP request is translated to an RTU request on the serial port; the unit ID of the TCP frame becomes the slave address	SCADA, PLC or energy software on Ethernet must read meters, drives or Z-PC modules on RS-485
Modbus Serial → Ethernet gateway	A serial master (for example an old PLC with only RS-485) reaches Modbus TCP servers on the network	Legacy controller must read a new Ethernet device
Gateway with tags	The Z-KEY polls the serial devices itself and keeps up to 500 variables in its own memory; clients read the memory image	Several clients read the same slow serial devices, or the serial side is unreliable and you want the Ethernet side to answer instantly
Serial device server	Transparent tunnelling of any serial protocol over TCP, with the SESC tool on the PC side	A vendor's configuration tool expects a COM port and the device is 300 m away

2. The limits you should design around

• Up to 8 Modbus TCP clients in server mode and up to 10 Modbus TCP servers in client mode.
• Up to 128 Modbus RTU/ASCII slave nodes per serial port, at up to 115 kbps.
• Up to 500 tags in tag mode, assigned through the TEMP-TAG-Z-KEY Excel template.
• Supply 10–40 Vdc or 19–28 Vac, about 2 W; 1.5 kVac isolation between supply, Ethernet and serial.
• Z-KEY, Z-KEY-P, Z-KEY-WIFI and R-KEY-LT carry UL-CSA certification, which matters for panels built to North American or Singapore specifications.

3. Why a gateway seems slow, and how to fix it

The gateway is never the bottleneck; the serial line is. At 9,600 bps a single read of ten registers takes roughly 30 ms including turnaround, so twenty devices polled with three requests each need about two seconds per cycle. Three SCADA clients polling the same devices triple that. Four settings fix most complaints:

1. Raise the baud rate to 38,400 or 115,200 bps if the cable and the slaves allow it.
2. Merge requests: read one contiguous block of 50 registers instead of five blocks of 10.
3. Use tag mode when more than one client reads the line; the Z-KEY polls once and every client gets an instant answer from memory.
4. Switch on quarantine: a device that stops answering is parked for a settable time instead of forcing every cycle to wait for its timeout. The traffic monitor in the web server shows you which address is the offender.

4. Configuration in six steps

1. Power the unit and run SDD (Seneca Discovery Device) to find its IP, or set a temporary address with the DIP switches.
2. Open the built-in web server and set the fixed IP, mask and gateway for your OT network.
3. Set the serial port: RS-485, baud, parity and stop bits identical to the slaves. Mixed settings on one line are the first thing to check when some devices answer and others do not.
4. Choose the mode. For plain SCADA access leave Ethernet → Serial gateway; for multiple clients import the tag template.
5. Set timeouts: serial response timeout slightly above the slowest device, and quarantine on.
6. Test with a Modbus TCP client from a laptop before you connect the SCADA; the diagnostics page shows request and error counters per slave.

5. Z-KEY or an Ethernet remote I/O?

If the serial devices are SENECA Z-PC modules and you are building new, consider the R-series instead: Ethernet I/O with Modbus TCP, PROFINET or EtherNet/IP and a built-in pass-through to RS-485. If the devices are existing meters, drives or third-party instruments, the Z-KEY is the right tool. For remote sites without Ethernet at all, look at the Z-LTE 4G data logger, which polls the serial devices and pushes the data over mobile network.

Quick answers

Can two SCADA servers read the same RS-485 meters through one Z-KEY?

Yes. The Z-KEY accepts up to 8 TCP clients. If both poll heavily, use tag mode so the serial line is read once.

Does the Z-KEY support Modbus ASCII?

Yes, RTU and ASCII on the serial side.

What is the difference between Z-KEY and R-KEY-LT?

Z-KEY has two serial ports and the full feature set in 17.5 mm; R-KEY-LT has one serial port, 1 W consumption and a 32 mm housing for small panels.

Can I update the firmware remotely?

Yes, through the web server.