Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mike]

Can anyone help me decode why mochad is disconnecting?  Here are my 3 clues so far:

1) nc localhost 1099   -  opens watching ALL x10 commands seen by  the CM15...  I can walk around the house triggering motion sensors and they all show up as seen.  On and off.  Ditto if I use a remote control and send codes.  So the CM15 IS interfacing...

10/28 15:04:03 Rx PL HouseUnit: B10
10/28 15:04:03 Rx PL House: B Func: Off
10/28 15:04:49 Rx PL House: B Func: On

BUT ONLY after it starts working by new boot sometimes, or if I manually start the service (I think) by ./mochad

2) ./mochad  -  but mochad reports no CM15 found if run this way...

Message from syslogd@raspberrypi at Oct 28 15:01:47 ...
 mochad[3072]: libusb_open_device_with_vid_pid failed

Broadcast message from systemd-journald@raspberrypi (Sun 2018-10-28 15:01:47 EDT):

mochad[3072]: libusb_open_device_with_vid_pid failed


Message from syslogd@raspberrypi at Oct 28 15:01:47 ...
 mochad[3072]: Could not find/open CM15A/CM19A -5

Broadcast message from systemd-journald@raspberrypi (Sun 2018-10-28 15:01:47 EDT):

mochad[3072]: Could not find/open CM15A/CM19A -5

3)  sudo systemctl status mochad  - reports it IS seen!??

● mochad.service - Start mochad service
   Loaded: loaded (/lib/systemd/system/mochad.service; disabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-10-28 15:01:27 EDT; 37s ago
  Process: 3068 ExecStart=/usr/local/bin/mochad (code=exited, status=0/SUCCESS)
 Main PID: 3069 (mochad)
   CGroup: /system.slice/mochad.service
           └─3069 /usr/local/bin/mochad

Oct 28 15:01:27 raspberrypi systemd[1]: Starting Start mochad service...
Oct 28 15:01:27 raspberrypi mochad[3068]: starting
Oct 28 15:01:27 raspberrypi systemd[1]: Started Start mochad service.
Oct 28 15:01:27 raspberrypi mochad[3069]: Found CM15A
Oct 28 15:01:27 raspberrypi mochad[3069]: In endpoint 0x81, Out endpoint 0x02

PS -A or aux generally shows mochad running...
---------------------------------------------------------------------------

So this is with ver 1.17...   I tried 1.16 and too many things have been tried for me to even recall why it did not work consistently...

Any ideas?

[petera]

Have you set up Mochad as a background daemon service as I mentioned in a previous post. Working on initial boot and the stopping is classic symptoms of Mochad service being setup incorrectly. Post a copy of your Mochad.service file

[petera]

This is a start to finish post of Mochad and Domoticz. Might be worth reading from start to finish to troubleshoot your problem https://www.sigmdel.ca/michel/ha/x10/domoticz_install_03_en.html

There has been reports of problems with Mochad locking up when sensors were sending commands back to Mochad.

I’d really try and get Mochad working fully before integrating it into Domoticz.

[mike]

Actually that is the guide I do use, so it was followed exactly...

I have see cases where it will work one time sending an echo a1 on | nc ...1099   command then lock up.  I have seen times it never does anything.  ps -A shows mochad in its list after plugging in the cm15. 

/home/pi/mochad/mochad-0.1.17/mochad.service is this:

[Unit]
Description=Start mochad service

[Service]
Type=forking
ExecStart=/usr/local/bin/mochad

[Install]
WantedBy=multi-user.target

[petera]

Actually that is the guide I do use, so it was followed exactly...

I have see cases where it will work one time sending an echo a1 on | nc ...1099   command then lock up.  I have seen times it never does anything.  ps -A shows mochad in its list after plugging in the cm15. 

/home/pi/mochad/mochad-0.1.17/mochad.service is this:

[Unit]
Description=Start mochad service

[Service]
Type=forking
ExecStart=/usr/local/bin/mochad

[Install]
WantedBy=multi-user.target

Where's your restart command in the service file

Here's a sample of a Mochad service daemon file you'd probably need to keep Mochad running on failure. You'll have to make adjustments to suit your own purposes.


[Unit]
Description=Mochad X10 Daemon
Requires=systemd-udevd.service
Wants=network.target
After=systemd-udevd.service network.target

[Service]
Type=forking
GuessMainPID=yes
ExecStart=/usr/local/bin/mochad
TimeoutStartSec=6
Restart=always
RestartSec=3

[Install]
WantedBy=multi-user.target

[mike]

http://forums.x10.com/Smileys/default/headbanging.gif         How I feel about Mochad at this point...   

Thanks, I will add your restart stuff to the file, just one question:  ADD TO WHICH FILE?

I found that same file in the mochad directory as I showed, but it is also in some other root location - IIRC it was maybe /etc/local

Oh never mind, I will just modify it in BOTH locations.

THANKS.

Last experimenting I could send echo a1 on | nc ...1099 and that left the command active so I could see everytime cm15 saw and reported a command from elsewhere.  Ie., I could push remote pad buttons and mochad would show them as they happened in the SSH window...  so I knew the cm15 was talking back to Mochad.  BUT the echo command I typed in for mochad to SEND to the cm15 was indeed echoed back on the screen, but no command went out of the cm15 to the pl...  like mochad is running but not its service - if there are two different programs supposed to be running at the same time?

[petera]

Add those lines to mochad.service which should be stored at /etc/systemd/system. Please ensure you don't have two incidences of mochad.service running. Just type sudo systemctl status mochad.service to ensure the service is running correctly.

Once you have a correctly constructed service daemon running on boot Mochad runs in the background until it is called upon. Again sudo systemctl status mochad.service to check all is working fine. One service only required to handle Mochad.

[mike]

not in /etc/systemd/system...   but here:

/home/pi/mochad/mochad-0.1.17/systemd/mochad.service
/lib/systemd/system/mochad.service

And it is running;  THIS is the one that is hooked to the cm15 I think...  It is mochad app program??  that is not hooked to it, if this makes sense?

The following is typical and still cm15 not working:

pi@raspberrypi:~ $ systemctl status mochad.service
● mochad.service - Start mochad service
   Loaded: loaded (/lib/systemd/system/mochad.service; disabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-10-28 18:01:45 EDT; 21h ago
  Process: 3612 ExecStart=/usr/local/bin/mochad (code=exited, status=0/SUCCESS)
 Main PID: 3613 (mochad)
   CGroup: /system.slice/mochad.service
           └─3613 /usr/local/bin/mochad

Oct 28 18:01:45 raspberrypi systemd[1]: Starting Start mochad service...
Oct 28 18:01:45 raspberrypi mochad[3612]: starting
Oct 28 18:01:45 raspberrypi systemd[1]: Started Start mochad service.
Oct 28 18:01:45 raspberrypi mochad[3613]: Found CM15A
Oct 28 18:01:45 raspberrypi mochad[3613]: In endpoint 0x81, Out endpoint 0x02
pi@raspberrypi:~ $

Not working as shown by this command:   

pi@raspberrypi:~ $ echo "pl b10 off" | nc  localhost 1099                                   
^Z       [<<-- I have to push this to close this and return to pi command line...]
[2]+  Stopped                 echo "pl b10 off" | nc localhost 1099
pi@raspberrypi:~ $

So mochad.service is running, connected to cm15, but mochad (the python script?  program?)  is not hooked to the service?

[mike]

I've changed them both...    no difference...

I went back into AHP and cleared memory again...  no change

I went in and changed it to transceive RF, no change

Sending echo...  nc     does nothing

systemctl check shows cm15 active and hooked up...

echo nc...   does nothing now after reboots...  If I didn't realize there is something ELSE going on here, I would think the added restart stuff is causing it to be worse again... 

but again, mochad service is running solid, with access to the cm15, it is just the echo a1 off | nc is NOT sending the pl asked to send... 

http://forums.x10.com/Smileys/default/headbanging.gif


http://forums.x10.com/Smileys/default/BDH.gif

[petera]

Can you turn a light on and off using Mochad directly

[petera]

After you have rebooted your Pi what happens when you type these two commands at the terminal prompt. Change the house codes for the ones you are using

$ echo "pl a1 on" | nc localhost 1099
$ echo "pl a1 off" | nc locahost 1099



btw you have a mochad.service file located here /home/pi/mochad/mochad-0.1.17/systemd/mochad.service. It shouldn't be there but I'm assuming it hasn't been enabled so it's doing no damage.You edit the mochad.service file located at /lib/systemd/system/mochad.service and that's it. Be careful what folders you are using to create files in.

[mike]

i am not creating ANY folders;  I am not copying or creating any files.  All the mochad stuff on my pi are from its own installation!

I will circle back to answer your question in another post;  sometimes it shows sending the codes and nothing happens, other times it shows nothing.  when it does show sending the codes, if I send 10 from another source it shows up in the list...  until I quit it with ^z.

I am convinced the cm15 is being attached to a version of mochad first run then stopped for whatever reason, and future restarted versions of mochad try to attach to another copy of cm15, but by then it is too late - cm15 is already attached to the first process that no longer is running so not available to future copies of mochad.  or something along these lines...  I can seee what appears to be multiple PID copies of cm15 being assigned in the /var/log/messages file:

Oct 29 15:40:10 raspberrypi kernel: [    2.263007] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
Oct 29 15:40:10 raspberrypi kernel: [    2.403953] usb 1-1.4: New USB device found, idVendor=0409, idProduct=005a
Oct 29 15:40:10 raspberrypi kernel: [    2.411591] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 15:40:10 raspberrypi kernel: [    2.422591] hub 1-1.4:1.0: USB hub found
Oct 29 15:40:10 raspberrypi kernel: [    2.431550] hub 1-1.4:1.0: 4 ports detected
Oct 29 15:40:10 raspberrypi kernel: [    2.502996] usb 1-1.1.2: new low-speed USB device number 5 using dwc_otg
Oct 29 15:40:10 raspberrypi kernel: [    2.651933] usb 1-1.1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 15:40:10 raspberrypi kernel: [    2.659459] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 15:40:10 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP device
Oct 29 15:40:10 raspberrypi liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="218" x-info="http://www.rsyslog.com"] start
Oct 29 15:40:10 raspberrypi kernel: [    2.666883] usb 1-1.1.2: Product: USB ActiveHome Interface
Oct 29 15:40:10 raspberrypi kernel: [    2.674260] usb 1-1.1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 15:40:10 raspberrypi kernel: [    2.697793] NET: Registered protocol family 10
Oct 29 15:40:10 raspberrypi kernel: [    2.707294] Segment Routing with IPv6
Oct 29 15:40:10 raspberrypi kernel: [    2.731695] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 29 15:40:10 raspberrypi kernel: [    2.766053] random: systemd: uninitialized urandom read (16 bytes read)
Oct 29 15:40:10 raspberrypi kernel: [    2.910969] random: systemd: uninitialized urandom read (16 bytes read)
Oct 29 15:40:10 raspberrypi kernel: [    3.183059] usb 1-1.1.3: new full-speed USB device number 6 using dwc_otg
Oct 29 15:40:10 raspberrypi kernel: [    3.199094] random: systemd-gpt-aut: uninitialized urandom read (16 bytes read)
Oct 29 15:40:10 raspberrypi kernel: [    3.338641] usb 1-1.1.3: New USB device found, idVendor=062a, idProduct=4c01
Oct 29 15:40:10 raspberrypi kernel: [    3.347104] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 15:40:10 raspberrypi kernel: [    3.355388] usb 1-1.1.3: Product: 2.4G Keyboard Mouse
Oct 29 15:40:10 raspberrypi kernel: [    3.363705] usb 1-1.1.3: Manufacturer: MOSART Semi.
Oct 29 15:40:10 raspberrypi kernel: [    3.394495] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:062A:4C01.0001/input/input0
Oct 29 15:40:10 raspberrypi kernel: [    3.474123] hid-generic 0003:062A:4C01.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. 2.4G Keyboard Mouse] on usb-20980000.usb-1.1.3/input0
Oct 29 15:40:10 raspberrypi kernel: [    3.523132] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.1/0003:062A:4C01.0002/input/input1
Oct 29 15:40:10 raspberrypi kernel: [    3.594192] hid-generic 0003:062A:4C01.0002: input,hiddev96,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on usb-20980000.usb-1.1.3/input1
Oct 29 15:40:10 raspberrypi kernel: [    7.499851] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Oct 29 15:40:10 raspberrypi kernel: [   11.727161] usbcore: registered new interface driver brcmfmac
Oct 29 15:40:10 raspberrypi kernel: [   12.221696] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Oct 29 15:40:10 raspberrypi kernel: [   12.316639] bcm2835_alsa bcm2835_alsa: card created with 8 channels
Oct 29 15:40:10 raspberrypi kernel: [   14.415832] random: crng init done
Oct 29 15:40:10 raspberrypi kernel: [   14.415861] random: 7 urandom warning(s) missed due to ratelimiting
Oct 29 15:40:11 raspberrypi kernel: [   16.185216] uart-pl011 20201000.serial: no DMA platform data
Oct 29 15:40:13 raspberrypi kernel: [   18.721255] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
Oct 29 15:40:15 raspberrypi kernel: [   20.543052] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 29 15:40:15 raspberrypi kernel: [   20.543101] brcmfmac: power management disabled
Oct 29 15:40:15 raspberrypi kernel: [   20.685380] Bluetooth: Core ver 2.22
Oct 29 15:40:15 raspberrypi kernel: [   20.685524] NET: Registered protocol family 31
Oct 29 15:40:15 raspberrypi kernel: [   20.685532] Bluetooth: HCI device and connection manager initialized
Oct 29 15:40:15 raspberrypi kernel: [   20.685559] Bluetooth: HCI socket layer initialized
Oct 29 15:40:15 raspberrypi kernel: [   20.685573] Bluetooth: L2CAP socket layer initialized
Oct 29 15:40:15 raspberrypi kernel: [   20.685619] Bluetooth: SCO socket layer initialized
Oct 29 15:40:15 raspberrypi kernel: [   20.703568] Bluetooth: HCI UART driver ver 2.3
Oct 29 15:40:15 raspberrypi kernel: [   20.703640] Bluetooth: HCI UART protocol H4 registered
Oct 29 15:40:15 raspberrypi kernel: [   20.703647] Bluetooth: HCI UART protocol Three-wire (H5) registered
Oct 29 15:40:15 raspberrypi kernel: [   20.706302] Bluetooth: HCI UART protocol Broadcom registered
Oct 29 15:40:16 raspberrypi kernel: [   21.313022] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 29 15:40:16 raspberrypi kernel: [   21.313037] Bluetooth: BNEP filters: protocol multicast
Oct 29 15:40:16 raspberrypi kernel: [   21.313066] Bluetooth: BNEP socket layer initialized
Oct 29 15:40:16 raspberrypi kernel: [   21.850149] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 29 15:40:22 raspberrypi mochad[425]: starting
Oct 29 15:40:22 raspberrypi mochad[427]: Found CM15A
Oct 29 15:40:22 raspberrypi mochad[427]: In endpoint 0x81, Out endpoint 0x02
Oct 29 15:40:23 raspberrypi domoticz: Domoticz is starting up....
Oct 29 15:40:23 raspberrypi domoticz: Domoticz running...
Oct 29 15:40:53 raspberrypi mochad[523]: starting
Oct 29 15:40:53 raspberrypi mochad[524]: Found kernel driver 0, trying detach
Oct 29 15:40:53 raspberrypi mochad[524]: terminated
Oct 29 16:06:07 raspberrypi kernel: [ 1562.443220] usb 1-1.1.2: USB disconnect, device number 5
Oct 29 16:08:37 raspberrypi kernel: [ 1712.784421] usb 1-1.2: new low-speed USB device number 7 using dwc_otg
Oct 29 16:08:37 raspberrypi kernel: [ 1712.922889] usb 1-1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 16:08:37 raspberrypi kernel: [ 1712.922915] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 16:08:37 raspberrypi kernel: [ 1712.922928] usb 1-1.2: Product: USB ActiveHome Interface
Oct 29 16:08:37 raspberrypi kernel: [ 1712.922941] usb 1-1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 16:08:37 raspberrypi mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.2"
Oct 29 16:08:37 raspberrypi mtp-probe: bus: 1, device: 7 was not an MTP device
Oct 29 16:09:10 raspberrypi kernel: [ 1745.515652] usb 1-1.2: USB disconnect, device number 7
Oct 29 16:09:13 raspberrypi kernel: [ 1748.596759] usb 1-1.1.2: new low-speed USB device number 8 using dwc_otg
Oct 29 16:09:13 raspberrypi kernel: [ 1748.734981] usb 1-1.1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 16:09:13 raspberrypi kernel: [ 1748.735010] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 16:09:13 raspberrypi kernel: [ 1748.735025] usb 1-1.1.2: Product: USB ActiveHome Interface
Oct 29 16:09:13 raspberrypi kernel: [ 1748.735037] usb 1-1.1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 16:09:13 raspberrypi mtp-probe: checking bus 1, device 8: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 16:09:13 raspberrypi mtp-probe: bus: 1, device: 8 was not an MTP device
Oct 29 16:10:08 raspberrypi kernel: [ 1803.339868] usb 1-1.1.2: USB disconnect, device number 8
Oct 29 16:11:18 raspberrypi kernel: [ 1874.034122] usb 1-1.1.2: new low-speed USB device number 9 using dwc_otg
Oct 29 16:11:18 raspberrypi kernel: [ 1874.172474] usb 1-1.1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 16:11:18 raspberrypi kernel: [ 1874.172502] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 16:11:18 raspberrypi kernel: [ 1874.172515] usb 1-1.1.2: Product: USB ActiveHome Interface
Oct 29 16:11:18 raspberrypi kernel: [ 1874.172527] usb 1-1.1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 16:11:19 raspberrypi mtp-probe: checking bus 1, device 9: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 16:11:19 raspberrypi mtp-probe: bus: 1, device: 9 was not an MTP device
Oct 29 16:12:26 raspberrypi mochad[635]: starting
Oct 29 16:12:26 raspberrypi mochad[636]: terminated
Oct 29 16:12:32 raspberrypi mochad[638]: starting
Oct 29 16:12:32 raspberrypi mochad[639]: terminated
Oct 29 16:12:59 raspberrypi mochad[646]: starting
Oct 29 16:12:59 raspberrypi mochad[647]: terminated
Oct 29 16:29:15 raspberrypi kernel: [ 2951.246758] usb 1-1.1.2: USB disconnect, device number 9
Oct 29 16:29:25 raspberrypi kernel: [ 2961.272716] usb 1-1.1.2: new low-speed USB device number 10 using dwc_otg
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411059] usb 1-1.1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411088] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411101] usb 1-1.1.2: Product: USB ActiveHome Interface
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411112] usb 1-1.1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 16:29:26 raspberrypi mtp-probe: checking bus 1, device 10: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 16:29:26 raspberrypi mtp-probe: bus: 1, device: 10 was not an MTP device
Oct 29 17:45:25 raspberrypi mochad[427]: detaching CM15A
Oct 29 17:45:25 raspberrypi mochad[427]: terminated
Oct 29 17:45:28 raspberrypi mochad[699]: starting
Oct 29 17:45:28 raspberrypi mochad[700]: Found CM15A
Oct 29 17:45:28 raspberrypi mochad[700]: In endpoint 0x81, Out endpoint 0x02

[mike]

I swear mochad cannot find the cm15 even tho it says found in momchad.service!      this var/log/messages seems to say it:

Oct 29 16:29:15 raspberrypi kernel: [ 2951.246758] usb 1-1.1.2: USB disconnect, device number 9
Oct 29 16:29:25 raspberrypi kernel: [ 2961.272716] usb 1-1.1.2: new low-speed USB device number 10 using dwc_otg
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411059] usb 1-1.1.2: New USB device found, idVendor=0bc7, idProduct=0001
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411088] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411101] usb 1-1.1.2: Product: USB ActiveHome Interface
Oct 29 16:29:26 raspberrypi kernel: [ 2961.411112] usb 1-1.1.2: Manufacturer: X10 Wireless Technology Inc
Oct 29 16:29:26 raspberrypi mtp-probe: checking bus 1, device 10: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.1/1-1.1.2"
Oct 29 16:29:26 raspberrypi mtp-probe: bus: 1, device: 10 was not an MTP device
Oct 29 17:45:25 raspberrypi mochad[427]: detaching CM15A
Oct 29 17:45:25 raspberrypi mochad[427]: terminated
Oct 29 17:45:28 raspberrypi mochad[699]: starting
Oct 29 17:45:28 raspberrypi mochad[700]: Found CM15A
Oct 29 17:45:28 raspberrypi mochad[700]: In endpoint 0x81, Out endpoint 0x02
Oct 29 20:13:10 raspberrypi mochad[1971]: starting
Oct 29 20:13:11 raspberrypi mochad[1971]: Found kernel driver 0, trying detach
Oct 29 20:13:11 raspberrypi mochad[1971]: terminated
Oct 29 20:14:14 raspberrypi mochad[1981]: starting
Oct 29 20:14:14 raspberrypi mochad[1982]: Found kernel driver 0, trying detach
Oct 29 20:14:14 raspberrypi mochad[1982]: terminated
Oct 29 20:19:04 raspberrypi mochad[2005]: starting
Oct 29 20:19:04 raspberrypi mochad[2006]: Found kernel driver 0, trying detach
Oct 29 20:19:04 raspberrypi mochad[2006]: terminated

each 3 line failure at end is from sending ./mochad command in terminal window...

[petera]

What's the output from dmesg and lsusb now.

[petera]

Can you revert to an image that Mochad is known to work on. Your current install looks broken to me.

Mochad really is easy to install. You create the makefile, build it and install it. You then plug in your CM15 and you're ready to go. After that you create the service daemon to launch Mochad on boot.