Tyger POS X10 Automation
You can control some X10 devices from Tyger POS Scripting, using the ActiveHome software and an X10 CM15A or CM19A interface. The software and interface list for about $50. X10 allows you to remote control lights turning them on or off, and setting dimmer settings. It can work with some other devices, like remote controls, cameras and motion sensors, but for now, we're only using the on/off/dim features. Suppose you want to alert the cooks when a kitchen ticket is printed. Go to www.x10.com, get the products you need. Install the ActiveHome software Install the interface hardware Set up a controllable outlet in the kitchen. Plug a strobe light, disco ball, air horn, blender full of rocks, or whatever AC powered appliance it takes to get your cooks' attention into the controllable outlet. Place an X10 switch near the printer, configured to turn the alarm on/off. Log into Tyger POS as an administrator Go to Administration / Setup / Printers / Kitchen Printers, and put this into the kitchen print script
SPIORD.X10_Send(sendplc,A1 ON) The A1 part is the address of the device to turn on, yours may be different. A1 is normally automatically assigned to the first device. If you are already using a kitchen ticket script, modify the script to include the line above. Now, whenever you print a kitchen ticket, the alarm will go off, and the cooks can turn the alarm off by clicking the nearby X10 switch. Tyger POS will automatically detect ActiveHome if installed, no special configuration is required. You can also use the ActiveHome software separately, for things like turning lights on/off at night to simulate activity. You need the X10 interface and ActiveHome installed on every computer which will control things.

Kitchen Ticket Alarm

SW31A - ActiveHome Pro Software CM19A Wireless PC Transceiver Tyger POS TM751 Small Wireless Transceiver

Wir eles s

There are many different ways you could set this up, this is just one of them.

A/C r we Po

A/C Power

om rC we Po

A/C Powered Alarm e.g. Strobe Light
Kitchen Printer Configuration Screen
The rest of the kitchen printer setup is 'as usual'.
SPIORD.X10_Send("sendplc","A1 ON")
Controlling lights in Dining Rooms
You can put buttons on the 'Tables' screen to turn lights on and off.
Table Setup Screen for button to Turn On Light
Places to get Stuff http://www.x10.com/homepage.htm http://www.thehomeautomationstore.com

One Time Condition Options
The One Time options provide the following functions: Hour the hour when the one time condition should become active Minute the minute when the one time condition should become active Calendar the date on which the one time condition should become active

Page 141

Time of Day Condition
Use Time of Day condition to run macros daily at a given time. Typical scenarios include: Launching a macro to shut down outside lights at approximately 11:00pm everyday Launch a macro to turn on sprinkler system every Wednesday and Sunday at 6:00am exactly.
Time of Day Condition Options
The Time of Day Trigger fields provide the following functions: Hour the hour when the one time event should be triggered Minute the minute when the one time event should be triggered Valid days the days of the week on which the condition is valid Randomness a random factor, shown in minutes, of when the trigger should happen. Use this field to act as a security measure so that outsiders will not see your triggers acting daily at the exact same time. For example, if you have selected 10 for the Randomness field and 12:15 PM as the trigger hour and minute, the trigger will happen sometime within a window of time between 12:05 PM and 12:25 PM.

Page 142

Sunrise/Sunset Conditions
Use Sunrise and Sunset conditions to run macros upon sunrise and sunset. Typical scenarios include: Turning on outside lights 5 minutes before sunset Turning off outside lights 20 minutes before sunrise
Sunrise & Sunset Condition Options
The Sunrise/Sunset Trigger fields provide the following functions: Offset the offset (in minutes) to subtract/add to the time of sunrise/sunset trigger Valid days the days of the week on which the condition is valid Randomness a random factor, shown in minutes, of when the trigger should happen. Use this field to act as a security measure so that outsiders will not see your triggers acting daily at the exact same time. For example, if you have selected 10 for the Randomness field and sunrise as the trigger mechanism, the trigger will happen sometime within a window of time between 10 minutes before or after sunrise. Sunrise/sunset triggers are calculated for each day by mControl. The calculation for sunrise/sunset is performed using location settings in the configuration area of mControl. The calculated time including offset will be shown underneath the settings buttons.

Camera Media List

This section provides a list of recorded video and snapshots. View media by cursoring to and selecting an item in the media list.

Page 156

IR Control Screen The IR Control screen allows configuration of IR functionality.

IR Control Options

IR Control Configuration
The Automation Options buttons provide the following functions: Back goes back to the Settings Screen Home goes back to the Zone View Screen
This section provides the following configuration options: Commands add, modify and delete IR commands Adapters view available adapter ports. These correspond to the available Global Cach ports available.

Page 157

Adapters Ports View the IR ports available for sending commands to.

Adapter Ports

When you select the Adapters tab, this screen provides a list of all the available adapter ports. These ports are used to send and receive IR commands. Use one of these ports in macro actions to define the destination location of the IR command. mControl currently only display the ports, as configured within the Global Cache or USB UIRT adapters or you can not edit, delete or add ports.

Page 158

IR Commands Shows a list of all IR commands and allows creation of new IR commands.

IR Commands

IR Command Options
The Automation Options buttons provide the following functions: Back goes back to the Settings Screen Home goes back to the Zone View Screen Add IR Command allows creation of a new IR command
This section shows the list of IR commands available for macros.

Page 159

mControl Client for Windows Mobile
To view mControls View Zone screen from a Windows Mobile device, use Internet Explorer on the device to access mControl. For Windows XP and Windows Vista access mControl via http://ServerIPAddress:29990/mobile.aspx For Windows Home Server, access mControl via http://ServerIPAddress/mControl/mobile.aspx
Ensure that you have selected either the Default or Desktop view modes to properly display mControl for Windows Mobile. mControl for Windows Mobile will not be displayed properly if the view mode is One Column. For information on Windows Mobile view modes, please see: http://www.microsoft.com/windowsmobile/gettingstarted/web_wm6.mspx

Page 160

mControl Mobile Zone View The mControl Mobile Zone View, which is considered the main menu of mControl, provides a summary of all the defined zones and all devices within a selected zone.

Add Conditions to the Trigger Once the trigger has been saved, select the trigger. Once within the trigger, press the Add Condition button to add a condition. Select the Condition Type to be Recurring Condition Type select Recurring Hour this is the hour to initiate this condition Minute this is the minute to initiate this condition Valid days this is the days on which this condition will be valid Occurrence this is how many times the condition will become true Interval (mins) this is how many minutes between each interval Interval (secs) this is how many seconds between each interval

Page 180

Add Actions to the Macro Define the set of actions the macro should execute upon receiving the trigger. Use the Add Action button to initiate adding a set of actions for this macro.
The following sample shows a set of actions to take upon activation of the Recurring Timers condition (and trigger). In this case, mControl will take a picture from the Axis 212 camera.

Page 181

Using MCE Events to Trigger Macros
Use MCE Event triggered macros when you want to perform home automation functions at a based on how you are using your Windows XP Media Center Edition 2005 system. For example, you may want to automatically dim lights when you start a DVD movie. Install and configure the MCE Add-in Utility The MCE Add-in Utility listens and forwards MCE Events to mControl. The MCE Add-in Utility uses Windows XP Media Center Edition 2005s Media State Aggregation Service (MSAS) to retrieve events. Once events are received, the MCE Add-in Utility forwards these events to mControl. MCE Add-in Utility must be installed on a MCE machine. mControl does not have to be installed an MCE machine. The MCE Add-in Utility can be on the same machine as mControl or other machines. The MCE Add-in Utility can be installed on multiple machines. Each one of these can be sending messages to mControl.

Media Center Events

Media Center PC with MCE Add-in Utility

mControl PC

MCE Add-in on the Same PC as mControl During mControl installation, the MCE Add-in will be automatically installed if the PC being installed on is a MCE system. In addition, the MCE Add-in will be automatically configured to talk to the mControl on the system. However, if the system is not a MCE system, the MCE Add-in is not installed.

Page 182

MCE Add-in on a Different PC then mControl Use the MceAddins.msi file from your mControl CD or Zip file to install the MCE Add-in Utility on a different PC.
Once installed, you must configure the MCE Add-in Utility to send messages to the mControl machine. 1. Ensure that there is a network between the PC on which the MCE Add-in Utility is installed and the mControl PC. Make a note of the workstation name or IP address of the mControl machine. 2. On the MCE Add-in Utility PC, navigate to the C:\Program Files\Embedded Automation\mControl\bin directory and use a text editor to edit the MSASAddIn.config file. Change the <client> parameters to use the mControl PCs workstation name or IP address instead of localhost. The example below shows localhost changed to mcontrol:
<client> <wellknown type="EmbeddedAutomation.mServerLib.IAuServer, mAuServerLib" url="tcp://mcontrol:29992/mAuServerURI"/> <wellknown type="EmbeddedAutomation.mServerLib.AuServerImpl, mAuServerLib" url="http://mcontrol:29991/mAuServerURI"/> </client>
Please note, it may be required to reset MCEs Media State Aggregation Service upon changing the configuration information. The simplest way to do this is to reboot.

Page 183

Create the Macro to Utilize MCE Events 1. Create the macro which will use one or more MCE Events (and other triggers) to run a set of actions. a. Create the Macro i. Navigate to the Settings page ii. Select the Automation option iii. Select the Add Macro option iv. Enter the information required to create the macro, including: Name the name of the macro Zone the zone to assign the macro within Display in Zone to enable the display of the macro within the zone Image the image to use for this macro v. Save changes
2. Define how the macro will start by adding a MCE Event condition. a. Create a trigger for the macro by pressing the Add Trigger button and then entering a name for the trigger.

Page 184

b. Once the trigger has been saved, select the trigger. Once within the trigger, press the Add Condition button to add a condition c. Select the Condition Type to be MCE Event i. Condition Type select MCE Event ii. Media Type this is the media type to be triggered on iii. Action this is the media action to be triggered on iv. PC Name the workstation from which the type/action event is comes from. By leaving this empty, events from all PCs are considered.

Manual Tab Use the Manual tab to view the current status of your EZRain device.
EZRain View Manual Options
EZRain View Manual Settings
The following EZRain View Manual Options are available: Back return to the View Zone page Apply commit the entered Valve Schedule settings to the EZRain Irrigation Controller The following EZRain View Manual Settings are available: Valve Schedule the time in minutes for each valve to operate Valve the valve to operate Run/Stop manual control of the Valve specified

Page 207

Program Tab Use the Program tab to view the current status of your EZRain device.
EZRain View Program Options EZRain View Program Settings
The following EZRain View Program Options are available: Back return to the View Zone page Apply commit the entered Valve Schedule settings for the selected Program to the EZRain Irrigation Controller Start/Stop Program initiate or stop the selected Program The following EZRain View Program Settings are available: Valve Schedule the time in minutes for each valve to operate for the selected Program

Page 208

Using Thermostats

Using HAI Thermostats

1. To enable HAI thermostat support within mControl, edit mControl configuration settings in the mServer.exe.xml located in the C:\Program Files\Embedded Automation\mControl\server directory. Open the mServer.exe.xml file using Notepad or equivalent text editor, find the section which has configuration settings for the HAI thermostat and make the following highlighted changes to load the HAI thermostat driver into mControl ensure that the load parameter for the adapter is Y and the parameters for COM port and baud rate are correct:
<adapter base="HAIRC" load="Y" assembly="EA.HAIRCTHERMO.dll" driver="EmbeddedAutomation.mServer.Adapters.HaiRcsThermoManager"> <aparam name="DISPLAY-AS" value="HAI RC Thermo" /> <aparam name="Description" value="HAI RC-Serial Thermostat" /> <aparam name="Supports" value="HAIRC" /> <aparam name="AProtocol" value="HAIRC" /> <aparam name="DebugLevel" value="9" /> <aparam name="COMPort" value="COM1" persistent="false" /> <aparam name="BAUD" value="300" persistent="false" /> <aparam name="KeepPortOpen" value="true" /> <aparam name="ResponseTimeout" value="1250" note="value in milliseconds" /> </adapter>

Page 228

Using D-Link Cameras
1. Follow the instructions provided with your D-Link camera to complete the hardware set-up, including establishing the wired or wireless network and connecting power. 2. Use the D-Link softwares IP Installer option to find the available cameras. Click on the Link button to configure for mControl. Please note the IP Address here for future use mControl requires this information.

Page 229

3. Once linked, select the Configuration option of the camera. Once you enter this screen, the D-Link software automatically loads a MPEG4 ActiveX component which allows you to view the camera. This procedure must be followed to load the ActiveX object on each client machine you wish to view the camera.
4. Navigate to the Tools tab, then select the Admin option. For security reasons, you may create an mControl user by assigning a Username/Password. Please note the Username/Password here for future use mControl requires this information.

Page 230

5. Once completed, you will either have to re-power (or reset) your camera. 6. Now you are ready to add the camera to mControl software. f. Navigate to the Settings page g. Select the Camera option h. Select the Add Camera option i. Enter the information required to connect to the camera, including: Name the name of the camera (for example, Back Porch) Zone the zone that the camera should be displayed within Model the camera model IP Address as per step #2 of this process, enter the IP or host.domain.com address Port HTTP port number assigned for the camera Username as per step #4, enter the Username Password as per step #4, enter the Password j. Save Changes and return

Page 231

Page 232

Adding a Custom Camera

If you do not see your camera supported within mControls supported list of Security Cameras, it may still be possible to use the camera. Use the following procedure to add a custom camera: 1. Add the custom camera definition to the mServer.exe.xml file located in the C:\Program Files\Embedded Automation\mControl\server directory. This process is recommended for users familiar with software coding. Please be aware that adding erroneous information to this file may cause failure of mControl to properly start and operate. It is recommended to make a back-up copy of this file before you make changes. Also, this procedure requires knowledge of the custom cameras (ActiveX) objects and parameters. Add a new section within the <modules> section and make the changes recommended in the table below. (It is recommended that you use the Axis 21x base as a starting point.)

Use the Speak recognized commands check box to hear a verbal response to commands.

Page 256

3. To use voice control, simply issue voice commands in either of the following ways: For lights and simple devices: mControl, please turn <device> <command> or mControl, turn <device> <command> mControl, please <command><device> For mControl macros: mControl, run <macro name> turn <command><device> or mControl, turn

Extending Voice Control

Source code for the One Voice to mControl Bridge utility is provided as part the mControl Software Development Kit (SDK). It is possible to extend the grammar file, allowing for greater flexibility in voice commands. The auto-generated grammar file is located in the C:\Program Files\Embedded Automation\mControl\tools directory and is called mControl Grammar.jsg. Do not adjust this manually.

Page 257

Configuring mControl Clients
Using mControl from a remote PC using Internet Explorer
1. Start Internet Explorer and enter the following in the address area: http://<mControl PC>:29990/default.aspx, where <mControl PC> is the name or IP address of the PC on which mControl was installed on.
Adding mControl to a remote Windows XP Media Center Edition PC
Please note, this is an unsupported feature of mControl and once implemented, requires manual editing of your Windows registry the mControl uninstaller does not remove these settings. We recommend making a back-up of your Windows registry before any substantive changes. 1. Copy the mControl.mcl file located in the C:\Program Files\Embedded Automation\mControl directory to the new client machines C:\Documents and Settings\<user of your choice>\Start Menu\Programs\Accessories\Media Center\Media Center Programs directory. 2. Edit the file using Notepad to modify the URL, replacing 'localhost' with the name of the new client machine. For example, if your mControl Automation Service machine is called 'MyServer, you would change the URL setting to "http://MyServer:29990/Default.aspx". 3. Once the file has been modified, you will be able to access it from the More Programs area of the client machine. If you refer to machines name instead of the IP address, please ensure that the name is entered in the Windows Hosts file with the associated IP address, so Windows can resolve the machines name. For more information on Hosts files: http://en.wikipedia.org/wiki/Hosts_file

Page 258

Adding mControl to the Start Menu of a Windows XP Media Center Edition PC
Please note, this is an unsupported feature of mControl and once implemented, requires manual editing of your Windows registry the mControl uninstaller does not remove these settings. We recommend making a back-up of your Windows registry before any substantive changes. To use this function on a remote PC, first perform the step above to Add mControl to a Remote Windows XP Media Center Edition PC. Only a maximum of two 3rd party items can be added to the Start Menu so if two 3rd party items are already installed on the Start Menu, the following steps will have no effect. 1. Using Notepad or equivalent text editor, copy the following into a file called mControl.reg:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Categories\Start Menu\{5688C348-8F19-4676-97F45178A68C37EC}] "AppID"="{aebf238a-a1c5-4354-ba23-e693cb9f219f}" "TimeStamp"=dword:0add6130 "Title"="mControl" "URL"="http://localhost:29990/Default.aspx"
Please ensure that the [HKEY_LOCAL_ C37EC}] line is not split into multiple lines in the mControl.reg file otherwise the key entry will be erroneous.
2. After saving the file, double-click on the file or, within Explorer, perform a right-click and select the Merge option. You will be asked if you want to add the information to the Windows registry. Once you agree, the registry settings will be added and mControl will be available on the Start Menu when Media Center is re-started.

Page 259

Adding mControl to the More Programs Menu of a Windows XP Media Center Edition PC
Please note, this is an unsupported feature of mControl and once implemented, requires manual editing of your Windows registry the mControl uninstaller does not remove these settings. We recommend making a back-up of your Windows registry before any substantive changes. To use this function on a remote PC, first perform the step above to Add mControl to a Remote Windows XP Media Center Edition PC. 1. Using Notepad or equivalent text editor, copy the following into a file called mControl.reg:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Applications\{aebf238a-a1c5-4354-ba23-e693cb9f219f}] "CompanyLogo"="C:\\Program Files\\Embedded Automation\\mControl\\EmbeddedLogo.png" "Description"="mControl for Windows MCE 2005" "Title"="mControl" "CompanyName"="Embedded Automation, Inc." [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Categories\More Programs\{3de6904a-d9c7-4ef9-b77dc1216b39161f}] "Title"="mControl" "ThumbnailUrl"="C:\\Program Files\\Embedded Automation\\mControl\\mHome_Thumbnail.png" "Subtitle"="mControl for Windows MCE 2005" "TimeStamp"=dword:09eea8e3 "AppId"="{aebf238a-a1c5-4354-ba23-e693cb9f219c}" "ImageUrl"="C:\\Program Files\\Embedded Automation\\mControl\\EmbeddedLogo.png" "Url"="http://localhost:29990/Default.aspx"
2. After saving the file, double-click on the file or, within Explorer, perform a right-click and select the Merge option. You will be asked if you want to add the information to the Windows registry. Once you agree, the registry settings will be added and mControl will be available on the Start Menu when Media Center is re-started. 3. Copy the files EmbeddedLogo.png and mHome_Thumbnail.png from the machine that mControl is installed in to the remote Windows Media Center PC. Change the entries CompanyLogo, ThumbnailUrl, and ImageUrl above to the directory where you have placed the copied images to.

<dimvalues> <onvalues>
10, 20, 25, 50, 75 20, 40, 60, 80, 100
<delay-hours> <delay-minutes> <delay-seconds> <cam-vid-duration>
0, 1, 2, 3, 4, 5, 6, 8, 10, 12, 24 00, 01, 02, 03, 04, 05, 10, 15, 20, 30, 45 00, 01, 02, 03, 04, 05, 10, 15, 20, 25, 30, 40, 50 1, 2, 3, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 1, 2, 3, 4, 5, 10, fps, 2 fps, 3 fps, 4 fps, 5 fps, 10 fps, Best Possible 1, 2, 3, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 1, 2, 3, 5, 10, 15, 20, 25, 30
<cam-vid-framerate> <cam-vidframeratedisp> <cam-snap-interval>

<cam-snap-pics>

Page 264
In the following sample, a 33% dim granularity has been added (as shown in red).
<configuration> <time-offset>-60|-45|-30|-20|-15|-10|5|+0|+5|+10|+15|+20|+30|+45|+60</time-offset> <dimvalues>10|20|25|33|50|75</dimvalues> <delay-hours>0|1|2|3|4|5|6|8|10|12|24</delay-hours> <delay-minutes>00|01|02|03|04|05|10|15|20|30|45</delay-minutes> <delay-seconds>00|01|02|03|04|05|10|15|20|25|30|40|50</delayseconds> </configuration>

Page 265

Adding Custom Style Sheets
Using the mControlDataSet.XML file, it is possible to create or modify style sheets or skins for mControl. mControl style sheets consist of the following elements: Element <style-sheet> Description Parent element which encapsulates the style sheet. id defines the name of the Style which shows in the Configuration section of mControl. <filename> <imageDir> <platforms> <javaMCE> <javaIE> <javaUMPC> Child element which defines the associated html style sheet name (.css file) for the skin. Child element which defines the directory name for where the images for the skin are located. Child element which defines the platforms available for the skin. Child element which defines the JavaScript variables required for positioning data-related items within the mControl user interface framework. index defines the array index for the JavaScript variable value defines the value for the JavaScript variable <MCE> <IE> <UMPC> Child element which defines the XML variables required for defining the mControl user interface framework. name defines the name of the XML variable value defines the value of the XML variable

544, 1073, 1132, 1157, 1331
1032, 1033, 1046, 1048, 1089, 1102, 1110, 1111, 1114, 1128, 1135, 1136, 1144, 1180, 1249, 1274, 1287, 1340, 1341
1049, 1054, 1134, 1140, 1141, 1142, 1207, 1237, 1255, 1288, 1303, 1328
Greatly expanded Mobile client which now allows viewing and control of cameras, security systems, thermostats and mControl macros. Also works on other platforms including iPhone/iTouch.

Page 288

v2.1 released February 2008 (continued)
1107, 1109, 1015, 1112, 1152, 1202, 1253, 1254, 1257
Expanded integration with Security Systems, including: Ability to run Elk tasks, perform Elk keypad function or control Elk outputs within mControl macros Ability to view and control thermostats (e.g, Aprilaire, HAI, etc.) interfaced to Elk-M1 systems Ability to use zone status changes to trigger mControl macros (e.g., Zone 2 equals violated)
183, 957, 1133, 1149, 1170, 1250, 1262, 1281, 1283
Revamped mControl Editor which allows for drag-and-drop management of mControl Zones/Devices and Macros. INSTEON protocol enhancements, including: Initial release of the mControl INSTEON Utility Support for new INSTEON thermostat (Venstar) Preliminary support for EZIOxx devices Proper button display for INSTEON multi-level devices (e.g., dimmers) Message throttling to mitigate INSTEON adapter send/receive collisions Improved communication support for devices requiring multiple hops in INSTEON mesh network Improved handling of clean-up messaging after a group command
837, 1099, 1100, 1212, 1275, 1293, 1294

1158, 1159, 1250

Revamped mControl Service Controller that allows configuration of adapters, including support for non-native mControl drivers (i.e., from DDK developers), in addition to basic service stop, start and restart functionality. Revamped mControl v2 Driver Development Kit (DDK) and related infrastructure changes to support custom protocols, adapters, modules, commands and properties. Using the DDK, our partners Tekniska Byran have been able to implement a driver for the KNX protocol.
988, 1216, 1270, 1271, 1298, 1299, 1300, 1301, 1302
98, 147, 148, 539, 542, 586, 917, 967, 986, 1030, 1034, 1036, 1067, 1068, 1069, 1087, 1088, 1097, 1098, 1108, 1120, 1121, 1122, 1123, 1124, 1125, 1126, 1127, 1129, 1131, 1137, 1139, 1145, 1147, 1150, 1153, 1154, 1156, 1165, 1167, 1168, 1169, 1171, 1174, 1175, 1177, 1178, 1183, 1195, 1197, 1198, 1199, 1203, 1206, 1209, 1210, 1213, 1217, 1228, 1230, 1231, 1234, 1235, 1236, 1239, 1241, 1242, 1243, 1245, 1246, 1247, 1251, 1252, 1256, 1259, 1260, 1261, 1273, 1276, 1277, 1278, 1279, 1282, 1284, 1289, 1291, 1296, 1306, 1311, 1312, 1316, 1322, 1334, 1335, 1336, 1338, 1339

87, 364, 933, 966, 971, 972, 968, 969, 979, 992, 993, 994, 995, 1020, 1021
843, 849, 895, 998, 1002, 1044, 1045
959, 984, 987, 1017, 1055, 1058, 1066
201, 227, 375, 385, 413, 440, 484, 784, 948, 964, 985, 1000, 1012, 1013, 1014, 1037, 1039, 1042, 1064, 1070, 1079, 1081
10, 47, 63, 173, 389, 502, 657, 886, 929, 943, 961
975, 996, 1010 949, 963, 965, 977, 981, 999, 1005, 1009, 1016, 1018, 1019, 1025, 1061
960 38, 79, 192, 217, 263, 272, 289, 305, 344, 381, 403, 466, 469, 518, 522, 525, 568, 570, 578, 580, 588, 603, 623, 632, 705, 748, 756, 762, 763, 767, 777, 779, 901, 918, 920, 930, 950, 953, 954, 970, 974, 990, 991, 997, 1007, 1008, 1011, 1029, 1038, 1040, 1043, 1047, 1052, 1053, 1057, 1059, 1063, 1076, 1077

Page 290

v1.70 released January 2007
220, 224, 244, 248, 325, 338, 511, 532, 537, 575, 755, 761, 773, 791, 839, 856, 857, 858, 859, 860, 868, 871, 874, 881, 883, 885, 892, 940, 942
743, 869, 870, 876, 893, 894, 897, 898, 899
253, 771, 780, 785, 865, 891, 910, 923

846, 889

119, 124, 906
191, 383, 392, 778, 851, 907
125, 534, 818, 828, 830, 831, 832, 911, 912, 913, 931, 932, 939
213, 223, 758, 764, 807, 808, 815, 827, 838, 842, 847, 848, 850, 864, 872, 873, 890, 902, 905, 921, 922, 925
Description Enhanced security camera support, including: Support for Panasonic cameras (BB-HCM331) Confirmed support for D-Link DCS-3220 and DCS-6620 series of cameras Enhanced Camera View page provides capability to take a snapshot, record a video and, if camera allows, perform pan-tilt-zoom functionality New macro trigger: On Camera Motion (supported on Axis cameras) New macro action: Record video (user-definable frame rate and duration) New macro action: Take snapshot (user-definable count) New Camera Media page allows viewing of snapshots and videos, sorted by date/time, media type or camera View camera snapshots and videos within Media Center Enhanced security system support, including: Support for DSC PowerSeries Security Systems (via PC5401 module) Support for Honeywell Ademco Security Systems Touch screen friendly numeric entry buttons for arming/disarming Enhanced device support, including: Support for HAI RC Thermostats Support for USB UIRT IR Receiver/Blaster Z-Wave protocol enhancements, including: Z-Wave Adapter Utility has been improved to display Z-Wave device information Improved robustness to manage lost connections X10 protocol enhancements, including: Universal Module (UM506) support Enhancements to CM17 (Firecracker) communications User Interface enhancements, including: Support for SnapStreams BeyondMedia media center New Windows Mobile interface provides view and control of mControl devices Button like behavior on devices Enhanced voice recognition capabilities (using One Voice Technologies Media Center Communicator) mControl macros can now be triggered by voice command Enhanced macro functionality Ability to specify images for each macro Ability to order macros within a zone Set durations for macro actions to allow for deterministic macro timing Many general enhancements to mControl including: User interface Installation process User Manual

Page 294

v1.31 released December 2005
Issue # 317,341,350, 354, 356 Description Improved robustness for installation, logging and copy protection, including: Installation in non-default directory or drive Size and number of log files can be set Proper version is shown in More Programs area of MCE Automatic upgrading of v1.1x database adds necessary fields Improved robustness for editing of mControl devices, zones and related data. Improved robustness for Macro handling, including: Will not allow selection of undefined addresses as triggers Improved robustness related to INSTEON and X10 support, including: Elimination of spurious exception errors Improved automatic handling of plugging and unplugging of CM15A and 2414U Behavior for INSTEON devices changed to reflect expected behavior instead of X10 behavior Multiple X10 ON commands handling Devices, if linked in mControl/2414U, will update status if ControLinc, SwitchLinc or KeypadLinc also have them linked and change status Incoming and outgoing X10 messages on 2414U INSTEON adapter Improved robustness for automatic linking and unlinking of devices in PowerLincs database
158,336,348 323,355 205,206,225, 299,302,313, 329,340,343, 345,347,351, 360,361,366, 367,368,372, 373,377,380
v1.30 released November 2005
Issue # ,221,228, 235,236,268, 269,274,275, 280,297,307, 311,322 Description Confirmed support of Windows XP Media Center Edition 2005 Rollup 2 Enhanced Macro support, including: Support for sunrise and sunset macro triggers. Configuration allows for entry of longitude and latitude, thereby allowing mControl to calculate the sunrise and sunset for the day. Offsets can be added to control desired trigger points relative to sunrise and sunset. Greater than 6 hours for delays Enhanced error checking for incorrect macro triggers and actions Added support for IR functionality, including: Support for the Global Cach Network IR Adapter, including learning functionality (using GC-IRL module) Support for raw Component Control Files (CCF), thereby allowing manual entry, using cut and paste, of known IR commands Enhanced configurability, including: Selectable styles (or skins). Default style is now non-animated Blue, to ensure optimum performance for MCE environments. Expanded XML configuration files and related documentation. Please refer to the Configuring mControl section of the mControl v1 (Home Edition) User Manual Performance improvements, including: mControl no longer throws an exception if stopped or restarted Memory management is no longer affected by presence or absence of internet connection Performance of the mControl client, when used in conjunction with Shared View Port (SVP) is greatly improved Improved entry field validation throughout
100,169,259, 277,278,296, 312,321

C:\Program Files\Embedded Automation\mControl\logs. Log files for the MCE Add-in are named
MSASAddIn<xxx>.log, where <xxx> represents a numeric value. As with mControl log files, these files are enumerated similarly.

Diagnostics

Use http://localhost:29990/diagnostic.aspx to generate a report of information related to your mControl installation.

Contact Us

Send us an email to: support@embeddedautomation.com or go to the Support page at www.embeddedautomation.com. Participate in the forum: www.embeddedautomation.com/forum

Page 305