Resolving WinCC User Limit Issues on KTP600 and Basic Panels

David Krause10 min read
HMI / SCADASiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview of WinCC User Administration in TIA Portal

WinCC user administration within TIA Portal provides a layered security model for SIMATIC HMI panels, consisting of users, user groups, and authorizations. The model allows operators to be granted granular permissions for screen navigation, value modification, recipe handling, and audit-relevant actions. However, the user administration runtime on each HMI panel family has different published performance limits, and exceeding them produces both functional degradation (login latency, group synchronization failures) and administrative restrictions (inability to add additional users via the engineering interface).

When designing a project around a SIMATIC Basic Panel such as the KTP600, KTP1000, or TP1500 Basic, engineers frequently discover that the 50-user ceiling enforced by WinCC is incompatible with the operator headcount of a production line. This article documents the tested and released limits for Basic Panels, the behaviour when those limits are exceeded, and the recommended migration path through Comfort Panels and SIMATIC Logon.

User Administration Object Model

WinCC user administration on a runtime HMI panel contains three distinct objects, each with its own size limit:

Object Released Limit (Basic Panel) Released Limit (Comfort Panel + SIMATIC Logon) Purpose
Users 50 2,000 (project-engineering limit, depends on panel) Individual operator identities
User groups 50 50 (engineering); 128 (group container in WinCC) Role containers (operator, supervisor, programmer)
Authorizations 32 32 Permission flags referenced by object-level access protection
Sub-users per group (empirical) ~100 before project transfer errors No hard runtime cap Members within a single user group

The 50-user ceiling is enforced by the WinCC Configuration Studio and by the runtime project files. The limit is derived from performance testing and is documented as a released limit rather than a hard memory limit. Engineers who attempt to bypass the limit by editing exported project files can encounter inconsistencies between the engineering view and the panel runtime after compilation.

KTP600 and Basic Panel Limits (TIA Portal V11 to V18)

The Basic Panel generation — including KTP400, KTP600, KTP1000, and TP1500 Basic — uses the WinCC RT Advanced runtime. Within this runtime the published limits for user administration are:

  • 50 users (combined across all user groups)
  • 50 user groups
  • 32 authorizations
  • 100-character maximum length on user names and passwords
  • 8-character minimum password length with configurable complexity rules
Critical: The 50-user limit applies to the panel runtime, not to the TIA Portal project source. A project can be engineered with more users as long as only 50 are transferred to the runtime image; however, the engineering tool will issue a warning and may refuse to compile once the threshold is exceeded.

Field testing has shown that approximately 100 sub-users can be assigned to a single user group before project transfers fail with a consistency error referencing the user administration table. This is not a published specification; it is the empirical threshold observed when the runtime user database exceeds the allocated memory block on the Basic Panel filesystem.

Why 50 Users Is a Performance Limit, Not a Hard Boundary

The 50-user limit is tested and released to guarantee specific login and authentication response times on the WinCC RT Advanced runtime. The authentication flow on a Basic Panel is implemented entirely in panel-resident firmware — there is no central authentication service. When a user attempts to log in, the panel:

  1. Hashes the supplied password using the panel-resident hash algorithm (SHA-256 in firmware V14+; SHA-1 in earlier V11/V12 builds).
  2. Iterates the local user database to locate the matching identity.
  3. Evaluates the user's group membership against the requested authorization.
  4. Returns the access decision to the runtime screen handler.

With more than 50 entries, the sequential scan latency on the panel's lower-tier processor (ARM9-class in KTP600, Cortex-A8 in TP1500 Basic) begins to exceed 1 second, which violates the runtime's interactive response budget. With 100+ users, login latency can reach 3–5 seconds, and the user administration dialog can time out during group synchronization at project startup.

Migration Path: Comfort Panel and SIMATIC Logon

For installations that require 100, 500, or 1000+ operator identities, the recommended architecture is to migrate from a Basic Panel to a Comfort Panel (TP700 Comfort, TP900 Comfort, TP1200 Comfort, TP1500 Comfort, TP1900 Comfort, TP2200 Comfort) and deploy SIMATIC Logon as a central authentication service.

Comfort Panel Advantages for User Administration

  • Higher-performance processor (Cortex-A8 / A9 class) supports user databases up to 2,000 entries with sub-second login latency.
  • Supports Active Directory integration through SIMATIC Logon.
  • Supports TLS-encrypted password storage (AES-256 in firmware V15+).
  • Provides a centralized user management dialog that scales to enterprise headcount.

SIMATIC Logon Architecture

SIMATIC Logon is a Windows service that authenticates HMI panel users against a central user store. The typical topology is:

SIMATIC Logon Topology Comfort Panel TP700 / TP1200 SIMATIC Logon Service Windows Server Active Directory Domain Controller SQL User DB Optional Log Mirror EtherNet/IP

SIMATIC Logon Configuration Steps

  1. Install SIMATIC Logon on a Windows Server (2016/2019/2022) within the production network. The installer is provided on the TIA Portal installation media or downloaded from the Siemens Industry Online Support portal.
  2. Open the Comfort Panel project in TIA Portal, navigate to Runtime settings > User administration, and enable SIMATIC Logon.
  3. Configure the SIMATIC Logon server address (IPv4 address or DNS hostname) and the connection port (default 1630/TCP).
  4. Import or synchronize the Active Directory groups that should be granted HMI access.
  5. Assign Comfort Panel local authorizations (32 maximum, unchanged) to the imported AD groups.
  6. Compile and download the project to the Comfort Panel.
  7. Verify authentication by logging in with a domain credential on the panel.

Configuration Parameters and Tags

The following internal tags are exposed by the WinCC runtime for user administration monitoring and can be evaluated in HMI scripts or via the PLC interface:

Tag Type Description
@CurrentUser String (32) Logged-in user name
@CurrentUserGroup String (32) Active user group
@CurrentUserLevel Int Authorization level (0–31)
@UserLogin Bool Trigger to initiate login dialog
@UserLogout Bool Trigger to log out current user
@PasswordChange Bool Trigger to open password change dialog
@UserAdministration Bool Trigger to open user admin dialog
@GroupMembership String array Groups of current user

These tags can be polled by the PLC to enforce procedural interlocks based on operator identity. The recommended scan rate is 100 ms, aligned with the HMI tag update cycle.

Compatibility Matrix Across TIA Portal Versions

TIA Portal Version KTP/Basic User Limit Comfort + SIMATIC Logon Notes
V11 50 Not supported SIMATIC Logon introduced in V12
V12 50 Supported (Logon V1.x) First Logon release
V13 SP1 50 Supported SHA-256 password hashing
V14 50 Supported Logon V1.5 update
V15 50 Supported (Logon V1.6) AES-256 password storage
V15.1 50 Supported TLS 1.2 to Logon server
V16 50 Supported (Logon V2.0) Multi-domain support
V17 50 Supported Unified Comfort firmware
V18 50 Supported Performance improvements
V19 / V20 50 Supported Current release; licensing per TIA Portal V20 licensing documentation

Licensing Considerations

TIA Portal and WinCC require a valid License Key for engineering and runtime. The licensing model for user administration depends on the installed edition:

  • STEP 7 Basic — Basic Panel configuration only (KTP/TP Basic).
  • STEP 7 Professional — Comfort Panel and WinCC RT Advanced/Professional configuration.
  • WinCC RT Advanced — Runtime license for Comfort Panel projects.
  • SIMATIC Logon — Separate license key, installed on the Windows host running the Logon service.

Refer to the official licensing documentation for STEP 7 and WinCC under TIA Portal for the current key-to-edition mapping and to verify which License Key covers SIMATIC Logon within your maintenance contract.

Troubleshooting Matrix

Symptom Likely Cause Resolution
Cannot add user #51 in TIA Portal Released limit reached Migrate to Comfort Panel + SIMATIC Logon, or split operators across multiple panels
Project transfer fails with "User database exceeds limit" Sub-user count exceeds runtime capacity Reduce to <100 sub-users per group, or migrate
Login latency > 2 seconds on KTP600 User database near limit Reduce user count or migrate to Comfort Panel
SIMATIC Logon authentication fails Port 1630 blocked, certificate mismatch, or Logon service stopped Verify firewall, check certificate trust chain, restart SIMATIC Logon service
Password change rejected Complexity policy not met Adjust complexity rules in project or via Logon policy
User administration dialog missing on Comfort Panel User lacks "User administration" authorization Grant authorization 31 to administrator group

Verification Procedure

  1. Open the Comfort Panel runtime and confirm the login dialog appears with the SIMATIC Logon branding.
  2. Log in with three test accounts from different Active Directory groups.
  3. Verify that each user receives the correct authorization level via the @CurrentUserLevel tag, polled from the PLC.
  4. Trigger a forced logout (@UserLogout = 1) and confirm the session is terminated within 500 ms.
  5. Reboot the panel and confirm the SIMATIC Logon session is restored without manual re-authentication (within the configured timeout).
  6. Inspect the SIMATIC Logon audit log on the server to confirm each login event is recorded with timestamp, user identity, and panel IP address.

Field-Proven Caveats

  • The 50-user limit applies per panel, not per project. A single TIA Portal project compiled to two Comfort Panels can have 50 users on each panel independently.
  • If you must remain on a KTP600 due to hardware constraints (panel cutout, supply voltage, ATEX zone), an external authentication gateway — for example, an industrial PC running a custom OPC UA server with its own user store — can front-end the panel. This is an architectural workaround, not a Siemens-supported configuration.
  • SIMATIC Logon V1.x is not compatible with Comfort Panel firmware V17+. Always upgrade the Logon service and the panel firmware together.
  • If the project is opened in a newer TIA Portal version (e.g., V18) but the Comfort Panel firmware is older (e.g., V14), some Logon features will be silently dropped during compilation. Match the panel firmware and engineering tool version.

Summary Recommendation

For deployments with fewer than 50 operators on a single panel, retain the KTP600 / Basic Panel configuration and apply the released limits without workaround. For deployments approaching or exceeding 50 operators, the only supported path to 1,000+ accounts is the Comfort Panel + SIMATIC Logon architecture. Any attempt to bypass the 50-user ceiling on Basic Panels by editing project files or by exploiting firmware bugs will produce performance degradation, login failures, and audit gaps.

What is the maximum number of users on a Siemens KTP600 panel?

The released limit is 50 users combined across all user groups on a KTP600 or any other Basic Panel running WinCC RT Advanced. Field testing has shown that approximately 100 sub-users per group can be assigned before project transfer errors occur, but the engineering tool will warn once the 50-user ceiling is reached.

Can the 50-user limit on a KTP600 be increased through a configuration parameter?

No. The limit is enforced by the WinCC RT Advanced runtime and by the engineering tool's project compilation. It is not adjustable through any exposed parameter. The only supported method to scale beyond 50 users is to migrate to a Comfort Panel with SIMATIC Logon.

How many users does a Comfort Panel support with SIMATIC Logon?

Comfort Panels can support up to 2,000 user entries with sub-second authentication when SIMATIC Logon is configured. SIMATIC Logon itself scales to the size of the connected Active Directory or local user store, so the practical ceiling is enterprise-wide.

What TIA Portal version first supported SIMATIC Logon?

SIMATIC Logon was introduced with TIA Portal V12. V11, referenced in the source question, does not support SIMATIC Logon. The Basic Panel user limit of 50 has remained unchanged from V11 through V20.

Which TIA Portal versions are compatible with SIMATIC Logon V2.0?

SIMATIC Logon V2.0 requires TIA Portal V16 or later. Earlier Logon V1.x versions are compatible with TIA Portal V12 through V15.1. Mixing Logon V1.x with Comfort Panel firmware V17+ can cause authentication failures.

What port does SIMATIC Logon use for panel communication?

SIMATIC Logon listens on TCP port 1630 by default. This port must be open in any firewall between the Comfort Panel and the Logon server, and the Windows firewall rule "SIMATIC Logon" must be enabled on the server.

Can a Basic Panel authenticate against Active Directory directly?

No. Basic Panels running WinCC RT Advanced cannot authenticate directly against Active Directory. Only Comfort Panels with SIMATIC Logon installed on a Windows host can integrate with AD. This is a hard architectural boundary.

Back to blog