Configuring Button Hotkeys in WinCC Advanced Runtime (TIA Portal)

WinCC Advanced (TIA Portal) provides built-in hotkey support for HMI buttons, but the set of supported keys is strictly limited compared to WinCC Professional or a custom .NET application. Engineers who want to jog an axis with the arrow keys, trigger a valve with the spacebar, or assign a function key to an alarm acknowledgment must first understand the supported key matrix, then design around its constraints. This reference documents the supported hotkey set for WinCC Advanced Runtime, the step-by-step configuration path, the differences against WinCC Professional and Basic Panels, and the verified workarounds that allow arbitrary keys to drive PLC tags.

1. WinCC Product Family Overview and Hotkey Capability

Siemens offers three distinct WinCC configurations inside the TIA Portal engineering framework, and the hotkey engine differs between them. Selecting the wrong configuration is the single most common cause of "the shortcut does nothing" complaints in the field.

2. Supported Hotkey Matrix for WinCC Advanced Runtime

The WinCC Advanced Runtime hotkey engine enumerates a fixed list of 24 logical keys exposed to the button property "Hotkey". The list is published in the TIA Portal help and confirmed in the Configuring operation in Runtime (Professional) documentation family.

3. Prerequisites for Hotkey Configuration

1. Installed TIA Portal V16 or later (V18 / V19 / V20 tested for the screenshots and combobox labels shown here).
2. WinCC Advanced V16 or later license. Open Project > Properties > Protection > Licenses to confirm the WinCC Advanced ES + RT bundle is present.
3. An HMI device of class Comfort Panel (TP700/900/1200/1500/1900) or a PC running WinCC RT Advanced.
4. An HMI tag wired to a PLC tag (or an internal tag driving a script) that the button will toggle or set when pressed.
5. For two-key shortcuts on Basic Panels, the panel must be a keyboard-attached variant (KTP with external keyboard, or TP with integrated keys). See Control keys and shortcuts (Basic Panels) - Support.

4. Step-by-Step: Assigning a Hotkey to a Button

1. In the TIA Portal project tree, expand HMI_1 > Screens > Screen_1 and double-click the target screen.
2. Select the button to which you want to bind a hotkey. Right-click > Properties.
3. In the Properties inspector, open Properties > General > Hotkey.
4. Click the combobox; the available selections are F1-F12 and Shift+F1..F12. Choose the desired key.
5. Wire the Press event to a tag set, a function list, or a script that drives the axis jog. Example with an internal boolean tag "Axis_Z_Jog_Up":

   // Function list bound to the Press event
   SetTagBit("Axis_Z_Jog_Up", 1)

6. Wire the Release event of the same button to clear the bit (otherwise the axis continues to drive after key release):

   // Function list bound to the Release event
   SetTagBit("Axis_Z_Jog_Up", 0)

7. Compile the HMI (Project tree > right-click HMI_1 > Compile > Software (rebuild all)).
8. Download to the target panel or start the WinCC RT Advanced simulation.
9. Press the configured function key. The button visually depresses and the bound tag flips. If the button does not depress, see Section 8 (Troubleshooting Matrix).

5. Why Arrow Keys Fail in WinCC Advanced Runtime

The WinCC Advanced Runtime hotkey engine explicitly does not enumerate arrow keys, alphanumeric keys, or control keys other than F1-F12 in the button property combobox. This is a deliberate product boundary, not a missing feature or a bug. The reasons are:

• Focus model. The Runtime routes hotkeys to a single focused screen. Mapping every printable key to a button would collide with text-input fields, password dialogs, and the on-screen keyboard.
• Function row reservation. F1-F12 are reserved on PC keyboards for application functions and are not consumed by Windows shell shortcuts, giving a clean separation.
• Safety. Forcing a fixed, well-known set prevents accidental "lost focus" keystrokes from moving a machine.

When an engineer tries to assign an arrow key, the combobox simply does not list it, and writing SetTagBit with a low-level keyboard hook is not available from the standard scripting API of WinCC Advanced. The two viable engineering paths are (a) upgrade to WinCC Professional, or (b) bridge an external process into the Runtime using OPC tags.

6. Verified Workarounds for Arbitrary Key Capture

6.1 External process reading stdin and writing an OPC tag (WinCC Advanced RT, PC target only)

WinCC Advanced Runtime on a PC exposes a Configurable OPC DA/UA server. A user-mode helper process can poll the Windows console for keystrokes and write the detected key code into an HMI tag. The tag is then read inside the Runtime by a button or by a script.

Minimal C# helper (.NET 6, Windows console):

using System;
using Opc.Ua;

class KeyBridge {
  static void Main() {
    var client = new Opc.Ua.ClientSession(new Uri("opc.tcp://127.0.0.1:48010"));
    client.Open();
    Console.WriteLine("Bridge running. Arrow Up = axis Z up, Arrow Down = axis Z down. Esc to quit.");
    while (true) {
      var key = Console.ReadKey(true);
      if (key.Key == ConsoleKey.Escape) break;
      if (key.Key == ConsoleKey.UpArrow)        client.Write("HMI_Tags.Axis_Z_Jog_Up",   1);
      if (key.Key == ConsoleKey.DownArrow)      client.Write("HMI_Tags.Axis_Z_Jog_Down", 1);
      System.Threading.Thread.Sleep(50);
      if (key.Key == ConsoleKey.UpArrow)        client.Write("HMI_Tags.Axis_Z_Jog_Up",   0);
      if (key.Key == ConsoleKey.DownArrow)      client.Write("HMI_Tags.Axis_Z_Jog_Down", 0);
    }
  }
}

The bridge must be launched before Runtime start, and the OPC server on the Runtime must allow loopback. Add the executable to the Windows startup group or to a WinCC Advanced startup script.

6.2 Global Windows hotkey via a signed Win32 helper

If the goal is to assign any key (including Alt+J, Ctrl+Shift+F5, the media keys, or a USB footswitch that registers as HID keyboard), use the Win32 RegisterHotKey API. The helper process raises a window message, which the helper translates to an OPC write. This works in parallel with the Runtime because Windows hotkeys have a higher precedence than the Runtime's internal hotkey combobox.

// P/Invoke registration inside the helper
RegisterHotKey(hWnd, 1, MOD_ALT, VK_UP);    // Alt+Up   -> Axis Z up
RegisterHotKey(hWnd, 2, MOD_ALT, VK_DOWN);  // Alt+Down -> Axis Z down

6.3 Upgrade to WinCC Professional

If the project budget allows a runtime upgrade, WinCC Professional exposes the full alphanumeric and arrow-key set in the same Properties > General > Hotkey combobox that WinCC Advanced uses. The configuration procedure is identical to Section 4. No external bridge, no DLL, no OPC traffic. The trade-off is the additional RT Professional license and the change in screen object model: Professional uses C-/VB-scripting and WinCC OLE controls, while Advanced uses the lighter TIA HMI tag/script model.

7. Basic Panels: Two-Key Shortcut Behavior

Basic Panels and Comfort Panels with attached USB keyboards use a two-key shortcut model. From the Control keys and shortcuts (Basic Panels) documentation: "With shortcuts, you keep the first key pressed. Then you press the second key." The configured first key is shown in the help text of the button; if the operator releases the first key before the second, the shortcut is cancelled.

This is the closest the Basic Panel line gets to arrow-key jog, and it is still bounded to F1-F12. For arrow-key jog on a panel-mounted HMI, the external-helper approach (Section 6) is required.

8. Troubleshooting Matrix

9. Verification Checklist After Configuration

1. Compile the HMI with "rebuild all" and resolve every warning in the Inspector output.
2. Download to the target. Confirm in the Runtime diagnosis view that the configured hotkey is listed under Settings > Hotkeys.
3. Start the Runtime in online mode. From the HMI focus, press the configured key. The button should visually depress and the bound tag should change in the HMI tag table.
4. For jog-style operation, release the key and confirm the Release event clears the tag within 100 ms.
5. For a PC Runtime, repeat the test with the engineering window focused, the Runtime window focused, and a third-party application focused. Only the Runtime-focused case should react to the Advanced hotkey; if it reacts in all cases, the helper from Section 6.2 has registered a global hotkey and is working as expected.
6. Document the final mapping in the HMI plan: Function key F5 = Axis Z jog up, F6 = Axis Z jog down, Shift+F5 = fast jog, F8 = acknowledge alarm. Provide this as part of the operator manual.

10. Field-Proven Caveats

• On a TP1500 Comfort Panel with an attached USB keyboard, F1 is reserved by the Runtime Help system. Choose F2-F12 for application hotkeys to avoid stealing F1.
• On a PC Runtime, the Windows screen saver and the accessibility sticky-keys feature can swallow the configured hotkey. Disable both for operator PCs.
• When the HMI is in change mode (online editing from TIA Portal), hotkeys are not delivered to the application; this is by design.
• If the project will be commissioned on different panel sizes, the same hotkey list is honored across the entire RT Advanced line, so the same PLC logic and HMI script can be reused without rework.
• For 21 CFR Part 11 / audit trail projects, an external helper that writes through OPC may not be accepted; in that case upgrade to WinCC Professional so the hotkey binding is fully inside the audit-friendly Runtime.

11. Quick Reference Mapping

FAQ