When using slow connection speeds (generally 64 Kbps or slower), you may want to enable bitmap caching and perhaps change the color settings for your connection. If you are using remote connections on a regular basis, you may need to experiment to find the combination of settings that optimizes the performance of your connection. You can save your connection settings in a file. To do this, use the Connection Settings option on the General tab of the Remote Desktop Connection dialog. (Click the Options button on the initial connection dialog to see the full set of dialog tabs and connection choices.) Multiple configuration files can be saved to customize settings for different connection speeds, different servers, and so on. (The Windows user name and password can also be stored.) Shortcuts for the configuration files can be placed on the Windows desktop to further speed up the connection process.
Bitmap caching can be enabled or disabled using a check box on the Experience tab of the Remote Desktop Connection dialog. Connection speed can also be selected on the Experience tab. Display color settings can be selected on the Display tab. Some considerations for making connection choices are:
DeltaV Operate supports color depth settings of 32 bit. If you change the screen resolution on the remote client system, it may be necessary to reset the color depth setting to 32 bit.
In general, the number of datalinks on a picture is not as great a factor in its startup time as the complexity of the bitmap (in terms of shape and color changes within the picture). A simple graphic with 200 datalinks will come up on a "slow" remote connection almost as quickly as on a direct LAN-connected machine; a picture with 700 datalinks will take longer to start up, but should operate normally. Alarm Summaries, which are not graphics-intensive, should open in almost the same amount of time as a direct connection.
For slow connection speeds, it is suggested that you do not open complex, color-intensive graphics. Such graphics may take several minutes to open. If network or protocol errors occur, DeltaV Operate may hang or appear to be hung. The connected client will not be able to exit DeltaV Operate or log off. The user will be able to disconnect using the X on the remote session title bar. The session will then have to be logged off by someone with administrator privileges (using Task Manager or DeltaV Diagnostics) or it may be automatically logged off through use of the "timeout" option. This option can be set by the administrator to automatically log off disconnected sessions after a set period of time.