IMDTouchKnowledge BaseShop main store

Troubleshooting

Why HMI Alarm Speakers Click but Audible Alarms Stay Silent

HMI and touchscreens Published 8 min read

Short answer

The setup-menu click comes from the operating system's touch-feedback path and proves only the speaker wiring. Alarm sound is a separate runtime path: confirm the alarm fires in the running .mer, enable it (registry value 3 on Series A Standard and Performance; firmware 12.106 and later with a configured audio output on Series B and C), and for waking an operator drive a 24 VDC, 100+ dB sounder from a PLC output while the alarm stays unacknowledged.

On this page
  1. What the click proves, and what it does not
  2. Sort the three silences first
  3. Confirm the alarm actually fires
  4. Enable the runtime audio path
  5. Sizing a 100 dB sounder for an operator seat 2 m from the panel
  6. The fallback that does not depend on the HMI
  7. The decision for each case
  8. Questions asked

Speakers clicking in the setup menus prove one thing: the leads land on the right terminals and the terminal's audio amplifier works. That click is the operating system's touch-feedback tone, and it runs on a path separate from the HMI runtime, so it says nothing about whether alarm audio will ever play. Work the fix in this order: confirm the alarm actually fires in the running project; enable the runtime audio path - on Series A Standard and Performance terminals that is a Windows CE registry value, on Series B and C Performance it is a minimum firmware version plus a speaker on the USB port or the 2-wire audio output connector; then, if the requirement is waking a drowsy operator over machine noise, stop relying on the terminal and drive a hardwired sounder from a PLC output that holds while the alarm stays unacknowledged.

What the click proves, and what it does not #

PanelView Plus terminals have no internal beeper or speaker. The sound in the setup menus comes from the Windows CE input configuration playing its touch-feedback tone through the audio output - a direct operating-system path that exists whether or not any HMI project is loaded.

FactoryTalk View ME's alarm subsystem is a separate client: when a message transitions into the active state, it asks the operating system to play the alarm sound. The two paths are enabled by different settings, so the feedback tone can be alive while the application audio path is dead - exactly the state that produces clicking speakers and silent alarms.

That split is why the Audible checkbox in Alarm Setup appears to do nothing. The checkbox does its job - it flags the message as one that should sound - but on a terminal the request lands on an audio path that is not enabled. The checkbox is genuinely functional on PC-based RSView runtime. If the sound has to come from the HMI application itself, that is the configuration where it works as documented: runtime on a PC at the machine, which is the case for industrial panel PCs.

Sort the three silences first #

Three failures look identical from the operator seat - silence - and they are not fixed the same way.

What you observe What it means First move
No banner, no alarm-list entry, no sound The alarm never triggered - a tag problem, not audio Force the trigger in the controller and watch the alarm display
Alarm shows, no sound, speakers click in setup menus Runtime audio path disabled Registry value on Series A; audio output and notification setting on Series B/C
Alarm shows, no sound, and no click in setup menus either Wiring, speaker power or volume Check the speaker leads, whether the speaker is powered, and the terminal volume
Sound plays once, then never again Trigger bit latched; sound fires on each new activation Watch the trigger bit clear between events
Sound starts and cuts off instantly A Silence or Acknowledge is being driven from logic Trace the Silence/Ack tag

Start with the first row. Half a shift gets lost inside regedce on terminals where the alarm trigger was never scanning.

Confirm the alarm actually fires #

Work down the list and stop at the first check that fails.

  • In FactoryTalk View Studio (v9 on this project), open Alarm Setup and check the trigger tag, the trigger type - value or bit - and the trigger value matched to the message. A message with no matching trigger value never activates, whatever the audio settings say.
  • Put the trigger tag on a diagnostic screen and watch it change while you force the condition in the controller. A tag that never scans explains everything by itself.
  • Force the condition and look for the banner or the alarm-list entry. A visual alarm means the alarm subsystem works and the fault is downstream in audio. No visual alarm means stop here and fix the trigger.
  • Check that the terminal is running what you edited: Alarm Setup and the audio notification setting live inside the .mer, so rebuild the runtime application and download it after every change. If the terminal is detected but the download fails, follow why an HMI is detected but the project download fails.
  • Confirm nothing in the logic or a startup macro is holding a Silence or Acknowledge-All high.

Enable the runtime audio path #

Which fix applies depends on the hardware generation - read the product label before editing anything.

Series A Standard and Performance: the registry value #

  • Close the runtime and exit to the Windows CE desktop. Desktop access is restricted on Standard terminals; enable it from the terminal's configuration menu first if the desktop will not open.
  • Run regedce.
  • Open HKEY_LOCAL_MACHINE\ControlPanelInputConfig and set the value to 3.
  • In the CE control panel, confirm volume and sounds output is enabled and not at minimum.
  • Reboot the terminal - a runtime restart is not enough - reload the .mer and force the alarm again.

Edit carefully: a wrong registry edit on a CE terminal can cost a firmware reload, and the machine sits down while you re-image it.

Series B and C Performance: firmware and the audio output #

Series B and C Performance terminals support the configured alarm audio output in firmware 12.106 and higher, with sound leaving through the USB port or the 2-wire audio output connector; the Series A registry value is not part of that generation's fix. The user manual's purpose for the audio hardware matches yours: connect a speaker or amplifier to announce alarms, give feedback of operator actions and carry video sound. Check the output's rating in the manual - if it is line-level, the speaker must be powered.

On a PanelView Plus 6 or PanelView Plus 7 Performance, a USB speaker is a supported path: attach it to a USB port and either restart or power cycle the terminal so the audio device enumerates.

Project side, navigate to Runtimes → Alarm Display Settings and, under Audio Settings, enable audible alarm notification; keep the per-message Audible flag set; rebuild and download. Then verify from the operator's ear: force the trigger three times in a row, power-cycle the terminal and repeat - a change that does not survive a reboot is the most common false victory on these terminals.

Sizing a 100 dB sounder for an operator seat 2 m from the panel #

Inputs: a sounder rated 100 dB SPL at 1 m - the floor of the 100+ dB class used for this job - and an operator ear 2 m away, the distance in this case, where the operator sits at the panel inside the machine cab. Substitute your own distance and rerun the same two lines.

Rule: a point source in open air loses 20·log10(d2/d1) dB between distances d1 and d2, which is 6 dB per doubling of distance.

Arithmetic: 2 m is one doubling from the 1 m rating point, so the level at the ear is 100 - 20·log10(2) = 100 - 20 × 0.301 = 100 - 6 = 94 dB. At 8 m - three doublings - the same sounder delivers 100 - 20·log10(8) = 100 - 20 × 0.903 = 100 - 18 = 82 dB. To hold 94 dB at the ear at 8 m instead, the rating must rise by the same 18 dB: 94 + 18 = 112 dB at 1 m.

Result: about 94 dB SPL at the ear at 2 m, about 82 dB at 8 m.

Decision: mounted within about 2 m of the seat, the 100 dB class does the wake-up job with roughly 94 dB at the ear. Moved out to 8 m, the same unit leaves 82 dB, which running hydraulics will bury - so keep the sounder at the seat, or specify the 112 dB class for that distance. These are free-field numbers; walls and the cab interior move the result a few dB either way.

The fallback that does not depend on the HMI #

A terminal's speaker path dies with the terminal - locked desktop, crashed runtime, reboot - so terminal audio disappears exactly when things go wrong. Drive the sound from the controller instead:

  • In the PLC, feed an alarm-active bit and an inverted acknowledged bit into an on-delay timer. Set the delay to a few seconds: long enough that nuisance alarms do not scream constantly, short enough to catch the dozing operator. Timer done energizes the output, and the output holds until the alarm is acknowledged.
  • Feed a 24 VDC panel-mount siren in the 100+ dB class from that output and mount it where the operator is - the cab - not down in the ground-level I/O panel.
  • With no spare output, pick up 24 VDC across an existing fault-indication lamp circuit so the sounder sounds whenever the fault lamp is on.

This sounder is an attention alert, not a safety function: the emergency stop and any safety-rated shutdown stay on their own rated hardware.

The decision for each case #

  • The alarm never shows on the screen: the trigger is the fault - fix it before touching any audio setting.
  • The alarm shows on a Series A Standard or Performance terminal: apply the registry value above (3), reboot, reload the .mer, and enable audible alarm notification on the next rebuild.
  • The alarm shows on a Series B or C Performance terminal: reach firmware 12.106 or higher, connect a speaker to the USB port or the 2-wire audio output connector, power cycle after attaching a USB speaker, and enable audible alarm notification.
  • The sound has to wake an operator over machine noise: drive a 24 VDC, 100+ dB sounder from a PLC output that holds while the alarm stays unacknowledged, sized by distance - 94 dB at the ear at 2 m, or a 112 dB unit at 1 m to hold that level at 8 m.

Questions asked

Does the Audible checkbox work on a PC-based runtime instead of a PanelView terminal?

Yes. On PC-based RSView or FactoryTalk View runtime the Audible checkbox is functional: the sound plays through the PC's sound scheme, configured from the Windows control panel's Sounds applet. On a PanelView Plus terminal the same checkbox only produces sound when the terminal's runtime audio path is enabled and a speaker is connected, which is why it can appear to do nothing.

The alarm sounded once and never repeats. Why?

Alarm annunciation fires on the transition into the active state, not while the condition merely persists. If the trigger bit latches and never clears, there is no new transition, so you hear one sound per shift. Make the trigger drop out between events - pulse it, or drive the alarm from a condition that resets itself - and the sound returns on every new activation.

The sound starts and stops immediately - what kills it?

A Silence or Acknowledge command is being driven from somewhere: a button mapped as Acknowledge-All, or a controller bit stuck high that the project maps to the alarm's acknowledge. Trace that tag, force it low, and re-trigger the alarm. If the sound then persists, the fault is in that mapping or in the logic driving the bit, not in the audio path.

Can I tap 24 VDC for the sounder from an existing fault lamp?

Yes. Energize the sounder from the same output that drives an existing fault-indication lamp, so it sounds whenever the lamp is on and the alarm logic needs no changes. Before landing the wires, check the 24 VDC supply has headroom for the sounder's rated current on top of the lamp, and tap the switched side so the sounder goes off with the lamp.

Is the hardwired sounder a safety function?

No. It is an attention alert tied to a process alarm staying unacknowledged; its job is waking an operator. The emergency stop and any safety-rated shutdown keep their own rated hardware and logic, and neither the sounder nor its PLC output gets wired into those circuits as a substitute.

Keep reading

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    HMI and touchscreens

  • Selection guide

    Planning an HMI Terminal Replacement From an Older Operator Panel

    Decide an operator-terminal replacement on installed cost — the terminal, cutout adaptation, application software, engineering, commissioning, downtime and a spare — never on terminal price alone. Measure the opening against the replacement's documented cutout range and count displays before ordering: a slightly smaller terminal needs a bezel adapter, and a large converted application can force the higher-performance model. Convert in the same brand when the source project opens cleanly; rebuild cross-brand when you accept the extra engineering hours for source control.

    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