Bosch DCN Next Generation Manuale Utente Scaricare il pdf (Pagina 27)

DCN Next Generation Open Interface Release 2.4 General

en | 27

Bosch Communications Systems | 2007 February | SRS_INF | Du010933

During the execution of that remote

function in the CCU, the internal

state of e.g. microphones changes.

This results in the generation of

update notifications, which are

transmitted to the remote controller

immediately. After the completion

of the remote function execution

the response of that function is sent

back to the remote controller. This

flow of messages to and from the

CCU is shown in Figure 5 (two

notification messages between the

request and the response).

The typical time between the request made and the response received is less than 0,5

seconds.

In the sequence described there is only one remote function request in execution on the

CCU. The remote controller waits for the completion of that remote function. The remote

controller can expect the following ending states of the remote request:

• The actual response of the remote function. The remote function is ended and there were

no transmission errors.

• The NAK packet. This implies that the CCU had a checksum error found after the

reception of the remote function request. The remote controller should respond on this

NAK message by sending again the same request.

• A time-out of the request pending. This means that the CCU does not respond any more.

The remote controller must wait upon the completion of his remote function request. But in

rare circumstance it is possible that there are two remote function requests pending. In that

case the CCU handles both remote function requests after each other (order is maintained).

4.4 Control flow with multiple remote controller’s

In a DCN NG-system as shown in Figure 1 (CCU with both a remote controller and the DCN

NG Control PC connected), there are up to three locations where events can be generated.

The locations are:

• The actual units. E.g. microphone keys, soft-keys (voting).

• The DCN NG Control PC connected using the RS-232 interface (or Ethernet in case of a

master CCU-NCO). This DCN NG Control PC uses Remote Function calls to trigger

functionality.

• The remote controller connected using the RS-232 interface (or Ethernet in case of a

master CCU-NCO). This Remote Controller also uses Remote Function calls to trigger

functionality.

To get a fully operational system both the DCN NG Control PC and the remote controller

must register themselves to the CCU, so they will receive update messages from the CCU.

Events coming from a unit are processed. During the processing, notifications are generated

and sent to all registered controllers. In the system mentioned above, both the DCN NG

Control PC and the Remote Controller will receive the same update notifications if they are

registered to the same application.

Remote functions coming from either the DCN NG Control PC or the Remote Controller

initiate a function in the CCU. During the function processing, notifications are generated and

sent to both the DCN NG Control PC and the Remote Controller. In this way both remote

controllers get the update information about the actions performed on request of the DCN NG

Control PC or the Remote Controller. (see also Figure 5).

Note that all remote functions are stored in a FIFO queue before execution. This means that

Remote Controller

CCU

Response

otif

Request

time

Figure 5 Message flow during a Remote function

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 295 296

Commenti su questo manuale

Nessun commento

Bosch DCN Next Generation Manuale Utente Pagina 27

Commenti su questo manuale

Prodotti e manuali riguardandi no Bosch DCN Next Generation