Comfort would not Arm

[dcrera]

Hi

Comfort would not arm to Away mode.

It comes up with Armfailure Z

Log show ArmFailure (4)
                Alarmerased (20)

Please assist

Thanks

[slychiu]

We need more information that that

• Did you open and close the entry door if arming to away? If you do not exit from the enrty door then there will be arm failure
  
• What are the open zones? Do security check F3,2 and hear what zones are announced.
  
• Is there an alarm already before arming? Is the red ARM led on the keypad off?
• What is the firmware version?
  

The reason for not being able to arm is usually very simple

[dcrera]

Hi

I had the same problem again with the system refusing to arm. Pretty annoying as I had left home on a weekend vacation and I had some of my family leave a little later and then system played up again.

Had no choice but to leave the system unarmed for the entire Easter weekend.

Came home today and did a security check and the system would not announce any zones. Only one zone annouced, the PIR movement in the lounge announced the Front Door (strange).

Did a system reset on the panel, still no joy.

Did a power and battery drain, still no joy.

Had a problem connecting to the UCM and did a reset again and I finally got comms.

Did a system download and all\'s well again.

Did a security check and all zones reported with no issues.

The CPU firmware  is 5.145 and Ucm is 5.174

Please advise how to proceed from here.

Thanks

[ident]

When you press the Away button to arm the system, the keypad will announce any open zone that is preventing the system from arming

If all zones are closed, the keypad says \"Please exit\".. and allows you  to leave the house and close the front door
Once the front door is closed, the system will check all zones dfor 6 seconds, and if no further zones are open, the system arms to Away Mode. If any zone is open during that final 6 seconds there is an ARM Failure

This could be caused by a zone becoming open. perhaps due to a zone fault or wiring problem or a  magnetic contact that is losing its magnetism or too high resistance of the wiring.

Your PIR causing the Front door to announce open is suspicious and indicates a problem on the zones, Resetting Comfort and removing the batteries is not the solution. The problem seems to be intermittent so resetting comfort allows you to check it a little later when the zones may have restored

I assire you that Comfort will not detect zones open when they are not so.

I suggest you upgrade the firmware to 5.183, NOT because the current firmwar 5,145 caused this problem. but because the new firmware records the zone which caused the Arm Failure, This may help you to find the zone responsible for causing the arm failure. see see http://www.comfortforums.com/forum79/1784.html

Can you also read the event log and send to suport@cytech.biz so we can try to help you to find the cause of your problem

Anyway did you know that even after you left the house you still could have armed it remotely by dialing in , entering your code and arming remotely to away or vacation mode

[dcrera]

Hi,

I am following the instructions and it requires the UCM version of 5.178 or higher, mine  is 5.174.

Is it Ok to proceed ? or how do I to upgrade the UCM firmare ? The UCM I have is a few months old.

Also, I tried arming the system remotely and Comfort did not request a signon message.

Thanks

[ident]

Also, I tried arming the system remotely and Comfort did not request a signon message.

When you phone your Comfort system, when it answers you are required to sign in i by pressing *, your code and the # key in order to access the Voice Menu. If you have  a greeting message, you can sign in by pressing *, you code and the # key
Then you can access the menu to arm the system.

Please try this so you can be familiar with how to remotely and locally arm the system, and so you can take advantage of the system.

I dont think it is necessary to upgrade the firmware at this stage
I wil reply privately about your event log that you sent

[dcrera]

Hi

I have used the remote sign in on numerous occasions to open and close my driveway gates when the gardener arrives.

In this instance it did not respond. After yesterday\'s \'fix\', I logged in remotely with no issues.

Thanks 

[dcrera]

Hi I had a problem with arming to Away mode.

Log reports :
05/09  08:30 Alarm Type #ARMFAILURE (4)
05/09  08:30 Sign in - User #, 1
05/09  08:30 Alarm Type #ALARMERASED (20)

What is #ARMFAILURE (4)? Is this zone 4

I updated my Comfort to :

FirmWare Cpu  5.183
                Ucm 5.200

This was done so that I would know exactly what was causing this problem, but I don\'t see anything different


Thanks

[admin]

Comfort 5.183 will report the open zone which caused arm fail before the Arm Fail event
You have not shown what came before the arm fail event, if any

05/09  08:30 Alarm Type #ARMFAILURE (4)
05/09  08:30 Sign in - User #, 1
05/09  08:30 Alarm Type #ALARMERASED (20)

ArmFailure (4) - the 4 means alarm type 4

However if the arm failure is caused not by an open zone but because the front door was not opened in Away Arming then obviously no zone would be recorded in the event log

Were you trying to arm to Away or Night, or Day mode? Look at the event log from the time that you attempted to arm

[dcrera]

Hi

After pressing the Away button, Comfort responded with \'Please exit\'. If there were any another messages, it would have been after the exit.

This is the entire log :

05/09  00:05 Sign in - User #, Keypad
05/09  00:05 Mode Change #Night Mode
05/09  00:05 Sign in - User #, 1
05/09  00:05 Sign in - User #, 1
05/09  00:05 Mode Change #Security Off
05/09  00:05 Sign in - User #, Keypad
05/09  00:05 Mode Change #Night Mode
05/09  05:26 Sign in - User #, 1
05/09  05:26 Sign in - User #, 1
05/09  05:26 Mode Change #Security Off
05/09  08:30 Alarm Type #ARMFAILURE (4)
05/09  08:30 Sign in - User #, 1
05/09  08:30 Alarm Type #ALARMERASED (20)
05/09  08:30 Sign in - User #, 1
05/09  08:30 Mode Change #Security Off
05/09  11:32 Sign in - User #, 1


Thanks