03-07-2014, 06:56 AM
Pages: 1 2
03-07-2014, 03:22 PM
Hello,
After making some tests, there is something I don\'t quite like about this solution.
If there is a continuous movement from the person being detected, the counter007 never increments!
That is to say that, with a continuous movement the person can take time to inactivate the alarm sistem ...!
How can one make a work arround on this? Maybe another timer to break the continuous movement?
After making some tests, there is something I don\'t quite like about this solution.
If there is a continuous movement from the person being detected, the counter007 never increments!
That is to say that, with a continuous movement the person can take time to inactivate the alarm sistem ...!
How can one make a work arround on this? Maybe another timer to break the continuous movement?
03-07-2014, 07:13 PM
Instead of
\" Do NullResponse After 30 Seconds Using Timer08\"
substiute with
\" Do TriggerAlarm After 30 Seconds Using Timer08\"
TriggerAlarm Response:
If Security Mode <> Security Off
Then Do Alarm Intruder Alarm
endif
\" Do NullResponse After 30 Seconds Using Timer08\"
substiute with
\" Do TriggerAlarm After 30 Seconds Using Timer08\"
TriggerAlarm Response:
If Security Mode <> Security Off
Then Do Alarm Intruder Alarm
endif
03-07-2014, 07:24 PM
But then, if there is a False Alarme (eg: Counter007=1) the alarm will end up triggering Intruder Alarm, or not?
03-08-2014, 07:26 AM
You are right, it will cause an alarm
You can still use the original response
If there is continuous motion for 30 seconds it will not trigger entry delay or cause alarm but the PIR should trigger again.
Or you may be able to thnk of a better logic
That is one of the problems of using PIR for Entry door
You can still use the original response
If there is continuous motion for 30 seconds it will not trigger entry delay or cause alarm but the PIR should trigger again.
Or you may be able to thnk of a better logic
That is one of the problems of using PIR for Entry door
03-08-2014, 08:05 AM
What is the instruction to test if the Zone (PIR) is ON?
My idea is: if after Timer08 ends and the Zone is still ON then trigger alarm.
My idea is: if after Timer08 ends and the Zone is still ON then trigger alarm.
03-08-2014, 08:08 AM
If Input (Zonename) <>0 Then..
03-08-2014, 10:37 PM
I tried the following:
Zone Response:
If Timer Timer10 = 0 Then
Do AgainstContMov After 15 Seconds Using Timer10
Set Counter020 = 0
End If
Increment Counter020
If Counter Counter020 >= 3 Then
Stop Timer Timer10
Start EntryDelay
Else
Skip Alarm
End If
Response AgainstContMov:
If Input PIR_Hall <> 0 Then
Start EntryDelay
End If
But the AgainstContMov Response is not working! With continuous motion, I would expect to start EntryDelay after 15s, but it doesnôt!
What is not right? Is it because it\'s a Virtual Input, from KNX?
Zone Response:
If Timer Timer10 = 0 Then
Do AgainstContMov After 15 Seconds Using Timer10
Set Counter020 = 0
End If
Increment Counter020
If Counter Counter020 >= 3 Then
Stop Timer Timer10
Start EntryDelay
Else
Skip Alarm
End If
Response AgainstContMov:
If Input PIR_Hall <> 0 Then
Start EntryDelay
End If
But the AgainstContMov Response is not working! With continuous motion, I would expect to start EntryDelay after 15s, but it doesnôt!
What is not right? Is it because it\'s a Virtual Input, from KNX?
03-09-2014, 06:06 AM
Start Entry delay only works when it is in a Zone Response
I think it is quite difficult to keep continuous motion on the PIR for 30 seconds. Perhaps there is a setting on the sensor to turn on for a fixed time when motion is detected, eg 1 second
There is no difference between the Virtual Input and a real Input once it is triggered
I think it is quite difficult to keep continuous motion on the PIR for 30 seconds. Perhaps there is a setting on the sensor to turn on for a fixed time when motion is detected, eg 1 second
There is no difference between the Virtual Input and a real Input once it is triggered
03-27-2014, 01:21 PM
I have alarm sensors connected to binary inputs and had many false alarms. I have reduced drastically alarms parameterizing these binary inputs. In my case prompted to send activation with 0.5 second delay and deactivation of the sensor without any delay. It is also possible to add that cyclically send deactivation sensor in a shorter delay activation time, but that can burden the KNX bus if you have many sensors on KNX. This has led me to 80% or 90% fewer false alarms in the KNX sensors.
Regards
Regards
Pages: 1 2