Contact Us

Phone: +86 19540588776
WhatsApp / Wechat: +86 19540588776
Email: info@yunshao.com
Address: Building 6, Guanlan High-tech Industrial Park, Longgang District, Shenzhen City, Guangdong Province, China

Page Catalog

Turnstile Gate Access Control Integration Guide
How Turnstile Gate Access Control Integration Works
Example: Integrating an RFID Reader with an Existing Access Controller
Key Components of an Integrated Turnstile System
Turnstile Integration Interfaces and Protocols
Integrating RFID, QR Code and Facial Recognition
Installation, Configuration and Testing Checklist
Common Turnstile Integration Problems and Solutions
Information Required for Turnstile Integration
Turnstile Gate Types for Access Control Integration
Why Choose YUNSHAO?
FAQ
Related Articles

Turnstile Gate Access Control Integration Guide

A turnstile gate can control physical passage, but a complete entrance system must also verify credentials, apply access rules, communicate with software, and record entry events. This turnstile gate access control integration guide explains how these components work together—and what project teams should confirm before installation.

How Turnstile Gate Access Control Integration Works

In an integrated system, a reader or biometric terminal collects a credential. The access controller or connected platform decides whether that person is authorized. If approved, the appropriate interface requests a single passage from the turnstile controller. The gate then uses its own motor control and safety sensors to manage movement and reset after passage.

STEP 01: Identify
Present an RFID card, QR credential or supported biometric identifier.

STEP 02: Authorize
Check identity, access schedule, location and permission rules.

STEP 03: Release
Send a compatible, direction-specific opening command to the gate.

STEP 04: Confirm
Monitor actual passage, reset the barrier and log the event where configured.

An authorization event and a completed passage are not always the same. Good integration distinguishes a valid credential, an opening command, a successful passage, and an unused or timed-out authorization.

Example: Integrating an RFID Reader with an Existing Access Controller

Consider an office where employees already use RFID cards and an existing access controller. The project team wants to add a turnstile without replacing the credential database. A typical integration can use the existing controller’s authorized relay output to request entry from the turnstile.

RFID Reader

Existing Access Controller — checks permission

Authorized Relay / Dry-Contact Output

Turnstile Control Board — entry command, sensors and gate movement

Optional return path: A supported passage-complete or status output from the turnstile can be wired or mapped back to the access controller. Not every gate/controller combination exposes the same feedback signals.

What the integrator must confirm: the correct entry/exit input, dry-contact requirements, pulse duration, electrical isolation, credential reader format, passage feedback availability and handling of an authorized user who does not pass through. This is a logical example, not a model-specific wiring diagram. Use the supplied terminal map and approved electrical drawings for installation.

Key Components of an Integrated Turnstile System

Turnstile gate and gate control board: Operate the barrier, passage sensors, direction indicators and relevant safety functions.
Credential reader or terminal: Reads cards, QR/barcodes or biometric credentials. Some terminals include local access-control functions.
Access controller: Applies or receives access decisions and communicates with the gate through supported inputs and outputs.
Management software: Manages users, access levels, schedules, visitor permissions and event records, according to the selected platform.
Network, power and safety interfaces: Provide reliable communication, correctly rated power, emergency behavior and monitoring.

Engineering distinction: The turnstile controller governs physical movement and safety. Access permissions are normally decided by a connected controller or credential platform. Never bypass the gate’s safety logic with a software integration.

Turnstile Integration Interfaces and Protocols

Different interfaces serve different purposes. A project should specify the exact signal, message format and supported functions—not simply ask whether the gate “supports TCP/IP.”

Interface	Typical integration role	What to verify
Relay / dry contact	Simple authorized entry or exit request to a compatible gate input	Contact type, pulse duration, direction mapping, isolation and feedback
Wiegand	Credential data transfer from certain readers to controllers	Bit format, wiring distance, credential format and security limitations
OSDP (including Secure Channel where supported)	Reader-to-access-controller communication using an interoperable protocol	OSDP support at both endpoints, Secure Channel configuration, addressing, wiring and firmware compatibility. OSDP on a reader does not imply OSDP support on the gate mainboard.
RS-485 / RS-232	Serial communication between supported readers, controllers or devices	Protocol specification, addressing, baud rate and command support
TCP/IP / Ethernet	Network transport for compatible controllers, terminals and management software	Actual application protocol, ports, network security and outage handling
API / SDK	Software integration for authorization, credential management or event exchange	Available endpoints, authentication, licensing, documentation and ownership

A relay input is not an API, and an Ethernet port does not guarantee open software integration. Obtain the specific controller and terminal documentation before finalizing the architecture.

Integrating RFID, QR Code and Facial Recognition

RFID access control is commonly used for employees, residents and long-term users. Check card technology, reader output, credential enrollment and whether the existing access controller can authorize the selected reader.

QR code and barcode access is useful for visitors, tickets and temporary access. The project must define who issues the code, where validity is checked, whether it can be reused and how offline validation works. For a detailed explanation, read our QR Code Turnstile Access Control Systems guide.

Facial recognition may support touchless entry where appropriate. Confirm terminal compatibility, recognition conditions, liveness capabilities where required, enrollment processes, data protection obligations and an alternative access method. See Turnstile Gate with Facial Recognition for a closer look at biometric configurations.

Multiple credential methods can share a turnstile lane, but the access controller and software must resolve conflicting commands and apply consistent permissions.

Connecting Turnstiles with Third-Party Building Systems

Integration often extends beyond the entrance lane. In commercial office buildings, visitor management software may issue temporary access credentials. A compatible elevator access control system can map the same authorized identity to permitted floors. Membership systems may validate gym access, while ticketing platforms can enforce single-use admission rules.

For each external system, agree on the source of truth for users and permissions, which system makes the access decision, how events are synchronized, and what happens when one service is unavailable. Document API responsibilities, cybersecurity controls and data retention before deployment.

Emergency egress requires separate review. Fire alarm interfaces, power-loss behavior, manual release and accessible routes must comply with the approved project design and local requirements. A software “open” command is not a substitute for compliant life-safety engineering.

Installation, Configuration and Testing Checklist

Use the following checklist during technical review and commissioning:

Check	Acceptance question
Gate selection	Does the mechanism suit traffic volume, lane width and security requirements?
Wiring and power	Are cable routes, voltage, grounding and signal isolation documented?
Input/output mapping	Do entry, exit, passage feedback and alarm signals match the controller?
Credential validation	Are valid, expired, revoked and duplicate credentials handled correctly?
Timing	Does the gate reset correctly after passage, timeout or an abandoned scan?
Network failure	Is the offline/failover policy defined and tested?
Safety and accessibility	Are obstruction detection, emergency behavior and accessible routes verified?
Logs and cybersecurity	Are timestamps, access events, authentication and network protections checked?
Handover	Are wiring diagrams, interface documents, test results and support contacts supplied?

Test the full workflow with the actual third-party software and installed devices, not just a standalone gate opening test.

Common Turnstile Integration Problems and Solutions

When an access-controlled gate does not behave as expected, first identify which component made the access decision and whether the turnstile received the correct command. The examples below are diagnostic starting points, not instructions to bypass safety functions.

Problem	Possible cause	Recommended check
Credential is accepted, but the gate stays closed	Incorrect relay wiring, pulse configuration or entry/exit input mapping	Check controller event logs, rated contact type and the gate’s documented command input.
Gate opens in the wrong direction	Entry and exit commands reversed	Verify the input-to-direction mapping and test each direction independently.
Access is granted, but no completed-passage event appears	Missing feedback connection or software event mapping	Determine whether the gate provides a passage output and whether the controller records it.
QR code works once but fails for a valid visitor	Expired token, duplicate-use policy, clock mismatch or connectivity problem	Review issuer/validator logs, validity window, time synchronization and offline policy.
Intermittent reader communication	Power, cable, addressing or protocol mismatch	Review the reader/controller manuals, cable specification, grounding and device diagnostics.
Emergency release does not match the approved design	Incorrect interface, configuration or misunderstanding of fail-safe behavior	Stop commissioning and have qualified personnel verify the fire/life-safety design and device documentation.

Information Required for Turnstile Integration

Before requesting a quotation or technical proposal, provide enough information to establish whether the existing access control system can work with the selected turnstile. A clear project brief can prevent incompatible hardware orders and unnecessary on-site modifications.

Site and lane details: application, indoor/outdoor environment, number of lanes, clear passage width, entry/exit direction and expected peak traffic.
Existing hardware: reader/terminal manufacturer and model, access controller model, available inputs/outputs and current wiring diagrams.
Software and credentials: platform name/version, RFID card technology or QR format, authorization workflow and available API/SDK documentation.
Required integration functions: open command, passage confirmation, anti-passback, visitor validity, event logs, offline behavior and remote monitoring.
Safety and infrastructure: approved emergency egress design, power supply, network topology, cable routes and applicable accessibility requirements.

Practical procurement tip: Send the access controller model and its wiring/interface manual together with the gate requirements. The presence of a common connector or transport protocol alone does not establish functional compatibility.

Turnstile Gate Types for Access Control Integration

YUNSHAO offers eight turnstile gate categories for different access control and entrance management applications. Depending on the model and project requirements, these gates can be integrated with RFID card readers, QR code scanners, facial recognition terminals, access controllers and third-party management systems. Explore the options below to identify a suitable configuration for your project.

Product classification note: The first six categories describe turnstile mechanisms. Ticketing Turnstile Gates and Automated Border Control Gates are application-specific solutions that may use similar underlying hardware. For a comparison of mechanical designs, see the Turnstile Gate Types Comparison guide.

Final selection should consider accessibility, emergency egress, pedestrian throughput, installation conditions and the destination market. Interface availability and integration functions must be confirmed for the selected model.

Why Choose YUNSHAO?

Founded in 2010 in Shenzhen, China, YUNSHAO manufactures pedestrian turnstile gates and supports OEM/ODM customization for distributors, project contractors and system integrators. Depending on the selected configuration, we can assist with compatible RFID readers, QR scanners, facial recognition terminals, access controllers, interface selection and technical coordination.

YUNSHAO turnstile gates include a three-year limited warranty for qualifying manufacturing defects, subject to the published Warranty Policy, plus lifetime technical support. Final integration scope and compatibility should be confirmed against the specific project requirements.

FAQ

Can a turnstile gate connect to an existing access control system?

Often yes, provided the existing controller and selected gate support compatible opening inputs, credential interfaces or documented communication methods. Confirm the exact wiring and functional requirements before ordering.

Does a turnstile gate need its own access controller?

The gate has a controller for barrier movement and safety. Credential authorization may be handled by a separate access controller, an intelligent terminal or another compatible platform, depending on the architecture.

Is TCP/IP enough to integrate a turnstile with third-party software?

No. TCP/IP provides network transport, but software integration also requires a compatible application protocol, documented API or SDK, or another supported communication method.

Can RFID, QR code and facial recognition share one turnstile?

Some configurations support multiple readers or terminals. The controller must coordinate authorization, direction, input priority and passage feedback. Physical mounting space and device compatibility should also be checked.

Does OSDP support on my reader mean the turnstile supports OSDP?

No. OSDP generally connects a reader to a compatible access controller. The controller may separately command the turnstile through relay inputs or another documented interface. Verify each link independently.

What should be tested before a turnstile system goes live?

Test valid and invalid credentials, both travel directions, passage timeout, obstruction detection, event logging, network failure, power-loss behavior and approved emergency release arrangements using the actual installed system.