Zone and trigger problem.

R

reeves1985

Pulling my weight
Sep 13, 2015
776
241
I'm newish to BI and been trying to get my head around 1 particular zone crossing and trigger that I can't work out.

I've been trying for 3 days to no avail.

I have a 5231 monitoring my front gate (gate cam)
A 59225HNI ptz on overview

Scenario:
I want to set up so that when someone enters or exits the front gate zone the ptz swings to the gate (preset 2).

Where I'm at
I configured the zones a, b and c.

I've made sure that the zones are seperate so that as you get to the gate the subject is not in both zones thus not causing a trigger.

So basically if a subject moves from zone A to B or B to A or zone A to C or C to A it fires the trigger for ptz to swing to that preset.

In object detection I've input
A-B, A-C (is this part correct)

I've also configured the HTTP command for the PTZ to fire on trigger. I've confirmed this worked correctly by testing the trigger and it does as it's supposed to.

What I can't get to work is
I can't get the zones to trigger.
So basically if I walk in the gate it doesn't trigger or if I wk out the gate It won't trigger.

I've tried adjusting the MAKE time from 0.0 to 1. I've 're adjusted the zones so that a subject can't be in any 2 zones at once (I've watched the video where this doesn't cause a trigger) so I've made sure that's not the case

Any help greatly areciated
 
Add a zone that spans the entire image. (Many of us use zone G for this.)
This full image Zone should not be referenced in the ‘Object crosses zone’ setting.

Also, try checking the ‘Object travels’ control.
 
jaydeel said:
Add a zone that spans the entire image. (Many of us use zone G for this.)
This full image Zone should not be referenced in the ‘Object crosses zone’ setting.

Also, try checking the ‘Object travels’ control.
Click to expand...

Funny you should say that I removed the zone for the entire image to make it clearer
I have done D that covers the whole image
I just removed it for the sake of that pic and forgot to mention it

I've tried it with object travels ticked and unticked
 
Silvermoose said:
I think your zones should be closer. Try separating them by one row of boxes.

L8tr
D
Click to expand...

I've tried that
But if my zones ate close subject will be in 2 of the boxes at the same time

E.g. zone A and Zone B,
This causes BI not to trigger
 
I personally don't use a zone to cover the entire image but I do make my zones touch each other. Maybe make a zone to cover the gate area and then make a zone on each side of the gate touching the gate zone.
 
lcam said:
I personally don't use a zone to cover the entire image but I do make my zones touch each other. Maybe make a zone to cover the gate area and then make a zone on each side of the gate touching the gate zone.
Click to expand...

The problem with that is where the camera is in relation to the gate a human subject would be in both zones at the same time,
This then doesn't trigger because the subject wouldn't be going from 1 zone to another
 
Are you on BI4 or 5? I have the same camera, and there appears to be a slight difference with how the software manages motion detection when using multiple zones. I'm on BI5 now and detection is much more reliable with a single zone rather than multiple zones. Maybe instead of zones, you could put a hotspot on the gate to catch all activity? If you're set on your current zone setup, then try some of the following to see if it helps:

First, if you still have footage (or if you can create footage) where motion was not detected when it should have been--make and test incremental changes to your settings; next, go back and review the footage with the Test Run Video Through Motion Detector. If your change(s) have the desired effect, then you'll see a yellow trigger box where you hadn't seen one before (be sure to make changes to the correct profile if you have multiple profiles--AND be sure you're currently on the same global profile at the time your video was recorded--otherwise you may be testing the wrong masks/zones). Be sure to go back several seconds or more before the trigger to start viewing—this will give the motion sensor time to “learn” the video before it can begin to actually discriminate motion. Using existing video will allow you to test your changes without having to wait for or create new motion for each test.

I suspect the problem is that zone A is too small, but if you don't want to change that just yet, try the following:

Redraw your zones or recheck the drawing of each zone to make sure some errant grid marks aren't hidden under any of your zones (I.e a few grid squares hiding under zone B)--do this for all three of your zones. To do this, just go in and clear D, check that zones ABC are not touching each other, next clear one zone at a time to see if there are any hidden squares, then cancel out, go back in and do the same thing in a different order, then cancel out and do it again until you're comfortable there are no hidden squares. (I've actually had this happen to me--whether or not it was my own mistake or things were skewed during early upgrades to BI5 and camera restores, I don't know).
Disable Sentry if enabled
Ensure your break time is 10 seconds or more
Lower your minimum size and contrast filters
Uncheck your object size exceeds until you get this sorted out
Hold off on checking object travels (pixels)
Cancel shadows, black&white, hi-def, etc until you get this sorted. (Don't change Gaussian if you have it set--this resets all your motion zones)

Finally, try making zone A larger (may have to cut back the other zones if you want some separation)--even though you have a very quick make time, the software needs some real estate to identify motion detection. And since zone A is so small, make sure the minimum size filter isn't too large.

Hopefully you'll get a new alert image with one or more of these changes. When viewing the video while testing if you're getting blue boxes but no yellow trigger box, you know you're on the right track, you just need to nail down which setting is the key. Also, when you do get an alert image, review the footage at 1X, 2X and 4X speeds to get the most info possible. Good luck.
 
Last edited:
  • Like
Reactions: Wen
beepsilver said:
Are you on BI4 or 5? I have the same camera, and there appears to be a slight difference with how the software manages motion detection when using multiple zones. I'm on BI5 now and detection is much more reliable with a single zone rather than multiple zones. Maybe instead of zones, you could put a hotspot on the gate to catch all activity? If you're set on your current zone setup, then try some of the following to see if it helps:

First, if you still have footage (or if you can create footage) where motion was not detected when it should have been--make and test incremental changes to your settings; next, go back and review the footage with the Test Run Video Through Motion Detector. If your change(s) have the desired effect, then you'll see a yellow trigger box where you hadn't seen one before (be sure to make changes to the correct profile if you have multiple profiles--AND be sure you're currently on the same global profile at the time your video was recorded--otherwise you may be testing the wrong masks/zones). Be sure to go back several seconds or more before the trigger to start viewing—this will give the motion sensor time to “learn” the video before it can begin to actually discriminate motion. Using existing video will allow you to test your changes without having to wait for or create new motion for each test.

I suspect the problem is that zone A is too small, but if you don't want to change that just yet, try the following:

Disable Sentry if enabled
Lower your minimum size and contrast filters.
Uncheck your object size exceeds until you get this sorted out
Hold off on checking object travels (pixels).
Cancel shadows, black&white, hi-def, etc until you get this sorted. (Don't change Gaussian if you have it set--this resets all your motion zones).

Finally, try making zone A larger (may have to cut back the other zones if you want some separation)--even though you have a very quick make time, the software needs some real estate to identify motion detection. And since zone A is so small, make sure the minimum size filter isn't too large.

Hopefully you'll get a new alert image with one or more of these changes. When viewing the video while testing if you're getting blue boxes but no yellow trigger box, you know you're on the right track, you just need to nail down which setting is the key. Also, when you do get an alert image, review the footage at 1X, 2X and 4X speeds to get the most info possible. Good luck.
Click to expand...

Thanks for all your tips
I am running BI5

I've literally just stumbled across the test footage option. Before I've been guessing.

For now I have actually set it as you say with just a zone around the gate.
Thst will work for now although I do need to have it setup similar to how I illustrated.

The reason being is
There is a constant flow of people walking up and down 24 hours a day, we have a problem drug dealer on the next street so its basically a addict highway.

I can make the zone small enough to not trigger from this but I dont want the triggers from either people walking out from mine or the neighbours as it's a waste of time as i dint need that clip/alert as there is no access to my gate other than from the actual 2 houses.
So I only want a trigger when someone actually walks from the street into the gate.

I could probably simplify it to 2 zones actually.
But I was beginning to get the same conclusion as you that zone A is too small
 
  • Like
Reactions: beepsilver
If you could possibly re-aim your camera downward a bit, it'd give you a little more space to draw a bigger zone A.
 
beepsilver said:
If you could possibly re-aim your camera downward a bit, it'd give you a little more space to draw a bigger zone A.
Click to expand...
There is that possibility,
I dont want to zoom it out anymore as I think that will take away from the purpose of the camera.
But adjusting it slightly downward is a good suggestion
 
  • Like
Reactions: beepsilver
You must log in or register to reply here.
Top Bottom