User`s guide

X10CONFIG(5) X10CONFIG(5)

ASIF_DATE20020621

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 user´s 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 direc-

tive 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,anevent occurring twice, or possibly an error,depending on circumstances.)

RESOLVE_OVERLAP directive

When uploaded timers specify Dawn/Dusk periods with different begin and end points, Heyu resolves the

situation such that the approximation time used for Dawn and/or Dusk is the same for every timer on any

givenday.There are twomethods for doing this and in most cases the newer method appears to give better

results in term of maximum error on Dawn or Dusk. This directive allows returning to the previous method

if more satisfactory.The choices here are OLD or NEW,with the default being NEW.

If the timers in your schedule involveonly clock times or don’tinv o lveboth Dawn and Dusk-relative times,

either choice will yield the same result.

(A future release of Heyu will makethis determination automatically and obsolete this directive.)

FIX_STOPSTART_ERROR directive

With parameter "YES" is a work around for the CM11A EEPROM bug "Stop Time = Start Time" which is

occasionally encountered when uploading speciﬁc schedules. It should be used (generally as a "conﬁg" line

in the schedule ﬁle) only when needed as it results in less efﬁcient use of the EEPROM memory space.

===============================================

The following directivesare applicable to CM17A

===============================================

RF_POST_DELAYdirective

This directive speciﬁes the delay in milliseconds following each standard RF command to a CM17A "Fire-

cracker" to allowtime for the transceivertorespond with its power line signal. The default is 850 millisec-

onds.

Example:

RF_POST_DELAY850

RF_FARB_DELAYdirective

RF_FARW_DELAYdirective

Speciﬁes the delay in milliseconds following respectively a ´farb´ or ´farw´ RF command to a CM17A.

The default is 850 milliseconds. This delay is speciﬁed separately from that for the standard RF commands

so that these commands can be used to control devices that don´t involveatransceiverand power line sig-

nals.

local 21