00193786-01 - 第12页

SIPLACE GEM SW Version GEM 505.01 HOST Interface Manual Page 12 of 236 ©Siemens AG, all rights reserved For messages received from the Host, the num ber of length bytes in Data Items can be 1, 2, or 3, provided that the …

SIPLACE GEM SW Version GEM 505.01

HOST Interface Manual

VID 2412003 PLACEINFO4

VID 2412004 PICKUPINFO4

VID 2412006 VACUUMDATA4

VID 2412007 SEGMENTINFO4

VID 2412008 PLACEINFO4SUB1

• Section 6: Variables:

2012041 – 2012044 (PickUpDataResetPointLocX) will be updated when „Pick-Up Error“

data item (PickUpErrorsLocX was reset.

1.3 Changes from Host Interface Manual V504.01

A significant change since Gem 504.01 is support for the new SIPLACE HF/3 machine.

This machine is available with a 12-nozzle or 6-nozzle revolver head or with a TwinHead.

• Section 4.2: Data Item Dictonary :

New values für PickUpResult, PlacementResult and ErrorCode added.

• Section 6: Variables :

New variables for PCB barcodes added:

VID 912021 PCBBCProc1Conv1

VID 912022 PCBBCProc1Conv2

VID 912023 PCBBCProc2Conv1

VID 912024 PCBBCProc2Conv2

• Corrections:

Report 29 PlaceError corrected

1.4 SECS-II Clarifications

The SIPLACE uses the following SECS-II conventions:

1.4.1 Data Format Types

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.

1.4.2 Data Item Length Bytes

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.

SIPLACE GEM SW Version GEM 505.01 HOST Interface Manual

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.

1.4.3 ASCII Data

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

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

1.4.4 Multi-Block Messages

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).

1.4.5 Function Zero

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.

1.5 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 SIPLACE complies to the following GEM

document:

1. E30-1994

1.6 GEM Compliance

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

„GEM Compliance Statement“ on page 13.

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.

SIPLACE GEM SW Version GEM 505.01

HOST Interface Manual

1.7 GEM Compliance Statement

GEM COMPLIANCE STATEMENT

FUNDAMENTAL GEM REQUIREMENTS IMPLEMENTED

COMPLIANT

State Models

✓Yes ✓ Yes

Equipment Processing States

✓ Yes ✓ Yes

S1,F13/F14 Scenario

✓ Yes ✓ Yes

Event Notification

✓ Yes ✓ Yes

On-line Identification

✓ Yes ✓ Yes

Error Messages

✓ Yes ✓ Yes

Control (Operator Initiated)

✓ Yes ✓ Yes

Documentation

✓ Yes ✓ Yes

ADDITIONAL CAPABILITIES IMPLEMENTED COMPLIANT

Establish Communications

✓ Yes ✓ Yes

Dynamic Event Report Configuration

✓ Yes ✓ Yes

Variable Data Collection

✓ Yes ✓ Yes

Trace Data Collection

✓ Yes ✓ Yes

Status Data Collection

✓ Yes ✓ Yes

Alarm Management

✓ Yes ✓ Yes

Remote Control (1)

✓ Yes

¨ No

Equipment Constants

✓ Yes ✓ Yes

Process Program Management (2) ¨ No ¨ No

Material Movement

✓ Yes ✓ Yes

Equipment Terminal Services

✓ Yes ✓ Yes

Clock

✓ Yes ✓ Yes

Limits Monitoring

✓ Yes ✓ Yes

Spooling

✓ Yes ✓ Yes

Control (Host Initiated)

✓ Yes ✓ Yes

(1) : Remote commands, only Start and Stop are available in this stage.

(2) : Process Program Management is not implemented until a later stage.

1.8 Terminology

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

interfacing with the SIPLACE: