You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
The HMI subsystem of TSENTRY is designed to provide as much common functionality as possible to the user while maximizing flexibility for a given system. Not only does TSENTRY provide a common set of useful management and diagnostic screens such as ProbeX and TrendX, it also provides a set of tools to allow the user to develop his own HMI screens and easily connect them to the host TSENTRY system.
Within TSENTRY HMI screens are divided into groups called HMI Applications. Each HMI Application is governed by a set of rules defined in the configuration file for that application. These rules specify application options such as which users are allowed to access which screens, which screen should be displayed by default, which languages are supported within the screens, and so on.
All HMI Applications in TSENTRY are viewed using the TSENTRY Screen Explorer, or Texplore, which acts as a container application for displaying and navigating between HMI screens. Texplore uses the various services to exchange information with the TSENTRY host in order to provide a secure yet highly customizable front end to any control system.
Texplore
Overview
The TSENTRY Screen Explorer, or Texplore, is the application used to display HMI screens to a user. Texplore is simply an application for browsing the TSENTRY HMI subsystem, much like Internet Explorer is an application for browsing the Internet. Texplore provides much of the common framework for an HMI such as connecting to a TSENTRY host, reading the HMI configuration file, providing a login screen, and managing the navigation between screens within the HMI application, but by itself does not define any specific HMI screens.
Texplore relies on several processes running on the TSENTRY controller to provide it with information as it operates as the HMI client browser. These are:
The NtRtInfo service, which exposes static information from the TSENTRY controller to client objects in a request/reply architecture.
The Tsecurity service, which provides authentication and authorization services to client objects.
The GsmOpcSvr process, which exposes the values of individual variables in global memory on the TSENTRY controller.
The TrendSrv process, which exposes sampled or trended values of variables in global memory on the TSENTRY controller.