KTP1200 Basic Slider Workaround TIA Portal HMI Configuration

KTP1200 Basic Slider Workaround: TIA Portal HMI Configuration Guide

SIMATIC KTP1200 Basic panels configured with TIA Portal V13 or later do not expose a native slider object in the WinCC Basic toolbox. The slider control ships only with Comfort Panels (and higher) running under WinCC Comfort, WinCC Advanced, or WinCC Professional. Operators on the factory floor still expect a draggable or stepping widget for speed setpoints, valve positions, and analog trim values, so this article documents the engineered workaround patterns that production sites use to deliver slider-equivalent behavior on the Basic Panel line.

The recommendations below cover the KTP1200 Basic PN (6AV2123-2MB03-0AX0) and KTP1200 Basic DP (6AV2123-2MB03-0BX0) families. The same workaround logic applies to KTP700 Basic (6AV2123-2GA03-0AX0) and KTP900 Basic (6AV2123-2GB03-0AX0) because all four share the same WinCC Basic runtime object set.

1. KTP1200 Basic Object Set Compared with Comfort Panels

The Basic Panel runtime is a stripped-down subset of the Comfort Panel runtime. Engineers who specify Basic Panels must accept the smaller object catalog and build custom widgets from the available primitives.

Source: SIMATIC HMI Panels Basic Panels Comfort Panels Operating Instructions (entry ID 109746413) and the SIMATIC HMI Panel product manual (entry ID 109746400).

2. Why the Slider Object Is Missing on Basic Panels

The WinCC Basic engineering framework packages the objects that ship with the Basic Panel runtime image. Siemens deliberately omits the slider object from the Basic runtime to reduce image size, panel cost, and licensing complexity. Slider support requires:

• A vector graphics renderer with smooth touch-drag interpolation. Basic Panel runtimes predate the optimized renderer introduced with Comfort Panel image V13 SP1.
• Multitouch gesture handling. KTP1200 Basic panels ship with a resistive single-touch overlay; Comfort Panels use projected capacitive multi-touch glass.
• A larger event queue for continuous tag updates during drag. Basic panels throttle events more aggressively to keep PROFINET IO traffic low.

Engineers who require a true draggable widget must therefore upgrade to a Comfort Panel (TP700 Comfort, TP900 Comfort, TP1200 Comfort, TP1500 Comfort, TP1900 Comfort, TP2200 Comfort) or build a composite widget from the objects listed in section 1.

3. Affected Versions, Part Numbers, and Firmware

Reference: SIMATIC HMI Basic Panels Operating Instructions (109746413) lists the runtime objects by panel family and is updated with each TIA Portal release.

4. Workaround Architecture

The objective is to give the operator a slider-equivalent experience using only objects available in WinCC Basic. Three engineered patterns cover virtually every use case:

1. IO field + two buttons (recommended default). An IO field shows the current value and accepts numeric entry; two buttons (+ and -) increment or decrement the value by a configurable step.
2. Bar + IO field + two buttons. Adds a horizontal or vertical bar that fills or empties proportionally to the value, giving visual feedback of position. This is the closest visual analog to a slider.
3. Gauge + IO field + two buttons. Round dial style is preferred when the operator needs a learned mapping of value to angle (for example, valve percent open).

All three methods rely on the same HMI tag. Pick the pattern whose visual semantics match the operator's mental model of the controlled process.

5. Prerequisites

• TIA Portal V13 SP1 or later with WinCC Basic installed.
• SIMATIC KTP1200 Basic PN or DP panel added to the project.
• PLC tag of type INT (16-bit) or REAL (32-bit floating point). Integer is preferred for fixed-step setpoints; REAL is required when the value has fractional resolution.
• HMI tag configured with the same data type as the PLC tag and a defined acquisition cycle (typically 100 ms or 1 s).
• Configured PROFINET (or PROFIBUS) connection between the panel and the S7-1200 / S7-1500 / S7-300 / S7-400 / ET 200SP CPU.

6. Method 1 - IO Field with Up/Down Buttons

6.1 Tag Configuration

Create a tag in the HMI that points to the PLC speed setpoint:

6.2 Screen Objects

1. Open the desired screen in TIA Portal under the KTP1200 Basic project.
2. Drag an I/O field from the toolbox onto the screen.
3. Configure the I/O field properties:
   • Mode: Input/Output
   • Tag: HMI_SetpointSpeed
   • Format: 9999 (decimal, no decimal point)
   • Limit Low / High: 0 / 1500 (mirrors tag limits)
4. Drag two buttons onto the screen. Label them + and -.
5. On the + button, configure the Press event:
   Add HMI_SetpointSpeed 50
6. On the - button, configure the Press event:
   Sub HMI_SetpointSpeed 50
7. For long-press stepping, additionally wire the Hold event with the same instruction and a shorter repeat (default repeat already triggers at 1 Hz on Basic Panels).

6.3 Behavior Notes

• Integer step of 50 rpm is a sensible default. For finer control, drop to 10 rpm or wire a second pair of buttons for fine stepping.
• The IO field clamps the value to the configured limits, even if the user types a value outside the range.
• Operator can also type a precise value directly into the IO field using the on-screen numeric keypad.

7. Method 2 - Bar Graph + IO Field + Buttons (Closest Slider Look)

This method delivers the visual continuity of a slider by combining a directional bar with stepping buttons.

1. Insert a Bar object and align it horizontally with the IO field from Method 1.
2. Set bar properties:
   • Tag: HMI_SetpointSpeed
   • Direction: Right (or Up if vertical)
   • Range Low / High: 0 / 1500
   • Show limits: enabled
   • Marker style: Fill
3. Place the IO field on top of (or beside) the bar so the numeric value floats above the fill region.
4. Wire the same + and - buttons as in Method 1.

The bar fills proportionally to the tag value while the buttons provide the slider's stepping semantics. Although the bar is a read-only display object, the operator perceives the widget as a slider because both the position and the increment/decrement gestures match the expected interaction.

Figure 1 - Engineered slider equivalent: bar (top), IO field with current value, and + / - step buttons.

8. Method 3 - Gauge + IO Field + Buttons

Use a Gauge when the controlled value has a familiar round-dial mapping (process pressure, level, valve position). Configure as follows:

• Gauge tag: HMI_SetpointSpeed
• Range Low / High: 0 / 1500
• Scale: 5 major ticks, 5 minor ticks (display only)
• Position: Anchor to the lower-left or lower-center of the screen
• Place the IO field and the two + / - buttons in the same screen area

Operationally identical to Method 2; only the visualization differs.

9. HMI Tag Configuration and Acquisition Cycle

10. PLC Integration Example (S7-1200 / S7-1500)

The HMI tag writes back to the PLC tag, where a function block can apply scaling, rate limiting, and safety clamps before passing the value to the drive.

// SCL (Structured Control Language) - SIMATIC S7-1200 / S7-1500
FUNCTION_BLOCK FB_SliderSetpoint
VAR
    RawSetpoint      : INT;       // written by HMI tag
    ScaledSetpoint   : REAL;      // 0.0..100.0 %
    RampValue        : REAL;      // ramped output
    RampStepPerSec   : REAL := 5.0;
    LastScan         : TIME;
END_VAR

BEGIN
    // Clamp raw input
    IF RawSetpoint < 0   THEN RawSetpoint := 0;   END_IF;
    IF RawSetpoint > 1500 THEN RawSetpoint := 1500; END_IF;

    // Convert to percent
    ScaledSetpoint := INT_TO_REAL(RawSetpoint) / 1500.0 * 100.0;

    // Rate limiter (5 % per second)
    RampValue := RampValue +
                 (ScaledSetpoint - RampValue) * RampStepPerSec * 0.01;
END_FUNCTION_BLOCK

This block can be paired with the KTP1200 Basic workaround by wiring the HMI tag HMI_SetpointSpeed directly to FB_SliderSetpoint.RawSetpoint.

11. Verification Procedure

1. Compile the TIA Portal project and download to the KTP1200 Basic panel.
2. Touch the + button and confirm that the IO field value increments by the configured step (default 50).
3. Hold the + button; verify that the value continues to step at the panel's autorepeat rate (~1 Hz on Basic Panels).
4. Touch the - button; confirm decrement and clamp at the configured lower limit.
5. Type a value directly into the IO field using the numeric keypad; confirm it accepts the typed value and clamps to the upper limit when out of range.
6. Power-cycle the panel; if the tag was set persistent, confirm the last value restores.
7. Read back the PLC tag online (via TIA Portal "Monitor & Force") and confirm it mirrors the HMI tag value within one acquisition cycle.

12. Troubleshooting Matrix

13. Performance and Memory Considerations

The Basic Panel runtime loads screens from internal flash on demand. Each additional I/O field, bar, or button consumes a small amount of flash and a slot in the active screen buffer. Engineers should:

• Reuse the same HMI tag across multiple widgets (IO field + bar + gauge) instead of cloning it.
• Avoid putting more than 30 dynamic objects on a single screen; Basic Panel rendering performance degrades beyond that point, especially during tag updates.
• Disable unused animations and visibility transitions on the panel properties to reduce CPU load.

14. Alternative Platforms and Equivalent Patterns

If a true draggable slider is non-negotiable, consider migrating to:

• SIMATIC TP1200 Comfort (6AV2124-1MC01-0AX0) with WinCC Comfort V16 - includes native slider object with drag, multitouch, and animation.
• SIMATIC Unified Comfort Panels (e.g. MTP1200 Unified Comfort, 6AV2128-3MB06-0AX0) with WinCC Unified - exposes slider as a standard Style widget.
• Third-party HMI such as Allen-Bradley PanelView 5310 or Beckhoff CP3918 - both expose native slider controls but require controller-side reconfiguration.

If keeping the KTP1200 Basic is mandatory, the IO field + buttons pattern is the lowest risk, easiest to validate, and recommended by Siemens application engineers for production deployments.

15. Field-Proven Caveats

• Some operators try to drag a bar by touching and holding the fill area. The Basic Panel runtime does not translate that gesture into a tag write. Adding a short text hint ("Use + and - to adjust") reduces support calls.
• On resistive touch panels, finger drag is interpreted as a single tap-and-release. Buttons should be sized at least 10 mm x 10 mm for reliable gloved-hand operation.
• For applications requiring sub-second response (e.g., jogging a servo at variable speed), set the acquisition cycle to 100 ms and ensure the PLC connection is on PROFINET rather than PROFIBUS.
• If you change the HMI tag data type after first compilation, delete and recreate the screen objects to avoid stale pointers in the runtime.

16. Quick-Reference Configuration Checklist

• [ ] HMI tag created with correct data type (INT or REAL) and limits
• [ ] Connection to PLC tested with online tag diagnostics
• [ ] IO field placed and configured for Input/Output mode
• [ ] Two buttons placed with Add / Sub scripts
• [ ] Optional bar or gauge aligned with IO field
• [ ] Acquisition cycle set (100 ms typical)
• [ ] Tag count within 250-tag budget
• [ ] Compile, download, and verify per section 11