Specifications

B&K Components Device Interface Protocol (BKC-DIP) Specification

Version 2.01.00

Updated 01/24/07

Page 9 of 54

For example, the following two commands both yield the same checksum, 01DFh.

(00, G, P00; 01EA)

However, the following two commands yield different checksums because of the whitespace in the

second title:

(00, S, P1, 0="Title";04A6)

(00, S, P1, 0=" Title ";04E6) white space characters before and after Title

Tag Delimiter :

It is often useful to be able to determine which response from the B&K Component’s device

corresponds to a particular command issued by the host. To facilitate this, an optional tag may be

concatenated to the receive ID. This tag may be up to 8 alpha-numeric characters in length, and is

then concatenated to the transmit ID of the message(s) generated by the unit.

A few examples to demonstrate the use of the tag:

(0:1234wxyz, G, P3=1, 0;053D) Get Z3 Preset 1, parameter 0 with tag

1234wxyz

(0:1234wxyz,E,G,P3=1,053D;065A) Echo from unit with tag 1234wxyz

(0:1234wxyz,R,P3=1,0="His TV ";0897)Reply from unit with tag 1234wxyz

NOTE: The use of tags is optional. If no tag delimiter is detected in the received command, no

tag is appended in the response from the unit.

NOTE: Unlike V1.0 BKC-DIP, V2.0’s tag is 8 characters long, as opposed to only 4. Refer to

New Features of BKC-DIP V2.0 vs. V1.0 for details.

NOTE: Messages generated autonomously by the unit (such as “U” update commands) do not

have tags associated with them.

(0,U,I,1=24;0261) Update IR command Z1 of 24 (Volume +), no tag

NOTE: Unlike V1.0 BKC-DIP, colons are allowed in double quoted strings (such as text strings

as in "Colon : valid"). Refer to New Features of BKC-DIP V2.0 vs. V1.0 for details.