CM15A

Version	Status	Date Updated	Updated By
710	Unknown	N/A	N/A
810	Unknown	N/A	N/A
1004	Unknown	N/A	N/A
1204	Unknown	N/A	N/A
1404	Unknown	N/A	N/A
Usage Information

Reference Info

Just for reference:

CM11A is pc interface to powerline only

CM15A is pc interface to powerline PLUS wireless signals (RF)

CM19A is wireless signals (RF) only (you'll need a 751 or other to convert to powerline signals)

Forum discussion

Update 2-17-10

In the latest build the template for the CM15A is downloaded and installed for use. There is still a problem though, in the packages dropdown box obexftp is listed. This is incorrect, it should be Pluto CM15A. Make sure that you do not connect your cm15a during the installation process since you will need to correct the template first before the cm15a is detected. Simply go to the Web administration page, click on Advanced hover over Configuration then click Device templates. In the "Do you know the template id..." type 2098. This should select the cm15a template. If it does then click pick device template, if it does not in the device category dropdown select Specialized Interfaces, click apply filter, and select cm15a from the device template drop down. Select pick device template. Find the Packages drop down box and select Pluto CM15A. Save the template and do a reload router. Once the router finishes reloading you can plug in your cm15a and it should be found automagically. Follow the prompts and you should end up with a functional CM15A

The instructions listed below should be no longer necessary

If you own X10 devices, then like me you were probably excited about the prospect of using the cm15a without going through the procedures below. Unfortunately I have not seen a new template show up on a new install of LMCE. A new template did appear on an existing installation I was using but I could not get that to work. I am not sure if it was because of the test cm15a interface or the fact that template number 2098 had been used by another device prior to the addition of the cm15a template. In any case all is not lost. You can still use the new code, which is available on the repository. I got mine to work by doing as root, apt-get update, apt-get install pluto-cm15a. This will install the interface code on your installation. Then create the template as shown below. Where ever you see CM15A_TEST below use CM15A instead. Set it up to automagically detect the interface and reload router. LMCE should ask you if you want to use it. Add your devices and away you go.

Setting up LinuxMCE for the CM15A Active Home Pro USB X10 Interface

The introduction of the CM15A to LinuxMCE was a joint venture between Nosilla_99 and Mythtified . Mythtified provided access to the hardware necessary to test the new code. Nosilla wrote and tested the code. If it had not been for Nosilla stepping up and making the time to write the code, then the CM15A would not be a reality within LinuxMCE.

Start by creating the template. Go to Advanced--->Configuration--->Device Templates. Once the window appears it is time to start by selecting the framework. At the top of the page, make sure that the manufacturer selected is Pluto. Below that will be the Device Category drop down. Click the drop down and select Specialized<Interfaces. Click Apply Filter and then click Add Device Template.

A window will appear to allow the initial setup of the template. Click the selection in the center: I'm going to write c++ code. Enter the name of the template in the text box and click add. The template name must match the executable name exactly, CM15A_TEST.

The template creation window will close leaving the device template window open. Click apply filter again and select CM15A_TEST from the drop down box. Click pick device template.

A new Edit Device Template window will appear. Implements DCE should be checked. If it is not then click the check box. In the Device Category drop down box, Interfaces – Specialized #97 should be the selection shown. If it is not then click the drop down box and select it.

Next click Add a new controlled via category device. A window will open. Click the drop down box and select Computers. Click save.

Move down a few lines and select USB from the Comm Method drop down box. Under Device Data select Only One Per PC and click Add. In the Comments text box type only one allowed. In the Default Value type the number 1. Do not select any of the check boxes. If Plug and Play is desired perform then perform the task in the next paragraph then click Save and then click Close.

At this point either a quick reload router can be done and then set up the device manually or a little bit more can be done to the device template to make the CM15A plug and play. Confirm that the Vendor Model ID is 0bc70001 by opening a terminal window and at the command prompt type lsusb. Look for the CM15A entry and will have X10 in the description. Once the ID has been confirmed, enter the ID number in the Vendor Model ID text box. In the PNP protocol drop down box select HAL USB. Click save then then click close. Do a quick reload router and wait for the device to be created. This could take several minutes.

To set up the interface manually, click on the Interfaces link from the Wizard links on the left of the page. Click Add Device. The Pick Device Template window will open. In the Device Category drop down box select Specialized < Interfaces, then click Apply Filter. In the Device Template drop down click the CM15A_TEST template that was created earlier, then click Pick Device Template. The Pick Device Template window will close showing the Interfaces window with the newly created CM15A interface. Make sure that CORE is listed under the Controlled by heading. If it is not, click the link and choose CORE. If your installation is not on the core then you will have to figure this part out for yourself. Once this is complete then do a Quick Reload Router and wait for the interface to be installed.

Once the interface has completed installation and if the installation was successful, then a log will be created in /var/log/pluto. The log file name will start with the device id number followed by the name of the interface. Example: 37_CM15A_TEST.log.

Enjoy.