00191134-03.pdf - 第11页

GEM for SIPLACE V5.01 ©Siemens AG, all rights r eserved page 11 of 252 operations with a Host Com puter. T he SIPLACE com plies to the following GEM docum ent: 1. E30-1994  *(0 &RPSOLDQFH This section c larifies…

GEM for SIPLACE V5.01

Changes from Host Interface Manual V3.02:

•

Definition of Data Item 'CompLeft2Place' corrected

The SEMI Equipment Communication Standard (SECS) is published by Semiconductor

Equipment and Materials International (SEMI). It defines a computer to computer

communications interface between a unit of factory Equipment and a Host Computer.

This Equipment complies to the SECS-II standard, all SECS-II message used in GEM are

implemented. The SIPLACE complies to the following versions of standards:

E5-1994 (SECS-II)

SEMI Document #2758, Line 1 Item #1 (The Year 2000 issue)

 6(&6,,&ODULILFDWLRQV

SIPLACE GEM is Year 2000 compliant according to the new Year 2000 SECS-II Standard

(SEMI Document #2758, Line 1 Item #1).

The SIPLACE uses the following SECS-II conventions:

 'DWD)RUPDW7\SHV

Where the Standards permit a choice of data item types, the choice has been made as

described in section „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.

We recommend the Host attempt to use the formats shown.

 'DWD,WHP/HQJWK%\WHV

For messages sent by the Equipment, the number of length bytes in Data Items is always

the minimum required to contain the Data Item length.

For messages received from the Host, the number of length bytes in Data Items can be 1,

2, or 3, provided that the length parameter can accurately be specified.

 $6&,,'DWD

Unless otherwise specified, all ASCII data items must contain printable ASCII data—that

is, characters in the range 0x20 to 0x7E.

 0XOWL%ORFN0 HVVDJHV

Wherever the Host is supposed to send a single-block message, this Equipment will also

accept multi-block format.

The maximum size for a single SECS message is approximately 1000 blocks (256,000

bytes).

 )XQFWLRQ=HUR

The Equipment sends a Reply Message using Function zero (F0) according to the

requirements of the GEM Control State.

Wherever this Equipment expects a Reply message from the Host, the Host can send F0.

The Equipment will instantly abort the outstanding transaction. The Equipment will not

take any additional action.

 *(0 6WDQGDUG

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

GEM for SIPLACE V5.01

operations with a Host Computer. The SIPLACE complies to the following GEM

document:

1. E30-1994

 *(0 &RPSOLDQFH

This section clarifies which GEM functions are implemented in this Equipment. See

„GEM Compliance Statement“ on page 12.

The SIPLACE never sends S2F25 (Loopback Diagnostic) to the Host. It will send the

appropriate S2F26 in response to an S2F25 from the Host.

The SIPLACE never sends S9F13 (Conversation Timeout) to the Host. The Equipment

can be defined as having an „infinite timeout“ for conversations.

The SIPLACE never sends S10F7 (Multi-Block Not Allowed) to the Host. It will accept

incoming messages consisting of printable characters and a maximum size of 320

characters.

The SIPLACE will accept, but does not require the Inquire/Grant transaction

(S2F39/S2F40, S6F5/S6F6, S7F1/S7F2) for incoming primary multi-block messages.

GEM for SIPLACE V5.01

1.4 *(0 &RPSOLDQFH6WDWHPHQW

GEM COMPLIANCE STATEMENT

FUNDAMENTAL GEM REQUIREMENTS IMPLEMENTED

COMPLIANT

State Models ✓Yes ¨ No

Equipment Processing States ✓ Yes ¨ No ✓ Yes

S1,F13/F14 Scenario ✓ Yes ¨ No

Event Notification ✓ Yes ¨ No

On-line Identification ✓ Yes ¨ No

Error Messages ✓ Yes ¨ No ¨ No

Control (Operator Initiated) ✓ Yes ¨ No

Documentation ✓ Yes ¨ No

ADDITIONAL CAPABILITIES IMPLEMENTED COMPLIANT

Establish Communications ✓ Yes ¨ No ✓ Yes ¨ No

Dynamic Event Report Configuration ✓ Yes ¨ No ✓ Yes ¨ No

Variable Data Collection ✓ Yes ¨ No ✓ Yes ¨ No

Trace Data Collection ✓ Yes ¨ No ✓ Yes ¨ No

Status Data Collection ✓ Yes ¨ No ✓ Yes ¨ No

Alarm Management ✓ Yes ¨ No ✓ Yes ¨ No

Remote Control ✓ Yes ¨ No ✓ Yes ¨ No

Equipment Constants ✓ Yes ¨ No ✓ Yes ¨ No

Process Program Management * ✓ Yes ¨ No ✓ Yes ¨ No

Material Movement ✓ Yes ¨ No ✓ Yes ¨ No

Equipment Terminal Services ✓ Yes ¨ No ✓ Yes ¨ No

Clock ✓ Yes ¨ No ✓ Yes ¨ No

Limits Monitoring ✓ Yes ¨ No ✓ Yes ¨ No

Spooling ✓ Yes ¨ No ✓ Yes ¨ No

Control (Host Initiated) ✓ Yes ¨ No ✓ Yes ¨ No

* is only possible to have one program on the SIPLACE (the GEM standard requires

three)

 7HUPLQRORJ\

The following terms are used throughout the document to refer to the various entities

interfacing with the SIPLACE: