I have been able to find one device causing this error

I have a EagleEye Motion detector set to device code M1

I know it is one the causes as shortly after i get the error I get a M1 off in the normal time when it should pass the off signal

I now am asuming based on the intermittent reports from one of devIDs that the other vllin may be PMS01 Wirless Motion Detector

has any one else come across these problems???


jason

Hi Jason,

Those should both work fine with the W800RF32 and Indigo. Could the batteries be low or are they slightly out-of-range?

Regards,
Matt

With the hawk eye it is possible but it has only been in service for a month
for the PMs01 .. It is one of three and I changed battery problem is now intermittent so I am going to change again .. range shouldn't be an issue as I have units further away

So I am going to assume power

I was having the same problem for awhile with my W800RF32, and this is the feedback I got from the manufacturuer of the product:

The problem you describe is one we hear of every now and then. So far it
has always been resolved to be outside RF interference. The X10 RF signal
is like AM radio and very venerable to interference. The W800RF32A is a
very sensitive receiver. These two factors result in some very unexpected
sources of interference. One last week turned out to be a yard light that
had been installed about the time the strange behavior started. What I
would suggest is to think back and see if anything in your household has
been added or moved to a new location. If you can't cure it this way try
relocating both the receiver and the antenna.


Good luck.

It's really weird. I came home from work today and my motion detectors weren't triggering anything. I looked at Indigo and all I saw in the logs were "undefined byte from w800rf interface". I rebooted, updated the keyspan drivers and now it only seems to work within a few feet of the antenna.

This thing has been working fine. I can't figure out what's changed to cause it to malfunction.

This has happened to me a few times. I have to believe its outside interference because it eventually goes away. Although if it is interference, I don't understand why power cycling the computer/keyspan/receiver would make any difference.

This is very strange. It only works as long as I put the wireless transmitting device within 6 inches of the antenna.

I've changed out all the cables. I've tried different locations. I've rebooted a million times. I don't know what else to try.

By the way, anyone know why I show two serial ports with this keyspan? One called KeySerial1 and one called USA19QW181P1.1.

gregjsmith wrote:By the way, anyone know why I show two serial ports with this keyspan? One called KeySerial1 and one called USA19QW181P1.1.

I don't know what is causing that to show up twice, but that might very well be related to your problem. It is as if you have 2 drivers installed, or your driver installation has become corrupt maybe?

Matt

I'm getting data from my motion detectors, it's just apparently not the right data. Perhaps someone can tell me if it's really right or not. Here's a sample from Serial Bridge.

Code: Select all

nections -- choose File->New Connection... menu item to create a new connection.

Nov 4, 2006 1:30 AM
  Loaded           settings "New Connection 1"
  Loaded           script "New Connection 1/script.scpt"
  Opening Connection "New Connection 1" using port "KeySerial1"

Nov 4, 2006 1:32 AM
  Received         60 00 3C 9E F8 C0 00 80 7E 00
  Received         FF
  Received         60 00 3C 9E F8 00 C0 80 7E 00
  Received         FF
  Received         60 00 3C 9E F8 00 C0 80
  Received         7E FF
  Sample           one byte = 96
  Sample           first byte = 0
  Sample           second byte = 60
  Sample           third byte = 158
  Sample           five character string = ¯¿
  Sample           rest of string =
  Sent             7F
  Sent             02 04 08 10 20 40
  Sent             68 65 6C 6C 6F 20 77 6F 72 6C 64
  Received         60 00 3C 9E F8 C0 00 80 7E 00
  Received         FF

Nov 4, 2006 1:32 AM
  Received         60 3C 9E F8 00 C0 80 7E 00 FF
  Received         60 3C 9E F8 00
  Received         C0 80 7E 00 FF
  Sample           one byte = 96
  Sample           first byte = 0
  Received         60 00
  Received         3C 9E F8 00
  Received         C0 80 7E 00
  Received         FF
  Received         60 00
  Received         3C 9E F8 00 C0 80 7E 00 FF
  Received         60 00
  Received         3C 9E F8 00
  Received         C0 80 7E 00
  Received         FF
  Sample           second byte = 60
  Sample           third byte = 158
  Sample           five character string = ¯¿
  Sample           rest of string =
  Sent             7F
  Sent             02 04 08 10 20 40
  Sent             68 65 6C 6C 6F 20 77 6F 72 6C 64

Nov 4, 2006 1:33 AM
  Received         60 00
  Received         3C 9E F8 00 C0 80 7E 00 FF
  Received         60 3C 9E F8 00
  Received         C0 00 80 7E 00 FF
  Received         60 00
  Received         3C 9E F8 00
  Received         C0 80 7E 00
  Sample           one byte = 96
  Sample           first byte = 0
  Received         FF
  Sample           second byte = 60
  Sample           third byte = 158
  Sample           five character string = ¯
  Sample           rest of string =
  Sent             7F
  Sent             02 04 08 10 20 40
  Sent             68 65 6C 6C 6F 20 77 6F 72 6C 64
  Received         60 3C 9E F8 00
  Received         C0 00
  Received         80 7E 00
  Received         FF

Set your Serial Bridge connection settings to 4800 baud. And what house/unit code is your motion detector using so that I can compare your output to what I'm seeing?

Regards,
Matt

My motion detectors are either on A or M, this is most likely from a "A" house code

How bizarre. I slightly relocated it in the equipment closet. The thing is picking up every signal and I haven't even installed the antenna or coax cable.