HSMS Details

There are several parameters that can be set to influence the behavior of the AdeptGEM programs that implement the HSMS communication layer. The HSMS parameters are defined in the SEMI specification and are presented here. In some cases, the setting of these parameters will be obvious, based on the physical equipment (the IP addresses, for example, are determined by the settings of the host and the equipment). Other parameters will need to be determined based on the behavior of the equipment in the host environment. The T7 and T8 parameters, for example, do not have an intrinsic "correct" value, but depend on the acceptable behavior of the entire system.

The IP address for the host can be specified either explicitly (for example, "172.16.200.1") or as the corresponding node name that has been defined in the V+ configuration data (i.e., using the CONFIG_C program).

All the HSMS parameters are stored as equipment constants in the GEM Variables database (see HSMS Communication Parameters and Predefined SVs, ECs, and DVVALs), which can be accessed with the menu selection:

Edit -> GEM Variables

HSMS Communication Parameters shows the range, default, and resolution for each parameter (the values for T3 through T8 are in seconds)
Table 4-2. HSMS Communication Parameters
Parameter
ECID
Default
Min
Max
Resolution
T3
9108
45
1
120
1
T5
9110
10
1
240
1
T6
9111
5
1
240
1
T7
9112
10
1
240
1
T8
9113
5
1
120
1
Session ID
9151
4660
0
32767
1
Connect Mode
Auto detected
PASSIVE, ACTIVE



Local Entity IP Address
Defined in V+ configuration data
None



Remote Entity IP Address
9300
None



TCP Port Number
9300
None



 

Table 4-3. HSMS Parameter Description
Parameter
Description
T3 Reply Timeout
Specifies maximum time an entity expecting a reply message will wait for that reply.
T5 Connect Separation Timeout
Specifies the time that must elapse between successive attempts to connect to a given remote entity.
T6 Control Transaction Timeout
Specifies the time that a control transaction may remain open before it is considered a communications failure.
T7 NOT SELECTED Timeout
Time that a TCP/IP connection can remain in NOT SELECTED state (i.e., no HSMS activity) before it is considered a communications failure.
T8 Network Intercharacter Timeout
Maximum time between successive bytes of a single HSMS message that may lapse before it is considered a communications failure.
Session ID
Identifies the equipment as an entity in the communications. (This is analogous to the SECS-I Device ID.)
Connect Mode
Specifies the logic this local entity will use during HSMS connection establishment.
Local Entity IP Address
Determines the address on which the local entity will listen for incoming connection requests. (Required for any entity operating in PASSIVE mode.)
Remote Entity IP Address
Determines the address of the remote entity to which the local entity will attempt to connect. (Required for any entity operating in ACTIVE mode.)
TCP Port Number
Determines the TCP port of the remote entity to which the local entity will attempt to connect. (Required for any entity operating in ACTIVE mode.)


Other HSMS Requirements

  1. The Option Used for Refusing Incoming Connection Requests if the implementation uses the Passive Mode for TCP/IP Connection Establishment:

Refuse to listen for or accept the connect request. No action is taken in the local entity; the remote entity's connect procedure will eventually time out.

  1. The maximum message size that can be received:

The size of a message received depends on the size of buffers used. The buffer size is configured using Equipment Constant 9154 in the GEM Variables database.

  1. The Maximum Expected Size of Messages Sent:

The maximum expected size of messages sent will be implementation-dependent, but not greater than 64 Kb.

  1. The maximum number of supported concurrent open transactions:

The maximum number of supported concurrent open transactions is one.

  1. The number of device IDs supported and their specific values:

The number of device IDs supported is one. This ID is configured by equipment constant 9151.

  1. Whether or not the implementation supports the normal or the restricted procedure for terminating communications:

The implementation supports the restricted procedure for terminating communications.

  1. The setting of the host vs. equipment parameter:

In this product, the Adept side is always equipment.