Difference between revisions of "CM11"
(getting started with the CM11 in a nutshell) |
(little update) |
||
Line 2: | Line 2: | ||
The CM11 (A/F/G/U/...) is a device that uses [http://hypermetrics.com/rubyhacker/x10proto.html X10] protocol to control lights and other appliances around the house by injecting data into powerline. | The CM11 (A/F/G/U/...) is a device that uses [http://hypermetrics.com/rubyhacker/x10proto.html X10] protocol to control lights and other appliances around the house by injecting data into powerline. | ||
− | Each X10 device has an address formed as ''housecode''[A..P]+''unitcode''[1..16]. As powerlines are usually shared between near houses/apartments it's a good idea to choose other housecode than your neighbor, or | + | Each X10 device has an address formed as ''housecode''[A..P]+''unitcode''[1..16]. As powerlines are usually shared between near houses/apartments it's a good idea to choose an other housecode than your neighbor, or have a suitable filter installed by a qualified electrician. |
+ | |||
+ | Note that some electric equipment can generate a lot of static on the powerlines. This can drasticly reduce the performance of the X10 installation. The solution is to install filters, effectively isolating these devices from the rest of the power grid. These type of filters are usually installed between the power socket and plug of the appliance. Some X10 switches and dimmers also have these filters built in already (depending on the make and model of course) to ensure more reliable operation. | ||
== Setup == | == Setup == | ||
# [http://192.168.80.1/ web admin] -> Show devices tree -> ''the device to which the CM11 is connected'' (For instance "The core/hybrid"). | # [http://192.168.80.1/ web admin] -> Show devices tree -> ''the device to which the CM11 is connected'' (For instance "The core/hybrid"). | ||
# Create Child Device -> Pick device template -> CM11A (The wizzard pops up to say she didn't detect lighting?, then shows "dev81" and an OK button in 1.1-RC1, I just ignored this). | # Create Child Device -> Pick device template -> CM11A (The wizzard pops up to say she didn't detect lighting?, then shows "dev81" and an OK button in 1.1-RC1, I just ignored this). | ||
− | # Device data -> COM Port on PC -> ''the port to which this device is connected'' -> save. (ttyS0="com1", ttyS1="com2", and so on, "pci0000:00/0000:00:13.1+2" in my case, which is a USB port [http://forum.linuxmce.org/index.php?topic=1850.msg8883#msg8883]). | + | # Device data -> COM Port on PC -> ''the port to which this device is connected'' -> '''save'''. (ttyS0="com1", ttyS1="com2", and so on, "pci0000:00/0000:00:13.1+2" in my case, which is a USB port [http://forum.linuxmce.org/index.php?topic=1850.msg8883#msg8883]). |
== Adding lights == | == Adding lights == | ||
# [http://192.168.80.1/ web admin] -> Show devices tree -> CM11A | # [http://192.168.80.1/ web admin] -> Show devices tree -> CM11A | ||
− | # Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)) | + | # Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)") |
# Device data -> Port/Channel Number -> ''HousecodeUnitcode'' -> '''save''' (codes range from "A1" to "P16", no seperator) | # Device data -> Port/Channel Number -> ''HousecodeUnitcode'' -> '''save''' (codes range from "A1" to "P16", no seperator) | ||
Line 18: | Line 20: | ||
== See also == | == See also == | ||
* The older [[CM11A]] page, which appears to be more aimed at development. | * The older [[CM11A]] page, which appears to be more aimed at development. | ||
+ | * The pluto [http://plutohome.com/wiki/index.php/CM11A CMA11A] page. | ||
+ | * The pluto [http://plutohome.com/wiki/index.php/Gc100 gc100] page for setup on the serial port of the gc100. | ||
+ | * An interesting comment about pluto with the CM11 [http://smart-home-blog.com/archives/726#comments] containing a workaround dealing with sensors and remotes. | ||
[[Category: Automation]] | [[Category: Automation]] |
Revision as of 01:26, 4 August 2007
Contents
Description
The CM11 (A/F/G/U/...) is a device that uses X10 protocol to control lights and other appliances around the house by injecting data into powerline.
Each X10 device has an address formed as housecode[A..P]+unitcode[1..16]. As powerlines are usually shared between near houses/apartments it's a good idea to choose an other housecode than your neighbor, or have a suitable filter installed by a qualified electrician.
Note that some electric equipment can generate a lot of static on the powerlines. This can drasticly reduce the performance of the X10 installation. The solution is to install filters, effectively isolating these devices from the rest of the power grid. These type of filters are usually installed between the power socket and plug of the appliance. Some X10 switches and dimmers also have these filters built in already (depending on the make and model of course) to ensure more reliable operation.
Setup
- web admin -> Show devices tree -> the device to which the CM11 is connected (For instance "The core/hybrid").
- Create Child Device -> Pick device template -> CM11A (The wizzard pops up to say she didn't detect lighting?, then shows "dev81" and an OK button in 1.1-RC1, I just ignored this).
- Device data -> COM Port on PC -> the port to which this device is connected -> save. (ttyS0="com1", ttyS1="com2", and so on, "pci0000:00/0000:00:13.1+2" in my case, which is a USB port [1]).
Adding lights
- web admin -> Show devices tree -> CM11A
- Create Child Device -> Pick device template -> take your pick (I added "Light Switch (on/off)")
- Device data -> Port/Channel Number -> HousecodeUnitcode -> save (codes range from "A1" to "P16", no seperator)
When you are done adding lights, you can continue with the setup wizzard to assign them to the proper rooms and give them names (she refers to ZWave devices and seems unable to actually controll the X10 devices in 1.1-RC1) Also you might have to "reload the router" before they actually work (orbiter screens will be also be regenerated), but they do work.