HouseBot

First of all, Merry Christmas to all of you. I just set-up the Generic Serial Interface to connect Housebot to my DSC security panel. I am using it just to read information (door sensors) and not to pass any commands since the security logic is in Housebot. In theory it was working fine but then Housebot started to go to 100% CPU or just crashes. I close Housebot and open it again and it runs OK for another 10-30 minutes. I have re-installed Housebot and even did a clean OS installation in the PC but I am still seeing the problem. When tracing the Interface I get in the trace files something like this:

Received character [6] - Int [54]
Received character [5] - Int [53]
Received character [0] - Int [48]
Received character [ ] - Int [13]
Received
Reading Data Complete
WaitCommEvent returned ERROR_IO_PENDING
GetCommMask returned [9]
Reading Data from Port
Reading Data complete
WaitCommEvent returned ERROR_IO_PENDING
Sending Subscription Notification for list [Generic Serial Data Received]

Any Clues? I have seen old posts (from 2004) talking about a similar issue but didnt't find a solution there. I just want to know if this is something that can be solved or if there is a workaround.

Saludos,

Victor

Victor,

What version of HouseBot are you running?

Also, when the CPU goes to 100%, is the hardware interface trace constantly accumulating messages, or is what you posted just the last message shown?

I have version 2.22 and no, the hardware interface is not constantly accumulating messages. Actually, it doesn't go up to 100% CPU exactly when it receives data but shortly ater that. Last night I changed the flow control settings of the com port and at least it has been running for almost 24 hours without problems although in the trace files I keep seeing the same errors.

Saludos,

Victor

Unless you are getting actual errors in the error log, you may be ok now. The ERROR_IO_PENDING message is not really an error. It's just a way for the Win32 serial interface to communicate back to the software that there is more data to read. The plugin handles the fact that there is more data, and traces the response which may appear as an error.