No. An HMI microphone jack carries sound to a remote viewer only if the panel's own documentation names a capture function and the remote access carries it. On panels where the input ships with no object to use it, connect nothing and meet the listening requirement with a dedicated IP intercom or alarm dialer commissioned separately from the control project.
You want to hear the machine while you look at it from off site. The panel has a microphone jack and remote access already works, so it feels like the pieces are there. They are not. A mic jack is a connector; remote access is a channel for screens and controls. Unless the manual for your exact panel model and project software version names a microphone-capture function that remote access carries, the jack does nothing, and no edit to the project will change that. The listening requirement is a small audio project of its own: a dedicated intercom or dialer with its own microphone, its own path, and its own listener at the far end. This article gives the checks that settle the question, a worked example with the numbers, and the install and test steps.
Why the jack does not reach the remote viewer
For sound to travel from a machine-area microphone to a remote viewer, three things must exist and all three must be documented for the model: the panel captures the audio, the project software has a function or object that uses it, and the remote-access feature carries that audio to the viewer. Miss one and the chain is silent.
The jack is only the first link. On some HMI panels the microphone input ships unused: the project software has no object that can take audio from it, so a connected microphone feeds nothing and the input behaves as disabled whatever you plug into it. That is a fact of the panel's software, not a setting you can flip.
Screen size is not a capability spec either. A 6-inch panel and its larger siblings in the same family share a bezel and a mounting cutout, not a feature list. Capture and remote-audio support are model-and-version facts, and the only source is that model's manual and release notes.
What to check before you wire anything
- Write down the exact model and the project software version, from the panel's label and the project file's about screen.
- Search the model's user manual and release notes for microphone, audio capture, and audio in, and read the remote-access chapter for what it carries.
- Ask the supplier one question: on this model and this software version, does the remote viewer hear microphone audio? A yes needs a manual chapter to point at.
- If the documentation names the function, follow that documented configuration and stop here.
- If it does not, treat the jack as unused hardware and build the listening path as a separate device. The rest of this article is that job.
What you need for the listening path
Decide the requirement in writing first: live listening, spoken status messages, or both, and where each listener sits. The answer picks the device.
| Device | Listener | Microphone | Transport | Function the manual must name |
|---|---|---|---|---|
| IP intercom | Stations on the plant network | Its own, at the machine | Plant LAN, carrying 8-bit PCM or 16-bit .wav audio to groups | Live microphone audio to stations |
| Alarm dialer | Off site, by phone, cell, or internet calling | Its own mic input | Phone line, cell service, or internet calling | Call-out messages, about 20 s stored, and call-in listening |
The capability must be written in the device's documentation, not implied by a connector. One published intercom design note specifies 8-bit PCM or 16-bit .wav files, or live microphone audio, sent to intercom groups with per-device volume. Typical dialer listings specify a mic input, call-in listening, and about 20 seconds of stored voice.
Sound in the other direction, from the panel out to the room, is a different job: adding an audio output to an HMI or shop-floor display covers that hardware.
If what you need off site is the line's status more than its sound, a screen does that job. Our shop-floor displays play prepared status pages offline from a memory card, or run your own Android app, independent of the HMI project.
A listening device observes. It does not replace machine alarms, safety functions, or the instrumentation a process requires, and those stay on their designed paths.
Example: a 6-inch panel on a packaging line, call-in from off site
Inputs, each with its source:
- Panel: a 6-inch HMI with a mic jack. Its manual and release notes name no microphone-capture function for this model and software version.
- Requirement: a supervisor off site calls in, listens live, and hears three recorded status messages.
- HMI audio contribution: 0 channels, because the project software has no object that consumes the mic input.
- Candidate device: an alarm dialer with typical listing figures, a mic input, call-in listening, about 20 s of stored voice.
Rule in words: every audio function the requirement names must be served by a device whose documentation names it too. Channels needed = channels the HMI provides + channels a separate device must add. A jack on any device counts for nothing until its manual names the function.
Arithmetic:
- Functions required: 2, spoken status messages and live call-in listening.
- Channels the HMI provides: 0.
- Channels to add: 2 − 0 = 2. One dialer whose documentation names both functions covers them, so devices to buy: 1.
- Message capacity: time each message with a stopwatch; assume 6 s each here. Three messages need 3 × 6 s = 18 s. The recorder holds 20 s, so the set fits with 2 s spare. A fourth message needs 24 s, over the 20 s capacity, and would not fit.
Result: one dialer at the line meets both functions over the phone. The panel's mic jack stays unconnected and the control project stays untouched.
Decision: if your recorded message set runs longer than the recorder's 20 s, specify a model with longer storage or cut messages until it fits. If the listeners sit at stations on the plant network, install the IP intercom instead, since its documentation covers live mic audio to groups. If a candidate device's documentation names neither function, it is the wrong device, whatever its jack count.
Install the audio path without touching the control project
- Write the requirement: live listening, spoken messages, or both, and each listener's location. This picks the device type.
- Choose by listener location: an IP intercom for stations on the plant network, a dialer for phone, cell, or internet calling.
- Before purchase, confirm the exact model's documentation names the mic input, the transport, and the listen-in function you need.
- Mount the microphone where the sound is, at the machine or in the area, following the device manual's placement guidance.
- Power and connect the device from its own manual: its network settings and its accounts, under the site's approved remote-access controls. For network devices, a VPN router for remote PLC and HMI access keeps the intercom off the open internet.
- Record the spoken messages and time the set. Keep the total under the recorder's capacity, about 20 s on typical units.
- Leave the HMI project alone. No screen edit creates an audio function on a panel whose documentation does not name one.
If the remote connection itself misbehaves during commissioning, HMI remote access port forwarding, tested step by step is the order to work through.
How to check it worked
Test each function at its real endpoint, and record what passed.
- Local: speak at the microphone and hear it at a nearby endpoint, a station speaker or the dialer's own playback.
- Remote: from the actual listening location, call in or connect, and judge the audio intelligible, not merely present.
- Spoken messages: trigger one on purpose and listen to it as its own test, because call-out and call-in are separate paths on most units.
- HMI: open the remote view and confirm screens, values, and controls behave as they did before the install. The audio work must have altered nothing in the control project.
- Record: date, panel model and software version, audio device model, and which device serves each function, so the next engineer inherits a fact sheet instead of a guess.
Recommendation: unless the manual for your exact panel model and software version names a microphone function that remote access carries, treat the jack as unused and buy the listening path as its own device: an IP intercom when the listeners sit on the plant network, an alarm dialer with mic input and call-in when they call from off site. Commission it from its own manual, keep the HMI project untouched, and keep machine alarms on their designed paths.
Questions
Can an adapter or a better microphone wake up an unused HMI mic input?
No. If the project software has no object that consumes microphone audio, the input is inactive at the software level, and changing microphone type, impedance, or power does not create the capture function. That function lives in the panel's firmware and project software, not in the connector. The only path to using the jack is a documented feature for your exact model and software version, found in that model's manual or release notes.
How do I choose between an IP intercom and an alarm dialer for machine listening?
Choose by where the listener sits. An IP intercom carries live microphone audio across the plant network to station speakers or handsets; published designs specify 8-bit PCM or 16-bit .wav audio sent to intercom groups, so it suits listeners on site. A dialer serves listeners off site: it plays a recorded message when it calls out and lets you call in to listen, over a phone line, cell service, or internet calling, with about 20 seconds of typical message storage.
Does a listening microphone cover any safety requirement?
No. The audio path is for observation. Machine alarms, safety functions, and required process instrumentation stay on their designed control and notification paths. A dialer's call-out is a notification convenience and must never be the only path for an alarm that requires a response, because nothing ensures anyone answers. Specify and commission the listening device alongside the people responsible for the machine's safety design.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.