Resolving HEIDENHAIN iTNC Virtual Keypad Display Issues

The iTNC demo opens across the monitor, but the virtual keypad either disappears behind it or appears only after you minimize the control. Start here: change the iTNC display from 1024x768 window FULL SCREEN to 1024x768 window. The keypad and control need separate desktop space; buying a larger monitor or adjusting its front-panel buttons does not create that space by itself.

Read the symptoms before changing settings

Separate a hidden keypad from a keypad that never starts. If the keypad becomes visible as soon as you minimize iTNC, it is already running. The full-screen control window is covering it.

Run the visibility test first: minimize iTNC and look for the keypad. Reinstalling the demo, changing monitor geometry, or repeatedly toggling startup options wastes time when that test proves the keypad is already active.

Understand why full screen hides the keypad

The demo control uses a fixed 1024x768 application area. In 1024x768 window FULL SCREEN, that fixed interface is expanded or presented across the available screen. The control occupies the foreground, leaving no usable desktop beside it for the separate virtual-keypad window.

In 1024x768 window, the control stays in a normal window. If the Windows desktop has more pixels than the control requires, the remaining area can hold the keypad. This is why monitor size alone is the wrong sizing criterion. A 19-inch panel can still be configured with too little desktop resolution, while a physically smaller display can expose enough workspace when its pixel dimensions and scaling permit it.

The tradeoff is visible. Windowed mode makes the iTNC control smaller than a full-screen presentation. That is not the fault; it is the space allocation that allows both windows to remain visible.

Window order also matters. Startup can launch the keypad first and the iTNC window second. The later foreground window can cover the keypad even though Launch keypad at startup worked. Treat startup and visibility as separate checks.

Configure the desktop and iTNC window

1. Close the iTNC demo before changing its presentation mode. Restarting from a known state makes the Control Panel and window behavior easier to identify.

2. Open the Windows display settings and read the current desktop resolution. A reported working trial for a 19-inch monitor used 1280x1024, which leaves pixels outside a 1024x768 control window. Use that value only if the display supports it properly.

3. Keep the monitor at its native resolution when possible. The native setting maps the desktop cleanly to the panel’s physical pixel grid. A non-native setting can make text and lines look soft even when the windows fit.

4. Open the iTNC Control Panel and select 1024x768 window. Remove the FULL SCREEN selection.

5. Launch or restore the iTNC control. Move the 1024x768 window to leave a clear strip of desktop for the keypad.

6. Do not use the monitor’s front-panel controls to solve this problem. Those controls handle display presentation such as image position; Windows controls the desktop pixel resolution, and iTNC controls its own window mode.

A 22-inch setup was described with the ambiguous strings 400x1050 and !400X1050. Do not enter either string as a target resolution. Read the actual selectable resolution from Windows and the monitor’s native specification, then confirm that both the 1024x768 control and keypad fit.

Launch and place the virtual keypad

1. Find the separate iTNC Control Panel icon. The minimized iTNC530 application button only restores or minimizes the control; it is not the configuration panel.

2. If the Control Panel is not visible, close iTNC and start it again. Inspect both the taskbar and the area near the clock because the icon’s location can differ with the desktop layout.

3. Open the iTNC Control Panel, select Keypad or Keyboard, and launch the virtual keypad.

4. Open Settings, select Launch keypad at startup, and accept the setting with OK.

5. Select vertical or horizontal presentation when those choices are active. Pick the orientation that fits the unused desktop area.

6. Restore the iTNC control and arrange both windows. If the keypad disappears, minimize iTNC again. A keypad revealed by that action is running behind the control, so return to the window-mode and placement checks.

Keyboard mapping remains a valid operating method while diagnosing the layout. It does not test whether the virtual keypad process is active, so use the minimize-and-reveal test instead.

Verify the correction in operating order

1. Start the demo from a closed state.

2. Confirm that the keypad launches automatically if Launch keypad at startup is selected.

3. Confirm that the iTNC control opens as a bordered 1024x768 window rather than taking over the entire display.

4. Place the control and keypad so neither covers the other.

5. Minimize and restore iTNC several times. The keypad must remain accessible after each restore.

6. Close and restart the demo. A correction is persistent only when window mode, keypad startup, and placement still work after restart.

If the keypad starts but cannot coexist with the control, compare the Windows desktop resolution with the space occupied by both windows. If Windows offers no suitable native-resolution layout, the limiting factor is available desktop area rather than the keypad command.

Avoid the fixes that repeatedly waste time

• Do not judge capacity by diagonal size. A 17-inch or 19-inch label says nothing about the active pixel workspace. Read the Windows resolution.

• Do not leave full screen enabled. A higher desktop resolution cannot provide useful side space while the iTNC window continues to cover the desktop.

• Do not confuse two controls. The minimized application and the iTNC Control Panel perform different jobs.

• Do not keep toggling startup. If minimizing iTNC reveals the keypad, startup already succeeded.

• Do not correct desktop resolution with monitor buttons. Change it in Windows. Use the monitor controls only for the presentation functions exposed by that display.

• Do not force a blurred resolution merely to enlarge the interface. Native resolution normally produces the clearest panel image. On a TFT display, Windows ClearType can improve text readability, but it does not create additional workspace or correct full-screen window coverage.

• Do not treat a smaller iTNC window as a new defect. The smaller presentation is the expected consequence of keeping a fixed 1024x768 control inside a larger desktop.

Decide when the display has reached its limit

Keep the native desktop resolution when it supplies enough room. If text is too small at that setting, adjust readable-text features such as ClearType before lowering the entire display resolution. Then retest window placement because any resolution change alters the available desktop area.

Escalate when the separate Control Panel remains absent after a clean restart, keyboard choices stay unavailable in windowed mode, or the keypad process never appears even with iTNC minimized. Record the selected Windows resolution, monitor native resolution, iTNC mode, the exact gray controls, and the startup sequence for official HEIDENHAIN support.

FAQ