W800 and MS13 Motion Sensor buffering

[derek]

Can anybody please offer some advice on the following situation.



I have about 10 MS13 motion sensors that all communicate fairly quickly with Housebot through a W800 RS232 wireless transceiver.



However there are times when there is significant delay for the command to arrive from the MS13 motion sensor to Housebot. I am watching the X10 Controller Device log to see the commands arriving at Housebot as Composite Property commands.



Is this occurring because multiple MS13s are sending commands at the same time and they are being buffered before appearing in the X10 Controller log?



Another thing I notice is that if Housebot is shut down for a period of time when it restarts all the motion sensor triggers that occurred while Housebot was shut down then appear in the X10 Controller log. This can sometimes be hundreds of triggers and it can take Housebot 5-10 minutes to catch up during which time lights are turning on and off all over the place. Where are these commands being buffered? Is Windows buffering RS232 data until Housebot restarts? If so can this be changed?



Any help would be appreciated.

[ScottBot]

Another thing I notice is that if Housebot is shut down for a period of time when it restarts all the motion sensor triggers that occurred while Housebot was shut down then appear in the X10 Controller log. This can sometimes be hundreds of triggers and it can take Housebot 5-10 minutes to catch up during which time lights are turning on and off all over the place. Where are these commands being buffered? Is Windows buffering RS232 data until Housebot restarts? If so can this be changed?

When HouseBot connects to the W800 on startup, it purges the communications port, so it shouldn't get anything left in the queue. However, the W800 may very well be buffering the events internally and then unloading them at the next connection.



I'm not aware of any way to tell the W800 to clear it's buffer, although a way may exist.