Universal Devices ISY-994i Series, Руководство пользователя

Страница: 246 / 692

Page | 223
every x number of days/weeks variables since those programs require a reference
that always increases by one each day. I have arbitrarily used MS Excel’s system of
setting Jan 1, 1900 equal to day one and then counting from there. This offered an
opportunity to test these programs well into the future and have a reference to
check the values against.
•
iEver.xxx.Counter starts with 0 and counts up to x-1. For example,
iEvery.Fourth.Day.Counter cycles through 0,1,2,3,0,1,2,3,etc. If today the variable
was equal to 1 and you wanted to start watering your lawn tomorrow continuing
every 4th day after that, set your program to water when the variable is 2.
•
iWeek.of.Month starts with 1 on the first day of the month and increases by 1 every
7 days until the next month starts. So if you wanted something to happen on the
second Tuesday of each month, set it to occur on Tuesdays when
iWeek.of.Month is
equal to 2.
•
iWeek.Counter counts the number of weeks since Jan 1, 1900. The purpose of this
variable is to calculate every x weeks programs as there is likely no value in
knowing how many weeks have passed since Jan 1, 1900. This value is produced by
dividing iDay.Counter by 7.
•
i.Every.xxx.Week programs start at 0 and count to x-1. This works the same as the
iEvery.xxx.Day.Counter programs except it is for weeks.
•
iOdd.Even.Day sets to 0 on even days and 1 on odd days of the month. This is useful
in communities with watering restrictions limiting certain addresses to water on
even or odd days of the month.
•
iHoliday sets to 1 on the listed holidays and 0 on all other days. Feel free to add
your own holidays. I use this value to shut down wake-up alarms.
•
iSync is a variable whose purpose is to test the status of this set of programs against
the ISY’s internal day of week function. An e mail is triggered if the two are out of
sync. If this variable is correct, it is quite safe to assume all of the variables are
correct.
•
The sVariables are simply the same value of the corresponding iVariables copied
over to the state variable side. The purpose of this is so that you can use them as
program “triggers”. You can certainly add more to the list as you see fit.
11.1.1.3Setting Up The Programs
•
The first step is to setup the variables. The variables do not load automatically with
the programs. There is at present no way to import variable setups so you must do it
manually. The screen captures at the bottom of this page show you all of the
locations for the variables. Please note that there are a number of variables in that
screen capture that are not part of this series of programs. Please just skip over
those id locations or use them for other applications. You must enter the listed
variables into ISY AT THE SAME ID LOCATION AS SHOWN. ISY programs reference
the id location NUMBER, not the name. The name you enter in the name column is
shown in the program for convenience only. Because I wrote these programs and
then worked on some other programs, and then came back to these programs, there
are some intervening variables which you need not concern yourself with, except to