Tamper reporting and TX delay to central station with EVL4
Posted: Sun Aug 01, 2021 8:28 am
Good morning. Three questions for you all. I have a DSC1832, EVL4, and Eyzon monitoring over ethernet/internet.
[*] How can I disable tamper reporting to the central station? I have set 00 in the tamper/restoral reporting codes (330-337). And I have disabled all the tamper/restoral call directions (359). But the central station is still notified immediately and calls me.
[*] Why is the transmission delay zone attribute ignored? I have a few zones with the #7 TX Delay attribute set. But that zone reports its alarm to the central station immediately. Note, I am not talking about a delayed entry zone. I'm talking about the TX delay zone attribute. The zone goes into alarm immediately, but my expectation is the transmission to the central station is delayed for X seconds.
[*] Does the Communication Cancelled Message (third communicator options 382 #3) actually do anything?
[*] How can I disable tamper reporting to the central station? I have set 00 in the tamper/restoral reporting codes (330-337). And I have disabled all the tamper/restoral call directions (359). But the central station is still notified immediately and calls me.
[*] Why is the transmission delay zone attribute ignored? I have a few zones with the #7 TX Delay attribute set. But that zone reports its alarm to the central station immediately. Note, I am not talking about a delayed entry zone. I'm talking about the TX delay zone attribute. The zone goes into alarm immediately, but my expectation is the transmission to the central station is delayed for X seconds.
[*] Does the Communication Cancelled Message (third communicator options 382 #3) actually do anything?