Author |
|
patrickm Senior Member
Joined: February 22 2007 Location: United States
Online Status: Offline Posts: 188
|
Posted: June 21 2007 at 11:09 | IP Logged
|
|
|
My powerhome behaviour became erratic yesterday morning and was very slow executing insteon commands. I then looked at the SDM log.
PLC:getlinks=false,failed due to corrupted database
ui:getlinks
uifinished:getlinks
This process was repeating over and over again. So the slow response time made sense. I tried to clear the PLC database from the Insteon Explorer window but had no success. I then tried to download the core application to the PLC with no change. I then tried using the SALAD IDE and it read the database with no problem. I then went into Houselinc and ran the PLC diagnostics which came back as PLC app invalid. I downloaded the PLC app and it came back with no errors. So I went back to Powerhome and it still had database errors coming back in the SDM log. I tried to clear the database and it finally cleared. I then added the device IDs to the PLC and it seems to be behaving better but not completely normal. I still have a couple of seconds of delay between insteon commands run within macros that still cannot be explained. Watching an hourglass for a 6 line macro seems very wrong. Non Insteon macros seem to run at normal rate of execution.
It seems like Powerhome, SALAD, and Houselinc have different methods of interacting with the PLC. I am wondering if there is any way of being able to recover from this PLC condition automatically in Powerhome. I thought the upcoming PLM would get rid of all of these PLC reliability issues but it sounds like it has a database as well.
Any ideas out there?
|
Back to Top |
|
|
cainemutiny Newbie
Joined: August 12 2010
Online Status: Offline Posts: 1
|
Posted: August 12 2010 at 00:54 | IP Logged
|
|
|
Hi Patrick,
Did you ever find a solution to this problem? I'm getting the same error. Thanks
|
Back to Top |
|
|
patrickm Senior Member
Joined: February 22 2007 Location: United States
Online Status: Offline Posts: 188
|
Posted: August 12 2010 at 17:12 | IP Logged
|
|
|
The solution at the time was using the SALAD IDE to reinitialize the PLC.
My software and computer hardware has changed significantly since then. I haven't had any issues with the same PLC with Windows 7 Ultimate and the Quad Core box that Insteon Explorer couldn't resolve so far.
I would try to resolve the problem with Insteon Explorer if you can. Download the Core Application if it's a PLC and clear the database. Pay attention to the Insteon Raw Log window. Watching the response of the PLC in terms of speed and data is pretty helpful in determining if the PLC or other Insteon hardware is functioning normally or if it's time for another RMA...
The SALAD IDE is in the Insteon SDK. Don't waste your money on the Insteon SDK.
-Patrick
|
Back to Top |
|
|