Comments on: Getting your X10 CM19A Module Working in Linux http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/ Free tools and information maintained by an online entrepreneur. Sat, 14 Jan 2012 04:40:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Michael LeMay http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-77647 Michael LeMay Sat, 14 Jan 2012 04:40:23 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-77647 The driver does not currently support retrieving the status of a device. The driver does not currently support retrieving the status of a device.

]]> By: Brian http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-74553 Brian Wed, 07 Dec 2011 16:38:09 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-74553 Is it possible to get the status of the device using this driver?  Is it possible to get the status of the device using this driver? 

]]> By: Conrad http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-53926 Conrad Fri, 17 Dec 2010 06:08:06 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-53926 Hi just wondering what would be the command to send an ALL LIGHTS ON or OFF?   cheers Hi just wondering what would be the command to send an ALL LIGHTS ON or OFF?
 
cheers

]]> By: Michael LeMay http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-51382 Michael LeMay Wed, 27 Oct 2010 15:25:35 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-51382 For some reason the blog software added a space at the end of the link I posted.  Maybe it'll work if I put a period after it: <a href="http://m.lemays.org/projects/x10-cm19a-linux-driver" rel="nofollow">http://m.lemays.org/projects/x10-cm19a-linux-driver</a>. For some reason the blog software added a space at the end of the link I posted.  Maybe it’ll work if I put a period after it: http://m.lemays.org/projects/x10-cm19a-linux-driver.

]]> By: Doug http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-51381 Doug Wed, 27 Oct 2010 14:42:12 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-51381 I had luck using the Python driver at http://www.cuddon.net/2009/08/python-driver-v01-for-cm19a-x10.html This is a userspace driver. It does not use the kernel driver and the kernel driver should not be installed for it to work.   I was unable to get the above Python link from Michael to work. It says "page not found. "   Does this driver work similiar to the cuddon.net driver? I had luck using the Python driver at http://www.cuddon.net/2009/08/python-driver-v01-for-cm19a-x10.html
This is a userspace driver. It does not use the kernel driver and the kernel driver should not be installed for it to work.
 
I was unable to get the above Python link from Michael to work. It says “page not found. “   Does this driver work similiar to the cuddon.net driver?

]]> By: Michael LeMay http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-51379 Michael LeMay Wed, 27 Oct 2010 14:15:02 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-51379 I re-uploaded the Linux C driver for those of you that still need it.  I wish you would also post the challenges you've experienced with the Python one, though.  Thanks! I re-uploaded the Linux C driver for those of you that still need it.  I wish you would also post the challenges you’ve experienced with the Python one, though.  Thanks!

]]> By: Eric http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-51027 Eric Mon, 18 Oct 2010 22:36:11 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-51027 Does anyone have a mirror of the previous version of the driver?  I had it working perfectly but had to do a new install and didn't keep the .tar archive.  I can't get the Python version to work no matter what, and I'd rather just use what works than fiddle with a new implementation. Does anyone have a mirror of the previous version of the driver?  I had it working perfectly but had to do a new install and didn’t keep the .tar archive.  I can’t get the Python version to work no matter what, and I’d rather just use what works than fiddle with a new implementation.

]]> By: Michael LeMay http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-50786 Michael LeMay Sun, 10 Oct 2010 19:03:28 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-50786 I'm glad to see that you're all getting some use out of the driver!  To follow up on Doug's comment, I did finally get around to porting the driver to Python, and the new version is posted here: http://m.lemays.org/projects/x10-cm19a-linux-driver  I added a bit of a tutorial on using the new version as well.  Enjoy! I’m glad to see that you’re all getting some use out of the driver!  To follow up on Doug’s comment, I did finally get around to porting the driver to Python, and the new version is posted here: http://m.lemays.org/projects/x10-cm19a-linux-driver  I added a bit of a tutorial on using the new version as well.  Enjoy!

]]> By: Doug http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-50221 Doug Sat, 18 Sep 2010 04:21:39 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-50221 I was in email contact with Mike Lemay andhe really has no answer for the error "x10-cm19a: devf_open: Couldn’t submit interrupt inpu" That many are getting. I get it sporadically but often enough to disrupt operations. My quick fix is to call a script twice a day that removes and reinstalls the driver. This always fixes the problem. A real squirely way to do it but for now it works. Mike said he is moving to a Python userspace solution. I see there is already one out there that others have tried. When I get time I will try that solution. In the meantime if anyone has an answer to this kernel driver problem it would be great. I was in email contact with Mike Lemay andhe really has no answer for the error “x10-cm19a: devf_open: Couldn’t submit interrupt inpu” That many are getting. I get it sporadically but often enough to disrupt operations. My quick fix is to call a script twice a day that removes and reinstalls the driver. This always fixes the problem. A real squirely way to do it but for now it works. Mike said he is moving to a Python userspace solution. I see there is already one out there that others have tried. When I get time I will try that solution.
In the meantime if anyone has an answer to this kernel driver problem it would be great.

]]> By: Doug http://pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/comment-page-1/#comment-50021 Doug Fri, 10 Sep 2010 02:14:43 +0000 http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/#comment-50021 Here is my log after connecting - Sep  9 22:03:36 slate kernel: usb 5-2: new low speed USB device using uhci_hcd and address 6 Sep  9 22:03:36 slate kernel: usb 5-2: new device found, idVendor=0bc7, idProduct=0002 Sep  9 22:03:36 slate kernel: usb 5-2: new device strings: Mfr=1, Product=2, SerialNumber=0 Sep  9 22:03:36 slate kernel: usb 5-2: Product: USB Transceiver Sep  9 22:03:36 slate kernel: usb 5-2: Manufacturer: X10 Wireless Technology Inc Sep  9 22:03:36 slate kernel: usb 5-2: configuration #1 chosen from 1 choice Sep  9 22:03:36 slate kernel: x10-cm19a: Probing x10-cm19a... Sep  9 22:03:36 slate kernel: x10-cm19a: Found input endpoint: 81, and output endpoint: 2 Sep  9 22:03:36 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0x35957020) Sep  9 22:03:37 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0x35957020) Sep  9 22:03:37 slate kernel: x10-cm19a: X10 CM19A USB RF Transceiver connected. Sep  9 22:03:37 slate kernel: x10-cm19a: X10 CM19A USB RF Transceiver initialized to listen for remote co ntrols. Sep  9 22:03:37 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0x35957020) and after sending a command (when it is working) - Sep  9 22:05:46 slate kernel: x10-cm19a: devf_write called with buffer length 4 Sep  9 22:05:46 slate kernel: x10-cm19a: got off command Sep  9 22:05:46 slate kernel: x10-cm19a: house code a Sep  9 22:05:46 slate kernel: x10-cm19a: unit = 7 Sep  9 22:05:46 slate kernel: x10-cm19a: Created HA command: off a 7 Sep  9 22:05:46 slate kernel: x10-cm19a: Transmitting 5 byte command: Sep  9 22:05:46 slate kernel: x10-cm19a: buf[0] = 20 Sep  9 22:05:46 slate kernel: x10-cm19a: buf[1] = 60 Sep  9 22:05:46 slate kernel: x10-cm19a: buf[2] = 9F Sep  9 22:05:46 slate kernel: x10-cm19a: buf[3] = 68 Sep  9 22:05:46 slate kernel: x10-cm19a: buf[4] = 97 Sep  9 22:05:46 slate kernel: x10-cm19a: wrote command Sep  9 22:05:46 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0x35957020) Sep  9 22:05:47 slate kernel: x10-cm19a: read back interrupt data Sep  9 22:05:47 slate kernel: x10-cm19a: devf_write: back from x10_transmit_cmd and when it is not this - Sep  9 20:29:01 slate kernel: x10-cm19a: devf_open: Couldn't submit interrupt input URB: -22 Here is my log after connecting -
Sep  9 22:03:36 slate kernel: usb 5-2: new low speed USB device using uhci_hcd and address 6
Sep  9 22:03:36 slate kernel: usb 5-2: new device found, idVendor=0bc7, idProduct=0002
Sep  9 22:03:36 slate kernel: usb 5-2: new device strings: Mfr=1, Product=2, SerialNumber=0
Sep  9 22:03:36 slate kernel: usb 5-2: Product: USB Transceiver
Sep  9 22:03:36 slate kernel: usb 5-2: Manufacturer: X10 Wireless Technology Inc
Sep  9 22:03:36 slate kernel: usb 5-2: configuration #1 chosen from 1 choice
Sep  9 22:03:36 slate kernel: x10-cm19a: Probing x10-cm19a…
Sep  9 22:03:36 slate kernel: x10-cm19a: Found input endpoint: 81, and output endpoint: 2
Sep  9 22:03:36 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0×35957020)
Sep  9 22:03:37 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0×35957020)
Sep  9 22:03:37 slate kernel: x10-cm19a: X10 CM19A USB RF Transceiver connected.
Sep  9 22:03:37 slate kernel: x10-cm19a: X10 CM19A USB RF Transceiver initialized to listen for remote co
ntrols.
Sep  9 22:03:37 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0×35957020)

and after sending a command (when it is working) -
Sep  9 22:05:46 slate kernel: x10-cm19a: devf_write called with buffer length 4
Sep  9 22:05:46 slate kernel: x10-cm19a: got off command
Sep  9 22:05:46 slate kernel: x10-cm19a: house code a
Sep  9 22:05:46 slate kernel: x10-cm19a: unit = 7
Sep  9 22:05:46 slate kernel: x10-cm19a: Created HA command: off a 7
Sep  9 22:05:46 slate kernel: x10-cm19a: Transmitting 5 byte command:
Sep  9 22:05:46 slate kernel: x10-cm19a: buf[0] = 20
Sep  9 22:05:46 slate kernel: x10-cm19a: buf[1] = 60
Sep  9 22:05:46 slate kernel: x10-cm19a: buf[2] = 9F
Sep  9 22:05:46 slate kernel: x10-cm19a: buf[3] = 68
Sep  9 22:05:46 slate kernel: x10-cm19a: buf[4] = 97
Sep  9 22:05:46 slate kernel: x10-cm19a: wrote command
Sep  9 22:05:46 slate kernel: x10-cm19a: freeing buffer in callback (0xf5957020/0×35957020)
Sep  9 22:05:47 slate kernel: x10-cm19a: read back interrupt data
Sep  9 22:05:47 slate kernel: x10-cm19a: devf_write: back from x10_transmit_cmd
and when it is not this -
Sep  9 20:29:01 slate kernel: x10-cm19a: devf_open: Couldn’t submit interrupt input URB: -22

]]>