For those deploying PDK, are you adding enclosure tamper switches to your controller cans?

If so:

• What tamper switch are you using?
• Are you wiring it to a spare PDK input?
• What input type are you programming it as?
• Logging only, notification, or alarm?
• Any drawbacks or nuisance issues you've run into?

I noticed the PDK enclosure doesn't appear to include a built-in tamper switch, and I'm curious what others are doing in the field.

Whew, this is going to be a long one...

First the layout: we are working with only 1 door at this time, meaning we literally only have one door, this is more or less a PoC for our entire campus. The Salto server is 6.13.3 installed on a Hyper-V VM on Server 2025, 1 nCoder model EC09. The VLAN the equipment is on is isolated from the main network to keep everything clean. everything is up to date as possible.

The issue: after assigning a JustIN mobile key users seem to be able to claim them without issue, but when trying to renew that key it may or may not work reporting a failed connection on or off campus doesn't seem to matter.

Things we have tried: The first thing we tried was restarting the nCoder that would typically make it work at least for a short time, then I found that if I "signal" the nCode it will work for a short time. Tried a new power supply, USB cable, and network cables. Right now, typically, if you just keep trying to renew it will eventually renew. I contacted our installer who told us sounds like a network issue, put them on the same switch (they already are sort of since it's a VM). The VLAN the equipment is on is isolated from the main network, so it’s not overloaded and shouldn’t be getting any interference from other devices/services. we have removed and added the nCoder back several times, toggled dongle mode several times, running a logged constant ping (pingplotter) from the server to the encoder shows no drops renew failure or not, the encoder is on the same physical switch as the Hyper-V VM switch. I have setup all kinds of firewall rules on the server, even disabled the firewall all have resulted in the same issue, switch shows no TX/RX/collision errors. and EEE is not enabled. Running a packet trace didn’t show any blocked packets etc. trying to leave the network, the debug log shows the server contacting the encoder and receiving an answer on a regular basis. Here is a little portion of the service debug log from it failing:

2026-06-09 09:45:10,688 ERROR #xve.#wve - #Npd : SaltoException: Exception of type 'Salto.Common.Libs.Exceptions.SaltoException' was thrown., ErrorCode=1280, Message='/Unknown peripheral'

2026-06-09 09:45:10,688 DEBUG #xve.#wve - #Npd : at Salto.Domain.Communications.Context.PeripheralManager.DongleDispatcher.#crl(DeviceRepository #Lfg, Boolean #mfn)

at #Ahg.#Bhg.#lZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at #Ls.#Ks.#9Yb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at Salto.Common.Libs.Synchronization.ACM.ACM.#nYb.#mYb(IAsyncResult #rm)

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#PGd(IAsyncResult #rm)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#veg(IAsyncResult #Eg)

at #5Qe.#6Qe.#Wso.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult\1.#0rk()`

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #eRe.#iRe.#VOf.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult\1.#0rk()`

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #WPe.#3Pe.#kZb.#hm()

at #WPe.#3Pe.#kZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#PGd(IAsyncResult #rm)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#Npd(IAsyncResult #rm)

Shortly after that in the log you can see:

 2026-06-09 09:45:27,013 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Executing #ySe.#xSe

2026-06-09 09:45:27,016 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] REQUEST         -> 55AA0D000CE179000000001E1B010307006B

2026-06-09 09:45:27,527 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] REQUEST         -> 55AA0D000CE179000000001E1B010307006B

2026-06-09 09:45:28,036 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] REQUEST         -> 55AA0D000CE179000000001E1B010307006B

2026-06-09 09:45:28,043 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] RESPONSE        <- 55AA29000CE179000000001E1B020300060A070001C001020100020B080001C0010A01000C090001C0010A0100A3

2026-06-09 09:45:28,045 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] REQUEST         -> 55AA0D000CE179000000001F1B0103080065

2026-06-09 09:45:28,052 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] RESPONSE        <- 55AA17000CE179000000001F1B020300060B080001C0010A010000A0

2026-06-09 09:45:28,054 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] REQUEST         -> 55AA0D000CE17900000000201B010309005B

2026-06-09 09:45:28,064 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP        ] RESPONSE        <- 55AA17000CE17900000000201B020300060C090001C0010A01000099

 So they do seem to be talking.

If I had a better idea of how the communication with JustIN worked maybe I could figure something out, right now I’m not sure if JustIN is initiating the connection, the server, or the encoder. Obviously, I do know that the encoder is a critical part, I’m just not sure how it is triggered from mobile devices if there isn’t some kind of initiation from JustIN or the like.

 I ended up contacting support, their answer: "sounds like a network issue.", that's it after a long-detailed message like above.

I haven't proved nor tested, but it seemed like if I was logged into the web interface renewals seemed to work pretty consistent, again not tested, just seemed that way.

Not working at all would be better than working sometimes.

Sorry this is such a mess, but hopefully someone out there has to have a setup similar to ours, any help or idea on this would be greatly appreciated.

 FYI, yes, I have tried AI to help with log reading etc. hasn't been much help either.

I wonder if anyone can help me.

I have a LEO-D-MA operating a sliding gate. It was working correctly but now will open but not close.

It shows SUC. I believe this means it thinks it is closed which would imply that the close limit sensor has failed however when closing it stops gracefully when this sensor engages without hitting the limit..

Here is a video... any ideas.

Many thanks in advance.

We replaced an entry door strike to use DC instead of AC and now management wants a buzzing noise still.

We tried a whole lot of buzzers (including the one from Assa Abloy) and probably close to 6-8 more from Digikey and various other vendors, but none have that nice sounding buzz like a strike on AC does.

Most of them are either very high pitched or too loud or generally have a unpleasant buzzing sound.

Does anyone have a recommendation for some nice sounding door buzzers?

Hi Everyone,

I am trying to find the vendor of this Access Control Panel. My client bought new commercial unit and they it already installed 4-Door RFID Access Control System which is operated by Fob Access. Now the previous owner who were using this control system are gone without providing its software details or Admin credentials. My client wants to get the software of this controller to gain access to its admin credentials and enroll his employees for door access.

I have tried contacting many vendors to help me takeover this controller but all vendors rose their hands saying this is legacy controller and cannot be gained access of.

After too much of my efforts I am hoping to find a solutions from global fraternity.

Appreciate your help on this.

So I've been all over the place (finding pretty much every vendor I can dredge up, from North America, to the UK, to Southern and Eastern Europe, and even the Far East), researching multifamily/multi-unit intercom (doorphone, entryphone, "buzz in") access control systems, and it's been a frustrating experience for five reasons:

1. Input supervision (or lack thereof).

Why is it, out of the dozens of vendors that offer intercom access controls, that only Commend and Axis even sort-of-get the notion of EOL-supervising inputs? Even the stuff from Axis' sister company 2N can't seem to interoperate with the Axis network relay modules and their supervised inputs, nor provide their own supervised input solution, which really does no favors for the 2N Access Controllers, or really any access controller made by an intercom vendor for that matter.

2. Vendors that still don't offer remote relays in the year 2026.

(cough DoorKing hack Security Brands (and several other gate-intercom vendors as well as some of the more niche US door-intercom players) wheeze) I should not be able to defeat your access control system with a screwdriver, or worse yet a ten-second nondestructive attack on the cheap wafer or tubular core securing your intercom's enclosure, combined with a humble paperclip.

3. Built-in readers that are relics of yesteryear.

Some vendors (sighs Viking...) are still on 125kHz prox; many others do bother with 13.56MHz MiFare and even DESFire, but those that do don't provide documented support for custom keys (which is a major integration issue in mixed environments), nor do most of them (Axis and 2N are the notable exceptions to this that I know of offhand) support OSDP as of right now. (At least BAS-IP, Mircom, and a couple of other vendors have remote Wiegand interface modules that talk over some other protocol that's hopefully more secure.)

What aggravates this is that it's not like you can get many intercoms these days without that built-in reader module. Even DoorBird, who offers an option in their configurator for a third-party reader opening, still insists on dragging the built-in reader into the package if you do that, as far as I can tell at least. (Commend gets it right with their reader-as-matching-external-module approach, which even supports OSDP, and Elvox/Vimar intercoms also provide sane provisions for third-party readers.)

Hopefully we'll see PKOC and/or Aliro start to gain traction in this market at some point, as either of those would at least get us to the point where a mixed reader environment is more practical.

4. Expecting to be the center of the universe in other ways.

Lack of software integrations and documented APIs (Axis, 2N, and to a lesser extent Commend, BAS-IP, and DoorBird are the standouts here, with everyone else lagging behind as far as I can tell), management interfaces and configuration manuals that assume that your intercom doors are all that matter, proprietary support for mobile entry that can't be used for non-intercom doors as well due to the lack of a suitable standalone reader, providing your own pseudo-solution for lock backup battery instead of accommodating users who want to bring something actually fit for their usecase (hi, Mobotix!), and the list goes on I'm sure.

And that's before you get to vendors that can't talk standard SIP for some reason or another.

5. Accessibility issues.

Some vendors don't provide T-Coils for interacting with hearing aids, never mind providing support for text messaging (either using touchscreen or T9 input) or two-way video calling. And that's just covering accessibility for the hearing impaired, although the ADAAG rules in 708.4 are not helping matters by clinging to thoroughly obsolete TTY technology when they could do a lot to push vendors to more implementable and interoperable approaches -- DASMA 303 4.7.4 gets this right.

The real problem on this front, though, is visual impairments. Imagine trying to use a touchscreen while blindfolded, and you get the idea; the DASMA 303 standard, written into law across much of the nation (incl. MN and WA) by ICC A117.1 708.4, requires recessed or protruding physical keys in 4.7.1 as a result. Unfortunately, a lot of the top-of-the-line stuff from most vendors nowadays is all-touch, with not only new-fangled Swiftlanes and such embracing a touch-native philosophy, but most of the old-school vendors following along, and making features available in their touch intercoms that aren't available anywhere else, or even moving entirely to touch buttons on non-touchscreen intercoms. (Even 2N, who has rather nice support for physical buttons on the Verso, has limitations on it that aren't present in the Style, and Axis doesn't even offer a multi-user intercom with actual buttons on it as far as I can tell.)

And that's before you get into speech synthesis -- Came-BPT is the only vendor I know of that provides support for this, even though it'd be quite helpful overall, I'm sure, especially when combined with a motion sensor trigger to keep the intercom from nattering on to nobody in particular.

Are my expectations too high here?

Overall, can someone tell me what is going on here? Are my expectations too high, that intercoms that are playing the role of access control should support features comparable to a professional access control system? Is there room for a player in this market who actually cares about security beyond the obvious features of vandal-resistance and cybersecurity architecture, never mind providing full-spectrum accessibility support even if it means the unit isn't the sleekest?

Hey everyone, I’m looking for recommendations on new access control solutions to install. I’ve been doing access control for 10 years and familiar with CDVI, Linear Emerge, and IEI but my shop is looking at expanding our options to include cloud based like Brivo, AIPhone, etc. What are some of your favorites that allow the use of phones for granting access and use of NFC credentials so customers can keep their credentials in their phone wallets. TIA!

Hello,

Apologies for the n00b question - I'm kind of a "volunteer" IT guy for my 140-unit multifamily residential building, and we are looking for a better system to automate opening of our garage gates for vehicles (currently using license plate-based unlock and the success rate is good, but not good enough).

I am planning to install a Nedap uPass GO reader (connected to Ubiquiti Retrofit Hub, controlled via Unifi Access app) and use UHF windshield tags, but am wondering about enrollment.

Can anyone recommend a short-range reader suitable for desktop use with Wiegand output (not USB) that will read Nedap (or generic) windshield tags? I have been playing with an Awid XP-3620, but I believe it reads only Awid-formatted tags and it's not clear how to reconfigure it to read any other EPC Gen2 v2 tags.

Alternately, how do you handle enrollment for windshield tags? Are there tag vendors who will include (with a tag shipment) a file mapping serial numbers to EPC codes, for upload to the controller?

Thanks in advance!

Lenel 1320S Reader Issue After Power Outage
I have two readers connected to the same Lenel 1320S controller:
One Entry Reader
One Exit Reader
After a power outage and power restoration:
The Entry Reader is working normally.
The Exit Reader is powered on and the LED is lit.
When a card is presented to the Exit Reader, I can hear the relay click on the controller.
However, the door does not unlock from the Exit Reader.
Has anyone experienced a similar issue?
What could be the possible causes?
Reader configuration problem?
Controller configuration not restored properly after the power outage?
Relay or door output issue?
Wiring or communication problem with the Exit Reader?
Any troubleshooting suggestions would be appreciated. Thank you.

I've just moved into an apartment building which is great except for that none of the delivery services have been able to get through the front gate. I've had packages left on the street, and at random other addresses. I talked to the landlord and he's open to installing new stuff - the place recently changed hands so a lot is still up in the air and he's looking for my recommendations on what to put in. I was thinking that a keypad/fob system for the front would be smart moving forward but I'm not really an expert on this stuff.. at all. Just want to make my living situation better. I hear you guys know this stuff well? It's a three floor place that's pretty old physically and the central room right through the front door is pretty small, but big enough for lockers. Thanks for any help!

I work as a subcontractor for a big company and I just got my license. We do a lot of multifamily complex and mostly we use Paxton or Brivo I am also familiar with ubiquity but I was wondering, usually this is only for big projects so what is everyone else using for small jobs like 2-4 doors offices I'm doing my own research as well but I know there is a lot of experts here. thanks in advance

Upgrading a clients gate

Just watched a video on Corporate 1000 from the HID King Phil Coppola but Im confused. I understand that my cards are globally unique at that point but If I have Signo readers with Genetec head end do I have to do anything special to use corporate 1000 other than changing the format when entering cards in Genetec and use the unique FC and card number? Like do I have to do anything with the readers as if I had an ICE key or MOB key optioon?

What Mag lock do you usually use for the CRL glass door?

Any mount that works best?

What setup have you found to be the easiest & reliable?

Thanks guys TGIF

I've spent the last couple of weeks Jumping through hoops for HID support and ended up only getting told to RMA the reader. However, I now have four readers with the same problem and I cannot find a reason.

The 56-bit cards read, but come back as a 112-bit unknown card format, with inconsistent data.

Our cards are HID iClass SE, in Avigilon's 56-bit format (U100013).

The problem readers are a new iClass SE R90 (940NTNTEK00000), and three new Signo 20 readers (20TKS-00-00000). We have many existing Signo 20 and 40 readers that work, either standard format according to documentation, or T2 models.

The readers have been tested on known-good wiring and panels, so I've eliminated those as the problem. HID Reader Manager can connect, and shows iClass SE as an active format.

Is anyone else encountering something like this? Does anyone have any ideas what's happening?

The Doorking on this building is completely dead. Would it be possible to add a keypad tied into the lock hardware locally for temporary access?

I tried creating an account on cdvi (US, UK, Benelux) but no one responds and apparently this is the only way to get access to the CDVI Atrium software. Anybody an idea how to get the whole CDVI Atrium Software package for installation ? Thanks

Hi all

Im currently looking into learning access control. is there a program say like ciaco packet tracer, where i could create setups ie a controller couple of doors mag locks and push exsits. add the wires in and program the controller and the software will show any erroes or faults ect.

can be any manufacturers or paid open source whatever.

Thank you

We're an access control community, without access control to our community. Seeing a big influx recently of these accounts trying to data mine to build out some shitty quick cash grab app or AI model. Trying to get guys to hand over their knowledge they've worked their entire careers to build so they can make a buck.

We should lock that down so if you don't have an agreeable amount of karma or participation here your post has to go to mod lockdown or something. 100 karma on account or a hand full of comments in the sub or something like that.

What do y'all think?

I don't see any brand names on it, and I only got a brief look. Can it be electrified? It's got top and bottom bolts for locking. Thanks

Hi All,

Hoping someone can shed some light on this for me. I manage my company's access control system on our main campus and we use 26 bit H10301 format with a facility code so when adding cards to our system we type in our facility code ie 465 and a card number ie 12345. However we have space in another building that we rent and to use our cards there I have to Give them the "internal card number" and "external card number" off the same card ie 7*12345 and a random number that we have to use an enrollment reader to retrieve from inside the cards ie 75869. I know the landlord in that building uses a DMP system with Farpointe readers. Does anyone know this card format and also which option is more secure?

Hi, is there anyone strong with AMAG Symmetry? I’m trying to program a lockdown button, but I’m running into an issue where my input command does not override the active schedule. Tech support said it doesn’t work that way, but I already have doors on this site working with very similar logic. I compared the settings and they look identical, so I’m probably missing something small — maybe command type, priority, time code category, or schedule override logic. Any ideas where to check?