One copper Ethernet run cannot carry an HMI link 1,500 feet: IEEE 802.3 limits a twisted-pair segment to 100 m (328 ft) and the route is 457 m. Bridge the span with fiber media converters, a point-to-point wireless bridge, chained switches or RS-422 serial, which is rated to about 4,000 ft at 100 kbit/s when the screen only talks to the PLC.
A second HMI 1,500 feet from the PLC cannot ride one copper Ethernet cable. IEEE 802.3 sets the twisted-pair channel at 100 m, about 328 ft, and this route is 457 m, more than four times the limit. Four ways bridge the gap: fiber between two media converters covers the whole run in one link, a point-to-point wireless bridge crosses it without trenching, a chain of switches splits the route into legal copper segments, and RS-422 serial covers it when the screen only needs to talk to the PLC. This page compares the four on distance, power and failure points, and ends with the pick for each case.
Why one copper run fails at 1,500 feet
The twisted-pair Ethernet a PLC and an HMI speak, 100BASE-TX or 1000BASE-T over Cat 5 cable or better, is specified in IEEE 802.3 to operate over a channel of up to 100 m without a repeater. The limit comes from electrical signal degradation along the cable, so it is physics, not a setting. It is the channel length, patch cords included. At 457 m a direct run either never trains or trains and drops the first time a drive starts.
A switch or media converter ends one segment and starts a fresh one, giving the signal a clean restart. It does not stretch a segment past the limit.
Two sidelines. Long-reach copper modes exist that push Ethernet to 700 meters over existing copper, but PLCs and HMIs rarely speak them, so they are a rebuild option, not a fix for this link. And the working 100 ft run to the first screen sits well inside the limit, so leave it alone and bring the new link up beside it.
The four ways to bridge the route, side by side
| Option | The long span is | Distance it covers | Power along the route | Where it wins |
|---|---|---|---|---|
| Fiber plus two media converters | Optical fiber | Converters list up to 7 km; the route fits easily | The two ends only | The plant default; glass carries no electrical noise or ground potential |
| Copper switch chain | Cat 5e/6 copper segments | The limit per segment; five 300 ft segments cover the route | Every switch: 4 midpoints here | Conduit and spare power already exist along the route |
| Point-to-point wireless bridge | Unlicensed radio link | Several km listed with clear line of sight; the path is the risk | The two ends | Across a yard or between buildings with no trench or conduit |
| RS-422 serial | Balanced serial on the PLC's second port | About 4,000 ft at 100 kbit/s; shorter as baud rises | The two ends | The remote screen only talks to this PLC |
Worked example: splitting a 1,500-foot route into copper segments
Inputs: the route is 1,500 ft of conduit between the PLC cabinet and the remote screen; the copper limit is 100 m, which is 328.1 ft (IEEE 802.3).
Rule: divide the route into the fewest segments that each stay at or under that length, and treat every switch between the ends as a powered node that needs power, an enclosure and protection.
Arithmetic: 1,500 ft × 0.3048 m/ft = 457.2 m. 457.2 m ÷ 100 m = 4.57, so five segments is the minimum count. 457.2 m ÷ 5 = 91.4 m per segment, which is exactly 300 ft. Margin per segment: 8.6 m, about 28 ft, left for patch cords and service loops. Switches between the ends: 5 - 1 = 4.
Result: the all-copper build is legal, and it puts four powered enclosures between the PLC and the screen, each one a restart point that can also collect dust or washdown water.
Decision: keep a copper chain for routes that need three segments or fewer, which is 300 m or 984 ft of route and two midpoints. Past that line, fiber does the whole run in one link with zero midpoints, and this 1,500-foot route is past it.
Where fiber wins
Two copper-to-fiber converters, one at the switch and one at the remote end, make the link look like a normal Ethernet port to the PLC and the screen. Converter listings run up to 7 km on fiber, so this route fits with room to spare. Match converter, fiber type and wavelength from the datasheet's reach table before you pull, and leave a service loop at each end.
Glass is why fiber is the plant default: it conducts nothing, so a link between two areas carries no ground potential difference and picks up nothing from drive cables or welders. Each converter needs clean power at its end. Commission the link with the status LEDs lit at both converters and a tag read and written from the remote screen.
Where a wireless bridge wins
When the route crosses a yard, a road or two buildings with no conduit path, two radios set up as a transparent Ethernet bridge carry the link without trenching. Radios sold for point-to-point backhaul list several kilometers with clear line of sight, so this hop is a short one; the risk is the path, not the distance. Plan the path: clear line of sight between antennas and, by the usual link-planning rule, 60 percent of the first Fresnel zone free of obstructions at midpath.
Treat the advertised rate as a ceiling; a radio advertising 54 Mbit/s at the physical layer delivers a fraction of that at range. HMI polling traffic is small, so even a modest link carries it, but watch the link through a full shift of plant activity before the screen depends on it.
Where a switch chain wins
The chain is the right build when conduit already runs the route and spare power sits at usable points along it, because every part is standard copper gear with no new medium to specify. The cost is in the worked example: four enclosures to power, protect and reach when something drops. Keep every copper run, patch cords included, at or under the segment limit, and label the chain so the next technician knows the link is four switches deep.
When serial RS-422 beats all three
If the remote screen's only job is talking to this PLC, serial skips the network build entirely. The RS-422 standard's guideline is about 4,000 ft (1,200 m) of cable at 100 kbit/s, with reach falling as the baud rate rises, so 1,500 ft at the 9.6 or 19.2 kbit/s rates PLC serial ports usually run sits well inside the rating.
Three checks before pulling cable: the PLC's second serial port and the screen must support the same electrical interface; the screen's driver list must cover this PLC over serial; and the PLC manual must allow the Ethernet screen and the serial screen to communicate at the same time. On a run this long, fit termination at the far end; the value and placement are worked out in the termination resistor value for a long RS-422 cable. If the spare port at the PLC is RS-232 instead, how far an HMI can be from the PLC on DF1 RS-232 sets that distance. The broader serial-or-Ethernet choice for an HMI is walked through in connecting a PC HMI to a PLC over a serial protocol or Ethernet.
Power and mounting at the remote end
Both ends need power, 1,500 feet apart. At the far end, a DIN-rail DC supply is the tidy feed when the screen lives in or beside a cabinet; near an outlet, a wall adapter does the job. We stock both, sized for our own displays, so match whatever you fit to the screen's input voltage; our DIN-rail supply and wall adapter options show the two types. Mounting is a fixed VESA bracket; check the screen's mounting pattern and weight against the bracket's listing before ordering.
If the station also carries a notice board for the crew, an offline shop-floor signage panel works next to the HMI: it plays its own files from its own storage, and its HDMI port is an output only, so nothing from the PLC feeds into it.
The decision for each case
- Inside one plant with power at both ends: fiber with two media converters. One link, zero midpoints, no noise pickup. This is the build for a route of this length.
- No trench or conduit path: point-to-point wireless bridge with verified line of sight and Fresnel clearance.
- Conduit and spare power already in place, route 300 m (984 ft) or less: copper chain, three segments, two midpoints.
- Screen talks only to this PLC: RS-422 on the second serial port, good for about 4,000 ft at 100 kbit/s.
- A full I/O base at the PLC changes none of this: every option here hangs off ports and switches the PLC already has.
Recommendation: for any HMI link past 300 m, run fiber with a media converter at each end. Keep the existing 100 ft Ethernet run untouched, bring the fiber link up beside it, and test reads and writes from the remote screen before cut-over. Choose the wireless bridge when fiber cannot be pulled, and RS-422 serial when the screen only talks to the PLC and both ends support the same serial protocol.
Questions
Can I run one 1,500-foot Ethernet cable and ignore the 100 m limit?
Sometimes the link trains at a reduced speed, and sometimes it never comes up at all. That length is the channel IEEE 802.3 holds the electrical design to, and this route leaves no margin: a drive starting, a warm cabinet or an oxidized connector takes the link down. Split the route with switches, or put the long span on fiber or a wireless bridge, so every copper segment sits at or under the limit.
Which fiber should I pull for a link this long?
Multimode and singlemode both cover the route with margin; what matters is the pairing. Converter datasheets list reach per fiber type and wavelength, from hundreds of meters on multimode up to the 7 km class, so pick the converter first and pull the fiber it is listed for. Leave a service loop at each end for retermination.
Will a second HMI slow the first one?
On Ethernet, no: HMI polling is a trickle next to a 100 Mbit/s or 1 Gbit/s link, so the existing screen keeps its response time. On serial, the second screen shares one port at 9.6 or 19.2 kbit/s class rates, so its scan time stretches as tags grow. Check the PLC manual for how many simultaneous connections each port supports before adding a screen.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.