Selection guide
Selecting a Panel PC With Audio Output for an HMI
Short answer
Select the panel PC by its audio path and its supplied Windows edition, not by screen size. The output must be line level into an amplified speaker or amplifier, Windows must use that output as its default playback device, and the deployed HMI project must run on the edition that actually arrives with the unit. A display under 10 inches is a preference, not a selection criterion.
On this page
Buy the panel PC on its audio path and its supplied Windows edition, and look at screen size last. An HMI that plays a sound every hour needs three things from the computer: a line-level audio output feeding an amplified speaker, Windows using that output as its default playback device, and an operating system that actually runs your deployed project. None of those three comes from a small display. The sub-10-inch screen you would prefer is a preference, not a selection criterion — the standard industrial diagonals run 10, 12, 15 and 19 inches and up, so a genuinely small install means separating the computer from the display rather than shrinking the panel PC. Below are the acceptance table to hold a supplier to, the line-level arithmetic that settles the speaker question, and the decision for each configuration.
Selection order and the acceptance table #
Two criteria in this table are order-killers: a unit with no audio output, or with a Windows edition your runtime does not support, cannot be rescued by a better screen. Make the supplier answer every row in writing, then prove the two software rows on the actual image before you commit the order. Mechanical fit stands apart from all of it — a perfect electrical match is useless if the cut-out drawing disagrees with the door.
| Requirement | Acceptance criterion | Evidence to demand |
|---|---|---|
| Runtime | The deployed project runs on the Windows edition and build that arrives on the unit | Written OS edition and version, plus a trial install of your project on that image |
| Controller link | The Ethernet port and driver stack support your PLC protocol | Interface specification plus a live communication test |
| Audible notification | A line-level output drives your amplified speaker through the default Windows playback device | Audio specification plus a playback test with the enclosure closed |
| Display size | The diagonal suits your screen design; under 10 in is a preference only | Diagonal and bezel dimensions |
| Installed fit | Cut-out, rear depth and connector clearance suit the mounting panel | Mounting drawing with cut-out dimensions |
Where the configurator offers a 24 V DC supply variant, prefer it: the unit then hangs straight off cabinet power instead of adding another adapter to maintain.
What the audio output actually is #
An audio output is a signal interface, not a loudspeaker. On an industrial panel PC it is nearly always a 3.5 mm (0.14 in) three-conductor TRS minijack on the connector panel, carrying line level. Line level is a voltage, not power: consumer equipment is nominally -10 dBV, about 0.316 V RMS, while professional interfaces run +4 dBu, about 1.23 V RMS, on balanced 6.35 mm connections. Panel PC onboard audio is the consumer kind. The jack expects a high-impedance input — an amplifier or a powered speaker — and cannot drive a passive 4 Ω or 8 Ω cone on its own. Headphone-style outputs behave the same way: they feed an amplified speaker's aux input happily, but they remain signal sources.
The question to put to the supplier is therefore precise: does the unit have a line-level output, what connector carries it, and what does the specification sheet call it? A listing that shows no audio interface at all fails the table outright.
Worked example: can the line-out drive a speaker directly? #
Take illustrative but typical values. The jack delivers consumer line level:
V_out = 1 V × 10^(-10/20) = 0.316 V RMS
You want a modest 1 W out of a passive 8 Ω speaker. The voltage that takes:
V_spk = √(P × R) = √(1 W × 8 Ω) = 2.83 V RMS
That is 2.83 V / 0.316 V ≈ 9 times what the jack supplies. Wire it directly anyway and the speaker receives:
P = V² / R = (0.316 V)² / 8 Ω ≈ 0.0125 W ≈ 12.5 mW
A hundredth of a watt — inaudible under any plant noise. The decision falls out of the arithmetic: an amplifier sits between the line-out and the speaker, which in practice means an amplified (powered) speaker or an amplifier module. If the amplified speaker's aux input is specified at 0.3 V RMS sensitivity, the drive ratio is 0.316 V / 0.3 V ≈ 1.05, about +0.5 dB of headroom — matched, with the Windows volume control left for trim.
Speaker choice and cabinet wiring #
Three arrangements work, in order of preference:
- External amplified speaker fed from the line-out. The usual plant answer. Mount it where the operator stands, not where the panel sits; feed it with a short shielded run and keep that run away from drive output and motor power cables.
- Integrated panel speaker. Only where the datasheet offers one, and always tested with the door closed — an enclosure can swallow a chime that sounds crisp on the bench.
- Amplifier plus passive speaker or horn. For a cabinet that already runs speaker cable to a remote sounder; the worked example above sets the gain you need.
If no amplified speaker suits the cabinet and you would rather build the driver stage, a single-supply op-amp preamp and speaker-driver stage is the standard circuit — op-amp audio amplifier design guide walks through both stages.
When the sound arrives as clicks or not at all, suspect the speaker feed before the software: the wiring faults behind why HMI alarm speakers click but audible alarms stay silent apply equally to a panel PC's external speaker.
One safety note: an hourly chime is informational. Any audible warning whose silence could contribute to injury belongs to a dedicated, risk-assessed safety function wired independently of the panel PC, never to a Windows volume slider.
Match the supplied Windows edition to the runtime #
'Windows' on a listing is not an operating system. Depending on the configurator, a panel PC arrives with no OS, with Windows 10 or 11 Pro, or with an IoT Enterprise image, and your runtime and its components are licensed and tested against editions, not against the word Windows. Before shortlisting hardware, record three things from the machine your project already runs on: the Windows edition and build, the runtime your project installs against (the .NET version or the equivalent library), and any service or driver the project starts. Order the panel PC in the edition that matches, then run the deployment package on that exact image. Expected result: the project opens with no missing-component errors and its screens display.
For the RAM, disk and edition arithmetic behind that match, the HMI panel PC RAM, SSD and Windows selection guide works the numbers.
Watch the class boundary here too: a proprietary HMI terminal is a different equipment class, and a project built for Windows does not install on terminal firmware unless the terminal vendor explicitly lists your runtime as supported.
Deploy the sound, the playback device and the schedule #
The audio configuration is part of the deployment, not a bench setting. Set the line-out as the default playback device for the production account, fix the volume and mute state, and confirm both survive a reboot. Deploy the sound with the application: if the project reads a file, that file belongs in a path the production account can read; if the sound is embedded in the project, test the built application rather than playback from the development environment. Then run it under the normal operating account with development tools closed. Expected result: the application finds the sound and plays it through the line-out.
Settle the trigger semantics before commissioning. An elapsed timer measures application runtime and restarts with the application; a clock-based trigger compares system time and needs a 'this hour already sounded' flag, or every evaluation inside the matching minute fires the sound again. Decide too what happens when the computer starts mid-hour after a power cut — skip, play once, or a documented rule — and write the choice into the project instead of leaving it as behavior.
Ethernet is a separate acceptance item. Link lights prove copper; matching protocol, controller address and updating tags prove communication. Commission it read-only: confirm displayed values against known controller values instead of jogging the machine to demonstrate a connection.
The decision #
Four configurations cover the question:
- Your runtime is fine at 10 inches and up — the normal case for a single-screen notification display. Select a machine-side unit that passes the acceptance table and order it as one of the industrial panel PCs built for flush panel mounting; the audio path and the supplied Windows edition decide, exactly as the table sets out.
- A display under 10 inches is a hard requirement. Split the functions: a compact industrial mini PC in the cabinet carries the audio jack, Ethernet and the runtime, and drives a small separate touchscreen monitor on the door. You get the small screen you wanted without asking a panel PC to be smaller than the market builds it.
- The unit is already bought and has no audio output. Add a USB audio adapter, set it as the default playback device, and treat it as a permanent service item — one more connector, driver and update to maintain.
- An existing proprietary terminal must gain the sound. It will not run your Windows project, so the terminal gets replaced, not upgraded. Pull the existing project first — reading an old HMI program before panel replacement is the procedure — then apply the acceptance table to the replacement.
Whichever case is yours, the acceptance test is the same: the deployed project runs on the image that arrives, and the hourly sound plays through the intended speaker with the cabinet closed and the plant running.
Questions asked
Can I add audio to a panel PC that arrived without an audio output?
Yes. A USB audio adapter enumerates as a standard Windows playback device, and an hourly chime needs nothing more from it. Check three things first: the adapter's cable must pass through the cabinet with the same sealing as every other gland, bus power from the port must cover the adapter, and the driver must install on your Windows image. After each Windows update, confirm the adapter is still the default playback device.
Can the line-level output drive a horn or industrial sounder directly?
No. A line-out supplies around a third of a volt of signal, about 12.5 mW into an 8 ohm load, while a horn needs watts. Feed an amplified horn speaker from the line-out, or skip analog audio entirely and switch a discrete sounder module from a digital output on the controller. For a simple hourly tone, the digital-output route is often the more robust choice.
Will a touchscreen HMI terminal play the sounds from a Windows-built HMI project?
Only if the terminal vendor lists your runtime as supported. Terminals run their own firmware, not Windows, so a project built for a PC will not install regardless of whether the terminal has a beeper. If the vendor's supported-software list does not name your runtime, the terminal is out; select a Windows panel PC or the mini PC plus separate monitor arrangement instead.
Why does sound come out of the monitor instead of the audio jack?
The display connection is the usual culprit. HDMI and DisplayPort carry audio alongside video, and Windows tends to make the monitor's audio device the default when it appears. Open the sound settings, set the line-out jack back as the default playback device, and lock that choice into the deployment image so it survives driver updates and reboots.