Author |
|
device Newbie
Joined: May 26 2009
Online Status: Offline Posts: 33
|
Posted: January 16 2012 at 13:33 | IP Logged
|
|
|
Recently upgraded my FitPC2 (Atom dual core) to 2.1.4. Did some electrical work and have noticed that the GUI becomes unresponsive during insteon timeout to the unreadable devices. It seems to retry after about 1 minute and queued GUI interactions get processed at the retry. I'd guess this is a windows message processing or locking issue inside PH but it could be a flaky PLM. I am not a windows app person but I suspect PH internal because if I reboot during the retry perios while the GUI is stalled PH reacts normally and exits. I assume the reboot notification treavels a different route from the GUI messages. Has anyone seen this?
Thanks!
D
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 16 2012 at 17:13 | IP Logged
|
|
|
D,
Can you post some screenshots of your eventlog and Insteon Explorer documenting the Insteon timeouts. A normal Insteon timeout shouldnt hang the GUI (could definitely hang the execution queue) so Im wondering if something else is going on that Im not expecting.
Thanks,
Dave.
|
Back to Top |
|
|
device Newbie
Joined: May 26 2009
Online Status: Offline Posts: 33
|
Posted: January 17 2012 at 00:59 | IP Logged
|
|
|
I said GUI because in the interval prior to the timeout message is displayed nothing in the GUI works - scrollbars, repaint. checkboxes, etc.
D
|
Back to Top |
|
|
device Newbie
Joined: May 26 2009
Online Status: Offline Posts: 33
|
Posted: February 01 2012 at 14:46 | IP Logged
|
|
|
Dave,
I decided to try replacing the PLM. Now after a couple days with the new PLM the timeout problem has disapeared and overall reliability of communication has improved. I guess it was just a flaky PLM after all.
Thanks for your time and effort!
D
|
Back to Top |
|
|