I'm completely stumped as to why my VRC0P will lock up and quit working every 2-3 months. To fix it, I need to unplug the VRC0P from the outlet, then plug it back in. I actually replaced my RZC0P thinking it was the issue, but apparently it wasn't because the new VRC0P is doing the same thing.
I'm using a custom built RS232 driver. The driver works 100% of the time except when, after 2-3 months, it will all of a sudden quit communicating with the VRC0P. I know it is not my home automation system causing the problem: the port stays open and port spy shows the commands being sent (but shows no response from the VRC0P
). Also, the green flashing light on the VRC0P goes out completely during this unresponsive period leading me to suspect the VRC0P.
Does anyone else have this issue with the VRC0P or the RZC0P? Any fixes? The only fix I can think of is plugging it into an X10 appliance module and having the VRC0P driver toggle the power going to the VRC0P when it becomes unresponsive.
Other thoughts: Is there some special protocol command that I could periodically send to clear the VRC0P's cache? If so, it's not documented in the protocol manual
Is it possible that there is a voltage transient over the serial port causing the VRC0P to lock up?
Any help or ideas much appreciated :blush:
PS: The driver was written for a PC based home automation system that uses free PC software called Premise.
The latest version of the VRC0P driver is found at the link below (you can view the code in notepad or better yet by importing the file as a module using Premise Builder):
http://www.cocoontech.com/forums/index.php...0&start=150
I'm using a custom built RS232 driver. The driver works 100% of the time except when, after 2-3 months, it will all of a sudden quit communicating with the VRC0P. I know it is not my home automation system causing the problem: the port stays open and port spy shows the commands being sent (but shows no response from the VRC0P

Does anyone else have this issue with the VRC0P or the RZC0P? Any fixes? The only fix I can think of is plugging it into an X10 appliance module and having the VRC0P driver toggle the power going to the VRC0P when it becomes unresponsive.
Other thoughts: Is there some special protocol command that I could periodically send to clear the VRC0P's cache? If so, it's not documented in the protocol manual

Any help or ideas much appreciated :blush:
PS: The driver was written for a PC based home automation system that uses free PC software called Premise.
The latest version of the VRC0P driver is found at the link below (you can view the code in notepad or better yet by importing the file as a module using Premise Builder):
http://www.cocoontech.com/forums/index.php...0&start=150