An instance of this function block type provides the device management
services described in subclause 3.3.2 of IEC 61499-1. The types and semantics of the
inputs and outputs of this type are identical to the correspondingly
named inputs and outputs of the
type defined in IEC 61499-1, with the following differences:
DSTinput designates the destination of the
RQSTinput as follows:
""(the empty string) designates the device;
"."character) indicates a resource in a containment hierarchy of resources, with the leftmost identifier corresponding to the outermost resource and the rightmost identifier corresponding to the innermost resource.
RESPoutputs are encoded according to the
Responseelements, respectively of the XML DTD given in subclause 6.4 of the Compliance Profile. The semantics of these elements shall be as defined in subclause 6.5.
REQ+primitive input always results in a
CNF+primitive output, since the actual result including failure conditions is encoded in the
RESPoutput. Similarly, a
REQ-input always results in a
CNF-output, since no management operation is attempted in this case. In particular, this means that, in an instance of the
DM_KRNLfunction block type, an
IND-primitive from the communication service interface will neither cause a management operation to be performed, nor will a response message be generated.
managerin the service sequences below is an instance of class
FBManagerdescribed in Annex C.2 of IEC 61499-1. This is the manager of the device or a contained resource depending on the value of the