Page 791
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
13.3.1.2 State Machine Description
For each possible DP-Slave a state machine (Slave-Handler) is established and
started by a superior state machine, the Scheduler. The Scheduler controls the
Slave-Handler through the primitives:
- Start_Slave_Handler.req
- Continue_Slave_Handler.req (Output_Clear)
The parameter Output_Clear (Boolean) indicates that not the
output data but zero has to be sent.
- Stop_Slave_Handler.req
The Slave-Handler indicates the result of the processing by means of the
following primitives to the Scheduler:
- Start_Slave_Handler.con
- Continue_Slave_Handler.con (Diag)
The parameter Diag (Boolean) indicates whether a regular data
exchange has taken place or not.
This parameter has the value false if DDLM_Data_Exchange was performed
successfully for a DP-Slave that is marked as active in the DP-Slave parameter
set. This bit is true in all other cases.
This parameter is always true for DP-Slaves which are marked in the DP-Slave
parameter set as not active.
- Stop_Slave_Handler.con
The Slave-Handlers additionally communicate with the user via the data
interface.
The Slave-Handler manages the individual states for every DP-Slave. The
following main states will be distinguished:
- diagnostic
- parametrization
- configuration
- data exchange
The user and the Slave-Handler communicate via the data interface using the
parameter a) to g):
Legend:
-r will only be read by the Slave-Handler and written by the User
-w will only be written by the Slave-Handler and read by the User
a) Active
(Sl_Flag.7) -r
Indicates whether the DP-Slave should be activated (=True) or not. In the second
case the state machine do not reach the state DATA.
b) New_Prm
(Sl_Flag.6) -r/-w
Indicates whether new parameter data are available for the DP-Slave.
c) Prm_Data
(Octet-String) -r
Parameter data of the DP-Slave. Structure see section "Send Parameter Data" of
the interface DDLM - User-Interface.