Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 251
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.6.3.4 Stop
A running program is stopped. It is not set to the beginning. The counters of
the used domains are decremented.
Table 32. Stop
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! Access Specification ! M ! !
! Index ! S ! !
! PI Name ! S ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! Error Type ! ! M !
! PI State ! ! M !
+---------------------------------+-----+-----+
Argument
The argument contains the service specific parameters of the service request.
Access Specification
This parameter states if the index or the name is used for addressing.
Index
This parameter is the logical address of the Program Invocation in the OD to
which this service is related.
PI Name
This parameter is the name of the Program Invocation.
Result(+)
The Result(+) parameter shall indicate that the service was completed success-
fully.
Result(-)
The Result(-) shall indicate that the service request was not completed success-
fully.
Error Type
This parameter contains information about the reason why the service was not
completed successfully.
PI State
This parameter indicates the state of the Program Invocation.
Page 252
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.6.3.5 Resume
A stopped program is set to the state RUNNING. It is not reset. The counters of
the used domains are incremented. Before that all corresponding domains are
checked if they are in the READY or in the IN USE state.
Table 33. Resume
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! Access Specification ! M ! !
! Index ! S ! !
! PI Name ! S ! !
! Execution Argument ! U ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! Error Type ! ! M !
! PI State ! ! M !
+---------------------------------+-----+-----+
Argument
The argument contains the service specific parameters of the service request.
Access Specification
This parameter states if the index or the name is used for addressing.
Index
This parameter is the logical address of the Program Invocation in the OD to
which this service is related.
PI Name
This parameter is the name of the Program Invocation.
Execution Argument
This optional parameter of type octet string contains data that is given to the
Program Invocation for the start.
Result(+)
The Result(+) parameter shall indicate that the service was completed success-
fully.
Result(-)
The Result(-) shall indicate that the service request was not completed success-
fully.
Error Type
This parameter contains information about the reason why the service was not
completed successfully.
PI State
This parameter indicates the state of the Program Invocation.
Page 253
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.6.3.6 Reset
A stopped program having the attribute Reusable = true is set to the beginning.
The Program Invocation transits to the state IDLE. If the attribute Reusable is
equal to false the Program Invocation Object transits to the state UNRUNNABLE.
Table 34. Reset
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! Access Specification ! M ! !
! Index ! S ! !
! PI Name ! S ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! Error Type ! ! M !
! PI State ! ! M !
+---------------------------------+-----+-----+
Argument
The argument contains the service specific parameters of the service request.
Access Specification
This parameter states if the index or the name is used for addressing.
Index
This parameter is the logical address of the Program Invocation in the OD to
which this service is related.
PI Name
This parameter is the name of the Program Invocation.
Result(+)
The Result(+) parameter shall indicate that the service was completed success-
fully.
Result(-)
The Result(-) shall indicate that the service request was not completed success-
fully.
Error Type
This parameter contains information about the reason why the service was not
completed successfully.
PI State
This parameter indicates the state of the Program Invocation.
Page 254
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.6.3.7 Kill
A Program Invocation is set to the state UNRUNNABLE. This is independent of the
current state. If the state of the Program Invocation was RUNNING or STOPPING,
the counters of the used domains are decremented.
Table 35. Kill
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! Access Specification ! M ! !
! Index ! S ! !
! PI Name ! S ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! Error Type ! ! M !
+---------------------------------+-----+-----+
Argument
The argument contains the service specific parameters of the service request.
Access Specification
This parameter states if the index or the name is used for addressing.
Index
This parameter is the logical address of the Program Invocation in the OD to
which this service is related.
PI Name
This parameter is the name of the Program Invocation.
Result(+)
The Result(+) parameter shall indicate that the service was completed success-
fully.
Result(-)
The Result(-) shall indicate that the service request was not completed success-
fully.
Error Type
This parameter contains information about the reason why the service was not
completed successfully.
Page 255
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.6.4 State Machine
4.6.4.1 State Machine Description
NON-EXISTENT
The Program Invocation is after a power-up, if not otherwise defined, or after
deletion, non-existent.
IDLE
A Program Invocation transits to the state IDLE by entering it in the DP-OD. Af-
ter a successful Reset service and after the end of the program the Program In-
vocation transits also to the state IDLE. Program Invocations may be predefined.
These Program Invocations transit after power-up to the state IDLE.
STARTING
Intermediate state for the preparation of the program start.
RUNNING
The program is running in this state. The domains that are defined in this Pro-
gram Invocation are now in the state IN USE.
STOPPING
Intermediate state for the preparation of the stop of the program.
STOPPED
The program is stopped in this state.
RESUMING
Intermediate state for the preparation of the resumption of the program.
RESETTING
Intermediate state in which the program is set to a well defined initial state.
UNRUNNABLE
In this state the program is stopped but it may not be started again. It may
only be deleted.
Page 256
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
+-----------------------+ 3
+------------>! NON-EXISTENT !<-----------+
! +-----------------------+ !
! ! ^ !2 ^ !
! ! ! +--+ +-----------------------+
! ! ! ! UNRUNNABLE !
! ! 1 ! 3 +-----------------------+
! V ! ^ !4 ^
! +------------------------+ 22 ! +--+
! +------->! IDLE !---------->+
! ! +------------------------+ !
! ! ! ^ ^ !4 ^ !
! ! V 5 ! 7 ! +--+ !
! ! +----------+ ! 8,22 !
! ! ! STARTING !----- ! ---------------->+
! ! +----------+ ! !
! ! ! 6 ! 24 !
! ! V ! !
! ! 26 +-----------------------+ 25,23 !
! ! +<--! RUNNING !----------->+
! ! ! +-----------------------+ !
! ! ! ! ^ 11 ^ 14 !
! ! ! V 9 ! ! !
! ! ! +----------+ +----------+ 16,22 !
! ! ! ! STOPPING ! ! RESUMING !----------->+
! ! ! +----------+ +----------+ !
! ! ! ! ! ^ ! 12,23 !
! ! +----+ ! +------ ! -- ! ----------->+
! ! V V 10 13 ! V 15 !
! ! 3 +-----------------------+ 22 !
+<-- ! -------! STOPPED !----------->+
! +-----------------------+ !
! ! ^ !4 ^ !
! 17 ! ! 20 +--+ !
! V ! !
! 18 +-----------+ 19,21,22 !
+<-------! RESETTING !----------------------->+
+-----------+
Figure 56. State Diagram
4.6.4.2 State Transitions
-----------------------------------------------------------------
Event
\Exit Condition
=> Action Taken
-----------------------------------------------------------------
1 CreateProgramInvocation.ind
\Domains available
AND Access to Domains allowed
=> .res(+)
2 CreateProgramInvocation.ind
\Domains not available
OR Access to Domains not allowed
=> .res(-)
3 DeleteProgramInvocation.ind
=> .res(+)
4 DeleteProgramInvocation.ind
=> .res(-)
5 Start.ind
Page 257
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
-----------------------------------------------------------------
Event
\Exit Condition
=> Action Taken
-----------------------------------------------------------------
6 Start successfully executed
\Domains in State READY or IN-USE
=> Counter increment
Start.res(+)
7 Start failed, non-destructive
(e.g. Domains not in State READY or IN-USE)
=> Start.res(-)
8 Start failed, destructive
=> Start.res(-)
9 Stop.ind
10 Stop successfully executed
=> Counter decrement
Stop.res(+)
11 Stop failed, non-destructive
=> Stop.res(-)
12 Stop failed, destructive
=> Counter decrement
Stop.res(-)
13 Resume.ind
14 Resume successfully executed
\Domains in State READY or IN-USE
=> Counter increment
Resume.res(+)
15 Resume failed, non-destructive
(e.g. Domains not in State READY or IN-USE)
=> Resume.res(-)
16 Resume failed, destructive
=> Resume.res(-)
17 Reset.ind
18 Reset successfully executed, Reusable = true
=> Reset.res(+)
19 Reset successfully executed, Reusable = false
=> Reset.res(+)
20 Reset failed, non-destructive
=> Reset.res(-)
21 Reset failed, destructive
=> Reset.res(-)
22 Kill.ind
=> .res(+)
23 Kill.ind
=> Counter decrement
.res(+)
24 End of Program, Reusable = true
=> Counter decrement
25 End of Program, Reusable = false
=> Counter decrement
26 Program stop
=> Counter decrement
Counter increment, Counter decrement: see StateMachineDomain Download.
Page 258
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.7 Variable Access
4.7.1 Model Description
The Variable Access Model provides services to read and to write variables and
to define and to delete dynamically new Variable List Objects.
The following services and objects are defined:
Table 36. Variable Access Services and Objects
+--------------------+-------------+----------------------+
! Service ! Confirmed/ ! Objects !
! ! Unconfirmed ! !
! ! ! !
+--------------------+-------------+----------------------+
! Read ! Confirmed ! Simple Variable, !
+--------------------+-------------! Array, !
! Write ! Confirmed ! Record, !
!--------------------!-------------! Variable List !
! ReadWithType ! Confirmed ! !
+--------------------+-------------! !
! WriteWithType ! Confirmed ! !
+--------------------+-------------! !
! InformationReport ! Unconfirmed ! !
+--------------------+-------------! !
! InformationReport- ! Unconfirmed ! !
! WithType ! ! !
+--------------------+-------------+----------------------+
! PhysRead ! Confirmed ! Physical Access !
+--------------------+-------------! Object !
! PhysWrite ! Confirmed ! !
+--------------------+-------------+----------------------+
! DefineVariableList ! Confirmed ! Object Description !
! ! ! Variable List, !
+--------------------+-------------! !
! DeleteVariableList ! Confirmed ! Variable List !
! ! ! !
+--------------------+-------------+----------------------+
! --- ! --- ! Data Type !
+--------------------+-------------+----------------------+
! --- ! --- ! Date Type Structure !
! ! ! Description !
+--------------------+-------------+----------------------+
4.7.2 Variable Access Objects
Objects entered in the S-OD are not deletable.
4.7.2.1 The Physical Access Object
The Physical Access Object describes the access to an actual octet string.
Such an octet string may neither be defined nor be deleted.
No explicit object description of the Physical Access Object is stored. The ad-
dress and semantics are known to the user.
The access rights are controlled through the Service Context Agreement, i.e. the
Context Agreement specifies if the physical access is allowed on this Communica-
tion Relationship.
Page 259
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Services onto the Physical Access Object:
- PhysRead \ +--------------------+
- PhysWrite >----------------------->! Physical !
/ ! Access !
! Object !
+--------------------+
Figure 57. Physical Access Object Services
Attributes
Object: Physical Access Object
Key Attribute: Local Address
Attribute: Length
Local Address
This object is accessed knowing its physical address and its structure, by-
passing the Object Dictionary of the related device. The data type octet string
is used implicitly.
Length
Statement of the length in octets for this object during read and write opera-
tions.
Page 260
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.7.2.2 The Simple Variable Object
The Simple Variable Object represents a single, simple variable which is charac-
terized by a defined Data Type. The Object Description of the Variable Access
Object Simple Variable is stored statically in the Object Dictionary (S-OD). The
mapping of a PROFIBUS Simple Variable to a real Simple Variable, which exists in
the application system, is defined by the object description of the Simple Vari-
able Object. Only one single Data Type of the set of configured Data Types is
allowed in the Object Description of the Simple Variable Object.
+--------------------------------+
! Object Description !
Index ! Simple Variable !
or ! !
Name ! +--------------+ ! +--------------+
------>!---->! Simple !-- Index i -------->! Data Type !
! ! Variable ! ! +--------------+
! +------+-------+ !
! ! !
! ! real ! +--------------+
! +- Object address ---------->! real !
! ! ! Simple !
! ! ! Variable !
+--------------------------------+ +--------------+
Figure 58. Overview of Simple Variable
Services on the Object Simple Variable:
+--------------------+
- OD Services ------------------------>! Object Description !
! Simple Variable !
- Read \ ! !
- Write : ! +--------------+ !
- ReadWithType >---------->! Simple ! !
- WriteWithType : ! ! Variable ! !
- InformationReport : ! +--------------+ !
- InformationReportWithType / +--------------------+
Figure 59. Simple Variable Servioces
Attributes
Object: Simple Variable
Key Attribute: Index
Key Attribute: Variable Name
Attribute: Data Type Index
Attribute: Length
Attribute: Password
Attribute: Access Groups
Attribute: Access Rights
Attribute: Local Address
Attribute: Extension
Index
Logical Address of the object.
Variable Name
The name of the object. Its existence and its length is defined in the OD Object
Description.