Handman
Senior Member
Joined: February 02 2009
Location: United States
Online Status: Offline
Posts: 229
|
| Posted: October 06 2020 at 17:16 | IP Logged
|
|
|
I am having a scenario which is very peculiar. Powerhome freezes for 13-14 seconds after there is an outgoing X10 command on the CM17A Firecracker module attached to the serial port (with a USB to serial converter). This was never a problem on my old PC, but I installed PH on a dedicated (if slightly underpowered) PC running W10. When the outgoing X10 command is sent with the Firecracker, PH seems to freeze. Windows will indicated that PH is not responding, the outgoing PH queue pauses and the clock on PH Status freezes. Then, 13-14 seconds after the outgoing command is logged in the PH status, the command is received by the intended device, the PH clock resumes 13-14 seconds ahead of where it was frozen, the items in the queue resume, and the incoming X10 command is received in the PH status. If I change the X10 controller to some other controller besides the Firecracker, then none of this slow behavior occurs. (Unfortunately the Firecracker is far more likely to get a response from the X10 device that’s targeted). What could be causing this behavior?
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Outgoing X10 causes Powerhome to freeze
