HMI programming link dead while the PLC link still works

What the working PLC link tells you

Port 2 to the PLC and the programming port are separate circuits on the same board, each with its own line driver and its own configuration. A live PLC link tells you the panel has power, the project runs, and one serial path is healthy. The programming port is still an open question, so test it on its own.

Leave the PLC link connected while you diagnose. The process keeps its data, and you keep a known-good reference point. Save the project file before any recovery step: some panels drop their loaded project when you pull the backup battery, so a battery reset belongs at the end of the visit and only with the project file in hand.

What each symptom points to

Record the exact message the programming software gives you, then match it:

• The software cannot open the COM port. The number selected in the software and the number the PC assigned have parted company, or another program holds the port. Close every serial tool, including the PLC programming package, and read the number in the PC's device list.
• The port opens and the panel never answers. This is the case in question. The suspects, in order: panel port configuration, cable wiring against the documented cable, ground reference, port hardware.
• Timeouts and checksum errors instead of clean silence. Data is arriving damaged. That points at the ground reference or a marginal conductor, and timeout and invalid checksum errors works that pattern.
• The panel reports a communication fault on screen, or the project stops running. The problem is wider than the programming link. Check panel power and status before touching the programming port.

Clear the COM selection and the printer assignment first

Start on the PC. Read the COM number the operating system assigned to the port or the USB adapter, then select that same number in the programming software. Where the software only lists COM1 to COM4, fixing the COM port number is its own job. Retry once and write down the exact response. If the port opens and the panel answers, you are done.

Then read the panel's own setup, from its documentation. Operator panels with printer support expose settings such as printer language, printer port, paper size, orientation, color and print quality. A port assigned to a printer is unavailable to the programming software, and the symptom is plain silence, the same silence as a dead port. The port assignment lives in the panel's communication or setup menu; move the programming port back to PC programming and retry once.

Check the cable conductor by conductor, not by continuity

A continuity pass proves each conductor meets end to end. It says nothing about which pin each conductor lands on, about shorts between adjacent pins, or about the shield. A cable can pass a tester twice and still be a null-modem where the documented programming cable is straight-through, or carry a broken ground conductor.

Work the cable properly:

1. Read the documented programming cable's conductor assignments and compare it conductor by conductor.
2. Inspect both connectors for bent contacts, loose shells and damaged strain relief, with the panel powered down if its documentation says so.
3. Connect direct: no extension lead, no gender changer, no unverified adapter.
4. Swap in a known-good cable of the documented type and retry.

Keep the run short. The original RS-232 standard assumed about 15 m (50 ft) of cable, and a programming lead should be a fraction of that. Extending an RS-232 HMI cable covers what extra length costs a link.

Measure the reference before you touch grounding

RS-232 carries TxD and RxD as voltages measured against the signal-ground conductor. The standard puts a mark between -15 and -5 V and a space between +5 and +15 V at the driver, and requires a receiver to respond to anything past ±3 V. Any voltage between the two grounds subtracts from that margin, volt for volt.

A laptop running on battery is normal, and this one worked that way for six months. A floating serial interface takes its reference from the far end through the cable's ground conductor, which is why unearthed laptops program panels every day. Two things break that arrangement. An open ground conductor in the cable leaves the panel's receiver at its own idle level; receiver inputs include an internal 5 kΩ pull-down, so the port reads a silent, healthy line and never answers. Or a real potential difference exists between the two ends at the moment of connection, the classic source of both garbled serial data and damaged ports.

Safety note: never run a wire from the laptop chassis to the panel chassis as a trial fix, around equipment that just took a supply disturbance. A jumper like that can put the offset current straight through the signal ground. Plugging the laptop's charger into the 220 V socket beside the panel adds nothing on most laptops, because most adapters carry no earth pin. Measure instead: laptop connector shell to panel chassis, with the cable connected, first volts AC then volts DC, and decide from the number.

Example: laptop on battery, panel on a UPS, 3.8 V between grounds

Inputs, with sources:

• Driver minimum from the RS-232 standard: +5.0 V for a space, -5.0 V for a mark, at the laptop, measured against its own signal ground.
• Receiver threshold from the same standard: ±3.0 V at the panel.
• Ground offset, an example field reading taken with a meter: panel signal ground sits 3.8 V above laptop signal ground.
• The rest from the case: 220 V supply with a deep sag, panel fed through a UPS, six months of clean edits, cable continuity checked twice, PLC link on port 2 alive.

Rule in words: the panel sees the driver voltage minus the offset between the two grounds, and anything inside ±3.0 V counts as no signal at all.

Arithmetic:

• Space: +5.0 V - 3.8 V = +1.2 V at the panel. 1.2 V sits inside the ±3.0 V threshold, so every space is lost.
• Mark: -5.0 V - 3.8 V = -8.8 V at the panel. Past -3.0 V, so marks still arrive.
• Margin: 5.0 V - 3.0 V = 2.0 V per polarity at minimum drive.

Result: one polarity survives and the other collapses. The panel receives broken framing, and the programming software is designed to report timeouts or checksum rejects in that state, while the PLC link on port 2 keeps running because the PLC shares the panel's ground reference in the cabinet.

Decision: keep the offset under 2.0 V. At 3.8 V the reference is the fault. Fit an isolated USB-to-RS-232 adapter or an isolated serial converter, or give both ends a proper common reference following the panel documentation, and stop swapping cables and PCs.

Isolate the fault to the PC, the cable or the panel

Substitute one element at a time:

1. Confirmed COM number, documented cable, verified port assignment: retry and record the exact message.
2. Second known-good PC, same cable, this panel. If it connects, the fault is in the first PC: its port, its driver, or its software setup.
3. First laptop and cable on a second panel of the same type. If it connects there, the fault is on the first panel.
4. The failure follows the element it follows. Log every combination and its exact response.

The laptop's port has programmed other field devices, so a dead PC port is the less likely branch; a wrong COM selection on it is the common one. Burned port electronics stay last: the panel crossed the sag on a UPS with port 2 alive, so treat hardware damage as the conclusion after configuration, cable wiring, reference and a second PC all check out. If the panel's documentation allows a project download through its other port, that path uses hardware the live PLC link has already exercised, and it is a legitimate way in while the question settles.

The order that finds the fault in one visit

1. Record the exact failure: the port will not open, or the panel gives no answer.
2. Match the COM number between PC and software; close other serial programs.
3. Read the panel's port configuration; clear any printer assignment on the programming port.
4. Verify the cable's conductor assignments against the documented programming cable; swap in a known-good cable.
5. Measure the ground offset. Under 2.0 V, move on. Over 2.0 V, fix the reference before anything else.
6. Substitute a second PC, then a second panel, one at a time.
7. Call the panel's programming port hardware the fault only after steps 2 to 6 pass and the port stays silent.

Recommendation: Clear the COM selection and the printer assignment, verify the cable wiring against the documented programming cable, then measure the ground offset, in that order. Above 2.0 V between laptop and panel, fix the reference with an isolated serial interface before swapping more hardware. At or under 2.0 V, with a verified cable and a second PC still getting silence, treat the panel's programming port as the fault and use the panel's second port for downloads where its documentation allows.

Questions