Texecom Premier Arming Fault

[datadiffusion]

Go to keypad, go to Walk test, I can't remember how Texe works but will it let you scroll through a list of zones, tell us what Zones 9 and more importantly Zone 10 say as description (plus open front door and see what comes up during test)

 

Again, limited experience with Texe but is it possible Zone 9 is the door sensor housing and unused built in reed, and Zone 10 is an external contact?

Edited October 22, 2019 by datadiffusion

[Captain_Mike]

I think it's getting beyond me and I have since spoken with Managing Director of installing company who is now sending round his "No 1 Engineer"

[datadiffusion]

Be interesting to hear what it was (or, what they tell you, which may be more elightening...)

[al-yeti]

2 hours ago, datadiffusion said:

Be interesting to hear what it was (or, what they tell you, which may be more elightening...)

So zone 9 has an expander on it 

 

Sounds like an abacus split lol only 8wireles zones connected to one zone input ?

 

Where that bloke DIY swb when we need him........

[datadiffusion]

Nah as I say I suspect an 8 zone wireless expander all for one active zone

 

Zone 9 being the contact housing case and bridged/disabled built in reed switch

Zone 10 being an external FSL contact wired to the above

 

Just me guessing assuming it's like Scanny would handle it

Edited October 22, 2019 by datadiffusion

[sixwheeledbeast]

The door contact is most likely still active when the system comes to arm, this is what is causing your "arm fail".

I can tell you now it's something your maintainer will need to resolve, it's not going to be something you can fix.

 

"Area in Exit A" Would indicate that you are arming the system and no zones are currently active.

"Zone 10 Active" Would mean the alarm believes the door is open.

 

Normally these type of things happen when the mesh network is not happy, this could be an array of things.

 

First thing I can think of if this is an entry route door, I have had an issue once where when a door had a poor signal security the message to the panel had a little bit of delay.

This was due to the message passing through poor signalling hops, increasing the settle time a bit cleared this up completely. That was a pretty large old house tho.

 

Another option is that the contact is set to the wrong radio mode for whatever reason, unlikely unless someone has messed with the default settings.

 

If I was coming to this without knowing the system and found nothing obvious like above, I would recommend to fresh start all the radio equipment and possibly replace the radio expander.

This would resolve it if the engineer makes sure it's commissioned correctly and the signal security is good on all devices.

In reality it probably doesn't all that work but it's belt and braces so to speak.

 

I would say you either have poor signal in that area for whatever reason or the system is unstable as not commissioned correctly, They are the most likely causes.

It can be difficult to pin down these intermittent issues, no doubt on the day an engineer turns up you can't reproduce it.

 

It would also appear that you haven't got system faults setup via the RedCare (It's probably a "Redcare Secure" unit using pins), I would ask about this if you don't know why you are not receiving fault messages.

I would normally expect a police calling system to have keyholder only response on "system faults" and "system tampers", that way if someone is tampering with your system you are notified.

Edited October 22, 2019 by sixwheeledbeast
typo