Why an HMI buzzer register is not an alarm trigger

Can you make an HMI panel buzzer beep on command?

No. In the register list that documents M+13, the register's only function is silencing the key beep on button presses; there is no command bit that sounds the buzzer, so a process alarm belongs on a horn or stack light switched by a PLC output.

A mute control changes what happens when a key is pressed. An alarm has to fire with nobody near the panel, at a moment no one chooses to touch anything, so a function scoped to key presses cannot carry it even though both produce sound. The register list is also the whole boundary of what is documented: if a trigger address existed, it would sit next to the mute bit with its own description, and it does not. Writing a value to an address the list does not describe is a change to an undocumented setting on a machine that is running, so the printed list is where the search ends.

What does the M+13 register actually do?

M+13's documented job is mute control for operator feedback: it disables the buzzer on button presses so keys stay quiet. The register list names no alarm-trigger address and no second buzzer function, so writing M+13 from the PLC will not produce an alarm sound.

Treat M+13 as a settings bit for the keypad. Some sites mute the chime because a beep on every key press gets wearing on a busy screen; others leave it on as touch feedback. Toggling it changes one thing, whether the next button press beeps, and its documented scope ends there. If beeps die later and nobody remembers why, this register is the first place to look. When a beep stops in the middle of a running session instead, that is a different fault with its own causes, covered in our article on the two causes behind an HMI beep that stops on button press.

Which symptom points to which cause?

Match the behavior before you change logic: a key beep that went silent points to M+13 doing its mute job, an alarm with no sound at all points to a missing horn path, and a horn that keeps sounding points to missing acknowledge logic.

• Beeps stopped after a register write. M+13 did exactly its documented job. Clear it and the key beeps come back; no alarm logic was involved.
• Alarm fires, nothing sounds anywhere. There is no annunciation path to lose, because the panel documents no buzzer trigger. The horn output has to be added.
• The alarm shows on screen but nobody hears it. The visual path works and the audible one does not exist. Give sound to a horn on an output point; a screen that beeps only when touched cannot watch a process.
• The horn sounds and cannot be silenced, or the light dies with the sound. Silence and acknowledge collapsed into one bit or got skipped. Build the sequence in the next sections before release.
• A guessed write changed something unrelated. Restore the documented value and stop probing. Undocumented addresses are not spare parts.

How do you annunciate a process alarm the supported way?

Annunciate from the hardware the alarm lives in: the PLC switches a horn or stack light through an output point, the panel shows the message on screen, and a silence pushbutton mutes the horn while the lamp stays lit until the condition clears.

Split the two jobs on purpose. The visual alarm stays on the panel's alarm list, where operators expect it. Where operators move away from the panel, a second screen earns its place: for a plain wall board that shows a prepared alarm page, our panel-mount displays play images and video from a microSD card or USB, with no subscription, and they take no signal input, so the PLC connection and the horn stay with the control panel. Keeping that display read-only is a specification decision, and our article on specifying a read-only process display for a plant covers what to ask for.

The audible alarm comes from a horn or stack light wired to an output point, because sound has to reach the floor whether or not anyone stands at a screen. The silence and acknowledge logic lives in the PLC, next to the alarm condition, where a panel power cycle cannot disturb it.

How do you size the PLC output for the horn?

Size from the device nameplate: divide the rated watts by the rated voltage to get the current, then compare it with the output point's rating, which compact controllers commonly set at 0.5 A per transistor point. Under the rating, switch directly; over it, switch an interposing relay.

The nameplate is the whole calculation. Divide the rated watts by the rated volts; a horn marked 3.6 W draws 0.15 A at 24 V DC. The limit to compare it with is the output point rating from your module's specification sheet: compact controllers commonly rate transistor points at 0.5 A each, with the common terminal rated higher. Buy the horn or lamp version whose voltage matches the control supply the panel and sensors already run on, and feed the horn from that supply through a fuse sized per the module specification. Anything inductive on the point, a relay coil or a sounder with one, gets the suppression diode its datasheet calls for, wired across the coil. One safety note: do the wiring with the control panel isolated. The 24 V DC side is the safe side; the supply's input is not.

Worked example: does one horn plus one lamp fit a single output point?

Yes: a horn nameplated 24 V DC, 3.6 W draws 3.6 W / 24 V = 0.15 A, a stack light lamp element at 1.2 W on the same supply draws 0.05 A, the combined 0.20 A sits under a 0.5 A point rating, so one point switches both directly.

The nameplate figures in this example are the inputs. Horn: 3.6 W gives 3.6 W / 24 V = 0.15 A, which is 150 mA. Stack light red lamp element: 1.2 W gives 1.2 W / 24 V = 0.05 A, which is 50 mA. One output point switches both together when the alarm fires: 0.15 A + 0.05 A = 0.20 A against a 0.5 A point rating, leaving 0.30 A spare. That is direct switching, no interposing relay, and horn and lamp come on and drop out together, which is what the sequence in the next section wants.

Move an input and the decision moves. A larger sounder nameplated at 1 A exceeds the 0.5 A point, so the point switches an interposing relay: with the relay coil rated at 0.5 W, the point supplies 0.5 W / 24 V = 0.021 A, about 21 mA, and the relay's contacts carry the 1 A horn. The contacts take the load, the coil takes its suppression diode.

What should the alarm sequence do when an operator silences it?

Silence mutes the horn only: the lamp stays lit and the alarm stays active until someone acknowledges it and the condition clears, and a new condition sounds the horn again even while the first is still silenced.

ISA-18.2, the standard plants use to manage alarm systems, puts audible annunciation in the operator's toolkit: a sound that can be silenced while the visual state holds until the condition is acknowledged and cleared. Written as states:

• Normal: horn off, lamp dark.
• Alarm: horn sounds, lamp flashes.
• Silence pressed: horn goes quiet, lamp keeps flashing. A new condition sounds the horn again.
• Acknowledge: lamp holds steady while the condition lasts.
• Clear: lamp goes dark and the sequence rearms.

The logic is a latch on the alarm bit with the silence pushbutton breaking only the horn branch; a horn latch with a silence pushbutton worked out rung by rung shows the rungs.

How do you test the horn path before you release it?

Test the chain from condition to sound: induce the condition the approved way, check the horn sounds with no key pressed, check silence leaves the lamp flashing, and check that clearing the condition darkens the lamp and rearms the sequence.

1. Induce the alarm condition through the site's approved test means, a test input or a supervised trip, never by masking a live alarm.
2. The horn sounds with nobody near the panel and no key pressed.
3. The silence pushbutton stops the horn and the lamp keeps flashing.
4. The condition clears: the lamp goes dark, and a second induced alarm sounds the horn again, which shows the sequence rearmed.
5. Write M+13 to its mute function and run the alarm once more: the horn still sounds. Key beeps and the alarm path stay independent.
6. The event reaches the log. Where the controller stores few alarms, our article on logging PLC alarms to a circular event buffer with separate pointers covers the pointer discipline.
7. Leave a line in the maintenance notes: M+13 mutes key beeps, and the register list documents no buzzer trigger. The next engineer should not have to rediscover that.

Recommendation: Sound process alarms with a horn or stack light on the control supply, sized from the nameplate and switched by a PLC output when the combined current stays under the output point's rating (commonly 0.5 A per point on compact controllers), and switch an interposing relay when it does not; reserve M+13 for operator key-beep preference, and give the horn silence and acknowledge logic before the change goes live.

Questions