Troubleshooting
Why WAV Event Sounds Play in Simulation but Not on an HMI Panel
Short answer
The sound plays in simulation because the PC sound card renders the WAV file. The panel stays silent because its buzzer is a tone generator, not an audio output: WAV playback needs a terminal with an audio output or a supported USB sound card feeding powered speakers, with volume set at the speaker.
On this page
Your WAV event plays in simulation because the simulation runs on the PC's sound card. It stays silent on the terminal because the beep comes from a buzzer, and a buzzer is a tone generator: it switches on and off at one pitch and cannot reproduce a WAV file under any project setting. WAV playback needs a real audio path — a terminal with an audio output, which is an unamplified line-level signal feeding powered speakers, or a supported USB sound card on models that accept one — and the listening volume is set at the speaker, not on the panel. Verify the event and its WAV asset in simulation first, then close the hardware gap the terminal actually has.
The buzzer cannot play WAV files #
A beep and a WAV file take different hardware. The beep comes from a built-in buzzer driven as a tone source: on, off, one pitch. A WAV file is sampled audio that must pass a digital-to-analog converter and an output stage before anything moves a speaker cone. A buzzer-only terminal has neither stage, so the event fires, the buzzer sounds, and the voice never does — no project download and no setting changes that.
That is the reported behavior on a CMT 3072XH: the event called a preloaded library voice labeled "enable", only the beep was audible, and the terminal offered no volume control for file audio. That is expected behavior for that hardware, not a fault in the event. The beep proves the event triggers and the buzzer works; it says nothing about WAV playback.
Confirm the event and the WAV asset in simulation #
Simulation is a valid test of the project and an invalid test of the terminal's audio hardware, because the sounds come from the PC sound card. EasyBuilder Pro, Weintek's project tool, attaches sound output to events and to objects such as buttons (documented for version 6.04), and the asset you hear in simulation is the asset the terminal will request.
- Open the event, or the object's sound settings, and confirm it requests the selected WAV — the library voice labeled "enable" in the reported case — rather than the default beep.
- Confirm the PC itself plays ordinary audio through the output you will listen on, and that the output is not muted.
- Run the project in simulation, trigger that event deliberately, and listen for the selected voice. A beep is not a pass.
- If a controller value drives the event, prove the trigger with the simulator connected to the live controller — the procedure is in testing HMI simulation against a live PLC.
Audible WAV playback in simulation proves the project requests that asset, and nothing about the panel. Other panel lines follow the same discipline — on C-more operator panels, event manager sounds come from PC-made WAV files — so the file is prepared and checked at the PC either way.
What the terminal has to provide #
| Audio path | What it is | What you do |
|---|---|---|
| Built-in buzzer | Tone source inside the terminal | Beep only; the WAV never plays |
| Audio output jack | Line-level, unamplified output | Feed powered speakers; identified on the cMT3090 and cMT3151 |
| USB sound card | Audio device on the terminal's USB port | Identified across the cMT and xE ranges; confirm the accessory for the exact model |
For this terminal family, buy the cMT3090 or cMT3151 if you want the jack, and treat every other cMT or xE model as a USB-sound-card install. The jack is disappearing from newer models, so confirm the exact model and its accessory list in the current datasheet before ordering. The reported CMT 3072XH has no jack, so its route is the USB sound card. If the station is due for replacement anyway, a PC-based operator station plays the same files through its own audio stack; what to check when choosing one is covered in selecting a panel PC with audio output for an HMI.
Power and wiring for the speakers #
The audio output is unamplified line level, so it expects an amplifier. Powered PC-style speakers are that amplifier; a passive speaker wired to the jack is inaudible or nearly so. Power comes from outside the terminal: the USB 2.0 specification allows a port to supply up to 500 mA at 5 V, which is 5 V × 0.5 A = 2.5 W, while published selection guidance for HMI terminal speakers points at 10–20 W units. A 10 W speaker needs four times the port's entire budget (10 W ÷ 2.5 W = 4), so that class of speaker runs from its own supply.
- Connect the terminal's audio output, or the sound card's output, to the speaker system's input.
- Power the speakers from their own supply and set the volume knob to a low, audible level.
- Trigger the same event that passed the simulation test and confirm the voice at the speaker.
- If the speaker clicks but stays silent, the amplifier or its power is the next check — see why HMI alarm speakers click but audible alarms stay silent.
A USB connector on a speaker proves nothing by itself: some speakers draw only power from USB and take the signal on a separate cable, others contain a complete USB audio device. Match what the speaker actually does to the path the terminal supports before buying it.
Worked example: enough level at a reception counter #
Illustrative numbers, not a specification: a small powered speaker rated 85 dB SPL at 1 W and 1 m, driven at its 10 W rating, listener 4 m away.
- Power gain: 10 × log10(10 W ÷ 1 W) = 10 dB, so 85 + 10 = 95 dB SPL at 1 m.
- Distance loss: 20 × log10(4 m ÷ 1 m) = 12 dB, so 95 − 12 = 83 dB SPL at the counter.
Typical office background sits near 60 dB, so 83 dB is clearly audible as a voice prompt. What moves the result: halving the power costs 3 dB, doubling the distance costs 6 dB, and a wall or corner behind the speaker adds a few decibels. The 10 W speaker in this example cannot run on the 2.5 W USB budget, so it takes its own supply.
The decision for each case #
- Terminal with the audio jack (cMT3090, cMT3151): connect powered speakers to the line output and set the level at the speaker. Done.
- cMT or xE terminal without the jack, including the CMT 3072XH: install the supported USB sound card into powered speakers, after confirming the accessory in that model's documentation.
- Terminal with neither a jack nor supported USB audio: the WAV cannot play on it. Keep the beep for annunciation, or move the station to an industrial panel PC whose audio output plays the files.
- Every case: the volume lives at the speaker or amplifier, because these terminals expose no file-audio volume control.
If the WAV is part of an alarm, keep the beep or a visual indication as well until the speaker path is proven at commissioning — a silent audio path must never be the only annunciation.
Questions asked
Would converting the WAV to another format make it play on the buzzer?
No. The barrier is the output hardware, not the file. A buzzer reproduces tones, not sampled audio, so no sampling rate, bit depth, or format conversion changes the outcome. The file format only matters once a real audio path exists — the jack or the supported USB sound card — and there you use the formats the engineering tool documents.
What does an unamplified audio output mean for the wiring?
The jack carries a line-level signal meant to drive an amplifier input, not a speaker. Connect it to powered speakers with their own supply, and route the audio cable away from drive and motor cabling, which can induce hum on a signal-level line. A passive speaker on that jack is inaudible or nearly so.
Will any USB speaker work on a cMT or xE terminal?
Only a speaker the terminal's documentation supports. Many USB speakers use the connector for power alone and take audio on a separate cable; others contain a complete USB audio device. Check the power too: a USB 2.0 port supplies at most 500 mA at 5 V, or 2.5 W, while terminal-audio guidance points at 10 to 20 W speakers, which need their own supply.
How do I control the volume of the event sounds?
At the speaker or amplifier. Buzzer-only terminals expose no volume control for file audio — the reported CMT 3072XH had none — so set the level with the speaker's knob during commissioning, and check any mute switch on the speaker whenever the sound later disappears.
How do I prove the installed panel plays the right message?
After wiring, trigger the same event that passed the simulation test and listen for the same voice, not a beep, at the normal listening distance with the area's ambient noise present. Repeat with the enclosure door closed and any nearby drives running; that is the condition the operator will actually hear.