High Voltage Shareware/high1.zip/high1/DIR4/X10DC150.ZIP/X10DC.HLP

Text File | 1993-12-22 | 38KB | 814 lines

.TOPIC:
Contents
────────────────────────────────────────────────────────────────
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▌GENERAL INFORMATION▐│▌   PROGRAM USAGE   ▐│▌ PROGRAM FEATURES ▐
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀│▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀│▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
X-10 Background    │Command Line Args  │Undocumented CP290
CP290 Description  │Communication Ports│CP290 Self Test
CP290 Event Data   │Keyboard Usage     │Signal Test
CP290 Icon Data    │Menu Bar           │Clock Sync'ing
X10.DAT File Format│Operating Modes    │Set Base HouseCode
X-10 BBS Sources   │Debug Mode         │Screen Colours
Help on Help!      │Problem Resolution │Save Options
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄  ╔═══════╗  ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▌REGISTRATION INFORMATION▐  ║X10EC║  ▌UPGRADE INFORMATION▐
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀  ╚═══════╝  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.TOPIC:
X-10 Background
────────────────────────────────────────────────────────────────────
The X-10 group manufactures and markets a wide variety of home
automation products that are relatively inexpensive and easy to
install.  The product line consists of 'controllers' that send
signals over existing home wiring to receiver 'modules' that
control lights & appliances.

X-10 technology was developed by a group of engineers in
Glenrothes Scotland, who began designing microelectronic chips
when Large Scale Integrated Circuits were first introduced
commercially in 1969. From 1976 to the present, all X-10 product
design and development has been performed by this same
organization, Pico Electronics Ltd., a subsidiary of X-10 Ltd.

The first X-10 products were announced in the U.S. on September
22, 1978. Prior to this introduction, two private label
agreements had already been concluded, one with Sears Roebuck
and the other with Radio Shack. Significant shipments to Radio
Shack and Sears began in 1979.  More recent private label
customers include Stanley Home automation and Heath Zenith.
X-10 Ltd ships to other major customers in addition to X-10
(USA) Inc. including Leviton Manufacturing Co. Inc.

Prior to July 1, 1984, X-10 products were marketed by BSR, as a
result of a joint venture between the X-10 developers and BSR
International PLC, parent of BSR (USA) Ltd. and BSR Canada Ltd.
On July 1st, 1984, X-10 (USA) Inc. was established to take over
all North American business activities formerly conducted by the
X-10 division of BSR (USA) Ltd. and BSR Canada. In November
1987, X-10 Ltd.  acquired BSR's interest in the company, and is
also X-10 (USA)'s parent company.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
CP290 Description
────────────────────────────────────────────────────────────────────
The CP290 is encased in a white plastic box about 5" wide x 7"
deep x 2" high.  There are 8 rocker buttons on the top of the
unit which will send ON/OFF commands to Unit Codes 1-8 of the
Base HouseCode A red LED flashes when you press the rocker
buttons.  The unit plugs into a 110 volt AC wall outlet and is
also supplied with an interface cable which plugs into the
back of the unit and into a 9 pin serial port.  A
micro-computer communicates with the device via this serial
connection.  The unit also has a 9-volt battery backup which
will retain the information stored within the unit in the
event of a power failure.

The primary purpose of the CP290 is to store a schedule of
events and issue X-10 commands at the scheduled times.  Up to
128 events can be stored within the device.  The CP290 will
also accept 'immediate' commands; X10DC sends its X-10 command
directives to the CP290 in this 'immediate' mode.  The serial
connection to a micro-computer is only active when the
micro-computer and CP290 are communicating; it can be
disconnected once the CP290 Event Data has been loaded. For
this reason, the CP290 is a good candidate to share a serial
port with another serial device using a switch box.

The CP290 is supplied with the program X10.EXE that allows
the user to define devices and create a schedule of events.
X10.EXE saves this information each time it is updated to
a X10.DAT file.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
CP290 Event Data
────────────────────────────────────────────────────────────────────
In addition to Time of Day, Day of Week and Base HouseCode,
the CP290 also stores Event Data.  X10DC -=DOES NOT=-
manipulate Event Data, however, it will download/upload the
Event Data in order to preserve it when performing functions
which alter or erase this data (ie. Change Base Housecode,
CP290 Self Test). X10EC (X10 Event Control) a companion
program to X10DC -=DOES=- manipulate Event Data as does
X10.EXE, the program supplied with the CP290.  There are also
several other fine shareware programs which manage Event Data.

The CP290 will store up to 128 Events.  The following data
is stored for each Event:

   DAY(S) OF WEEK ∙ Monday,Tuesday...
             TIME ∙ Hour & Minute
             MODE ∙ Repeat each week,
                    Repeat each week but randomize time +/- 30
                      minutes (for security reasons)
                    Today ONLY
                    Tomorrow ONLY
        HOUSECODE ∙ eg. A -> P
     UNIT CODE(S) ∙ 1-16
Events scheduled for TODAY/TOMORROW are cleared from memory at 4
minutes after midnight on the day they were scheduled.

X10EC extends the storage capability of the CP290 by using the
CP290 Icon Data area.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
CP290 Icon Data
────────────────────────────────────────────────────────────────────
The CP290 also has memory set aside for Icon storage.  The DOS
character-based software does not display any graphical Icons
hence this storage area is unused when the CP290 is used with
the X10.EXE program.  However, X10EC, a companion program to
X10DC does use the ICON storage area to store Sunrise/Sunset
Offset information as well as the 'Last Upload' Date/Time and
other information.  Consequently, if you use X10EC you will want
to be sure the Preserve ICON Data option is toggled on under the
options menu.  This will ensure that the ICON Data is preserved
if you perform a CP290 Self Test or set the Base HouseCode.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
X10EC
────────────────────────────────────────────────────────────────────
                      X10EC ∙ X10 Event Control
                            Version 1.0
                         (c) 1993 D.Huras
────────────────────────────────────────────────────────────────────
This program manages CP290 Event Data including SUNRISE/SUNSET
offsets and uses the same DOS character-based point & click
interface as X10DC.  Distinguishing Features:
   ∙ Supports * 5 * UNDOCUMENTED CP290 Commands
   ∙ Compatible with the X10.DAT file format used by X10.EXE
     (X10.DAT files can be read, created, updated and written)
   ∙ Supports X10.EXE 'Frozen' Events
   ∙ Supports Relative Times (Sunrise/Sunset +/- Offsets)
   ∙ All EVENT information (including Sunrise/Sunset Offsets
     and Last Upload Date/Time) is stored within the CP290
   ∙ EVENTS can be programmed without touching the keyboard
     (using a mouse)
   ∙ EVENTS can be sorted using one of 3 sort criterias
   ∙ Program EVENTS from a DEVICE List Window -OR- an EVENT
     List Window
   ∙ 'Intelligent' Edit (referential integrity) automatically
     updates EVENTS when you change a DEVICE House/Unit code
   ∙ Merge Device Descriptions from any number of X10.DAT
     files into one X10.DAT file
   ∙ Detects and exploits EGA/VGA 43/50 line mode
   ∙ Supports ANY Commport/IRQ/Base IO Address

X10EC can be registered online using Compuserve Software Registration;
Program ID# ____.  (Go SWREG).
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
X10.DAT File
────────────────────────────────────────────────────────────────────
The X10.DAT File Format is used by the X10.EXE program that
comes with the CP290 Computer Interface.  If you have used the
X10.EXE program then you will have created an X10.DAT that
contains all of the device definitions (ie.  House Code, Unit
Code, Location, Description) that you 'INSTALL'ed using
X10.EXE.  (The X10.DAT file will store up to 256 device
definitions.)  X10DC will read in an X10.DAT file, locate all
of your device definitions, and place them in a scrollable
list box.  You can then send commands to these devices.  X10DC
will look for an X10.DAT file in the current directory each
time it runs unless you specify the location with the /F:
command line argument.  You can also explicitly load an
X10.DAT file from any drive/directory by using the 'Load X10
File' menu item (CTRL-L) when X10DC is running.  The location
of the file can then be saved to an INI file by using the
'Save Options' menu item (CTRL-S).

The X10.DAT file also stores event information; up to 128
events can be stored in the file.  See CP290 Event Data.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
X-10 BBS Sources
────────────────────────────────────────────────────────────────────
The following BBS's are primarily dedicated to Home Automation
and are good sources of both X-10 software and documentation.

     AUTOMATIC MANSION........................604-872-8407

     BARAN-HARPER GROUP HOME AUTOMATION BBS...905-471-9574
     (HC2000 Source)                          905-471-6776

     HOME AUTOMATION LABS.....................404-319-6227

There is also a Home Automation section within the Consumer
Electronics Forum (CEFORUM) on CompuServe.

If you are aware of other BBS's that should be included in this
list, please contact the author.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Help On Help!
────────────────────────────────────────────────────────────────────
Selecting a Help link:
══════════════════════
With a mouse - click on phrases outlined by two triangles.
With the keyboard - Press TAB or Shift-TAB to select a link.
   Press ENTER to jump to that topic.

Scrolling the Help window:
══════════════════════════
With a mouse - click on the horizontal or vertical scroll
   bars.
With the keyboard - press the cursor navigation keys.

Command Buttons:
════════════════
Use a mouse to click a button or press the letter
mentioned below.

Contents - displays a table of contents for the application's
   Help.  Press C to select Contents.

Search -  opens a dialog box that lists all available Help
   topics.  Select a topic from the list box and press ENTER.
   Press S to select Search.

Back - jumps to the last Help topic viewed. Press B to select
    Back.

Exit - Closes the Help Window.  Press X to select Exit.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Command Line Args
────────────────────────────────────────────────────────────────────
The following arguments can be entered in any order:

  /Annnnn ∙ Base I/O Address ..see User Defined CommPort
  /BW ∙ Use Monochrome colours
  /Cn ∙ COMMPORT where n = 1,2,3 or 4
  /D  ∙ TURNS ON DEBUG MODE
        When DEBUG MODE is ON, the CP290 responses &
        checksums are displayed in the Command History List Box.
  /F:[d]\filename ∙ X10.DAT FILE SPECIFICATION for MODE 3
        where [d] = drivespec eg. /F:C:\X10\X10.DAT
  /In ∙ IRQ where n=1-15 ...see User Defined CommPort
  /Mn ∙ MODE where n = 1,2 or 3 ...see Operating Modes
  /NH ∙ Do Not Load HELP Sub-System
  /NH-∙ Load HELP Sub-System (Override INI directive)
  /NS ∙ No Sounds during Signal Test
  /NS-∙ Sounds during Signal Test (Override INI directive)
  /P  ∙ Toggles ON Preserve CP290 Icon Data

DEFAULTS:  If the program is run without any command line
arguments it will default to COMMPORT 1,OPERATING MODE 1,
DEBUG OFF, F:X10.DAT, Preserve ICON Data

NOTES:
1) Most Command Line directives (with the exception
   exception of /A,/I & /NH) can be modified once the
   program loads by selecting the appropriate menu items
   under the Options Menu.  Registered Users can save all
   these settings to the X10DC.INI file by using the 'Save
   Options'² menu item.

2) COMMAND LINE OPTIONS OVERRIDE ALL X10DC.INI SETTINGS

────
² Not available in UNREGISTERED Version
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Communication Ports
────────────────────────────────────────────────────────────────────
X10DC supports "pseudo standard" CommPorts 1 thru 4 using the
following settings:
  ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  █          │      ├─ Base I/O Addr.──█  FOR PS/2 Settings
  █ CommPort │ IRQ  │ Decimal │  HEX.  █  see PS/2 CommPorts
  █──────────┼──────┼─────────┼────────█
  █    1     │   4  │  1016   │  3F8   █
  █    2     │   3  │   760   │  2F8   █
  █    3     │   4  │  1000   │  3E8   █
  █    4     │   3  │   744   │  2E8   █
  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If one of these CommPort settings matches your hardware
configuration simply use the /C command line argument with
the appropriate CommPort.  The CommPort= X10DC.INI directive
can also be used.  Note that if X10DC is run without the  /I
(IRQ) or /A (Base I/O Address) Command Line arguments then
the User Defined CommPort is undefined and not
selectable from the menu bar.

If your hardware configuration differs from the table above,
then can define your own CommPort;see User Defined CommPort
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
User Defined CommPort
────────────────────────────────────────────────────────────────────
You can define your own CommPort by using the /I and /A
Command Line Args (or IRQ= & Base_IO_Address= X10DC.INI
file directives).  IRQ can be set to any value between 1 and
15 (inclusive).  Base I/O Address can be set to any value
greater than zero.  CAUTION: your hardware may "lock up" if
incorrect settings are used.  You should supply both
arguments (/A & /I), however, if you only supply one of the
arguments then the defaults applicable to CommPort 1 will
apply to the other argument.  (eg. if only the /I5 argument
is supplied, then the /A argument defaults to 1016).  If
either the /I or /A argument is supplied, then the 'User
Defined Commport' under the 'Options' menu becomes enabled.

The /C command line argument AND the CommPort= X10DC.INI
directive ALWAYS override the the User Defined CommPort
when the program first loads.  However, the 'User Defined
CommPort' will remain enabled under the 'Options' menu.
To start the program with the User Defined CommPort active,
ensure that there is no /C command line argument AND no
CommPort= X10DC.INI directive.

THE BASE I/O ADDRESS MUST BE SPECIFIED IN DECIMAL NOTATION.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
PS/2 CommPorts
────────────────────────────────────────────────────────────────────
   ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
   █   PS/2   │      ├─ Base I/O Addr.──█ NOTE: A User Defined
   █ CommPort │ IRQ  │ Decimal │  HEX.  █       CommPort must be
   █──────────┼──────┼─────────┼────────█       used for PS/2
   █    1     │   4  │  1016   │  3F8   █       CommPorts 3-8
   █    2     │   3  │   760   │  2F8   █
   █    3     │   3  │ 12832   │ 3220   █
   █    4     │   3  │ 12840   │ 3228   █
   █    5     │   3  │ 16928   │ 4220   █
   █    6     │   3  │ 16936   │ 4228   █
   █    7     │   3  │ 21024   │ 5220   █
   █    8     │   3  │ 21032   │ 5228   █
   ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Keyboard Usage
────────────────────────────────────────────────────────────────────
Use the TAB/Shift-TAB keys to move among the various
controls.² The Up/Down arrows can be used to move up and down
List Boxes, and the Spacebar and Enter key can be used to
select the current List Box item, check/uncheck a check box,
or invoke a command button.  The ESCAPE key will exit the
current function or the program if no other windows are
visible.  All of the Command Buttons and controls have quick
access keys:

     House Code ∙ Alt-o [Mode 1 & 2]
   Unit Code(s) ∙ Alt-u [Mode 1 & 2]
    Device List ∙ Alt-u [Mode 3]
            ALL ∙ Alt-l [Mode 2]
           NONE ∙ Alt-n [Mode 2]
         Action ∙ Alt-a
     Brightness ∙ Alt-b [when enabled]

          MODE² ∙ Alt-m
           SEND ∙ Alt-s
           EXIT ∙ Alt-x
           HELP ∙ Alt-h

Command History ∙ Alt-c
────
² The MODE Command Button is NOT in the TAB STOP sequence;
  Keyboard users must use ALT+character to access this button.
  (This eliminates extraneous TAB keystrokes)
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Menu Bar
────────────────────────────────────────────────────────────────────
Press & release the ALT key to activate the Menu Bar.  Menu
items can be selected by pressing the highlighted key (when
applicable), or by positioning the highlight bar using the
up/down arrow keys and pressing ENTER.  Some screen button
functions are replicated within the menus (eg. Exit, Help).
However, there are some functions which are only available
from within menus.  CommPort, Operating Mode, Debug & Sounds
can all be set from the Options Menu; the current state of
each of these parameters is indicated on the menu itself with
a '∙' character to the left of the menu item.

Short-cut Keys have been defined for many of the menu
items.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Short-cut Keys
─┤FILE Menu├────────────────────────────────────────────────────────
        Load X10 File ∙ Ctrl-L
                 Exit ∙ Ctrl-X (Same as Exit Button, Alt-X)

─┤CLOCK Menu├───────────────────────────────────────────────────────
         Set PC Clock ∙ Ctrl-T (Enter Time)
      Set CP290 Clock ∙ Ctrl-K (Synchronize w/PC)
       Refresh Clocks ∙ Ctrl-R
   Set Base HouseCode ∙ Ctrl-B (Preserve Events)

─┤TEST Menu├────────────────────────────────────────────────────────
      CP290 Self Test ∙ Ctrl-E
Signal Test Generator ∙ Ctrl-G

─┤OPTIONS Menu├─────────────────────────────────────────────────────
           CommPort 1 ∙ Ctrl-F1
           CommPort 2 ∙ Ctrl-F2
           CommPort 3 ∙ Ctrl-F3
           CommPort 4 ∙ Ctrl-F4
User Defined CommPort ∙ Ctrl-F5 (when applicable)

               Mode 1 ∙ Shift-F1
               Mode 2 ∙ Shift-F2
               Mode 3 ∙ Shift-F3

        Sounds Toggle ∙ Ctrl-N
    Debug Mode Toggle ∙ Ctrl-D
   Preserve ICON Data ∙ Ctrl-I

       Screen Colours ∙ Ctrl-C

         Save Options ∙ Ctrl-S²

─┤HELP MENU├────────────────────────────────────────────────────────
                 Help ∙ F1 (Same as Help Button, Alt-H)
                About ∙ Ctrl-A
────
² Not available in UNREGISTERED Version
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Operating Modes
────────────────────────────────────────────────────────────────────
Operating Mode can be set using the 'Options' menu, the MODE
command button (cycles through the modes), or the /M command
line argument.
────────────────────────────────────────────────────────────────────
MODE 1 ∙ Provides a List Box of Unit Codes; only 1 Unit Code
         can be selected.  However, this mode will be easier
         to use if you don't have a mouse since you'd have to
         TAB through all the Unit Code check boxes used in
         MODE 2.
MODE 2 ∙ Provides a Check Box for each Unit Code plus ALL and
         NONE buttons to quickly Check/Uncheck all check
         boxes.  In this mode, multiple Unit Codes can be
         targetted for the X-10 Command.
MODE 3 ∙ Provides a List Box of Devices which are read from
         an X10.DAT File; X10DC will look for "X10.DAT" in
         the current directory UNLESS the /F: command line
         argument is supplied.  If X10.DAT cannot be found,
         the program will switch to Mode 1.  Select 'Load X10
         File' under the File menu to load an X10.DAT file
         from another sub-directory. (Once the file is
         loaded, its location can be SAVEd² by selecting
         'Save Options' under the Options menu.)

         NOTE: ONLY THE 1st 8 DEVICES CAN BE TARGETTED FOR
               COMMANDS WITH THE UNREGISTERED VERSION.
────
² Not available in UNREGISTERED Version
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Debug Mode
────────────────────────────────────────────────────────────────────
┌────────────────────────────────────────────────────────────┐
│ Using COMMPORT: 2   X10 DIRECT CONTROL  CP290 Day: Tuesday │
│Base House Code: P      Version 1.50    CP290 Time: 11:51 AM│
│Mode: 1   Debug ON   (c)1993 ∙ D.Huras     PC Time: 11:52 AM│
└──────────────┼─────────────────────────────────────────────┘
               └────┐
                  ──┴─────
When enabled, the DEBUG ON message appears in the screen
Header. In addition, all responses from the CP290 are
displayed in the Command History List Box, as well as
Checksums and Timing Information.

Debug Mode can be toggled ON/OFF from the Options Menu.

NOTE: Debug Mode increases program overhead; memory
requirements will be greater and program performance will be
somewhat degraded.  It is recommended that you only toggle
Debug Mode ON when necessary.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Problem Resolution
────────────────────────────────────────────────────────────────────
Generally, if your CP290 works with the X-10 supplied
software then you should have no problems running X10DC.
The program will load if you run it without any arguments
(thereby defaulting to COMMPORT 1) and your CP290 is
actually attached to COMMPORT 2.  If this is the case X10DC
will report an error when it attempts to retrieve the Time
and Base HouseCode.  You can toggle to the correct COMMPORT
once the program is running by using the Options menu.  In
future you should include the Command Line argument /C2 if
your CP290 is connected to COMMPORT 2.  The Save Options
menu option will save all settings to the X10DC.INI which
obviates the need for command line arguments.

If you run X10DC with a modem attached to the COMMPORT, you
may get unpredictable results since the modem will echo
everything back to X10DC.

If you are sure that the X10DC is using the correct COMMPORT
and problems persist, try using Debug mode and then scroll
through the Command History List Box; see if the calculated
checksums match; look at the TIMER and MaxTimer Values. If the
MaxTimer Value exceeds the TIMER value then the program is
timing out while waiting for X-10 responses. PLEASE REPORT ANY
TIMING PROBLEMS TO ME; adjustments can be made to the program
to improve its compatibility if this turns out to be a
problem.  As a last resort, run the CP290 Self Test,
but only do so if you have backed up your EVENT DATA using a
program you are sure works within your operating environment.
(X10DC will preserve the CP290 Event Data but if you are
experiencing problems with X10DC then this function may
fail).

In some cases X10DC may report that a command failed, or a
checksum did not match, but in fact the command was accepted
by the CP290 and transmitted on the powerline.  This could
happen if spurious responses are received from the CP290, ie.
if you were to press the rocker buttons on the CP290 just
after sending a command.  If this happens, exit the program
and re-invoke it to resynchronize, alternatively, if you have
2 serial ports you could try toggling the CommPort. (ie. if
your CP290 is on CommPort 1 then switch to CommPort 2, then
switch back to CommPort 1).

The open architecture of the PC compatible operating
environment and the near infinite combinations of hardware and
software complicate the compatibility of applications
software.  While every effort has been made to ensure that
X10DC is compatible with all hardware/software combinations,
there may be operating environments in which X10DC will not
run properly.

Problems can be reported to:

   David Huras
   37 Ruddell Crescent
   Georgetown, Ont. L7G 5N4
   CANADA

   FAX: [phone]
   CIS: 72767,472
   Internet: [e-mail]
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Undocumented CP290
────────────────────────────────────────────────────────────────────
X10DC supports the following undocumented CP290 commands:

   Fade OFF   ■ DIMS Light(s) to 0 then turns Unit(s) OFF
                (Can target multiple units for this command)
   X-Light ON ■ Exclusive Light ON - Issues an ALL LIGHTS OFF
                then Brightens selected Unit(s)
                (Can target multiple units for this command)
   All Lights ON  ■ All Lights on selected House Code set ON
   All Lights OFF ■ All Lights on selected House Code set OFF
   All Units OFF  ■ All Units on selected House Code set OFF
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
CP290 Self Test
────────────────────────────────────────────────────────────────────
The CP290 can perform a Self-Test to determine if there are any
detectable problems within the device.  The Self-Test will
return either a pass or fail status when it is run.  X10DC will
report the results of the test in the CP290 Status window.
Whenever a Self-Test is run the memory contents of the CP290 are
overwritten.  X10DC can preserve the CP290 Event Data and
CP290 Icon Data by downloading it from the CP290 prior to the
Self-Test and uploading it back to the CP290 after the Test.
(X10DC also allows a Self-Test to be invoked without event
preservation, but this leaves the device in a state which may
cause problems with other programs that communicate with the
CP290. It is recommended that the Self-Test always be invoked
with Event Preservation regardless of whether or not there is
any stored Event Data.)
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Signal Test
────────────────────────────────────────────────────────────────────
The Signal Test Generator is a powerful feature that enables
the user to track down and isolate X-10 transmission/reception
problems and faulty modules.  This feature will send X-10
ON/OFF commands repeatedly until the test is ended by the
user.  (Similar to the Leviton 6385 device).  The address to
be targetted for commands can be a fixed House Code and Unit
Code; alternatively, either the House Code or Unit Code (or
both) can be varied. This allows you to send commands
repeatedly to:

∙ A 'Fixed' House Code & 'Fixed' Unit Code (eg. A1)
∙ A 'Fixed' House Code & 'Variable' Unit Code (eg. A1 - A16)
∙ A 'Variable' House Code & 'Variable' Unit Code (ie. A1 - P16;
  All 256 addresses would be tested in this case)
∙ A 'Variable' House Code & 'Fixed' Unit Code (eg. A1 - P1)

When the Signal Test Generator is selected, a window is
displayed that allows you to set the House Code & Unit Code to
either 'Fixed' or 'Variable' mode; if 'Fixed' is selected then
a List Box is enabled so that the fixed code can be selected.
The Delay between commands can be set from 0 to 60 seconds;
this delay applies to the pause between each pair of ON/OFF
commands.  Once all required settings have been made the OK
button becomes enabled.  When the OK button is clicked the
test will begin; the test can be terminated by pressing [Esc].
Note, if the Delay is set to 0, then the [Esc] key may have to
be hit several times to stop the Signal Test.  X10DC will emit
a brief beep before each ON command is sent, and another lower
pitched beep before each OFF command is sent.  These beeps can
be disabled by toggling the Sounds item on the 'Options'
Menu.

'Fixed' Mode Testing
────────────────────
Generally speaking, you would want to use the 'Fixed' option
to test the range of X-10 signal reception by starting the
Signal Test using address P1 for example (the "only" address
that the Leviton 6385 will test) and then walking around to a
variety of outlet locations within your home and plugging in a
module set to P1 to see if the ON & OFF commands are being
received at all locations.  The program attempts to let you
know when the commands are sent by beeping although you may
not be able to hear the beep from all outlet locations.

'Variable' Mode Testing
───────────────────────
The 'Variable'² option can be used when you suspect that an
X-10 module has trouble receiving commands targetted for
specific House and/or Unit Codes.  In this case, instead of
walking around to locations, you would adjust the House and/or
Unit Code dials on the module as the Signal Test cycles
through each combination.  You may want to toggle the Sounds
off in this case.

────
² Not available in UNREGISTERED Version
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Clock Sync'ing
────────────────────────────────────────────────────────────────────
Clocks tend to run either fast or slow and therefore should be
synchronized periodically.  X10DC allows you to set the time
in both the PC and CP290 manually by specifying hh:mm and also
allows you to synchronize the PC and CP290 by using one of the
clocks to set the other.  When the PC clock is used to
synchronize the CP290 clock, X10DC will wait until the seconds
are at zero since the resolution of the CP290 clock is limited
to minutes.  (This wait can be cancelled by pressing the [Esc]
key).  When the CP290 is used to synchronize the PC, the hours
and minutes from the CP290 are used immediately to set the PC
Clock; since the CP290 cannot provide 'seconds', it is
recommended that a CP290->PC Clock Sync be followed by a
PC->CP290 Clock Sync.  This will ensure that both Clocks are
synchronized.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Base HouseCode
────────────────────────────────────────────────────────────────────
The Base HouseCode stored in the CP290 is only applicable to
the rocker keys on the top of the CP290.  These keys are
labelled 1 to 8 and correspond to whatever House Code is
stored as the Base HouseCode in the CP290.  The CP290
re-initializes itself whenever the Base HouseCode is changed;
as a result, all of the CP290 Event Data is erased.  X10DC
gives you the option of either Preserving or Erasing the Event
Data whenever the Base HouseCode is changed.  If the user
elects to preserve the Event Data, it is downloaded from the
CP290 before the Base HouseCode is changed and then uploaded
back to the CP290 after the Base HouseCode has been changed.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Screen Colours
────────────────────────────────────────────────────────────────────
This feature allows the user to choose their own screen
colours.  A list of screen elements is presented on the left
side of the screen and all of the available Foreground and
Background (when applicable) colours are displayed next to the
screen elements.  To change a colour, simply select the screen
element you wish to change and click on the preferred
Foreground/Background colours.  The Colour defaults can be
restored by clicking on the Colour button, similarly Black &
White colours can be selected by clicking on the Monochrome
button.  Note: some colour combinations will render the screen
unreadable, if this happens press the [Esc] key to exit the
dialogue and restore the colours to their previous setting.
Once you are satisfied with your colour selections the
Save Options command can be used to store them so that X10DC
always starts up with your selected colours.

The colours for message boxes cannot be changed (always black
on white;compiler limitation).
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Save Options
────────────────────────────────────────────────────────────────────
This menu option saves all of the current program settings
to the X10DC.INI file.  If an X10DC.INI file exists, the
program will display a Warning Message and confirm that you
wish to overwrite the existing X10DC.INI file before
proceeding.  The X10DC.INI file that X10DC generates is a
plain ASCII file that you can edit using your favourite
editor.  X10DC will ignore any errors within the X10DC.INI
file (if DEBUG MODE is on the ignored line numbers will be
displayed in the Command History box; ensure DEBUG=ON is the
FIRST LINE in your X10DC.INI).  Note that the X10DC.INI file
is parsed before command line arguments and therefore will
be overridden by contradicting command line arguments.

The Graphic Gauges setting is also set from this screen.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Graphic Gauges
────────────────────────────────────────────────────────────────────
The Graphic Gauges checkbox determines whether or not graphical
EGA/VGA characters are used to construct the sliding percentage
complete gauge.  If this causes problems with your screen
display, then uncheck the box; the ASCII character '█' 219 will
be used to paint the gauges instead.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
REGISTRATION INFORMATION
────────────────────────────────────────────────────────────────────
X10DC is currently supplied as functioning software without
built-in delays or obtrusive "nag" screens prompting you to
register.  Some features are not fully supported in the
Unregistered Version of the program.  A significant amount of
time and effort went into this program; please register the
program if you intend to use it beyond the 30 day evaluation
period.  Registered Users will be shipped a printed manual and a
3½" diskette (if you would prefer a 5¼" diskette please advise)
containing the registered version of the program which includes
the following features:

∙ Full support for the Signal Test Generator which allows you
  to cycle through all House & Unit Codes and send an ON/OFF
  command to each address.

∙ Full support for operating mode 3 which reads in an X10.DAT
  file and builds a "list box" of device names which can be
  targetted or X-10 commands.  (Unregistered Version will only
  send commands to the first 8 Devices).

∙ Support for an INI file which provides complete program
  customization capabilities including Screen Colours.

∙ BONUS PROGRAM: Registered Users will also receive a bonus
  program; X10DAT reads an X10.DAT file and prepares a report
  listing all installed devices and scheduled events including
  "frozen" events and multiple unit events. See the X10DAT.RPT
  file for a report sample.

Register via CompuServe Shareware Registration
 GO SWREG (Registration ID# 620)

   -=OR=-

Charge the registration fee to your Visa, Master Card, American
Express by ordering X10DC (Item #10924) from Public (software)
Library, call 800-242-4PsL (713-524-6394 overseas) or FAX your
order to 713-524-6398.  These numbers are for ordering only.
ALL OTHER INQUIRIES (eg. technical support, volume discounts
site licensing) should be directed to the author.  See the
Problem Resolution section for information on contacting
the author.

   -=OR=-

Register by sending $20 to:

   David Huras
   37 Ruddell Crescent
   Georgetown, Ont. L7G 5N4
   CANADA

───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Compuserve Shareware Registration
────────────────────────────────────────────────────────────────────
You can register X10DC, X10EC or BOTH using CompuServe
Shareware Registration.  The Registration Fee will be charged to
your CompuServe billing account and the latest version of the
software will be shipped within one business day. GO SWREG while
on CompuServe to use Shareware Registration.

Program Title         Program Name    Program ID#   Charge
═══════════════════   ════════════    ═══════════   ═══════
X-10 Direct Control      X10DC             620       $20.00
X-10 Event Control       X10EC            1774       $25.00

X-10 Control Bundle      X10CB            1775       $40.00
(X10DC + X10EC)

Shareware Registration (SWREG) will prompt you through the
registration process; you can register programs by referring to
them by program name or ID #.  SWREG will display a description
of the program and prompt you to confirm the registration order;
you have the opportunity to abandon the registration process at
any time.
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
UPGRADE INFORMATION
╔══════════════════════════════════════════════════════════════╗
║REGISTERED USERS of prior versions of X10DC can upgrade to the║
║current version at ANY TIME by simply sending a diskette      ║
║containing their registered version of the software and $2    ║
║for postage to the address above.                             ║
╚══════════════════════════════════════════════════════════════╝
───────────────────────<End of Topic>────────────────────────────────
.TOPIC:
Special Thanks
────────────────────────────────────────────────────────────────────
SPECIAL THANKS to Gary Soles, Beta Tester.
───────────────────────<End of Topic>────────────────────────────────