A touch panel that beeps on every press is following a project attribute, not a hardware fault. Set Enable Beeper to Off in Setup > Project Attributes in the programming software, then download the project to the panel; the editor change alone does nothing until the panel receives it.
A touchscreen panel that beeps on every press is not broken and usually needs no hardware. The beep is a project attribute. You turn it off in the programming software: open the project, set Enable Beeper to Off in Setup > Project Attributes, then download the project to the panel. The download is the step most often skipped. A setting changed only in the editor changes nothing on the floor until the panel receives the new project. This page gives the documented path, the checks that tell you the download landed, the other places a beep can hide, and what to do when the setting was already off.
Symptoms and what each points to
Match what the panel does to the source before you change anything:
- A short beep on every touch press. The project's beeper attribute is on. This is the case the fix below covers.
- The beeping continues after the attribute was set to Off. The edited project never reached the panel, or the download went to a different panel or an older file. The example below walks that decision.
- Beeps only when an alarm fires. The alarm function drives the sound, enabled separately from the touch beeper.
- A beep on a touchscreen connected to a Windows PC. The touch driver's own beep, set in the driver's defaults utility, with no HMI project involved.
- One beep at power-up. The panel's startup self-test. If that single beep is the whole complaint, the project is the wrong place to look; the panel manual is where to check whether it can be changed.
Turn the beeper off in the project attributes
The documented path comes from programming software version 3.1A.
- Open the panel's project in the programming software.
- Open the Setup menu and select Project Attributes.
- Find the Enable Beeper radio button on the right side of the window and set it to Off.
- Save the project.
- Download the project to the panel.
- Touch the panel in the places that beeped before. Silence after a completed download is the confirmation.
If your Project Attributes window has no Enable Beeper radio button, your editor version differs from 3.1A. Find the sound option in the manual that matches your installed version before touching anything else in the project.
One check before silencing any panel sound: confirm the beeps are touch feedback. If the same beeper also marks alarms, leave the alarm sound on; the touch attribute and the alarm function are separate settings.
Prove the download reached the panel
The editor change takes effect on the panel only through a download. Run three checks, in order:
- The download completes with a success message. On a healthy link a small project finishes in a minute or two. A download that crawls past that is a link problem, not a project problem; a project download that takes minutes covers that fault on its own.
- The download went to the panel you are standing at, with the project you edited. On a line with several panels it is easy to send the fix to the neighbor.
- The touch is silent in the places that beeped before. Silence is the result.
Optional hardware check: some panel families have a system setup screen in the runtime with a Beep Test button, and the manual states the test sounds the internal beeper whether the beeper is enabled or disabled. So if Beep Test sounds and the touches are silent after your download, the sound hardware works and the fix landed.
Where the same switch hides in other editors
Not every editor calls it Enable Beeper.
In EBPro, the editor behind another common panel family, open the project, go to the Home tab, open System Parameter Settings and go to its System tab, then select the option to disable sound. The rule afterwards is the same: save and download, or the panel never hears about the change.
Beeps from a touchscreen on a Windows PC belong to the touch driver. The driver ships a defaults utility and an ini file so an administrator can set or disable the touch beep across a whole fleet from one deployment. No HMI project involved.
Some panels let the PLC program switch the internal beeper. If the project shows no beeper option anywhere, check the PLC logic before the panel settings; one walk-through of PLC-side beeper control shows what that looks like.
Example: the setting was off and the panel still beeped
A packaging station runs a touchscreen HMI on programming software version 3.1A. It beeps on every touch. On the first day an engineer opens the project, sets Enable Beeper to Off, saves, and closes the editor. The beeping stays.
The setting is off in the project, so the question is where the change stopped. The download log answers it. Say the log shows:
- Last completed download to this panel: 08:30, the day before.
- The edit saved: 16:05 that same day, after that download.
The edit never reached the panel, so the decision is a download, not another setting change. Download the project at 16:12 the next day. It completes at 16:13:30, which is 90 seconds for a project of nine screens, inside the usual minute-or-two window. Touch the same spots: silent.
One number would have changed the decision. If the log had shown a completed download at 16:10, after the edit, the project file would have been the next suspect: an older copy with the beeper still on, pulled from a shared folder and sent to the panel. And if the download were confirmed correct and the beeping stayed, the remaining places for the sound are the alarm function, the PLC logic, then a touch driver on a host PC, in that order.
Keep the edited project as the master copy
The panel runs whatever project it received last. Put the edited file where your downloads come from and retire older copies that still have the beeper on, or the next download brings the beep back. A restart changes nothing about a healthy panel's file.
The same editor-then-download rule governs other panel-level settings: the backlight saver timeout on a PLC panel is changed in the project and applied by download too.
If a panel starts losing its project on power cycles, that is a storage fault of its own and the beeper setting is the least of it; a panel that loses its project after a power cycle covers the checks.
Recommendation: Set Enable Beeper to Off in Setup > Project Attributes, download the project to the panel, and keep the edited file as the only master copy. If the beeper still sounds after a download that completed after the edit, check the alarm function, then the PLC logic, then a touch driver on the host PC, in that order.
Questions
Does Enable Beeper off also mute alarm sounds?
No. The project attribute governs the beeper that confirms a touch press. Alarm sounds are enabled separately in the alarm function, and on multi-panel systems one panel can act as a server that enables alarms for several connected clients, so a client panel can beep even with its own alarm option off. Check the alarm configuration and any server panel before blaming the download.
What if there is no Enable Beeper option in Project Attributes?
The documented radio button belongs to programming software version 3.1A. A different version can rename the option or move it into a system parameter settings window, so search the manual for your installed version instead of guessing. Note the version number and the menu names you do see; the matching manual chapter will name the sound option in your editor.
Will a power cycle turn the beeper back on?
No. The setting travels inside the project file, and a healthy panel keeps the file it last received through a restart. The beeping returns only when someone downloads an older project copy that still has the beeper option on. That is why the edited file should be the only master copy, and why a beep that returns weeks later points to a download, not to the panel.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.