
DCN Next Generation Open Interface Release 2.4 General
en | 13
Bosch Communications Systems | 2007 February | SRS_INF | Du010933
3.2.1 Format of type MDSC_REMOTEPROCEDURE_REQ
Remote functions are messages, which are always transmitted to the CCU. The message
type must be equal to the value ‘MDSC_REMOTEPROCEDURE_REQ’.
The “message data” transmitted for a remote function follows the following format:
typedef struct
{
WORD wFnId; // function identifier
REQSTRUC tStructure; // function parameters if any!
} RSMT_REMOTEPROCEDURE_REQ;
where:
wFnId The function identifier.
tStructure A structure containing the parameters needed to process the
function defined by the function identifier (if any).
The ‘wFnId’ and the ‘tStructure’ are tightly coupled. Therefore the parameter structure is not
defined strictly with the basic types, but a special type is used to identify that the structure
depends on the function identifier.
The actual structure definition to be sent along with the remote function is not described in
this document. The structures are presented along with the definition of the remote function in
the interface documents for the application.
After the remote function request is sent to the CCU, the CCU will always
send back a
response upon the reception of a remote function (see §3.2.2). The remote controller should
wait for the response to be sure that the function ended successfully before sending another
remote function to the CCU.
Note that the CCU does not generate this kind of messages.
3.2.2 Format of type MDSC_REMOTEPROCEDURE_RSP
Upon a receipt of a remote function the CCU shall process the requested function and create
a response as result of that function. The message type will be equal to the value
‘MDSC_REMOTEPROCEDURE_RSP’.
The message data received for the response of a remote function follows the following
format:
typedef struct
{
WORD wFnId; // function identifier
WORD wError; // return error-code from the function
RSPSTRUC tStructure; // response information if any!
} RSMT_REMOTEPROCEDURE_RSP;
where:
wFnId The function identifier. The same value as passed with the
remote function request.
wError The return error-code of the function called. Note that if this
value is non-zero, the content of the ‘tStructure’ parameter is
not valid
4
.
tStructure A structure containing the response information after the
processing of the remote function (if any).
The ‘wFnId’ and the ‘tStructure’ are tightly coupled. Therefore the response information
structure is not defined strictly with the basic types, but a special type is used to identify that
the structure depends on the function identifier.
4
Upon error the ‘wError’ field is filled with an error code (see Appendix C), which references the source of the
error. Depending on the location of the error the ‘tStructure’ data may not be present. Therefore do not use the
‘tStructure’ data when ‘wError’ is not
equal to zero.
When the error code has not been described, the error must be reported.
Commenti su questo manuale