User`s guide

X10CONFIG(5) X10CONFIG(5)

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 today´s date wrap around into next year.

Examples:

MODE COMPATIBLE

MODE HEYU

*** WARNING - WARNING - WARNING ***

Users running PCs conﬁgured for dual-boot between Linux and MS-Windows should NOToperate Heyu in

HEYU mode if theyexpect to evermanually execute X-10´s ActiveHome(TM) program (or allowits

"Communications Bridge" drivertobelaunched at boot time). Here´s why:

If the CM11A detects that its ACpower has been interrupted, evenfor 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 Heyu´s 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.)

PROGRAM_DAYSdirective

When operating Heyu to upload timers and macros to the CM11A interface in HEYU mode, this directive

instructs Heyu to compile the uploaded schedule to run for the number of days speciﬁed (1-366), beginning

today.This directive isignored when Heyu is operated in COMPATIBLE mode. The default value is 366

days. Example:

PROGRAM_DAYS90

The advantage to running for a shorter number of days becomes evident when timers are programmed for

Dawn- or Dusk-relative times. Because of the limited size (1024 bytes) of the CM11A EEPROM memory,

Heyu uses a stair-step approximation to the daily times of Dawn and Dusk overthe PROGRAM_DAYS

interval. The unequal-length step intervals are determined iteratively to minimize the error while ﬁtting in

the available EEPROM memory space.

As a result, evenasingle Dawn- or Dusk-relative timer will generally occupymost of the EEPROM space.

Howeverasmore timers are added to the schedule, the stair-steps are recalculated so everything will ﬁt,

although at the expense of a larger error.

LATITUDE directive

LONGITUDE directive

These are used to allowHeyutocompute the times of dawn and dusk overthe year for your particular loca-

tion. There are no defaults.

The format of the directive line is the word LATITUDE followed by a space and then the direction, degrees,

acolon and the minutes. The LONGITUDE directive follows the same format. Example:

LATITUDE N37:41

LONGITUDE W121:52

Note: Versions of Heyu earlier than 2 did not use a direction (N/S/E/W) symbol and assumed the conven-

tion that positive Latitude is North and positive Longitude is West. For compatibility,Heyuversion 2 will

makethe same assumptions if the direction symbol is omitted.

COMBINE_EVENTS directive

This directive instructs Heyu whether or not to combine events which have the same day-of-week code,

date range, type (i.e., Clock, Dawn, or Dusk based), and time-of-day.Heyuthen needs to upload only a

single timer executing a concatenated macro, which savesconsiderable EEPROM space when Dawn/Dusk

local 18