IMDTouchKnowledge BaseShop main store

Troubleshooting

How to check PROFIBUS termination when an HMI reads no data

HMI and touchscreens Published 6 min read

Short answer

Isolate power, set both segment ends' termination switches ON and every middle connector OFF, then measure between A and B at any opened connector: two 220 Ω terminations in parallel give 110 Ω ± 5 Ω on a healthy bus. About double means one termination is dead, open means a broken conductor, near zero a short; if the bus reads right, the fault is in the driver, address or transmission-rate configuration.

On this page
  1. What resistance should the PROFIBUS bus read between A and B?
  2. Which connectors get termination ON and which get OFF?
  3. Why can one intermediate switch left ON blank the whole bus?
  4. How do I measure the bus resistance safely?
  5. What does the ohm reading say is broken?
  6. Why cycle the termination switches even when the positions look right?
  7. What if the bus reads healthy but the HMI still shows no data?
  8. Questions asked

An HMI that suddenly reads no machine data on a PROFIBUS link is checked from the wire up, and one number decides the physical layer: with power isolated and both end terminations switched ON, a healthy segment reads the parallel combination of its two terminating resistors between the A and B conductors at any opened connector. Set the switches first (the two physical cable ends ON, every connector between them OFF), then isolate and measure. A reading near a single terminator's value, an open circuit or near zero names the failed part directly; a correct reading moves the hunt to the driver, station address and transmission rate in the HMI project.

What resistance should the PROFIBUS bus read between A and B? #

With both end terminations switched ON and all power removed, a healthy PROFIBUS segment reads 110 Ω ± 5 Ω between the A and B conductors at any opened connector, because the two 220 Ω terminating resistors sit in parallel across the pair.

Each segment end puts one terminator across the pair. A PROFIBUS connector builds that into a three-resistor network — 380 Ω, 380 Ω and 220 Ω in Siemens parts — that the slide switch connects; plain RS-485 practice instead speaks of a 120 Ω terminator, but the 110 Ω measured value is the switched PROFIBUS connector case. Termination belongs to the RS-485 physical layer, not to the protocol above it, so the same check applies whatever rides on the pair — the same layer that matters when choosing the RS-485 protocol for one HMI and multiple PLCs.

Calculated example on a 120 m segment, measured at one end:

  • Two terminations in parallel: (220 × 220) ÷ (220 + 220) = 48 400 ÷ 440 = 110 Ω.
  • Cable resistance limit 110 Ω/km loop, i.e. 55 Ω/km per conductor; the far terminator sits behind 0.120 km × 55 Ω/km = 6.6 Ω.
  • Far branch: 220 + 6.6 = 226.6 Ω in parallel with the near terminator: (220 × 226.6) ÷ 446.6 ≈ 111.6 Ω.

Decision: accept 105 Ω to 115 Ω as healthy. Cable length moves the reading toward the top of that band only on runs of hundreds of metres; a missing termination, an open conductor or a short lands far outside it.

Which connectors get termination ON and which get OFF? #

Only the two physical ends of the segment carry termination ON; every connector in between, where the cable passes straight through, stays OFF — one cable entering makes a device an end, two cables make it a pass-through.

A three-station layout checks out like this:

  • HMI at one cable end: switch ON.
  • PLC in the middle with two cables: switch OFF.
  • PLC at the far cable end: switch ON.

Count cables first, then trace the run. The cable route, not the device type, decides the endpoints — watch for a cabinet that continues the segment in another direction, or a stub someone left on a terminal.

Why can one intermediate switch left ON blank the whole bus? #

An intermediate connector switched ON terminates the line mid-segment, and on connectors whose switch also breaks the through-connection it disconnects every device downstream, so one wrong switch can blank the entire bus including the HMI.

On many PROFIBUS connectors the ON position physically separates the incoming from the outgoing cable, which is exactly what you want at an end and destructive in the middle: every device after that connector disappears from the bus, and the mid-segment terminator adds reflections on top. Keep every station between the two ends switched OFF, and when a segment "mostly" works, suspect a mid-bus switch before anything else.

How do I measure the bus resistance safely? #

De-energize the whole segment before touching the meter: an ohmmeter supplies its own test current, so any live voltage on the pair both ruins the reading and can damage the instrument — then read between A and B at any connector.

  1. Stop the machine and isolate every source feeding the segment — the HMI supply, each PLC panel, any repeater — under the site's isolation procedure.
  2. Prove dead before selecting ohms: verify zero volts between A and B, and from each conductor to the reference.
  3. Open any connector on the segment and leave both cables landing on it where present, so the segment stays continuous through the measurement.
  4. Measure between the A and B terminals; on standard PROFIBUS cable those conductors are green (A) and red (B). The reading is polarity-independent, but note any suspect connector for a polarity check later.
  5. Record the reading together with every switch position on the segment.

What does the ohm reading say is broken? #

A reading near one terminator alone means one termination is missing, an open or megohm reading means no termination or a broken conductor, and a near-zero reading means a short across the pair — each points at a different repair.

Power-off reading across A–B What it means What to do
105–115 Ω Both terminations in circuit, pair continuous Restore power and check the configuration layer; also verify no connector has A and B swapped, which a resistance reading cannot see
Roughly one terminator plus a few Ω Only one termination in circuit Split at a middle connector and measure each half: the good half reads about that, the dead half reads open
Open circuit (megohms) Both terminations absent, or a conductor broken Confirm both end switches, then continuity-test each conductor section by section
Near 0 Ω Short between the conductors Inspect strand ends, terminal screws and crushed cable
Unstable or drifting Intermittent contact in a switch, screw terminal or clamp Cycle the switches, re-tighten, re-measure; replace the connector if it stays noisy

With a cable section fully disconnected from devices and terminations, A to B must read open, and each conductor end to end must read close to its calculated value — no more than the per-conductor limit applied to the section's length, as in the example above. Anything much higher is a high-resistance joint.

Why cycle the termination switches even when the positions look right? #

Switch contacts oxidize, so a switch parked in the ON position for years can still leave its terminator electrically out of the circuit; operating every switch OFF then ON and re-measuring exposes the bad contact immediately.

With power still isolated, move every termination switch through OFF and ON a few times, restore the position each connector needs, and repeat the A–B reading at the same point. A reading that changes as you cycle identifies a contact-sensitive connector — that is evidence for replacement, not a repair. Where the connector's termination network draws power from the attached device, confirm that supply is live in normal operation; a correct switch position alone does not prove a working termination.

What if the bus reads healthy but the HMI still shows no data? #

Then the fault sits above the physical layer: the HMI project's driver, station address and transmission rate must match the PLC's actual interface, because the connector shell alone does not identify the protocol riding the RS-485 pair.

An S7-200-class machine may speak PPI rather than PROFIBUS DP through the same style of connector, so read the configured connection — controller, driver, interface, station address, transmission rate — and compare it against the PLC port before touching more wire. The same two conductors carry several industrial protocols, and picking between them is its own decision — how to choose between Modbus, PROFIBUS and CANopen — but the power-off termination check applies to all of them.

A panel that runs its screens yet shows no live values over a proven wire is a communication-configuration fault, the same class as when an MER download shows no live data because the runtime kept stale communications settings. And if some tags update while others stay blank, the bus is fine — look at those tags' addresses and data types instead.

Questions asked

Can I take the bus resistance measurement with everything powered up?

No. The meter drives its own test current, so any voltage on the pair invalidates the reading and can damage the instrument. Isolate every source feeding the segment, including separately supplied panels and repeaters, and prove zero volts between A and B before switching to ohms. Terminations that draw bias from a device supply also change a live reading, so the power-off value is the only trustworthy one.

How do I find which end's termination is dead when the bus reads about one terminator alone?

Split the segment at a middle connector and measure each half toward its own end with power off. The healthy half reads roughly that same value plus its cable resistance; the half whose end termination is not switching in reads open. Cycle that end's switch through OFF and ON and re-measure, and replace the connector if the reading stays unstable.

Does it matter where along the segment I take the measurement?

No, as long as the segment stays continuous — both cables still landing on the opened connector — every point sees the same two terminations in parallel, so the healthy figure applies everywhere. Detach one cable, though, and you are reading a single half with one termination, which gives roughly double plus that half's cable resistance.

Where does termination go when the segment passes through a repeater?

A repeater electrically separates the network into independent segments, and each segment is terminated at its own two physical ends — the repeater's port counts as an end for the side it serves. Repeat the switch-and-measure procedure per segment; a healthy network reads the same power-off value on every one of them.

Does the same check work on an S7-200 PPI link?

Yes, as a physical-layer check. PPI rides the same RS-485 pair, so a correctly terminated two-end segment reads the same value with power off. What differs is the configuration layer: the HMI must be set to the interface and protocol the PLC actually runs, not the protocol the connector shell suggests.

Keep reading

  • How-to

    Programming a Fatek PLC Through a Weintek HMI Ethernet Link

    Yes — the FBs-20 can be programmed from a PC through the panel with only the console's one Ethernet cable. Bridge the panel's RS232 line over Ethernet with the panel's pass-through feature or an Ethernet-to-serial converter, present it to the PC as a virtual COM port, then open that port in WinProladder with the PLC's own baud, parity and station number and a raised timeout, because the panel's polling shares the line.

    HMI and touchscreens

  • Troubleshooting

    Why a C-more Micro Will Not Power From an H2-SERIO Port

    The H2-SERIO's three RS-232 ports supply no +5 V, so a C-more Micro panel that powered from the CPU's serial port goes dark on any of them. Feed the panel external DC power — the EA-MG-P1 option does that while Port 1's RJ12 keeps handling TX and RX — and leave the panel on its built-in Com Port 1 with Do-more Serial. Port 1 and Port 2 in the HMI name the panel's ports; A, B and C name the module's.

    HMI and touchscreens

  • Explainer

    How an HMI Works in an Industrial Control System

    An HMI displays controller tag values and writes operator inputs back to controller tags; the two paths fail independently. Trace every fault from the live controller tag value, because that one reading splits tag, binding, driver and logic faults cleanly.

    HMI and touchscreens