01-04-2007, 09:33 AM
Comfort G2 Week/5.054, 1 x KP03, 1 x KP04, 1 x DP03, Comfigurator 2.1.2(beta), various UCMs/RIOs/X10/etc.
Did some minor changes in Comfigurator and downloaded. After the reset, the KPs beeped and \"communication failure keypad 1\" was reported on the KP04 display. Could find no problems, reset Comfort numerous times, downloaded the previous CCL and others, recycled power completely, and so on, to no avail. Then I noticed that announcements were being made on the doorpad so anyone could hear when the system is armed/disarmed/zones bypassed/etc., despite the option being turned off in Comfigurator. Downloaded a new CCL with 2 KP\'s & no DP\'s setup - DP still broadcasted everything - had visions of burglars waiting for \"Security off\" to make their entrance! (I also have hourly time announcements to help me keep track of time so was wondering if passers-by thought that this was a new neighbourhood service!
Was about to disconnect voice to the DP when I noticed that the key on the DP was depressed slightly on one side - touched it and all the problems went away. And yes, if one depresses it off centre this can be repeated. But a spare DP doesn\'t exhibit this stuck key problem, so probably not a Comfort problem, although the spare one hasn\'t been exposed to the elements. Will have to open the installed one to see what I can find out.
But strangely, the comms problem only occurred on downloading a new CCL, not after the key was pressed by the last visitor (as far as I know, at least 6 or 7 hours earlier). And why would it report comms failure on \"keypad 1\"? I think there\'s no \"key stuck\"
in the vocab, but is communication failure the correct/logical problem to report? If so, then at least it should say doorpad 1 and not keypad 1??
Not a serious problem, now that I\'m aware of it, but it would be interesting to hear an explanation for this behaviour. And perhaps a new version of Comfort could detect non-release of the key and turn off voice/mic till the key is released/pressed again?
This is the second time that this has happened. I don\'t remember the finer details of the previous occurrence, but it was immediately after I installed Comfigurator 2.1.2(beta). I was about to re-install 2.1.0 when the problem suddenly disappeared. Perhaps some vibration caused the key to release but I can\'t be absolutely sure that this was the same cause.
Did some minor changes in Comfigurator and downloaded. After the reset, the KPs beeped and \"communication failure keypad 1\" was reported on the KP04 display. Could find no problems, reset Comfort numerous times, downloaded the previous CCL and others, recycled power completely, and so on, to no avail. Then I noticed that announcements were being made on the doorpad so anyone could hear when the system is armed/disarmed/zones bypassed/etc., despite the option being turned off in Comfigurator. Downloaded a new CCL with 2 KP\'s & no DP\'s setup - DP still broadcasted everything - had visions of burglars waiting for \"Security off\" to make their entrance! (I also have hourly time announcements to help me keep track of time so was wondering if passers-by thought that this was a new neighbourhood service!
Was about to disconnect voice to the DP when I noticed that the key on the DP was depressed slightly on one side - touched it and all the problems went away. And yes, if one depresses it off centre this can be repeated. But a spare DP doesn\'t exhibit this stuck key problem, so probably not a Comfort problem, although the spare one hasn\'t been exposed to the elements. Will have to open the installed one to see what I can find out.
But strangely, the comms problem only occurred on downloading a new CCL, not after the key was pressed by the last visitor (as far as I know, at least 6 or 7 hours earlier). And why would it report comms failure on \"keypad 1\"? I think there\'s no \"key stuck\"
in the vocab, but is communication failure the correct/logical problem to report? If so, then at least it should say doorpad 1 and not keypad 1??Not a serious problem, now that I\'m aware of it, but it would be interesting to hear an explanation for this behaviour. And perhaps a new version of Comfort could detect non-release of the key and turn off voice/mic till the key is released/pressed again?
This is the second time that this has happened. I don\'t remember the finer details of the previous occurrence, but it was immediately after I installed Comfigurator 2.1.2(beta). I was about to re-install 2.1.0 when the problem suddenly disappeared. Perhaps some vibration caused the key to release but I can\'t be absolutely sure that this was the same cause.
