Спецификация протокола Profibus

Page 141

PROFIBUS-Specification-Normative-Parts-5:1997

4 Fieldbus Message Specification (FMS) ...............................169

4.1 Service Model ......................................................169

4.1.1 Short Description of Services ......................................169

4.1.1.1 Marginal Conditions for the Services ...............................172

4.1.1.2 Client and Server ..................................................172

4.1.2 Short Description of Objects .......................................174

4.1.2.1 Access Rights ......................................................175

4.1.2.2 Domain Restrictions of Objects .....................................178

4.1.2.3 Creation and Deletion of Objects ...................................178

4.1.3 Addressing of Objects ..............................................178

4.1.3.1 Logical Addressing .................................................178

4.1.3.2 Physical Addressing ................................................178

4.1.3.3 Implicit Addressing ................................................179

4.1.3.4 Named Address ......................................................179

4.1.4 Assignment of Services to Master / Slave and to Objects ............179

4.1.5 Data Types .........................................................182

4.2 VFD Support ........................................................183

4.2.1 Model Description ..................................................183

4.2.2 The VFD Object .....................................................184

4.2.2.1 Attributes .........................................................185

4.2.3 VFD Support Services ...............................................186

4.2.3.1 Status .............................................................186

4.2.3.2 UnsolicitedStatus ..................................................187

4.2.3.3 Identify ...........................................................187

4.3 Object Dictionary (OD) Management ..................................188

4.3.1 Model Description ..................................................188

4.3.2 Structure of an OD .................................................190

4.3.2.1 Static List of Types (ST-OD) .......................................190

4.3.2.2 Static Object Dictionary (S-OD) ....................................191

4.3.2.3 Dynamic List of Variable Lists (DV-OD) .............................191

4.3.2.4 Dynamic List of Program Invocations (DP-OD) ........................192

4.3.3 Object Description in the OD .......................................193

4.3.4 OD Object Description ..............................................193

4.3.4.1 Attributes .........................................................194

4.3.4.2 Representation of the OD on Transmission ...........................195

4.3.4.3 Empty Object Dictionary ............................................196

4.3.5 The OD Object ......................................................196

4.3.5.1 Attributes .........................................................196

4.3.6 OD Services ........................................................197

4.3.6.1 GetOD ..............................................................198

4.3.6.2 PutOD Services .....................................................199

Page 142

PROFIBUS-Specification-Normative-Parts-5:1997

4.3.7 State Machine...................................................... 202

4.3.7.1 State Machine Description.......................................... 202

4.3.7.2 State Transitions.................................................. 203

4.3.8 EXAMPLE of a PutOD Sequence........................................ 204

4.4 Context Management................................................. 204

4.4.1 Model Description.................................................. 204

4.4.2 The FMS CRL Object................................................. 204

4.4.3 The Transaction Object............................................. 207

4.4.3.1 Attributes......................................................... 208

4.4.3.2 State Machine...................................................... 208

4.4.4 Context Management Services........................................ 209

4.4.4.1 Initiate........................................................... 209

4.4.4.2 Abort.............................................................. 212

4.4.4.3 Reject............................................................. 214

4.4.5 Tests at Connection Establishment.................................. 215

4.4.5.1 Context Test in FMS................................................ 215

4.4.5.2 Tests at the FMS User.............................................. 215

4.4.6 State Machine for connection-oriented Communication

Relationships...................................................... 216

4.4.6.1 State Machine Description.......................................... 216

4.4.6.2 State Transitions.................................................. 217

4.4.7 State Machine for connectionless Communication Relationships....... 226

4.4.7.1 State Machine in the Client........................................ 226

4.4.7.2 State Machine in the Server........................................ 227

4.5 Domain Management.................................................. 229

4.5.1 Model Description.................................................. 229

4.5.2 The Domain Object.................................................. 229

4.5.2.1 Attributes......................................................... 229

4.5.2.2 Object Description of the OD on Transmission....................... 231

4.5.3 Download Services.................................................. 231

4.5.3.1 InitiateDownloadSequence........................................... 231

4.5.3.2 DownloadSegment.................................................... 232

4.5.3.3 TerminateDownloadSequence.......................................... 233

4.5.3.4 RequestDomainDownload.............................................. 234

4.5.4 Upload Services.................................................... 235

4.5.4.1 InitiateUploadSequence............................................. 235

4.5.4.2 UploadSegment...................................................... 236

4.5.4.3 TerminateUploadSequence............................................ 237

4.5.4.4 RequestDomainUpload................................................ 238

4.5.5 State Machine for Download......................................... 239

4.5.5.1 State Machine Description.......................................... 239

4.5.5.2 State Transitions.................................................. 240

Page 143

PROFIBUS-Specification-Normative-Parts-5:1997

4.5.6 State Machine for Upload ...........................................240

4.5.6.1 State Machine Description ..........................................240

4.5.7 EXAMPLES ...........................................................242

4.5.7.1 EXAMPLE of a Download Sequence .....................................242

4.5.7.2 EXAMPLE of an Upload Sequence ......................................243

4.6 Program Invocation Management ......................................244

4.6.1 Model Description ..................................................244

4.6.2 The Program Invocation (PI) Object .................................244

4.6.2.1 Attributes .........................................................245

4.6.2.2 Object Description of the OD on Transmission .......................247

4.6.3 Program Invocation Services ........................................247

4.6.3.1 CreateProgramInvocation ............................................247

4.6.3.2 DeleteProgramInvocation ............................................249

4.6.3.3 Start ..............................................................250

4.6.3.4 Stop ...............................................................251

4.6.3.5 Resume .............................................................252

4.6.3.6 Reset ..............................................................253

4.6.3.7 Kill ...............................................................254

4.6.4 State Machine ......................................................255

4.6.4.1 State Machine Description ..........................................255

4.6.4.2 State Transitions ..................................................256

4.7 Variable Access ....................................................258

4.7.1 Model Description ..................................................258

4.7.2 Variable Access Objects ............................................258

4.7.2.1 The Physical Access Object .........................................258

4.7.2.2 The Simple Variable Object .........................................260

4.7.2.3 The Array Object ...................................................262

4.7.2.4 The Record Object ..................................................265

4.7.2.5 The Variable List Object ...........................................267

4.7.2.6 The Data Type Object ...............................................270

4.7.2.7 The Data Type Structure Description Object .........................272

4.7.3 Variable Access Services ...........................................273

4.7.3.1 Read ...............................................................273

4.7.3.2 Write ..............................................................274

4.7.3.3 PhysRead ...........................................................275

4.7.3.4 PhysWrite ..........................................................276

4.7.3.5 InformationReport ..................................................277

4.7.3.6 DefineVariableList .................................................278

4.7.3.7 DeleteVariableList .................................................279

4.7.3.8 ReadWithType .......................................................280

4.7.3.9 WriteWithType ......................................................281

4.7.3.10 InformationReportWithType ..........................................282

Page 144

PROFIBUS-Specification-Normative-Parts-5:1997

4.8 Event Management................................................... 283

4.8.1 Model Description.................................................. 283

4.8.2 The Event Object................................................... 284

4.8.2.1 Attributes......................................................... 284

4.8.2.2 Object Description of the OD on Transmission....................... 285

4.8.3 Event Management Services.......................................... 286

4.8.3.1 EventNotification.................................................. 286

4.8.3.2 AcknowledgeEventNotification....................................... 287

4.8.3.3 AlterEventConditionMonitoring...................................... 288

4.8.3.4 EventNotificationWithType.......................................... 289

4.8.4 State Machine...................................................... 290

4.8.4.1 State Machine Description.......................................... 290

4.8.4.2 State Transitions.................................................. 290

4.8.5 EXAMPLE: Event Management Services................................. 291

4.9 Interface between FMS and LLI...................................... 292

4.9.1 Overview of Services............................................... 292

4.9.2 Mapping of FMS Services on LLI Services............................ 292

4.10 Interface between FMS and FMA7..................................... 293

4.10.1 Overview of local FMS Management Services.......................... 293

4.10.1.1 FMS Disable........................................................ 293

4.10.1.2 FMS Load CRL....................................................... 293

4.10.1.3 FMS Enable......................................................... 294

4.10.1.4 FMS Read CRL....................................................... 295

4.10.1.5 FMS Ident.......................................................... 296

4.10.1.6 FMS Reset.......................................................... 297

4.10.2 FMA7 ErrorType..................................................... 297

4.11 Operating Behaviour of FMS......................................... 298

4.11.1 Start of FMS....................................................... 298

4.11.2 Conditions of Readiness for Operation.............................. 298

4.11.3 FMS Readiness for Operation........................................ 298

4.11.4 FMS Basic State Machine............................................ 298

4.11.4.1 FMS Basic State Machine Description................................ 298

4.11.4.2 State Transitions.................................................. 299

4.12 Structured Parameters ErrorType and TypeDescription................ 303

4.12.1 Parameter Error Type.............................................. 303

4.12.1.1 Meaning of Error Class and Error Code.............................. 303

4.12.1.2 Meaning of the remaining Parameters................................ 306

4.12.2 Parameter Type Description......................................... 306

4.13 Tables............................................................. 308

4.13.1 List of Object Codes............................................... 308

4.13.2 List of Standard Data Types........................................ 308

4.13.3 List of Object Attributes and Service Parameters................... 309

4.13.4 List of Services................................................... 311

Page 145

PROFIBUS-Specification-Normative-Parts-5:1997

4.14 Conformance ........................................................311

4.14.1 Implementation and System (PICS Part 1) ............................312

4.14.2 Supported Services (PICS Part 2) ...................................312

4.14.3 FMS Parameters and Options (PICS Part 3) ...........................314

4.14.4 Local Implementation Values (PICS Part 4) ..........................314

Page 146

PROFIBUS-Specification-Normative-Parts-5:1997

1 Scope

This specification specifies the Application Layer protocol, the Application

Layer interface, the corresponding Network Management and the mapping onto the

Data Link Layer of the bit serial PROFIBUS System according to the PROFIBUS Data

Link Layer.

PROFIBUS is intended for automation applications that are close to the process

and makes simple bus interfaces with real-time behaviour possible. This specifi-

cation allows field automation components of different manufacturers to be in-

terconnected in a distributed system and guarantees reliable communication. Such

a system is called an "open system". In addition the PROFIBUS protocol makes

possible the easy integration into hierarchically higher automation systems

(Manufacturing Automation Protocol, MAP). Thus the interconnection expense is

minimized.

With the degree of freedom in the specification a flexibility is achieved that

allows the implementation of different system configurations and functional

structures for different application areas. It is intended to define specific

profiles (application-oriented functional standards) for different application

areas such as building automation, discrete part manufacturing, process control

etc.

2 Normative References and additional Material

ISO 7498/1:1989 Information processing systems; Open System Interconnec-

tion; Basic Reference Model

ISO 7498/4:1989 Information processing systems; Open System Interconnec-

tion; Basic Reference Model; Part 4: Management Framework

ISO 8824:1987 Information processing systems; Open System Inter-

connection; Specification of Abstract Syntax Notation One

(ASN.1)

ISO 8825:1987 Information Processing Systems; Open System Inter-

connection; Specification of Basic Encoding Rules for Ab-

stract Syntax Notation One (ASN.1)

ISO TR 8509:1987 Information Processing Systems; Open System Inter-connec-

tion - Service Conventions

IEEE 754:1985 IEEE Standard for Binary Floating-Point Arithmetic

Page 147

PROFIBUS-Specification-Normative-Parts-5:1997

3 General

3.1 Terms and Apprevations

The multiplicity of technical terms and the need to relate to existing interna-

tional bus standards make it necessary to limit the technical terms to a well

defined set.

Abbreviation Meaning

.con confirmation primitive

.ind indication primitive

.req request primitive

.res response primitive

ABO ABOrt or FMA7 Abort

ACI Acyclic Control Interval

ACK ACKnowledged

acyc acyclic

AD Additional Detail

ALI Application Layer Interface

ASIC Application Specific Integrated Circuit

ASN.1 Abstract Syntax Notation One

ASS ASSociate service of LLI

BRCT BRoadCasT communication relationship

C Conditional

CCI Cyclic Control Interval

CI Control Interval

CN ConNection

CON CONfirmation

CREF Communication REFerence

CREL Communication RELationship

CRL Communication Relationship List

CRL Header Header of the Communication Relationship List

CSRD Cyclic Send and Request Data with reply

"D" Defined connection

DIN Deutsches Institut fuer Normung e.V., German standards body

DIS Draft International Standard

DP-OD Dynamic list of Program invocations (Object Dictionary)

DS Disconnected Station local FDL/PHY controller not in logical

token ring or disconnected from line

DSAP Destination Service Access Point

DTA Data Transfer Acknowledged

DTC Data Transfer Confirmed

DTU Data Transfer Unconfirmed

DV-OD Dynamic list of Variable lists (Object Dictionary)

FC Function Code

FDL Fieldbus Data Link, Layer 2

FER Fieldbus Encoding Rules

FMA Fieldbus MAnagemant

FMA1/2 Fieldbus Management Layer 1 and 2

FMA7 Fieldbus Management Layer 7

FMS Fieldbus Message Specification

FR+ Final Response

GAP Range of station addresses from This Station (TS) to its suc-

cessor (NS) in the logical token ring, excluding stations above

HSA

Page 148

PROFIBUS-Specification-Normative-Parts-5:1997

GAPL GAP List containing the status of all stations in this sta-

tion's GAP

HSA Highest Station Address (FDL Address)

HW Hardware

"I" Open Connection at the Requester

ID Identifier

IDM Image Data Memory

IEEE Institute of Electrical and Electronical Engineers, USA

IL Ident List

IMA Idle Machine Activated

IND Indication

INFO Information Report

INI Initiate

IS International Standard

ISO International Organization for Standardization

IV Invalid parameters in request

IVID Invoke ID

kbit/s kilobit per second (Data Signalling Rate)

L_sdu Link Service Data Unit

LAS List of Active Stations

LG Locally Generated

LL Live List

LLI Lower Layer Interface

Loc_add Local Address

LR Local Resource not available or not sufficient

LS Local Service not activated at Service Access Point or local

LSAP not activated

LSAP Link Service Access Point

LSB Least Significant Bit

M Mandatory

MAP Manufacturing Automation Protocol

MMAC Master-Master connection for ACyclic data transfer

MMS Manufacturing Message Specification

MSAC Master-Slave connection for ACyclic data transfer with no Slave

initiative

MSAC_SI Master-Slave connection for ACyclic data transfer with Slave

Initiative

MSB Most Significant Bit

MSCY Master-Slave connection for CYclic data transfer with no Slave

initiative

MSCY_SI Master-Slave connection for CYclic data transfer with Slave

Initiative

MULT Multicast Communication Relationship

NA No Acknowledgement/Response

NE Non Existent

NIL locally existing value, but not fixed in this specification

NOK Not OK

"O" Open connection at the Responder

OD Object Dictionary

OD-ODES Object Dictionary Object Description

OSCC Outstanding Services Counter Client

OSCS Outstanding Services Counter Server

PDU Protocol Data Unit

PEE Poll Entry Enabled

PHY Physical Layer

Page 149

PROFIBUS-Specification-Normative-Parts-5:1997

PI Program Invocation

PICS Protocol Implementation Conformance Statement Proforma

R+ Result(+)

R- Result(-)

RAC Receive Acknowledged Request Counter

RC Reason Code

RCC Receive Confirmed Request Counter

RDH Response FDL Data High and no resource for send data

RDL Response FDL/FMA1/2 Data Low and no resource for send data

Rem_add Remote address

REQ Request

RES Response

ROM Read Only Memory

RR no Resource for send data and no Response FDL data (acknowled-

gement negative)

RS no Service or no Rem_add activated at Remote Service Access

Point (acknowledgement negative)

RSAP Remote Service Access Point

RSV Reserve

RTimer Receive Timer

RVR ReadValueRem

S Selection

S-OD Static list of Objects (Object Dictionary)

SAC Send Acknowledged request Counter

SAP Service Access Point

SC State Conflict

SCC Send Confirmed request Counter

SDA Send Data with Acknowledge

SDN Send Data with NO acknowledge

SI Slave Initiative

SN Sign

SRD Send and Request Data with reply

SSAP Source Service Access Point

ST-OD Static list of Types (Object Dictionary)

Std Standard

STimer Send Timer

SU Summer time (standard time / summer time)

SW Release Software Release

T1 Timer 1

TQUI Quiet Time, Transmitter fall Time (Line State Uncertain Time)

and / or Repeater switch Time;the time a transmitting station

must wait after the end of a frame before enabling ist receiver

TRR Real Rotation Time the time between the last successive recep-

tions of the token by this Master station

TS This Station

TSDR Station Delay of Responder the actual time this responder waits

before generating a reply frame

TSET Setup Time the time between an event (e.g. interrupt SYN timer

expired) and the necessary reaction (e.g. enabling receiver)

TSL Slot Time the maximum time a Master station on this PROFIBUS

System must wait for a transaction response

TTR Target Rotation Time the anticipated time for one token rota-

tion on this PROFIBUS System including allowances for high and

low priority transactions, errors and GAP maintenance

U User optional

UE negative acknowledgement, remote User interface Error

VFD Virtual Field Device

Page 150

PROFIBUS-Specification-Normative-Parts-5:1997

3.2 Architecture and Placement in the ISO/OSI Layer Model

The PROFIBUS architecture is based on the ISO/OSI model of open communication

(ISO 7498). The PROFIBUS specification uses Layer 1 (Physical Layer, PHY), Layer

2 (Data Link Layer, FDL ) and Layer 7 (Application Layer). The Layers 3 to 6 are

empty to minimize expense and increase efficiency.

The Physical Layer (Layer 1), Data Link Layer (Layer 2) and the corresponding

management (FMA1/2) are described in the Data Link Layer of the PROFIBUS Speci-

fication. The Application Layer (FMS, LLI) and the corresponding management (FMA

7) are described in this specification.

*********

***** *********

**** ************

* Application Process ******

* *

******* ********

************* ********* ^

^ ******* !

! ! !

FMS Services FMA7 Services

! ! !

! v v

+-----------------------------------+---------------+

! F M S ! !

! ! !

!... Application Layer ..(Layer 7)..+.... F M A 7 !

! ! !

! L L I ! !

! ! M !

+---------------------------------------+ a !

! ! n !

! empty (Layer 3 to 6) ! a !

! ! g !

+---------------------------------------+---- e ----+

! ! m !

! Data Link Layer (Layer 2) ! e !

! ! n !

! F D L ! t !

! ! !

+---------------------------------------+ F M A 1/2 !

! ! !

! Physical Layer (Layer 1) ! !

! ! !

! P H Y ! !

! ! !

+---------------------+-----------------+-----------+

!

=========================#=================================

Figure 1. Placement in the ISO/OSI Layer Model

Спецификация протокола Profibus

Подождите немного. Документ загружается.