Nabble - X10 - WiSH

Has anyone seen x10serv crash as soon as one clicks on "DETECTED: tab in the java GUI

2008-07-11T17:26:56Z

Has anyone seen x10serv crash as soon as one clicks on "DETECTED: tab in the java GUI?

Here is the x10serv -d output in that prescise moment in time: (after this the kernel holts, entire system crashes, reboot is the only way out)

x10serv (pid 13932): client host 192.168.248.51
x10serv (pid 13932): client port 49422
x10serv (pid 13932): got < changed
x10serv (pid 13932): Reading /dev/x10/changed
x10serv (pid 13932): writing [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
](67)
x10serv (pid 13932): writing [A: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
](68)
x10serv (pid 13932): writing [B: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [C: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [D: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [E: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [F: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [G: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [H: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [I: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [J: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [K: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [L: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [M: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [N: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [O: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
x10serv (pid 13932): writing [P: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
](68)
All done
x10serv (pid 13932): zero length message, closing
x10serv: reapchild()
x10serv (13932): Found child at 2
Network server accept failure 4
Error: Interrupted system call

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

First try under FC9 - cm11ad works but crashes after some time

2008-07-05T09:00:59Z

First try under FC9 - cm11ad works but crashes after some time

The only item recorded in /var/log/messages is this:

Jul 4 20:35:36 localhost kernel: cm11ad[7431]: segfault at 1002683f ip 0258cd9a sp b7fe20d4 error 4 in libc-2.8.so[251d000+163000]

After cm11ad crashes, restarting it by hand works just fine and ops continue, I dont even have to modprobe or re-load the x10serv or the logd

I did try modprobe x10 debug=1 and then loaded cm11 with -debug option but I dont see any additional feeback other than the /var/log/messages 2 lines with relevant info which is not very helpful?

Any ideas?
Thanks
Boyan

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Re: Time delay when executing blocking commands. Almost nodelay when executing non-blocking commands

2008-01-29T12:29:24Z

You are correct that there is an artificial delay in blocking commands to
the transceiver. There is a parameter you can pass called /delay that will
allow you to adjust this time.

The reason it is there is because I couldn't figure out how to tell the
transceiver to wait for a clear line before transmitting so I always add a
specific delay before the start of any command to allow time for the line to
go quiet. This is very poor design as it relies on having only one active
transceiver in the home. The delay allows for intelligent devices to
respond to queries without the next command jumping in.

Note that this is not a problem with the PowreLink Serial but is for both
the PowerLink USB and the CM11A.

Scott

----- Original Message -----
From: "Boyan Biandov" <boyan.biandov@...>
To: <wish-info@...>
Sent: Tuesday, January 29, 2008 2:15 PM
Subject: [wish-info] Time delay when executing blocking commands. Almost
nodelay when executing non-blocking commands

> Hi,
>
> I am seeing an interesting behavior using CM11A:
>
> I see a time delay when executing blocking commands but almost no delay
> when executing non-blocking commands. This is not the classic "duh,
> that's why they are called non-blocking".
>
> Let me be more specific on this behavior:
>
> When I use echo which is a blocking command, the command blocks for
> about 10 seconds, after which time I get the prompt back. The actual
> task (light turning ON or OFF) is not carried out until the 9th second,
> which is about one second from when I get my prompt back. So there is
> about 8 second delay when I neither get the prompt back nor the x10
> command is sent out.
>
> Conversely when I use nbecho I get the prompt back right away and the
> x10 command is carried out almost instantaneously.
>
> What gives?
>
> ~Boyan
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> wish-info mailing list
> wish-info@...
> https://lists.sourceforge.net/lists/listinfo/wish-info
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Time delay when executing blocking commands. Almost no delay when executing non-blocking commands

2008-01-29T11:08:45Z

Hi,

I am seeing an interesting behavior using CM11A:

I see a time delay when executing blocking commands but almost no delay
when executing non-blocking commands. This is not the classic "duh,
that's why they are called non-blocking".

Let me be more specific on this behavior:

When I use echo which is a blocking command, the command blocks for
about 10 seconds, after which time I get the prompt back. The actual
task (light turning ON or OFF) is not carried out until the 9th second,
which is about one second from when I get my prompt back. So there is
about 8 second delay when I neither get the prompt back nor the x10
command is sent out.

Conversely when I use nbecho I get the prompt back right away and the
x10 command is carried out almost instantaneously.

What gives?

~Boyan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

I can't control brightness while use WiSH

2007-12-14T12:57:14Z

My english is is not good. Sorry.
I start use linux some days ago and try to use your driver in my system.
I use Gentoo.
When I tried to compile driver from sources i recieved error messages.
There for I changed program texts:

nano +621 /var/src/x10dev-2.1.7/dev/dev.c

if (x10api.data >= 0) {
dbg ("unregistering %d:%s", x10api.data, DATA_DEVICE_NAME);
// if (unregister_chrdev (x10api.data, DATA_DEVICE_NAME) == -EINVAL)
// dbg ("error unregistering %s", DATA_DEVICE_NAME);
unregister_chrdev (x10api.data, DATA_DEVICE_NAME);
}
if (x10api.control >= 0) {
dbg ("unregistering %d:%s", x10api.control, CONTROL_DEVICE_NAME);
// if (unregister_chrdev (x10api.control, CONTROL_DEVICE_NAME) == -EINVAL)
// dbg ("error unregistering %s", CONTROL_DEVICE_NAME);
unregister_chrdev (x10api.control, CONTROL_DEVICE_NAME);
}

Is it correct?

After that "make" finished successfuly.
But I recieved message:
scripts/Makefile.build:72: kbuild: /var/src/x10dev-2.1.7/dev/Makefile - Usage of O_TARGET := x10.ko is obsolete in 2.6. Please fix!

I don't know how correct this.
But after "make install" it work.

When I put command "echo 0 > /dev/x10/a5" or "echo 1 > /dev/x10/a5" it work fine.

But when I try to send command "echo ps11 > /dev/x10/a5" nothing happens.

When I use my devices in Windows all work and lamp change it brightness.

I use CM11 and LM12 modules.
I use kernel linux-2.6.23-gentoo-r3

Can you answer to my questions:
1. What do I change to drive brightness of lamp?
2. Can I see what transmit your driver through serial port? In log
file I see:

Dec 14 00:23:23 gent T A5
Dec 14 00:23:23 gent T A ON <-------- it work
Dec 14 00:27:09 gent T A5
Dec 14 00:27:09 gent T G PRESETDIMLOW <-------- it doesn't work
Dec 14 00:27:16 gent T A5
Dec 14 00:27:16 gent T M PRESETDIMLOW <-------- it doesn't work
Dec 14 00:27:21 gent T A5
Dec 14 00:27:21 gent T L PRESETDIMHIGH <-------- it doesn't work
Dec 14 00:27:25 gent T A5
Dec 14 00:27:25 gent T A OFF <-------- it work

Today I add to kernel USB Prolific and recompile kernel
Then I change string "/usr/sbin/cm11ad -device /dev/ttyS0"
to "/usr/sbin/cm11ad -device /dev/ttyUSB0" in start script. All work fine, but brightness don't change.

Can anybody help me?

Victor Kozmin

determine source for messages

2007-12-03T12:59:37Z

I just installed the windows version of misterhouse. I have both the cm11a and cm15a. However I am using the cm11a right now due to compatibility with misterhouse. I have 5 door sensors (one on each door and my garage door), 1 motion sensor (hopefully more), 2 flood light motion sensors (one installed in the back), one lightbult screwer inner thinger (in one basement socket). 3 lamp controls (plugged into the wall, but the wife unplugged the lamp). two x10 cameras (one looking at the front door, the other not used) and a wireless tranceiver (M751) I got most of this in a bundle with the security module DS7000

two things:
1) is there source to the door window opener that I can get it to be recognized by misterhouse and perform an action based on that open door or do i need the w800
2) how do i interpret the log below to know what darn device is sending this:

.............

CM11 data=85 hex=55
CM11 done
Backlog:
X10: interface=cm11 isfunc=1 save_unit=XB1 data=XBJ
CM11 send data=BJ
CM11 dim=0 header=00000110 hb=1110 cb=0010 bd=0x06,0xe2 checksum=0xe8
CM11 send: 06e2 try: 1
..
CM11 data=232 hex=e8
CM11 ack
CM11 send pc_ok, try: 1
............
CM11 data=85 hex=55
CM11 done
Backlog:
12/03/07 10:44:00 AM: Saving object states ... done
X10: interface=cm11 isfunc=0 save_unit=XB1 data=XB1
CM11 send data=B1
CM11 dim=0 header=00000100 hb=1110 cb=0110 bd=0x04,0xe6 checksum=0xea
CM11 send: 04e6 try: 1
..
CM11 data=234 hex=ea
CM11 ack
CM11 send pc_ok, try: 1
............
CM11 data=85 hex=55
CM11 done
Backlog:
X10: interface=cm11 isfunc=1 save_unit=XB1 data=XBK
CM11 send data=BK
CM11 dim=0 header=00000110 hb=1110 cb=0011 bd=0x06,0xe3 checksum=0xe9
CM11 send: 06e3 try: 1

help wanted

2007-11-06T06:39:16Z

Hi,hope to get your help!
I am now using a X10-based CM11 (not CM11A), it has a PC Serial interface, I used it to connect with the COM1 in my PC which is runing Fedora Core 6.
Hope to use this CM11 to control Lamp or other equipments,
but (Question 1)where to get this compatible Linux driver fro this X10-based CM11 (not a CM11A)?
(Question 2)How to install that linux driver?
(Question 3)What's the difference between CM11 and CM11A, I found may reference about CM11A but can not found any about CM11.

Thanks in advance!

Best Regards!

----------------
Jerry

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

X10 Powerlinc on KeySpan USB dongle

2007-08-28T17:10:22Z

Hello;

I am trying to move my x10 setup over to my new Centos5 machine that
(currently) has no serial ports. I am attempting to use my KeySpan
USB-to-Serial connector and attaching the Serial-Powerlinc to that.
Installation of x10dev2 went fine.

Here is my syslog output as I do the mod probe and bring up the 3
processes manually:

Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/usb-serial.c: USB
Serial Driver core
Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for Keyspan - (without firmware)
Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for Keyspan 1 port adapter
Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for Keyspan 2 port adapter
Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for Keyspan 4 port adapter
Aug 28 16:56:03 centos5 kernel: usb 4-2: Keyspan 1 port adapter
converter now attached to ttyUSB0
Aug 28 16:56:03 centos5 kernel: usbcore: registered new driver keyspan
Aug 28 16:56:03 centos5 kernel: drivers/usb/serial/keyspan.c:
v1.1.4:Keyspan USB to Serial Converter Driver
...
Aug 28 17:00:17 centos5 sudo: david : TTY=pts/0 ; PWD=/home/dsdee ;
USER=root ; COMMAND=/sbin/modprobe x10
Aug 28 17:00:17 centos5 kernel: x10: X10 DEV module v2.1.3
(wsh@...)
Aug 28 17:00:17 centos5 kernel: x10: $Id: dev.c,v 1.23 2006/03/29
02:33:23 root Exp root $
Aug 28 17:00:17 centos5 kernel: x10: X10 driver successfully loaded
Aug 28 17:00:20 centos5 sudo: david : TTY=pts/0 ; PWD=/home/dsdee ;
USER=root ; COMMAND=/usr/sbin/pld -tag x10pld -device /dev/ttyUSB0
Aug 28 17:00:20 centos5 x10pld[3941]: starting.
api-device=/dev/x10/.api, pidfile=/var/run/x10d.pid
Aug 28 17:00:20 centos5 x10pld[3941]: Successfully opened X10 API device
/dev/x10/.api
Aug 28 17:00:21 centos5 x10pld[3942]: Transmit thread starting
Aug 28 17:00:23 centos5 x10pld[3942]: Connecting to Powerlinc Serial
Interface on /dev/ttyUSB0
Aug 28 17:00:25 centos5 x10pld[3942]: Timeout reading from /dev/ttyUSB0
Aug 28 17:00:25 centos5 x10pld[3942]: transmitter connected
Aug 28 17:00:28 centos5 sudo: david : TTY=pts/0 ; PWD=/home/dsdee ;
USER=root ; COMMAND=/usr/sbin/x10logd -s -t x10_pl
Aug 28 17:00:28 centos5 x10_pl[3944]: starting.
Logfile=/var/log/x10log, socket-device=/dev/x10/log,
pidfile=/var/run/x10logd.pid

As you can see, it's getting a "Timeout reading from ..." after starting
up the x10pld daemon.

Has anyone else gotten a setup like this to work???

Thanks in advance,
David

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Re: USB Powerlinc (V1) extended codes

2007-07-01T10:36:07Z

Hi Scott,

Thanks for responding. No problem about the delay...

I managed to sign up already and also submitted a patch to Sourceforge.
(the posting should show up under the ard_pangalactic SF account name).
I'm not sure if the patch format is correct - first time I'm
contributing something to SF.

Regarding incoming extended messages: The code for extracting the
extended X10 code from the USB packets and translating that to parsed
fields in a structure is already in place in the patch mentioned above.
I just don't know how to expose that info to the user mode apps. An
extra device that can be only read from might do the trick. Maybe
/dev/statusraw. The format would probably be similar to sending extended
commands. I currently just print something like this to the kernel
message queue:

Jul 1 12:31:49 mpl plusbd[4662]: received data - decoding: 40 60 e6 96
a9 a6 55 55
Jul 1 12:31:49 mpl plusbd[4662]: Decoding extended message - signal
strength: 60
Jul 1 12:31:49 mpl plusbd[4662]: received data - decoding: 40 00 6a 57
9a 5a a6 99
Jul 1 12:31:50 mpl plusbd[4662]: received data - decoding: 41 00 55 55
a9 50 00 00
Jul 1 12:31:50 mpl plusbd[4662]: Decoded extended message:
Jul 1 12:31:50 mpl plusbd[4662]: hc 6 ;
Jul 1 12:31:50 mpl plusbd[4662]: cmd 7 ;
Jul 1 12:31:50 mpl plusbd[4662]: c_u 1 ;
Jul 1 12:31:50 mpl plusbd[4662]: uc 6 ;
Jul 1 12:31:50 mpl plusbd[4662]: data 80 ;
Jul 1 12:31:50 mpl plusbd[4662]: ctype 3 ;
Jul 1 12:31:50 mpl plusbd[4662]: ecmd 8 ;
Jul 1 12:31:50 mpl plusbd[4662]: Error: Extended data not supported

I haven't had time to play with this recently. Hopefully I can get
Misterhouse to interface with the driver at some point.

/br,
Ardi

Scott Hiles wrote:

> Ardi,
>
> Somehow this message was stuck in queue and I never approved it. I was just
> checking through status of things and happened upon it.
>
> I have been very inactive in development since I broke my back this year.
> Just getting back into the swing of things now.
>
> Anyhow, if you would like to contribute your code to the drivers, the
> community would be very happy to have it and could probably improve on it.
> Join the mailing list and apply to be a developer on the project and I will
> add you to the project for you to make your changes.
>
> As for the decoder...I know that the logic in the status mechanism is
> difficult, but it all based on trying to queue things between the dev driver
> and the usermode application. It isn't until the usermode application that
> any translation is done and the raw data is spit into the status queue. The
> x10log program decodes the raw messages into readable information.
>
> Scott
>
>
> -----Original Message-----
> From: Ardian Dhrimaj [mailto:adhrimaj@...]
> Sent: Monday, May 07, 2007 9:05 PM
> To: wish-info@...
> Subject: USB Powerlinc (V1) extended codes
>
> Hi folks,
>
> I have modified the 2.x drivers for the USB Powerlinc (I have an 1132U)
> to add limited support for extended code commands (ext code 1 - for data
> /control; NOT extended data). I'd like to submit the changes for
> review/testing but am new to sourceforge in general and have no idea how.
>
> I only have a couple of LM14s (2 way lamp dimmers by X10) and that is
> all I could test with. The changes allow the user to send an extended
> command directly to a unit address:
>
> $ echo EXT 3F31 > /dev/x10/a1
>
> where 3f is the data byte, 3 is the command type, and 1 is the extended
> command itself. The data format is spelled out at
> ftp://ftp.x10.com/pub/manuals/xtc798.doc. The command above for example,
> means "Turn on immediate at 100% brightness".
>
> I did this because I use the extended commands to setup a lamp as a
> morning alarm. Turn on at minimum brightness no matter what the previous
> state, then ramp up slowly to max.
>
> I also implemented a decoder for extended code responses, but have only
> tested this with the above mentioned LM14s. Also, given the way the WISH
> drivers currently work, I have no idea how to report that status back to
> user mode applications - it just generates some prints to /var/log/messages.
>
> My work is based on Ubuntu Feisty.
>
> /br,
> Ardi
>
>
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Re: Question about Insteon PLM

2007-07-01T08:09:39Z

WSH wrote:
> This looks like an interesting little box, and one worth looking at. I
> will download the developers guide and see what it looks like. After my
> little spat with SmartHome over the licensing for the PowerLinc v2
> controllers, I have had little motivation to do anything with the
> SmartHome products.

I know the feeling but won't comment any further here.

> I just read through the license and it looks like I can do the
> development without getting into trouble. The exception is that it
> appears that I can never reference it as a SmartHome compatible device
> without their approval.

What you can't do is use Insteon in the name of your software.
Their protecting their trademark. I don't think this is too
uncommon. Bruce Perens uses Ion, which I like and I've used also.

I've had trouble programming these beasts. Smart Home keeps
changing little details about how you talk to it (grrr) but
doesn't provide those details any where (except on their dev
forums). I tried to get them to open up their docs to the
Open Source community but they would have none of that. Add to
that the increase in the price of the Dev Docs (covers the
Windows software) and I got a bit miffed with them.

Currently I'm buried in school work, I'm taking two online
courses to get another degree. I have another project that
I hope I'll get done soon and then, maybe I'll have some
free time to attack the Insteon code. I'd really like to
get my MH working with it.

--
Linux Home Automation Neil Cherry ncherry@...
http://www.linuxha.com/ Main site
http://linuxha.blogspot.com/ My HA Blog
Author of: Linux Smart Homes For Dummies

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Re: Question about Insteon PLM

2007-07-01T06:29:05Z

This looks like an interesting little box, and one worth looking at. I will download the developers guide and see what it looks like. After my little spat with SmartHome over the licensing for the PowerLinc v2 controllers, I have had little motivation to do anything with the SmartHome products.

I just read through the license and it looks like I can do the development without getting into trouble. The exception is that it appears that I can never reference it as a SmartHome compatible device without their approval.

I'll order one and see what I can get going.

Scott

From: Adam Kupsta [mailto:adam@...]
Sent: Friday, June 29, 2007 10:48 AM
To: wsh@...; ncherry@...
Subject: Question about Insteon PLM

Hi,

I’m relatively new to Linux based home automation, however would like to code a high-level application that interfaces with (preferably Wish) to control and monitor HA devices around a home.

In researching various technologies, I see more availability of products and documentation from X10 and Insteon (smarthome). Recently in my quest for the holy grail (finding an easy interface to develop for) I came across this that seems to come close to what many in the Linux HA space are looking for:

http://www.smarthome.com/2412s.html

It’s relatively inexpensive and looks pretty simple to program (all serial commands). When I went through the developer’s manual (just scroll down the page and you can get the developers PDF manual, with everything documented) there’s even interfaces (I read this as planned addons) to this device that allow it to be controlled via ethernet and RF as well. This version is RS232 only.

This got me thinking…. I’m not sure if any of you had plans to integrate / support this in your products. I’d be happy to assist where I can. From what I read about WiSH, it’s exactly what would be needed to allow other DYI selfers to integrate both X10 and Insteon.

Best regards,

Adam Kupsta

Re: USB Powerlinc (V1) extended codes

2007-07-01T06:00:50Z

Ardi,

Somehow this message was stuck in queue and I never approved it. I was just
checking through status of things and happened upon it.

I have been very inactive in development since I broke my back this year.
Just getting back into the swing of things now.

Anyhow, if you would like to contribute your code to the drivers, the
community would be very happy to have it and could probably improve on it.
Join the mailing list and apply to be a developer on the project and I will
add you to the project for you to make your changes.

As for the decoder...I know that the logic in the status mechanism is
difficult, but it all based on trying to queue things between the dev driver
and the usermode application. It isn't until the usermode application that
any translation is done and the raw data is spit into the status queue. The
x10log program decodes the raw messages into readable information.

Scott

-----Original Message-----
From: Ardian Dhrimaj [mailto:adhrimaj@...]
Sent: Monday, May 07, 2007 9:05 PM
To: wish-info@...
Subject: USB Powerlinc (V1) extended codes

Hi folks,

I have modified the 2.x drivers for the USB Powerlinc (I have an 1132U)
to add limited support for extended code commands (ext code 1 - for data
/control; NOT extended data). I'd like to submit the changes for
review/testing but am new to sourceforge in general and have no idea how.

I only have a couple of LM14s (2 way lamp dimmers by X10) and that is
all I could test with. The changes allow the user to send an extended
command directly to a unit address:

$ echo EXT 3F31 > /dev/x10/a1

where 3f is the data byte, 3 is the command type, and 1 is the extended
command itself. The data format is spelled out at
ftp://ftp.x10.com/pub/manuals/xtc798.doc. The command above for example,
means "Turn on immediate at 100% brightness".

I did this because I use the extended commands to setup a lamp as a
morning alarm. Turn on at minimum brightness no matter what the previous
state, then ramp up slowly to max.

I also implemented a decoder for extended code responses, but have only
tested this with the above mentioned LM14s. Also, given the way the WISH
drivers currently work, I have no idea how to report that status back to
user mode applications - it just generates some prints to /var/log/messages.

My work is based on Ubuntu Feisty.

/br,
Ardi

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

OT: Invitation to participate in research project

2007-06-25T03:06:32Z

Hello there

I would greatly appreciate a small amount of your time to assist with
my doctoral research at The University of Newcastle. The research
concerns open source licensing and we're seeking developers working on
Java projects. The research is supervised, ethics-approved, anonymous
and results will be freely available. Participation will also provide a
custom licensing report for your project. To learn more, please visit:

http://licensing-research.newcastle.edu.au

Thanks for reading this email, and I hope you'll consider participating.

Best regards
Ben Alex

(My apologies for being off-topic; this list will not be emailed again)

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Bug in cm11a_xcvr.c?

2007-05-11T16:57:21Z

Hello Guys,

I have installed about 35 X10 modules in my house over a year ago, so I thought it would be nice to finally make some use of them. The WiSH project seems like a nice idea, so I went ahead and installed it.

I'm new to this project so I don't know all ins and outs or any history. But I do think that the CM11 support is a bit broken: I can send X10 commands and devices respond to them, but commands sent by other devices, such as the remote control, are not detected by WiSH. The driver cm11a_xcvr does receive them, but discards them.

So I took a look at the code and I noticed that the loop in the function start 'continues' upon the reception of data because the static int function updateack doesn't return any value. Making updateack returning 0 does the job, but I don't know if that's the solution or just a quick fix because didn't have the time to get my head around this mechanism yet. What's also strange is that the static int function clearack doesn't return anything either and that it isn't actually used.

Is this a known problem? Does anybody else experience this problem?

Cheers,

Robert.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

USB Powerlinc (v1) and extended codes

2007-05-09T18:21:03Z

Hi folks,

Resending this since I sent it with the wrong orig.
address the first time:

I have modified the 2.x drivers for the USB Powerlinc
(I have an 1132U) to add limited support for extended
code commands (ext code 1 - for data /control; NOT
extended data). I'd like to submit the changes for
review/testing but am new to sourceforge in general
and have no idea how.

I only have a couple of LM14s (2 way lamp dimmers by
X10) and that is all I could test with. The changes
allow the user to send an extended command directly to
a unit address:

$ echo EXT 3F31 > /dev/x10/a1

where 3f is the data byte, 3 is the command type, and
1 is the extended command itself. The data format is
spelled out at
ftp://ftp.x10.com/pub/manuals/xtc798.doc. The command
above for example, means "Turn on immediate at 100%
brightness".

I did this because I use the extended commands to
setup a lamp as a morning alarm. Turn on at minimum
brightness no matter what the previous state, then
ramp up slowly to max.

I also implemented a decoder for extended code
responses, but have only tested this with the above
mentioned LM14s. Also, given the way the WISH drivers
currently work, I have no idea how to report that
status back to user mode applications - it just
generates some prints to /var/log/messages.

My work is based on Ubuntu Feisty.

/br,
Ardi

____________________________________________________________________________________
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.
http://farechase.yahoo.com/promo-generic-14795097

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wish-info mailing list
wish-info@...
https://lists.sourceforge.net/lists/listinfo/wish-info

Re: /dev/x10 directory disappears on system reboot

2007-03-01T05:18:24Z

Ubuntu systems do not appear to have /etc/udev/devices. Try creating the directory /etc/udev/devices and then rerun the script to create the devices. If Ubuntu honors the convention of looking for static devices in /etc/udev/devices, it will recreate your device files when the machine starts. The other option is to add a call to the script that creates the devices in your startup before the drivers are loaded.

Scott

From: wish-info-bounces@... [mailto:wish-info-bounces@...] On Behalf Of junkmail@...
Sent: Thursday, March 01, 2007 12:26 AM
To: wish-info@...
Subject: [wish-info] /dev/x10 directory disappears on system reboot

I installed wish on my ubuntu box, and have a strange problem. Every time I reboot, the /dev/x10 directory disappears, and I have to re make/make install to get it to reappear. Once I re-compile, it works fine, I can send commands, etc no prob, but when I restart the box, the folder disappears and I get this error when trying to start the daemon:

pld opening /dev/x10/.api for API Error: Unable to open device /dev/x10/.api (No such file or directory)
Am I doing something really stupid or what's the deal? (I've included the terminal output to show what I'm talking about at the bottom of this email)

My setup:
Ubuntu 2.6.17-10-server
Serial Powerlinc II (1132B) connected with a Prolific PL2303X USB-to-Serial converter

A couple other things:

1) In order to compile/install on Ubuntu, I had to install the kernel headers package:

apt-get install linux-headers-`uname -r`

I was getting this error when attempting to make:

make: *** /lib/modules/2.6.17-10-server/build: No such file or directory.  Stop.

Maybe you could add that to the FAQ's or something so others might have it there if the kernel headers aren't installed by default on their distro?

2) I have a powerlinc II serial, and the manual start commands on the webpage are wrong. You have the daemon name wrong. It's listed as /usr/sbin/pl and should be /usr/sbin/pld
Page is: http://wish.sourceforge.net/index2.html#Installation

modprobe x10
/usr/sbin/pld -device /dev/ttyS0
/usr/sbin/x10logd

-Scott J
--------------------------------------------
Here's the terminal output showing what I mean that the /dev/x10 folder seems to go missing on me with every reboot:
--------------------------------------------
root@... modprobe x10 root@... /usr/sbin/pld -device /dev/ttyUSB0 -debug pld, debug turned on OK...let's start pld opening /dev/x10/.api for API Error: Unable to open device /dev/x10/.api (No such file or directory) root@... ls /dev/x10 -bash: cd: /dev/x10: No such file or directory root@... ls CREDITS dev html kernel-patches Makefile scripts daemons example_scripts INSTALL License.txt RCS utils root@... make (cd daemons; make) make[1]: Entering directory `/usr/src/x10dev-2.1.5/daemons' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/x10dev-2.1.5/daemons' (cd utils; make) make[1]: Entering directory `/usr/src/x10dev-2.1.5/utils' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/x10dev-2.1.5/utils' (cd dev; ./make.sh) make[1]: Entering directory `/usr/src/x10dev-2.1.5/dev' make -C /lib/modules/2.6.17-10-server/build SUBDIRS=/usr/src/x10dev-2.1.5/dev modules make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-server' scripts/Makefile.build:56: kbuild: /usr/src/x10dev-2.1.5/dev/Makefile - Usage of O_TARGET := x10.ko is obsolete in 2.6. Please fix! Building modules, stage 2. MODPOST make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-server' make[1]: Leaving directory `/usr/src/x10dev-2.1.5/dev' root@... make install sh ./scripts/install.sh cp -f daemons/*d /usr/sbin/ cp -f utils/x10logd /usr/sbin/ cp -f utils/x10watch /usr/bin/ cp -f utils/nbread /usr/bin/ cp -f utils/nbecho /usr/bin/ sh ./scripts/makedev.sh Creating X10 devices in /dev/x10 with data_major=120 and control_major=121 (cd dev; ./make.sh install) make[1]: Entering directory `/usr/src/x10dev-2.1.5/dev' mkdir -p /lib/modules/2.6.17-10-server/kernel/drivers/char/x10 cp -f x10.ko /lib/modules/2.6.17-10-server/kernel/drivers/char/x10 make[1]: Leaving directory `/usr/src/x10dev-2.1.5/dev' depmod root@owfs:/dev/x10# /usr/sbin/pld -device /dev/ttyUSB0 -debug pld, debug turned on OK...let's start pld opening /dev/x10/.api for API pld starting device=/dev/x10/.api pidfile=/var/run/x10d.pid logtag=pld X10 message: src=0x4, hc=0x0, uc=0x0, cmd=0x2, f=0x0 root@owfs:/dev/x10#

-------------------------------------------------------------------------
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

/dev/x10 directory disappears on system reboot

2007-02-28T21:26:15Z

make: *** /lib/modules/2.6.17-10-server/build: No such file or directory.  Stop.

/dev/x10 directory disappears on system reboot

2007-02-28T21:24:14Z

make: *** /lib/modules/2.6.17-10-server/build: No such file or directory.  Stop.

linux/config.h

2007-01-19T18:34:19Z

Hello;

I have used wish with Fedora Core 4 and 5. I just installed Fedora Core
6. I have the latest kernel sources and the kernel headers.
Linux/config.h does not seem to be present. What is supposed to be in
it and where might I find it?

Thanks Bob Laughlin

-------------------------------------------------------------------------
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

Re: powerlinc usb and 2.6.17.1?

2007-01-13T12:17:07Z

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

Re: powerlinc usb and 2.6.17.1?

2007-01-13T11:17:06Z

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

Re: powerlinc usb and 2.6.17.1?

2007-01-13T10:05:18Z

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
>

powerlinc usb and 2.6.17.1?

2007-01-13T08:54:23Z

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

unable to build wish on suse 10.1

2006-12-17T18:07:05Z

I am attempting to build wish on a Suse 10.1 (Linux 2.6.16). I have the kernel sources loaded; when I try to do a make, I get:

make[1]: Entering directory `/usr/local/src/x10dev-2.1.5/dev'
make -C /lib/modules/2.6.16.21-0.25-default/build SUBDIRS=/usr/local/src/x10dev-2.1.5/dev modules
make[2]: Entering directory `/usr/src/linux-2.6.16.21-0.25-obj/i386/default'
make[2]: *** No rule to make target `modules'. Stop.
make[2]: Leaving directory `/usr/src/linux-2.6.16.21-0.25-obj/i386/default'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/usr/local/src/x10dev-2.1.5/dev'

Do I need to do something to my kernel sources before building wish?