How-to
DH-485 Wiring for HMI Replacement: RS-232 Pin Map
Short answer
DH-485 is a protocol, not one electrical standard: it runs over RS-232 or RS-485. The serial version on a 9-pin PanelView port is RS-232, and a replacement HMI connects pin-for-pin on pins 2, 3 and 5 to the controller's channel 0.
On this page
- Is DH-485 an RS-232 or an RS-485 connection?
- How do I tell which electrical flavor the existing port uses?
- Which pins carry DH-485 over RS-232 on the DB9?
- Which controller port does the HMI cable connect to?
- How do I wire and verify the replacement HMI cable?
- What settings must match for DH-485 to come up?
- Why does the new HMI show no communication?
- Questions asked
Replacing a dead DH-485 operator terminal? The answer is pins 2, 3 and 5. DH-485 ships in two electrical flavors, RS-232 and RS-485, and the serial version that ran a PanelView 550 into channel 0 of an SLC or PLC-5 is the RS-232 flavor: a straight-through, pin-for-pin cable on three conductors, 2 to 2, 3 to 3, 5 to 5. This walk-through shows how to confirm the flavor, land the cable on the right controller port, prove the wiring with a meter, and bring the replacement HMI online.
Is DH-485 an RS-232 or an RS-485 connection? #
Neither, by itself: DH-485 is a network protocol that ships in two electrical flavors, RS-232 and RS-485, and the flavor is decided by the port hardware, not by the DH-485 name or the software configuration.
DH-485 defines what the devices say to each other; the RS-232 and RS-485 standards define what the wires carry. RS-232 is single-ended and point-to-point: two devices, three conductors, transmit, receive and a shared ground, over short runs in electrically quiet surroundings. RS-485 is differential and multipoint: complementary signals on a twisted pair, up to 32 devices on one segment, and correspondingly longer runs. An HMI talking to one controller is exactly 2 nodes, and the 9-pin DH-485 port on a PanelView 550 is the RS-232 flavor of the two.
How do I tell which electrical flavor the existing port uses? #
One field test settles it: if the old terminal programs through a plain straight-through RS-232 cable on that same port, the port is the RS-232 flavor of DH-485, and the pin map below applies.
The installation that established this wiring had exactly that combination: a DH-485 port on a 9-pin connector, programmed by a straight RS-232 cable on the same, and only, port. The connector shape alone proves nothing, because DH-485 also runs over RS-485 on hardware that looks similar. Read the interface off the port label and the terminal's documentation. If the documentation says RS-485, stop: an RS-232 pin map is not an RS-485 wiring plan, and no cable from this article belongs on that port.
Which pins carry DH-485 over RS-232 on the DB9? #
Pins 2, 3 and 5, wired straight through with no crossover: pin 2 to pin 2, pin 3 to pin 3, pin 5 to pin 5, between the HMI and the controller channel.
Three of the connector's nine positions do all the work, so 9 − 3 = 6 positions sit unused. Pin 5 is the shared reference both single-ended data signals are measured against, which is why the link dies without it even though only two pins move data.
| DB9 position | Role on this link | Lands on |
|---|---|---|
| 2 | Data, one direction | Position 2 at the far end |
| 3 | Data, the other direction | Position 3 at the far end |
| 5 | Shared signal reference | Position 5 at the far end |
For the 6-inch C-More Micro that commonly replaces these terminals, a cable designated EA-DH485-CBL exists for exactly this DH-485 link; whichever cable you use, verify its connector ends and pinout against both ports rather than trusting the name. Do not carry this map to another serial device just because it also wears a DB9: RS-232 equipment can use different pin conventions, and this map is specific to the DH-485 serial flavor.
Which controller port does the HMI cable connect to? #
Channel 0 on the processor: an SLC 5/0x exposes it as a DB9, a PLC-5 as a DB25, and the RJ socket on those chassis is the PC programming connection, so landing the HMI there gets you nothing.
The SLC 500 Modular Hardware Style User Manual documents the DH-485 channel on those processors, and in service you will almost always find the operator terminal on channel 0. The RJ socket next to it is reserved for the programming PC on most units you will encounter, so treat it as off-limits.
On the PLC-5 the channel is a DB25, and this DB9 map does not transplant: the three signal functions stay the same, but their physical positions on a 25-position connector are different and are not given here, so read them from that port's documentation before terminating.
One naming trap worth clearing early: despite the similar labels, PLC-5 and S5 are unrelated product families, and difference between the PLC-5 and S5 product families matters when you order adapters by name.
How do I wire and verify the replacement HMI cable? #
Build one straight-through three-conductor cable and prove it with four meter checks before power-up: three continuity readings, one pair per conductor, plus one isolation reading to rule out a short between the data pins.
- Power both ends down before you mate or re-pin anything. These serial ports are not built for live plugging, and a slip on a powered connector is how replacement projects turn into repair projects.
- Record the configuration before disconnecting the old terminal: channel 0's protocol, serial parameters and station addresses, plus the old PanelView project's communication settings.
- Wire or verify the cable pin-for-pin on the three live positions from the table above. If you are using the EA-DH485-CBL, check its ends against both ports first.
- Meter it: one continuity reading per conductor across the ends, then pin 2 against pin 3 at the same connector, which must read open.
- Land the connectors on the HMI communication port and channel 0, DB9 on the SLC 5/0x, DB25 on the PLC-5, and leave the RJ to the PC.
- Restore power, select the DH-485 driver in the HMI project, enter the recorded values, download the project, and confirm the HMI reads live controller data.
Worked example, both connectors on the bench with a 2 m DB9 cable and the meter on continuity: pin 2 to pin 2 across the ends reads low and beeps, pin 3 to pin 3 beeps, pin 5 to pin 5 beeps, which is 3 of 3 conductors proven. Pin 2 against pin 3 at the same connector reads open, so there is no short between the data pins. Total: 3 + 1 = 4 checks, 4 passes, and the cable is proven straight-through and short-free before it ever sees a live port.
What settings must match for DH-485 to come up? #
The HMI project needs the DH-485 driver pointed at channel 0, with the exact serial parameters and node addresses you recorded before the swap, because the wiring carries none of that, and matching values cannot fix a wrong cable.
| Setting | What to enter | Where it comes from |
|---|---|---|
| Protocol | DH-485 | The HMI's driver list |
| Electrical interface | RS-232, per the cable above | Port documentation and the pin check |
| Serial parameters | The recorded channel 0 values | Controller channel configuration |
| Station and node addresses | The recorded addresses | Controller and old terminal project |
No universal baud rate or parity belongs in this article, and none is needed: the values that ran the old terminal are, by definition, the working values for that channel, and entering them unchanged in the replacement is the entire configuration task. One boundary to respect: selecting DH-485 in the project does not convert a port's hardware. RS-232 stays RS-232 no matter what the software calls it.
Why does the new HMI show no communication? #
Three checks cover nearly every dead link on this swap, in this order: the cable must be straight-through on pins 2, 3 and 5, the connector must sit on channel 0 rather than the RJ socket, and the HMI's serial values must equal the recorded channel 0 settings.
| Symptom | Most likely cause on this link | First move |
|---|---|---|
| Dead at power-up | Cable not straight-through, or the plug is in the RJ programming socket | Repeat the four bench checks; confirm the connector is on channel 0 |
| Comes up, then drops | Serial parameters differ from the recorded values, or the run is long | Compare every value; shorten the cable |
| Connects but tags fail | Driver or station address mismatch in the HMI project | Verify the DH-485 driver and the recorded addresses |
The order is fixed: physical link first, port identity second, configuration third. Software cannot repair a crossed conductor or a wrong socket, so clear those two before touching a single setting.
Questions asked
Will a null-modem cable work for this DH-485 link?
No. The DH-485 serial flavor is straight-through: pin 2 to pin 2, pin 3 to pin 3, pin 5 to pin 5. A null-modem cable crosses the two data pins between the ends, so each data conductor lands on the wrong position and the link stays dead. If a null-modem is all that is on the bench, re-pin one end or use a straight-through cable instead.
How far can the RS-232 DH-485 cable run?
Plan on about 15 m (50 ft) as the ceiling. That is the nominal load limit the RS-232 standard works from for a point-to-point cable, and this flavor of DH-485 inherits it. A cabinet full of drives shortens the practical run, and low-capacitance cable stretches it a little. If the route is genuinely long, the RS-485 flavor is the one built for distance.
Can I reuse the same three pins for an RS-485 DH-485 port?
No. The 2-3-5 map belongs to the RS-232 flavor only. An RS-485 port carries complementary signals on a differential pair and supports multipoint drops, up to 32 nodes on one segment, where RS-232 serves exactly two devices. Wiring a differential port with three single-ended conductors will not communicate, so confirm that port's data terminals from its documentation before wiring.
Where do the baud rate and station addresses come from?
From the running system, before you remove anything. Read channel 0's configured serial parameters and node addresses from the controller, and the communication settings from the old terminal's project, then enter the same values in the replacement HMI's DH-485 driver. The values that ran the old terminal are the working values for that channel, so there is nothing to invent at commissioning.
Does the replacement terminal care which electrical flavor it gets?
No. The terminal's DH-485 driver runs over either electrical flavor as long as the pins carry the right signals. The port hardware decides RS-232 or RS-485, your cable matches the hardware, and the driver selection stays DH-485 either way. That is why this swap works without an interface converter.