To enable local Vision client fallback, do the following steps:
- Go to Config > Gateway Settings in the local Gateway.
- Scroll down to the Local Vision Client Fallback section and select the Enable Local Fallback.
- Select a Fallback Project from the dropdown list.
Note, that the selected project must be published in the local Gateway, and it must have at least one main window.
- Optionally, you can change the Seconds to Failover setting to a value other than 60 seconds.
This setting controls the number of seconds to wait before fallback automatically starts. During comm failure, you can also click a button to load the local fallback project immediately.
When local Vision client fallback is enabled, the Client attempts to open port 6501 on the local machine. If the port can be opened successfully, the Client reads fallback settings from the local Gateway and shows a Fallback Project button on the bottom of the Gateway Connection Lost window. You can click this button at any time to load the fallback project, or simply wait for the fallback project to automatically load. You may want to set the local Client to automatically log in to avoid typing in a username and password when the Client loads. This can be set in the Login section of the project's properties.
Testing Local Fallback
Testing local Vision client fallback is highly recommended before you start to depend on it in a production setting. The easiest way to test fallback is to simply unplug the network cable to the Client machine, or disable the network card on the machine. If the Fallback Project button is not visible on the Gateway Connection Lost window, check your local Gateway console and verify that the message Started Fallback Socket on port 6501 is present in the console. Any other error message related to the Fallback Socket Controller indicates that some other problem has occurred (most likely the port cannot be reserved) and local fallback is not available to Clients.
Automatically Transferring Back
Local Vision Client Fallback will not automatically transfer back to the main Gateway when it is running again, as simplicity was key in this system. You can, however, provide your own solution to automatically switch back. One example is to add a retarget script to your Timer Client Event Scripts to silently try to reconnect.