Establish Communications
| SEMI E30 Sections: |
3.2, 4.1 |
| Database Usage: |
 |
|
Documentation Requirements: |
None. |
Communications are established in accordance with the GEM Communications State model. The GEM Control Panel shown in GEM Control Panel, Establish Communication Options has buttons and indicators that implement the Communications State Model. To display the GEM Control Panel:
Selecting Enabled starts the scenario that attempts to establish communication with the host. If the attempt is successful, the new communicating state is shown at the bottom of the Communication group.
Selecting Disabled halts communication with the host.
Before communication can be enabled successfully, the communication channel must be properly installed and configured, and the host must be ready to establish communication. All the configuration options for the serial or Ethernet channel, as well as the GEM parameters, are set in the GEM Variables database.
The equipment constants that define the communication configuration and GEM parameters are included in Predefined Collection Events. They are also summarized in Tables 4-1 through 4-3.
Equipment constant 9300 specifies the serial channel ID for SECS-I or the Ethernet node and port ID for HSMS. The possible values for a serial channel are: LOCAL.SERIAL:1, LOCAL.SERIAL:2, LOCAL.SERIAL:3 (AWC CPU only), SERIAL:1, SERIAL:2, and SERIAL:3. See the AdeptNET User's Guide for details on proper Ethernet node names and port numbers.
GEM Requirements
These GEM requirements are specified in Section 4.1.4 of SEMI E30:
1. The communication state model is fully implemented as described above.
2. The EstablishCommunicationsTimeout equipment constant is stored as ECID 9100 in the GEM Variables database.
AdeptGEM Debug Windows
The AdeptGEM system provides a pair of debug windows that trace the message traffic and success state of message transmission. The windows are displayed whenever communications is enabled and equipment constant 9105 is set to enable the windows. (This equipment constant is checked each time communications are enabled.)
When it is enabled by equipment constant 9105, the "GEM Service" window displays status messages from the main AdeptGEM task, which processes SECS-II messages.
Similarly, the "SECS-I Debug" or "HSMS-SS Debug" window (one or the other can be displayed, depending on the low-level interface that is in use) displays messages from the AdeptGEM low-level communications task. Each message in this window contains a two- or three-character code that identifies the event that is being reported. These codes correspond to the suffixes of the global variables uc.stat.*.
In addition to the AdeptGEM debug windows, equipment constant 9105 can be set to request that other debug messages be output to the V+ monitor, and that those messages and the SECS-II messages be logged in a memory-resident log of recent messages. For details, see the description of the global variable gm.debug.