Since last month (which happens to be when I upgraded all firmware and started using Comfigurator 4.0.3) the alarm panel reports communication failure with keypad 03, which is then reported as resolved a few seconds later.
This morning the alarm panel reported communication failure with keypad 01 and a few seconds later it was reported as resolved.
is the keupad power supply connnected to 12V or S12V?
S12V may be switched off by response or time program
casn you read the event logf and check the events that occured around these times?
11-11-2025, 10:25 AM (This post was last modified: 11-11-2025, 10:29 AM by Howser.)
(11-11-2025, 10:01 AM)slychiu Wrote: is the keupad power supply connnected to 12V or S12V?
S12V may be switched off by response or time program
casn you read the event logf and check the events that occured around these times?
I suspect the 12V power supply output to the keypads has malfunctioned and is intermittently dropping the voltage. How old is the Ccomfort, do you have the serial number?
11-12-2025, 09:18 AM (This post was last modified: 11-12-2025, 02:01 PM by Howser.)
(11-12-2025, 02:43 AM)slychiu Wrote: I suspect the 12V power supply output to the keypads has malfunctioned and is intermittently dropping the voltage. How old is the Ccomfort, do you have the serial number?
I upgraded to Comfort II in 2011 and again to CM9001B end of 2019. Comfigurator does not show the serial number, serial number below (from the board)
It is probably a power supply fault.If the intermittent keypad troubles are annoying you can disable thecomunications failure alarm, by assigning Null alarm to non detector alarm for Rs485 communications failure
this will prevent the rs485 comms failure from activating, which means you may not be informed of other communications failures.
Maybe you can leave it this way for some time and see what happens
(11-13-2025, 01:31 AM)slychiu Wrote: this will prevent the rs485 comms failure from activating, which means you may not be informed of other communications failures.
Maybe you can leave it this way for some time and see what happens
Regarding the power supplier, I swapped power suppliers around and the problem still persist.
Then I suspect the controller CPU board may have a faulty RS485 driver. If you do not want to change the CM9001 , you may want to disable the RS485 Comms failure alarm, in Nondetector alarms, RS485 comms failure set to null This will diosable all comms failure alarms
(11-13-2025, 01:31 AM)slychiu Wrote: this will prevent the rs485 comms failure from activating, which means you may not be informed of other communications failures.
Maybe you can leave it this way for some time and see what happens
Regarding the power supplier, I swapped power suppliers around and the problem still persist.
Would the backup battery cause this issue?
Would the comms error trigger an alarm (siren and external monitor trigger) when the alarm is in Away Mode?
