Zone Crossing - Not working - What have I missed ?

[lucky13]

Hi Chaps

So I have been trying to set up zone crossing but for some reason they just aren't working.

I've pasted screenshots below showing that the zones and also that they lap over each other, some guides say do this, some guides say don't overlap but I've tried both ways still without any luck.

I very rarely get it working, if it does it's from zone B - C or vice versa but I haven't ever seen A-B either way working.

Can someone please explain what I'm doing wrong

I've parsed a test video through it but no detection

I'd love to know what I've missed as I've followed several guides and can't see what the problem is

 

[lucky13]

Anyone ?

 

[Roger]

Did you watch ? I am not sure of the solution to your issue but in that video he mentions that you have to have a zone that overlaps all your other zones. Might be something to try.

 

[lucky13]

Yes thanks I’ve viewed them all but he mentions each zone has to know about the other zones and I assumed this is done also by overlapping them or at least a lot of other guides mention this.

I’ll try unlapping them and adding another zone to cover the whole area.

Thanks sometimes you just need a wake up slap when you have been going around in circles for a few nights

 

[anijet]

Try eliminating zone B. Leave A the way it is but combine B & C into just B. Maybe your current B is too narrow.

It does work. I use it on several cameras since it became available and it really eliminates false triggers.

 

[srglassw]

Not only should the zones not be overlapped, they should not touch one another either. There should be a gap between zones. This is discussed beginning at 3:15 of the Zone Crossing video in message #3 of this thread.

 

[lucky13]

So i’ve now only got 2 zones that are not overlapping or touching with a 3rd zone that covers all of them, only zone A and B Have a rule setup with A-B syntax..only A and B actually trigger an email.

Still doesn’t work more than 50% of the time at best, all very odd..

 

[fenderman]

So i’ve now only got 2 zones that are not overlapping or touching with a 3rd zone that covers all of them, only zone A and B Have a rule setup with A-B syntax..only A and B actually trigger an email.

Still doesn’t work more than 50% of the time at best, all very odd..

Ensure you don't have limit decoding enabled in the video settings...

 

[lucky13]

Thanks for looking Fenderman, I’ve attached below all my video settings and also the camera auto detection settings, I have a
SD1A203T-GN-W , do you see anything I should change ?

 

[fenderman]

Thanks for looking Fenderman, I’ve attached below all my video settings and also the camera auto detection settings, I have a
SD1A203T-GN-W , do you see anything I should change ?

Yes. First, post your new zone settings...your b zone may be too small, its hard to tell from that image you posted...it could be less than that 100 pixels you set in object detection...watch the video again and set it similarly, using larger zones.

 

[anijet]

I have all my zones adjacent to each other with no gaps in between. Many have up to 4 zones, all touching, none overlapping. 12 cameras all cloned with motion. About half with zone crossing. All work as expected consistently.

Also I don't have a zone that "covers all of them".

 

[anijet]

It would help if you posted a picture of the camera without the zones see we can see what the path is. It looks like there are steps with a motorcycle in the way. Not sure what areas you are trying to monitor.

 

[jrf]

I have all my zones adjacent to each other with no gaps in between. Many have up to 4 zones, all touching, none overlapping. 12 cameras all cloned with motion. About half with zone crossing. All work as expected consistently.

Also I don't have a zone that "covers all of them".

Yep, you don't have to do that. What it does help with is movement from trees/shadows as they have to move a fair amount to get from a zone that doesn't touch or near another zone. So for simplistic sake say zone A is the left 1/3 of the screen and zone B is the right 1/3 of the screen and zone G is the whole screen. Then there is the middle 1/3 of a gap between A and B.

When an object (of matching size/contrast) enters A it tracks it...as it moves out into the "middle 1/3" of the screen it keeps tracking it because of zone G, when it finally enters zone B...boom trigger. I have found that technique to be wildly helpful and eliminate a lot of false positives. That overall zone G (which you never use in the crossings field) allows the software to keep tracking the object when it leaves another zone.

However if you don't have issues with false triggers or in a more statically lit environment...no need to do all that.

 

[anijet]

Yep, you don't have to do that. What it does help with is movement from trees/shadows as they have to move a fair amount to get from a zone that doesn't touch or near another zone. So for simplistic sake say zone A is the left 1/3 of the screen and zone B is the right 1/3 of the screen and zone G is the whole screen. Then there is the middle 1/3 of a gap between A and B.

When an object (of matching size/contrast) enters A it tracks it...as it moves out into the "middle 1/3" of the screen it keeps tracking it because of zone G, when it finally enters zone B...boom trigger. I have found that technique to be wildly helpful and eliminate a lot of false positives. That overall zone G (which you never use in the crossings field) allows the software to keep tracking the object when it leaves another zone.

However if you don't have issues with false triggers or in a more statically lit environment...no need to do all that.

In your example would the crossing rule be A-B and G would not be mentioned at all?

 

[jrf]

In your example would the crossing rule be A-B and G would not be mentioned at all?

Correct, zone crossing rule would be A-B for both directions. Do not use G in the example I'm giving above. It's just there to keep tracking the object.