Anyone familiar with DSX access control for doors

Trying to help understand the system the church has and how it relates to a computer running W,inDSX?

Small building. Only a couple of doors.
DSX has a pretty well laid out website, the computer is needed to run the software that sets the automation and access control schedules and so forth.
 
This is pretty simple with key fobs to open 2 doors. One PC programs the key fob.

At this point I don"t see any type of controller on the network that would send power to open door locks. This is from network displays vs physically looking at the cabling.

I have been looking at the website and it's not exactly clear what pieces are needed for a system with 2 doors and 10 or 20 users.

What I have not found yet is a block diagram or flow chart as to how the system fits together.
 
This is pretty simple with key fobs to open 2 doors. One PC programs the key fob.

At this point I don"t see any type of controller on the network that would send power to open door locks. This is from network displays vs physically looking at the cabling.

I have been looking at the website and it's not exactly clear what pieces are needed for a system with 2 doors and 10 or 20 users.

What I have not found yet is a block diagram or flow chart as to how the system fits together.





1. DSX Controller








  • Example: DSX-1040, DSX-1020, DSX-1042, etc.
  • Acts as the brain of the system; it manages access control decisions and communicates with the host PC and connected hardware.
















2. Host PC with DSX Software








  • DSX Software (WinDSX or WinDSX SQL):
    • Used for configuration, monitoring, and management of the access control system.
    • Can be networked or standalone.

  • PC Requirements:
    • Typically runs Windows OS and must meet DSX’s system requirements.
















3. Power Supply








  • Regulated 12V or 24V DC power supply, often with battery backup (UPS or SLA batteries).
  • Required to power the controller, locks, readers, etc.
















4. Readers








  • Proximity or Smart Card Readers (HID, DSX-branded, etc.)
    • Installed at each controlled door to read user credentials.

  • Supported formats include HID, iClass, Mifare, etc.
















5. Credential Devices








  • Cards, fobs, or mobile credentials
    • Programmed and assigned to users in the DSX system.
















6. Electronic Locking Hardware








  • Electromagnetic Locks (maglocks) or Electric Strikes
    • Physically lock/unlock the doors based on access decisions.

  • May also include fail-safe or fail-secure hardware.
















7. Door Position Switch (DPS)








  • Monitors whether the door is open or closed.
  • Helps detect forced entry or door held open alarms.
















8. Request-to-Exit (REX) Devices








  • Motion sensors or Push-to-Exit buttons
    • Allow people to exit without triggering alarms or requiring a credential.
















9. Wiring / Cabling








  • Shielded cables for data and power connections between components.
  • Typically includes:
    • Reader cable (e.g., 22/6 or 22/8)
    • Lock power cable
    • RS-485 for controller communication
















10. Optional Components








  • Enclosures (for mounting controllers)
  • Network modules (for IP communication)
  • Elevator control boards
  • Alarm inputs/outputs
  • Integration with CCTV or fire systems



there’s got to be an IT closet or some place the church has their infrastructure unless they got the access control stuff stuck up in an attic or undercroft.
 





1. DSX Controller








  • Example: DSX-1040, DSX-1020, DSX-1042, etc.
  • Acts as the brain of the system; it manages access control decisions and communicates with the host PC and connected hardware.

I think I know where the DSX electronic components are. I am thinking there is DSX software running on a PC server and then at times when needed WinDSX running on a desktop to add new keyfobs.
















2. Host PC with DSX Software








  • DSX Software (WinDSX or WinDSX SQL):
    • Used for configuration, monitoring, and management of the access control system.
    • Can be networked or standalone.

  • PC Requirements:
    • Typically runs Windows OS and must meet DSX’s system requirements.
















3. Power Supply








  • Regulated 12V or 24V DC power supply, often with battery backup (UPS or SLA batteries).
  • Required to power the controller, locks, readers, etc.
















4. Readers








  • Proximity or Smart Card Readers (HID, DSX-branded, etc.)
    • Installed at each controlled door to read user credentials.

  • Supported formats include HID, iClass, Mifare, etc.
















5. Credential Devices








  • Cards, fobs, or mobile credentials
    • Programmed and assigned to users in the DSX system.
















6. Electronic Locking Hardware








  • Electromagnetic Locks (maglocks) or Electric Strikes
    • Physically lock/unlock the doors based on access decisions.

  • May also include fail-safe or fail-secure hardware.
















7. Door Position Switch (DPS)








  • Monitors whether the door is open or closed.
  • Helps detect forced entry or door held open alarms.
















8. Request-to-Exit (REX) Devices








  • Motion sensors or Push-to-Exit buttons
    • Allow people to exit without triggering alarms or requiring a credential.
















9. Wiring / Cabling








  • Shielded cables for data and power connections between components.
  • Typically includes:
    • Reader cable (e.g., 22/6 or 22/8)
    • Lock power cable
    • RS-485 for controller communication
















10. Optional Components








  • Enclosures (for mounting controllers)
  • Network modules (for IP communication)
  • Elevator control boards
  • Alarm inputs/outputs
  • Integration with CCTV or fire systems

there’s got to be an IT closet or some place the church has their infrastructure unless they got the access control stuff stuck up in an attic or undercroft.

I believe I know where the DSX electronics are. I assume there is a PC server running DSX software. And when needed a desktop running WinDSK software to add new keyfobs.

I need to figure out how the WinDSX software finds the DSX software running on a server. Hostname or IP address?

I have not found the DSX software running on a server yet via Unifi network displays
 
As discussed in the other thread - it can't hurt to add the local router as a third dns server in the settings.
You can easily verify that by reverting the main dns server to be the local 192.xxx box. If you lose internet as before but get your software to work - you have your answer.

Also, you need to confirm that software worked before in the first place.
 
I believe I know where the DSX electronics are. I assume there is a PC server running DSX software. And when needed a desktop running WinDSK software to add new keyfobs.

I need to figure out how the WinDSX software finds the DSX software running on a server. Hostname or IP address?

I have not found the DSX software running on a server yet via Unifi network displays
Could you access the network and see a list of connected devices?
 
I have and have not identified it yet. The church has a server for church software (financial, etc) and it could be on that server. But that server would need some type of connection (network??) to the DSX electronics.
Unless whoever originally set the DSX up just used a patch cable to the cabinet that holds the equipment and whenever changes were made they just plugged it.
 
Unless whoever originally set the DSX up just used a patch cable to the cabinet that holds the equipment and whenever changes were made they just plugged it.
There are a lot of unknowns at church. Network switches and WIFI access points above suspended ceiling probably just sitting on top of the tiles. No one is quite sure where.

The local tech company they hire made some changes and the DSX lock system broke and they had to call the DSX installer and got a big $$ bill.
 
There are a lot of unknowns at church. Network switches and WIFI access points above suspended ceiling probably just sitting on top of the tiles. No one is quite sure where.

The local tech company they hire made some changes and the DSX lock system broke and they had to call the DSX installer and got a big $$ bill.
I worked and volunteered many years for churches always killed myself and went far and beyond to save the church a buck. Often I learned some things were meant to be handled by outside contractors.
 
I worked and volunteered many years for churches always killed myself and went far and beyond to save the church a buck. Often I learned some things were meant to be handled by outside contractors.
I am hoping to do the same here. I am upgrading some of their outdated Unifi hardware with newer Unifi hardware. I will be copying the network configuration from a USG to UDM Pro so theoretically everything should stay the same. Still there are things I may not know about and don't want to mess them up.

The DSX access control is one of them.

I am thinking if the WIFI network names and VLANs all stay the same things should be fine.
 
In the typical low security version of this system, there's no such thing as "programming a key fob." The fobs carry a permanent unique serial number from the factory, and the controller holds a list of authorized fobs which may be different for different doors.

It isn't necessary to have a server constantly online for day to day unlocking of doors. When it is necessary to add or remove fobs from the list(s), a PC links to the controller. This process may involve a fob reader connected to the PC to easily get the fob's number, but this workstation doesn't alter the fob. Numbers are printed on fobs at the factory, but perhaps by design they wear off after being carried in a pocket for a while.
 
I am hoping to do the same here. I am upgrading some of their outdated Unifi hardware with newer Unifi hardware. I will be copying the network configuration from a USG to UDM Pro so theoretically everything should stay the same. Still there are things I may not know about and don't want to mess them up.

The DSX access control is one of them.

I am thinking if the WIFI network names and VLANs all stay the same things should be fine.
when it comes to anything wifi as long as you use the same SSID and password you can change routers 10x and it wouldn't make a difference. how sophisticated is the churches network?
 
when it comes to anything wifi as long as you use the same SSID and password you can change routers 10x and it wouldn't make a difference. how sophisticated is the churches network?
Well the Unifi router is a USG. So maybe 8 years old? 10? They could have wired everything back to a main patch panel but instead there is one switch connected to another switch to another switch and one moves across the church building. Equipment hidden above suspended ceiling tiles.

The good thing is all the streaming equipment in the two different locations is wired.
 
Well the Unifi router is a USG. So maybe 8 years old? 10? They could have wired everything back to a main patch panel but instead there is one switch connected to another switch to another switch and one moves across the church building. Equipment hidden above suspended ceiling tiles.

The good thing is all the streaming equipment in the two different locations is wired.
with that many switches daisy chained together i take it they're "unmanaged"? if they aren't i would be real careful how much you dig into the network.
 
Ok so there is a network connection to a network switch. But it's 100Mbs and the Unifi displays shows little more than that the port is active.

So there must be a PC acting as a server. Now to find someone who knows more about it.
 
Back
Top Bottom