SECS/GEM Interface Option (Version 4.8.3 and Higher) for Fluidmove for Windows ® (FmNT Version 4.8.3 and Higher) ® (FmXP Version 5.0 and Higher) User Manual P/N 7207036, Rev.
NOTICE This is an Asymtek publication which is protected by copyright. Original copyright date 2005. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Asymtek. The information contained in this publication is subject to change without notice. Manuals on the Internet For the convenience of Asymtek customers and field service representatives, copies of this manual can be downloaded from http://www.asymtek.com/support/manuals.htm.
TABLE OF CONTENTS 1 INTRODUCTION ................................................................................................... 1-1 1.1 Overview....................................................................................................................1-1 1.2 Terminology...............................................................................................................1-2 1.3 SECS/GEM – Fluidmove Compatibility ....................................................................
2 3 MESSAGE SUMMARY ......................................................................................... 2-1 2.1 Host-to-Equipment Messages ...................................................................................2-1 2.2 Equipment-to-Host Messages ...................................................................................2-3 OPERATING CHARACTERISTICS ...................................................................... 3-1 3.1 3.2 3.3 3.4 3.5 iv Communications States.....
3.6 3.7 3.8 3.9 3.5.6 Related Variables ....................................................................................................3-26 3.5.7 Related Collection Events .......................................................................................3-26 Process Program Management...............................................................................3-27 3.6.1 Equipment Management of Process Programs ......................................................3-27 3.6.
vi 4.2.9 S1F14 - Connect Request Acknowledge .................................................................. 4-7 4.2.10 S1F15 - Request Off-Line ......................................................................................... 4-8 4.2.11 S1F16 - Off-Line Acknowledge ................................................................................. 4-8 4.2.12 S1F17 - Request On-Line ......................................................................................... 4-8 4.2.
4.2.47 S2F48 - Variable Limit Attributes Send ...................................................................4-35 4.2.48 S5F1 - Alarm Report................................................................................................4-36 4.2.49 S5F2 - Alarm Acknowledge.....................................................................................4-37 4.2.50 S5F3 - Enable/Disable Alarm Send.........................................................................4-37 4.2.
4.2.85 S7F4 - Process Program Acknowledge ..................................................................4-55 4.2.86 S7F5 - Process Program Request ..........................................................................4-56 4.2.87 S7F6 - Process Program Data ................................................................................4-56 4.2.88 S7F17 - Process Program Delete ...........................................................................4-57 4.2.
5.3 5.4 5.5 5.6 5.7 5.2.10 Host Requests Annotated Report by CEID ............................................................... 5-8 5.2.11 Host Requests Report by RPTID .............................................................................. 5-8 5.2.12 Host Requests Annotated Report by RPTID............................................................. 5-8 5.2.13 Are You There ...........................................................................................................
5.8 5.9 6 5.7.4 Illegal Data Format ..................................................................................................5-21 5.7.5 Data Too Long.........................................................................................................5-21 Clock........................................................................................................................5-22 5.8.1 Host Sets Date and Time ............................................................................
Table of Figures Figure 1-1 Terminal Message Notification (FmXP shown) ....................................................1-18 Figure 1-2 SECS/GEM Setup Dialog Box – Control Tab (FmXP shown) ..............................1-19 Figure 1-3 SECS/GEM Setup Dialog Box – Terminal Tab (FmXP shown) ............................1-20 Figure 1-4 SECS/GEM Setup Dialog Box – Setup Tab (FmXP shown).................................1-21 Figure 1-5 SECS/GEM Setup Dialog Box – Communication Tab (FmXP shown) .................
Table 3-7 Control State Variables..........................................................................................3-11 Table 3-8 Control State CEIDS..............................................................................................3-12 Table 3-9 E10 State Transitions ............................................................................................3-14 Table 3-10 E10 State Values .................................................................................................
Table 4-14 RSPACK Values ..................................................................................................4-29 Table 4-15 STRACK Values ..................................................................................................4-30 Table 4-16 VLAACK Values...................................................................................................4-32 Table 4-17 LVACK Values .....................................................................................................
Table 5-14 SECS Messages Host Requests Report by CEID .................................................5-7 Table 5-15 SECS Messages Host Requests Annotated Report by CEID................................5-8 Table 5-16 SECS Messages Host Requests Report by RPTID...............................................5-8 Table 5-17 SECS Messages Host Requests Annotated Report by RPTID .............................5-8 Table 5-18 SECS Messages Are You There ................................................................
Table 5-50 SECS Messages Host Requests Date and Time ................................................5-22 Table 5-51 SECS Messages Equipment Requests Date and Time.......................................5-22 Table 5-52 SECS Messages Host Enables Spooling of Messages.......................................5-23 Table 5-53 SECS Messages Spooled and Transmitted ........................................................5-24 Table 5-54 SECS Messages Host Purges Spool...................................................
1 Introduction 1.1 Overview This manual describes the SECS/GEM interface (version 4.8.3 or higher) used with Fluidmove for Windows NT (FmNT) version 4.8.3 or higher, or Fluidmove for Windows XP (FmXP) version 5.0 or higher. The term “Fluidmove” as used in this manual refers to the applicable software (FmNT or FmXP) used on the Equipment. This document is a modification of the GW Associates GES-1993 SECS/GEM Interface document and has been especially prepared to support Fluidmove.
1.2 Terminology Abbreviations and terms used in this manual are defined in Table 1-1. Table 1-1 Definition of Terms Term Definition Alarm An alarm is related to any abnormal situation on the Equipment. GEM allows the Host to be notified when alarm conditions are detected and cleared. ALID Equipment Alarm ID. The identifier for a specific alarm condition. CEID Collection Event ID. The identifier for a specific collection event.
Table 1-1 Definition of Terms (continued) Term Definition HSMS-SS High Speed Message Service-Single Session. This standard defines TCP/IP network communication used by GEM for Host/Equipment communication. It replaces the SECS-I standard. ID Identifier or Identification. Operator The person who physically has access to the Equipment’s material port(s) and control panel. This is the person who is operating the dispensing system.
1.3 SECS/GEM – Fluidmove Compatibility Compatibility between Fluidmove and SECS/GEM version is as follows: 1.4 • FmNT 4.8 and earlier is compatible only with Fluidmove SECS/GEM, version 4.1. • FmNT 4.8.2 and later, and FmXP 5.0 and later requires Fluidmove SECS/GEM, 4.8.1 or later. SECS Standard The SEMI Equipment Communication Standard (SECS) is published by Semiconductor Equipment and Materials International (SEMI).
1.4.2 Physical Connection The GEM hardware interface must be a TCP/IP network card connection through a Ten-Base-T connector or BNC jack (SECS-II interface). NOTE The following information is provided only as a reference for RS-232 connections (SECS-I interface) and is currently not implemented by Fluidmove: • The RS-232 connector on the Equipment deviates from the standard SECS-I DB25F connector. • The Equipment provides a male 25-pin RS-232 “DB25M” connector on its back panel as the SECS port.
1.4.4 Interleaved Blocks The Equipment never sends interleaved blocks to the Host. That is, the Equipment always sends all blocks of one message before sending the first block of the next message. This simplifies the job of the Host. However, the Equipment allows the Host to send interleaved blocks, if it so chooses. 1.4.5 Simultaneous Transactions The Equipment may initiate several simultaneous outstanding SECS transactions.
1.5 SECS-II Clarifications The Equipment uses the following SECS-II conventions: 1.5.1 Data Format Types Where the Standards permit a choice of data item types, the choice has been made as described in Section 4 SECS Message Detail. For outgoing messages, the Equipment always sends Data Items of the exact format shown. For some incoming messages, the Equipment “forgives” minor Host errors. For example, the Equipment may accept a U1 Data Item where a U2 format was expected.
1.6 GEM Standard The SEMI Generic Equipment Model for Effective Factory Automation (GEM) is another document published by SEMI. The GEM standard defines some useful conventions for designing the communications interface on a unit of factory Equipment to improve operations with a Host Computer. The Equipment complies with SEMI E30-1993. 1.
Table 1-3 GEM Compliance Statement FUNDAMENTAL GEM REQUIREMENTS IMPLEMENTED COMPLIANT State Models ⌧ Yes No ⌧ Yes No Equipment Processing States ⌧ Yes No ⌧ Yes No S1F13/S1F14 Auto Connection Scenario ⌧ Yes No ⌧ Yes No Event Notification ⌧ Yes No ⌧ Yes No On-line Identification ⌧ Yes No ⌧ Yes No Error Messages ⌧ Yes No ⌧ Yes No Control (Operator Initiated) ⌧ Yes No ⌧ Yes No Documentation ⌧ Yes No ⌧ Yes No ADDITIONAL CAPABILITIES IMPLEMENTED COMPLIANT Establish Co
1.8 SEMI E10 Standard NOTE Fluidmove does not upload the E10 states through the SECS/GEM interface. SEMI E10 provides a guideline for the definition and measurement of Equipment reliability, availability, and maintainability (RAM). This document defines six basic Equipment States which define how Equipment time is categorized. A status bar on the Equipment reflects the current E10 state. These Equipment states are as defined in SEMI E10-1992 (Section 3, ‘Equipment States’).
1.9 SECS I / SECS II Parameters 1.9.1 SECS-I Parameters This section provides hardware settings that apply only to the RS-232 hardware interface. NOTE Fluidmove currently does not support this interface. Table 1-4 SECS Installation Parameters Parameter Default Device ID 1 Baud Rate 9600 Allowable speeds are 110, 150, 300, 600, 1200, 2400, 4800, 9600, and 19200 Baud. T1 0.5 Sec Inter-character Timeout. Range allowed is 0.1 to 10.0 seconds, at increments of 0.1 seconds. T2 10.
1.9.3 GEM Configuration This Equipment is configurable for operation with most older Host computers which do not support the GEM message set, or support an older version of GEM. 1. Equipment constant “CONFIGALARMS” (VID 1) selects the message the Equipment will send for Alarm Reports. “ConfigAlarms” may be 0, 1, or 2, selection S5F1, S5F71, or S5F73, respectively. 2. Equipment constant “CONFIGCONNECT” (VID 2) selects the message the Equipment will send for Connect Request.
Table 1-6 shows the recommended settings for compatibility with various types of Hosts. Factory (Default) settings are shown in bold. Table 1-6 Compatibility Settings Introduction Equipment Constant E30-93 GEM 3.1 GEM 3.0 GEM 2.0 GEM 1.
1.10 State Diagrams This document uses several Finite State Machine diagrams to describe the current condition of the Equipment’s SECS link, material handling mechanisms, and process cycle. Each Finite State Machine diagram includes a State Diagram and a complete description of the states and state transitions. All Finite State Diagrams have been prepared in the format specified in the GEM standard.
1.11 Machine Operation and the GEM Interface 1.11.1 Connecting to the Host Fluidmove loads the GEM communications driver immediately upon startup. Once connection to the driver is established, the device enters its default communication state as set by the Operator. This default state can be set via the SECS/GEM Setup dialog box in Fluidmove. The recommended selection is “Enabled”.
1.11.4 Loss of Communications Link: Spooling Communications may be temporarily lost with the Host from time to time. GEM message responses and requests are automatically spooled to disk when this happens. When communications are restored the messages on the SPOOL file are automatically sent to the Host. Spooling is enabled for Fluidmove.
Remote run commands are described in Table 1-7. Table 1-7 Remote Run Commands Command Description START This command is successful when the Control State is OnLine - REMOTE , the board is in the Dispensing position, the machine is configured for a run, and the process program has been selected. This event begins the continuous processing of substrate trays. Processing can be interrupted by STOP, PAUSE, and ABORT commands. The Operator can also initiate PAUSE and STOP commands from the Run Window.
1.11.6.4 Terminal Message Notification After a terminal message has been received from the Host, the GEM status bar at the bottom of the Fluidmove Run Window will start blinking. See Figure 1-1. GEM status bar displays the current communication, control, and spooling state. If the user has selected the beeping option (through the SECS/GEM Setup dialog box) a half-second interval beep is also provided to catch the user’s attention. During run-time, the GEM status bar is displayed.
1.11.7 SECS/GEM Setup Dialog Box in Fluidmove The SECS/GEM Setup dialog box can be accessed by pressing the SECS/GEM button in the Fluidmove Main Window. The dialog box contains tabs with buttons and drop-down menus for control and setup of GEM features. These tabs are described in Figure 1-2 through Figure 1-7. 1 4 5 1 2 3 Item Name 1 Control Description On-Line Local: The Operator has control of the system. The system will reject most Host commands.
1 2 3 4 5 Item Name 1 Incoming Message 2 Acknowledge 3 Outgoing Message 4 Send 5 Status Box Description Messages from the Host are displayed in this box. Press to acknowledge receipt of the incoming message from the Host. Enter messages to the Host in this box. Press to send the message in the Outgoing Message box. Displays the current communication state, control state, and spooling state.
1 2 3 4 5 6 Item Name 1 Establish Communication Timeout The user-configurable equipment constant that defines the delay, in seconds, between attempts to send S1F13. This value is used to initialize the CommDelay timer. Default Communication State Allows the user define the default communication state upon Fluidmove’s startup. The valid choices are: ENABLED: Fluidmove will attempt to establish communication link upon start up.
1 2 Item Name Description 1 Device ID Displays the unique identifier for the Equipment. 2 Status Box Displays the current communication state, control state, and spooling state.
1.11.8 Fluidmove Run Window Interface The Fluidmove Run Window includes a SECS/GEM tab that shows communication status and allows messages to be sent between the Host and the Operator. This tab is described in Figure 1-7. 1 2 3 4 5 7 6 Item Name Description 1 Incoming Message 2 Acknowledge 3 Outgoing Message 4 Send 5 Status Box Messages from the Host are displayed in this box. Click to acknowledge receipt of the incoming message from the Host. Enter messages to the Host in this box.
2 Message Summary This section covers the primary SECS messages sent and received between the Host and the Equipment. 2.1 Host-to-Equipment Messages Table 2-1 describes primary SECS messages sent by the Host, and the associated reply messages from the Equipment. The CState column indicates the control state the Equipment must be in to accept the message. The current value of the Equipment Control State can be found in variable CONTROLSTATE (VID 4).
Table 2-1 SECS Messages – Host-to-Equipment (continued) Primary Reply CState Description S2F35 S2F36 4,5 Link Event Report S2F37 S2F38 4,5 Enable/Disable Event Report S2F39 S2F40 4,5 Multi-Block Inquire/Grant S2F41 S2F42 5 S2F43 S2F44 4,5 Reset Spooling Streams and Functions S2F45 S2F46 4,5 Define Variable Limits Attributes S2F47 S2F48 4,5 Variable Limit Attribute Request S5F3 S5F4 4,5 Enable/Disable Alarm S5F5 S5F6 4,5 List Alarms S5F7 S5F8 4,5 List Enabled Alarms
2.2 Equipment-to-Host Messages Table 2-3 describes primary SECS messages sent by the Equipment, and the associated reply messages from the Host. Refer to Table 8-1 for further details. In the Notes column, those messages marked with “N” are provided for non-GEM or older GEM compatibility.
3 Operating Characteristics This section describes the operating characteristics of the Equipment. 3.1 Communications States The Equipment represents the current state of its SECS link using a Communication Finite State Machine diagram. The purpose is to make clear how this link is initiated and terminated. The Communications State is displayed in the GEM status bar and the SECS/GEM tab of the Fluidmove Run Window.
3.1.1 Communications Finite State Description Figure 3-1 illustrates the Communications Finite State Machine that the Equipment maintains. " NOTE Refer to Table 3-1 for definition of numbers used in Figure 3-1.
3.1.1.1 State Transitions The following table describes the transitions that can occur. Transitions shown in Figure 3-1 do not cause the Equipment to signal any Collection Event ID (CEID) or to send Event Reports to the Host. " NOTE The numbers in the # column refers to those in Figure 3-1. Table 3-1 State Transitions # From 1 Unknown Power-Up 2 Disabled Operator enables SECS link. Enabled Equipment will attempt to establish communications with the Host.
3.1.1.2 Communications States The current communication state will be one of the values specified in Table 3-2. There is no variable indicating the communication state. The communication state is presented to the Operator on the main Operator interface screen. Table 3-2 Communication State Values Value Description DISABLED The SECS link to the Host is disabled at the Equipment. The Equipment will send no messages to the Host. The Equipment will not respond to a Host-initiated ENQ.
3.1.2 Power Up At Power Up (or System Start), the equipment constant “INITCOMMSTATE” (VID 7) controls whether the state is initialized to DISABLED or ENABLED. The factory setting is DISABLED. 3.1.3 Related Variables Table 3-3 lists the variables (SVs, ECs, or DVs) which are relevant to establishing communications. For a more complete description of these variables, refer to Appendix A. Table 3-3 Related Variables Variable Name 3.1.
3.2 Control States This section describes the Control characteristics of the Equipment. The Equipment may be in one of the control states in the following table. This value is reflected in status variable CONTROLSTATE (VID 28). Table 3-4 Control States Value State 1 Off-Line/Equipment Off-Line 2 Off-Line/Attempt On-Line 3 Off-Line/Host Off-Line 4 On-Line/Local 5 On-Line/Remote GWGEM software maintains the GEM Control State finite state machine.
3.2.1 Control Finite State Description Figure 3-2 and Table 3-5 describe the Equipment Control State. The Equipment behaves differently and will accept different messages depending on its current control state. The purpose of this diagram is to make clear to the Host exactly what is happening at the Equipment. The logic for these states and transitions is the logic specified in the GEM standard. " NOTE Refer to Table 3-5 for definition of numbers used in Figure 3-2.
3.2.1.1 Control State Transitions Certain state transitions will cause a collection event to be signaled. If the event is enabled, this event will be sent to the Host along with the appropriate reports if appropriate. Table 3-5 lists the state transitions and notes when events will be sent to the Host. " NOTE The numbers in the # column refer to those in Figure 3-2.
Table 3-5 Control State Transitions (continued) # 9 From On-Line Trigger To Host puts the Equipment OffLine by sending S1F15 and receiving the S1F16 with OFLACK = 0x00. Host Off-Line Description EVENT: GemEquipmentOFFLINE (CEID 22). The Equipment will accept a Host initiated request to go On-Line by replying to the S1F17 with ONLACK = 0x00. 10 Host Off-Line Successful completion of S1F17 / S1F18 transaction, with ONLACK = 0x00. On-Line 11 Unknown Entry into On-Line super-state.
3.2.1.2 Control States The variable CONTROLSTATE (VID 28) represents the current control state, and will be one of the values listed in Table 3-6. Table 3-6 Control State Values Value Description Off-Line/EQUIPMENT OFFLINE The Operator has put the Equipment off-line. In this state, only the Operator can put the Equipment on-line. Any Host-initiated primary message (except S1F13 and S1F17) will be replied to with an SnF0 ABORT message by the Equipment.
3.2.2 Power Up At power-up, the equipment constant “INITCONTROLSTATE” (VID 9) controls whether ControlState is initialized to ONLINE or OFFLINE. Within the Off-Line super-state, the equipment constant “OFFLINESUBSTATE” (VID 42) controls whether the Control State defaults to: 1. Equipment Off-Line 2. Host Off-Line 3. Attempt On-Line If INITCONTROLSTATE (VID 9) initializes to On-Line, the variable ONLINESUBSTATE (VID 44) determines whether the default state is: 1. Local 2.
3.2.4 Related Events Table 3-8 lists the collection events (CEIDs) which are relevant to the Control State. For a more complete description of these events, refer to Appendix B or the description in this chapter. Table 3-8 Control State CEIDS Collection Event 3.3 CEID GemControlStateLOCAL 8 GemControlStateREMOTE 9 GemEquipmentOFFLINE 22 Process States See Figure 3-4 for a description of the Fluidmove processing state model.
3.3.1 E10 State Figure 3-3 illustrates the state of the Equipment in relationship to overall factory production. The E10 state diagram is implemented in the Equipment according to the details specified in the SEMI E10 document. The following summarizes the Equipment’s implementation of the E10 standard: The Equipment can transition from any state to any other state except for “Productive”. The “Productive” state can only be entered from the “Standby” state.
3.3.1.1 E10 State Transitions Certain state transitions will cause a collection event to be signaled. If the event is enabled, this event will be sent to the Host along with the appropriate reports if appropriate. Table 3-9 lists the state transitions and notes when events will be sent to the Host. " NOTE The numbers in the # column refer to those in Figure 3-3.
3.3.1.2 E10 STATE Values The values for E10 states are listed in Table 3-10. Table 3-10 E10 State Values Value Description Non-Productive/NonScheduled Time The Equipment is not scheduled to be used in production. An Operator can put the Equipment into this state at any time. Non-Productive/Unscheduled Downtime The Equipment has been scheduled to be used in production, but is unable to be used because of unforeseen events.
3.3.2 Equipment Process States Figure 3-4 illustrates in greater detail the processing at the Equipment. This diagram depicts the working states of the Equipment. " NOTE Refer to Table 3-11 for definition of numbers used in Figure 3-4.
3.3.2.1 Equipment Process State Transitions " NOTE The numbers in the # column refer to those in Figure 3-4. Table 3-11 Process State Transitions # From Trigger To Description 1 Unknown Power-Up Idle At power-up, the Equipment defaults to the IDLE state. 2 Idle Run Command Running Either the Host or Operator issues a run command. This command can be issued by a remote command from the Host or by local Operator.
3.3.2.2 Equipment Process State Values The values for Equipment process states are listed in Table 3-12. Table 3-12 Equipment Process State Values Value Description Idle The Equipment is initialized to this state. This state indicates that the Equipment is not dispensing on a board nor is it waiting for a board to arrive at the dispense station.
3.4 Data Collection Note the three types of variables: Status Variable (SV), Data Variable (DV), and Equipment Constants (EC). The Host sets only ECs. DVs are time stamped by being associated with Collection Events IDs (CEID), and will be reported by Fluidmove in Event Reports. 3.4.1 Variables The Equipment has a fixed set of Variables which can be read by the Host. Each variable is identified by a unique Variable ID (VID). Appendix A lists all variables for both Fluidmove and standard GEM operations.
The Equipment allows the Host to enable and disable Event Reports using S2F37. If the Host enables a CEID, for which no Event Report is defined, the Equipment will send a “null” (no data) report when the event occurs. The Host can “force” Event Reports on the Equipment using the following Event Report Request messages: 3.4.6 S6F15 Host requests an Event Report associated with a CEID. S6F17 Host requests an Annotated Event Report associated with a CEID.
3.4.7 Limits Monitoring The Host can define limits for various Variables on the Equipment. When the appropriate limits transitions occur, the Equipment will report this occurrence by sending an event to the Host (if the event is enabled). The Host may define limits for a particular Variable through the S2F45 (Define Variable Limit Attributes). Through this message, the Host may define up to seven limits for each eligible Variable. For each limit (LIMITID), the Host defines an UPPERDB and a LOWERDB.
Limits States Disabled 2 1 Enabled C Below Limit 5 3 4 No Zone Above Limit 6 Figure 3-6 Limits State Diagram 3-22 Operating Characteristics
3.4.8 Limits State Transitions Table 3-14 Limits State Transitions # From 1 Enabled Host undefines limits attributes. 2 Disabled Host defines limits. Conditional Host sends S2F45 to define limits. 3 Below Limit Variable changes to greater than or equal to UPPERDB. Above Limit Limit transition event is signaled to Host if enabled. 4 Above Limit Variable changes to less than or equal to LOWERDB. Below Limit Limit transition event is signaled to Host if enabled.
3.4.9 Disk Files The Equipment maintains a disk file which contains the current equipment constant settings. The file is updated each time the Operator or Host changes an equipment constant. The most recent settings for some of the equipment constants are read from the file when the Equipment is powered-on. All Event Report definitions, links, and enable status as well as Limits attributes are also maintained on separate disk files. 3.4.
3.5.2 Reporting The Equipment reports alarms to the Host when they occur, without Host action, using the alarm report message S5F1 or configurable option, depending on CONFIGALARMS. The transition of an ALID from OFF to ON is referred to as “going on” or “leading edge”, and the transition from ON to OFF as “going off ” or “trailing edge”. The Equipment reports both leading and trailing edge transitions.
3.5.6 Related Variables The following table lists the variables (SVs, ECs, or DVs) which are relevant to alarm management. For a more complete description of these variables, refer to Appendix A. Table 3-18 Alarm Management Variables Variable Name 3.5.
3.6 Process Program Management Processing on the Equipment is controlled by Process Programs. The Equipment requires selection of a Process Program for each process. The Equipment supports the use of unformatted process programs. Fluidmove uses proprietary ASCII and binary image files to define process programs (recipes). 3.6.1 Equipment Management of Process Programs The Equipment provides a Process Program Library, implemented as a set of binary files maintained on a hard disk.
3.6.3 Related Variables The following table lists the variables (SVs, ECs, or DVs) which are relevant to process program management. For a more complete description of these variables, refer to Appendix A. Table 3-19 Process Program Management Variables Variable Name 3.6.4 VID PPCHANGENAME 40 PPEXECNAME 32 PPCHANGESTATUS 41 Related Events The following table lists the collection events (CEIDs) which are relevant to process program management.
3.7 Remote Commands Processing at the Equipment can be guided by either a local Operator or by a Host computer. This section describes the remote commands available to the Host. Much of the behavior of the Equipment and its acceptance of remote commands is directed by requirements of the Control State. For a complete description of the Control State, refer to 3.2 Control States. The Equipment will accept remote commands only when the Control State is Remote.
3.7.1 S2F41 Commands The general format for remote commands using the S2F41 message is: S2F41 [W] E * Command Parameter Name * Command Parameter Value > ... > > . The following commands may be sent by the Host to the Equipment: START This command starts processing on the Equipment assuming all proper initialization has taken place and material is present. S2F41 [W] > .
PAUSE The PAUSE command will cause the Equipment to complete the current instruction in process, but not to start the next instruction until the RESUME command has been given. S2F41 [W] > . RESUME After a PAUSE command has been given, the RESUME command will continue to process the existing board according to the recipe. S2F41 [W] > . LOCAL While the Equipment is in Remote state, the Host can put the Equipment into Local state by sending the LOCAL command.
3.7.2 Related Variables The following table lists the variables (SVs, ECs, or DVs) which are relevant to remote control. For a more complete description of these variables, refer to Appendix A. Table 3-21 Remote Control Variable Variable Name 3.7.3 VID ABORTLEVEL 21 PREVIOUSCOMMAND 34 Related Events The following table lists the collection events (CEIDs) which are relevant to remote control. For a more complete description of these events, refer to Appendix B or the description in this chapter.
3.8 Material Movement Material movement on the Equipment consists of the following three board holding areas: • Pre-dispense Area • Dispensing Area • Post-dispense Area In order for processing to begin, a board must arrive from the upstream machine. The Equipment then conveys the board to the pre-dispense area, conveys it to the dispensing area, processes it, and then conveys the board to the post-dispense area. Before a new lot can be started, the board must be removed from the dispensing area.
3.9 Equipment Terminal Services The Equipment supports exchange of free text messages with the Host (SECS Stream 10). This Equipment accepts the following messages from the Host, and responds accordingly if the W-Bit is set to 1: S10F3 S10F5 S10F9 /* Single Line Data */ /* Multi-Line Data */ /* Broadcast */ The message text will be displayed on the Equipment’s CRT.
3.10 Error Messages The Equipment provides standard Stream 9 messages to report SECS-I errors. Refer to 5.7 SECS Error Messages for detailed description of these messages: S9F1 Unrecognized Device ID S9F3 Unrecognized Stream S9F5 Unrecognized Function S9F7 Invalid Data S9F9 Transaction Timeout S9F11 Data Too Long Fluidmove can reject a primary message received from the Host as incorrectly formatted for SECS-II (invalid data, or data too long). 3.
3.12 Spooling When the SECS link between the Host and the Equipment goes down (RTY error on the Equipment side), the Equipment will spool appropriate messages so that the Host can read them once the link comes back up (after a successful Connect Request transaction). The Host can set spooling attributes on the Equipment by setting certain equipment constants with the S2F15/16 transaction. The Host can define streams and functions of messages to be spooled through the S2F43/44 transaction.
3.12.2 Spooling Sequence Messages are sent to the spool only if the Host has enabled these messages for spooling. This precondition will not be repeated throughout this section. Assume that the messages referred to in this section have been enabled for spooling. While spooling is active, the Host may initiate primary messages and the Equipment will respond, if it is in the COMMUNICATING state. Figure 3-7 and Table 3-24 describe the spooling sequence.
" Table 3-24 Spooling State Transitions NOTE The numbers in the # column refer to those in Figure 3-7. # From Trigger To 1 Power On Equipment shutdown Power Off 2 Power Off Equipment Startup History* (Power On) Equipment re-boots after a shutdown. Spooling will continue according to its state when the Equipment was powered off. 3 Spool Inactive The Equipment experiences a transmission failure and the variable GemConfigSpool (VID 66) is set to “1” (enabled).
3.12.2.1 Spooling Starts When a transmission failure occurs, the first message sent to the spool is the event message GemSpoolingActivated. The next message sent to the spool is the message which caused the communications failure. Table 3-25 depicts the activity at the Equipment when spooling starts.
3.12.2.3 Host Reads Spooled Data The Host can read spooled messages by sending the S6F23 message. Upon receipt of this message, the Equipment will reply and attempt to send spooled messages. Messages are sent in order of oldest to newest, with no priority given to a particular kind of message. The EC MAXSPOOLTRANSMIT determines the maximum number of spooled messages which are sent per S6F23 message received from the Host.
3.12.3 Spool States 3.12.3.1 Power Off The Equipment is completely shut down. 3.12.3.2 Power On The Equipment is “on” and in a stable state. Table 3-26 describes the substates. Table 3-26 Power On Spool Substates Substate Description Spool Inactive Spooling is not activated. This is either because GemConfigSpool is “0” (disabled) in which case, spooling will never be active, or because while GemConfigSpool is enabled (“1”), a RTY error has not occurred. In this state, no messages are sent to the spool.
3.12.4 Related Variables The following table lists the variables (SVs, ECs, or DVs) which are relevant to spooling. For a more complete description of these variables, refer to Appendix A. Table 3-27 Spooling Variables Variable Name 3.12.
4 SECS Message Detail This section describes the basics of SML notation and lists each message sent or understood by the Equipment. 4.1 SML Notation Message descriptions are shown using “SECS Message Language” (SML) notation. SML is a general notation developed by GW Associates for describing SECS messages. SML is similar to the notation used in the SECS Standards documents, but SML is a more precise and regular notation. 4.1.
Table 4-1 Components of a SML Data Item (continued) Description Component value Value of a single item element. Values are shown in a notation that depends on the item type. For example, ASCII values are shown as characters enclosed in quotes, Unspecified Binary values are shown in hexadecimal. An ellipsis (…) is used to indicate additional elements may occur, as for example where substructures may repeat in a List structure.
4.1.2 Message Format The format of a complete message is as follows: SnFn W item . The components of a complete message are described in Table 4-2. Table 4-2 Components SML Notation Component SnFn The Stream and Function Codes, S1F1 for example. The W-Bit, if set. Omitted if not set. If the W-Bit is optional, it is coded within brackets “[W]”. W item . Description A Data Item that is formatted as described in 4.1.1. A period (.) ends the message definition.
4.2 SECS Messages The following subsections describe the SECS messages sent or understood by the Equipment. 4.2.1 S1F1 - Are You There S1F1 W. * H<->E The Host may send this message to the Equipment at any time. The Equipment sends this message periodically as a “heartbeat” to determine if the SECS link is operational. The equipment constant ConfigConnect can be set to cause the Equipment to send S1F1 instead of S1F13 for Connect Request. 4.2.
4.2.4 S1F3 - Selected Status Request S1F3 W * H-> E ... > . * Variable ID The Host requests status from the Equipment. The Host sends the VIDs of interest. Several VIDs can be specified if desired. Normally, only VIDs of class SV (i.e. Status Variables) are used in this message. However, the Equipment allows the Host to use any VID of class DV, EC, or SV. If S1F3 contains a zero-length list, then the Equipment will report all variables of class SV, in order by VID.
4.2.6 S1F11 - Status Variable Namelist Request S1F11 W * H->E ... >. * Status Variable ID The Host format descriptions for the specified Variables. Several VIDs can be specified if desired. Normally, only VIDs of class SV (i.e. Status Variables) are used in this message. However, any VID of class DV, EC, or SV can be used. If S1F11 contains a zero-length list, then the Equipment will report all variables of class SV, in order by VID. S1F11 W * H->E . 4.2.
4.2.8 S1F13 - Connect Request The Equipment sends this message using the following format: S1F13 W * H<-E > . The Host sends this message using the following format: S1F13 W * H->E . Either end of the link may send S1F13 as the first message to establish connection of the link. Under the Equipment’s initialization logic, the Equipment will always attempt to establish the link. If no Host acceptance reply is received, the Equipment sends this message periodically. 4.2.
4.2.10 S1F15 - Request Off-Line S1F15 W . * H -> E Host requests the Equipment to go Off-Line. 4.2.11 S1F16 - Off-Line Acknowledge S1F16 . * H <- E * OFLACK Equipment Control State transits to Host Off-Line and sends this message in response to S1F15 primary. OFLACK is always zero. 4.2.12 S1F17 - Request On-Line S1F17 W . * H -> E Host requests the Equipment to go On-Line. 4.2.13 S1F18 - On-Line Acknowledge S1F18 .
4.2.14 S1F65 - Connect Request " NOTE This message is provided only for compatibility with Host computers which support an older version of GEM. The equipment constant ConfigConnect can be set to cause the Equipment to send S1F65 instead of S1F13 for Connect Request. The Equipment sends this message using the following format: S1F65 W * H<-E > . Format 1: The Host sends this message using the following format: S1F65 W * H->E .
4.2.15 S1F66 - Connect Request Acknowledge " NOTE This message is provided only for compatibility with Host computers which support an older version of GEM. If the Host sends S1F65, Format 1, the Equipment replies S1F66 using the following format: S1F66 * H<-E > > . * COMMACK If the Host sends S1F65, format 2, the Equipment replies S1F66 using the following format: S1F66 .
4.2.16 S2F13 - Equipment Constant Request S2F13 W * H->E ... > . * Equipment Constant ID The Host requests the VIDs of interest. Several VIDs can be specified if desired. Normally, only VIDs of class EC (i.e. equipment constants) are used in this message. However, any VID of class DV, EC, or SV can be used. If S2F13 contains a zero-length list, then the Equipment will report all variables of class EC, in order by VID.
4.2.18 S2F15 - New Equipment Constant Send S2F15 W * H->E > * Equipment Constant ID ... > . The Host sends new values for desired equipment constants. Several equipment constants can be specified if desired. Only VIDs of class EC can be used in this message. 4.2.19 S2F16 - Equipment Constant Send Acknowledge S2F16 . * H<-E * Equipment Acknowledge Code Normal completion returns a zero (0) in EAC.
4.2.20 S2F17 - Date and Time Request S2F17 W . * H<->E The Host may send this message at any time to determine the Date and Time base that the Equipment is currently using. The Equipment sends this message at the request of the Operator. 4.2.21 S2F18 - Date and Time Data S2F18 * H<->E * TIME - Date and Time . * If TIMEFORMAT = 0 – OR – .
4.2.22 S2F23 - Trace Initialize Send S2F23 W * H->E ... > > . * * * * Trace ID DSPER - Data Sample Period Total Number of Samples Reporting Group Size * Status Variable ID The Host requests the Equipment to initiate a time driven trace operation. The Equipment will send trace data using S6F1. If TRID in S2F23 matches TRID of an existing trace, the existing trace operation is canceled, and replaced by the new one.
For compatibility with older Host implementations, the Equipment allows the following alternative form for this message, using an array format: S2F23 W * H->E > . 4.2.23 * * * * * Trace ID DSPER - Data Sample Period Total Number of Samples Reporting Group Size Status Variable ID array S2F24 - Trace Initialize Acknowledge S2F24 . * H<-E * TIAACK - Trace Init. Ack.
4.2.24 S2F25 - Diagnostic Loopback Request S2F25 W . * H->E * ABS - Any Binary String The Host sends an arbitrary binary string to test operation of the link. The Equipment never sends this message to the Host. 4.2.25 S2F26 - Diagnostic Loopback Data S2F26 . * H<-E * ABS - Any Binary String The Equipment “echoes” back the binary data from the Host’s S2F25. 4.2.26 S2F27 - Initiate Process Request S2F27 [W] > > .
4.2.27 S2F28 - Initiate Process Acknowledge S2F28 . * H<-E * Command Ack. Code Normal completion returns a zero (0) in CMDA. A non-zero value for CMDA indicates that the Equipment has rejected the Remote Command. Table 4-6 CMDA Values CMDA 4.2.28 Description 0x00 OK. All normal. 0x01 Invalid command. Equipment rejects command. 0x02 Cannot perform now. Equipment rejects command. 0x40 Control State is Local. Equipment rejects command. 0x41 Incorrect Process State for this command.
4.2.29 S2F30 - Equipment Constant Namelist Reply S2F30 * H<-E, Multiblock > * * * * * * Equipment Constant ID Equipment Constant Name ECV Minimum Value ECV Maximum Value ECV Default Value Units of Measure ... > . The Equipment returns the equipment constant descriptions in the order requested in S2F29. If any VID specified in S2F29 is invalid, the corresponding List in S2F30 has the following error format: 4.2.
4.2.32 S2F33 - Define Report S2F33 W * H->E, Multiblock ... > > ... > > . * DATAID * Report ID * Variable ID The Host specifies one or more Report IDs, and defines which Variables should be included in each report. If S2F33 is multi-block, the Host may optionally send the S2F39/S2F40 Inquire/Grant Transaction before sending S2F33, but this Equipment does not require it. The Equipment ignores DATAID.
4.2.33 S2F34 - Define Report Acknowledge S2F34 . * H<-E * DRACK - Acknowledge Code Normally, DRACK is zero. Any non-zero DRACK indicates the Equipment has rejected the entire S2F33 message. Table 4-8 DRACK Values DRACK 4-20 Description 0x00 OK. 0x02 Denied. Invalid format. 0x03 Denied. At least one RPTID already defined. 0x04 Denied. At least one VID does not exist.
4.2.34 S2F35 - Link Event Report S2F35 W * H->E, Multiblock * DATAID * Collection Event ID * Report ID ... > > ... > > . The Host links Report Ids to selected Collection Event Ids. The Specified CEIDs are initialized to “disabled”. See 4.2.36 S2F37 for enabling CEIDs. If S2F35 is multi-block, the Host may optionally send the S2F39/S2F40 Inquire/Grant transaction before sending S2F35, but the Equipment does not require it. The Equipment ignores DATAID.
4.2.35 S2F36 - Link Event Report Acknowledge S2F36 . * H<-E * LRACK - Acknowledge Code Normally, LRACK is zero. Any non-zero LRACK indicates the Equipment has rejected the entire S2F35 message. Table 4-9 LRACK Values LRACK 4-22 Description 0x00 OK. 0x02 Denied. Invalid format. 0x03 Denied. At least one CEID link already defined. 0x04 Denied. At least one CEID does not exist. 0x05 Denied. At least one RPTID does not exist. Other Equipment has rejected the S2F35 message.
4.2.36 S2F37 - Enable/Disable Event Report S2F37 W * H<-E ... > > . * Coll. Event Enable * Collection Event ID The Host enables reporting for a list of Collection Event IDs, or disables reporting for the list. CEED is “True” to indicate Enabling, or “False” to indicate Disabling reporting for the specified CEIDs. The Host can enable or disable all CEIDs by using the following special format: S2F37 W * H->E > . 4.2.37 * Coll.
4.2.38 S2F39 - Multi-Block Inquire S2F39 W * H->E > . * DATAID The Host may send this Inquire/Grant transaction preceding any multiblock S2F33 or S2F35. For this Equipment, this Inquire/Grant is optional. The Equipment accepts it, but ignores it, commits no resources, and initiates no Conversation Timeout. The Equipment accepts multiblock S2F33 or S2F35 even if not preceded by the Inquire/Grant. 4.2.39 S2F40 - Multi-Block Grant S2F40 .
4.2.40 S2F41 - Remote Command with Parameters S2F41 [W] * H->E * Command Parameter Name * Command Parameter Value > ... > > . The Host sends a command with parameters to the Equipment. If a command has no parameters, S2F41 has the following format: S2F41 [W] * H->E > . * Remote Command String The Equipment ignores case when performing validity checks on the RCMD and CPNAME strings.
4.2.41 S2F42 - Remote Command Acknowledge S2F42 * H<-E > ... > * Host Command Ack. Code * Name of Parameter * Cmd Param Ack Code > . Normal completion returns a zero (0) in HCACK. The number of erroneous parameters “N” in S2F42 will be zero. A non-zero value for HCACK indicates that the Equipment has rejected the Remote Command. The number of erroneous parameters “n” can be zero or greater.
Table 4-13 CPACK Values SECS Message Detail CPACK Description 0x01 Invalid parameter name (CPNAME). The CPNAME is not a valid parameter for this command. 0x02 Illegal parameter value (CPVAL). The parameter value is out of range. 0x03 Illegal format for parameter (CPVAL). The value for this parameter does not use the correct SECS-II data item type. 0x40 Duplicate parameter name. This parameter name occurred at least twice in the S2F41 command.
4.2.42 S2F43 - Reset Spooling Streams and Functions S2F43 W * H -> E ... > * Message Stream * Message Function > ... > . The Host sends message to specify which messages the Equipment should spool in the event of a communications loss. When this message is received by the Equipment, all previous definitions of messages to spool are replaced.
4.2.43 S2F44 - Reset Spooling Acknowledge The S2F44 message has two forms, depending on the return code in RSPACK. If there are no errors in S2F43, the format of S2F44 is as follows. S2F44 * H <- E * RSPACK > . If S2F43 contains any errors, the Equipment will discard the entire S2F43, and return error information is S2F44, as follows: S2F44 * H <- E * Msg String * Stream Ack Code * Msg Function ... > > .
When errors exist in the request to set some messages as spool-able, the Equipment will return codes explaining the nature of the error. These codes are found in the STRACK data item. Table 4-15 STRACK Values 4.2.44 STRACK Description 0x01 Spooling not allowed for this stream. Spooling is never allowed for stream one. 0x04 Requested message is a secondary message and therefore ineligible for spooling.
UPPERDB and LOWERDB must match the value format of the specified variable The Host may undefine all limits for all VIDs: S2F45 W * H -> E > . The Host may undefine all limits for a specific VID: S2F45 W * H -> E > ... > > . The Host may undefine a specific limit for a specific VID: S2F45 W * H -> E > > ... > ... > > .
4.2.45 S2F46 - Variable Limit Attribute Acknowledge This message acknowledges the successful setting of limits as defined in the Host-generated S2F45. S4F46 * H <- E * VLAACK > . If any of the limits proposed in S4F45 are invalid, all limits for all variables in this message are rejected. The following message is sent in the event of an error: S4F46 * H <- E * LVACK > > ... > > .
The LVACK data item gives information to the Host about the status of setting a specific variable when the request to set it is unsuccessful. Table 4-17 LVACK Values LIMIT-ACK Description 0x01 Requested variable does not exist. 0x02 Variable is not eligible for limits definition. 0x03 Requested variable was repeated in request message. 0x04 Error in setting limit due to reason specified in LIMITACK.
4.2.46 S2F47 - Variable Limit Attribute Request S2F47 W * H -> E ... * Requested Variable ID > . The Host sends this message to the Equipment to request the limits attributes for specific variables. The Host may request the limits attributes for all defined variables with the following message. S2F47 W * H -> E . In response to this message, the Equipment reports all limits attributes for all variables.
4.2.47 S2F48 - Variable Limit Attributes Send S2F48 * H <- E * Variable ID * Units of Measure * Minimum Limit * Maximum Limit * Limit ID * Upper Deadband * Lower Deadband > ... > > > ... > . The Equipment sends this message in response to a Host S2F47 and reports the characteristics of limits for specified variables.
If the Host requests the limits for a specific variable which is eligible for limits monitoring but does not have any limits defined, this variable will be reported as follows: S2F48 * H <- E > * Variable ID * * * * Units of Measure Minimum Limit Maximum Limit No Limits Defined > ... > . 4.2.48 S5F1 - Alarm Report S5F1 [W] * H<-E > .
4.2.49 S5F2 - Alarm Acknowledge S5F2 . * H->E * ACK5 - Alarm Acknowledge The Host acknowledges the Alarm Report. This Equipment ignores the ACKC5. 4.2.50 S5F3 - Enable/Disable Alarm Send S5F3 [W] * H->E > . * ALED - Alarm Enable/Disable Code * ALID - Alarm ID The Host commands the Equipment to enable or disable (depending on ALED) reporting for the specified Alarm ID in S5F1, S5F8, S5F71, and S5F73.
4.2.51 S5F4 - Enable/Disable Alarm Acknowledge S5F4 . * H<-E * ACKC5 - Acknowledge Code Table 4-20 ACKC5 Values ACKC5 4.2.52 Description 0x00 Normal. Everything correct. 0x01 Invalid ALID. S5F5 - List Alarms Request S5F5 W . * H->E * Alarm ID Array The Host requests the Equipment to send the current status of the specified Alarm IDs. The Host can use the following special format to request the status of all Alarm IDs: S5F5 W . 4.2.
For any invalid ALID specified in S5F5, the corresponding entry in S5F6 has the following special error format: > * ALCD - Alarm On/Off and Severity Code * Alarm ID * ALTX - Alarm Text If S5F5 specified all alarms, S5F6 reports alarms in order by alarm ID. 4.2.54 S5F7 - List Enabled Alarms Request S5F7 W . * H->E The Host requests the Equipment to send the current status of all Alarm IDs which are currently enabled (refer to 4.2.50 “S5F3 – Enable/Disable Alarm Send”). 4.2.
4.2.56 S5F71 - Alarm Report Block Send S5F71 [W] * H<-E * ALID - Alarm ID * T = Alarm On, F = Alarm Off * ASER Alarm Serial Number * CLOCK > > > . " NOTE This message is provided only for compatibility with Host computers which support an older version of GEM.
4.2.57 S5F72 - Alarm Report Block Acknowledge S5F72 * H->E . The Host acknowledges Alarm Report. This Equipment ignores the data portion of S5F72. 4.2.58 S5F73 - Alarm Report Block Acknowledge S5F73 [W] * H<-E * ALID - Alarm ID * T = Alarm On, F = Alarm Off * TIMESTAMP > . " NOTE This message is provided only for compatibility with older Host computers which support GEM 3.1 (refer to 1.9.3 GEM Configuration).
4.2.60 S6F1 - Trace Data Send S6F1 [W] * H<-E * Trace ID * Sample Number * STIME - Sample Date/Time * If TIMEFORMAT = 0 • OR - * If TIMEFORMAT = 1 ... > * Variable Value >. The Equipment sends time driven trace data, as previously requested by the Host using S2F23. TRID is the Trace ID as initiated by the Host. SMPLN is the sample number. The first sample is “1”, the next “2”, and so on.
4.2.62 S6F3 - Annotated Event Report S6F3 [W] * H<-E, Multiblock > ... > > ... > * DATAID * Collection Event ID * DSID=RPTID Report ID * Variable ID * Variable Value > . " NOTE This message is provided only for compatibility with older Host computers which do not support GEM (refer to 1.9.3 GEM Configuration).
4.2.63 S6F4 - Annotated Event Report Acknowledge S6F4 . * H->E * ACKC6 The Host acknowledges the Event Report. The Equipment ignores ACKC6. 4.2.64 S6F5 - Multi-Block Data Send Inquire S6F5 W * H<-E > . * DATAID The Equipment sends this Inquire/Grant transaction preceding any multiblock S6F3, S6F9, S6F11, or S6F13. The DATAID specified here will appear in the following S6F3, S6F9, S6F11, S6F13.
4.2.66 S6F9 - Event Report " NOTE This message is provided only for compatibility with older Host computers which do not support GEM. (Refer to 1.9.3 GEM Configuration.) S6F9 [W] * H<-E, Multiblock * PFCD (always zero) * DATAID * Collection Event ID * DSID=RPTID Report ID * Variable Value ... > > ... > > . If the equipment constant “ConfigEvents” is set to “0”, the Equipment sends S6F9 instead of the normal S6F11 Event Report.
4.2.67 S6F10 - Event Report Acknowledge S6F10 . * H->E * ACKC6 The Host acknowledges the Event Report. The Equipment ignores ACKC6. 4.2.68 S6F11 - Event Report Send S6F11 W * H<-E ... > > ... > > . * DATAID * Collection Event ID * Report ID * Variable Value This message is the “normal” message that the Equipment uses to report events. In order for this message to be used, the equipment constant “ConfigEvents” must be set to “1”.
4.2.69 S6F12 - Event Report Acknowledge S6F12 . * H->E * ACKC6 The Host acknowledges the Event Report. The Equipment ignores ACKC6. 4.2.70 S6F13 - Annotated Event Report Send S6F13 W * H<-E, Multiblock > * Variable ID * Variable Value ... > > ... > > .
If the CEID is enabled, but no Reports are linked to this CEID, S6F11 has the following special format: S6F13 W * H<-E > . 4.2.71 * DATAID * Collection Event ID S6F14 - Annotated Event Report Acknowledge S6F14 . * H->E * ACKC6 The Host acknowledges the Event Report. The Equipment ignore ACKC6. 4.2.72 S6F15 - Event Report Request S6F15 W . * H->E * Collection Event ID The Host sends the CEID of interest, requesting normal format reports.
4.2.73 S6F16 - Event Report Data S6F16 * H<-E, Multiblock ... > > ... > > . * DATAID * Collection Event ID * Report ID * Variable Value The Equipment sends one or more Event Reports which the Host has previously linked to that CEID (refer to 4.2.34 “S2F35 – Link Event Report”). Each report contains specific Variables which the Host has previously defined for that Report (refer to 4.2.32 “S2F33 – Define Report”).
4.2.74 S6F17 - Annotated Event Report Request S6F17 W . * H->E * Collection Event ID The Host sends the CEID of interest, requesting annotated format reports. 4.2.75 S6F18 - Annotated Event Report Data S6F18 * H<-E * Variable ID * Variable Value > ... > > ... > > . The Equipment sends one or more Event Reports which the Host has previously linked to that CEID (refer to 4.2.
If the CEID specified in S6F17 is invalid, or if no reports are linked to this CEID, this message has the following format: S6F18 * H<-E, Multiblock > . 4.2.76 * DATAID * Collection Event ID S6F19 - Request Report Request S6F19 W . * H->E * Report ID The Host requests a Report for the specified RPTID. 4.2.77 S6F20 - Request Report Data S6F20 * H<-E, Multiblock ... > . The Equipment sends the Report.
4.2.79 S6F22 - Request Annotated Report Data S6F22 * H<-E, Multiblock > * VID - Variable ID ... > . The Equipment sends the Annotated Report. If no Report is defined for the RPTID in S6F21, S6F22 has the following special error format: S6F22 * H<-E . 4.2.80 S6F23 - Request Spooled Data S6F23 W .
4.2.81 S6F24 - Request Spooled Data Acknowledge S6F24 . * H <- E Equipment acknowledges the Host’s request to either purge spooled messages or send spooled messages to the Host. Table 4-23 RSDA Values 4.2.82 RSDA Description 0x00 Normal. Equipment will start to send spooled data or optionally purge the spool. Action performed will depend on value for RSDC in S6F23. 0x02 Denied. Spooled data does not exist.
4.2.83 S7F2 - Process Program Load Grant S7F2 . * H<->E * PPGNT The Receiver grants permission to send a Process Program. The Receiver sends PPGNT value 0x00 to indicate it will accept the Process Program, and the Sender should send S7F3. If the Receiver sends any other value in S7F2, it refuses the Grant, and the Sender should not send S7F3. The Process Program may be either a Load Recipe, Process Recipe, or Parameter Table.
4.2.84 S7F3 - Process Program Send S7F3 W * H<->E, Multiblock * PPID - Process Program ID * PPBODY – Process Program Body PPID is the recipe file name and should include the extension RCP. Send an Unformatted Process Program. Before sending a multi-block S7F3, the Equipment always first sends the S7F1/S7F2 Inquire/Grant transaction. The Host may send S7F1/S7F2 before sending S7F3. The Equipment accepts it, but does not require it. 4.2.
When the Host sends S7F4, the Equipment interprets ACKC7 as follows: Table 4-27 S7F4 ACKC7 Interpretations ACKC7 4.2.86 Description 0x00 Normal. Other Refusal. The upload operation fails. S7F5 - Process Program Request S7F5 W . * H<->E * Process Program ID PPID is the recipe file name and should include the extension RCP. Request the other end of the link to send a specified Process Program from its library. 4.2.
4.2.88 S7F17 - Process Program Delete S7F17 W * H->E ... > . * Process Program ID PPID is the recipe file name and should include the extension RCP. The Host deletes one or more Process Programs from the Equipment library. If S7F17 contains a zero-length List, the entire library is deleted. 4.2.89 S7F18 - Process Program Delete Acknowledge S7F18 . * H<-E * ACKC7 - Acknowledge Code The Equipment acknowledges the Process Program delete.
4.2.90 S7F19 - Process Program Directory Request S7F19 W . * H->E The PPIDs returned are the recipe file names and should include the extension RCP. The Host requests a directory of the Process Programs currently in the Equipment library. 4.2.91 S7F20 - Process Program Directory S7F20 * H<-E ... > . * Process Program ID The Equipment sends a directory of its Process Program library. If the library is empty, the list will be zero length. 4.2.
4.2.95 S9F7 Invalid Data S9F7 . 4.2.96 * H<-E * MHEAD - Header of bad msg S9F9 Transaction Timer Timeout S9F9 . 4.2.97 * H<-E * SHEAD - Stored Header S9F11 - Data Too Long S9F11 . 4.2.98 * H<-E * MHEAD - Header of bad msg S10F1 - Terminal Request S10F1 [W] * H<-E > . * Terminal ID * Message Text The Equipment sends text to the Host.
4.2.99 S10F2 - Terminal Request Acknowledge S10F2 . * H->E * Acknowledge Code The Host may send the following values for ACKC10: Table 4-30 S10F2 ACKC10 Values ACKC10 Description 0x00 Normal. Host accepts the S10F1. Other Host rejects the S10F1. 4.2.100 S10F3 - Terminal Display, Single S10F3 [W] * H->E > . * Terminal ID * Message Text The Host sends to the Equipment.
4.2.101 S10F4 - Terminal Display Single Acknowledge S10F4 . * H<-E * Acknowledge Code This Equipment may send the following values for ACKC10: Table 4-32 S10F4 ACKC10 Values ACKC10 0x00 Description Normal. 4.2.102 S10F5 - Terminal Display, Multiblock S10F5 [W] * H->E, Multiblock ... > > . * Terminal ID * Message Text S10F5 can contain multiple TEXT data items. Each TEXT data item is limited to 160 characters.
4.2.103 S10F6 - Terminal Display Multiblock Acknowledge S10F6 . * H<-E * Acknowledge Code This Equipment may send the following values for ACKC10: Table 4-34 S10F6 ACKC10 Values ACKC10 0x00 Description Normal. 4.2.104 S10F9 - Broadcast S10F9 [W] . * H->E * Message Text The Host sends text to the Equipment. The Equipment displays the text on its CRT. The Host may optionally set the W-Bit to “1” in S10F9. If so, the Equipment replies with S10F10. 4.2.
5 SECS Scenarios Unless otherwise noted in this section, the Communications State is “Communicating” and the Control state is either “On-Line/Local” or “On-Line/Remote”. 5.1 5.1.1 Equipment Communications Equipment Establishes Communications Assumption: Equipment’s Communication state is “Enabled/Not Communicating”. Table 5-1 SECS Messages Equipment Establishes Communications Step 1. SECS Message H <- E S1F13 W 2. 3. Description Equipment attempts to send Establish Communications Request.
5.1.2 Host Establishes Communications Assumption: Equipment’s Communication state is either “Enabled/Not Communicating” or “Enabled/Communicating”. Table 5-2 SECS Messages Host Establishes Communications Step SECS Message Description 1. H -> E S1F13 W Host sends Establish Communications Request. 2. H <- E S1F14 The Equipment responds with Establish Communications Acknowledge, with COMMACK set to zero. After this message is successfully sent, communications is established.
5.1.4 Losing Connection, Re-Connecting Table 5-4 SECS Messages Losing Connection, Re-Connecting Step SECS Message Description 1. H <- E SxFy Any Message. The Equipment encounters SECS block transmission errors while attempting to send a message to the Host., and reaches its Retry Limit (RTY). The Equipment considers the SECS link as disconnected. Spooling will become Active if enabled. 2. H <-E S1F13 W Connect Request. The Equipment attempts to re-establish the link. 3. 4. 5.1.
5.2 5.2.1 Data Collection Host Initializes Event Reporting Table 5-6 SECS Messages Host Initializes Event Reporting Step 1. SECS Message H -> E S2F37 W Description Disable Event Reports. The Host disables reporting for all Collection Events. S2F37 W > . 2. H <- E S2F38 The Equipment acknowledges. Temporarily, the Equipment will make no event reports. 3. H ->E S2F33 W Define Report. The Host erases all previous report definitions and links: S2F33 W > .
5.2.2 Equipment Reports Event Table 5-7 SECS Messages Equipment Reports Event Step SECS Message 1. Description The Equipment recognizes that an event has occurred. The Host has enabled reporting for the CEID, and possibly has defined one or more Reports and linked them to the CEID. The equipment constant “RpType” is set to “False”, requesting normal reports. 2. H <- E S6F5 W Inquire. If S6F13 will be multi-block, the Equipment first sends this Inquire to request permission.
5.2.4 Host Initiates Trace Table 5-9 SECS Messages Host Initiates Trace Step SECS Message 1. H -> E S2F23 W The Host initiates a trace. 2. H <- E S2F24 The Equipment acknowledges the trace request. If the data in S2F23 is not valid, the acknowledge code in this message is nonzero and the scenario ends. Otherwise, the following steps are done “TOTSMP” times, where TOTSMP is the total number of samples to be done. 3. Description The Equipment waits “DSPER” (data sample period).
5.2.6 Host Requests Status Table 5-11 SECS Messages Host Requests Status Step SECS Message Description 1. H -> E S1F3 W Discrete Variable Request. The Host requests the VIDs of interest. 2. H <- E S1F4 The Equipment sends the Variable values. 5.2.7 Host Defines Limits Table 5-12 SECS Messages Host Defines Limits Step SECS Message Description 1. H -> E S2F45 W Host defines new variable limits attributes. 2.
5.2.10 Host Requests Annotated Report by CEID Table 5-15 SECS Messages Host Requests Annotated Report by CEID Step SECS Message Description 1. H -> E S6F17 W Request Annotated Event Report. The Host requests a report for the specified CEID. In this way, the Host requests the Equipment to “pretend” that the specified CEID has occurred. 2. H <- E S6F18 The Equipment sends annotated reports linked to that CEID. 5.2.
5.2.13 Are You There Table 5-18 SECS Messages Are You There Step SECS Message Description 1. H -> E S1F1 W Are You There. The Host sends this simple message. 2. H <- E S1F2 The Equipment reports its MDLN and SOFTREV. 5.2.14 Host Reads Equipment Constants Table 5-19 SECS Messages Host Reads Equipment Constants Step SECS Message Description 1. H -> E S2F13 W Host requests the values of one or more equipment constants. 2.
5.3 Alarms 5.3.1 Equipment Reports Alarm Table 5-21 SECS Messages Equipment Reports Alarm Step SECS Message Description 1. H <- E S5F1 [W] If reporting for this alarm ID is disabled, skip this and the following step. Otherwise send the alarm. The equipment constant “WBitS5” determines whether the W-bit is “0” or “1” in this message. 2. H -> E S5F2 If the W-bit in S5F1 is 1, the Host acknowledges the alarm report. Otherwise, skip this step. 3.
5.3.4 Alarm Report (GEM, Ver 3.1 Compatibility) " NOTE This scenario is provided only for compatibility with Host computers which support GEM, Version 3.1. Table 5-24 SECS Messages Alarm Report (GEM, Ver 3.1 Compatibility) Step SECS Message 1. Description The equipment constant “ConfigAlarms” is set to 2 for nonGEM compatibility. The Equipment recognizes that an alarm condition has gone “on” (i.e. has become Unsafe). 2. H <- E S5F73 [W] The Equipment reports the Alarm going on.
5.3.5 Alarm Report (GEM, Ver 1.7 Compatibility) " NOTE This scenario is provided only for compatibility with Host computers which support GEM, Version 1.7. Table 5-25 SECS Messages Alarm Report (GEM, Ver 1.7 Compatibility) Step SECS Message 1. Description The equipment constant “ConfigAlarms” is set to 1 for GEM, Version 1.7 compatibility. The Equipment recognizes that an alarm condition has gone “on” (i.e. has become Unsafe). 2. H <- E S5F71 [W] The Equipment reports the Alarm going on.
5.4 5.4.1 Control State Host Sends On-Line Command Assumption: Control State is “Host Off-Line”. Variable GemControlState = 3. Table 5-26 SECS Messages Host Sends On-Line Command Step SECS Message Description 1. H -> E S1F17 W Host instructs the Equipment to go “On-Line”. 2. H <- E S1F18 Equipment responds to successful On-Line transition with ONLACK=0. Control state transits to either Local or Remote as guided by EC GemOnlineSubstate. 3. H <- E S6F11 W 4. H -> E S6F12 5.4.
5.4.3 Host Sends Remote Command Assumption: Control State is on-line and Remote. Table 5-28 SECS Messages Host Sends Remote Command Step SECS Message Description 1. H -> E S2F41 [W] The Host sends the command. The W-bit in this message bay be either 0 or 1. 2. H <- E S2F42 If the W-bit was 1, the Equipment acknowledges the command. If the Equipment cannot perform the command, the acknowledge code in this message is non-zero.
5.4.6 Go Local, Operator-Initiated Table 5-31 SECS Messages Go Local, Operator-Initiated Step SECS Message 1. Description ControlState is Remote. The Operator switches the Equipment to Local control state. 2. H <- E S6F11 W The Equipment signals CEID GemControlState LOCAL. Event Reports as appropriate. 3. H -> E S6F12 The Host acknowledges the report. 5.4.7 Go Local, Host-Initiated Table 5-32 SECS Messages Go Local, Host-Initiated Step SECS Message 1. Description ControlState is Remote. 2.
5.5 Process Program Management 5.5.1 Unformatted, Host-Initiated Download Table 5-34 SECS Messages Unformatted, Host-Initiated Download Step SECS Message Description 1. H -> E S7F1 W Host requests permission to send a multi-block Process Program to the Equipment. If the Process Program is singleblock, this step and the next one may be skipped. 2. H <- E S7F2 The Equipment grants permission for the Host to send the Process Program. 3.
5.5.3 Unformatted, Equipment-Initiated Download Table 5-36 SECS Messages Unformatted, Equipment-Initiated Download Step SECS Message Description 1. H <- E S7F5 W Equipment requests a Process Program. 2. H -> E S7F6 The Host sends the Process Program. If the Process Program is valid, the Equipment stores the Process Program in its library, and the scenario ends.
5.5.5 Host Deletes Process Program Table 5-38 SECS Messages Host Deletes Process Program Step SECS Message Description 1. H -> E S7F17 W Host sends a request to delete one or more Process Programs from the Equipment’s library of Process Programs. 2. H <- E S7F18 The Equipment replies with an acknowledge code. If all specified Process Program(s) were deleted successfully, the acknowledge code is 0.
5.6 Equipment Terminal Communications 5.6.1 Host to Equipment, Single Line Table 5-41 SECS Messages Host to Equipment, Single Line Step SECS Message 1. Description The Host has data to display at the Equipment’s front panel. 2. H -> E S10F3 [W] Terminal Display. The Host sends text. The Equipment displays the text on its front panel. 3. H <- E S10F4 If the W-bit in S10F3 is 1, the Equipment acknowledges. 4. The Operator acknowledges that he/she has read the message. 5.
5.6.3 Equipment Sends Text to Host Table 5-43 SECS Messages Equipment Sends Text to Host Step SECS Message 1. 5.7 Description The Operator enters data to send to the Host. 2. H <- E S10F1 [W] 3. H -> E S10F2 Equipment sends text to Host. The W-bit in this message may be either 0 or 1. The Host displays the message for the Operator. If the W-bit in S10F1 is 1, the Host acknowledges the text message. SECS Error Messages 5.7.
5.7.3 Unrecognized Function Table 5-46 SECS Messages Unrecognized Function Step SECS Message Description 1. H -> E SnFn [W] Host sends a primary message with a stream number for which the Equipment recognizes some messages, but with a function number that the Equipment does not support for that stream. The W-bit can be either 0 or 1. 2. H <- E S9F5 Equipment replies with “Unrecognized Function”. 5.7.4 Illegal Data Format Table 5-47 SECS Messages Illegal Data Format Step SECS Message 1.
5.8 Clock 5.8.1 Host Sets Date and Time Table 5-49 SECS Messages Host Sets Date and Time Step SECS Message Description 1. H -> E S2F31 W Date and Time Send. The Host sends a new Date and Time to the Equipment. 2. H <- E S2F32 The Equipment sets its Clock/Calendar hardware and acknowledges the command. 5.8.2 Host Requests Date and Time Table 5-50 SECS Messages Host Requests Date and Time Step SECS Message Description 1. H -> E S2F17 W Date and Time Request.
5.9 Spooling For all of the spooling scenarios, spooling is meaningful only when Control State (CONTROLSTATE = 4 or 5) is “On-Line”. When CONTROLSTATE is “Off-Line” (CONTROLSTATE = 1, 2, or 3), the Equipment sends only stream one primaries and SnF0 secondaries, neither of which are eligible for spooling. 5.9.1 Host Enables Spooling of Messages Table 5-52 SECS Messages Host Enables Spooling of Messages Step 1.
5.9.2 Messages Spooled and Transmitted Assumption: Spool State is “Spool Inactive”. Table 5-53 SECS Messages Spooled and Transmitted Step 1. SECS Message H <- E SnFn 2. Description Equipment attempts to send any message to the Host. After failure to deliver message, the Equipment assumes that the link is down, and will start to spool all messages marked for spooling. The first message spooled is the collection event “SpoolActivated”. 3. H <- E S1F13 W Equipment attempts to establish communications.
Table 5-53 SECS Messages Spooled and Transmitted Step SECS Message 11. H -> E S6F23 W The Host requests that the Equipment continue de-spooling messages. 12. H <- E S6F24 Equipment indicates that it will start to send spooled messages with return code RSDA = 0x00. Go to Step 10. 13. H <- E S6F11 W Equipment notifies the Host that sending of spooled messages has been completed by sending CEID GemSpooling Deactivated. 14.
6 Machine Variable Definitions The following data variables are collected by the Host to support intelligent communications with the Equipment: • Status Variables • Data Variables • Equipment Constants Each variable is given a header line with its associated ID value and its name. The storage type and the definition of the variable are listed below in smaller type. Variables listed in the header in capital letters are GEM standards. The others belong to Fluidmove.
Table 6-1 Status Variables (continued) Variable Name CLOCK ID 27 Storage Type A[16] Description The current value of the clock accurate to hundredths of a second. The format is: YYYYMMDDHHmmsscc. This format is always the same, regardless of TIMEFORMAT. CONTROLSTATE 28 U1 The value indicating the current Control State Machine state: 1 - OffLine/Equipment OffLine 2 - OffLine/Attempt OnLine 3 - OffLine/Host OffLine 4 - OnLine/Local 5 - OnLine/Remote DeviceID 115 A[12] The SECS Device ID.
Table 6-1 Status Variables (continued) Variable Name ID Storage Type Description PREVIOUSPROCESSSTATE 36 U1 The previous Process State for the Equipment. The values for this state can be found in Appendix A. PROCESSSTATE 37 U1 The current Process State for the Equipment. The values for this state can be found in Appendix A. ProductionStartTime 105 A[14] RunMode 110 U1 The specific type of runtime operation being conducted; dry run, production run, pass-through, or prototype test run.
6.2 Data Variables Table 6-2 Data Variables Variable Name ID Storage Type Description ALARMTEXT 1000 A[0..40] The Alarm Text ( ALTX ) for the most recent alarm transition. ALARMSEVERITYCODE 1001 B[1] The Severity Code (the low order seven bits) of the most recent alarm transition. BarcodeRaw 350 A[30] The barcode string exactly as it is read by the scanner from the barcode tag on the board at the dispense station.
Table 6-2 Data Variables (continued) Variable Name DWVDISPENSES ID Storage Type Description 411 U4 Dispense Weight Verification: number of dispenses that will be performed. Valid only after collection event “DispenseWeightComplete” occurs. DWVTARGETRANGE 412 F8 Dispense Weight Verification Target Range: If range limit checking is enabled, this variable will contain the maximum allowable range for the dispense weight verification routine.
Table 6-2 Data Variables (continued) Variable Name DWVMEASUREDAVG ID Storage Type 416 F8 Description Dispense Weight Verification Average: average weight of all dispenses after the dispense weight verification completes or “-1” if the routine fails or is interrupted before it completes. Valid only after collection event “DispenseWeightComplete” occurs. ECIDCHANGE 46 U4 FluidState1 306 A[10] The ID of the last event to be reported to the Host.
Table 6-2 Data Variables (continued) Variable Name ID Storage Type Description NumFailedBoards 107 U4 PPCHANGENAME 40 A[0..8] PPCHANGESTATUS 41 U1 The last action performed on the Process Program. 1 - Created 2 - Changed 3 - Deleted ScaleMeasurement1 406 F8 The actual value read from the scale during a Flow Rate Verification Procedure when Valve 1 is being used.
6.3 Equipment Constants Table 6-3 Equipment Constants Variable Name BOARDFREQUENCY ID Storage Type 610 U4 Description This value is set by the station controller to the board frequency it requires collection event 2010 to occur. The default is zero which prevents collection event 2010 from triggering. CONFIGALARMS 1 U1 This EC determines the type of alarm message which is sent following an alarm. 0 – S5F1, 1 – S5F71, 2 – S5F73.
Table 6-3 Equipment Constants (continued) Variable Name ID Storage Type Description 46 U4 This is the largest number of messages that may be read from the Spool file during a single read. This limits the number of messages sent to the Host in response to the S6F23 message and helps to prevent clogging of the communications link during a link recovery after a long communications failure.
Table 6-3 Equipment Constants (continued) Variable Name ID Storage Type Description WBITS10 18 U1 This variable determines the default state of the W bit for all messages in stream 10 sent from the Equipment to the Host. WBITS5 19 U1 This variable determines the default state of the W bit for all messages in stream 5 sent from the Equipment to the Host. WBITS6 20 U1 This variable determines the default state of the W bit for all messages in stream 6 sent from the Equipment to the Host.
7 Host-to-Equipment Messages " NOTE In Table 7-1 “Primary” and “Reply” columns: * = Fluidmove secondary message handlers ** = Fluidmove primary message handlers Table 7-1 Host-to-Equipment Messages Primary Reply Cstate S1F1 S1F2 4,5 Are You There None S1F3 S1F4 4,5 Selected Status Possible variable access S1F11 S1F12 4,5 Status Variable Namelist Request None S1F13 S1F14 All Connect Request None S1F15 S1F16* 4,5 Request Off-Line None S1F17 S1F18* 1,2,3 Request On-Line Non
Table 7-1 Host-to-Equipment Messages (continued) 7-2 Primary Reply Cstate Description Notes S2F31 S2F32 4,5 Date and Time Send None S2F33 S2F34 4,5 Define Report None Disk write occurs. S2F35 S2F36 4,5 Link Event Report None Disk write occurs. S2F37 S2F38 4,5 Enable/Disable Event Report None. Disk write occurs.
Table 7-1 Host-to-Equipment Messages (continued) Primary Reply Cstate Description Notes S7F3 S7F4 4,5 Unformatted Process Program Send UFPP verify Disk write occurs. S7F5** S7F6* 4,5 Unformatted Process Program Request None Disk read occurs. S7F17** S7F18 4,5 Process Program Delete None Disk write occurs. S7F19 S7F20* 4,5 Process Program Directory None Disk read occurs.
8 Equipment-to-Host Messages " NOTE In Table 8-1 “Reply” column: * = Fluidmove secondary message handlers Table 8-1 Equipment-to-Host Messages Primary Reply Description -- (any) SnF0 Primary rejected while Off-Line None S1F1 S1F2 Are You There None (heartbeat) GemGoAOnline (Attempt Online) S1F13 S1F14 Connect Request None S1F65 S1F66 Connect Request None N S2F17 S2F18 Date and Time Request GemHostTimeReq S5F1 S5F2* Alarm Report GemNoteAlarmEvent N S5F71 S5F72 Alarm Report B
Table 8-1 Equipment-to-Host Messages (continued) Primary Reply S6F13 S6F14 Annotated Event Report Send GemNoteEvent Possible variable access routines. N S7F1 S7F2 Process Program Inquire/Grant GemUFPPSend or GEMFPPSend S7F3 S7F4* Unformatted Process Program Send GemUFPPSend Disk Read occurs S7F5 S7F6 Unformatted Process Program Request GemUFPPLoad UFPPVerify Disk write occurs.
Appendix A – Data Dictionary Variables Table A-1 is a summary explanation of the machine variables described in Section 6 sorted by ID number and containing details of the content of each variable. The data formats are as follows: A[nn] ASCII text of length nn. Where two numbers are indicated, they specify a range of acceptable lengths. Bool A boolean flag indicating TRUE or FALSE. F4,F8 A floating point number in four bytes. I1,I2,I4,I8 Signed integers of the indicated length in bytes.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description INITCONTROLSTATE. Initial (power-up) control super-state. 9 EC U1 10 EC U2 17 18 19 EC EC EC BOOL U1 U1 1 = Off-Line 2 = On-Line HEARTBEAT. The time in seconds that the Equipment will delay before sending S1F1 to test the link. Units are seconds. Valid values are 0-3200 (a setting of zero will disable the heartbeat). RPTYPE.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description 26 SV U4 ALARMSERIAL. The sequence number of the most recent alarm change (going on or going off). This number starts at zero at power-up and increments by one for each alarm transition which occurs. CLOCK. The Equipment's current Date and Time in the following format: YYYYMMDDhhmmsscc.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description PREVIOUSPROCESSSTATE. The Process State in effect before the most recent transition to the current Process State. 0 = Idle (Boot-up) 1 = Idle 36 SV U1 2 = Running 3 = Paused 4 = Aborting 5 = Error PROCESSSTATE. The current Process State. 0 = Idle (Boot-up) 1 = Idle 37 SV U1 2 = Running 3 = Paused 4 = Aborting 5 = Error 38 SV A[6] SOFTREV. Software revision number with Major and minor parts. Example: "1.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description ONLINEFAILED. The default Control State transition when Attempt OnLine fails. 43 EC U1 1 = Equipment Off-Line 2 = Host Off-Line ONLINESUBSTATE. The default (power-up) online substate of the Control State Model. 44 EC U1 4 = Local 5 = Remote 46 EC U4 MAXSPOOLTRANSMIT. The maximum number of spooled messages the equipment will send each time the Host reads the spool.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description 57 DV U4 GEMLIMITSVID. Contains the VID of the variable whose value crossed defined limits. 60 EC U2 GEMLIMITSDELAY. Determines how often the Equipment checks if variables are within the defined limits (seconds). 61 EC BOOL Internal to the Equipment. The Host should not access this variable. OVERWRITESPOOL. This EC determines the action to be taken by the Equipment when the Spool file reaches its capacity.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description ProductionStartTime. The time stamp when production started. The format is: YYYYMMDDhhmmss. Similar to the TIME(39) variable format. YYYY = year from 0000 to 9999 MM = month from 01 to 12 105 SV A[14] DD = day from 01 to 31 hh = hours from 00 to 59 mm = minutes from 00 to 59 ss 106 SV U4 107 DV U4 = seconds from 00 to 59 BoardCount.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description FluidThawTime1. This is the time stamp in the YYYYMMDDhhmmss format, at which the fluid was removed from the refrigerator and began to warm up. Similar to the TIME(39) variable format. YYYY = year from 0000 to 9999 302 SV A[14] MM = month from 01 to 12 DD = day from 01 to 31 hh = hours from 00 to 59 mm = minutes from 00 to 59 ss = seconds from 00 to 59 303 SV A[12] FluidFileName2.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description 404 DV F8 FlowRateMin2. The minimum flow rate for Valve 2 in mg./sec. allowed during this run. 405 DV F8 FlowRateMax2.The maximum flow rate for Valve 2 in mg./sec. allowed during this run. 406 DV F8 ScaleMeasurement1. The actual value read from the scale during a Dispense Weight Verification Procedure when Valve 1 is being used. 407 DV F8 ScaleMeasurement2.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description DWVTARGETMAXLIMIT. Maximum allowable deviation from the target weight of the dispense weight for the Dispense Weight Verification routine. 414 DV F8 Note: If the verification routine fails and the failed weight is required, the data variable “SCALEMEASUREMENT1” (if valve 1) or “SCALEMEASUREMENT2” (if valve 2) will have the last value read from the scale.
Table A-1 Data Dictionary Variables (continued) VID Class Format Name and Description TEMPHTR1CHAN1 – TEMPHTR1CHAN17. Heater 1 temperatures for channels 1-17 respectively (DV 801 = channel 1, DV 802 = channel 2, etc.). 801 to 817 DV F8 The units are in degrees. No other information is supplied such as the unit of degrees (°C or °F) or what device the channel is mapped to (i.e., pre-dispense station, needle heater, etc.).
Appendix B – Collection Events Table B-1 lists the collection events that exist at the Equipment. Table B-1 CEID CEID Name Description Note: CEID 1 – 65 are standard GEM 1 ControlStateChange Event is triggered when there is a change in control state. 2 ProcessStateChange Event is triggered when there is a change in process state. 3 GemPPChangeEvent Event is triggered when the Operator creates, changes, or deletes a process program.
Table B-1 CEID (continued) CEID Name Description Board Handling 2001 BoardAtDispenseLoc1 The board is at the dispensing location for Conveyor 1 and ready for dispensing. 2002 DispensingDone1 Dispensing is completed for Conveyor 1. The board is ready to leave the dispensing location. 2003 BoardAtDispenseLoc2 The board is at the dispensing location for Conveyor 2 and ready for dispensing. 2004 DispensingDone2 Dispensing is completed for Conveyor 2.
Table B-1 CEID (continued) CEID Name Description Setup 4001 PromptedSetupStarted An operator has initiated the Prompted Setup process. 4002 PromptedSetupCompleted The Prompted Setup Process is completed. 4003 FindNeedleXYZ An automatic needle XYZ calibration has been performed. 4004 ManualMeasureFlowRate1 A flow rate measurement for Valve 1 has been initiated by an operator. 4005 ManualPurgeNeedle1 A needle purging of Valve 1 has been initiated by an operator.
Table B-1 CEID (continued) CEID Name Description Run Time 5001 HeaterMonitorTimeout The heaters at the dispensing location failed to reach the specified temperature range within the timeout period. 5002 HeaterMonitorSkipped The Operator has selected to skip the temperature monitoring and proceed to dispensing. 5003 HeaterMonitorAborted The Operator has selected to abort the temperature monitoring and aborted the run.
Appendix C – Alarms Since the number of alarms that Fluidmove reports to SECS/GEM is constantly growing, each individual alarm will not be listed here. The alarm section of the GWGEM GCD file is automatically generated from the Fluidmove source code using a custom software tool. Use the SECS/GEM message S5F5 to retrieve a list of all alarms currently reported by your version of Fluidmove. The format for each alarm is described below: ALID Alarm ID.
Glossary Alarm An alarm is related to any abnormal situation on the Equipment that may endanger people, Equipment, or material being processed. GEM allows the Host to be notified when alarm conditions are detected and cleared. ALID Equipment Alarm ID CEID Collection Event ID Collection Event A collection event is a detectable occurrence significant to the Equipment that is considered to be significant to the Host. GEM allows the Host to be notified when a collection event occurs.
HSMS-GS High Speed Message Service-General Session. This standard defines TCP/IP network communication used by GEM for Host/Equipment communication. It is intended to be applied for complex systems containing multiple independently accessible subsystems and uses an extended state machine. HSMS-SS High Speed Message Service-Single Session. This standard defines TCP/IP network communication used by GEM for Host/Equipment communication. It replaces the SECS-I standard. ID Identifier or Identification.
