Sharing one HMI programming cable with the PLC link

Why one cable can do both jobs

The assembly is built as 2 m (6.56 ft) of RS-232 with a six-conductor RJ12 plug on each end, made for the panel's programming port. The cable carries the signals on those conductors and nothing else, so the same leads that reach the PC also reach the PLC. Power the panel down, move the PC end to the PLC serial port, power up, and the panel talks over the same wires.

The catch is in the software, not the copper. A serial link needs the panel and the PLC to agree on five values: the protocol driver, the baud rate, the parity, the stop bits and the station address. The cable sets none of them, so a swap that worked at the bench can still fail at the machine. Read the PLC side of the five values from the PLC programming software, enter the same values in the panel's protocol setup, and check the panel driver list before you tune serial settings, because a wrong driver returns no reply even when every other value matches. Those five values belong on a card taped inside the enclosure door; they are the first thing to verify on any link between a panel and a PLC, and the same check order runs through the shop-floor screen and link fixes on this site.

What each symptom points to

• The download never starts. That is the PC side, not the panel link: the wrong serial port selected in the programming software, a USB-to-serial adapter that never created a port, or an RJ12 plug whose latch never clicked home. Read the port number the adapter created in the PC's device manager, reseat both plugs, and check the programming cable's power pin next.
• The download finishes, then the panel shows a communication error against the PLC. A settings mismatch or the wrong port on the PLC. Compare all five values against the PLC programming software, and confirm the plug is in the serial port configured for the protocol you selected, not another port on the same PLC.
• The link ran at the bench and drops in the panel. Routing. RS-232 is single-ended and tolerates noise poorly; a run laid beside a drive output cable or a contactor coil collects enough switching noise to corrupt data. Re-route it and re-test before you replace anything.
• Values come back garbled or the link drops at random. The run is too long for its bit rate, or the latch tabs are worn from repeated swaps. The length figures are in the next section. If the PLC speaks Modbus RTU and you see no replies or address errors, that pair of faults is split cause by cause in the Modbus RTU no-reply and address errors article.

How far the RS-232 run can go

The EIA/TIA-232 standard sizes a run by capacitance at the receiver: 2500 pF. A typical serial cable contributes about 50 pF per foot, and 50 ft of that cable is 2500 pF, which is where the classic pairing of 50 ft (15 m) with 19,200 bit/s comes from. Higher bit rates cut the allowed length hard:

At 9600 bit/s the same load budget buys more length. If the PLC sits farther away than the table allows, the answer is a different interface, and the per-interface figures for RS-232 against RS-422 and RS-485 are set out in the HMI-to-PLC serial cable distance article. When the gap is small, adding 10 ft to a panel cable safely is its own short job.

Worked example: a 2 m panel cable extended 10 ft at 19,200 bit/s

The inputs, and where each comes from:

• Shipped programming cable: 2 m (6.56 ft), the built length of the assembly.
• Extension: 10 ft of the same cable type, to reach a PLC mounted one bay down the enclosure line.
• Link speed: 19,200 bit/s, the value entered in the panel protocol setup and the PLC port, and the speed the 15 m figure is quoted at.
• Load model: 2500 pF budget, 50 pF per foot of typical cable.

The rule in words: the run is sound only when it fits two limits at once, the distance figure for its bit rate and the 2500 pF capacitance budget.

The arithmetic:

• Length: 6.56 ft + 10 ft = 16.56 ft. 16.56 ft × 0.3048 m/ft = 5.05 m.
• Capacitance: 16.56 ft × 50 pF/ft = 828 pF. That is 828 ÷ 2500 = 33 percent of the budget, leaving 1672 pF, which at 50 pF/ft is another 33 ft of cable in hand.
• Distance check at 19,200 bit/s: 5.05 m against the 15 m figure. It passes with 9.95 m to spare.
• Speed check on the same run: the 57,600 bit/s guidance is 5.0 m, so 5.05 m is already past it. The 115,200 bit/s guidance is 2.5 m, so only the bare 2 m cable fits.

The result and the decision: run the extended 5 m link at 19,200 bit/s or slower. At 57,600 bit/s, cut the extension or drop the speed. At 115,200 bit/s, the bare 2 m cable is the most the guidance allows, and the extra distance belongs in a different interface.

Checks first, then the permanent fix

1. Commission on the programming cable. Download the project, power the panel down, move the plug from the PC to the PLC serial port, and match the five values. Read live values from the PLC to prove the link before anything else.
2. Prove writes before motion. Write to a register that moves nothing first, and hand the link a machine function only after that read-back is clean; the write-test order for an operator panel link is written for exactly this step.
3. Fit the permanent cable. Buy or build a dedicated panel-to-PLC cable to the conductor arrangement in the panel maker's cable drawing, at the length the drawing gives. The shipped assembly goes back in the laptop bag where it belongs.
4. Route the permanent cable in the duct, away from drive output cables and contactor coils, and leave slack so a door swing cannot pull on either RJ12 plug.
5. Label both ends with the port each plug fits and keep one spare modular cable in the enclosure. Latch tabs break first on cables that get swapped between a PC and a PLC, and a spare turns that failure into a two-minute fix.
6. Verify. Power-cycle the panel and the PLC separately. The link must re-establish on its own after each power cycle, with no settings changed by hand.

Recommendation: Use the 2 m (6.56 ft) programming cable to commission the panel and to cover a breakdown, then leave a dedicated panel-to-PLC cable in place. Keep the RS-232 run inside 15 m (50 ft) at 19,200 bit/s, inside 5.0 m at 57,600 bit/s and inside 2.5 m at 115,200 bit/s. Past those figures, change the interface.

Questions