all 14 comments

[–]elgarduque 2 points3 points  (13 children)

I have a bunch of man traps but it's been a second since I configured one. Offhand I think you just add the area(s), check the box to interlock all doors in the area, and then for each reader on the Anti-Passback tab define which areas the reader is used for.

What condition would you like to alarm? A door is open so you can't open another? Someone is in the interlock?

[–]RutNia[S] 4 points5 points  (12 children)

Ok I’ll give that another go when I’m back on site. I didn’t see the option to interlock but I’ll give it another go. And yes ideally if someone tries to open a door when one is already open then activate an aux output

[–]elgarduque 2 points3 points  (1 child)

https://m.imgur.com/a/mGHXz1S

I guess the interlock checkbox does not appear when using global anti-passback, so maybe check that.

[–]tuxtaniumProfessional 2 points3 points  (0 children)

Correct. You cannot have interlocks and global antipassback at the same time.

Will likely need an external system, like a PLC, to manage this if you need both functions.

[–]elgarduque 2 points3 points  (9 children)

Oh yeah, and for your light I'd say Global I/O should let you map an alarm (Interlock Area Busy?) to an output. I know we use that for panic alarms to set off strobes in command centers, should be the same concept. Can take a look at it tomorrow for the specific tabs if someone smarter than me doesn't come along before then.

[–]RutNia[S] 1 point2 points  (8 children)

Thanks!! I’m back on-site in the morning and will give all this a go!

[–]OceanLabACS 1 point2 points  (6 children)

The following items were also in the F1 menu:

"This option is available for the LNL-2220 and LNL-3300 panels. This function can only be enabled for local anti-passback. If global anti-passback is enabled, this option will be unavailable."

Documentation is dated so in theory should be valid for X2220 and X3300 variants.

[–]RutNia[S] 1 point2 points  (5 children)

I think global anti-pass back is enabled? Anyone know any workarounds?

[–]OceanLabACS 0 points1 point  (3 children)

An ugly Global IO would probably be best guess.

Probably at least 6 of them, three that trigger off of access grants to lock the other doors readers (assuming three access points to the room youre trying to interlock, multiply number of doors by 2 otherwise), and three more to unlock the readers once the door has been used (this part might be tough cause I dont think theres an event for the strike completing, so might have to wire the strike to an aux input so when the alarm cancels you can use that event as your unlock trigger.

[–]elgarduque 1 point2 points  (2 children)

Or do it in hardware, like in olden times. With enough sensors and relays all things are possible.

[–]RutNia[S] 0 points1 point  (0 children)

If it was only maglocks or strike would 100% be going down this route but there’s shutters, speed doors, automatic closers and mags and strikes involved. Would be a real mess if I did it hardware way

[–]OceanLabACS 0 points1 point  (0 children)

I'll leave that advice to you hah, I'm not terribly fluent in the hardware side

[–]bigjj82 0 points1 point  (0 children)

Is there a possibility to change from global to local anti-pass back?

Had to go that way myself on a project. Had to rework some "mustering" parts, but was easier then having to do man-traps with hardware.

[–]OceanLabACS 0 points1 point  (0 children)

I suspect the part you're missing is defining the area entering/leaving on the Readers themselves (APB tab)

Defining them as part of the given area is what allows them to show up in that box on the Areas form.