Specifications

B&K Components Device Interface Protocol (BKC-DIP) Specification
Version 2.01.00
Updated 01/24/07
Page 45 of 54
Using the above example:
(from host) (01, G, P1=0, 1;0286) "G" get Z1 preset 00 command
from host destined for units with 01h receive IDs
(from unit) (1, E, G, P1=0, 0286;0366) "E" echoed get Z1 preset 00
command from unit with 01h Transmit ID
(from unit) (1, R, P1=0, 1=47;0309) "R" reply containing preset info
from unit with 01h Transmit ID
Another example would be in reply to a host get system:
(from host) (00, G, S;018D) "G" get system info command from host
from units with 00h receive IDs
(from unit) (2, E, G, S,018D; 02D9) "E" echoed get system info command from
unit with 02h Transmit ID
(from unit) (2, R, S, 0=...;cs16) "R" reply containing system info from same
unit with 02h Transmit ID
Replies also occur in response to get format requests from the host:
(from host) (00, G, F1=0;021E) "G" get Z1 preset format command
from host from units with 00h receive IDs
(from unit) (1, E, G, F1=0,021E ,0364) "E" echoed get preset format
command from unit with 01h Transmit ID
(from unit) (1, R, F1=0, 0=”D”...;cs16) "R" reply containing system preset
info from the same unit with 01h Transmit ID
Reply from the Get Display command (transmitID, G, D, d; cs16)
New to V2.0 BKC-DIP, there are now three different reply types: BKC-DIP V1.0 compliant,
BKC-DIP V2.0 with no attributes, and BKC-DIP V2.0 with attributes.
With the development of V2.0 BKC-DIP, there were two goals with regards to Get Display Reply
messages: minimize data transmitted and address the shortcommings of indicating the attributes
of the text from BKC-DIP V1.0. These design requirements are diametrically opposed, thus 2
reply modes are available in BKC-DIP V2.0 to address these differing goals: BKC-DIP V2.0
Compliant Display Reply without Attributes and BKC-DIP V2.0 Compliant Display Reply
with Attributes.
The reply format of each of these reply types will be discussed below, as well as pros/cons of each
type, plus the system settings required to enable each reply type.
The following documentation will assume the following On Screen Display buffer (currently Bh x
1Ch in size) content:
row 0=" CONTROL OUT B "
row 1="Input 1 On Input 2 On"
row 2="Input 3 On Input 4 On"
row 3="Input 5 On Input 6 On"
row 4="Input 7 On Input 8 On"
row 5="Input 9 On Zone In On"
row 6="FM Tuner On AM Tuner On"
row 7=" "