24/7 Facility Access via Raspberry Pi š„§ š°
Daxko Core uses a Raspberry Pi device to fulfill facility access requirements. The device acts as a bridge between the door hardware, a barcode scanner, and the membership software. Below is a diagram of what this connection is like.
Our team will order the device, configure the necessary parameters, and subsequently ship it to your organization once the setup is complete.
Setting up 24/7 access with Daxko Core is pretty straightforward. We send you a pre-configured Raspberry Pi device that acts as the brain for your facility.
How it all comes together
The Door: This is the turnstile or door you want to automate. Each device controls a single door or turnstile ā one Pi cannot manage more than one access point.
Door Leads: These are the two wires coming from your door. We need to identify these early, as shorting them is what triggers the door to open.
Manual Override: The door leads are usually hooked up to a physical button at the front desk, which lets staff manually open the door.
The Pi: We send you a pre-configured Raspberry Pi (a mini-computer) that handles all the access logic.
Power: Plug the Pi into a power source to get it running.
Network: Use an ethernet cable to connect the Pi to your internet so it can talk to Core.
Scanner: Plug your barcode scanner into the Piās USB port. Scanners are sold separately and are not provided by Core, though we do have a recommended model ā see Recommended Hardware.
Relay: The Pi has a relay that hooks into your doorās wiring (usually in-line with your manual button). Once someone scans a valid barcode, the Pi triggers this relay to "press" the button for you and unlock the door. The relay engages for a pre-set duration, 3 seconds by default.
The Raspberry Pi device bridges your door wiring, your barcode scanner, and our software. It connects to your network via ethernet and stays plugged into power.
Once a member scans a valid barcode, the Pi triggers a relay - effectively "pressing the button" for you - to unlock the door.
The Pi communicates with your local network, so you can monitor entries through your browser. Just check with your IT team to make sure your network supports the local connection link.
Door controller compatibility
The relay only completes a circuit ā it does not supply any power of its own. It will work with any door controller that has a control wire operating on the completion of a circuit, either to trigger the controller directly or to allow power to flow to it.
Where to place the device
The Pi is a mini-computer and must be protected from moisture and excessive heat, both of which can cause serious damage and render the device inoperable.
It is intended for indoor use only and is not suitable for outdoor placement, or for indoor environments with similar conditions such as pool areas and saunas.
The device also needs to reach a standard power outlet, a wired ethernet connection to the branch network, and the door controller via the wire leads coming off the relay.
The Raspberry Pi system supports the following facility access restrictions:
By Waiver
By Addon
By Membership Type
By Gender
By Minimum Age
By Maximum Age
By Time and Membership Type
By Time and Waiver
By Time, During or Outside Business Hours
By Bypass Waiver
Filters can be set when the device is built, and can also be changed remotely afterward.
Who's going through the door
Since the PI is connected to your local network, any computer can see who is going through the door. Most of the time, the PI can be accessed by going to:
However, some networks are not set up to allow this type of connection. Check with your network administrator for the link for your local branch.
Check-ins from the Pi are also recorded in the normal Check In Log, where each device appears as its own searchable user. Unlike the device-hosted page above, the Check In Log can be viewed from anywhere in Core.
Network whitelisting
Each device connects to Core from your branchās IP address, and that address must be on our whitelist. It needs to be added when the device first arrives, and added again any time your branchās IP address changes.
A device that stops working after a network change is most often an un-whitelisted IP address. Our team can connect to the device remotely to retrieve its address and troubleshoot.
Have Questions?
If you have any questions or would like to initiate an order, please contact our team via The Bubble, and we will be happy to assist you.