X10 CM19A on Buster via mochad

Getting your soundcard to work, using Debian on non-i386 hardware, etc

X10 CM19A on Buster via mochad

Postby Motozoic » 2019-12-28 21:10

After many years of using numerous versions of Ubuntu Server, it dawned on me that perhaps using the Debian base itself might be a more optimized experience. So far, it certainly has been. I'm running Debian Buster on an old mini-ITX board with a dual core Celeron BGA, 4GB of RAM, and a 128GB SSD. Super speedy, super reliable so far. I'm having issues getting a USB device I've used on numerous other systems to work properly: an X10 RF transmitter, CM19A. I'd appreciate any help I can get with this as I'm stuck. Thanks for looking.

Via the command:
lsusb -v -d 0bc7:

I get:
Code: Select all
Bus 002 Device 003: ID 0bc7:0002 X10 Wireless Technology, Inc. Firecracker Interface (ACPI-compliant)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0bc7 X10 Wireless Technology, Inc.
  idProduct          0x0002 Firecracker Interface (ACPI-compliant)
  bcdDevice            1.00
  iManufacturer           1 X10 Wireless Technology Inc
  iProduct                2 USB Transceiver
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)


I just have no idea. I've attempted all manner of things to get this thing online. The software interface I'm attempting to communicate with the device is mochad, which has been successfully installed without issue (v0.1.17). Via
systemctl status mochad
I get:
● mochad.service - Start mochad service
Loaded: loaded (/lib/systemd/system/mochad.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2019-12-15 08:54:26 MST; 1 weeks 6 days ago
Main PID: 322 (mochad)
Tasks: 2 (limit: 3956)
Memory: 972.0K
CGroup: /system.slice/mochad.service
└─322 /usr/local/bin/mochad


When attempting to execute mochad I get:
mochad -d
mochad.c:627:Could not find/open CM15A/CM19A -5

Message from syslogd@SinghUtil at Dec 28 14:55:47 ...
mochad[24048]: usb_claim_interface failed -6

Broadcast message from systemd-journald@SinghUtil (Sat 2019-12-28 14:55:47 MST):

mochad[24048]: usb_claim_interface failed -6

root@SinghUtil:/home/manu/packages#
Message from syslogd@SinghUtil at Dec 28 14:55:47 ...
mochad[24048]: Kernel driver detach failed -5

Broadcast message from systemd-journald@SinghUtil (Sat 2019-12-28 14:55:47 MST):

mochad[24048]: Kernel driver detach failed -5


Message from syslogd@SinghUtil at Dec 28 14:55:47 ...
mochad[24048]: Could not find/open CM15A/CM19A -5

Broadcast message from systemd-journald@SinghUtil (Sat 2019-12-28 14:55:47 MST):

mochad[24048]: Could not find/open CM15A/CM19A -5
User avatar
Motozoic
 
Posts: 1
Joined: 2019-12-28 20:38
Location: Tucson, AZ

Re: X10 CM19A on Buster via mochad

Postby CwF » 2019-12-29 17:01

I'm listening. I use the old serial port version in a xp vm. I guess I understand this may never come to linux. I don't understand why X10 has died off? How is a wifi outlet better when you have copper already connected. Modern automation is moving in the wrong direction. I did a dozen lights, the hvac, some garage equipment 20 years ago with an IBM package, it all still works. When the curly mercury lights came out, they blew it up putting out so much noise, and loaded up like a capacitor while off. LED's work fine. I haven't tried the firecracker with heyu(?) yet, and didn't know about mochad.

Good luck. Post back success or failure!
CwF
 
Posts: 545
Joined: 2018-06-20 15:16


Return to Hardware

Who is online

Users browsing this forum: No registered users and 2 guests

fashionable