IMDHMIControls LibraryShop main store

Selection guide

Choosing PLC to SCADA communication over long distances

Industrial networks Published 9 min read

Short answer

For PLC-to-SCADA communication over long distance, choose the transport by reach and connection behavior: fiber Ethernet for a continuous long link (one span rated 2 km), RS-485 where serial fits, extenders or radio on existing pairs, dial-up or leased-line modems on phone service. Direct copper Ethernet fails at 100 m per segment; the SCADA driver or OPC service, not the PLC's ASCII modem commands, carries the protocol.

On this page
  1. How far can each transport actually reach?
  2. Can one long Ethernet cable carry the whole PLC-to-SCADA link?
  3. Which transport fits a long PLC-to-SCADA run?
  4. Dial-up or leased-line modems on the existing phone line?
  5. What carries the PLC protocol over the chosen transport?
  6. Can the PLC dial out on an alarm and send the data to SCADA?
  7. How do I verify the link before building the SCADA screens?
  8. Questions asked

For a PLC-to-SCADA link across 500 m or more, choose the transport first and the protocol second. Direct copper Ethernet cannot do it in one span: the IEEE 802.3 copper segment is rated 100 m, so a run of that length needs a different medium. Fiber Ethernet carries the whole distance continuously; RS-485 conversion, Ethernet extenders, transparent serial radio, and dial-up or leased-line modems on the existing phone pair cover the cases where fiber cannot be pulled. Whatever the medium, it only moves bytes: the SCADA driver or OPC service speaks the PLC protocol, and the PLC's ASCII dial-out instruction drives the modem without ever packaging SCADA data. This guide gives the reach numbers, a decision table for the long-haul case, and the alarm dial-out arrangement that works.

How far can each transport actually reach? #

Copper Ethernet stops at 100 m per segment under IEEE 802.3, RS-232 at about 30 m in practice, RS-485 reaches roughly 1,200 m at 100 kbps, standard fiber optics span 2 km (100BASE-FX multimode) to 10 km (100BASE-LX10 single-mode), and a modem works wherever the phone service reaches.

The copper figure is the electrical span for one twisted-pair segment, and the documented way past it is powered repeaters or switches at each segment boundary. On a route of this length that means five segments and four powered points along the way, each needing an enclosure, power and access.

RS-232 is a single-ended signal built for short device-to-device links such as modems and printers, which is why its practical figure is quoted in feet: 100 ft covers a bench-to-modem run, not a building-to-building one. RS-485 exists for the longer job; its differential pair rejects noise on long runs, its reach trades against data rate, and any RS-485 budget is quoted together with its speed.

Fiber reach is set by the optics at each end, one span at a time, and the span rating is a property of the optics and the fiber type, not of the route length you need. Either optic quoted above crosses a route of this length with room to spare. Where the path has several spans in series, the fiber span budgets for pipeline SCADA page shows how per-span budgets decide total reach. One safety note: a cable that leaves the building is a lightning path, so fit surge protection at both ends before the first power-up.

Can one long Ethernet cable carry the whole PLC-to-SCADA link? #

No: a copper Ethernet segment is rated 100 m, so the route fails as one span — in meters, 500 / 100 = 5 segments, which places 4 powered switches or repeaters mid-route — and fiber, extenders or serial conversion are the practical choices for the long haul.

Worked example — deciding between copper and fiber on this route. Copper Ethernet needs 5 segments and 4 mid-route repeaters or switches, each one an enclosure, a power supply and a place to maintain. One fiber span with 100BASE-FX optics is rated 2,000 m, so the margin is 2,000 − 500 = 1,500 m and no mid-route hardware exists. The same route on RS-485 sits inside the 1,200 m rating at 100 kbps: 1,200 − 500 = 700 m of margin, again with no repeaters, at serial speed rather than Ethernet speed.

Decision: fiber when SCADA polls continuously over Ethernet; RS-485 when a verified spare twisted pair exists and the poll volume is modest; copper Ethernet with mid-route repeaters only where powered enclosures are practical along the whole route.

Do not expect the phone pair to behave as Ethernet cable either way: the segment rating assumes twisted-pair cabling of the grade the standard specifies, and telephone-grade cable with ordinary hardware tolerance decides whether a link trains at all. That is why reused pairs get extenders, not raw Ethernet.

Which transport fits a long PLC-to-SCADA run? #

Fiber Ethernet is the first choice for a run of this length that must stay connected continuously; RS-485 conversion, transparent serial radio, Ethernet extenders over an existing pair, and dial-up or leased-line modems cover the cases where the phone line is the path you actually have.

Transport Medium and documented reach Connection behavior Choose it when
Fiber Ethernet with copper-to-fiber converters at each end New fiber; 2,000 m per span on 100BASE-FX, 10 km on 100BASE-LX10 Continuous Ethernet SCADA polls continuously and fiber can follow the phone-line route
Ethernet extenders (a configured, matched pair) Existing twisted pair; reach is the extender pair's rating for that wire Continuous proprietary Ethernet link You must reuse an existing pair and keep Ethernet end to end
RS-232-to-RS-485 conversion Spare twisted pair; about 1,200 m at 100 kbps Continuous serial The PLC port is serial and a verified spare pair exists
Transparent serial radio Radio path; reach confirmed by a test at both antenna points Continuous serial when radios pass the protocol unchanged Trenching is impossible and the radio path test passes
Dial-up modems Switched telephone service; 33.6 kbps (V.34) On demand: SCADA PC calls, PLC-side modem answers Polling tolerates connect time per cycle and the pair is switched service
Leased-line modems Dedicated leased circuit; speed fixed by the carrier circuit Always connected The pair is provisioned as a leased circuit and the link must stay up

Two notes decide the converter and radio rows. A two-wire RS-485 link needs transmit direction control at the converter, and turnaround timing errors corrupt frames, so choose two-wire or four-wire operation only after checking what the converter supports and how many conductors you have. A transparent radio must carry the serial protocol unchanged end to end — DF1 full duplex between the PC interface and the PLC port, for example — so confirm that transparency before you buy.

Dial-up or leased-line modems on the existing phone line? #

Dial-up modems on a switched telephone service give an on-demand link at up to 33.6 kbps (V.34); leased-line modems on a dedicated circuit give an always-connected link; classify the pair first, because switched service, a leased circuit and a dead spare pair take different equipment.

Switched service and a leased circuit are different physical services and do not accept the same modems, so confirm with the carrier what the pair actually is before ordering either. On dial-up, the robust arrangement puts the PLC-side modem in the answering role and lets the SCADA PC place every call: one coordinator at the PC instead of dialing logic at both ends. A PLC-originated call needs coordinated logic at both ends and is covered in the alarm section below. Modems also add call setup time and their own failure modes, so they earn their place when the phone line is the only path you have, not merely the path that happens to exist.

Decision: dial-up when the pair is switched service and polling can wait out each call setup; leased-line modems when the circuit is provisioned for it and the link must stay up; fiber or a spare pair whenever either is actually available.

What carries the PLC protocol over the chosen transport? #

The SCADA driver or OPC service carries the PLC protocol; the transport only moves bytes, so set the driver's framing to match the PLC port — DF1 full duplex over a serial radio or converter path, the driver's Ethernet path over fiber — and never invent a message format.

Configure, do not write: SCADA reads and writes PLC data through a supported driver or its OPC interface, and the driver speaks the PLC's native protocol while the modems, radios, converters or fiber carry the bytes underneath. Over transparent serial radios, DF1 full duplex runs end to end between the PC interface and the PLC serial port, and the radios never see a tag.

Getting the PC side to reach the controller through intermediate hardware is the same discipline as any bridged driver path, for example the way you Reach a CompactLogix through a ControlNet bridge in RSLinx: the driver must see through the bridging hardware to the controller.

Where the long haul becomes a protocol-aware serial-to-Ethernet gateway, and the gateway is a small computer instead of a dedicated box, an industrial mini PC mounted next to the controller in the cabinet is the usual host. Watch the one-master limit: a PLC serial connection serves a single client at a time, so a basic serial server makes SCADA polling and laptop programming contend, and simultaneous access needs a gateway built for multiple sessions or a move to fiber.

Can the PLC dial out on an alarm and send the data to SCADA? #

The PLC can dial, but the dial-out instruction only commands the modem: on a MicroLogix 1500, the AWA instruction sends Hayes-command ASCII out the serial port, and after dialing the port must return to System Mode before the SCADA driver can poll — the call moves no data by itself.

AWA writes ASCII strings, which is exactly what a Hayes-command modem dial sequence needs, and nothing more; it does not package PLC data for the SCADA system. A PLC-originated alarm call therefore works only as a coordinated workflow: the PLC issues the dial command, the PC modem answers, the PLC port returns to System Mode, and the SCADA driver or OPC service detects or re-establishes the dormant link and polls the alarm and process data. The answer-and-recover logic has to exist on the SCADA side.

Decision: with an existing switched line, run PC-initiated polling with the PLC modem answering, and add PLC dial-out only when your SCADA platform can answer a call and revive the driver connection on its own. When alarm delivery must be guaranteed, an always-connected transport — fiber or a leased line — removes the dialing problem entirely.

Prove the path with the PC driver before any tag is configured: classify the medium, match the serial settings at both ends, browse or read the PLC, then test polling, link loss, reconnection and, on dial-up, a triggered alarm through answer, recovery and clean disconnect.

  1. Classify the path before buying hardware: switched service, leased circuit, verified spare twisted pair, or new fiber. The medium decides the equipment, not the other way round.
  2. Configure the PLC serial port and the PC driver with matching protocol framing and line settings; over a transparent radio or converter path, treat the whole link as one extended serial cable.
  3. Connect and confirm the PC driver browses or reads the PLC before any SCADA configuration starts.
  4. Poll normally, then break the link on purpose and watch recovery. A marginal long-haul link shows up as frozen or question-mark values in the client, the symptom set described in Why HMI values show question marks: PLC comms timeouts.
  5. On dial-up, trigger a real alarm and verify the dial, the PC answer, the return to System Mode, the driver reconnection, the alarm acquisition and a clean hang-up.
  6. Run a laptop programming session while SCADA polls and confirm neither drops; if they contend, the architecture needs a multi-session gateway or fiber.

Questions asked

Is a 33.6 kbps dial-up link fast enough for SCADA polling?

Run the arithmetic. V.34 moves 33,600 bits per second, about 4,200 bytes per second, so a 500-byte poll response transfers in roughly 0.12 seconds and a scan cycle of one to a few seconds over a modest tag set is realistic. It is not a link for high-resolution trending or large recipe transfers; keep those on fiber or a leased circuit.

Can the same fiber run also carry the existing phone service?

Yes, with separate electronics at each end. A fiber pair has capacity far beyond one SCADA link, so telephone service and future expansion can share the cable. Plan the end enclosures for both services from the start: media converters for the Ethernet, telephone-over-fiber or VoIP equipment for the phones, and termination space for whatever comes next.

How do I check that a spare twisted pair can carry RS-485?

Check three things before you commit the design. Confirm continuity and conductor condition end to end with a meter. Confirm the pair carries no telephone service, because one pair runs one service. Then connect the converters at both ends and test real traffic at the intended rate; a pair that passes a multimeter can still fail on capacitance or noise at speed.

Does an Ethernet extender just adapt the RJ45 plug to the phone pair?

No. Extenders use their own line signal and are configured as a matched pair: both ends must be the same product family and rated for the installed wire type and length. That is why the reach figure lives in the extender pair's specification rather than in any Ethernet standard, so check the installed wire against that rating before you buy.

Keep reading

  • How-to

    How to learn PLC, SCADA and DAQ from scratch

    Learn the three as one project, not three courses: pick one route, wire one real input, program a three-state sequence, exchange one Modbus register, bind SCADA tags and store a timestamped value. Pass the five checkpoint tests on the way; simulation alone never exercises terminals, polarity or reconnection.

    SCADA and data logging

  • How-to

    Reach a CompactLogix through a ControlNet bridge in RSLinx

    When autobrowse through a 1784-U2CN ControlNet path lists the bridge's EtherNet/IP module but no CompactLogix or third-party EtherNet/IP devices, add the target IP address manually under that module's Ethernet port in RSWho or the FactoryTalk Linx browse tree, then select the resulting device as the online path in the Logix programming software. The devices are reachable; only discovery fails, and a manual entry needs no discovery.

    Industrial networks

  • Selection guide

    SCADA and PLC platform selection for plant revamps

    Judge the whole chain — engineering tool, exact controller, fieldbus role, OPC UA endpoint, SCADA runtime and client — not the IDE alone. Freeze pass-or-fail gates on the license boundary, target hardware, fieldbus, OPC UA and documentation, then pilot one representative plant unit on the real controller. Adopt only after deployment, protocol behavior, diagnostics and failure recovery all pass there; until then the incumbent platform stays the baseline.

    SCADA and data logging