DCN Next Generation Open Interface

1 DCNNG Open InterfaceST/PRM3-EU | |14.Mar.07 © Robert Bosch GmbH reserves all rights even in the event of industrial property rights. We reserve all rights of

disposal such as copying and passing on to third parties.

Communications Systems DCN Next GenDCN Next Gen

DCN Next Generation Open Interface

Control a meeting using Open Interface

• Microphones• Voting• All room settings




Touchscreen Control

Activate Microphone

Touch panel and interface box + custom made software




Custom made SW for controlling DCN

Assigning applications Microphone control and mode selection Voting control and showing results Activating Attendance Registration




Page for selecting DCN voting modes




Control equipment from AMX & Crestron

www.amx.com www.crestron.com




How to handle

Bosch Security Systems BV is not supplying touch screen equipment. Contact AMX or Crestron dealer locally. React proactive. Select the dealer which has experience and is dealer

for Bosch and AMX or Crestron.




Synoptic Panel Control




Remote Controller with Single CCU

Authorization Code for Open Interface (LBB4187) needed. Register your CCU online together with the authorization code to get a license

key. Connect PC to Port 1 of the CCU

• Baudrate 115200• Protocol Full

Enter License key into the CCU using the Download and License Tool.

Download &LicenseTool




Remote Controller with Single CCU

Configure Port 1 of the CCU for Simple Protocol. Connect Open Interface Device to Port 1 of the CCU

• Baudrate 115200• Protocol Simple

Open Interface protocol ready for use.

Open InterfaceDevice

Open Interface




Open Interface Applications

(SC) System Configuration (SI) System Installation (DB) Database (MM) Microphone Management (VT) Voting (AT) Attendance Registration (MD) Message Distribution (IN) Simultaneous Interpretation (IC) Intercom (LD) Text Status Display (CC) Camera Control




System Structure

CCU

SISC DB MM VT IN MD AT IC LD CC

UnitsACN

Open Interface

RS232




Communication

The communication between the CCU and the remote controller is message based (remote functions and update notification).




Support & Information

DCN Open Interface (DOS) Tool (CCU_DDTK.EXE) Open Interface Documentation

• Protocol Description• Open Interface Commands




Open Interface Documentation

All information which is needed to make an Open Interface program is described in the Open Interface Documentation.




CCU_DDTK tool

DOS-based (also Windows DOS-Box) Uses Simple or Full protocol for communication

• Full has handshaking• Simple no handshaking

Definition file (fnid.def) with:• Names• Function number• Input and/or output structures




RS-232RS-232

System setup Open Interface Training

Del. with LCD& CR ID 4

Del. with LCD& CR ID 4

Del. with LCD ID 3

Del. with LCD ID 3

Del. withoutLCD ID 2

Del. withoutLCD ID 2

Chairman Unit ID 1

Chairman Unit ID 1

PCDDTK

DCN-CCUCentral Control Unit

DCN-CCUCentral Control Unit




Install the DDTK Toolkit• CCU_DDTK -PS -S1:19200

- Note : FNID.def file and CCU_DDTK.exe should be in the same folder.

Hands On




Collect System configuration• Use Open Interface document for SC-commands and

parameters explanation• Use following commands:

- SC_C_START_APP- SC_C_GET_CCU_VERSIONINFO- SC_C_GET_CCU_CONFIG

Practice 1 System Configuration




Fill DB with your name residing on a unit• Check it with MM Speakers info on LCD.• Use following commands to fill Database with one record:

- DB_C_START_APP- DB_C_MAINT_CCU_DB1 1 1 3 1 1 0 0 3 1 1 1 1 1 “Test”





Add your neighbor to another unit and do not give him voting authorization

• Check by running a voting round• Use Following commands:

- DB_C_CCU_APPLY_ONE 1 1 3 1 2 0 0 4 1 1 1 0 1 - DB_C_STOP_APP- SC_C_STOP_APP





Try behavior of SI functions :• SC_C_START_APP• SI_C_START_INSTALL 1 • SI_C_SELECT_UNIT 1 1 (turns Unit 1 on)

• SI_C_SELECT_UNIT 2 1 (turns Unit 2 on)

• SI_C_SELECT_UNIT 2 0 (turns Unit 2 off)

• SI_C_STOP_INSTALL• SC_C_STOP_APP

Practice 4 System Installation




Start MM on DDTK and check behavior Remote controller• Turn On/Off Microphone• Add delegate to request list• Change Max number of speakers• Change Microphone mode to override

• MM_C_START_MM• MM_C_SET_MICRO_ON_OFF 1 1• MM_C_SPK_APPEND 3• MM_C_RTS_APPEND 2 65535• MM_C_SET_ACTIVE_MICS 3• MM_C_SET_MIC_OPER_MODE 2• MM_C_STOP_MM

Practice 5 Microphone Management




Prepare YES/NO voting• End voting time = 10 seconds• Flashing secret response• Use present key for presence• No Notifications• Results not Compressed• Show result on stop voting

Practice 6 Voting




Suggestion

VT_C_START_APP 0 0 10

Preparation:• VT_C_SET_GLOBAL_SETTINGS 2 1 0 0 0 0 1 0 0 0• VT_C_SET_VOTINGPARAMS 1 2 0 0 1• VT_C_DOWNLOAD_SUBJECT 234 “Voting Test” “Mymotion”

Execution:• VT_C_START_VOTING• VT_C_HOLD_VOTING• VT_C_GET_RESULTS• VT_C_RESTART_VOTING• VT_C_STOP_VOTING 1• VT_C_GET_RESULTS• VT_C_STOP_APP




Protocol Layout

Header and Checksum are protocol dependent!

Header Message Checksum




Simple Protocol VS Full Protocol

Simple Protocol Checksum over messages No acknowledgement No retransmissions No line checking

• Controller can check use SC_C_CHECK_LINK function

Full Protocol Line checking

• Starts after first message Checksum over messages Acknowledge of message reception Retransmissions on failures

We will use Simple Protocol in this training!




Protocol Layout


The header has a fixed length and forms a leader to recognize the start-point of a message

• ESC value = 0x1B• ‘$‘ value = 0x24• CR value = 0x0D

ESC $ CR




Protocol Layout


Currently the following types are defined for communication with the CCU:

• MDSM_REMOTEPROCEDURE_REQ : Always transmitted to the CCU.

• MDSM_REMOTEPROCEDURE_RSP : Respons back from the CCU

• MDSM_NOTIFY : Notification from the CCU

Type Length Data




Protocol Layout


Type Length Data

Defines the actual length of the data present in the array following.

Only this amount of data of the ‘byData’ array is transmitted.




Protocol Layout


Type Length Data

The actual function (+ if necessary some parameters) or notification which has to be sent or received.




Protocol Layout


The Checksum is calculated using the following sequence:

• Sum all bytes over the header and the message.

• Take modulo 256 of the calculated checksum and do a bitwise invert of the checksum.

This calculated checksum is sent along with the packet. The receiver executes the same calculation and verifies the calculated checksum with the received checksum.

Checksum Byte




Packing a request message

Header ChkMessage

30 00

MM_C_SPK_APPEND

03

Type

04 00

Length

1C 00

28

ESC $ CR 60

1b240d03040030001c00==

09F9F

ChecksumCalculation

hex

Inverse 60




Unpacking a response message

Header ChkMessage

30 00

MM_C_SPK_APPEND

params03

Type

04 00

Length

00 00

Error code




Unpacking a notification

Header ChkMessage

05

Type

04 00

Length

0E 00

MM_C_SPK_APPEND_ON_PC 28

1C 00

Date post:	30-Dec-2015
Category:	Documents
Upload:	lesley-zimmerman
View:	111 times
Download:	12 times

DCN Next Generation Open Interface

Documents