IMDTouchKnowledge BaseShop main store

Troubleshooting

WinCC flexible IO field not editable on the panel

HMI and touchscreens Published 6 min read

Short answer

An IO field that displays its tag but ignores touches is disabled, not over-protected: the enabled checkbox for operator interaction is cleared even though the secured box is unchecked. Tick enabled on the object first, then clear or set the secured box to match your access policy, compile and download. Clearing security alone never makes the field interactive.

On this page
  1. Read the runtime symptoms before you touch any settings
  2. Enabled and secured are two independent settings
  3. Five fields, one editable: the arithmetic of the fault
  4. Make the fields editable and put the fix on the panel
  5. When entry opens but the value will not stay
  6. Questions asked

A WinCC flexible IO field that shows its process value but ignores every touch is not over-protected — it is disabled. The enabled checkbox that permits operator interaction on that object is cleared, and unchecking the secured box cannot change that: enable the object first, then set or clear the secured box and its authorization level to match the access policy you want. The checks below sort a per-object configuration fault from a panel-wide input failure, give the runtime decision for every enabled-and-secured combination, and end with the steps that put the fix on the panel.

Read the runtime symptoms before you touch any settings #

One screen carries five IO fields configured as inputs. After the download, exactly one of them accepts entry, and buttons, counters and symbolic IO fields on other screens behave normally. That pattern tells you where the fault lives before you open a single property dialog:

  • Touch the one working field on the same screen. Its entry interface opens, so touch handling, screen layering and the panel's input path are all proven. This is a per-object settings fault.
  • Touch an affected field and nothing opens at all: the object is not enabled, or an invisible object is stacked over it. Work through the enabled check below.
  • Entry opens but the value snaps back or never reaches the controller: the enabled state is fine and the write path is not. Skip to the last section.
  • Objects on every screen ignore touches, or touches land in the wrong place: that is the opposite case, a touch layer or calibration fault, and no object property will fix it.

One project trap sits behind the checkbox: a screen can drive an object's enabled state dynamically from a tag or script at runtime. A ticked box in the project does not guarantee an enabled field in runtime, so if the static settings look right and the field is still dead, find the value controlling that state and read it while runtime is running. If enabled is genuinely ticked, no dynamic condition holds the field off and the entry interface still never opens, drag the visible field aside on a project copy — a second, invisible object covering it is receiving the touch instead.

Enabled and secured are two independent settings #

An IO field carries two separate conditions for operator entry. Enabled decides whether the object reacts to a touch at all. Secured decides who may complete the operation once it reacts: the field demands a login holding the selected authorization level before it accepts the entry. Unrestricted access removes the permission check; it never switches the object on. That is why clearing secured on a dead field changes nothing, and why the two checkboxes must be read as a pair, not as alternatives.

Enabled Secured Runtime behavior Decision
cleared unchecked Field follows its tag but no entry interface ever opens Tick enabled, recompile, download, retest — this is the fault behind the dead fields
cleared checked Same dead field, and no login prompt ever appears because the object never reacts Fix enabled first, then decide whether this field should stay protected
ticked checked Entry opens only for a user holding the configured level Intended configuration for protected fields; test with and without that login
ticked unchecked Entry opens for any user The configuration for unrestricted entry

Do not repair a disabled field by handing every user a higher authorization level. That buries the interaction fault under a wider permission model and leaves the fields that genuinely need protection weaker. Keep secured set on any field that writes a setpoint a wrong entry could make dangerous: enabled is the input switch, secured is the guard on it.

Five fields, one editable: the arithmetic of the fault #

The reported case makes the matrix concrete. Five IO fields on one screen are configured as inputs and downloaded to a MultiPanel 277. At runtime one accepts entry and four sit dead, and the fields that do work elsewhere on the machine are secured to the administrator level, while the four dead fields are unsecured — they are meant to be editable by anyone.

Field Enabled Secured Runtime result
1 to 4 cleared unchecked Follows the tag value, ignores every touch
5 ticked as configured Entry interface opens; the control case

Work the arithmetic. Five fields are configured for input, so five should accept entry, and 5 - 1 = 4 fields are dead. Those four are already unsecured, so further security editing contributes 0 editable fields: 1 + 0 = 1 working field survives every round of unchecking. Tick enabled on the four, leave secured unchecked, recompile and download, and 4 + 1 = 5 fields accept entry, which closes the fault. The working field never needed touching, and the administrator-secured fields elsewhere stay exactly as they are.

Make the fields editable and put the fix on the panel #

  1. Save a recoverable project copy, and note the screen name and each affected field's tag assignment before you edit anything.
  2. Open the first dead IO field's property settings and tick enabled. This is the step that decides the fault; do it before you touch security.
  3. Set security to the intent: clear secured for unrestricted entry, or leave it checked and select the authorization level the field requires. With enabled still cleared, neither choice has any effect — that ordering is the trap behind the original symptom.
  4. Confirm the field's mode is Input or Input/Output. An Output field follows its tag and can never accept entry, however its enabled and secured boxes are set.
  5. Compile the project, clear any errors it reports and download to the panel. The panel runs the compiled file, so the edit does nothing until it is transferred.
  6. On the panel, touch each repaired field, enter a test value and confirm it lands in the controller. Then verify the access policy still holds: entry with the intended user, and no entry without a login on any field you left secured.

When entry opens but the value will not stay #

A field that opens entry and then reverts, or accepts a value the controller never sees, has cleared the enabled hurdle and failed on the write path. Work that path in order: check the field's value limits against the test value, then the tag's data type and address, then any controller logic that writes the same tag every scan and overwrites the entry before you can see it. If the field later shows a number the operator never typed, the article on why an HMI edit box shows a value that was never set follows that tag from entry to controller and back.

Keep the two failure paths apart while you work. No entry interface at all is an enabled-state or overlapping-object problem, and no amount of security reconfiguration fixes it. Entry that opens but does not stick is a limits, tag or controller problem, and no checkbox on the object fixes that.

Questions asked

Does clearing the secured checkbox remove the authorization level too?

No. The level selection only has effect while the field is secured, and clearing secured removes the login requirement entirely. If you secure the field again later, select the level explicitly rather than trusting whatever default the dialog offers, because a level you did not choose will not match the access policy you assume.

How do I hide what the operator types into an IO field?

Enable Hidden input for the field, in the Security > Operation group of its property settings in WinCC flexible. Runtime then masks the characters as they are typed, which suits password and code entry. Hidden input changes only how the entry is displayed: the field still needs its enabled checkbox ticked and an input or input/output mode before it accepts anything at all.

Do I have to compile and download again after changing one checkbox?

Yes. The panel runs the compiled runtime file, not the project open on the engineering PC, so a property edit stays invisible until the project is compiled and transferred again. Save the project, compile it, clear any errors and download, then prove the fix with a real touch on the panel rather than assuming the setting took.

What is the difference between input, output and input/output mode?

An input field only accepts operator entry. An output field only displays the tag value. An input/output field does both: it follows the tag and opens an entry interface when touched. An output field and a disabled input field look identical at runtime, with the value updating and touches doing nothing, which is why the mode selection belongs in the same check as the enabled box.

If buttons and other objects accept touches, can the touchscreen itself still be at fault?

Not for the dead fields. Objects that accept input on the same panel prove the touch layer, its controller and the calibration are working, so the fault sits in the individual object's configuration. Suspect the touch hardware only in the mirror case: every object on every screen ignores input, or touches register in the wrong place across the whole display. Then recalibrate and test with the panel vendor's documented procedure before editing the project.

Keep reading

  • Troubleshooting

    Why WinCC Flexible Edits Do Not Show in Runtime

    Saved WinCC flexible edits stay invisible in Runtime until the runtime output is regenerated with Rebuild all and transferred to the target; the panel runs a build, not your project file. After redeploying, confirm the edit on the panel itself, and test every VBScript command on that target class because Windows CE panels support fewer commands than PC Runtime.

    HMI and touchscreens

  • Troubleshooting

    When HMI user management works in simulation but not on the panel

    The simulator reads user management from the project; the panel keeps its own local user data store that keep-current-values downloads never refresh. Download to the panel once with Reset to start values for runtime values, confirm the role's runtime rights for that HMI, then test one login and one permitted function.

    HMI and touchscreens

  • Troubleshooting

    HMI numeric input does not change FX2N timer preset

    A numeric input works only when it writes the exact D register the timer or counter instruction reads as its preset. Open the device monitor, enter a known value, and watch that register: if it does not move, fix the link, driver or address; if it moves but the delay stays fixed, the rung still reads a K constant or another register — change the preset operand to the register, mind the timer's time base, then test two settings before production.

    HMI and touchscreens