IMDTouchKnowledge BaseShop main store

Troubleshooting

Getting Unconfirmed Alarm Status Out of a C-More Panel

HMI and touchscreens Published 7 min read

Short answer

No tag on the EA9 exports alarm-confirmation state to the PLC, so the buzzer cannot follow the C-more confirm action. Latch the alarms in the PLC, acknowledge them with a panel pushbutton that writes a PLC bit, and run the buzzer while any alarm stays unacknowledged; the PLC to Panel Beep ON/OFF tag can mirror the same state onto the panel beep.

On this page
  1. Can I get the number of unconfirmed alarms into a PLC tag?
  2. Does the Beep ON/OFF tag tell the PLC when an alarm is confirmed?
  3. How do I stop an external buzzer when the operator acknowledges?
  4. What should the PLC acknowledgment logic look like?
  5. Should the panel beep follow the same acknowledgment?
  6. How do I test the buzzer before it goes back to service?
  7. What if the buzzer must match the C-more alarm list exactly?
  8. Questions asked

You cannot pull unconfirmed-alarm state out of an EA9 C-more panel. The documented tag interface between panel and PLC has no alarm-confirmation tag — neither an unconfirmed-alarm count nor a discrete bit — and the only alarm-adjacent tag, Beep ON/OFF, works in the other direction: PLC logic switches the panel beep, and nothing flows back. The workable design puts the acknowledgment where the buzzer is. Latch alarms in the PLC, acknowledge them from a pushbutton on the panel that writes a PLC bit, and run the buzzer while any latched alarm remains. The sections below give that logic, the ANSI/ISA-18.2 state model behind it, and the tests to run before the horn returns to service.

Can I get the number of unconfirmed alarms into a PLC tag? #

No. The EA9 tag interface has no tag for alarm confirmation at all — neither an unconfirmed-alarm count nor a discrete unconfirmed bit — so the alarm list's confirm state cannot be exported to the PLC.

The tag configuration between the panel and the controller falls into two groups: tags the panel writes to the PLC, and the PLC to Panel group, which holds items like Beep ON/OFF. Alarm confirmation appears in neither group, and no documented data-transfer object carries the alarm list's confirm state outward. Alarms themselves are defined in the Event Manager against PLC tags, and messages can embed PLC tag data — so the arrival condition of every alarm already exists as a bit in your controller. Only the confirm action is trapped inside the panel. That asymmetry is what makes the workaround below clean.

Does the Beep ON/OFF tag tell the PLC when an alarm is confirmed? #

No. Beep ON/OFF is a control input, not feedback: PLC logic turns the panel beep on and off with it, the beep stays on until the bit turns off, and no alarm or confirmation state flows back.

The direction matters more than the name. The tag lives on the PLC to Panel tab, so the PLC is the writer and the panel is the listener. Using it to detect confirmation inverts the data flow and simply does not work: the panel never writes that tag, so it holds whatever your logic last put there. If you force the bit and the panel stays silent, you are looking at a speaker or configuration fault, not a tag fault — see why alarm speakers click but audible alarms stay silent for that diagnosis.

How do I stop an external buzzer when the operator acknowledges? #

Give the buzzer its own acknowledgment in the PLC: sound it from a PLC alarm bit, and stop it with an acknowledge bit that a C-more pushbutton writes — do not try to infer the panel's confirmation.

Build it from four pieces:

  • One condition bit per alarm, the same tag the Event Manager alarm uses as its trigger.
  • One unacknowledged latch per alarm, set the moment the condition goes true and cleared only by the acknowledge action.
  • One acknowledge pushbutton on a panel screen, assigned to a bit the panel writes to the PLC.
  • One buzzer output driven by those latches.

Place the acknowledge pushbutton where the alarm banner cannot hide it; if the banner and the button fight for screen space, there is a documented approach to working around the EA9 alarm banner covering buttons. Decide at design time who acknowledges what: this PLC acknowledge is a distinct function from the alarm list's own confirm, so tell operators which button stops the horn, or the buzzer and the list will disagree and nobody will trust either.

What should the PLC acknowledgment logic look like? #

Latch each alarm when its condition is true, clear the latch only on acknowledgment, and run the buzzer while the count of latched alarms is 1 or more — the state model ANSI/ISA-18.2 defines.

That standard, published internationally as IEC 62682, models every alarm with an active state and an acknowledged state. The horn belongs to the unacknowledged-and-active combination: acknowledgment silences it while the alarm remains active, and the alarm returns to normal only when its condition clears.

The names below are illustrative, not panel object names: AL1 through AL4 are Boolean alarm condition bits, initially false; U1 through U4 are Boolean unacknowledged latches, initially false; ACK_ALL is the Boolean pushbutton bit, initially false; COUNT is an integer, initially 0; BUZZ is the Boolean output to the horn, initially false.

  • On a rising edge of ALn, set Un.
  • On a rising edge of ACK_ALL, clear U1 through U4.
  • COUNT = U1 + U2 + U3 + U4.
  • BUZZ = (COUNT >= 1).

Walk it through three events:

  • 08:12 — the high-temperature and door alarms go true, so U2 = 1 and U4 = 1 while U1 = 0 and U3 = 0. COUNT = 0 + 1 + 0 + 1 = 2, and 2 >= 1, so BUZZ = 1.
  • 08:13 — the operator presses the acknowledge pushbutton. U1 through U4 all clear, COUNT = 0 + 0 + 0 + 0 = 0, and 0 >= 1 is false, so BUZZ = 0. AL2 and AL4 are still true, so both alarms stay on the list until the conditions clear — the horn stops, the indication does not.
  • 08:20 — a pump fault arrives, so U3 = 1. COUNT = 0 + 0 + 1 + 0 = 1, and 1 >= 1, so BUZZ = 1 again. A new alarm sounding the horn after an earlier acknowledgment is exactly the behavior the state model expects.

If different alarms must be acknowledged individually, replace ACK_ALL with per-alarm acknowledge bits and clear only the latch each bit serves; the buzzer rule does not change.

Should the panel beep follow the same acknowledgment? #

Yes — drive the panel beep from the same unacknowledged-any bit through the PLC to Panel Beep ON/OFF tag, so the panel beep and the external buzzer silence together on one acknowledgment.

Assign a PLC tag to Beep ON/OFF on the PLC to Panel tab and let BUZZ drive it. Because the beep stays on until the bit turns off, a level-driven bit like BUZZ is the natural fit. The horn and the beep then share one acknowledgment, and an operator cannot silence one and leave the other running. If the panel polls the PLC over a serial link, expect the beep to lag the buzzer by the poll interval, and read why alarm beeps sound irregular over serial PLC links before blaming the tag.

How do I test the buzzer before it goes back to service? #

Force each alarm condition, acknowledge it, then add a second alarm before acknowledging, and verify the buzzer at the output card and at the device — the horn must stay on while any alarm is unacknowledged.

Work the list in order:

  1. Force AL1 true; the buzzer must energize within one PLC scan.
  2. Press acknowledge; the buzzer must drop out while AL1 stays true and the alarm stays visible on the panel.
  3. Clear AL1; the alarm indication must return to normal.
  4. Force AL2 and AL3 true together, acknowledge, then force AL4 true immediately after; the buzzer must sound again, proving re-annunciation after acknowledgment.
  5. Unplug the panel link while an alarm is unacknowledged; the buzzer keeps running, because the latches, the acknowledge bit and the output all live in the PLC.
  6. Confirm the horn is audible at the machine, and reset every forced bit before handover.

One safety note: this buzzer is operational annunciation only — emergency stops and protective interlocks stay hardwired and independent of the HMI and this logic.

What if the buzzer must match the C-more alarm list exactly? #

It cannot be done through the documented tag interface: the EA9 exposes no confirmation-state signal, so the list's own confirm action cannot drive a PLC output. The workable paths are PLC-owned acknowledgment or a vendor-confirmed interface in a newer software release.

The documented interface for this panel generation carries no alarm-confirmation tags, so treat that as the design basis rather than a guess. Software gains features over time, so before committing a design that depends on list-native confirmation, open the tag configuration screens in your installed project and look for a confirmation-related entry; if one exists in your version, verify what it actually represents before wiring an output to it. If list-native confirmation is a hard production requirement and your version shows nothing, take it to the vendor with the panel model, firmware version and project configuration, and ask directly.

The decisions, by case:

  • Buzzer must mirror the alarm list's confirm action exactly: not available on the documented interface; escalate to the vendor before shipping anything.
  • Buzzer can follow a PLC acknowledgment: build the latch logic above; it is complete and survives panel failure.
  • Only an audible at the panel is needed: the Beep ON/OFF tag alone does it, driven by whatever PLC logic you choose.

Questions asked

Is there a system tag for the total number of alarms in the list?

No. The documented tag set between the EA9 and the PLC carries no alarm count of any kind, confirmed or unconfirmed. If you need a count, compute it in the PLC from the alarm condition bits you already own, for example by summing the individual unacknowledged flags, and display that number on the panel as an ordinary numeric tag.

Will the alarm list's own confirm button stop my buzzer?

No. The confirm action inside the C-more alarm list stays inside the panel; no tag carries it to the PLC. Put a separate acknowledge pushbutton on the screen, assign it a bit the panel writes to the PLC, and use that bit's rising edge to clear the unacknowledged latches. Train operators to use that button for the horn.

What happens to the buzzer if the panel or its link goes down?

The buzzer keeps working. Because the alarm latches, the acknowledge bit and the buzzer output all live in the PLC, a failed panel or a broken communication cable cannot silence the horn or clear a pending acknowledgment. Only the panel-local beep is lost with the panel, which is one more reason to keep the horn on a PLC output.

Can I use Beep ON/OFF as an alarm output from the panel?

No, the direction is wrong. Beep ON/OFF is a bit the PLC writes to control the panel beep, and the beep stays on until that bit turns off. It is a good way to make the panel beep track your PLC acknowledgment logic, but it never reports alarm or confirmation state back to the controller.

Is acknowledging an alarm the same as clearing it?

No. Under the ISA-18.2 state model, acknowledgment only silences the audible annunciation; the alarm stays active and displayed until its condition returns to normal. Clear the horn on the acknowledge action, clear the indication on the condition itself, and let any new alarm arriving later sound the horn again.

Keep reading

  • Troubleshooting

    Why HMI Alarm Beeps Sound Irregular Over Serial PLC Links

    The panel samples the toggle bit once per serial request round, and the PLC services one request per scan, so the round takes about request groups × scan time. When that exceeds the 100 ms toggle interval, transitions are missed and the beep stutters. Move dependable timing to the panel's own buzzer or a PLC-driven physical buzzer.

    HMI and touchscreens

  • Troubleshooting

    Why rebuilt HMI runtime files show #### for PLC tags

    Hashes on every tag after transferring a rebuilt WinCC Runtime Advanced project are a display symptom, not a communication code. Restore the working runtime files as a baseline, add an alarm view showing buffered System alarms, and branch on the message text: connection establishment, TLS certificates and clocks, hidden project pairing, or single-field formatting.

    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