morgan306 Posted October 15, 2014 Posted October 15, 2014 On an PD6662/EN50131 system, if the system is activated followed by a tamper, would it send an intruder, followed by confirmed, or intruder then tamper? I think confirmed, but I'd like to be sure as I have a grading exam tomorrow. !
james.wilson Posted October 15, 2014 Posted October 15, 2014 depends on the panel and sw version. If SIA >2 then yes securitywarehouse Security Supplies from Security Warehouse Trade Members please contact us for your TSI vetted trade discount.
james.wilson Posted October 15, 2014 Posted October 15, 2014 no if pins it should send an intruder then a tamper. some fw versions will treat that as a confirm, some wont. If sia then the arc procedures will decide. Pins are out of date and have been for some years securitywarehouse Security Supplies from Security Warehouse Trade Members please contact us for your TSI vetted trade discount.
morgan306 Posted October 15, 2014 Author Posted October 15, 2014 Say pins on a Galaxy for arguements sake.
james.wilson Posted October 15, 2014 Posted October 15, 2014 dunno, it shouldnt a tamper isnt a confirm event now but adrian knows more on the regs in his head than me securitywarehouse Security Supplies from Security Warehouse Trade Members please contact us for your TSI vetted trade discount.
9651 Posted October 15, 2014 Posted October 15, 2014 Just had a look through my notes. It should as James said send a tamper now if set, not an unconfirmed. However, if another detector triggers in the confirmation window it will send a confirmed is how i intemperate it? I'm going to try it on a RI tomorrow,
breff Posted October 15, 2014 Posted October 15, 2014 Something that I am not sure on, however, when PD6662 is turned on with a Premier, it automatically selects the option of 'No confirm for device tamper', which makes me think that no confirmed should be sent The opinions I express are mine and are usually correct! (Except when I'm wrong)(which I'm not)
AdrianMealing Posted October 15, 2014 Posted October 15, 2014 Something that I am not sure on, however, when PD6662 is turned on with a Premier, it automatically selects the option of 'No confirm for device tamper', which makes me think that no confirmed should be sent Tamp no confirm is only for the same device, so if the device goes active, then a tamper from the same device will not cause a confirmed alarm, however a tamper from another device in the confirmation window will. Just had a look through my notes. It should as James said send a tamper now if set, not an unconfirmed. However, if another detector triggers in the confirmation window it will send a confirmed is how i intemperate it? I'm going to try it on a RI tomorrow, Depends on the order, if tamper first then yes send tamper, if activation first then tamper from a different device, = Alarm + confirmed dunno, it shouldnt a tamper isnt a confirm event now but adrian knows more on the regs in his head than me Only from the same device amealing@texe.com Head of Industry Affairs Visit Our Website Texecom
whistle Posted October 15, 2014 Posted October 15, 2014 We had a site with a keypad and speaker in the 24 hour security lodge, they had a FA one night single activation. The temp guard had no idea of the code so started trying different codes to shut the sounder up. Ended up going tamper keypad (Galaxy 520) anyhow it sent a confirmed upon the tamper and got policed.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.