powerlinc usb and 2.6.17.1?

[Joe Buehler-3]

I am unable to get wish to work with 2.6.17.1.  I've tried
two different machines, one SMP with an add-on PCI USB
card and one UP with integrated USB, with the same results:

echo on >/dev/x10/c2

(for example) does nothing to the named x10 receiver.
I've turned on debugging on driver and daemon -- nothing
obviously amiss -- and increased the -delay parameter on
plusbd to 10.  It just doesn't work.

Perhaps this kernel version is not a good one to use
for wish?

I had had an older version working with a 2.4 kernel just
fine for quite a while.

Joe Buehler


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

[Scott Hiles]

Have you verified that you are pointing the driver at the correct device?
If you have the latest version, I have some code in the startup script that
attempts to detect the device name for the USB device.  But, if your system
has a different mapping than Fedora, you may need to adjust this script to
detect your USB device.

Look in your /var/log/messages and make sure that the SmartHome device is
found and that when you start plusbd that you get a message in the
/var/log/messages indicating the version of your transceiver.

Scott

> -----Original Message-----
> From: wish-info-bounces@...
> [mailto:wish-info-bounces@...] On Behalf Of
> Joe Buehler
> Sent: Saturday, January 13, 2007 11:54 AM
> To: wish-info@...
> Subject: [wish-info] powerlinc usb and 2.6.17.1?
>
> I am unable to get wish to work with 2.6.17.1.  I've tried
> two different machines, one SMP with an add-on PCI USB
> card and one UP with integrated USB, with the same results:
>
> echo on >/dev/x10/c2
>
> (for example) does nothing to the named x10 receiver.
> I've turned on debugging on driver and daemon -- nothing
> obviously amiss -- and increased the -delay parameter on
> plusbd to 10.  It just doesn't work.
>
> Perhaps this kernel version is not a good one to use
> for wish?
>
> I had had an older version working with a 2.4 kernel just
> fine for quite a while.
>
> Joe Buehler
>
>
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the
> chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
> &CID=DEVDEV
> _______________________________________________
> wish-info mailing list
> wish-info@...
> https://lists.sourceforge.net/lists/listinfo/wish-info
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

[Joe Buehler-3]

WSH wrote:

> Have you verified that you are pointing the driver at the correct device?
> If you have the latest version, I have some code in the startup script that
> attempts to detect the device name for the USB device.  But, if your system
> has a different mapping than Fedora, you may need to adjust this script to
> detect your USB device.
>
> Look in your /var/log/messages and make sure that the SmartHome device is
> found and that when you start plusbd that you get a message in the
> /var/log/messages indicating the version of your transceiver.

I'm running the latest -- 2.1.5.  Here is how I built it:

rm -fr x10dev-2.1.5 &&
tar -xzf x10dev-2.1.5.tar.gz &&
(
        cd x10dev-2.1.5 &&
        make &&
        make install &&
        true
)

This is on a CentOS 4.3 box.  Since their (highly patched) 2.6.9
kernel did not work I thought I would try an unpatched kernel.org
version, but it (2.6.17.1) behaves the same.  I am in the process
building 2.6.19.2 at the moment to see what happens there.

I believe you are talking about the hiddev line that the startup
script looks for?  Here it is:

Jan 11 21:47:51 altera kernel: usb 2-2: new low speed USB device using ohci_hcd and address 2
Jan 11 21:47:51 altera kernel: usb 2-2: configuration #1 chosen from 1 choice
Jan 11 21:47:52 altera kernel: hiddev96: USB HID v1.00 Device [SmartHome SmartHome PowerLinc USB] on usb-0000:00:0d.0-2
Jan 11 21:47:52 altera kernel: usb usb3: configuration #1 chosen from 1 choice

Here is the plusbd log for starting up and then my trying to send a command to C2:

Jan 13 11:43:44 altera kernel: x10: X10 DEV module v2.1.3 (wsh@...)
Jan 13 11:43:44 altera kernel: x10: $Id: dev.c,v 1.23 2006/03/29 02:33:23 root Exp root $
Jan 13 11:43:44 altera kernel: x10: X10 driver successfully loaded
Jan 13 11:43:44 altera plusbd[20768]: starting. api-device=/dev/x10/.api, pidfile=/var/run/x10d.pid
Jan 13 11:43:44 altera plusbd[20768]: Successfully opened X10 API device /dev/x10/.api
Jan 13 11:43:45 altera plusbd[20777]: starting transceiver (pthread_create)
Jan 13 11:43:45 altera plusbd[20777]: pthread_crate completed...transceiver started
Jan 13 11:43:45 altera plusbd[20777]: Transmit thread starting
Jan 13 11:43:45 altera plusbd[20777]: Connecting to USB Powerlinc Interface on /dev/hiddev0
Jan 13 11:43:45 altera plusbd[20777]: /dev/hiddev0: Vendor 0x10bf, Product 0x0001 version 0x0400
Jan 13 11:43:45 altera plusbd[20777]: /dev/hiddev0: 1 application on bus 2, devnum 3, ifnum 0
Jan 13 11:43:45 altera plusbd[20777]: USB Powerlinc version 0x0400 found
Jan 13 11:43:45 altera plusbd[20777]: INPUT Report id: 0 (1 fields)
Jan 13 11:43:45 altera plusbd[20777]: INPUT Field: 0: app: ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000001 val 00 idx 0
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000002 val 00 idx 1
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000003 val 00 idx 2
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000004 val 00 idx 3
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000005 val 00 idx 4
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000006 val 00 idx 5
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000007 val 00 idx 6
Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000008 val 00 idx 7
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Report id: 0 (1 fields)
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Field: 0: app: ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000001 val 00 idx 0
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000002 val 00 idx 1
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000003 val 00 idx 2
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000004 val 00 idx 3
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000005 val 00 idx 4
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000006 val 00 idx 5
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000007 val 00 idx 6
Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000008 val 00 idx 7
Jan 13 11:43:46 altera plusbd[20777]: Reports initialized...now starting PowerLinc initialization
Jan 13 11:43:46 altera plusbd[20777]: wrote 20 04 1e 00 00 00 00 00
Jan 13 11:43:46 altera plusbd[20777]: wrote 20 71 00 00 00 00 00 00
Jan 13 11:43:46 altera plusbd[20777]: USB PowerLinc stages 1 and 2 complete
Jan 13 11:43:46 altera plusbd[20777]: wrote 20 08 00 00 00 00 00 00
Jan 13 11:43:46 altera plusbd[20777]: INPUT Report id: 0 (1 fields)
Jan 13 11:43:46 altera plusbd[20777]: INPUT Field: 0: app: ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000001 val 80 idx 0
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000002 val 01 idx 1
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000003 val 00 idx 2
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000004 val 01 idx 3
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000005 val 04 idx 4
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000006 val 00 idx 5
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000007 val 00 idx 6
Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000008 val 00 idx 7
Jan 13 11:43:46 altera plusbd[20777]: USB Powerlinc Hardware Rev 1.4 found
Jan 13 11:43:46 altera plusbd[20777]: got connect message
Jan 13 11:43:46 altera plusbd[20777]: transmitter connected
Jan 13 11:43:46 altera plusbd[20777]: Waiting for input from API interface
Jan 13 11:43:57 altera plusbd[20777]: X10 message: src=0x2, hc=0x2, uc=0x1, cmd=0x2, f=0x0
Jan 13 11:43:57 altera plusbd[20777]: transmit:  hc=0x2, uc=0x1, fc=0x2
Jan 13 11:43:57 altera plusbd[20777]: sem_wait_timeout: timeout=10000
Jan 13 11:43:58 altera plusbd[20777]: sending 00 43 42 00 00 00 00 00
Jan 13 11:43:59 altera plusbd[20777]: wrote 00 43 42 00 00 00 00 00
Jan 13 11:43:59 altera plusbd[20777]: sending 00 43 63 00 00 00 00 00
Jan 13 11:44:00 altera plusbd[20777]: wrote 00 43 63 00 00 00 00 00
Jan 13 11:44:00 altera plusbd[20777]: update_state:  dir=1, hc=0x2, uc=0x1, fc=0x2
Jan 13 11:44:00 altera plusbd[20777]: semaphore value:  1
Jan 13 11:44:00 altera plusbd[20777]: Got the state lock
Jan 13 11:44:00 altera plusbd[20777]: Updating status.....
Jan 13 11:44:00 altera kernel: X10: T C2
Jan 13 11:44:00 altera kernel: X10: T C ON
Jan 13 11:44:00 altera plusbd[20777]: status update done.
Jan 13 11:44:00 altera plusbd[20777]: Released the state lock
Jan 13 11:44:00 altera plusbd[20777]: Waiting for input from API interface

Joe Buehler


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

[Scott Hiles]

Everything in your log indicates that the transceiver is recognized and is
working.  So, this is not a kernel issue.

So, this log indicates that the driver is successfully communicating with
the transceiver both in transmitting commands and getting responses from the
transceiver.  The next thing I would check would be to see if the
transceiver on a noisy line.  You said it worked before with the 1.x drivers
so I am thinking that it should be working.

But, make sure that your transceiver is plugged directly into a wall outlet.
Then make sure that the outlet that it is plugged into does not also have
your computer, a TV, a motorized appliance, or a UPS plugged into the same
circuit.  

If you have all of that checked out, try plugging a lamplink or something
directly into the same socket that the transceiver is plugged into and see
if you can get any commands to the lamplink.  

I have a Powerlinc that went bad that behaves as your is behaving.
Everything in the system seemed to work and the powerlink responded but it
never sent anything on the powerline.  The way that I proved to myself that
it was the Powerlinc was I hooked it to a computer with the SmartHome
software and it also could not send out any signals.  So, if all else fails,
verify that the transceiver is working properly if you can.

I can't think of anything else off the top of my head.

Scott

> -----Original Message-----
> From: wish-info-bounces@...
> [mailto:wish-info-bounces@...] On Behalf Of
> Joe Buehler
> Sent: Saturday, January 13, 2007 2:17 PM
> To: wish-info@...
> Subject: Re: [wish-info] powerlinc usb and 2.6.17.1?
>
> WSH wrote:
>
> > Have you verified that you are pointing the driver at the
> correct device?
> > If you have the latest version, I have some code in the
> startup script that
> > attempts to detect the device name for the USB device.  
> But, if your system
> > has a different mapping than Fedora, you may need to adjust
> this script to
> > detect your USB device.
> >
> > Look in your /var/log/messages and make sure that the
> SmartHome device is
> > found and that when you start plusbd that you get a message in the
> > /var/log/messages indicating the version of your transceiver.
>
> I'm running the latest -- 2.1.5.  Here is how I built it:
>
> rm -fr x10dev-2.1.5 &&
> tar -xzf x10dev-2.1.5.tar.gz &&
> (
> cd x10dev-2.1.5 &&
> make &&
> make install &&
> true
> )
>
> This is on a CentOS 4.3 box.  Since their (highly patched) 2.6.9
> kernel did not work I thought I would try an unpatched kernel.org
> version, but it (2.6.17.1) behaves the same.  I am in the process
> building 2.6.19.2 at the moment to see what happens there.
>
> I believe you are talking about the hiddev line that the startup
> script looks for?  Here it is:
>
> Jan 11 21:47:51 altera kernel: usb 2-2: new low speed USB
> device using ohci_hcd and address 2
> Jan 11 21:47:51 altera kernel: usb 2-2: configuration #1
> chosen from 1 choice
> Jan 11 21:47:52 altera kernel: hiddev96: USB HID v1.00 Device
> [SmartHome SmartHome PowerLinc USB] on usb-0000:00:0d.0-2
> Jan 11 21:47:52 altera kernel: usb usb3: configuration #1
> chosen from 1 choice
>
> Here is the plusbd log for starting up and then my trying to
> send a command to C2:
>
> Jan 13 11:43:44 altera kernel: x10: X10 DEV module v2.1.3
> (wsh@...)
> Jan 13 11:43:44 altera kernel: x10: $Id: dev.c,v 1.23
> 2006/03/29 02:33:23 root Exp root $
> Jan 13 11:43:44 altera kernel: x10: X10 driver successfully loaded
> Jan 13 11:43:44 altera plusbd[20768]: starting.
> api-device=/dev/x10/.api, pidfile=/var/run/x10d.pid
> Jan 13 11:43:44 altera plusbd[20768]: Successfully opened X10
> API device /dev/x10/.api
> Jan 13 11:43:45 altera plusbd[20777]: starting transceiver
> (pthread_create)
> Jan 13 11:43:45 altera plusbd[20777]: pthread_crate
> completed...transceiver started
> Jan 13 11:43:45 altera plusbd[20777]: Transmit thread starting
> Jan 13 11:43:45 altera plusbd[20777]: Connecting to USB
> Powerlinc Interface on /dev/hiddev0
> Jan 13 11:43:45 altera plusbd[20777]: /dev/hiddev0: Vendor
> 0x10bf, Product 0x0001 version 0x0400
> Jan 13 11:43:45 altera plusbd[20777]: /dev/hiddev0: 1
> application on bus 2, devnum 3, ifnum 0
> Jan 13 11:43:45 altera plusbd[20777]: USB Powerlinc version
> 0x0400 found
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Report id: 0 (1 fields)
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Field: 0: app:
> ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000001
> val 00 idx 0
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000002
> val 00 idx 1
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000003
> val 00 idx 2
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000004
> val 00 idx 3
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000005
> val 00 idx 4
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000006
> val 00 idx 5
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000007
> val 00 idx 6
> Jan 13 11:43:45 altera plusbd[20777]: INPUT Usage: ff000008
> val 00 idx 7
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Report id: 0 (1 fields)
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Field: 0: app:
> ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000001
> val 00 idx 0
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000002
> val 00 idx 1
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000003
> val 00 idx 2
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000004
> val 00 idx 3
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000005
> val 00 idx 4
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000006
> val 00 idx 5
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000007
> val 00 idx 6
> Jan 13 11:43:46 altera plusbd[20777]: OUTPUT Usage: ff000008
> val 00 idx 7
> Jan 13 11:43:46 altera plusbd[20777]: Reports
> initialized...now starting PowerLinc initialization
> Jan 13 11:43:46 altera plusbd[20777]: wrote 20 04 1e 00 00 00 00 00
> Jan 13 11:43:46 altera plusbd[20777]: wrote 20 71 00 00 00 00 00 00
> Jan 13 11:43:46 altera plusbd[20777]: USB PowerLinc stages 1
> and 2 complete
> Jan 13 11:43:46 altera plusbd[20777]: wrote 20 08 00 00 00 00 00 00
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Report id: 0 (1 fields)
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Field: 0: app:
> ff000001 phys 0000 flags 2 (8 usages) unit 0 exp 0
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000001
> val 80 idx 0
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000002
> val 01 idx 1
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000003
> val 00 idx 2
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000004
> val 01 idx 3
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000005
> val 04 idx 4
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000006
> val 00 idx 5
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000007
> val 00 idx 6
> Jan 13 11:43:46 altera plusbd[20777]: INPUT Usage: ff000008
> val 00 idx 7
> Jan 13 11:43:46 altera plusbd[20777]: USB Powerlinc Hardware
> Rev 1.4 found
> Jan 13 11:43:46 altera plusbd[20777]: got connect message
> Jan 13 11:43:46 altera plusbd[20777]: transmitter connected
> Jan 13 11:43:46 altera plusbd[20777]: Waiting for input from
> API interface
> Jan 13 11:43:57 altera plusbd[20777]: X10 message: src=0x2,
> hc=0x2, uc=0x1, cmd=0x2, f=0x0
> Jan 13 11:43:57 altera plusbd[20777]: transmit:  hc=0x2,
> uc=0x1, fc=0x2
> Jan 13 11:43:57 altera plusbd[20777]: sem_wait_timeout: timeout=10000
> Jan 13 11:43:58 altera plusbd[20777]: sending 00 43 42 00 00 00 00 00
> Jan 13 11:43:59 altera plusbd[20777]: wrote 00 43 42 00 00 00 00 00
> Jan 13 11:43:59 altera plusbd[20777]: sending 00 43 63 00 00 00 00 00
> Jan 13 11:44:00 altera plusbd[20777]: wrote 00 43 63 00 00 00 00 00
> Jan 13 11:44:00 altera plusbd[20777]: update_state:  dir=1,
> hc=0x2, uc=0x1, fc=0x2
> Jan 13 11:44:00 altera plusbd[20777]: semaphore value:  1
> Jan 13 11:44:00 altera plusbd[20777]: Got the state lock
> Jan 13 11:44:00 altera plusbd[20777]: Updating status.....
> Jan 13 11:44:00 altera kernel: X10: T C2
> Jan 13 11:44:00 altera kernel: X10: T C ON
> Jan 13 11:44:00 altera plusbd[20777]: status update done.
> Jan 13 11:44:00 altera plusbd[20777]: Released the state lock
> Jan 13 11:44:00 altera plusbd[20777]: Waiting for input from
> API interface
>
> Joe Buehler
>
>
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the
> chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
> &CID=DEVDEV
> _______________________________________________
> wish-info mailing list
> wish-info@...
> https://lists.sourceforge.net/lists/listinfo/wish-info
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info