- Dec 27, 2016
- 398
- 154
Has anyone written up a guide of sorts on IVS Tripwire on Dahua cameras (ex IPC-HFW5231E-Z5)? I seem to struggle to understand the logic.
There is a “detection zone”. Should this be used big to the boarder of the frame to allow time for an object to be noticed before the trip lines, unless there is a lot of noise causing false triggers that necessitate making it smaller?
Are the tripwire rules “OR” or “AND”? In other words, does an object that crosses any rule cause a trigger, or does it take an object crossing all active rules to cause a trigger?
Does a zig-zag rule make the rule more sensitive or less sensitive?
What does the “Parameters” tab sensitivity do? Is this minimum pixel change or contrast or velocity of change for each rule?
How does an intrusion area differ from a trip wire area (enclosed polygon)?
In the past, I have noticed a person needs to be seen (trigger level 1), then cross a line (trigger level 2), and then exit a line (trigger level 3) to count as a trigger in the recording. Perhaps I am wrong in this, but it seems to be what I have seen when I get it to work.
I have also heard that changing the "Encode" "Smart Code" to closed vs open has an affect, but perhaps this is only with an incompatible NVR.
There is a “detection zone”. Should this be used big to the boarder of the frame to allow time for an object to be noticed before the trip lines, unless there is a lot of noise causing false triggers that necessitate making it smaller?
Are the tripwire rules “OR” or “AND”? In other words, does an object that crosses any rule cause a trigger, or does it take an object crossing all active rules to cause a trigger?
Does a zig-zag rule make the rule more sensitive or less sensitive?
What does the “Parameters” tab sensitivity do? Is this minimum pixel change or contrast or velocity of change for each rule?
How does an intrusion area differ from a trip wire area (enclosed polygon)?
In the past, I have noticed a person needs to be seen (trigger level 1), then cross a line (trigger level 2), and then exit a line (trigger level 3) to count as a trigger in the recording. Perhaps I am wrong in this, but it seems to be what I have seen when I get it to work.
I have also heard that changing the "Encode" "Smart Code" to closed vs open has an affect, but perhaps this is only with an incompatible NVR.