IMD SolutionComputing LibraryShop main store

How-to

Connecting an SLC 5/03 PLC to an industrial remote access router

Remote access and virtualization Published 7 min read

Short answer

Connect the SLC 5/03's 9-pin channel 0, left in its default DF1 mode, to the router's serial port with a null-modem RS-232 cable at 19,200 baud, keeping it under 3 m. The rectangular port is DH-485 on RS-485 wiring at 19.2 kbps, needs an interface module, and must never meet an Ethernet jack.

On this page
  1. Which SLC 5/03 port do I connect to the router?
  2. Is the rectangular SLC 5/03 connector an Ethernet port?
  3. What cable joins the 9-pin port to the router?
  4. Is the 9-pin port set to DF1 or DH-485, and where do I check?
  5. What settings must match at both ends?
  6. How slow is 19.2 kbps for remote access and uploads?
  7. What if the router has no DF1 driver on its serial port?
  8. How do I verify the link before relying on it remotely?
  9. Questions asked

Use the 9-pin serial port, not the rectangular one. Leave the SLC 5/03's channel 0 in its default DF1 mode, run a null-modem RS-232 cable of at most 3 m (118 in.) from it to the eWON Cosy 141's serial port, and set both ends to 19,200 baud. The rectangular connector is a DH-485 port on RS-485 wiring: it is not Ethernet, it runs 19.2 kbps, and reaching it from RS-232 takes an interface module. The cable is the last thing you choose, after reading the channel configuration and the router's documented serial driver list, never from connector shape.

Which SLC 5/03 port do I connect to the router? #

The 9-pin port, channel 0, is the one to use: it is an RS-232 port that ships configured for DF1 and connects directly to a serial-capable router. The rectangular port serves DH-485 and stays out of this link.

The processor gives you two channels, and they are not interchangeable. Channel 0, the 9-pin port, is RS-232 and can be configured for DF1 full-duplex, DF1 half-duplex, DH-485 or ASCII; the documentation for the modular SLC processors lists exactly those options. Channel 1, the rectangular connector, is physically RJ45 but uses RS-485 wiring and is fixed to the DH-485 protocol.

A link works only when three layers match: the connector, the electrical interface and the protocol. RS-232 and RS-485 define signalling levels; DF1 and DH-485 define the conversation. A cable that mates mechanically can still be wrong on the other two layers, which is why you read both configurations before you buy anything.

Is the rectangular SLC 5/03 connector an Ethernet port? #

No, it is not Ethernet: it is the DH-485 port on RS-485 wiring, fixed at 19.2 kbps, and it belongs on a DH-485 network only. No Ethernet cable, hub or router jack takes it.

The connector shape is a coincidence that has cost many people an afternoon. If your plan was Ethernet from the SLC into the router, it cannot work on a 5/03: its documented communication options are DH-485 and the RS-232 protocols, and there is no Ethernet port on this processor.

To reach a DH-485 network from RS-232 equipment, the documented device is the DH-485/RS-232 interface module covered by manual 1747-UM005. Its serial side accommodates RS-232/423, RS-422 and RS-485 signalling, and it is the bridge when DF1 is not an option. Everything on that network runs 19.2 kbps, so this route is also the slow route, as the numbers below show.

What cable joins the 9-pin port to the router? #

A null-modem RS-232 cable, the programmer cable documented for the SLC 5/03 and 5/04 serial port, with a maximum documented length of 3 m (118 in.), running from channel 0 to the router's serial port.

The installation sheet for that programmer cable specifies 3 m (118 in.), which also answers "where does the router mount": near the processor, in the same panel. RS-232 here is point-to-point, one cable and two devices, with no multidrop taps.

Before ordering, read the router's serial port pinout in its own documentation and confirm it against the null-modem wiring. Some routers wire their serial port like the PC side and take the documented cable as-is; others need the complementary wiring, and a connector that fits says nothing about which one you have. Never adapt an Ethernet patch lead or a guessed pinout: the wrong wiring leaves both ends silent and wastes hours.

Is the 9-pin port set to DF1 or DH-485, and where do I check? #

Check the channel 0 configuration in your programming software before you order anything: DF1 is the factory default, but the port can also be set to DH-485 or ASCII, and someone may have changed it.

Read it, do not assume it. If channel 0 shows DF1 full-duplex, leave it there: that is the configuration the cable answer above assumes. Full-duplex suits a two-device cable; half-duplex DF1 exists for modem-style multidrop networks you do not have here.

If the port reads DH-485 or ASCII, change it to DF1 through your programming software and record the change. If it is stuck on DH-485 and you cannot get in over it, the interface module route described earlier is the documented way back onto the processor.

What settings must match at both ends? #

Match protocol, baud, framing and error checking at both ends, and start at 19,200 baud: that is the documented DH-485 rate on this processor family, and DF1 at 19,200 is the pairing to verify in the router's serial driver settings.

On the router side, the serial link is configured in its gateway wizard, where you select the PLC driver and set the serial parameters; whatever is entered there must equal channel 0's configuration. The list to align:

  • Protocol: DF1 full-duplex on both ends
  • Baud: 19,200
  • Parity and stop bits: identical on both ends
  • Station address: the PLC's station address entered as the router's target

Do not chase the baud rate first. If the link stays dead with a verified cable, the station address and the driver selection are the more common mismatches, and a protocol mismatch never appears as a baud error.

How slow is 19.2 kbps for remote access and uploads? #

Raw throughput at 19,200 bits/s is 1,920 bytes/s with a 10-bit asynchronous frame, so a 64 KiB program download has a floor of about 34 seconds and a real-world time several times longer.

Worked example, with illustrative file sizes rather than a measured transfer:

  • Line rate: 19,200 bits/s
  • Asynchronous frame: 1 start bit + 8 data bits + 1 stop bit = 10 bits per byte
  • Raw ceiling: 19,200 bits/s ÷ 10 bits per byte = 1,920 B/s
  • 65,536-byte program file: 65,536 ÷ 1,920 ≈ 34 s
  • 1 MiB file: 1,048,576 ÷ 1,920 ≈ 546 s ≈ 9 min

Those are floors at 100% line utilization. DF1 moves data in transactions with replies and acknowledgements, so plan on a multiple of the floor. The decision: monitoring and tag polling at this rate are comfortable, and program downloads get scheduled for a quiet window or done at the panel.

What if the router has no DF1 driver on its serial port? #

Then stop cabling and re-plan the middle: the SLC 5/03 has no Ethernet and no other bridging option of its own, so the link needs either a router driver that speaks DF1 or a PC-based gateway at the panel.

The driver list in the gateway wizard decides this before any cable is bought. If DF1 for this PLC family is listed, proceed with the null-modem cable. If it is not, the serial link can instead terminate on a fanless mini PC in the cabinet running your OPC server, with the router carrying only Ethernet. The remaining option is the DH-485 interface module route when the whole DH-485 network must be reachable, at the 19.2 kbps rate that implies.

Whichever path you pick, keep the router's plant-side segmentation deliberate from day one; connecting a PLC to the plant network without exposing drives is the side of the design that outlives this cable.

Prove data end to end before you leave: a serial status light or a driver page showing the DF1 link is not enough, and you must see live tag values change through the router's remote path, then survive one disconnect.

  1. Re-read channel 0 after cabling and confirm it still shows DF1 full-duplex at 19,200 baud; the connection itself must not have disturbed the configuration.
  2. Open the router's driver page and confirm the protocol, baud and station address match what you recorded.
  3. Watch one live value, such as an accumulating timer or counter, through the remote path; an LED proves the electrical layer, not the protocol layer.
  4. Break the link once, by unplugging or dropping the remote session, and confirm it recovers without a power cycle or a site visit.
  5. Record protocol, baud, framing, station address and cable length on the panel documentation before you close the door.

One rule before you go online remotely: the machine runs while you are connected, so program changes and mode changes get scheduled with operations first. If the serial side is solid but the remote session is not, the fault is further up the path, and troubleshooting a PLC agent that will not go online remotely picks it up from there.

Questions asked

Can I use the eWON Cosy 141's Ethernet ports to reach the SLC 5/03?

No. The SLC 5/03's documented communication options are DH-485 and RS-232 protocols such as DF1; the processor has no Ethernet port. The router's Ethernet jacks belong to the network side of the router and cannot bridge a serial protocol they never see. The PLC-facing link has to be serial: DF1 on the 9-pin port, or the DH-485 network through an interface module.

What does the DH-485/RS-232 interface module actually do?

It converts between RS-232 equipment and a DH-485 network. Its manual, 1747-UM005, documents a DF1 mode for connecting modems and other user devices, and its serial side accommodates RS-232/423, RS-422 and RS-485 signalling. You need it when the only usable path is the DH-485 network, for example when channel 0 has been set to DH-485 and DF1 is no longer available on the cable.

Can the DH-485 network keep running while the router uses the 9-pin port?

Yes. The two connectors are separate channels with separate configurations: channel 1 is fixed to DH-485, channel 0 is the configurable RS-232 port. Wiring the router to channel 0 in DF1 does not reconfigure channel 1, so an existing DH-485 network on the rectangular port continues as it was. Record which channel serves which device before you leave the panel.

Why does my file transfer take much longer than the calculated floor?

Because the calculation assumes a perfectly filled line. DF1 moves data in transactions, each with a request, a reply and acknowledgements, and every transaction adds framing and turnaround time; retries on a marginal connection add more. The 1,920 B/s figure is the physical ceiling, so treat throughput near it as a best case and expect a multiple of the floor in practice.

Do I need an OPC server in the middle of this link?

Only when the router cannot speak DF1 itself. With a DF1 driver selected in the router's gateway wizard, the router bridges serial to Ethernet and your software connects through it directly. When the driver list has no DF1 entry for this PLC family, the OPC server on a PC at the panel becomes the bridge, and the router carries Ethernet only.

Keep reading

  • Troubleshooting

    Ping works but PLC program download fails over remote access

    ICMP success proves only the routed IP path, not the programming session. A download opens separate query and download connections on documented TCP and UDP ports, and broadcast discovery does not cross a routed VPN. Point the controller's default gateway at the remote-access router LAN address, permit both programming ports to the controller LAN IP, and add the controller manually by IP.

    Remote access and virtualization

  • Troubleshooting

    Troubleshooting a PLC agent that will not go online remotely

    A green remote session proves only that you reached the gateway. Prove the programming connection locally first, then the agent's target address and subnet, then the agent type and protocol, then the client — one boundary at a time. Most of these faults are a mistyped target address or an agent type that carries the wrong protocol.

    Remote access and virtualization

  • Troubleshooting

    Fixing a VM remote PLC connection with a NAT adapter

    Set the guest's virtual adapter to NAT with DHCP, disable every other guest adapter, and keep the remote-access soft key on the host. The failure that repeats is a second bridged adapter pulling the PLC route away from the NAT path. Test the host path first, then the guest, and check that no local subnet matches the plant network.

    Remote access and virtualization