bk ck1.1 Guía Del Desarrollador
Purpose of Keypad ID Numbers
All CK1.1 Keypads have assignable Hex ID's. The factory default ID will be FF, as in the CK1.2 Keypads.The range of
IDs will be 0h-FFh. This will allow communication to multiple slaved keypads through the CT System. The purpose of
the Keypad Unit ID # is to enable specific keypads to be addressed via RS-232 communications.Thus you could have
a keypad in the Kitchen send a special B&K IR command to the CT Receiver, then the CT would in turn send a spe-
cific RS-232 message to each room’s keypad instructing each one to turn off the local TV in that room. Since each
room’s keypad has a unique ID#, they will only respond to the correct command.
IDs will be 0h-FFh. This will allow communication to multiple slaved keypads through the CT System. The purpose of
the Keypad Unit ID # is to enable specific keypads to be addressed via RS-232 communications.Thus you could have
a keypad in the Kitchen send a special B&K IR command to the CT Receiver, then the CT would in turn send a spe-
cific RS-232 message to each room’s keypad instructing each one to turn off the local TV in that room. Since each
room’s keypad has a unique ID#, they will only respond to the correct command.
1. UPPER CASE ASCII characters are required to communicate serial information from the source of RS-232
to the keypad.
to the keypad.
2. The baud rate for all CK1.1 keypads (1.2 as well) is 9600.This insures proper communication between the
source of serial information and the keypad(s).The keypad shall ignore any serial information at any baud rate
other than 9600.
source of serial information and the keypad(s).The keypad shall ignore any serial information at any baud rate
other than 9600.
3. Since "Main Pages" do not exist on the CK1.1, all buttons are required to be addressed under the heading
of "Device 0".Any serial string containing a reference to "Main Pages (Mx)" shall be ignored by the CK1.1 key-
pad. In contrast, any message containing a reference to "Device 0 (D0)", is ignored by a CK1.2 keypad. By
implementing the "Device 0" concept, it is possible to achieve independent control of both the CK1.1 and the
CK1.2 keypad, while still maintaining the same basic structured protocol.
of "Device 0".Any serial string containing a reference to "Main Pages (Mx)" shall be ignored by the CK1.1 key-
pad. In contrast, any message containing a reference to "Device 0 (D0)", is ignored by a CK1.2 keypad. By
implementing the "Device 0" concept, it is possible to achieve independent control of both the CK1.1 and the
CK1.2 keypad, while still maintaining the same basic structured protocol.
Defined Example: (also see page 44)
(0,K,D0,P2;) CK1.1 Keypad with receive ID of 0, jump to PAGE 2
(4 total pages on a CK1.1 keypad)
(FF,K,D0,P1,B41;) CK1.1 Keypad with a receive ID of FFh, press button 41
(button mapping follows).
Displaying text on CK1.1 Keypad
Basic text messages can be displayed on the CK1.1 bottom most text line. This is the same line that displays the
page number. Displaying text on line 7 (Y6) (maximum 7 characters long) will follow the same format as the CK1.2
keypad. Example BKC-DIP Format: (ID,K,L,Txx,X0,Y6,"1234567";).
page number. Displaying text on line 7 (Y6) (maximum 7 characters long) will follow the same format as the CK1.2
keypad. Example BKC-DIP Format: (ID,K,L,Txx,X0,Y6,"1234567";).
ID
= keypad hex ID.
K
= Keypad
L
= Literal line
Txx
= Time constant in Hex. 0 THRU 99 in tenths of a second.
Example: T64h * 100ms = 10 seconds
X0
= Only column 0 is supported
Y6
= Only row 6 is supported
“”
= Up to 7 Character text string. Must be UPPER case ASCII characters or #s.
Defined Example:
(FF,K,L,T64,X0,Y6,”HELLO “;) = Hello displayed for 10 seconds on all keypads.
(FF,K,L,T64,X0,Y6,”HELLO “;) = Hello displayed for 10 seconds on all keypads.
44
Type in Section Title
S
B
I M P LY
E T T E R !
B K
&
U
S
I
N
G
C
K
E
D
I
T
O
R
T
O
P
R
O
G
R
A
M
Advanced Programming Tips