User`s guide

X10CONFIG(5) X10CONFIG(5)
STATE_FORMATdirective
If set to the value OLD, the output of the state commands ´onstate´, ´dimstate´, ´chgstate´, and ´addrstate´
revert to the former heyuhelper style, e.g., a2Dim. Taking the default value NEW displays output as either
1(True) or 0 (False) when a housecode|unit parameter is provided, or a unit bitmap of the state (bit 0 ->
unit 1) as a decimal integer when the parameter is a housecode only.This directive isintended to provide
compatibility with existing scripts.
STATE_CTRL directive
With the default value of "SINGLE" for this directive,the output of state commands ´onstate´, ´dimstate´,
´chgstate´, and ´addrstate´ is boolian 0 or 1 when the address parameter includes the unit, or a bitmap if the
address parameter is only a housecode. Specifying the value of this directive as"BITMAP" results in the
output being a bitmap regardless of whether or not the address include a unit.
===============================================
The following Directivesare applicable when a schedule of Timers and Macros is to be uploaded by Heyu
to the CM11A´s EEPROM.
===============================================
SCHEDULE_FILE directive
Instructs Heyu to use the named file as the user´s schedule file (which must be in the same directory as the
configuration file). The default is x10.sched.
Example:
SCHEDULE_FILE vacation.sched
MODE directive
Heyu can operate in one of twomodes insofar as uploaded timers and macros are concerned. But before
getting into these, first a fewwords about the CM11A interface´s internal clock:
The CM11A clock has no notion of actual dates, but is merely a day counter which starts from 0 and incre-
ments daily until it reaches 365 (a total of 366 days), after which it rolls overto0.Anindependant counter
keeps track of the weekday,starting at 0 (Sunday) and incrementing daily through 6 (Saturday) before
rolling overto0.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 overto0: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 configured such that Day 0 corresponds to Jan 1st in the cur-
rent 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 user´s schedule must be re-uploaded on Jan 1st, at least
in years following common years. (The CM11A will otherwise keep chugging away, but events fired off
will be a day in error.)
In HEYU mode, the CM11A clock is configured such that Day 0 corresponds not to Jan 1st but to today´s
date. The uploaded schedule can be configured to run for anyperiod between 1 and 366 days via the PRO-
GRAM_DAYSdirective.(See the description of that directive for reasons for wanting this.) The user´s
schedule can be re-uploaded at anytime prior to expiration of the PROGRAM_DAYSperiod and corre-
spondance will be maintained for the next period of PROGRAM_DAYS. Note howeverthat if this period
is allowed to expire without re-uploading the schedule, the CM11A will cease to fire offany programmed
ev e nts (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
local 17