ATS path fault Texecom

[m0t]

I installed my panel over the weekend and set it up last night over COM-WIFI and it was all working fine.

Last night I received notifications to my phone when the panel was armed etc. When I woke up this morning I checked the app on my phone and it connected fine.

About half an hour later I disarmed the alarm with a prox tag and it threw up an ATS path fault causing the unit to chirp away. It wouldn't connect through the app until I put the engineer code in.

When setting up the COM-WIFI I followed the instructions, are their any settings which I could tweak so this doesn't happen again?

Edit - should add that the delay is set to 2 as per the manual

 

[Nintendofan]

The Com-wifi's are suffering 'issues' and Texecom know about this, these issues have been happening for a few weeks now and have progressively gotten worse, this is their response:

We are currently investigating the cause of this issue.
In the meantime, I would suggest disabling monitoring of ATS faults (Global Options > Monitor Hardware), disabling ATS Path Faults from the areas (Area Programming > Area Options) and enabling an ATS Fault Delay of ~20-30 mins (Global Options > System Timers).
So far this is a temporary fix to prevent the panel displaying the fault constantly; However I must note that this will prevent the panel from displaying any legitimate line faults and should not be used on a monitored system.

 

[secureiam]

Whilst I am sure the issue will be resolved soon, all the notifications generated appear to be going through okay, just the regular polling events that seem to be troublesome.

I am trying to identify why and when the comwifi is going down that I have, but its a long process of testing.

 

[m0t]

Cheers, sounds like it is a wait and see scenario then. I'll adjust the settings as above when I get home.

 

[m0t]

Is this also likely to be the cause of the frequent Comip alarm and restore messages that I am seeing in the event log?

 

[secureiam]

Yes, have changed the settings as Paul posted?

 

[alarmwatch]

From my results it's just that the regular polling is more often so catches the errors. Very occasionally the events get missed too.

 

[m0t]

I'd set it at 5 minutes but i will put it back further.

Thanks guys