semi合集-English.pdf - 第3044页

SEMI E122-0703 © SEMI 2003 25 15.9 Collection Plan Activation — The collection plan is comm unicated to equipment as param eters to the START remote command, with one parameter specifying the Dataset, TestTypeData and Te…

SEMI E122-0703 © SEMI 2003 24

DatalogPlan

-TestType : Integer

-TestStatus : Integer

TestTypeData

-TestID : Integer

-TestStatus : Integer

TestStepData

-Name : String

DataSet

-SiteID : Integer

TestSite

-ReportID : Integer

TestReport

-dataSets 0..*

-enabledTestTypes

0..*

-enabledTestSteps0..*

-attachedReport

-testSites

0..*

Figure 2

Datalog Plan

15.7.1 Datalog Plan — The plan specifies what

TestTypes, test steps are enabled for data collection and

describes the data to be collected. It also specifies a

way to group the data into data sets based on test-site.

15.7.2 Dataset — The Dataset defines a grouping of

data based on test-site of unit data. One or more test-

sites may be specified for each dataset. If no test-site is

specified, all test-sites is assumed. Each Dataset is

associated with a name.

15.7.3 TestSite — TestSite specifies the processing

test-site of the unit where test data was produced.

15.7.4 TestTypeData — TestTypeData defines the data

to be collected for a particular TestType (functional,

parametric etc) via an attached data report definition.

15.7.4.1 TestType — Specifies the type of test for

which to collect data on via the attached report

definition.

15.7.4.2 TestStatus — Specifies the pass/fail status of

test for which data will be communicated to host.

15.7.5 TestStepData — TestStepData defines the data

to be collected for a particular test via an attached data

report definition. TestID specifies the ID of the test as

provided by the TEST-LIST report, and TestStatus

specifies pass/fail condition for which data will be

communicated to host.

15.7.6 TestReport — TestReport defines the structured

format and the data variables to communicate to host.

The ReportID uniquely identifies the report defined in

the equipment.

15.8 Test Data Reporting — Test data reporting is

enabled by specifying a DATALOG-PLAN parameter

in the START command or by defining an unnamed

datalog plan in the STARTcommand using the

DATALOG-DATASETS, DATALOG-BY-

TESTTYPE, DATALOG-BY-TESTID, and

DATALOG-OPTIONS parameters. If no datalog plan

is specified in the START command, the last supplied

datalog plan is used. Initially (after a PP-SELECT), all

test data reporting will be disabled (using datalog plan

“NONE”). The unnamed plan defined in the START

command will be undefined as soon as another datalog

plan is activated.

15.8.1 Sample test data reporting can be done by

setting the DATALOG-PLAN to “NONE” and then,

every once in a while, setting it to another datalog plan

that generates the desired reports.

15.8.2 If limited test data reporting is desired at all

times, but full test data reporting is required on a

sample basis, two datalog plans can be defined and each

START command can indicate the appropriate datalog

plan.

SEMI E122-0703 © SEMI 2003 25

15.9 Collection Plan Activation — The collection plan is communicated to equipment as parameters to the START

remote command, with one parameter specifying the Dataset, TestTypeData and TestStepData definitions

respectively. An additional parameter is also included to globally enable or disable all test data collection for

process program. The parameters are DATALOG-DATASETS, DATALOG-BY-TESTTYPE, DATALOG-BY-

TESTID, and DATALOG-OPTIONS. Please see START remote command parameters in Table 8 for format

details.

15.10 Test Data Acquisition — This section specifies an interface to allow transfer of data sets from equipment to

host. It defines at a conceptual level the messaging services, and does not define the actual messaging protocol.

Information on structure of the message, how data is represented, or how the message is exchanged will be defined

in a separate document, which maps the services to a specific protocol (such as SECS-II).

15.10.1 Test Data Transfer Communications — The required messages and the exchange sequence for a normal

transfer of data sets between two systems are presented below in Figure 3.

Host

Equipment

OPEN(DSName:String, Handle:Integer)

READ(Handle:Integer, MaxLen:Integer)

CLOSE(Handle:Integer)

SEND(DSName:String)

READ DATA REPLY(Handle:Integer, Data:<unspecified>)

Data Available

Indication

Open Data Set

for Transfer

Data

Transfer

Data Set

Figure 3

Test Data Transfer Message Flow

15.10.1.1 SEND — Used by equipment to indicate to host that data is available for a data set and request host

system to read it. The data set is identified by its name in the argument.

15.10.1.2 OPEN — Host requests that a certain data set be opened for transfer. A handle is provided unique to this

session to be used in subsequent transfer requests.

15.10.1.3 READ — Host requests data be transferred for an open data set, identified by the handle. A max length is

provided to indicate to equipment the maximum byte length of the data to be sent.

15.10.1.4 READ DATA REPLY — Equipment reply to a READ request. A block of data no bigger than the max

length specified in the READ request is attached to the reply message. Handle identifies the open data set of the

sent data.

15.10.1.5 CLOSE — Closes a data transfer session and frees the handle.

15.10.1.6 RESET — Closes all open data sets.

15.10.2 Synchronization — In order to synchronize the two systems during recovery situations, a RESET message

is defined that can be used by either Host or Equipment to unconditionally close all open data sets.

15.10.3 This specification must be used in conjunction with a protocol mapping specification in order to get a full

definition of the test data acquisition interface.

NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for any

particular application. The determination of the suitability of the standard is solely the responsibility of the user.

Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant

literature, respecting any materials or equipment mentioned herein. These standards are subject to change without

notice.

By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position

respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this

standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and

the risk of infringement of such rights are entirely their own responsibility.

International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o

the contents in whole or in part is forbidden without express written

consent of SEMI.