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

Page 61

PROFIBUS-Specification-Normative-Parts-3:1997

After receiving the data and request frame error-free, the remote FDL controller

immediately starts transmitting the requested data (see Part 4, Table 3a, b7=0,

Code No 8/10) that was previously provided by the Remote User by means of a

FDL_REPLY_ UPDATE.request primitive. In case of a FDL_REPLY_ UPDATE without a

corresponding SSAP or in case of an error, an acknowledgement is returned (see

Part 4, Table 3a, b7=0, Code No 1/2/3/9/12/13). The received L_sdu and the

information concerning the back-transmission is passed to the Remote User by

means of a FDL_DATA_REPLY. indication primitive via the FDL user interface. If

an answer or an acknowledgement is not received within the slot time T

SL

, the

local FDL controller shall repeat the data transmission and request. Between the

original data transmission and the requested answer no other traffic takes place

on the PROFIBUS. By means of a FDL_DATA_REPLY.confirm primitive the local FDL

controller signals to the Local User that the data was duly received by the

remote FDL controller and returns the requested data or an error message.

The Remote User is responsible for valid data in the remote FDL controller. By

means of a FDL_REPLY_UPDATE.request primitive the Remote FDL User may initiate

loading of this data. Upon completion of loading the data area the FDL control-

ler informs the FDL user by means of a FDL_REPLY_UPDATE.confirm primitive.

Parameters of the primitives:

FDL_DATA_REPLY.request

(SSAP, DSAP, Rem_add, L_sdu, Serv_class)

- The parameters SSAP, Rem_add, L_sdu and Serv_class have the same meaning as

described for SDA under the FDL_DATA_ACK.request primitive. The L_sdu may

have a length of zero.

- The parameter DSAP specifies the service access point for the requested data

area and the data to be sent (shared_data_area) as well as the Remote User

that receives the indication. A DSAP value of 63 (global access address) is

not permissible.

This primitive is passed from the Local User to the local FDL controller to send

data to a Remote User and to simultaneously request data from that user or to

exclusively request data. Receipt of this primitive by the local FDL controller

causes transmittal of the L_sdu with data request by means of the SRD procedure.

The L_sdu may have a length of zero.

During the processing of a SRD request (i. e. while waiting for a response or an

acknowledgement, respectively) no further service shall be sent from the local

FDL controller.

FDL_DATA_REPLY.indication

(SSAP, DSAP, Loc_add, Rem_add, L_sdu, Serv_class, Update_status)

- The parameters have the same meaning as described for SDA under the

FDL_DATA_ACK.request primitive with respect to the received SRD frame. The

L_sdu may have a length of zero.

- The parameter Update_status specifies, whether or not the response data

(L_sdu) has been passed to the local FDL controller. The following parameter

values are specified:

Page 62

PROFIBUS-Specification-Normative-Parts-3:1997

Table 3. SRD, Values of Update_status

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! NO ! No reply data (L_sdu) transmitted. ! t !

! LO ! Low priority reply data transmitted. ! - !

! HI ! High priority reply data transmitted. ! - !

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

This primitive is passed from the remote FDL controller to the

Remote User when the response/acknowledgement frame for a SRD frame was sent.

The reaction of the Remote User upon receipt of the primitive is not specified.

In case of a repetition of the response/acknowledgement frame caused by the

receipt of a repetition of the SRD frame, the Indication primitive shall not be

repeated. The primitive is not applicable when the parameter Indication_mode =

Data (see subclause 4.2.3.7) and if the length of the L_sdu is zero both in the

received frame and in the corresponding Reply Update (response data). In this

case the resources of the LSAP are not used.

FDL_DATA_REPLY.confirm

(SSAP, DSAP, Rem_add, L_sdu, Serv_class, L_status)

- The parameters SSAP, DSAP and Rem_add have the same meaning as described for

SDA under the FDL_DATA_ACK.request primitive with respect to the SRD frame. A

DSAP value of 63 is not permissible.

- The parameter Serv_class specifies the FDL priority of the request frame.

- The parameter L_sdu contains the requested data of the remote FDL controller.

- The parameter L_status contains the result of the corresponding SRD request

and encompasses the values UE, RS, LS, LR, NA, DS and IV as specified for SDA

(see Table 1.) and additionally:

Table 4. SRD, Values of L_status

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! DL ! Positive acknowledgement for sent data, ! !

! ! reply data (L_sdu) with low priority ! !

! ! available. ! - !

! DH ! Positive acknowledgement for sent data, ! !

! ! reply data with high priority available. ! - !

! NR ! Positive acknowledgement for sent data, ! !

! ! negative acknowledgement for reply data, as! !

! ! not available to the remote FDL controller.! t !

! RDL! Negative acknowledgement for sent data, ! !

! ! resources of the remote FDL controller not ! !

! ! available or not sufficient, reply data ! !

! ! with low priority available. ! t !

! RDH! Negative acknowledgement for sent data, ! !

! ! resources of the remote FDL controller not ! !

! ! available or not sufficient, reply data ! !

! ! with high priority available. ! t !

! RR ! Negative acknowledgement, resources of the ! !

! ! remote FDL controller not available or not ! !

! ! sufficient and reply data not available. ! t !

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

Page 63

PROFIBUS-Specification-Normative-Parts-3:1997

This primitive is passed from the local FDL controller to the Local User to sig-

nal success or failure of the previous data transfer and request and to hand

over the requested data in case of an error-free procedure. The reaction of the

Local User upon receipt of this primitive is not specified. If L_status indi-

cates a temporary error a later repetition may be successful. In case of a per-

manent error the Local User should consult management prior to repeating the

service.

FDL_REPLY_UPDATE.request

(SSAP, L_sdu, Serv_class, Transmit)

- The parameter SSAP specifies the service access point of the Remote User that

carries out this request and which data area (shared_data_area) shall be up-

dated by the L_sdu. A SSAP value of 63 is not permissible.

- The parameter L_sdu specifies the contents of the data area that is identi-

fied by the SSAP parameter.

- The parameter Serv_class has the same meaning as described for SDA under the

FDL_DATA_ACK.request primitive.

- The parameter Transmit specifies whether the Update is transmitted only once

(single) or many times (multiple), i. e. in the case of "multiple" the data

area is transferred again for each subsequent SRD.

The primitive is passed from the Remote User to the remote FDL controller to

receive the response data. Receipt of this primitive causes the remote FDL con-

troller to try to access the data in the course of which data consistency shall

be guaranteed. This primitive in connection with the SRD of the Local User is

only of importance to the Remote User.

FDL_REPLY_UPDATE.confirm

(SSAP, Serv_class, L_status)

- The parameters SSAP and Serv_class have the same meaning as described for SDA

under the FDL_DATA_ACK.confirm primitive.

- The parameter L_status indicates the result of the corresponding UPDATE

request. The following parameter values are specified:

Table 5. SRD, Values of L_status (UPDATE)

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! OK ! Update data (L_sdu) loaded. ! - !

! LS ! Service at local LSAP or local LSAP not ! !

! ! activated. ! p !

! LR ! Resources of the local FDL controller not ! !

! ! available or not sufficient. ! t !

! IV ! Invalid parameters in request. ! - !

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

This primitive is passed from the remote FDL controller to the Remote User to

signal success or failure of the UPDATE request. The reaction of the Remote User

upon receipt of this primitive is not specified. If L_status indicates a tempo-

rary error, a later repetition may be successful. In case of a permanent error

the Local User should consult management prior to repeating the service.

Page 64

PROFIBUS-Specification-Normative-Parts-3:1997

4.1.3.4 Cyclic Send and Request Data with Reply (CSRD)

The Local User prepares a L_sdu each for one, many, or all Remote Users. For

each Remote User the data is passed to the local FDL controller by means of a

FDL_SEND_UPDATE.request primitive. The addresses and the sequence of the ad-

dressed remote stations shall be specified by the Local User by means of the

Poll List. The Local User passes the Poll List by means of a FDL_CYC_DATA_

REPLY.request primitive where initially all entries are set to "lock". At the

same time this action requests the cyclic send including the data request

(cyclic low priority SRD). The FDL controller accepts this combined service

request and signals the acceptance of the Poll List by means of a FDL_CYC_DATA_

REPLY.confirmation.

To allow for a prioritization of the stations to be polled, multiple identical

FDL address are permissible in the Poll List.

The FDL controller shall only start the cyclic send of the L_sdu with a data re-

quest (see Part 4, Table 3a, b7=1, Code No 12) to the requested remote FDL

controller if the corresponding marker is set to "unlock". This shall have been

initiated by the Local User by means of a FDL_CYC_ENTRY.request primitive.

If no data is to be sent then a SRD frame without data is sent to each remote

station.

After each data transfer and request an immediate response or acknowledgement is

expected (see Part 4, Table 3a, b7=0, Code No 8/10 or Code No 1/2/3/9/12/13,

respectively). The local and remote FDL controllers react as described for the

SRD (see subclause 4.1.3.3). The local FDL controller cyclically passes the re-

quested data or an error message to the Local User by means of a FDL_CYC_DATA_

REPLY.confirm primitive.

If the send data is transmitted only once (Transmit = single, cf. FDL_SEND_

UPDATE.request), the subsequent SRD frames shall not contain send data until a

new update is available.

The Local User may pass new data to the Remote User by means of a FDL_SEND_

UPDATE.request primitive at any time.

During the Cyclic Send and Request Data with Reply the Local User shall not

request any further cyclic service. The acyclic services SDA, SDN and SRD are

permissible. The FDL controller performs the cyclic SRD service with the given

Poll List as long as a FDL_CYC_DEACT.request primitive is issued by the Local

User.

Parameters of the primitives:

FDL_SEND_UPDATE.request

(SSAP, DSAP, Rem_add, L_sdu, Transmit)

- The parameter SSAP specifies the service access point of the Local User that

carries out this request and which data area (shared_data_area) is updated by

means of the L_sdu. A SSAP value of 63 is not permissible.

- The parameter DSAP specifies the service access point of the Remote User. A

DSAP value of 63 is not permissible.

- The parameter Rem_add contains the destination FDL address of the remote

station.

Page 65

PROFIBUS-Specification-Normative-Parts-3:1997

- The parameter L_sdu specifies the contents of the data area that is identi-

fied by means of the SSAP parameter. For the L_sdu a length of zero is per-

missible.

- The parameter Transmit specifies whether the Update is transmitted once

(single) or many times (multiple). In the case of "multiple" the data area is

transmitted with each further SRD.

The primitive is passed from the Local User to the local FDL controller to

receive the send data. The receipt of this primitive causes the local FDL con-

troller to try to receive the data in the course of which data consistency shall

be guaranteed.

FDL_SEND_UPDATE.confirm

(SSAP, DSAP, Rem_add, L_status)

- The parameters SSAP, DSAP and Rem_add have the same meaning as described for

the FDL_SEND_UPDATE.request primitive.

- The parameter L_status indicates the result of the corresponding UPDATE

request. The following parameter values are specified:

Table 6. CSRD, Values of L_status (UPDATE)

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! OK ! Send update data (L_sdu) loaded. ! - !

! LS ! Service at local LSAP or local LSAP not ! !

! ! activated. ! p !

! LR ! Resources of the local FDL controller not ! !

! ! available or not sufficient or Rem_add/ ! !

! ! DSAP not yet in the Poll List. ! t/p !

! IV ! Invalid parameters in request. ! - !

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

This primitive is passed from the local FDL controller to the Local User to

indicate the success or the failure of the UPDATE request. The reaction of the

Local User upon receipt of this primitive is not specified.

FDL_CYC_DATA_REPLY.request

(SSAP, Poll_list)

- The parameter SSAP specifies the LSAP of the Local User. A SSAP value of 63

is not permissible.

- The parameter Poll_list may be of the following values:

Page 66

PROFIBUS-Specification-Normative-Parts-3:1997

Table 7. Poll_list

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

!En- ! Name ! Meaning !

!try ! ! !

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

! 1 ! Poll_list_length ! Length of Poll List (3 to p+1) !

! 2 ! Rem_add ! Remote FDL address (DA) \first !

! 3 ! DSAP ! Destination LSAP (DAE) /Entry !

! 4 ! Rem_add ! Remote FDL address (DA) !

! 5 ! DSAP ! Destination LSAP (DAE) !

! . ! ... ! ... !

! p ! Rem_add ! Remote FDL address (DA) \last !

!p+1 ! DSAP ! Destination LSAP (DAE) /Entry !

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

- The parameters Rem_add (0 to 126 [EXT]) and DSAP (0 to 62) have the same

meaning as described for SDA under the FDL_DATA_ACK.request primitive.

Rem_add as global address and the DSAP value of 63 are not permissible. For

remote stations to which no LSAP is transferred, the parameter DSAP is NIL.

This primitive is passed from the Local User to the local FDL controller to

cyclically send data to the Remote User and to request data from these users at

the same time. The receipt of the primitive causes the local FDL controller to

immediately start the cyclic data transfer with the SRD procedure after the

marker has been set to "unlock". During the execution of the single cyclic SRD

(i. e. while waiting for the response or the acknowledgement) no further service

may be transmitted by the local FDL controller.

FDL_CYC_DATA_REPLY.confirm

(SSAP, DSAP, Rem_add, L_sdu, Serv_class, L_status, Update_status)

- The parameters SSAP, DSAP and Rem_add have the same meaning as described for

SDA under the FDL_DATA_ACK.request primitive with respect to the SRD frame. A

DSAP value of 63 is not permissible.

- The parameters L_sdu, Serv_class and L_status have the same meaning as

described for SRD under the FDL_DATA_REPLY.confirm primitive. In case of Poll

List delivery the parameter L_status may take the following additional

values:

Table 8. CSRD, Values of L_status

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! OK ! Poll List accepted. ! - !

! NO ! Poll List not accepted, as the Poll List ! !

! ! was already available in the local FDL ! p !

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

The parameters DSAP, L_sdu and L_status refer to the remote station with the

destination FDL address that is specified by the parameter Rem_add.

- The parameter Update_status specifies whether or not the data to be sent

(L_sdu) was passed to the remote FDL controller. The following parameter

values are specified:

Page 67

PROFIBUS-Specification-Normative-Parts-3:1997

Table 9. CSRD, Values of Update_status

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! NO ! No send data (L_sdu) transmitted. ! t !

! LO ! Send data with low priority transmitted. ! - !

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

This primitive is passed from the local FDL controller to the Local User to

indicate success or failure of the Poll List acceptance. In this case only the

parameters SSAP and L_status are significant. Furthermore after each cyclic SRD

this primitive is passed to the Local User to indicate the success or the fail-

ure of the corresponding Send and Request Data and to transfer the received data

when no errors occurred. This primitive is omitted after each cyclic SRD, if the

parameter Confirm_mode = Data (see subclause 4.2.3.7) and if the L_sdu has

length zero both in the received frame as well as in the corresponding Send Up-

date (send data). In this case the resources of the LSAP are not used. The

primitive is not omitted, however, if a L_status value of UE, RS, LR, NA, DS or

RR occurs.

FDL_CYC_ENTRY.request

(SSAP, DSAP, Rem_add, Marker)

- The parameter SSAP has the same meaning as described for the FDL_CYC_DATA_

REPLY.request primitive.

- The parameters DSAP and Rem_add specify the Poll List entry.

- The parameter Marker with the values "unlock" or "lock" specifies whether the

entry "Rem_add/DSAP" in the Poll List is to be unlocked or locked.

This primitive is passed from the Local User to the local FDL controller to un-

lock or lock an entry (Rem_add/DSAP) in the Poll List, i. e. to cyclically send

or not to send SRD frames to the corresponding DSAP of the remote FDL control-

ler.

FDL_CYC_ENTRY.confirm

(SSAP, DSAP, Rem_add, L_status)

- The parameter SSAP has the same meaning as described for the FDL_CYC_DATA_

REPLY.request primitive.

- The parameters DSAP and Rem_add specify the Poll List entry.

- The parameter L_status indicates the result of the corresponding ENTRY

request. The following parameter values are specified:

Page 68

PROFIBUS-Specification-Normative-Parts-3:1997

Table 10. CSRD, Values of L_status (ENTRY)

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! OK ! Marker set. ! - !

! LS ! Service at local LSAP or local LSAP not ! !

! ! activated. ! p !

! NO ! Marker not set, as Rem_add/DSAP parameter ! !

! ! is not in the Poll List. ! p !

! IV ! Invalid parameters in request. ! - !

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

This primitive is passed from the local FDL controller to the Local User to

indicate the success or failure of the corresponding entry unlock or lock.

FDL_CYC_DEACT.request

(SSAP)

- The parameter SSAP specifies the LSAP of the Local User with the cyclic SRD.

A SSAP value of 63 is not permissible.

This primitive is passed from the Local User to the local FDL controller to ter-

minate the cyclic SRD. The receipt of this primitive causes the local FDL con-

troller to stop the cyclic SRD procedures after passing through the Poll List.

FDL_CYC_DEACT.confirm

(SSAP, L_status)

- The parameter SSAP has the same meaning as described for the FDL_CYC_DEACT.

request primitive.

- The parameter L_status indicates the result of the corresponding request. The

following parameter values are specified:

Table 11. CSRD, Values of L_status (DEACT)

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

!Code! Meaning ! temporary/!

! ! ! permanent !

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

! OK ! Cyclic SRD service correctly finished. ! - !

! LS ! Service at local LSAP or local LSAP not ! !

! ! activated. ! p !

! IV ! Invalid parameters in request. ! - !

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

This primitive is passed from the local FDL controller to the Local User after

terminating the cyclic SRD. The reaction of the Local User upon receipt of this

primitive is not specified.

FDL_DATA_REPLY.indication

(SSAP, DSAP, Loc_add, Rem_add, L_sdu, Serv_class, Update_status)

FDL_REPLY_UPDATE.request

(SSAP, L_sdu, Serv_class, Transmit)

FDL_REPLY_UPDATE.confirm

(SSAP, Serv_class, L_status)

- Description of the primitives and the parameters: cf. SRD.

Page 69

PROFIBUS-Specification-Normative-Parts-3:1997

4.2 FMA1/2 User - FMA1/2 Interface

This clause describes the management services (FMA1/2 = Fieldbus Management for

Layers 1 and 2) that are provided to the FMA1/2 User and the associated service

primitives and parameters. One distinguishes between mandatory and optional

services.

FDL User FMA1/2 User

----------- +---------------------+=========+

! ! !

Layer 2 ! FDL ! !

! ! !

! ! FMA1/2 !

----------- +---------------------+ !

! ! !

Layer 1 ! PHY ! !

! ! !

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

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

"Layer 0" Physical Medium

---------------------------------

Figure 6. Interface between FMA1/2 User and FMA1/2 in Relation to Layer Model

The service interface between the FMA1/2 user and FMA1/2 provides the following

functions:

- Reset of Layers 1 and 2 (local)

- Request for and modification of the actual operating parameters of FDL and

PHY (local) and of the counters (local)

- Notification of unexpected events, errors, and status changes (local and

remote)

- Request for identification and for the LSAP configuration of the stations

(local afnd remote)

- Request for the actual list of stations (Live List) by means of FDL status

(remote)

- Activation and deactivation of the local LSAPs

4.2.1 Overview of Services

The FMA1/2 provides the following services to the FMA1/2 user:

- Reset FMA1/2

- Set Value7Read Value FMA1/2

- Event FMA1/2

- Ident FMA1/2

- LSAP Status FMA1/2

- Live List FMA1/2

- (R)SAP Activate / SAP Deactivate FMA1/2

Page 70

PROFIBUS-Specification-Normative-Parts-3:1997

Reset FMA1/2 (mandatory)

The FMA1/2 user employs this service to cause the FMA1/2 to reset Layer 1 (PHY),

Layer 2 (FDL) and itself. A reset is equivalent to power on. The FMA1/2 user

receives a confirmation thereof.

Set Value FMA1/2 (optional)

The FMA1/2 user employs this service to assign a new value to the variables of

Layer 1 or of Layer 2. The user receives a confirmation whether the specified

variables have been set to the new value.

Read Value FMA1/2 (optional)

This service enables the FMA1/2 to read variables of Layers 1 and 2. The

response of the FMA1/2 contains the actual value of the specified variables.

Event FMA1/2 (mandatory)

The FMA1/2 employs this service to inform the FMA1/2 user about certain events

or errors in Layers 1 and 2.

Ident FMA1/2 (optional)

When requesting the identification service, a distinction is made between master

and slave stations. By employing this service the FMA1/2 user of a slave station

determines the version data of the local FDL and FMA1/2 hard- and software. When

employing this service in the case of a master station, the FMA1/2 user may

additionally request the same type of information from a remote station.

LSAP Status FMA1/2 (optional)

The FMA1/2 user employs this service to inform himself about the configuration

of Service Access Points of the local FDL or, in the case of a remote station

(Remote LSAPs), about their FDL services. In the case of a Slave station this

service is only possible for local LSAPs.

Live List FMA1/2 (optional)

This service provides the FMA1/2 user of a master station (not possible for

slave stations) with an up-to-date list of all stations that are functional on

the bus (see Part 4, subclause 4.1.4).

SAP Activate FMA1/2 (optional)

This service enables the FMA1/2 user to activate and to configure a Link Service

Access Point (Local LSAP) for the individual FDL services. Excluded from this is

the responder function for the reply services (SRD and CSRD). The FMA1/2 user

receives a confirmation on the execution of the service from the FMA1/2.

RSAP Activate FMA1/2 (optional)

The FMA1/2 user employs this service to activate a Local LSAP for the responder

function of the reply services (SRD and CSRD). The user receives a confirmation

of execution from the FMA1/2.

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

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