semi合集-English.pdf - 第2204页

SEMI E54.##-0705 © SEMI 2005 3 5.3.4 Device Profile — a kind of electric table to provide the ch aracteris tic features of a device including configuration and cap abilities. 5.3.5 Service Access Element — an addressable…

100%1 / 7923
SEMI E54.##-0705 © SEMI 2005 2
4.3 A-LINK Documents
1
A-LINK Public Specification ver. 1.2 — Basic Reference Model for Open Systems Interconnection
NOTICE: Unless otherwise indicated, all documents cited shall be the latest published versions.
5 Terminology
5.1 Abbreviations and Acronyms
5.1.1 AUF — A-LINK User Forum
5.1.2 CDM — Common Device Model
5.1.3 NCS — Network Communication Standard
5.1.4 OSI — Basic Reference Model for Open Systems Interconnection (ISO 7498)
5.1.5 PHY — Physical Layer
5.1.6 SAN — Sensor/Actuator Network
5.1.7 SDM — Specific Device Model
5.1.8 UI — User Interface
5.2 This section includes the terms defined in SEMI E54.1 Sensor/Actuator Network Common Device Model.
5.2.1 Attribute
5.2.2 Behavior
5.2.3 Byte
5.2.4 Class
5.2.5 Common Device Model
5.2.6 Device
5.2.7 Device Manager (DM) Object
5.2.8 Device Model
5.2.9 Instance
5.2.10 Network Communication Standard
5.2.11 Object
5.2.12 Sensor, Actuator and Controller (SAC) Object
5.2.13 Service
5.2.14 Specific Device Model
5.2.15 state diagram
5.3 Terminology Defined in A-LINK
5.3.1 AUF — A-LINK User Forum.
1
A kind of consortium for A-LINK users to recommend improvement to A-
LINK trade organization
2
, share A-LINK applications, provide A-LINK compliance test and etc.
5.3.2 AN MS — a station that accesses and exchanges data by polling its assigned Networked-Slave stations.
5.3.3 AN SS — a station that is managed and accessed by AN MS.
1 http://www.a-linkuf.com
2 http://www.algosystem.co.jp
SEMI E54.##-0705 © SEMI 2005 3
5.3.4 Device Profile — a kind of electric table to provide the characteristic features of a device including
configuration and capabilities.
5.3.5 Service Access Element — an addressable location in a device for the directing of service requests.
5.3.6 Data Exchange — a capability to communicate such data for a device as raw/processed sensed data and
variable settings.
5.3.7 Directive — a capability to instruct such basic functions to a device as reset or abort.
5.3.8 DP Facility — a capability to manage diagnostic matters.
5.3.9 Unite Inventory — a capability to realize and communicate the Device Profile.
5.3.10 Unite States — a capability to communicate state of a device.
6 Communication Protocol High Level Structure
6.1 In a typical remote I/O configuration, single master architectures are used to optimize response times. In
complicated applications, multi-master architectures are also possible. A-LINK uses the polling principle for
communication.
6.1.1 Message transfer is organized in cycles. A message cycle mainly consists of a request-frame followed by a
corresponding acknowledge/response-frame of the addressed station. An exception to this is the global-control
function for synchronization and coordination of several remote I/O stations.
6.1.2 A brief description of the A-LINK protocol as it relates to the ISO 7498 OSI model follows in the sections
below. For protocol efficiency, A-LINK does not define layers 3 to 7. However, since the OSI model specifies
Layer 7 as the interface between the Application Process and the communication stack, it is appropriate to discuss
several aspects of the A-LINK standard at this level.
NOTE 1: The information contained in this section is for reference only. It in no way represents specifications for A-LINK. See
related documentation for these specifications.
6.2 Physical Layer — Layer 1
6.2.1 The bottom Physical Layer is established by RS-485. See the A-LINK standard for more information for
detail.
6.3 Data Link Layer — Layer 2
6.3.1 Data Transfer
6.3.1.1 The Data Link Layer provides the functions for sending and receiving data over the network. Data Elements
are packaged, delivered, and checked. Acknowledgements, responses, retries, and timeouts are used to guard
against Line Protocol Errors (e.g., frame, overrun, and parity) and Transmission Protocol Errors (e.g., start and end
delimiters, frame check, frame length, and response times).
6.4 Network Layer — Layer 3
6.4.1 There is no distinct network layer.
6.5 Transport Layer — Layer 4
6.5.1 There is no distinct transport layer. Such functions as disassembling of message into transport unit and
reassembling for transportation are implemented in the Application Layer.
6.6 Session Layer — Layer 5
6.6.1 There is no distinct session layer.
6.7 Presentation Layer — Layer 6
6.7.1 There is no distinct presentation layer. Such functions as data representation conformance are implemented in
the Application Layer.
6.8 Application Layer — Layer 7
SEMI E54.##-0705 © SEMI 2005 4
6.8.1 The Device shall comply with A-LINK application layer specification for defining and addressing objects
including functions deferred in lower layers as described above.
6.8.2 User Interface (UI)
6.8.2.1 The UI provides the user with access to functionality of the A-LINK protocol as a part of application layer.
7 Required Object Types
7.1 This section describes a general mapping of the SEMI SAN Object Model to the A-LINK environment.
Component definitions are clarified and the mapping of Attributes, Services, and Behaviors are specified.
7.2 Object Model
7.2.1 The Object Model defined in the CDM is represented in the A-LINK NCS. Especially the DM, SAC, and
abstract or fundamental application objects are mapped.
7.2.2 The Application Objects associated with the SDM standards are mapped in A-LINK User Forum Public
Specification documents. §9 specifies the mapping of SDM Objects in A-LINK.
7.3 Component Mapping Summary
7.3.1 Table 1 provides a summary of the components of the CDM object model as they relate to the components of
A-LINK.
7.4 Objects
7.4.1 The required objects of the CDM are identified here. Additional objects that are contained in the SDM are
given identifiers in the Device Profile. §9 specifies additional mapping information.
7.4.2 Table 1 lists the Object Identifiers specified for use in protocol messages.
Table 1 Object Identifiers
Object Name A-LINK Class/Object ID CDM Object ID Tag CDM Attribute/Service ID Tag Prefix
Device Manager 1 DmI0 Dm
SAC 2 SacI0 Sac
Assembly 3 AsmIn Asm
Local Link 4 LnkIn Lnk
Sensor–AI 9 SenIn Sai
Sensor–EI 10 SenIn Sei
Sensor–BI 11 SenIn Sbi
Sensor–BI–TH 12 SenIn Sbith
Actuator–AO 17 ActIn Aao
Actuator–EO 18 ActIn Aeo
Actuator–BO 19 ActIn Abo
Controller 24 CntIn C
Application Objects >31 - -
7.5 Attributes
7.5.1 All attributes are accessible via Get_Attribute and Set_Attribute services defined in the sections below.
Attributes are also accessible via different A-LINK peculiar instructions which are additionally mapped in this
document based on attribute type.
7.5.1.1 The attributes of the DM object consists of distinctive information, states, and setups. Distinctive
information attributes are retrieved with the Unite Inventory. Inquiring state attributes are provided by getting status
data. Setup attributes are written by setting configuration data.