bk ck1.1 Developer's Guide

Utilize Save As to make a new file with a new file name. Use the concept of a template to save time in the on
future projects. A template file is simply a configuration file that you have preprogrammed to be used later on. All
files are saved with the file extension .mxf; all exported device files are saved with the extension .mxd. Be sure to
label your files appropriately. The CKEditor does not make any distinction between keypads or remotes.

Archive and save your customer files. In addition, you can export devices as .mxd files. Programming systems with
similar components gets even faster when you don’t have to redo your work over and over. You have your own ideas
about what buttons should be labeled and how they should be arranged. You’ll save all of your work in a unique and
time saving way by exporting the device stand alone.That way, you can import just the device in any new configuration.

Each keypad needs to have its program downloaded to it separately. If programming multiple keypads in a daisy
chain, be sure to program the first keypad in the chain first, and then the second so on. Otherwise error messages
will appear on the keypad screen.

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

By clicking the <CK1.1>
selection at the bottom of the
device drop down, you are
able to create buttons directly
onto the CK1.1

In this example, source but-
tons have been created for
the first page. Source buttons
have been created on the
remaining pages. Jump com-
mands can be added to any
button. The jump commands
will execute as the last step of

a macro or after a single hit IR command. Pages can be hidden while still allowing page jumps to bring you
to any page. Commands for each button must be dragged and dropped onto the CK1.1 Keypad simulator.
See next page.