Posts: 237
Threads: 41
Joined: Sep 2006
Reputation:
0
Thanks Chiu, - that was quick! :-)
New firmware applied, will observe & report back.
Will leave the KP reset every hour in for now just to validate the firmware fix, in a day or two if there\'s no more occurrences of the wrong text problem, I\'ll remove the KP reset & see how the \'blank LCD\' issue behaves....
Many Thanks!
Paul G.
Posts: 237
Threads: 41
Joined: Sep 2006
Reputation:
0
Think it\'s safe to say this firmware has fixed it :-)
Several days now, and I haven\'t observed a single instance of the wrong text message appearing on any keypad.
I\'m still doing the hourly reset of the KP06, so I\'m not sure what the current state of affairs with the blank LCD problem is. Will remove the reset & report back in a few more days.
Posts: 5,941
Threads: 868
Joined: Apr 2006
Reputation:
2
So did you remove the reset on the KP06? Are they still having the blank problem?
Posts: 237
Threads: 41
Joined: Sep 2006
Reputation:
0
Hi Chiu.
Actually I left the hourly reset in place, since I\'ve gotten used to it and I kinda like it beeping on the hour every hour - obviously I could set an hourly response to do stuff like that, but in truth it *is* still having the problem of the display going blank intermittently... even with the hourly reset, I still occasionally notice it has a blank screen now & then.
Also, just last week, one evening I was sitting on the sofa watching TV when Comfort suddenly made an alert... I assumed it was a \"line cut\" fault, as the Telco do occasionally have problems from time to time so I ignored it until the next day when I noticed the blank LCD, again, I left it assuming the next hourly reset would correct it. When, after the hour had rolled over, and no beep was heard I took a closer look... the keypad was *utterly* dead, I removed the bezel & removed both the LCD and the key modules from the connectors, - that normally causes a tamper alarm, but it did not, and upon reassembly it was still dead.
I decided therefore to do a manual keypad reset from Comfigurator, but it was unresponsive... I did a rescan for modules, and it had disappeared from the list of detected keypads, and the log showed a communication failure... that in fact was what that alert was the previous evening, not a line cut at all...
In the end, I had to do a complete power cycle of keypad (I actually power cycled comfort to achieve this, since it was actually easier to do that), and the keypad came back to life, and has been behaving ever since, although it is a tad worrying that the problems with this particular keypad seems to have escalated... if it had happened whilst I was away & the system was armed, it might have been awkward...
