HMI volume control arrows not working: check firmware first

Why do the volume arrows do nothing while mute still works?

Because mute and level adjustment are separate functions. In the documented defect, firmware 2.2+SP1 on 12 and 15 inch panels leaves the volume control dead. The rest of the object, mute included, keeps working, and version 2.23 corrects it.

Mute answering tells you the touch layer and the runtime behind that screen respond to a press. The release note scopes the bug to the volume control alone. A working mute fits a defect limited to the level function, and it clears touch recalibration and object replacement from the front of the check order. The reported case tried both styles of volume object, and both were equally dead. That fits a panel-side defect and counts against a configuration mistake in one object. Read the version next.

Which symptoms point at firmware instead of the amplifier?

Dead arrows with a live mute, on a 12 or 15 inch panel reporting a 2.2-series version, point at the documented firmware defect first. The amplifier becomes the suspect only when the panel already runs version 2.23 or later and the arrows still do nothing.

• Arrows dead, mute alive, both object styles identical, panel reporting a 2.2-series version: the documented volume-control defect. Update first.
• Arrows and mute both dead: touch input or the object is the suspect. Recalibrate the touch layer, as in the article on a touch button that only responds to half, and check the object's level tag.
• Arrows respond on screen, amplifier level never moves: the panel side works. Check the amplifier's input selection and the wiring between panel and amplifier.
• Arrows stopped after a project download: compare the object against the previous project backup. Confirm the level tag still points at the address the controller expects.

The amplifier enters the check order once the panel runs a corrected version and the arrows still do nothing.

How do I read the exact firmware version the panel reports?

Read the version from the panel's own information screen and write down the full string, service pack included. The defect entry names 2.2+SP1 while the case panel reported 2.2, and only the full string tells you which one you have.

The version lives in the panel's setup or system-information menu. The route to it, and the difference between the panel firmware and the programming-software version on your laptop, is covered in how to read an HMI panel firmware version for field maintenance. Read the revision again before any project transfer; the article on checking the firmware revision before a transfer gives the reason. For the bug list, open the firmware history page for your panel family on the maker's support site, and read the readme that ships with each release. Some histories push the detail into that readme. Makers release new firmware versions primarily for bug fixes, which is why the history page is the first document to open on this fault.

What does the version check look like as a worked example?

A 15 inch touch panel drives an external amplifier. The volume object's arrows do nothing, the center mute works, both object styles fail identically, and the panel reports version 2.2. That is the set of facts that resolves against a defect fixed in version 2.23.

1. Record the symptom set: arrows dead, mute live, 2 object styles tried, panel size 15 in, reported version 2.2.
2. Open the maker's firmware history for that family. The entry dated 10/31/2008, released as version 2.23, lists one relevant fix: the volume control does not work in 2.2+SP1 on 12 and 15 inch panels.
3. Match the facts against the entry. Panel size 15 in falls inside the 12 and 15 inch list. The reported version 2.2 sits in the 2.2 series the entry names. The symptom, a dead volume control with the screen otherwise working, matches the entry's description. Match: 3 of 3.
4. Decide: the amplifier and its wiring stay untouched. The repair is the update to version 2.23 or later, with the project backed up first.
5. Re-test after the update: five presses on the up arrow step the amplifier's level up five times, five presses on the down arrow step it back down, mute still toggles, and adjustment still works after unmuting. If the arrows stay dead on the corrected version, the firmware question is closed and diagnosis moves to the amplifier input with the recorded facts in hand.

What do you back up before a firmware update?

Back up the runtime project and any recipe or alarm files before the update. Operator-panel vendors document backing up this data before an operating-system update or a reset to factory settings, and the same order applies to any touch panel.

Write three things down first: the panel model and size, the exact version string shown on the panel, and the symptom note, arrows dead with mute responding. Then save the software. Where the panel family supports read-back, read the project back from the panel before editing anything, and back up the recipe files before any download. The vendor's update procedure says to back up the project data before an update or a reset to factory settings, so follow that order for your panel family.

How do you apply the fix and test the arrows again?

Apply the vendor's documented update for the installed panel family. Keep the power stable through the write, then test the arrows by pressing them repeatedly with the amplifier connected and watching the level change. Test mute afterwards as a separate action.

1. Confirm the target from the history: version 2.23 or later in the documented family.
2. Load the update from a storage medium. One panel family documents the path as the panel's Control Panel, then Service & Commissioning, then Update OS, then select the storage medium. Other families keep the same function under a service or update menu in their control panel; use the instructions printed for your panel and its software.
3. Run the update from stable power and let it finish. A panel that loses power mid-write can come back without a working image, so this is the one step that gets time.
4. Read the version again after the restart and check it against the target.
5. Test the arrows with the amplifier connected: five presses up and five presses down, watching the level step at the amplifier each time. Then press mute, unmute, and confirm the arrows still adjust.
6. If the panel stops communicating after the update, work through the checks for an HMI panel that will not communicate after a firmware update before you flash anything again.

Recommendation: When the volume arrows are dead, mute still answers, and a 12 or 15 inch panel reports a 2.2-series version, treat the documented volume-control defect as the first cause. Back up the project, update to the release that names the fix, version 2.23 or later in that family, and start on the amplifier or wiring only if the arrows are still dead on the corrected version.

Questions