User`s guide

X10CONFIG(5) X10CONFIG(5)
MAX_DUSK directive
These directivesallowbounds to be placed on the times of Dawn and Dusk computed by Heyu. For exam-
ple, setting the value for MIN_DAWNto06:30 will instruct Heyu to execute a timed event scheduled for
dawn at 06:30 instead, wheneverthe computed time for dawn is earlier than 06:30. These directivesmay
be useful for users in extreme latitudes, when for example a lamp is scheduled to turn on at dusk and turn
offat9:30 PM. But if during the summer months dusk actually occurs after that hour,then the on/offcycle
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 directivesare specified as hh:mm Civil (i.e., wall-clock) time. The directivesmay be
disabled with the word OFF in place of a time. The default is OFF.
Heyu version 2 nowhas timer options for conditional compilation of events depending on the values of
Dawn and Dusk, so these directivesmay no longer be useful.
(Note: Due to Heyu´s optimizations, the order in which events scheduled for the same time are actually
executed is not necessarily that in which theyappear in the user´s schedule file. Allowatleast 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 file written when a schedule is uploaded or upload checked.)
DAWN_SUBSTITUTE directive
DUSK_SUBSTITUTE directive
These directivesare obsolete and will be ignored.
REPORT_PATHdirective
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 configuration file is
stored. This directive instructs Heyu where the user would likethem 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 CM11A´s EEPROM, Heyu records critical information in the
files ´x10record´, ´x10macroxref´, and ´x10image´. Fordebugging or informational purposes, this directive
instructs Heyu to write these files 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 hexdump 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 newevents and newundelayed
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_DATEdirective
Used for test purposes, this directive instructs Heyu to substitute the argument date for today´s date when
processing the user´s schedule file.
The date format is yyyymmdd.
Example:
local 20