B&K SR10.1, Руководство по программированию

Страница: 23 / 68

Using the IR Database
Discrete Codes, Toggles and other New Words
The B&K Editor database is unique in the industry because it includes “secret” discrete codes that are not on the
actual remote controls for many components. These codes are highly sought after by professional installers because
they make automation of the home theater possible via reliable macros! Here are the facts you need to know:
Discrete Commands versus Toggle Commands
When a remote control’s only button to turn on and off a TV set is labeled Power, it is usually a “toggle” command.
Test it by pressing the button twice. If the power button turns on the TV, then turns it off, it is a toggle command.
That is a big problem when you are programming macros! If you program a macro for watching TV with a toggle,
then the macro is essentially point and pray (if the TV was off, it will turn on, if it was already on, it will turn off). On
the other hand, if a macro is programmed with a discrete Power ON command, the macro will work every time (if
the TV was off, it will turn on, if it was already on, it will stay on).
So the term “discrete command” or “discrete code” means that the code will only do ONE THING to a component.
For example:
A single “Input” command is a toggle type command if it simply changes the input to another input when issued,
while separate buttons for Antenna A, Antenna B, Ext 1, Ext 2 and Ext 3 are discrete input commands if, when issued,
the TV goes directly to the named input (and if you give the same command again, it stays on the selected input).
Here are some important facts about Discrete commands:
“Secret” Discrete Codes exist for some components. Why are they secret? Because the manufacturer
wants the remote control that accompanies the component to have the simplest appearance (fewest buttons). Since
toggles reduce the number of buttons, they make the remote control appear easier to operate. Many manufacturers
understand the needs of custom installers and build their components to also respond to discrete codes. They
distribute the discrete codes via service remotes, etc. For the first time, those codes are collected and integrated
into our database.
Not all components respond to the discrete codes in the Database. A component has to be BUILT to
respond to discrete codes.The fact that other models from the same manufacturer do respond to discrete codes
is the reason the codes are added to a code set. However, some models will not respond, because the manufacturers
did not build it to respond through budgetary considerations, time constraints or a simple oversight.
Selecting a Code Set from the Database
1 Open the Database Window - Select IR
Database from the Program Menu or the Toolbar.
2 Select the Device - selecting it from the list box
as shown:
17 Step by Step Tutorial
S B
I M P LY E T T E R !
B K
&
T
H
E
B
&
K
A
U
T
O
M
A
T
E
D
T
H
E
A
T
E
R
TIP -
Start with the top Device first, so that after you
have programmed the first device, you can avoid
pulling down the menu again, simply tap the Next
Device button.