W800RF32 problem

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

W800RF32 problem

Alfredo Quesada
Hi

I'm newbie with X10 technology, but I'm working with
W800RF32 receiver, and MS90/MS13E motion sensors.

I've installed MisterHouse at my linux machine and
after taking a look at a few example codes I've added
2 lines to mh.ini:
W800_module = X10_W800
W800_port = /dev/ttyS0 (it's the right one)

After this I've launched the program by typing:
mh x10_rf_relay.pl

The idea was to see X10 commands received from the
motion sensors (at this point I was using MS90) and
I'm receiveing this:
02/07/06 11:46:56 AM x10_rf_relay will relay these
housecode: ALL
Creating Tk Command menu
Creating Tk Items menu
Creating Tk Groups menu
Setting tk geometry to +0+0
02/07/06 11:46:59 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:46:59 AM W800: bad checksum (attempting to
recover)
02/07/06 11:47:00 AM: Saving object states ... done
02/07/06 11:47:02 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:47:09 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:47:13 AM W800: flushing incomplete data:
fc
02/07/06 11:47:13 AM W800: failed to recovered from
bad checksums (count=3)
02/07/06 11:48:00 AM: Saving object states ... done
02/07/06 11:48:35 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:35 AM W800: bad checksum (attempting to
recover)
02/07/06 11:48:42 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:44 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:46 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:46 AM W800: failed to recovered from
bad checksums (count=4)
02/07/06 11:48:50 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:50 AM W800: bad checksum (attempting to
recover)
02/07/06 11:48:52 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:56 AM W800: flushing incomplete data:
fffe
02/07/06 11:48:56 AM W800: failed to recovered from
bad checksums (count=2)
02/07/06 11:48:58 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:58 AM W800: bad checksum (attempting to
recover)
02/07/06 11:49:00 AM: Saving object states ... done
02/07/06 11:49:02 AM W800: flushing incomplete data:
fffffa
.........

When trying to read incoming raw data from the serial
port (using cutecom) I was receiving strange packets,
and as far as I currently know X10 commands appear as
32 bit frames (after decoding), being 16 of them the
inverse of the rest (I haven't found anything about
some kind of "control" frames in X10 protocol
specification..).

So checking the environment I saw incoming raw data
even after powering off motion sensors. I don't know
if this could be the (unknown for me) control frames I
mentioned before, but I tried to find any other near
RF devices that would be sending data (433 MHz). I
finally found an old logitech wireless keyboard, and
it seems that old models use this frecuency band, so
maybe I'm receiving data from this keyboard and is
breaking "right frames" (the problem here is that this
keyboard if from a neighbor office, so I can't switch
it off..).

What do you think about it?
When receiving raw data at the serial port, should I
only see 32 bit sequences? or maybe the complete
undecoded stream?

Thanks in advance

Regards


__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/ 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

Reply | Threaded
Open this post in threaded view
|

RE: W800RF32 problem

Jim Serack
Alfredo,

Mine just sends a nice neat packet when it gets a signal from the sensor. I
don't think there is a checksum in the X10 RF security signal - but there
are byte compliments.
I have the module declaration and rf relay defined the same.

I assume that Misterhouse is running as root or has appropriate permissions
for /dev/ttyS0

If you really think it is RF interference - why not shield the antenna and a
module in some grounded metal box (like the fridge, oven, microwave) and see
if the problem goes away. If it does - then you would be looking at making a
directional antenna to ignore you neighbors keyboard.

Jim


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Alfredo
Quesada
Sent: February 7, 2006 6:30 AM
To: [hidden email]
Subject: [mh] W800RF32 problem


Hi

I'm newbie with X10 technology, but I'm working with
W800RF32 receiver, and MS90/MS13E motion sensors.

I've installed MisterHouse at my linux machine and
after taking a look at a few example codes I've added
2 lines to mh.ini:
W800_module = X10_W800
W800_port = /dev/ttyS0 (it's the right one)

After this I've launched the program by typing:
mh x10_rf_relay.pl

The idea was to see X10 commands received from the
motion sensors (at this point I was using MS90) and
I'm receiveing this:
02/07/06 11:46:56 AM x10_rf_relay will relay these
housecode: ALL
Creating Tk Command menu
Creating Tk Items menu
Creating Tk Groups menu
Setting tk geometry to +0+0
02/07/06 11:46:59 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:46:59 AM W800: bad checksum (attempting to
recover)
02/07/06 11:47:00 AM: Saving object states ... done
02/07/06 11:47:02 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:47:09 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:47:13 AM W800: flushing incomplete data:
fc
02/07/06 11:47:13 AM W800: failed to recovered from
bad checksums (count=3)
02/07/06 11:48:00 AM: Saving object states ... done
02/07/06 11:48:35 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:35 AM W800: bad checksum (attempting to
recover)
02/07/06 11:48:42 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:44 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:46 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:46 AM W800: failed to recovered from
bad checksums (count=4)
02/07/06 11:48:50 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:50 AM W800: bad checksum (attempting to
recover)
02/07/06 11:48:52 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:56 AM W800: flushing incomplete data:
fffe
02/07/06 11:48:56 AM W800: failed to recovered from
bad checksums (count=2)
02/07/06 11:48:58 AM W800: bad initial checksum:
11111111 11111111 11111111 11111111
02/07/06 11:48:58 AM W800: bad checksum (attempting to
recover)
02/07/06 11:49:00 AM: Saving object states ... done
02/07/06 11:49:02 AM W800: flushing incomplete data:
fffffa
.........

When trying to read incoming raw data from the serial
port (using cutecom) I was receiving strange packets,
and as far as I currently know X10 commands appear as
32 bit frames (after decoding), being 16 of them the
inverse of the rest (I haven't found anything about
some kind of "control" frames in X10 protocol
specification..).

So checking the environment I saw incoming raw data
even after powering off motion sensors. I don't know
if this could be the (unknown for me) control frames I mentioned before, but
I tried to find any other near RF devices that would be sending data (433
MHz). I finally found an old logitech wireless keyboard, and it seems that
old models use this frecuency band, so maybe I'm receiving data from this
keyboard and is breaking "right frames" (the problem here is that this
keyboard if from a neighbor office, so I can't switch it off..).

What do you think about it?
When receiving raw data at the serial port, should I
only see 32 bit sequences? or maybe the complete
undecoded stream?

Thanks in advance

Regards


__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/ 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
________________________________________________________
To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
<a href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
________________________________________________________
To unsubscribe from this list, go to: <a href="http://sourceforge.net/mail/?group_id65">http://sourceforge.net/mail/?group_id65

Reply | Threaded
Open this post in threaded view
|

Re: W800RF32 problem

Charles Sullivan
In reply to this post by Alfredo Quesada

Are you sure the MH module you are using is the correct one
for the W800RF32A ?  There was/is an older W800 receiver which
reported the bytes differently.

Try this stand-alone shell script to verify that the WR800RF32 is
reporting correctly.
------------- w800rf32a.sh --------------------------
#! /bin/bash

# Display output (in hex) from WGL W800RF32A RF receiver

if [ $# -ne 1 ] ; then
  echo "Usage: $0 <serial port>"
  exit
fi

echo "Reading from port: "$1
stty -F $1 4800 cs8 raw cread clocal -parenb -cstopb -echo
cat $1 | xxd -g 1 -c 4
--------------- end --------------------------------

Transmitting A1 On and A1 Off from a PalmPad or other
standard X10 RF remote should display:

$ w800rf32a.sh /dev/ttyS0
Reading from port: /dev/ttyS0
0000000: 60 9f 00 ff  `...
0000004: 60 9f 00 ff  `...
0000008: 60 9f 00 ff  `...
000000c: 60 9f 00 ff  `...
0000010: 60 9f 00 ff  `...
0000014: 60 9f 00 ff  `...
0000018: 60 9f 20 df  `. .
000001c: 60 9f 20 df  `. .
0000020: 60 9f 20 df  `. .
0000024: 60 9f 20 df  `. .
0000028: 60 9f 20 df  `. .
000002c: 60 9f 20 df  `. .

where the actual bytes sent to the serial port are the
"60 9f 00 ff" displayed. (A quick tap on a PalmPad button
repeats the RF transmission 6 times.)  Bytes 2 and 4 are
the complements of 1 and 3.

Here are the bytes for Lights On and Lights Off from an
X-10 KR10A Security Remote with secure ID = 0x2c.
The high nybble of byte 2 is not complemented as it
would be for standard X10 RF.

0000018: 2c 23 46 b9  ,#F.
000001c: 2c 23 46 b9  ,#F.
0000020: 2c 23 46 b9  ,#F.
0000024: 2c 23 46 b9  ,#F.
0000028: 2c 23 46 b9  ,#F.
000002c: 2c 23 46 b9  ,#F.
0000030: 2c 23 46 b9  ,#F.
0000034: 2c 23 c6 39  ,#.9
0000038: 2c 23 c6 39  ,#.9
000003c: 2c 23 c6 39  ,#.9
0000040: 2c 23 c6 39  ,#.9
0000044: 2c 23 c6 39  ,#.9
0000048: 2c 23 c6 39  ,#.9
000004c: 2c 23 c6 39  ,#.9


Regards,
Charles Sullivan

On Tue, 07 Feb 2006 16:44:01 -0800
[hidden email] wrote:

> Date: Tue, 7 Feb 2006 05:29:43 -0600 (CST)
> From: Alfredo Quesada <[hidden email]>
> To: [hidden email]
> Subject: [mh] W800RF32 problem
> Reply-To: [hidden email]
>
> Hi
>
> I'm newbie with X10 technology, but I'm working with
> W800RF32 receiver, and MS90/MS13E motion sensors.
>
> I've installed MisterHouse at my linux machine and
> after taking a look at a few example codes I've added
> 2 lines to mh.ini:
> W800_module = X10_W800
> W800_port = /dev/ttyS0 (it's the right one)
>
> After this I've launched the program by typing:
> mh x10_rf_relay.pl
>
> The idea was to see X10 commands received from the
> motion sensors (at this point I was using MS90) and
> I'm receiveing this:
> 02/07/06 11:46:56 AM x10_rf_relay will relay these
> housecode: ALL
> Creating Tk Command menu
> Creating Tk Items menu
> Creating Tk Groups menu
> Setting tk geometry to +0+0
> 02/07/06 11:46:59 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:46:59 AM W800: bad checksum (attempting to
> recover)
> 02/07/06 11:47:00 AM: Saving object states ... done
> 02/07/06 11:47:02 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:47:09 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:47:13 AM W800: flushing incomplete data:
> fc
> 02/07/06 11:47:13 AM W800: failed to recovered from
> bad checksums (count=3)
> 02/07/06 11:48:00 AM: Saving object states ... done
> 02/07/06 11:48:35 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:35 AM W800: bad checksum (attempting to
> recover)
> 02/07/06 11:48:42 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:44 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:46 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:46 AM W800: failed to recovered from
> bad checksums (count=4)
> 02/07/06 11:48:50 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:50 AM W800: bad checksum (attempting to
> recover)
> 02/07/06 11:48:52 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:56 AM W800: flushing incomplete data:
> fffe
> 02/07/06 11:48:56 AM W800: failed to recovered from
> bad checksums (count=2)
> 02/07/06 11:48:58 AM W800: bad initial checksum:
> 11111111 11111111 11111111 11111111
> 02/07/06 11:48:58 AM W800: bad checksum (attempting to
> recover)
> 02/07/06 11:49:00 AM: Saving object states ... done
> 02/07/06 11:49:02 AM W800: flushing incomplete data:
> fffffa
> .........
>
> When trying to read incoming raw data from the serial
> port (using cutecom) I was receiving strange packets,
> and as far as I currently know X10 commands appear as
> 32 bit frames (after decoding), being 16 of them the
> inverse of the rest (I haven't found anything about
> some kind of "control" frames in X10 protocol
> specification..).
>
> So checking the environment I saw incoming raw data
> even after powering off motion sensors. I don't know
> if this could be the (unknown for me) control frames I
> mentioned before, but I tried to find any other near
> RF devices that would be sending data (433 MHz). I
> finally found an old logitech wireless keyboard, and
> it seems that old models use this frecuency band, so
> maybe I'm receiving data from this keyboard and is
> breaking "right frames" (the problem here is that this
> keyboard if from a neighbor office, so I can't switch
> it off..).
>
> What do you think about it?
> When receiving raw data at the serial port, should I
> only see 32 bit sequences? or maybe the complete
> undecoded stream?
>
> Thanks in advance
>
> Regards
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

Reply | Threaded
Open this post in threaded view
|

Re: W800RF32 problem

Alfredo Quesada
Well, as I was thinking there's another device using
the 433 MHz band near me. I tried to do tests in
another place far enough and reading raw data from the
serial port (using cutecom) I can see the incoming
messages :D

I'm working with MS13E and MS90 motion sensors from
Marmitek, and the first one seems to send ON/OFF
standard x10 commands. You also can change its values
for house/unit-code manually at the device. But MS90
works different.. It selects automatically its own
codes "randomly" when powering it on, and is also
using own format messages (without being 1st and 3rd
bytes the complements of 2nd and 4th).
The most interesting for me here should be being able
to change the codes from the central station with x10
commands, not manually/automatically at the devices.
Is there any way to do it?

help would be appreciated

thx in advance

regards

 --- Charles Sullivan <[hidden email]>
escribió:

>
> Are you sure the MH module you are using is the
> correct one
> for the W800RF32A ?  There was/is an older W800
> receiver which
> reported the bytes differently.
>
> Try this stand-alone shell script to verify that the
> WR800RF32 is
> reporting correctly.
> ------------- w800rf32a.sh
> --------------------------
> #! /bin/bash
>
> # Display output (in hex) from WGL W800RF32A RF
> receiver
>
> if [ $# -ne 1 ] ; then
>   echo "Usage: $0 <serial port>"
>   exit
> fi
>
> echo "Reading from port: "$1
> stty -F $1 4800 cs8 raw cread clocal -parenb -cstopb
> -echo
> cat $1 | xxd -g 1 -c 4
> --------------- end --------------------------------
>
> Transmitting A1 On and A1 Off from a PalmPad or
> other
> standard X10 RF remote should display:
>
> $ w800rf32a.sh /dev/ttyS0
> Reading from port: /dev/ttyS0
> 0000000: 60 9f 00 ff  `...
> 0000004: 60 9f 00 ff  `...
> 0000008: 60 9f 00 ff  `...
> 000000c: 60 9f 00 ff  `...
> 0000010: 60 9f 00 ff  `...
> 0000014: 60 9f 00 ff  `...
> 0000018: 60 9f 20 df  `. .
> 000001c: 60 9f 20 df  `. .
> 0000020: 60 9f 20 df  `. .
> 0000024: 60 9f 20 df  `. .
> 0000028: 60 9f 20 df  `. .
> 000002c: 60 9f 20 df  `. .
>
> where the actual bytes sent to the serial port are
> the
> "60 9f 00 ff" displayed. (A quick tap on a PalmPad
> button
> repeats the RF transmission 6 times.)  Bytes 2 and 4
> are
> the complements of 1 and 3.
>
> Here are the bytes for Lights On and Lights Off from
> an
> X-10 KR10A Security Remote with secure ID = 0x2c.
> The high nybble of byte 2 is not complemented as it
> would be for standard X10 RF.
>
> 0000018: 2c 23 46 b9  ,#F.
> 000001c: 2c 23 46 b9  ,#F.
> 0000020: 2c 23 46 b9  ,#F.
> 0000024: 2c 23 46 b9  ,#F.
> 0000028: 2c 23 46 b9  ,#F.
> 000002c: 2c 23 46 b9  ,#F.
> 0000030: 2c 23 46 b9  ,#F.
> 0000034: 2c 23 c6 39  ,#.9
> 0000038: 2c 23 c6 39  ,#.9
> 000003c: 2c 23 c6 39  ,#.9
> 0000040: 2c 23 c6 39  ,#.9
> 0000044: 2c 23 c6 39  ,#.9
> 0000048: 2c 23 c6 39  ,#.9
> 000004c: 2c 23 c6 39  ,#.9
>
>
> Regards,
> Charles Sullivan
>
> On Tue, 07 Feb 2006 16:44:01 -0800
> [hidden email]
> wrote:
>
> > Date: Tue, 7 Feb 2006 05:29:43 -0600 (CST)
> > From: Alfredo Quesada <[hidden email]>
> > To: [hidden email]
> > Subject: [mh] W800RF32 problem
> > Reply-To: [hidden email]
> >
> > Hi
> >
> > I'm newbie with X10 technology, but I'm working
> with
> > W800RF32 receiver, and MS90/MS13E motion sensors.
> >
> > I've installed MisterHouse at my linux machine and
> > after taking a look at a few example codes I've
> added
> > 2 lines to mh.ini:
> > W800_module = X10_W800
> > W800_port = /dev/ttyS0 (it's the right one)
> >
> > After this I've launched the program by typing:
> > mh x10_rf_relay.pl
> >
> > The idea was to see X10 commands received from the
> > motion sensors (at this point I was using MS90)
> and
> > I'm receiveing this:
> > 02/07/06 11:46:56 AM x10_rf_relay will relay these
> > housecode: ALL
> > Creating Tk Command menu
> > Creating Tk Items menu
> > Creating Tk Groups menu
> > Setting tk geometry to +0+0
> > 02/07/06 11:46:59 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:46:59 AM W800: bad checksum
> (attempting to
> > recover)
> > 02/07/06 11:47:00 AM: Saving object states ...
> done
> > 02/07/06 11:47:02 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:47:09 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:47:13 AM W800: flushing incomplete
> data:
> > fc
> > 02/07/06 11:47:13 AM W800: failed to recovered
> from
> > bad checksums (count=3)
> > 02/07/06 11:48:00 AM: Saving object states ...
> done
> > 02/07/06 11:48:35 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:35 AM W800: bad checksum
> (attempting to
> > recover)
> > 02/07/06 11:48:42 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:44 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:46 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:46 AM W800: failed to recovered
> from
> > bad checksums (count=4)
> > 02/07/06 11:48:50 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:50 AM W800: bad checksum
> (attempting to
> > recover)
> > 02/07/06 11:48:52 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:56 AM W800: flushing incomplete
> data:
> > fffe
> > 02/07/06 11:48:56 AM W800: failed to recovered
> from
> > bad checksums (count=2)
> > 02/07/06 11:48:58 AM W800: bad initial checksum:
> > 11111111 11111111 11111111 11111111
> > 02/07/06 11:48:58 AM W800: bad checksum
> (attempting to
> > recover)
> > 02/07/06 11:49:00 AM: Saving object states ...
> done
> > 02/07/06 11:49:02 AM W800: flushing incomplete
> data:
> > fffffa
> > .........
> >
> > When trying to read incoming raw data from the
> serial
> > port (using cutecom) I was receiving strange
> packets,
> > and as far as I currently know X10 commands appear
> as
> > 32 bit frames (after decoding), being 16 of them
> the
> > inverse of the rest (I haven't found anything
> about
> > some kind of "control" frames in X10 protocol
> > specification..).
> >
> > So checking the environment I saw incoming raw
> data
> > even after powering off motion sensors. I don't
> know
> > if this could be the (unknown for me) control
> frames I
> > mentioned before, but I tried to find any other
> near
> > RF devices that would be sending data (433 MHz). I
> > finally found an old logitech wireless keyboard,
> and
> > it seems that old models use this frecuency band,
> so
> > maybe I'm receiving data from this keyboard and is
>
=== message truncated ===


__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/ 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

Reply | Threaded
Open this post in threaded view
|

Re: W800RF32 problem

David Mark
In reply to this post by Alfredo Quesada
Alfredo Quesada <freddy2_tiny <at> yahoo.com> writes:

>
> Hi
>
> I'm newbie with X10 technology, but I'm working with
> W800RF32 receiver, and MS90/MS13E motion sensors.
>
> I've installed MisterHouse at my linux machine and
> after taking a look at a few example codes I've added
> 2 lines to mh.ini:
> W800_module = X10_W800

There is also a W800RF module.  That is the one I used.

> W800_port = /dev/ttyS0 (it's the right one)
>
> After this I've launched the program by typing:
> mh x10_rf_relay.pl

Don't know anything about this module.  But I can tell you that the current
w800rf module is broken.  The logic used to validate packets is wrong.  It
works for some HC/UC addresses but not others.  The various other devices like
the security remote(s), universal remotes are unusable.  I fixed all of the
bugs here as all of my devices work, but I had to create serial packages for
them (which flies in the face of current mh convention for RF devices.)  I
don't remember why I had to do this, but I couldn't get it to work any other
way.  If anyone wants the updated code with the various packages, I will post
them.  Maybe someone can compare the updated logic to the current module(s)
and update them.  I just don't have the time right now.

I should also point out that mh dupe handling is broken for RF.  The whole
thing with multikey and multireceive (or whatever) is in need of a rewrite.  
For one, there is no way for RF and serial controllers to share the same hash
for dupes and multi-key commands. Dupes need to look at all previously
received data.  As for combining multiple keys like A1 (pause) AK, that is not
a serial issue.  I will fix this soon as I am sick of having to use timers to
throw out dupes.









-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365