GOT2000 VNC: Guaranteed Time Is Idle, Not Forced Exit

GOT2000 VNC stays connected after the panel's Guaranteed Time reaches 60 seconds. You expected a forced logout, but the viewer remains open. Start here: that setting measures inactivity after the last operation from the VNC client. It is not a fixed connection-duration timer.

Identify the actual disconnect requirement

Separate an idle-session requirement from a forced-session requirement before changing the project. They need different mechanisms.

Write the requirement in one sentence. Use “disconnect after 60 seconds without a VNC-client operation” for idle control. Use “disconnect 60 seconds after connection regardless of activity” for a fixed session limit. Do not treat those statements as interchangeable.

Measure inactivity from the last remote operation

Take the first reading at the VNC client. Record the time of its last remote operation, then stop operating it completely. Do not start timing from the initial connection unless no operation occurs after login.

1. Connect the VNC viewer to the GOT.
2. Perform one deliberate remote operation and record its completion time.
3. Remove your hands from the viewer controls. Do not click, type, or operate the remote screen.
4. Watch for the server to close the client connection.
5. Record the elapsed time from the last client operation, not from application launch.

If the connection closes after the configured idle interval, the function works. Continued remote use was resetting the interval in the earlier test. That is not the fault.

If the connection does not close, repeat the test with a clean viewer session and no intentional input. A scripted viewer, remote-access layer, or automated input utility can create operations without an operator click. Isolate those components before editing the GOT project.

Confirm the running GOT has the setting

Check the project in GT Designer3. The identified configuration path is GOT Setup, then Advanced Setting. Locate the VNC-related Guaranteed Time value and confirm that it is set to 60 seconds.

Next, prove that the edited project is the project running in the GOT. A value displayed in the engineering file has no effect until the corresponding configuration reaches the panel.

1. Open the exact GT Designer3 project assigned to the target GOT.
2. Read the VNC Guaranteed Time under GOT Setup and Advanced Setting.
3. Apply the changed project through the normal GOT transfer workflow.
4. Complete any activation or restart action requested by the engineering software or panel.
5. Return to the project or GOT configuration display and verify that the intended value is present.

If the panel still behaves like the old configuration, investigate project selection, transfer completion, and configuration activation. Reinstalling the VNC viewer wastes time at this stage because the disconnect timer belongs to the GOT side.

Decide whether idle timeout solves the job

Use the result of the controlled test as the branch point.

• Disconnect occurs after idle time: Keep Guaranteed Time. It releases the inactive VNC session so another user can connect.
• Disconnect occurs only after the last remote operation: The GOT is following inactivity semantics. Continued operation legitimately keeps the session active.
• Disconnect never occurs during a clean idle test: Recheck the deployed project and the exact setting before considering a product fault.
• Fixed-duration logout is required: Stop tuning Guaranteed Time. Search the installed GT Designer3 help for a distinct maximum-session or disconnect function, or place the fixed-duration policy in the client or remote-access layer.
• An HMI button or event must disconnect clients: Verify that the specific GOT configuration exposes a VNC disconnect action. Do not substitute an idle setting for an explicit command.

The mechanism matters. An idle timer protects access when a remote operator walks away. A fixed lifetime ends an active session. An event-driven disconnect reacts to panel logic or an operator command. One timer cannot provide all three behaviors.

Apply the resolving configuration

Use this procedure when the requirement is to free a session after 60 seconds without remote operation.

1. In GT Designer3, open the target GOT project.
2. Navigate to GOT Setup and Advanced Setting.
3. Set the VNC Guaranteed Time to 60 seconds.
4. Transfer the updated configuration to the intended GOT.
5. Activate the transferred configuration using the normal project workflow.
6. Reconnect the VNC viewer, perform one remote operation, and leave the client untouched.
7. Measure from that last operation until the GOT disconnects the client.

Do not repeatedly change the value while the project-deployment question remains open. First prove which project is running. Do not test by continuously moving through screens and then expect the connection to close 60 seconds after login; active use defeats an inactivity timer by design.

Verify release and reconnection

Run two tests. The first proves idle disconnection. The second proves that useful activity does not behave like inactivity.

1. For the idle test, connect, make one operation, stop input, and measure the interval until disconnection.
2. After disconnection, attempt a new VNC connection. Successful access confirms that the previous client no longer occupies the session.
3. For the active test, reconnect and make deliberate remote operations within the configured interval.
4. Confirm that the connection remains available while those operations continue.
5. Stop all operations and confirm that disconnection now occurs after the idle interval.

A pass requires both behaviors: active operation refreshes the session, and a truly idle client is removed. If the GOT drops an actively operated session, investigate network loss separately; that is not the expected result of an inactivity timer.

FAQ