fully Off through fully On and vice-versa. This allows their use in scripts for controlling things other than modules. REMOTE3 - Similar to REMOTE4 except that the On command is ignored by the state engine except for addressing the particular unit in the housecode it does not change the stored brightness level. The Off command does set the brightness level to zero and the Bright and Dim commands make incremental changes in this level within the range fully Off to fully On. (The Bright and Dim signals sent by RF remotes do not include a unit code. This module type allows using the On signal to address a particular unit without changing the stored brightness level and then using the Dim and Bright commands for some analog control purpose via a script.) REMOTEP - Again not actually a module, but can be used as a target for transmitters which send only the Preset (1-32) codes. SHUTTER (SW10) - Shutter and shade controller which support Extended Code Type 0 commands. The Marmitek SW10 Shutter Motor Controller is the only module known to support these commands and Marmitek keeps it a secret. This Heyu model supports Extended Type 0 functions 0x01, 0x02, 0x03, 0x04, and 0x0B. The Heyu model also supports the standard On and Off commands, but not Dim or Bright, to which the shutter module is reported to react in an unpredictable manner. VDATA - A virtual module which can store a data byte as if it were a (raw) brightness level 0-255. Data is written to this virtual module only with the heyu vdata HU <data> command - it is unaffected by any other X10 command. The following security transmitter models are included for use with RF auxiliary input from a W800RF32A or RFXCOM receiver. DS10A - (PDS01) X-10 DS10A Security Door/Window Sensor DS90 - (DS18-1) X-10 DS90 Sec Door/Window Sensor (2 chan) DS18-1 - () ElekHomica DS18 Sec Door/Window Sensor (2 chan) DS18 - () ElekHomica DS18 Sec Door/Window Sensor (1 chan) MS10A - (PMS01) X-10 MS10A Security Motion Sensor (See section "MS10A WARNING" in man page x10aux(5)) SH624 - (PSR01) X-10 Security Remote KR10A - (PKR02, KR21) X-10 Security Keyfob Remote. KR18 - (KR18E) Marmitek Security Keyfob Remote. SD10 - () Marmitek SD10 Smoke Detectors SD90 - () Marmitek SD90 Smoke Detectors BMB-SD18 - () BMB SD18 Smoke Detector MS90 - (MS18E) Marmitek MS90 Security Motion Sensor EH-CWSD10 - () ElekHomica EH-CWSD10 Smoke Detector
EH-WD210 - () ElecHomica EH-WD210 Water Detector GB10 - () Marmitek GB10 Glass Break Detector SVDATA - () Generic X10 Security Remote (all vdata) Most (but not all) security sensors transmit a 16-bit security ID which is detectable with the RFXCOM RF receiver operating in variable length packet mode (the default). For backward compatibility, the directive SECURID_16 NO instructs Heyu to ignore the upper 8-bits. Some security sensors, notably the Aux channel of the DS90 Door/Window sensor, have a rmware bug whereby a parity bit used to check the upper 8 bits of the 16-bit security ID is incorrect in every other RF repetition, which means that half the signals are discarded as noise. The conguration directive SECURID_PARITY NO instructs Heyu to disregard the parity bit. Its use is less risky than throwing away half the signals, but if none of your sensors exhibit this bug theres no need to use it. Conguration directive DISPLAY_RAW_RF NOISE can be used to determine whether the bug exists. Unlike the larger SH624 security remote, the smaller KR10A, KR18, and KR21 security keyfob remotes have no physical Away/Home or Max/Min switches, and by default transmit the swAway and swMin ags when the Arm button is pressed. Appending the parameters SWHOME and/or SWMAX to the alias directive for these keyfob remotes results in the ags being decoded respectively as swHome and/or swMax. Alternatively, appending the parameter DUMMY to the above security keyfob remote alias directive results in the signals transmitted by the Arm and Disarm button presses being decoded instead as Alert and Clear, thus allowing the remote to be used for a user-dened purpose unrelated to Arm and Disarm. Module type SEC_IGNORE can be used to ignore signals from X10 Security sensors which may not be under your control, e.g., signals from a nearby neighbors sensor. An unused Housecode/Unit address must be sacriced. Specify the Security IDs for one or more sensors to be ignored. Example: ALIAS Neighbor_Sensors P6 SEC_IGNORE 3C 4E 2A

The following entertainment transmitter model is included for use with RF Auxiliary input from a W800RF32A, RFXCOM, or MR26A receiver. UR81A - (UR61A) X-10 Entertainment Universal Remote. The following module types are used to override the settings dened by the TRANSCEIVE and RFFORWARD directives for specic units and functions within a housecode. Each requires one of the parameters TRANSCEIVE, RFFORWARD, or RFIGNORE be specied following the module name in the ALIAS directive. PALMPAD - Controls RF On, Off, Dim, Bright. KEYCHAIN - Controls RF On and Off ONLYON - Controls RF On ONLYOFF - Controls RF Off MS12, MS13, MS14, MS16 - Controls RF On and Off (The MSxx module types are similar to the KEYCHAIN module type but are dened as "sensors" and as such will be listed in the table displayed by heyu show sensors.) Example: If housecode C is set to be transceived, specifying: ALIAS XMMS_Control C1-6 KEYCHAIN RFFORWARD allows using the On/Off buttons C1-6 on a RF remote to launch scripts controlling the XMMS audio player software on the PC without the delay of a powerline signal. The other unit buttons continue to transceive powerline signals to lamps and appliances. PLCSENSOR - A target for a transmitter which sends X10 On and Off signals over the power line and which has a "heartbeat", i.e., it periodically retransmits its current state. The Heyu cong directives HIDE_UNCHANGED and INACTIVE_TIMEOUT apply to this module type as they do for
RF security sensors. The following module type decodes RF signals transmitted from RFXSensor modules and received by a W800RF32A/AE or RFXCOM RF receiver, and maps them to a Housecode|Unit address. RFXSENSOR - A decoder for RFXSensor transmitters and external sensors. Two parameters are required, the base_address of the sensor and a mnemonic for the type of sensor, e.g., Temperature/Humidity, Temp/Barometric Pressure, etc. The mnemonic will be one of: TH, TB, TV, TP, TT, or T. Example: ALIAS Basement L9 RFXSENSOR 0x20 TH The RF signals sent by the sensor with base_address 0x20 will be decoded as RFX Temperature and Relative Humidity functions received (RCVA) at Housecode|Unit L9. See man page x10rfxsensors(5) for full details. The following module types decode RF signals transmitted by RFXMeter sensors. Each requires as a parameter the ID address of the sensor. RFXPOWER - Electric Watt-Hour meter. RFXWATER - Water meter. RFXGAS - Gas meter. RFXPULSE - Pulse meter. RFXCOUNT - General counter. Example: ALIAS MyWaterMeter C9 RFXWATER 0x04 Module type DIGIMAX decodes RF signals transmitted by the DigiMax 210 wireless thermostat and received by the 433.92 MHz RFXCOM X10 RF receiver in variable length packet mode. Its parameter is the 16-bit ID of the thermostat. Module types ORE_xxx decode signals transmitted by various Oregon remote sensors and received by the 433.92 MHz RFXCOM X10 RF receiver in variable length packet mode. See man page x10oregon(5) for full descriptions. Module type ELS_ELEC1 decodes signals transmitted by the Electrisave CM113 Electricity Monitor sensor and received by the 433.92 MHz RFXCOM X10 RF receiver in variable length packet mode. The optional directive "ELS_VOLTAGE <voltage>" species a nominal AC voltage to be multiplied by the measured current to display an apparent power. See page X10oregon(5) for more information. Module type OWL_ELEC2 decodes signals transmitted by the OWL CM119 Electricity Monitor sensor and received by the 433.92 MHz RFXCOM X10 RF receiver in variable length packet mode. The directive "OWL_VOLTAGE <voltage>" species the nominal AC voltage to be used to compute the Power and Energy values. See page X10oregon(5) for more information. SwitchLinc and LampLinc modules can be manually congured to always turn on to some level less than the maximum (32), or always resume the previous setting. If youve congured your modules in either of these ways, you must inform Heyu of the fact by adding the module option ONLEVEL nn or ONLEVEL RESUME. NOTE: In order for the Heyu state engine to properly track the state of modules with the resume feature (LM14A and SwitchLinc/LampLinc option), its memory must be synchronized with the modules memory. This can be done by sending the module an X10 command setting it at a known level greater than the Off level, or by having it respond to a status request with a preset/xstatus level greater than the Off level. Examples: ALIAS hall_light B7 ALIAS patio_lights B2,4-6 ALIAS porch_light D1 WS467

ALIAS livingroom_lamp H7 SL2LM ONLEVEL 20 It is advisable to dene single-unit aliases for all housecode|units in addition to any multiple-unit aliases which may be convenient for use in Scenes/Usersyns/Macros, and to dene a Module_type only for singleunit aliases. (Once a Module_type is dened, it applies to that same housecode|unit however used, e.g., in the above example Heyu will understand that D1 is a WS467 dimmer when either heyu turn porch_light on or heyu turn D1 on is executed, or if D1 is also included in a multiple-unit alias like D1,2-5,7) Modules not dened for a Housecode|unit in an ALIAS directive are assigned to be the default module, which is a standard X-10 lamp module. This can be changed with the DEFAULT_MODULE directive. Note: Versions of Heyu prior to 2 used a different format for aliases: No ALIAS directive was used and the Housecode letter and Units were separated by whitespace, e.g., simply hall_light B 7. For compatibility, Heyu version 2 will still accept this format, however its use is discouraged and deprecated. (Module type cannot be specied with this format.)

DEFAULT_MODULE directive

Sets the module attributes of all Housecode|Units which are not dened in an alias directive. If not otherwise specied by this directive, the default module is the standard X-10 plug-in lamp module (StdLM).

START_ENGINE directive

Many of Heyus features require the Heyu state engine daemon heyu_engine to be running. This directive instructs Heyu how heyu_engine is to be started. With the default value of MANUAL, the engine must be started by entering heyu engine at the command line. With the value AUTO, the engine will be started automatically along with Heyus other background processes when heyu start is run. Example: START_ENGINE AUTO

LOG_DIR directive

Use this directive to specify the directory in which the Heyu state engine daemon should write its log le heyu.log.<tty>. The keyword NONE (which is the default) instructs Heyu to not write a log le. Example: LOG_DIR /var/log/heyu/ The log le will contain entries like appear in the Heyu monitor, and in addition, an entry whenever a script (excluding heyuhelper) is launched. It will also collect the text output of a launched script, if that output isnt redirected to a different le. Two or more instances of Heyu running on the same computer can share a common log le by appending the keyword "COMMON". If each instance of Heyu is started with the base subdirectory switch (-0 through -9), each entry in the log le heyu.log.common will display the subdirectory number (0 through 9) from whence the signal originated. Example: LOG_DIR /var/log/heyu common Note that the log le will continue to grow. Manually delete or trim it from time to time, or congure a Unix utility like logrotate to manage it.

DATE_FORMAT directive

Species how a numeric date is displayed. The syntax for this directive is: DATE_FORMAT <order> [<separator>] where <order> is YMD => Year/Month/Day (Default) DMY => Day/Month/Year
MDY => Month/Day/Year and where the optional <separator> is / (Default), -, or. Examples: DATE_FORMAT DATE_FORMAT DATE_FORMAT DATE_FORMAT DATE_FORMAT YMD YMD DMY DMY MDY / => 2008/01/23 (Heyu default) - => 2008-01-23 (ISO 8601 standard) - => 23-01-2008 (many European countries). => 23.01.2008 (Germany traditional) / => 01/23/2008 (USA traditional)
The specied order of Month and Day also applies to the date ranges specied for Timers in schedule les to be uploaded to the CM11A EEPROM. The separator between month and day must be /, - or. but does not have to be the same as that specied with DATE_FORMAT. The separator between the begin and end dates may optionally be either - or :. (Use the latter for clarity when the Month/Day separator is a -.) Examples: TIMER smtwtfs 01/23-12/31. (with DATE_FORMAT YMD or MDY) TIMER smtwtfs 23-01:31-12. (with DATE_FORMAT DMY) Dates where the month name is spelled out are not affected by this directive and usually appear like: Wed 23 Jan 2008

LOGDATE_YEAR directive

Instructs Heyu whether or not the dates reported for entries in the Log le and Monitor should include the year. The choices are YES or NO, with the default being NO, to omit the year.

TAILPATH directive

Use this directive to specify the full pathname of the system tail command if its not on the normal PATH accessable to Heyu. The Heyu command logtail will use this pathspec to call tail.

HEYU_UMASK directive

Governs the permissions for les created by Heyu. The default for this directive is 0000 which results in les having permissions rw_rw_rw_. The value 0002 results in les having permissions rw_rw_r__ ; the value 0022 results in les having permissions rw_r__r__. Example: HEYU_UMASK 0002

TempLinc Model 1625 remote thermometer can be programmed to transmit a temperature report any time the temperature changes.)

ACK_HAILS directive

Setting this directive to YES will instruct the Heyu state engine daemon (if running) to send a hail_ack with the default housecode whenever it receives a hail signal over the power line. The hail_ack is sent as if from a launched script. The choices are YES or NO, with the default being NO. Example: ACK_HAILS NO

AUTOFETCH directive

When a state command which returns the addressed state of a module is executed at the command line, Heyu by default (AUTOFETCH YES) instructs the state engine to rst update the state le, since Heyu only automatically updates this le following an X10 function. Setting the value of the directive to NO disables this action for (only) those specic state commands. Most users will want to accept the default value of YES. See the description of the fetchstate command in man page heyu(1) for a more detailed discussion of this issue.
TIMER_LOOPCOUNT directive
Species the base loopcount for the fast timing loops needed by some CM17A and experimental commands. To determine the value for this directive, run heyu utility calibrate.

FORCE_ADDR directive

Heyu doesnt normally send a separate Housecode|Unit address byte for commands like all_lights_on which dont actually require the unit number (the housecode is included with the function), or for extended commands which contain the unit number within the function code. However X-10s ActiveHome software always sends this byte, generally using unit 13. This directives forces Heyu to always send an address byte. If always sending an address byte cures some problem you are having, choose YES. Otherwise take the default of NO. Example: FORCE_ADDR NO

SPOOLFILE_MAX directive

This directive sets the limit on the size of the spoolle beyond which the Heyu relay daemon will rewind it once it detects a period of inactivity (currently 5 seconds). The size set by this directive may be between 20 and an absolute maximum 1048576 bytes (but dont use this max value). The default limit is 1000000 bytes. For changes in this directive to become effective when Heyu is already running, use the heyu restart command. Note that re-synchronization with the Heyu state engine daemon or monitor takes a couple of seconds, during which time Heyu will ignore incoming X10 signals or macro executions. So dont set a low limit except for testing purposes.

SCRIPT_CTRL directive

Globally enables or disables launching of scripts by Heyu. The default value of ENABLE permits scripts to be launched; the value DISABLE inhibits them from being launched. This will hopefully be useful when the conguration le contains many SCRIPT directives and it is desired to temporarily disable them without having to delete them or comment them all out. All scripts are affected, including heyuhelper and powerfail or rfood scripts. (This directive may be overridden at the command line by the heyu script_ctrl enable|disable command.)

SCRIPT directive

Species the Linux/Unix command to be launched and the conditions under which it will be launched. The conditions for launching the command may also (or additionally) be specied separately in a LAUNCHER directive. The format is as follows: SCRIPT [-l <label>] <launch conditions> :: [exec options] <command line> The script label is optional as long as the all the launch conditions are contained within the SCRIPT line. It can be any arbitrary case-sensitive name up to 32 characters in length, not beginning with a - character. If no label is specied, Heyu will create one using the line number where it appears in the cong le to make it unique, e.g., Script_21. If the launch conditions are wholly or in part specied with a LAUNCHER directive, a script label is mandatory, so that Heyu can match up the script with the assocated launcher.
Launch conditions can be quite simple, like A1 on, or quite complex. In addition, there are special launch condition for extraordinary situations: powerfail, -rfood, -timeout. See x10scripts(5) for a full description of launch conditions. Keep in mind that Heyu will normally launch a script only for the rst set of launch conditions which are satised, i.e., only one script is launched per signal or special condition, although this restriction can be overridden. Launch conditions are tested in the order they appear in the conguration le. The symbol :: (two colons) is always required (so that Heyu can distinguish when the launch conditions end and the command line starts). Exec options are zero or more of the following: -xtend (or simply -x) Create an environment compatible with Xtend scripts. (No other options are compatible with -xtend.) -rawlevel (or simply -r) Use native raw dimlevels instead of percentages for state bitmaps in the Heyu environment. -noenv (or simply -n) Provide no additional environment variables beyond those already in the users environment. The <command line> can be any executable binary, shell script, or shell command. Examples: SCRIPT SCRIPT SCRIPT SCRIPT SCRIPT

D1 on :: doorbell_actions.sh -l wake_em_up C1 on :: play $HOME/music/reveille.wav -l PowerFail -powerfail :: echo "There was a power failure" | mail -l RF_Flood -rfood :: heyu on Siren -l Timeout -timeout timer2 :: echo "Timeout on Timer number 2" | mail
If a script directive references an alias in place of a housecode|unitcode, the alias directive must have been dened earlier in the conguration le.

LAUNCHER directive

This optional directive can wholly or in part specify the condition or conditions under which the associated script will be executed (or launched). The format is: LAUNCHER <script label> <launch conditions>; <launch conditions>;. where: <script label> identies the associated script with the same label. See x10scripts(5) for a full description of what can appear in <launch conditions>. Multiple launchers for the same script may be continued on the same line following a semicolon, or may be congured as separate LAUNCHER lines. Example: If no launch condition was specied in the wake_em_up script above, it would be specied in a launcher like this: LAUNCHER wake_em_up C1 on
LAUNCHER_SCANMODE directive
See section "SCAN MODE" in man page x10scripts(5) for details.

SCRIPT_SHELL directive

Denes the shell used when a script is executed. (Provide the full pathname.) The default is to use the shell dened by the SHELL variable in the users environment, or /bin/sh if no such variable exist.
LAUNCHPATH_PREFIX directive LAUNCHPATH_APPEND directive
Prex and/or append an additional directory or directories to the existing $PATH in the environment provided for Heyu scripts. (This works only for shells where the path separator is a semicolon.) Example: LAUNCHPATH_APPEND /etc/heyu/scripts

LAUNCH_SOURCE directive

Sets the default source or sources of the X10 signal allowed to launch a script as part of the <launch conditions>. One or more of the following may be specied. The default is RCVI. SNDC Sent from the Heyu command line. SNDM Sent upon execution of an uploaded macro by a Timer. SNDT Sent upon execution of an uploaded macro by a Trigger SNDP Sent by Heyu from a power-fail script. RCVI Received over the power line via the CM11A interface. RCVT A Trigger which initiates execution of an uploaded macro. SNDA Sent over the power line by the heyu_aux daemon. RCVA Virtual data received from the heyu_aux daemon. ANYSRC All of the above. NOSRC None of the above (sources must be specied in the <launch conditions>). Example: LAUNCH_SOURCE rcvi sndc

ISDARK_OFFSET directive

Denes the offset in minutes from Dusk and Dawn to use for the script environment logical variable X10_isDarkTime. Its default value of 30 minutes means that X10_isDarkTime will be TRUE from 30 minutes after Dusk until 30 minutes before Dawn. This directive also determines the interval during which the launch condition ag dark is TRUE.

MODE directive

Heyu can operate in one of two modes insofar as uploaded timers and macros are concerned. But before getting into these, rst a few words about the CM11A interfaces internal clock: The CM11A clock has no notion of actual dates, but is merely a day counter which starts from 0 and increments daily until it reaches 365 (a total of 366 days), after which it rolls over to 0. An independant counter keeps track of the weekday, starting at 0 (Sunday) and incrementing daily through 6 (Saturday) before rolling over to 0. Additional counters track hours, minutes, and seconds with the usual rollovers. (The CM11A has no notion of Standard versus Daylight Time.) The day and weekday counters increment when the time rolls over to 0:00:00. In either mode, the CM11A clock is maintained by Heyu on Standard Time thoughout the year. Timers scheduled by the user in Civil (i.e. wall clock) time are automatically divided by Heyu into separate timers for periods of Standard and Daylight Time during the year. Time management is intended to be handled by Heyu transparently to the user. In COMPATIBLE mode, the CM11A clock is congured such that Day 0 corresponds to Jan 1st in the current year and the uploaded schedule of timers and macros is prepared to run for 366 days, i.e., through either Dec 31st or the following Jan 1st, depending on whether the current year is a leap or common year. In order to maintain the proper correspondence, the users schedule must be re-uploaded on Jan 1st, at least in years following common years. (The CM11A will otherwise keep chugging away, but events red off will be a day in error.) In HEYU mode, the CM11A clock is congured such that Day 0 corresponds not to Jan 1st but to todays date. The uploaded schedule can be congured to run for any period between 1 and 366 days via the PROGRAM_DAYS directive. (See the description of that directive for reasons for wanting this.) The users schedule can be re-uploaded at any time prior to expiration of the PROGRAM_DAYS period and correspondance will be maintained for the next period of PROGRAM_DAYS. Note however that if this period is allowed to expire without re-uploading the schedule, the CM11A will cease to re off any programmed events (unless of course the period is set for 366 days). The schedule should be programmed for the entire year regardless of the MODE or PROGRAM_DAYS
directives. Based on those directives, Heyu determines what parts of it to use and what parts to ignore. In HEYU mode, events scheduled for execution on dates earlier than todays date wrap around into next year. Examples: MODE COMPATIBLE MODE HEYU *** WARNING - WARNING - WARNING *** Users running PCs congured for dual-boot between Linux and MS-Windows should NOT operate Heyu in HEYU mode if they expect to ever manually execute X-10s ActiveHome(TM) program (or allow its "Communications Bridge" driver to be launched at boot time). Heres why: If the CM11A detects that its AC power has been interrupted, even for a very short time, it will continually issue commands back to the PC requesting a clock update. ActiveHome and/or its Communications Bridge will _silently_ comply with this request (as will Heyus Relay), but ActiveHome will set the CM11A clock to an incorrect date and time for HEYU mode. (This is easily and automatically corrected by running the heyu setclock command, but the PC has to be rebooted back into Linux/Unix to do it.)

DAWNDUSK_DEF directive

By default Heyu denes Dawn and Dusk to be Sunrise and Sunset. This directive allows globally dening them instead as the morning and evening times of several standard twilights, as follows: RISESET (or simply R) - Sunrise and Sunset (default) CIVIL (or simply C) - Civil Twilight NAUTICAL (or simply N) - Nautical Twilight ASTRONOMICAL (or simply A) - Astronomical Twilight Example: DAWNDUSK_DEF CIVIL DAWNDUSK_DEF N
DAWN_OPTION directive DUSK_OPTION directive
These directives instruct Heyu how to assign the time for Dawn or Dusk in each timer subinterval. The options for this directive are: FIRST - Use the Dawn/Dusk time for the rst day in the subinterval. EARLIEST - Use the earliest of the times for any day in the subinterval. LATEST - Use the latest of the times for any day in the subinterval. AVERAGE - Use the arithmetic average of the times in the subinterval. MEDIAN - Use a time halfway between the earliest and latest times. The default is FIRST, which is the most convenient for comparing Heyus computations with Dawn/Dusk times published in newspapers or by the US Naval Observatory. (Remember that Heyus times are Standard Time, while newspapers generally publish Civil [wall clock] times.)
MIN_DAWN directive MAX_DAWN directive MIN_DUSK directive

MAX_DUSK directive

These directives allow bounds to be placed on the times of Dawn and Dusk computed by Heyu. For example, setting the value for MIN_DAWN to 06:30 will instruct Heyu to execute a timed event scheduled for dawn at 06:30 instead, whenever the computed time for dawn is earlier than 06:30. These directives may be useful for users in extreme latitudes, when for example a lamp is scheduled to turn on at dusk and turn off at 9:30 PM. But if during the summer months dusk actually occurs after that hour, then the on/off cycle of the lamp would normally be reversed, turning on at that late dusk and remaining on until 9:30 PM the following day. The value for these directives are specied as hh:mm Civil (i.e., wall-clock) time. The directives may be disabled with the word OFF in place of a time. The default is OFF. Heyu version 2 now has timer options for conditional compilation of events depending on the values of Dawn and Dusk, so these directives may no longer be useful. (Note: Due to Heyus optimizations, the order in which events scheduled for the same time are actually executed is not necessarily that in which they appear in the users schedule le. Allow at least a one minute time difference when order is important. The actual order can be determined from the list of timers in the OUTPUT TIMERS section of the report.txt le written when a schedule is uploaded or upload checked.)

DAWN_SUBSTITUTE directive DUSK_SUBSTITUTE directive
These directives are obsolete and will be ignored.

REPORT_PATH directive

Reports report.txt and/or cronreport.txt created when the command heyu upload [check|croncheck] is run are by default written in the Heyu base directory, i.e., the directory where the conguration le is stored. This directive instructs Heyu where the user would like them written instead. The full pathspec is required (127 characters maximum). Example: REPORT_PATH./
WRITE_CHECK_FILES directive
When a schedule is actually uploaded to the CM11As EEPROM, Heyu records critical information in the les x10record, x10macroxref, and x10image. For debugging or informational purposes, this directive instructs Heyu to write these les with a.check extension when heyu upload check is run. In addition, this directive instructs Heyu to write x10image.hex which is a human-readable hex dump of the EEPROM memory image. The choices here are YES or NO. The default is NO.
REPL_DELAYED_MACROS directive
This directive instructs Heyu to replace events having delayed macros with new events and new undelayed macros when possible. (The purpose is to avoid pending delayed macros, which are purged when a new schedule is uploaded.) The choices are YES or NO, with the default being YES.

ASIF_DATE directive

Used for test purposes, this directive instructs Heyu to substitute the argument date for todays date when processing the users schedule le. The date format is yyyymmdd. Example:

ASIF_DATE 20020621

ASIF_TIME directive
Used mainly for test purposes, this directive instructs Heyu to use the argument time of day instead of the system time when processing the users schedule le. Its format is hh:mm (Civil Time). The default is to use the current system time. Example (simulates operation at Noon): ASIF_TIME 12:00

FEB_KLUGE directive

Heyu ver 2 always interprets 02/30 as the last day of February when used as a start or stop date. This directive instructs Heyu to also interpret 02/28 and 02/29 as the last day of February. The options here are YES or NO, with YES being the default. (If you choose NO, programming 02/28 or 02/29 in the wrong year could result in a skipped day, an event occurring twice, or possibly an error, depending on circumstances.)

=============================================== The following directives provide controls for RF input to Heyu from the auxiliary port daemon heyu_aux. Theyre more fully explained in man page x10aux(5). ===============================================

TTY_AUX directive

Specify the auxiliary serial port and RF receiver device. TTY_AUX <serial port> <receiver device> where <receiver device> is W800RF32A, MR26A, or RFXCOM. Example: TTY_AUX /dev/ttyS1 W800RF32A There is no default for this directive.
SUPPRESS_RFXJAM directive
Older rmware versions of the RFXCOM receiver sent a special "jamming" signal when they detected RF jamming, but the system was prone to many false positives and the feature was removed. This directive allows suppressing the jamming signals from older RFXCOM versions by treating them as RF Noise. The options for this directive are YES or NO, with the default being NO.
For RF signals received by the W800RF32A from security remotes and sensors, this ALIAS format maps the device to a housecode|unit address. ALIAS <label> <housecode|unit> <device model> <ID> [<ID> [<ID>.]] where <ID> represents the security ID of a device expressed as a hexadecimal number, either with or without the "0x" prex. Up to 16 security IDs can be associated with a single housecode|unit address in the case of multiple security remotes of the same model. (Each sensor device should be mapped to its own address.) Examples: ALIAS kitchen_door F11 DS10A 0x3c ALIAS keychain_remote G8 KR10A 2a b4 c7 The ID for entertainment remotes like the UR81A is xed and included in the model, so isnt specied with the ALIAS directive.
TRANSCEIVE directive RFFORWARD directive
Determine which housecodes which are to be transceived to power line code (source SNDA) by the heyu_aux daemon and which housecodes are forwarded directly (source RCVA) to the heyu_engine daemon for launching scripts or whatever. These applies only to signals from Standard X10 remotes, not security or entertainment remotes. TRANSCEIVE <list> RFFORWARD <list> where <list> may be the keywords ALL or NONE, or may be a string of housecode enclosed in square [] brackets. Additionally, the keyword ALLEXCEPT followed by the housecode string in square brackets may be used. Example: TRANSCEIVE [BFH] RFFORWARD [DE] which will transceive standard X10 RF signals on housecode B, F, and H, and forward X10 RF signals on housecodes D and E. RF signals on all other housecodes will be ignored. Another example: TRANSCEIVE [BFH] RFFORWARD ALLEXCEPT [BFH]
The default for the TRANSCEIVE directive is ALL, and for the RFFORWARD directive is NONE, meaning that signals on all housecodes will be transceived. The same housecode cannot be both transceived and forwarded. Certain special module types have options to override the TRANSCEIVE and RFFORWARD lists for specic units and functions within a housecode.

TRANS_DIMLEVEL directive

This directive species the dim level (1-22) for each RF Dim or Bright signal transceived (or forwarded) by heyu_aux. The default level is 2 which results in a brightness level change of about 6 percent in standard X-10 Lamp Modules. Example: TRANS_DIMLEVEL 2

AUX_REPCOUNTS directive

This directive instructs heyu_aux how to handle multiple bursts in an uninterrupted sequence by providing 3 numbers: AUX_REPCOUNTS <MIN> <REPEAT> <MAX> See man page x10aux(5) for details. Most users wont need to change the defaults (200) for this directive.

DISPLAY_RAW_RF directive

This directive instructs Heyu whether or not to display the raw RF data bytes from the receiver device. The choices are the default "NONE" to not display any raw data, "NOISE" to display data which heyu_aux judges to be RF noise, or "ALL" to display both noise and normal raw RF data. Only change from the default for testing or debugging.

SECURID_16 directive

This directive determines whether Heyu will use the full 16-bit ID of security sensors when received by a RFXCOM receiver in variable length packet mode. It is provided primarily for temporary backward compatibility in case the user has a large number of sensors congured with 8-bit IDs, until they can be recongured. The parameters are YES or NO, with the default being YES. The ID of a security device which transmits only an 8-bit ID is taken to be the lower byte of the 16-bit ID.

SECURID_PARITY directive

Security sensor transmissions include a parity check on the upper 8-bits of a 16-bit ID. Some sensors, notably the Aux channel of the DS90 Door/Window sensor, incorrectly report the parity on half of the RF repetitions. This directive with parameter YES (which is the default) instructs Heyu to check the parity. The parameter NO instructs Heyu to ignore the parity. Use NO only if you have a sensor exhibiting this bug.

HIDE_UNCHANGED directive

This directive applies only to transmitters identied by their module type as having a "heartbeat", i.e., sensors which periodically repeat their current state as an "I am alive" indication. The choices are YES or NO, with the default being NO. With YES, the sensor signal is displayed in the monitor and log le only when theres a change from the previous state of the sensor or if the signal launches a script.

HIDE_UNCHANGED_INACTIVE directive
As above, but for the "func Inactive" pseudo_signal.

ORE_LOWBATTERY directive

Denes for Oregon sensors which transmit a battery level the percentage at or below which Heyu will raise the low-battery ("LoBat") ag. The default is 20%. Note that many Oregon sensor models transmit a low battery indicator rather than a battery level, and for these models this directive has no effect. Example: ORE_LOWBATTERY 10%
ORE_CHGBITS_T directive ORE_CHGBITS_RH directive ORE_CHGBITS_BP directive
Dene for Oregon Temperature, Relative Humidity, and Barometric Pressure sensors the difference between succesive data values required for the data value to be identied as "changed". The parameter is the number of least counts for the data in question. The default for each is 1. See man page x10oregon(5) for details.
ELS_CHGBITS_CURR directive
Dene for the Electrisave sensor the difference between successive current values required for the data to be identied as changed. The parameter is the number of least counts for the data. The default is 1, which corresponds to 0.1 Ampere. See man page x10oregon(5) for details.
OWL_CHGBITS_POWER directive OWL_CHGBITS_ENERGY directive
Dene for the Owl CM119 sensor the difference between successive Power and Energy values for the data to be identied as changed. The parameter is the number of least counts for the data in question. The default for each is 1, corresponding to 0.001kW and 0.0001kWh respectively. See man page x10oregon(5) for details.
OWL_DISPLAY_COUNT directive
Determines whether the raw data is displayed in the monitor/logle for Owl CM119 sensors. The parameter choises are YES or NO, with the default being NO.

ORE_DATA_ENTRY

Denes whether data is entered in Oregon native or scaled units for Oregon sensor emulation. The parameter choices are NATIVE or SCALED, with the default being NATIVE. See section "OREGON SENSOR EMULATION" in man page x10oregon(5) for details.
ORE_DISPLAY_CHAN directive
Determines whether the channel number of an Oregon sensor is displayed in the logle, monitor, and heyu show oregon table. Setting the parameter of this directive to NO suppresses display of the channel number, while with the default YES the channel number is displayed.

Installation Instructions Dacor Kitchen Entertainment Center
save and read these instructions CONVENTIONS USED IN THESE INSTRUCTIONS
WARNINGS: Must be followed carefully to avoid personal injury or damage. NOTES: 1. 2. 3. 4. 5. Contain helpful hints and tips to facilitate the installation. IMPORTANT Before beginning installation, please thoroughly read and become familiar with these instructions. Installation and service must be completed by a qualified installer or service agency. Installer: Please leave these Installation Instructions with the owner. Owner: Please keep these instructions for local electrical inspectors use and for future reference. Read the accompanying Use & Care Manual prior to operating this appliance.

TABLE OF CONTENTS

Installing the DKEC Getting started Verifying package contents Tool checklist Route the cables Prepare the site Connectivity template Position the bracket Mount the DKEC Install the batteries Power up Internet connection information Video mode Registering a new DKEC

Part No. 65514 Rev. B

Page Page Page Page Page Page Page Page Page Page Page Page Page
INSIDE FRONT COVER THIS PAGE IS BLANK INTENTIONALLY

Getting Started

The first question new DKEC owners need to ask is,Where should I install my DKEC? The installer and home owner should discuss the question to come up with a mutually satisfactory solution. The choice of where to locate the DKEC is a very important one. The DKEC is designed for the kitchen environment. To get the maximum benefit from the product on a daily basis, consider the following details: Most kitchens have a work triangle as defined by the sink, the refrigerator and the stove. This is where people typically spend most of their time while in the kitchen. Consider how the unit will most easily be viewed, taking into account that the display can pivot 60 degrees to either side of center. How much light from sources such as windows will fall directly on the screen? Uncontrollable light flooding the screen can make it difficult to view content on the DKEC screen. Dont install the DKEC above a stove, a coffee maker, sink, dishwasher vent or any other location that will subject it to high heat and/or humidity. The installer will need to get the necessary wiring to the unit. Careful consideration needs to be given to how the installer plans to run and conceal the wires. Consideration should be given to suitable locations for the junction boxes where wires will terminate behind the unit. Before beginning the installation of the DKEC the installer should: Read through all installation instructions. Make sure all peripheral connections are available at the installation location (TV cable, electrical power, connections to security locks, video monitor, phone line, or Broadband). Seek additional information from other sections of this document including Internet Connection Information and Video Mode sections.

Tool Checklist

The following tools may be necessary for installing the DKEC: Drill and drill bits Standard and Phillips head screwdrivers Small standard screwdriver Wallboard saw or knife Center punch or awl RJ45/RJ11 crimping tool RG6 - f connector - stripping/crimping tool Masking tape Tape measure Pliers Zip ties
Note: If you are installing the DKEC in a site that has structured wiring, see Internet Connection Information for more information. Also see Connectivity Template on page 3 for suggested termination layout. Prepare the Site

The two most common installation configurations for the DKEC are shown below. The minimum space required is also shown. It is advisable that the DKEC installer consult with the kitchen cabinet installer to ensure that the site is properly prepared prior to the installing of the DKEC. Selecting a suitable site for installation: Avoid areas where the DKEC would be exposed to extreme heat or moisture. Allow a full 11 of horizontal space (front to back), accounting for backsplash and trim if necessary. The mounting surface must be flat and level. The cabinet material must be at least thick and able to support 30 lbs. When installing the unit, allow sufficient vertical space above the countertop to accommodate screen in lowered position. The minimum distance required is 13.
Note: Mounting screws are NOT included with the DKEC. While we recommend the use of six 5/16 T-nuts and screws, it is impossible to predict the length of screws needed for a particular customers installation. WARNING: Installation of this device should be performed by a professional. Proper installation requires ensuring that the supporting unit can bear the weight of the device, that all mountings are secure and that electrical and telephone wiring meets local building codes, and that all mounting instructions are followed. IMPROPER INSTALLATION COULD LEAD TO PROPERTY DAMAGE, SEVERE PERSONAL INJURY OR DEATH. Dacor disclaims any and all liability for damages and/or injury resulting from improper installation. Route the Cables
The following is the full list of cables that may need to be run to the installation site. Each installation site will require different configurations depending on how the DKEC will be used. RG6 cabling with a coaxial cable connector (F-style) for the cable TV service. S-Video cable Analog signal cable, left and right channel with RCA connectors for audio input or output (these are separate from the connectors for the internal speakers). RCA Composite video cable AC power cables with a ground should be routed to within 3 of the top of the installation site to hide cables from view. Telephone wire with the RJ11 connectors for Dial-Up Internet access. -or CAT 5 wire with an RJ45 connector for Ethernet connection.
3 3/4 (97mm) 13 (330mm) 10 13/16 (275mm) 23 5/8 (600mm)
Verifying the Package Contents
DKEC unit Use and Care Manual Washable, wireless keyboard Two (2) AA batteries for keyboard Washable, wireless remote Two (2) AAA batteries for remote Two (2) Styli AC Power Cord Right Angle F connector. PCMCIA Ethernet Card Mounting Bracket Mounting Template Connectivity Template Quick Start Guide Remote and Keyboard Guide
Shown in a Custom Built Nook
23 5/8 (600mm) 13 (330mm) 10 13/16 (275mm) Shown Under a Standard Flat Cabinet Surface

Connectivity Template

The Connectivity Template included with the DKEC suggests how the unit could be wired under ideal conditions. It enables the installer to determine ahead of time where to place the junction boxes and outlets. Keep in mind, however, that the existing wall contains structural studs. The location of these studs will dictate what kind of junction boxes can be used and where they can be placed. There is no guarantee that the layout suggested by the Connectivity Template will work as is for each particular situation. Place the template on the wall area behind the location for the unit. It should be located such that the center line of the template (see marking on template) is aligned with the desired center line of the DKEC unit. Note that the images on the Connectivity Template include the outline of the DKEC unit itself.

Position the Bracket

Position the Mounting Template in the desired location. If the bottom surface of the kitchen cabinet (where the bracket is to be mounted) is recessed from the bottom of the kitchen cabinet frame, you will need to bring the bracket and the cabinet into alignment. This should be done using furring strips at the locations of the mounting screws. For reasons of aesthetics, also note where the bottom of the DKEC unit itself will be when the unit gets installed into the bracket. In cases where the unit is installed into a custom nook, the bottom of the DKEC should align with the bottom surfaces of the adjacent kitchen cabinets. Using the template, make sure that the bracket will be mounted such that the vertical face of the DKEC unit will be flush with or just slightly recessed back from the vertical face of the cabinets. Leave adequate clearance in the rear for electrical/electronic connections. Tape the Mounting Template in position, then mark the locations of the 6 mounting holes. Use an awl or nail to create a center mark in each mounting hole. Remove the template.
Attaching the Unit to the Mounting Bracket
Before securing the unit, plug the cables into the appropriate connectors as indicated on page 4. Loosen the two screws on the bracket in order to receive the two slotted tabs along the rear edge of the unit. Slide the DKEC unit into the bracket. The tabs should fully engage the pins (B, as shown above). Using a screwdriver, tighten the screws on the mounting bracket, alternating between the two screws until the tabs are secure (C, as shown above). When installation is complete, the face of the unit should be flush with, or slightly recessed from the face of the cabinets.

Positioning the Connectivity Template
The template can be held in place with masking tape. Make sure that the template is right side up on the wall (look for the Top arrow). Option A Based on the Connectivity Template the following items are recommended for the actual wiring of an DKEC unit: Recommended Products: Two Siemon Home Recessed Wall plates, From the Angled MaxTM Tool less line, Part number MX-TFP-S-06-25 Five recessed RCA connectors for the audio and video connections, Siemon Home part number MX-RC-25 One F connector, for radio and television reception, Siemon Home part number MXFA-25 One RJ45 connector for the Ethernet connection, Siemon Home part number MX5-F25 One RJ11 connectors for a Dial Up connection, Siemon Home part number MX3-F25 Grounded Clock hanger receptacle, Pass & Seymour part number S3713 or S3833 Option B The installer may need to take an approach that is a variation on the approach shown on the Connectivity Template. In some circumstances it may be more desirable to use the following product: Leviton 80704W wall plate, fits to a single gang receptacle and has a 1 -3/8 inch diameter hole in the middle. (All terminal cables can be run directly out of the hole in the wall plate.)
Positioning the Mounting Template
Remove the mounting bracket from the top of the DKEC by loosening the two screws at the back of the unit using a screwdriver. We recommend installing the mounting bracket with six 5/16 T-nuts and screws. Seat the screws firmly against the bracket, but do not overtighten.

Completed Installation

Installing the Mounting Bracket

Mount the DKEC

Install the DKEC onto the mounting bracket taking care to align the guide rails on the bracket with the rails on top of the DKEC (A, as shown in Attaching the Unit to the Mounting Bracket). Slide the unit about half way back on the rails.

FM Antenna

Rear Panel Connections
Detailed Instructions The DKEC supports three types of Internet connectivity using a PCMCIA network interface card (NIC). Depending upon which type of card is used, you can connect using: Wired (Ethernet) Broadband. Your broadband service may be provided over DSL or cable modem. Wireless (802.11b) Broadband. Dial-Up Internet Access. The dial-up Internet services must not require the installation of additional software. The following instructions cover three basic methods of access - Wired Broadband, Wireless Broadband or Dial-Up. Wired Broadband Setup If Internet access is provided through a Broadband service using the included Ethernet card, the instructions cover the following scenarios: Case #1 - An existing network is in place and an Internet connection is being shared among devices on the network, or; Case #2 - The local network is not yet in place.

Broadband

Install the Batteries
Prior to turning on the unit, do the following: Install Keyboard Batteries: Using a Phillips screwdriver, remove the 2 large screws in the battery cover on the backside of the keyboard. Then remove the cover and gasket. Install two (2) AA batteries (supplied) into the keyboard. Reinstall the gasket, battery cover, and screws. Install the screws so that the battery cover is firmly seated, but do not over tighten. Make sure that the small rubber washer associated with each screw is properly installed when reattaching the cover. Install Remote Batteries: Using a Phillips screwdriver, remove the small screw in the battery cover on the backside of the remote. Install two (2) AAA batteries (supplied) into the remote. Install the screws so that the battery cover is firmly seated, but do not over tighten. Make sure that the small rubber washer associated with the cover screw is properly installed when reattaching the cover.
Secured Screw Battery Cover Rubber Gasket

Power Up

The DKEC is initially powered on in two steps: 1. Locate the red rocker switch on the back of the unit near the AC power connection. Push this switch to the on position to power on the device. (This switch can also act as a reset by flipping it off then back to on, but it is intended to always remain in the on position unless a reset is necessary.) The unit will boot up in approximately one minute. A steady red light indicates that the device is on and in a sleep state. 2. To bring the unit out of sleep state, use either the On/Off button on the keyboard or remote or on the front panel of the unit. The unit can be returned to sleep state by pushing one of these buttons.
Note: The Ethernet card can only be used for Internet browsing or access. File transfer, file sharing, print sharing, and other LAN/WAN functions are not supported.
Broadband Case # 1: Existing Network The first configuration option is connecting your DKEC to an existing network with a shared Broadband connection. These instructions assume you have a router/switch (with an available port) in place on your network that supports multiple internal network IP addresses. A. Route and Connect Cables Make sure that the router is connected to the Ethernet card inserted in the DKEC. If this is not already done, route a standard Ethernet (category 5) cable with RJ45 plugs between your router and DKEC. Take care to connect the DKEC to a free Ethernet jack in the back of the router and not to the WAN port. The WAN port is reserved for the Ethernet cable coming from the modem. B. Configure Broadband Settings To configure your Broadband Connection Settings: 1. Press the Internet button on the keyboard or remote, then press the Options button. 2. Choose Connection Settings from the Internet Options menu. 3. Select the Broadband Settings button. The DKEC will display the Broadband Settings screen. 4. If your router/switch (or the modem/ router/switch combination) supports DHCP, select the Use DHCP server checkbox by pushing the Go or Enter buttons on the remote or keyboard, or tapping the checkbox on the touch screen. If DHCP is not supported, you will

On/Off Button On/Off Button
Internet Connection Information
Making it Simple The DKEC is engineered to take advantage of a Broadband connection and comes with an Ethernet Networking card which can be inserted into the PCMCIA slot on the rear of the device. If your home has a Broadband service installed (cable, satellite or DSL), and The Broadband service supports DHCP, and The modem is installed and configured, and The router (which is optional) is installed and configured, then Simply insert the included PCMCIA card, and plug the card into the modem (or router, if used) using an RJ45 network cable. Power up the DKEC and push the Internet button on the remote or keyboard. The DKEC will connect to your Broadband service using DHCP.
Battery Cover Secured Screw

Installing the Batteries

No additional software needs to be loaded onto the DKEC for it to work with a Broadband Internet connection.
need detailed information from your ISP so that you can complete the required fields. This include the IP address, Subnet Mask Gateway Router and the DNS Primary and Secondary numbers that must be entered in the appropriate fields. Choose OK to save the information, choose OK again. Choose the Refresh Connection button, then choose OK to exit the Options menu. The DKEC should now have be connected to the Internet.
Broadband Case #2: No Existing Network Assumptions These instructions assume the following existing conditions: The site of the installation has a Broadband (cable, DSL or satellite) Internet connection installed. If this is not the case, please call your Broadband provider to have this service installed. The Broadband services provided to the home support DHCP (Dynamic Host Configuration Protocol). If you are not sure, contact the Broadband service provider. If they do not support DHCP, ask your ISP to provide you with a static IP address and two DNS numbers. It is assumed that the Broadband provider has supplied the owner with a cable or DSL modem. If the modem was not connected to the Broadband termination box, contact the provider to get the instructions for doing this. The modem the Broadband service provider has supplied supports DHCP. If you are not sure contact the service provider to verify that this modem will support DHCP. If it does not, you will need to manually configure the modem (see C. Modem Configuration ). The router/switch being used (or the modem/router combination) will support DHCP. If a router needs to be purchased, DKEC, LLC recommends the following: Linksys Router, Instant Broadband Series, Ethernet Cable/DSL Router model #BEFSR81. You may need to use a router for one of two reasons. Either you want to connect to your Broadband connection with more then one device (e.g. a computer and a DKEC), or you are using a service provider that requires authentication information to connect to their service. If one of the above does apply, you will need to place a router or switch between the modem and the DKEC. A. Is There a Broadband connection? Yes:Go to step B. No: Call Broadband provider to install.

B. Modem Connection Once you have verified that there is a Broadband connection coming into your location, you may need to connect the provided equipment (most likely a cable modem or DSL router provided by the Broadband ISP) to the Broadband connection. Many times the Broadband line is installed to the locations demarcation or termination box. You will need to find this box to determine how the location is wired. This will give you the ability to connect the modem/router to the Broadband line as well as to the premises wiring. C. Modem Configuration
Using a wireless bridge I1. nsert the included networking card into the PCMCIA slot on the back of the DKEC. 2. Connect the wireless bridge to your home PC and configure it following the directions provided by the manufacturer of the bridge. 3. When the wireless bridge is properly configured for your wireless network, disconnect it from your home PC. 4. Insert one end of an Ethernet cable into the bridge, and one end into the Ethernet jack on the PCMCIA card. In most cases, no further connection settings are required. If no connection is established when you first go to Internet Mode, see B. Configure Broadband Settings on page 4 for more information. Using a wireless PCMCIA card Because the DKEC uses the Windows CE.NET platform, we cannot ensure the compatibility of all wireless network cards. Please contact customer support for a current list of supported wireless PCMCIA networking cards. The first time you go to Internet Mode, you will need to enter any configuration settings required by your wireless network. This may include a WEP (Wired Equivalent Privacy) key and other security settings. This may also include additional IP information if you use a Static IP address. To connect using a wireless PCMCIA card 1. Insert a wireless networking card into the PCMCIA slot on the back of the DKEC. 2. After turning on the DKEC, press the Internet button on the keyboard or remote, then press the Options button. 3. Choose Connection Settings from the Internet Options menu. 4. Select the Wireless Settings button. 5. Select your home network. 6. If your network requires a WEP key, select the Security button, then: a. Select the appropriate security options. b. Enter the WEP key. c. Choose OK. 7. If you use a static IP address, select the IP button, then: a. Clear the Use DHCP (Auto) checkbox. b. Enter static IP address, subnet mask, gateway router and DNS servers. c. Choose OK. 8. Choose the Connect button. Some networks are set up to allow only specific devices to connect based on the devices MAC (Media Access Control) address. You can quickly find the MAC (Media Access Control) address (also known as the physical address) of your wireless card. To find a cards MAC address 1. From the Internet Options menu, select Connection Settings. 2. Select the Wireless Settings button. 3. Select the IP button. The MAC Address of the wireless card is displayed. Write it down so you can enter it when configuring your router for the DKEC.

Note: This is typically done by the service provider.
Once you have the modem connected to a Broadband connection, you may have to configure it. Does your Broadband modem need configuring? Yes:You will most likely not be able to configure a Broadband modem with a DKEC. Many modems have to be configured by connecting the modem to a PC and entering the information such as IP address or user name/ work group/passwords. You will need to configure it with a PC or contact the provider for assistance. No: Go to step D.
D. Router Configuration If you are not using a router, simply make sure that the Ethernet cable from the modem is plugged into the Ethernet card in the back of the DKEC. If you are using a router, plug the cable from your modem into your routers WAN port. Next, run an Ethernet cable from the Ethernet card in the DKEC to a port in the router. Once you have done this, you can refer to the setup guide your router manufacturer provided regarding the details of router configuration. Keep in mind that if your service provider supports DHCP, follow the router manufacturers directions that are applicable for this situation. Similarly, if your service provider does not support DHCP, follow the router manufacturers directions that are applicable in this situation. Broadband Settings Follow the same directions described in B. Configure Broadband Settings on page 4.
Wireless Broadband Setup There are two ways to connect the DKEC to your wireless network: Using a wireless bridge connected to the Ethernet card, which is essentially an Ethernet connection; or, Using an approved wireless PCMCIA card.
Sample Configuration Diagrams
Dial-Up Setup The DKEC can also connect to a dial-up Internet provider, using a PCMCIA modem card equipped with an RJ-11 phone jack. The installer should run a twisted pair of wire from the master phone panel to a junction box located behind the DKEC. In order to configure Dial-Up Settings you will need some information from your Internet Service Provider. If you dont have an ISP, you will need to obtain one prior to completing the Internet setup of your DKEC.
Cable TV Printer Router (could be wireless) Home Office PC
Note: The DKEC does not currently support any ISPs that require downloading or installing software. At the time of the printing of this manual, AOL is an example of an ISP that will not work with the DKEC because of their download requirements, although you can still retrieve AOL mail using the DKEC Internet browser.
You will need the following information: User name Password Dialing Prefix The access phone number the ISP has provided The Primary DNS (not always required) The Secondary DNS (not always required)

Incoming Cable

Incoming Phone Wire

Audio Station

Printer

CD Player

Example of DKEC Configuration as Part of Home-Based Ethernet
Game Console Cable TV Combined into a single unit in some cases Modem Incoming Cable Router (could be wireless)
Video Camera (via video in)
To connect using a Dial-Up connection 1. Insert the modem card into the PCMCIA slot on the back of the DKEC. 2. Plug the analog telephone line into RJ-11 jack on the modem card.
CAUTION: Do not connect the DKEC to a digital phone line. Severe damage can occur to the DKEC.
3. 4. 5. 6. 7. After turning on the DKEC, press the Internet button on the keyboard or remote, then press the Options button. Choose Connection Settings from the Internet Options menu. Select the Modem Settings button. Enter the appropriate information in the User Name, Password, Dialing Prefix (if any), and ISP Phone # fields. Choose OK to save the information, then choose OK twice more to exit the Options menu. You should now have access to the Internet.
Incoming Phone Wire Typical DKEC Accessory Configuration

Video Mode

Introduction The DKEC can be connected to a video camera which you can use to monitor another part of the house. For example, you can monitor the activity in a childs room or see who is at the front door. You can also use Video Mode to view video tapes on a VCR or play video games on a game system. Additionally, you may wish to take advantage of the higher quality of Satellite or Digital Cable by using the S-video connection, which can also be viewed in Video Mode.
Wiring Diagrams We have provided basic wiring diagrams for a wired or wireless camera.
Back of DKEC Video Camera
Note: If you connect your Satellite or Digital Cable service to the DKEC using S-Video, the DKEC remote or keyboard cannot be used to change channels in Video Mode. Continue to use your existing remote control with the set-top box.
If youve connected both an S-Video and a composite signal, both are accessible from Video mode. To connect an S-Video source Plug an S-Video cable from the camera, VCR, game machine or satellite/cable receiver into the S-Video connection on the back of the DKEC. To the right are samples of wiring diagrams for a wired or wireless camera. To view video sources 1. Press the Video mode button. The composite signal (if any) appears. 2. Press the Video mode button again. The S-Video signal (if any) appears.

Wireless Camera Example Model: x10.com, XC10A Addressable Power Supply Example Model: x10.com, XM10A

Back of DKEC

To 120VAC Wireless Base Unit
Example Model: X10.com, VR31A

To 120VAC

Wiring Diagrams

Support and Registration

Registering a New DKEC
IMPORTANT: This section assumes that the DKEC unit has been fully configured for either Broadband, Wireless or Dial-Up connectivity. If this is not the case, please refer to the appropriate section in this manual for configuration details.
Before going online with the DKEC for the first time, you are given the opportunity to register the unit. If you are the installer, you should choose the Register Later button, and allow the owner to complete registration. If you are the owner, choose the Register Now button to ensure that the warranty is activated and that you receive software updates.
IMPORTANT: In order to receive future software updates, the owner must register the unit.

NOTES:

Web Site: Phone:
www.dacor.com (800) 793-0093