X10 AUTOMATE DOMOTIQUE V2.43D, AUTOMATE DOMOTIQUE PRO V2.43D User Manual

Automate Domotique

v2.43d

Automate Domotique PRO

v2.43d

ABLE OF CONTENTS

WELCOME TO AUTOMATE DOMOTIQUE 1

WHAT’S INCLUDED ............................................ 1

WHAT YOU NEED................................................ 1

INSTALLING AUTOMATE DOMOTIQUE......... 2

INSTALLING AUTOMATE DOMOTIQUE.................. 2

INSTALLING THE EVENT MANAGER SOFTWARE.... 2

Starting Out ................................ ..................3

AUTOMATE DOMOTIQUE SPECIFICATIONS

.............................................................................4

ELECTRICAL SPECIFICATIONS ............................. 5

PROGRAMMING SPECIFICATIONS......................... 5

WHAT IS EVENT MANAGER.........................6

HOW EVENT MANAGER WORKS..........................6

Device DataBase................................ ...........6

Events...........................................................6

SCREEN TYPES................................ ................... 6

EVENT MANAGER WINDOWS.............................. 6

WHAT IS X-10....................................................7

X-10 ADDRESSES............................................... 7

X-10 THEORY................................ .................... 7

DIM/BRIGHT LIMITATIONS.............................. 7

EVENT BASICS.................................................8

WHAT IS AN EVENT ................................ ............ 8

Event Type ....................................................8

Logic Type ................................ ....................9

Compound AND/OR.................................... 10

Nesting........................................................ 11

Summary of valid ‘IF’ conditions ................ 11

Summary of valid ‘THEN’ actions:.............. 12

EVENT PROCESSING ......................................... 12

Fast Events ................................ ................. 12

Standard Events................................ .......... 12

IF Always Examples.................................... 13

A QUICK TOUR OF EVENT MANAGER..... 15

A CASE STUDY: OTTO MASHON....................... 15

CREATING A DEVICE DATABASE .............19

DEFINE X-10 ................................................... 19

DEFINE TIMERS................................................ 20

DEFINE TIMELABELS........................................ 20

DEFINE FLAGS ................................................. 21

DEFINE VARIABLES.......................................... 22

DEFINE IF MACROS.......................................... 22

DEFINE THEN MACROS................................... 23

DEFINE IR/IO-XPANDERS................................. 24

Automate Domotique PRO & IO-Xpander Setup

................................................................... 24

Analog Inputs................................ .............. 25

Digital Inputs.............................................. 27

Relay Outputs..............................................28

USING THE EVENT EDITOR ....................... 29

TOOLBOX ................................ ........................29

REATING AN EVENT

New Event.................................................... 29

Fast Events..................................................29

Event - Add..................................................29

Event - Edit ................................................. 29

Event - Delete..............................................30

DITING AN EVENT

DELETING AN EVENT ........................................30

IF CONDITIONS ................................................31

X-10 Device State................................ ........ 31

X-10 Sequence............................................. 34

If Timer........................................................35

If Flag ................................ ......................... 37

If Variable ................................................... 37

IF Macro................................ ..................... 38

If Comment.................................................. 39

If Time......................................................... 39

If Time Label ............................................... 40

If Date.........................................................40

If SunRise/SunSet ......................................... 41

If ASCII In................................................... 42

AND Statement ............................................43

OR Statement................................ ............... 44

If System Variables......................................44

If Digital Input................................ ............. 45

If Analog Inputs...........................................45

If Relay Output ............................................46

If Infrared ................................ .................... 46

If HVAC....................................................... 47

THEN/ELSE ACTIONS..................................... 48

X-10 Device.................................................48

Timer/Delay................................................. 49

Flag.............................................................50

Variable....................................................... 51

Message Logging.........................................52

THEN Macro............................................... 52

Comment ................................ ..................... 53

IR Command................................................ 54

ASCII Out.................................................... 54

Nested IF/THEN..........................................56

Relay Output................................................57

HVAC.......................................................... 57

MENU CHOICES ............................................ 57

FILE.................................................................57

File - New ................................ .................... 57

File - Open..................................................58

File - Save ................................................... 58

File - Save As ................................ .............. 58

File - Rules Check ................................ ....... 58

File - DownLoad................................ .......... 58

File - Print ................................................... 59

File - Exit ................................ .................... 59

EDIT ................................ ................................59

Cut .............................................................. 60

Copy............................................................60

........................................29

...........................................30

Paste........................................................... 60

Freeze.........................................................60

Thaw................................ ........................... 60

DEFINE............................................................ 60

TILITIES

........................................................ 61

Mega Controller..........................................61

Stop Schedule................................ .............. 62

Start Schedule................................ ............. 62

Clear Schedule............................................62

Time Set......................................................62

X-10 Signal Test ................................ .......... 63

System Info.................................................. 63

Message Log...............................................64

Self Test ...................................................... 64

Modem........................................................ 64

Options ....................................................... 67

Time Setup .................................................. 67

POWER FAILURE........................................... 68

FCC COMPLIANCE........................................69

GLOSSARY OF TERMS.................................70

APPENDIX A - LOCATION ............................ 71

APPENDIX B - EXAMPLES............................77

APPENDIX C - TROUBLE SHOOTING........79

APPENDIX E - IO REFERENCE.................... 81

YSTEM OVERVIEW

.......................................... 81

Definition of Terms ..................................... 81

Getting Started ............................................ 81

Setting the IO-Xpander Address.................. 82

Connecting the SD-Net Cable......................82

DEFINING YOUR IO-XPANDER........................... 84

ROUBLE-SHOOTING

IO T

................................... 84

IO SPECIFICATIONS.......................................... 85

SD-Net Specifications..................................85

Opto Inputs................................................. 85

Relays.........................................................85

Analog Inputs................................ .............. 85

Power Requirements.................................... 85

IO APPLICATIONS....................................... 86

Input Applications ................................ ....... 86

Relay Applications................................ ...... 87

Analog Applications....................................88

Miscellaneous Applications ......................... 90

INDEX................................ ............................... 91

Welcome to AUTOMATE DOMOTIQUE

Automate Domotique and Automate Domotique PRO are powerful interactive automation system that integrates control of the different subsystems throughout a home or business including Lighting, Security, Entertainment (Audio/Video), Heating/Cooling, Irrigation, etc. The system can be controlled by computers, X10 controllers, in-wall keypads, wireless keypads (RF remotes), infrared remotes, analog and digital inputs, and time/event schedule. Automate Domotique features include:

??2-Way X10 Communication

appliances.

??2-Way IR Com munication

video, home theater, and other infrared-operated equipment.

??2-Way SERIAL Communicatio

other serial devices (thermostats, weather stations, etc.).

??INPUTS AND OUTPUTS

interfacing with security systems, heating/cooling systems, irrigation, etc.

??Built in Battery Backup ??External Battery Backup

operation during power outages.

??Real-time clock/calendar ??SunRise/SunSet calculations ??X10 Sequence Feature

pressing A-1 A-2 A-1 within 3 seconds could dim the lights.

??Message Log ??Security Mod ??Expansion port ??Power Fail Catch-up

- Your schedule can log any Event you specify with a time-date stamp attached e - Have your front porch light (and/or other devices) come on at ‘approximately’ the time you specify.

- for add-on products

- Sends and Receives standard and advanced X10 signals for control of lighting and

- Sends and Receives infrared signals (with optional InfraRed Xpander™) for control of audio,

n - Sends and Receives ASCII via RS-232 ports for connection to computer, modem and

- (Automate Domotique PRO ) 16 Digital / 8 Analog Inputs, 8 Relay Outputs (expandable) for

- saves your schedule in case of power outage. – (Automate Domotique PRO ) allows connection of 12V battery (optional) to maintain system

- automatically adjusts for Daylight Savings and Leap Year.

- A series of X10 commands within a defined time window can trigger an Event. For example,

- returns devices to their scheduled state when power fails and is then restored.

What’s Included

In addition to this manual, your Automate Domotique package contains:

One Automate Domotique or Automate Domotique PRO

One AC power adapter

One 4-Conductor Modular cable

One DB9-DB25 adapter

Program Diskettes - Event Manager Software

One Powerline Interface Module (TW523 or Equivalent)

What you need

An IBM PC-AT or 100% compatible computer capable of running Microsoft Windows , with an asynchronous serial port.

A 3.5" high-density floppy disk drive for software installation.

A hard disk with at least 1.6 mega-bytes available or a high capacity floppy diskette drive.

Microsoft Windows 3.1 or higher or Win95.

Installing AUTOMATE DOMOTIQUE Installing Automate Domotique

Choose a mounting location accessible to a continuously powered ac source

1. Turn off your PC.

2. Plug one end of the 9 pin Serial cable into Automate Domotique,s RS-232 port.

3. Plug the other end of the 9 pin Serial cable into your PC’s serial port (use the DB9-DB25 adapter if needed).

4. Plug one end of the modular TELEPHONE type cord into the Power Line Interface module.

5. Plug the other end of the cord into the Automate Domotique jack labeled “P.L.I.”.

6. Plug the Power Line Interface into an AC outlet.

7. Plug the power transformer into Automate Domotique’s Power-In jack.

8. Plug the power transformer into an AC outlet.

9. Restart your PC.

AUX P.L.I.

TW523

To IR Remote or IO Devices

TO SERIAL PORT OF COMPUTER

DB9-DB25 ADAPTER (if needed)

POWER

POWER TRANSFORMER DB9 MALE

DB9 FEMALE

RS232

Note: Do not plug the Power Line Interface into a filtered outlet or power s trip - this will degrade X10 signals!

Installing the Event Manager Software

Before installing Event Manager, you should copy the distribution disks onto a set of working disks, then store the original disks for safekeeping.

Event Manager comes with an installation program that will copy the various parts of the Event Manager software onto the drives and directories that you specify. The program’s menus and prompts will lead you through the install process.

To Install:

Start Microsoft Windows.

1. Insert Setup disk in drive A

2. From Program Manager (Windows 3.1X), select File menu and choose Run (Win95 select START and choose Run).

3. Type a:\setup and press ENTER

A comprehensive installation/setup program will take over at this point. You will be prompted for directory information, drive, etc. Each prompt will contain default (recommended) information.

After the Install program is done, a Setup program will start to allow you to set Event Manager parameters.

Starting Out

After connecting all cables and completing the Setup program it is time to start the Event Manager Software and test communications.

Starting Event Manager

Windows 3.1X: Double click with your mouse on the Automate Domotique WinEVM icon located in the WinEVM group.

Win95: Select START, then select PROGRAMS, select WinEVM, then select WinEVM.

Event Manager will load your Device DataBase and the last Schedule that you were working on. If this is the first time you have used Event Manger, no Device DataBase will exist and a blank one will be created for you.

Testing Communications

Select Utilities | System Info. If you see a screen appear with various system parameters, then the communication path between your PC and Automate Domotique is working. If an error occurs:

1. Make sure you have specified the correct Com port.

2. Windows cannot support shared hardware interrupts. Since COM1 and COM3 (also COM2 and COM4) share the same interrupts, you cannot have one serial device installed on COM1 and the other device installed on COM3 (or one device on COM2 and another on COM4).

3. If you have an external modem, check that it is connected to a serial port. If you have an internal modem, check the switch setting (on the board) to ensure that it is assigned to the appropriate COM port.

4. Select the Serial Port option from the System menu to check that your specification of the COM port is correct. If you cannot start WinEVM, use an editor to display the C:\WINDOWS\WINEVM.INI file. There is a line under the section entitled [WinEVM] that should appear as: COMPORT = n , where n = 1 to 4.

5. There are a number of TSR (Terminate and Stay Resident) programs that are provided with voice fax modem boards. If you have installed another software package that utilizes your board, make sure this program is not running when you start Windows and SuperVoice. If it is still running, it will assume control of the Com Port and no other programs will have access to this port. Check your AUTOEXEC.BAT file to ensure that the program is not loaded during the boot up routine

Automate Domotique Specifications

Automate Domotique

The Automate Domotique Front Panel contains two LED status indicators.

XMIT REC

Both LED’s are normally ON. The “XMIT” LED (green) will flash when Automate Domotique transmits an X-10 command. The “REC” LED (yellow) will flash when Automate Domotique receives an X-10 command. Both LED’s will flash at a 1-second interval if the PSC05 is not plugged in and attached to the Automate Domotique.

Automate Domotique PRO

The Automate Domotique PRO contains three LED status indicators.

FRONT

XMITREC NET

The green and yellow LED’s are normally ON. The “XMIT” LED (green) will flash when Automate Domotique PRO transmits an X-10 command. The “REC” LED (yellow) will flash when Automate Domotique PRO receives an X-10 command. They will flash at a 1-second interval if the TW523 is not plugged in and attached to the Automate Domotique PRO.

The “NET” LED (red) will flash indicating network activity (although it will still flash even if there are no IOXpander’s attached). The flash rate is dependant on Schedule size, the larger the Schedule, the slower it will flash.

Electrical Specifications

Power Supply 12VDC Plug-In Transformer Transmission Rate: 9600 bps asynchronous Data Format: 8 Data Bits, No Parity,

One stop Bit

Screw Terminals Digital Inputs,

Analog Inputs, Relay Outputs

Compatibility IBM or compatible

w/asynchronous serial port

Required Operating System

Windows 3.1x or Win95

Required Disk Space 2 Mbytes Physical Size: Automate Domotique

1.5” H, 6.5” D, 5.5” W Automate Domotique PRO

1.5” H, 6.5” D, 8” W

Digital Inputs

Quantity 16 (expandable to 80) Type Non-polarized, opto-

isolated

Isolation 500 V channel-channel &

channel-ground

Input Range 4-24V DC or AC (50-1,000

Hz)

Input Resistance 470 ohms min Response Time 100 milliseconds typ,

requires pulse width of 100 milliseconds

Analog Inputs

Quantity 8 (expandable to 40) A/D Type Successive approximation Resolution 8 bit (20mV/bit) Input range 0-5 V(uni-polar) Filtering none Conversion Time 20us type, 30us max Linearity +/- 1 bit Accuracy 0.2% of reading +/- 1 bit Input Current 100 nA max at 25 degrees C

Relay Outputs

Quantity 8 (expandable to 40) Contact Rating 2A @ 24 VDC Contact type Gold overlay silver Contact resistance 100 milliohms max (initial) Contact arrangement SPDT Operating time 20 milliseconds max Release time 10 milliseconds max Life rating Mechanical: 10 million

operations min

Electrical: 100,000 min

@ full load

Programming Specifications

X-10 Devices 256 Timers 32 Time Labels 32 Flags 256 Variables 256 IF Macros 16 THEN Macros 256 IR Commands 500 (with optional JDS InfraRed Xpander™) Lines of Code approx. 3000-4000 (based on actual schedules, each IF condition or THEN action uses different amounts

of memory)

What is Event Manager

Event Manager is the user interface that runs on your PC that lets you create schedules for use with AUTOMATE DOMOTIQUE. With Event Manger, you can create and edit schedules that once downloaded into AUTOMATE DOMOTIQUE, allow total control of your home or office.

How Event Manager Works

The following flowchart shows the steps for creating a schedule and demonstrates how Event Manager works with AUTOMATE DOMOTIQUE.

Device DataBase

Before you create a Schedule for AUTOMATE DOMOTIQUE, it is recommended that you create a Device DataBase. This tells the Event Manager what devices are in your home. Devices may be added, changed or deleted in the Device DataBase at any time.

Events

An Event consists of an “IF” section (conditions), followed by a “THEN” section (actions). If the IF section is true, the THEN section is executed. If not, the THEN section is skipped.

START

CREATE

DEVICE

DATABASE

CREATE

SCHEDULE

Screen Types

There are many types of Event Manager screens. The main screen will show the main menu bar, the time and date and the current schedule in the editor workspace.

Event Manager User’s Guide The menu bar is your primary access to all the menu commands. If a menu command

is followed by an ellipsis mark (...), choosing the command displays a dialog box. A command without an ellipsis mark indicates that once you choose it, that action occurs.

ADD/DELETE/EDIT

EVENTS

DOWNLOAD

SCHEDULE

END

Event Manager Windows

Most of what you see and do in the Event Manager environment happens in a window. A window is a screen area that you can move, close and open. Only one window can be active at any time. The active window is the one that you’re currently working in. Any commands you choose or text you type generally applies only to the active window. Event Manager makes it easy to spot the active window by highlighting the window title. If your windows are overlapping, the active window is always the one on the top of all the others (the foreground).

What is X-10

The X-10 POWERHOUSE System is a line of home automation products designed to control lights and appliances using existing electrical wiring as a communications medium. X-10 is the “De Facto” standard for Power Line Carrier (PLC) transmission. The code format was first introduced in 1978 and is compatible with many manufacture’s versions of PLC devices.

X-10 Addresses

All X-10 receiver modules have two code dials: a house code dial and a unit code dial. There are 16 house codes, ranging from the letters A to P. There are also 16 unit codes, ranging from 1 to 16. That means there are 256 possible combinations of module addresses.

X-10 Theory

X-10 is based on a technique known as carrier current communication. High frequency bursts are sent out over the power line that are received by the receiver modules. The high frequency bursts, or bits, are sent to coincide with the zero crossing of the AC power line. The receiver modules know to start listening to the AC line for a bit sequence when it detects a zero crossing. The format used by X-10 is an 11-bit sequence consisting of a start code, a house code, and either a function code or a module number. The first 2 bits represent a Start Code, the next four represent the HouseCode, and the last five represent the KeyCode, either a NumberCode (1 through 16) or a Function Code (ON, OFF, All Lights On, etc.). This complete block, (StartCode, HouseCode, KeyCode) is always transmitted at least twice.

Power Line Cycles

11 2 4 5

Code

Code transmitted when a number button is pressed

Start Code

Code transmitted when a Function button is pressed

House Code Code

NumberStart

Start Code

House Code Code

Number

FunctionFunction

To understand why an X-10 transmission can only contain either a module number or a function code, you need to understand how a manual X-10 system works. Use the MegaController to see what is being sent when a button is pressed from a manual control console. You will see that when a number button is pressed, it sends the HouseCode-NumberCode to select the module. When a function button is pressed, it sends the HouseCode-FunctionCode to control the selected module.

DIM/BRIGHT Limitations

The Power Line Interface can receive Dim and Bright codes, but the output will represent the first Dim or Bright code received, followed by every third code received, i.e., the output from the Power Line Interface will not be a continuous stream of Dim or Bright codes as transmitted.

What this means to AUTOMATE DOMOTIQUE: AUTOMATE DOMOTIQUE keeps track of Dim/Bright levels for any of the 256 X-10 devices. Since AUTOMATE DOMOTIQUE cannot reliably receive Dim/Bright codes sent by another X-10 controller, any Dim or Bright code received by AUTOMATE DOMOTIQUE will be ignored. This means that as long as you use AUTOMATE DOMOTIQUE to dim or brighten a light, it will know exactly what level of brightness the light is at. But if you dim or brighten a light using a controller other than AUTOMATE DOMOTIQUE, AUTOMATE DOMOTIQUE will ignore those commands and not update the Dim/Bright level for the light.

The Bottom Line - If you use AUTOMATE DOMOTIQUE to control dim/bright levels, dimming or brightening using another X-10 controller or at the switch itself, will cause AUTOMATE DOMOTIQUE to get out of sync with what the real level is.

Event Basics

“Junior, IF you eat your vegetables, THEN you can watch TV, ELSE you’re going to bed!”

This section gives you an overview of what an Event is and how it is used in a schedule. An understanding of the Event Concept is very important to make the most of AUTOMATE DOMOTIQUE. Be sure that you understand this concept before you create your own schedule.

What is an Event

An Event consists of an “IF” section, followed by a “THEN” section. If the IF section is true, the THEN section is executed.

Event Type

There are two types of Events, the IF-THEN and the IF-THEN-ELSE.

IF-THEN

The simplest form of an Event is an IF-THEN: if

condition is true then do action end If the condition is true, then the action is executed. This simple form of an IF statement gives you the choice of executing an action(s) or skipping it. For instance, if the opening statement was put into an IF-THEN statement, it might look something like this:

if eat your vegetables then watch TV end

IF’s are easy to understand because we use them constantly in our daily conversations.

IF-THEN-ELSE

Event Manger also lets you choose between two actions with the IF-THEN-ELSE structure. if

condition is true then do action1 else do action2 In the previous example, if the condition is true, the first action is executed, if the condition is false, the action following the else statement is executed.

For example, if the opening statement was put into an IF-THEN-ELSE statement, it might look something like this: if

eat your vegetables then watch TV else goto bed end IF Junior eats his vegetables, he can watch TV, IF he does not, he will have to go to bed.

FAST EVENT

Fast Events are Events triggered by X10 ON/OFF commands and Digital Inputs (AUTOMATE DOMOTIQUE 's) going ON/OFF. These events are executed immediately when triggered regardless of schedule size. A Fast Event can be placed anywhere in the schedule.

Logic Type

The Event’s Logic Type refers to whether the IF conditions will be ‘ANDed’ or ‘ORed’ together when determining if the THEN/ELSE actions should be executed.

AND

If ‘AND’ is chosen, all of the conditions must be met before any action will be taken. EVENT

If eat vegetables and dishes washed Then watch TV End

In this example, Junior must eat his vegetables and wash the dishes to get to watch TV, only doing one will not work. This is what the AND does: All of the conditions must be true in order to make the actions happen.

If ‘OR’ is chosen, only one condition has to be met before any action will be taken. Suppose Junior’s mother decides not to be so tough, changing the orders to, “Eat you vegetables or wash the dishes and you

can watch TV”.

EVENT If eat vegetables or dishes washed Then watch TV End

Now junior has a choice, either eat his vegetables or wash the dishes, and he will be able to watch TV. This is what the OR does: Only one of the conditions has to be true in order to make the actions happen.

Any number of IF conditions can be combined to control any number of THEN actions. For example:

EVENT sample event If condition 1 is true and condition 2 is true and condition 3 is true and condition 4 is true Then

do this action End

In this example, all the conditions must be met before the ‘THEN’ action will be executed. More than one action may be executed in the ‘THEN’ section of the event.

For example:

EVENT sample event If

condition1 is true

or condition2 is true Then do action1

do action2

Else do action3 do action4 do action5 do action6 End

In this example, if condition1 is true or condition2 is true, then do action1 and action2, if neither condition is true, then do action 3, 4, 5 and 6.

A more meaningful Event would use real conditions to control real devices. For example:

EVENT sample event If Time = 6:00 PM .MTWTF. Then (X: Frontporch Light B 3) ON End

In this example, when the time is equal to 6 PM on any weekday but not weekends, the Frontporch Light turns on.

EVENT sample event If (F: Alarm Activated) is SET and Time = 6:00 PM .MTWTF. Then (X: Frontporch Light B 3) ON End

In this example, if the flag ‘Alarm Activated’ is set

the time is equal to 6 PM on any weekday but not weekends, turn on

and

the Frontporch Light.

Compound AND/OR

Event Manager can use compound AND/OR logic. As an example:

EVENT AND/OR Sample Event If (X:Make Coffee C 1) is ON

-AND Time = 6:00 AM .MTWTF.

or Time = 10:00 AM S.....S

Then (X: Coffee Maker C 2) ON (X: Make Coffee C 1) Idle Delay 01:00:00 (X: Coffee Maker C 2) OFF End

In this example, Otto defines a ‘Make Coffee’ switch as X-10 address C1. He turns this switch ON at night only if he puts coffee and water in the coffee machine. If this switch is ON -AND-, it’s 6 AM weekdays OR 10 AM weekends, then turn on the coffee maker, set the ‘Make Coffee’ switch to Idle, then turn off the coffee maker after 1 hour.

Event Manager can use compound OR/AND logic as well. As an example:

EVENT OR/AND Sample Event If (X:Alarm Active L 1) is ON and Time = 6:00 PM SMTWTFS

-OR (X:Alarm Active L 1) is OFF and Time = 8:00 PM SMTWTFS Then (X: Front Door B 1) ON (X: Garage Light B 2) ON End

In this example, Otto wants his outside lighting to turn on at a different time based on whether or not the security system is set. If the security system is ON and it’s 6 PM, -OR-, the security system is OFF and it’s 8 PM, then turn on the Front Door and Garage lights.

Nesting

Nesting is a way to add complex decision making into your Events. The maximum number of Nested Events is 3.

Summary of valid ‘IF’ conditions

Time equal to hh:mm days hh = hour , mm = min, days = SMTWTFS Time is less than hh:mm days hh = hour , mm = min, days = SMTWTFS Time is greater than hh:mm days hh = hour , mm = min, days = SMTWTFS Time Label Label given to a certain time Date (equal, before, after) Equal to SunRise /SunSet days days = SMTWTFS Before SunRise/SunSet days days = SMTWTFS After SunRise/SunSet days days = SMTWTFS X-10 Device State = ON/OFF/IDLE Module A1 - P16 X-10 Sequence Up to 6 sequential X-10 commands within a specified time window Timer = Running, Stopped, Expired 32 timers (1 second resolution) Flag = Set/Clear/Idle 256 flags Variable “=”,“>”,“<” ,etc (0-255) 256 variables IF Macro A series of ‘IF’ conditions ASCII Input Up to 32 characters System Variables Power Restore, X-10 loss, First Schedule Pass, Power loss Digital Inputs ON/OFF/Toggles/GOES On/GOES Off states of Digital Inputs Analog Inputs Value of Analog Input (0-255) Relay Outputs On/Off IR Sequence Up to 10 sequential IR commands within a specified time window IR Power Sensor 4 Power Sensors

Any combination of ‘IF’ conditions may be combined in an Event.

Summary of valid ‘THEN’ actions:

X-10 Device = ON/OFF/DIM/BRI Module A1 - P16 All Lights On HouseCode A-P All Lights Off HouseCode A-P All Units Off HouseCode A-P Timer Load/Clear/Start Flag Set/Clear Variable Load/Clear/Inc/Dec Message Log 8K of message space Then Macros Series of ‘THEN’ actions ASCII Output Up to 32 characters IR Commands IR Commands sent by InfraRed-Xpander Relay Outputs On/Off control of Relays

Event Processing

After you download a Schedule to AUTOMATE DOMOTIQUE, AUTOMATE DOMOTIQUE will start with the first Event, check ‘IF’ conditions and do any actions, go on to the next event, do the appropriate actions, and so on until the end of the schedule is reached. AUTOMATE DOMOTIQUE then starts over at the beginning of the Schedule evaluating the first Event.

Fast Events

Standard Events

Standard Events are based on an IF statement(s) and THEN actions and are processed in sequential order. Utilities | System Info will list the total time to complete one pass through a schedule.

When an event is evaluated, AUTOMATE DOMOTIQUE checks if the logic type of the Event is AND or OR. AUTOMATE DOMOTIQUE will use the logic type to evaluate the conditions and decide whether to take the required action(s). For AND logic events, all the conditions must be true, for the OR logic events, only 1 condition has to be true.

Example 1 IF/THEN/ELSE

EVENT sample event If After SunSet SMTWTFS or Before SunRise SMTWTFS Then SET (F:It’s Dark) Else CLEAR (F:It’s Dark) End

Start

Event 1

Event 2

Event 3

Last Event

(First Event)

(Last Event)

The flag “It’s Dark” will be set if, the current time is after SunSet on any day, or if the current time is before SunRise on any day of the week, otherwise the flag “It’s Dark” will be cleared.

Example 2 IF/THEN/ELSE

EVENT sample event If Time is After 5:00 PM .MTWTF. and Time is Before 8:00 PM .MTWTF. Then (X:Security Light B 7) ON Else (X:Security Light B 7) OFF End

This event will turn on the X-10 device that has the name “Security Light” if, the time is after 5 PM during weekdays

and

before 8 PM during weekdays. The event would turn the “Security Light” off when the time is not between 5 PM and 8 PM weekdays.

Important Note If the Event is

not

‘IF Always’, each time an Event is evaluated, AUTOMATE DOMOTIQUE will not execute any action unless the conditions have changed since the last time the Event was evaluated. If the Event is ‘IF Always’, every time an Event is evaluated, AUTOMATE DOMOTIQUE will execute the actions if the IF conditions ar e met.

Using the previous example, if the current time was 4:59pm on Monday, the event would evaluate as not true (the first condition was not true, i.e., the current time was not after 5 PM), since during the previous evaluation cycle, the event evaluated as not being true, no changes occurred so no actions would take place. When the current time changes to 5 PM, both conditions are met (it is after 5 PM and before 8 PM), and the THEN actions are processed. On subsequent evaluation cycle no actions will be processed until the time is after 8 PM (because both IF’s are still true), whereas the event evaluates as not true, and the previous evaluation cycle evaluated as being true, the ELSE actions will be processed.

Example:

EVENT: sample event If

Time = 5:00 PM S.....S

and (X:HotTub B 5) is ON Then (X:HotTub Blower B 6) ON End

In this example, IF the X-10 device ‘HotTub’ is ON,

the current time is 5 PM on Saturday or Sunday, THEN turn the X-

and

10 device ‘HotTub Blower’ ON. Example:

EVENT: sample event If

Time equals 5:00 PM S.....S

or Time equals 6:00 PM .MTWTF. Then (X:Porch Light B 3) ON End

In this example, IF the current time is 5 PM on Sat or Sun, or the time is 6 PM on Mon-Fri., THEN turn on the X-10 device ‘Porch Light’ ON.

IF Always Examples

The Event in Example 1 is an ‘IF Always’ type of Event. When A-1 is turned ON, AUTOMATE DOMOTIQUE will send the ‘B-1’ ‘B-ON’ X-10 command followed by a 2 second delay, and keep repeating this command as long as A-1 is on. This type of Event will keep executing the actions as long as the if condition(s) stay true. When using “IF Always” it is recommended that you insert some delay to allow time for other X-10 commands to be processed. In Example 2, when A-1 is

turned on, AUTOMATE DOMOTIQUE will send the ‘B-1’ ‘B-ON’ command once, until A-1 is turned OFF and ON again. This type of Event must see the conditions change before the actions are executed.

Example 1:

EVENT: If Always (X: A 1) is ON Then (X:B 1) ON Delay 0:00:02 End

Example 2:

EVENT: If (X: A 1) is ON Then (X:B 1) ON End

A Quick Tour of Event Manager

A Case Study: Otto Mashon

Otto Mashon just completed his installation and is ready to start automating. He starts by automating his study. Otto has always wanted to push a single button on his mini-controller to activate his Overhead Lamp and the Radio.

For a quick test, Otto creates a simple schedule to turn on A7 (Overhead Lamp) and J2 (FM Radio) whenever M5 (button 1 on his mini-controller) is pressed.

Otto begins by making a list of the X-10 devices. The list consists of the button on the mini-controller, the lamp and the radio. Once Otto’s list is completed, he begins to create his Device DataBase

NAME LOCATION DESCRIPTION HOUSE/UNIT Address Study Lamp Study Overhead Lamp A-4 Radio Study FM Radio A-12 Switch1 Study Mini-Controller B-4

Otto must define devices in his Device DataBase before he can use them in a schedule. This is done by selecting the Define | X-10 Device menu choice.

From here, Otto fills out the X-10 Device Definition Dialog Box with the information for each X-10 device that he wants to control and for each type of X-10 controller that will be used (the mini-controller in this example).

When Otto is satisfied with the names and selections for the three devices that he will be using, he leaves the X-10 Device List menu by pressing the [OK] button.

Now that Otto has the mini-controller, lamp and radio defined in the Device DataBase he wonders,

10 devices to work together”

have both the Study Lamp and Radio to turn on. Likewise, when he leaves, he wants to turn the Study Lamp and Radio off with one button.

Otto starts thinking to himself, “

Lamp and the Radio. Lets see;

. He decides that when he enters his study, he wants to press a button on his mini-controller, and

Now how will this work? If the switch on the mini-controller is ON, then turn ON the Study

”

“How do I want these X-

if the mini-controller switch is ON then turn the Study Lamp ON turn the Radio ON end

Since he hasn’t created any Events yet, his Editor Workspace shows a schedule that is empty and is untitled.

Otto’s first step is to create an Event. He creates a new Event by pressing the [New] button in the right side ToolBox. He fills out the Event Definition dialog box with the name and description of the Event. In this example the name is “Study”, the Event type is “IF-THEN”, the logic type is “AND” and the insert point location is “After this Event”

When satisfied with his selections, he presses the [OK] button to accept the new Event. The new Event named “Study On” shows up in the Editor Workspace.

Looking at the workspace Otto wondered how he could make the lamp and radio turn on when he presses the mini-controller button. “ by moving the highlight bar onto the ‘IF’ statement and pressing the [Add] button in the ToolBox. A popup menu appeared and he chose `X-10 Device State’ since that is the type of device that he wants to use in this Event. After selecting ‘X-10 Device State’, another popup window appeared. Otto chose `Switch 1' from the list and the `ON’ radio button. “

what I want ?

“

Now that the `IF’ part of my Event is correct, I have to add the Study Lamp and Radio in this somehow

adding an Action statement the same way he did the IF condition statement, by moving the highlight bar onto the ‘THEN’ statement in the Event, and pressing the [Add] button in the ToolBox.

He chose ‘X-10 Device’ from the ‘THEN Action’ popup window and was put into the X-10 Device Action dialog box.

Well, the first thing I have to do is make the button push on my mini-controller be the IF statement

”, Otto thought, “

If Switch 1 is ON, yes that’s it

”. He presses the [OK] button to accept this choice.

”. He does this

Now is this

”. Otto did this by

Otto moves the highlight bar onto the Study Lamp and chose the ON radio button from the list of actions. “

”, Otto thought while pressing the [OK] button. The Event is updated with this selection. “

easy the Radio and I’ll be done

Otto again selects the [Add] button in the ToolBox and the THEN Action popup window appears. Otto chose ‘X-10 Device’ and the X-10 Device dialog box appeared. He selects ‘Radio’ by highlighting it in the list box and pressing the ON radio button.

Otto decided that this Event was complete and he wanted to see if it would work. Otto saved the schedule first by selecting the Schedule | Save As menu, entering the name “sample” and pressing the [OK] button. To download the schedule into AUTOMATE DOMOTIQUE, Otto selects the Schedule | DownLoad menu.

Otto chose ‘[x] Download Schedule’ since he wanted to download his newly created schedule and the ‘[x] Download Device Database’ option. With ‘Download Device Database’ selected, AUTOMATE DOMOTIQUE will be downloaded with the Initial State values that were defined in the Device DataBase. AUTOMATE DOMOTIQUE keeps track of all Devices and whether they are ON or OFF and by downloading the Initial States, you can pre-define an X-10 Device to be ON or OFF. This is normally used for the first download only.

Pressing [OK], the schedule is downloaded and Otto was put back in the Workspace. Otto, eager to try his new schedule, presses the “B4-ON” button on his mini-controller. This turned on the Study Lamp and

Radio. Having created his first Event to turn the on the Study Lamp and Radio, Otto is eager to create another to turn them off.

So Otto goes back to work to define a new Event, one that will turn the Study Lamp and Radio off when the mini-controller switch is turned off. Since he is using X-10 devices that have been defined already, Otto does not have to define any new ones.

Otto decides that this Event will turn the Light and Radio OFF when the mini-controller button “B4-OFF” is pressed. He creates a new Event by pressing [New Event] in the ToolBox. He fills out the Event Definition dialog box and names this Event ‘Study Off’.

”, mused Otto.

Now, all I have to do is add

This is getting

When satisfied with his selections, Otto presses the [OK] button to accept the new Event. “I will make this Event work just like the first one, except replace the ON’s with OFF’s.” He did this by moving the

highlight bar onto the ‘if’ statement in the Event and pressing the [Add] button in the ToolBox. A popup menu appears and he chooses ‘X-10 Device’.

The ‘X-10 Device’ dialog box appeared and he selects ‘Switch 1’ from the list of devices and the OFF’ radio button. Otto presses the [OK] button to accept this choice.

Otto adds the Study Lamp and Radio, turning both of them OFF, to the ‘then’ part of the Event in same manner as he did in the first Event.

Otto decides that the new Event is complete and he wants to try it out. He saves the schedule first by selecting the menu, since the schedule has already been named, Otto saves it under the same name. Otto then selects the menu.

Otto chooses ‘Download Schedule’ from the DownLoad options but not the ‘Download Device Database’ option since he did not want to change the internal states in AUTOMATE DOMOTIQUE, as they now reflect the actual states of these devices. Pressing [OK], the schedule is downloaded and Otto is back in the Workspace.

Otto presses the “5-ON” button on his mini-controller, and the Study Lamp and the Radio turns on. He then presses the “5-OFF” button, the Study Lamp and Radio turns off. “This is what it’s all about”, murmured Otto as he began defining new Events.

Otto is well on his way to an automated home. He has mastered the concept of defining devices in the DataBase and creating a basic IF-THEN Event.

Schedule | Save

Schedule | DownLoad

Creating a Device DataBase

One of the first steps to take before creating a Schedule is to create your Device DataBase. This DataBase contains your X-10 devices (appliance, lamp and remote control types), Timers, Variables and Flags. Once a device has been created it can be used in any Schedule.

Starting Out

The first place to start would be to make a list of all the X-10 type devices you have in your home or office. Once you have your list, we suggest that you spend the time to enter these devices into the DataBase. It may seem like a lot of work at first, but it will save you a lot of time down the road if you decide to change the X-10 address of your devices.

Note Event Manager can only handle 1 Device DataBase, and all Schedules created will use this Device DataBase. If you need to have a different Device DataBase, for example, if you have another home or customer that has different Device needs, cre ate another directory and copy all the files from the ‘AUTOMATE DOMOTIQUE’ directory.

The Define Menu is where all the Devices are defined, including X-10, Timers, Time Labels, Flags, Variables, Macros, IR, I/O and HVAC.

Define X-10

The Define | X-10 command will open the X-10 Device List. This box allows you to create, edit and delete X-10 devices in the Device DataBase. An X-10 device can be a lamp or appliance module, an X-10 remote or any device that can send or receive X-10 commands.

Creating a New X-10 Device

In the Define | X-10 Device List window, type or select as required for each X10 device:

NAME - Enter the device name to refer to (e.g. Living Rm Light). DESCRIPTION - Enter a brief device description (e.g. reading light). LOCATION - Enter the devices location (e.g. Living Room). ENABLED - Check this box to enable the use of the device in a schedule. INITIAL STATE - Enter the default state for the device to assume when downloading the device database. TYPE

LAMP: Dimmer-type modules, X-10 and PCS APPLIANCE: on/off only type modules CONTROLLER: Transmitter type devices LAMP-6381: Levition 6381 SAN020 models (or equivalent modules that respond to the Extended Code

commands).

POWER FAIL CATCHUP - Check this box to force the device into its scheduled state when power fails and is then restored.

REFRESH MODULE - Check this box to periodically issue the X-10 on or off command that corresponds to state currently stored in Automate Domotique’s memory.

After completing the list, press [OK] to store the information into the DataBase, [APPLY] to send the options to Automate Domotique’s memory, [CANCEL] or <ESC> to return without storing.

Note 1: Only one X -10 Device can be defined for a HouseCode/UnitCode address. X -10 Device names must be unique, meaning, you cannot use an X -10 Device name more than once.

Note 2: You must select “Download Device Database” when downloading to AUTOMATE DOMOTIQUE for any of the Refresh, Catch -up or Enable options to take effect, OR, press the [APPLY] button to send options without downloading.

Define Timers

AUTOMATE DOMOTIQUE Timers are countdown timers, meaning if you load one with a time, it will start to count down to zero. Timers can be loaded with a value, started and stopped from within a schedule. Each Timer counts down in 1-second intervals and can be loaded with a maximum time of 18:12:16 (18 hours, 12 minutes, 16 seconds).

Menu Item Description

Name The Timer name that will be used in the schedule (required) Description Brief description of the Timer (optional)

Define TimeLabels

A Time Label is a time with a descriptive name given to it. An example would be assigning the time 7:00 AM to the name “Wakeup”. Your schedule can now refer to “Wakeup” anywhere that 7:00 AM would be used. If you need to change a time that is used often in your schedule, it would be useful to use a Time Label. This way, when you change the time in the Time Label, all references to that label will change.

A more powerful feature of Time Labels is the Time Dependent/offset capability. This capability allows a time to be based upon another time. An example would be assigning a time to be 30 minutes after SunSet and used to turn on exterior lighting. Since SunRise and SunSet are recalculated everyday, this Time Label would always be 30 minutes after SunSet.

Menu Item Description

Name Time Label name that will be used in the schedule Description Brief description of the Time Label (optional) Dependent Select whether this will be dependent upon another time. If YES is selected, a listbox showing all the

defined Time Labels and an Offset time field will be shown. If NO is selected, you must fill in the time that this Time Label will refer to.

Creating a New Time Label

1. In the Time Labels window, select the [New] button. Event Manager opens the Time Label Definition window.

2. Complete the Name and Description fields.

3. Select whether this Time Label will be dependent upon another time by pressing the appropriate YES/NO radio button.

IF YES - dependent on another time

a) Move the highlight bar onto the Time that this Time Label will be dependent upon b) Select whether time will be added or subtracted from the selected Time Label. c) Enter the amount of time that will be added or subtracted. The maximum time that can be added or subtracted

is 4 hours 15 minutes, (4:15). The offset time combined with the Time Label cannot be greater than 23:59 or less than 00:00, meaning the combined time cannot carry over into the next or previous day. This will not cause an error condition, but the IF statement will never be true.

IF NO - not dependent on another time

a) Enter the Hour and Minutes and select the days that will be assigned to this Time Label b) Select whether this Time Label will use the Security feature.

4. Select the [OK] button to accept your choice and store the Time Label into the Device DataBase, or [CANCEL] to quit without storing.

Note: You can’t use the same name for more than one TimeLabel.

Editing an Existing Time Label

1. In the Define Time Label window, move the highlight bar to the Time Label that is to be edited and select the [EDIT] button.

2. Make changes to the Time Label. Select the [OK] button to accept your choice and store the Time Label into the Device DataBase, or [CANCEL] to quit

without storing.

Note: You will be asked to confirm your choice if you change the name of a Time Label that is used in the current schedule.

Deleting a Time Label

1. In the Define Time Label window, move the highlight bar to the Time Label that is to be deleted.

2. Select the [DELETE] button.

Define Flags

A Flag is a variable that has three states: Set, Clear or IDLE. Any Event can set or clear a flag as well as check the state. Flags are useful for communicating between Events or assigning a global variable such as ‘Alarm Armed’.

Menu Item Description

Name The Flag’s name that will be used in the schedule Description Brief description of the Flag (optional)

Initial State This will be the initial state that this flag will be set to in AUTOMATE DOMOTIQUE if the DownLoad

Device DataBase option is selected when downloading the schedule.

Define Variables

A Variable can have a value that ranges from 0 to 255. Variables can be incremented, decremented, loaded with a value and cleared. Variables are useful when you need to base decisions on reoccurring conditions. An example would be to count the number of times the motion sensor at your front door was activated. This would tell you how many people came to your front door.

Menu Item Description

Name The Variable’s name that will be used in the schedule (required) Description Brief description of the Variable (optional) Initial Value This will be the initial value that this Variable will be set to in AUTOMATE DOMOTIQUE if the

DownLoad Device DataBase option is selected when downloading the schedule.

Define IF Macros

An IF Macro is a series of IF conditions, and the logic type associated (AND/OR). The IF conditions are entered into the Macro the same way as Events. Each IF Macro can be used in your Schedule any number of times.

IF Macros are useful for when you use the same set of IF conditions in more than one Event. By defining a set of IF conditions as an IF Macro and replacing those repeated conditions, you can reduce your schedule size and make it more readable.

Example 3 IF Macro named ‘Dark Weekdays’

MACRO BEGIN If After SunSet .MTWTF. or Before SunRise .MTWTF. MACRO END

When an IF Macro is used in an Event, the conditions within the macro must be met for the IF Macro to be true.

EVENT: Good Morning If IF MACRO(Dark Weekdays) Then (X:PorchLight A 2) ON End

In this example, if the IF Macro “Dark Weekdays” is TRUE, (that is, if it after SunSet OR before SunRise on weekdays), THEN turn the Porch Light ON.

Creating a New IF Macro

1. In the Define IF Macro window, select the [New] button. Event Manager opens the IF Macro Definition window.

2. Complete the Name, Description and Logic Type fields.

3. Add IF Conditions by using the ToolBox.

3. Select the [OK] button to accept your choice and store the IF Macro into the Device DataBase, or the [Cancel] button to return without saving.

Note you can’t use the same name for more than one IF Macro.

Editing an Existing IF Macro

1. Highlight the IF Macro that you want to edit and select the [EDIT] button.

2. Change or Add IF Conditions by using the ToolBox.

3. Select the [OK] button to accept your choice and store the IF Macro into the Device DataBase, or the [Cancel] button to return without saving.

Deleting an IF Macro

1. Highlight the IF Macro that you want to delete.

2. Press the [DELETE] button on your keyboard.

Define THEN Macros

A THEN Macro is a series of THEN actions. The THEN actions are entered into the Macro the same way THEN and ELSE actions are in the Event Editor. Each THEN Macro can be used in a Schedule any number of times Then Macros can contain Nested IF/THEN structures and calls to other THEN Macros.

THEN Macros are similar to IF Macros, except they use action statements instead of condition statements. THEN Macros are useful when you use the same set of actions over and over in different Events.

Example 4 THEN Macro named ‘Lights Off’

MACRO BEGIN (X:Study Lamp A 7) OFF (X:Radio A 12) OFF MACRO END

Example 5 Event using a THEN Macro

EVENT: Good Night If 11:00 PM SMTWTFS Then (THEN MACRO:Lights Off) End

In this example, if the time is 11:00 PM on any day, the Study Light and Radio will be turned off.

Creating a New THEN Macro

1. In the Define THEN Macro window, enter a name for the macro in the name field and then press the EDIT button. Event Manager opens the THEN Macro Definition window.

2. Add THEN Actions by using the ToolBox tools.

3. Select the [OK] button to accept your choice and store the THEN Macro into the Device DataBase.

Note you can only have one THEN Macro with a given name.

Editing an Existing THEN Macro

1. In the Define THEN Macro window, move the highlight bar to the THEN Macro that you want to edit and select the [EDIT] button.

Deleting a THEN Macro

1. Highlight the THEN Macro that you want to delete.

2. Press the [DELETE] button.

Define IR/IO-Xpander

To define the IR or IO-Xpander, select the desired device and double click or press the Define button and the appropriate IR or IO define screen will be displayed.

To Enable the IR or IO-Xpander to be used by AUTOMATE DOMOTIQUE, select the Enable checkbox next to the device. When the OK button is pressed, the enable information is sent to AUTOMATE DOMOTIQUE and stored in non-volatile memory. AUTOMATE DOMOTIQUE uses this to determine which devices to read and write to.

Automate Domotique PRO & IO-Xpander Setup

The Define | IO-Xpander | AUTOMATE DOMOTIQUE or Define | IO-Xpander | IO-Xpander command will open the IO Setup Dialog box. When setting up the IO-Xpander, select the address that matches the dip-switch address on the IOXpander.

The dialog box appears allowing you to enter names for each IO connection. Each name corresponds to a connection on the AUTOMATE DOMOTIQUE or IO-Xpander, which has 16 opto-isolated inputs, 8 SPST relays(see appendix for ratings) and 8 8-bit Analog-Digital inputs.

Analog Inputs

The Analog inputs connect internally to an Analog to Digital Converter that converts analog voltages into a digital representation compatible with AUTOMATE DOMOTIQUE. The A/D converters are 8 bit (range: 0-255) with an input voltage range of 0-5 volts DC. This gives a resolution of approximately 20mV/bit (256 x 20mV = 5V). When AUTOMATE DOMOTIQUE reads an A/D input, it will read a value in the range of 0-255, which represents a voltage from 0-5 applied to the input. The table below shows some typical input voltages and shows what AUTOMATE DOMOTIQUE will read.

Input Voltage AUTOMATE

DOMOTIQUE

0 volt 0 1 volt 51

2.5 volt 128 4 volt 205 5 volt 255

Table 1: Analog Input Voltages

Calibrating

Calibration can be done through an external gain/offset circuit or done through software. There are tradeoffs using either method, if resolution is important the external gain/offset circuit is preferred, if resolution/accuracy is not as important (there is no general rule of thumb, each application is different and the tradeoffs must be examined on a case by case basis) the software gain/offset may be acceptable.

Lets suppose you are going to measure temperature using an AE1000 Wall plate temperature sensor. The AE1000 temperature sensor output voltage is linearly proportional to the Fahrenheit temperature (10.0 mV/degree F and has a range from +32 to +212 degrees F).

Assume the temperature being measured is 72? F. The LM34D will output 720mV (72? x 10mV/degree). AUTOMATE DOMOTIQUE will read this 720mV and the digital representation will be 36.

A/D resolution-20mV/bit: 720mV ? (20mV/bit) = 36

So, AUTOMATE DOMOTIQUE reads '36' when the temperature is 72?. It would be nice if the value AUTOMATE DOMOTIQUE read was the same as the temperature. The two ways of doing this could be:

1. Build a 2x amp to convert the 720mV to 1400mV (1400mV / (20mV/bit) = 72)

2. Multiply the value read by AUTOMATE DOMOTIQUE by 2 (36 x 2 = 72), a gain of 2

Option 2 requires the least amount of work, but the resolution of the A/D converter is multiplied by 2 as well, going from 20mV/bit to 40mV/bit. To use the option 2 approach, the gain can be increased by software from within the Define | IO- Xpander dialog boxes. Every A/D input can be calibrated with a software gain and offset. The gain will actually multiply the A/D value and the offset will be added to the result. Using the previous AE1000 example, let’s say a gain of 2 will give a value of 70 at 72 degrees. It is not 72 as would be expected due to many factors, wiring capacitance, AE1000 accuracy, etc. By specifying an offset of 2, this will bring the value in line with the temperature. The formula for scaled A/D is:

scaled_value = (raw_A/D_value x gain) + offset

If you do not need a gain factor, be sure to set the gain to 1 and offset to 0.

NOTE1: You may use Define IO any time you add another IO -Xpander, change connections or rename ports. Note that if you do make a change, such as swapping 2 inputs, you will need to re-download the schedule before the changes take effect.

NOTE2: Connect ANALOG GROUND to GROUND when using the on-board 5VDC Power source to power analog devices.

+ 65 hidden pages