17871249862986 副本 scaled
  • Home
  • Solution details
Solution

Custom Communication & Protocols

Different access control projects use different system architectures.

VELAXIZ supports custom communication interfaces and protocols for turnstiles and speed gates, helping system integrators connect pedestrian gates with access control controllers, management platforms and other third-party systems.

Depending on the selected model and project requirements, communication options can include RS232, RS485, TCP/IP and dry contact interfaces.

The appropriate communication method can be selected according to the existing system architecture and integration requirements.


RS232 Communication

RS232 is a commonly used serial communication interface for direct communication between devices.

It can be used where the turnstile needs to exchange data or commands with a nearby controller or system device.

RS232 communication is suitable for applications that require:

  • Direct device connection
  • Short-distance communication
  • Command transmission
  • Equipment configuration
  • System debugging

The exact communication structure depends on the turnstile controller and the connected third-party device.


RS485 Communication

RS485 is widely used in access control and industrial automation projects.

Compared with point-to-point communication, RS485 is suitable for environments where multiple devices may need to communicate over a shared communication line.

Typical applications include:

  • Multi-lane turnstile installations
  • Access control systems
  • Building management systems
  • Industrial entrance projects
  • Centralized device management

RS485 can provide a practical communication option for projects requiring stable wired communication between turnstiles and control equipment.


TCP/IP Communication

For network-based projects, selected VELAXIZ turnstiles can support TCP/IP communication.

TCP/IP allows the turnstile controller to connect to a local network and communicate with compatible management software or control systems.

This can be useful for:

  • Centralized system management
  • Network-connected entrances
  • Multiple access points
  • Remote device communication
  • Large building projects
  • Multi-site system architectures

Network communication provides greater flexibility for modern access control projects where devices are managed through an IP-based infrastructure.


Dry Contact Interface

Dry contact is one of the simplest and most widely used methods for connecting a turnstile with a third-party access control controller.

After the access control system verifies a user, the controller sends an opening signal to the turnstile.

The turnstile then performs the required opening action.

Dry contact integration is particularly useful when the project already has an existing:

  • Access control controller
  • Card reader system
  • Biometric controller
  • Visitor management system
  • Ticketing controller
  • Third-party security system

Because the access control system and turnstile can operate as separate components, dry contact provides a straightforward integration method for many projects.


Third-Party System Communication

Many system integrators already have their own access control software or hardware platform.

In these projects, the turnstile needs to communicate with the existing system rather than operate as a standalone device.

VELAXIZ can evaluate the required communication method according to:

  • Existing access control architecture
  • Controller type
  • Communication interface
  • Required commands
  • Device status feedback
  • System integration requirements

This allows the turnstile to become part of the customer’s existing entrance control infrastructure.


Command and Status Communication

Communication between the turnstile and the control system may include different types of information.

Depending on the selected controller and integration method, communication can be used for functions such as:

  • Open gate command
  • Left-direction opening
  • Right-direction opening
  • Gate closing
  • Passage authorization
  • Device status
  • Alarm status
  • Passage status
  • Operating mode control

The available commands and feedback depend on the product controller and communication protocol.


Custom Protocol Requirements

Some projects require communication with a specific third-party platform or controller.

Where technically feasible, protocol requirements can be evaluated according to the customer’s integration documentation.

Useful information may include:

  • Communication protocol documentation
  • Interface specifications
  • Command format
  • Data structure
  • Baud rate requirements
  • Network parameters
  • Control logic requirements

Providing clear protocol documentation during the early stage of the project can help simplify integration and testing.


Communication for Multi-Lane Turnstiles

Large entrance projects often use several turnstile lanes operating together.

A suitable communication architecture can help the management system control and monitor multiple lanes from a centralized platform.

Depending on the project design, each turnstile may communicate individually with the control system or operate as part of a larger access control network.

Proper communication planning is particularly important for:

  • Office lobbies
  • Corporate campuses
  • Factories
  • Transportation facilities
  • Stadiums
  • Large commercial buildings

Choosing the Right Communication Method

The most suitable communication method depends on how the complete access control system is designed.

Dry Contact
Suitable for simple and reliable opening signal integration with third-party controllers.

RS232
Suitable for direct serial communication over shorter distances.

RS485
Suitable for stable wired communication and multi-device applications.

TCP/IP
Suitable for network-based management and larger system architectures.

The correct interface should be selected according to the existing controller, software platform and required level of communication.


Connect the Turnstile to Your Existing System

A turnstile should not force system integrators to redesign an entire access control architecture.

VELAXIZ supports multiple turnstile communication interfaces and protocols, including RS232, RS485, TCP/IP and dry contact, helping pedestrian gates connect with compatible third-party systems.

If your project requires a specific communication method or protocol, provide your interface requirements or protocol documentation.

Our technical team can evaluate the integration requirements and recommend a suitable communication configuration.


FAQ

What communication protocols can a turnstile support?

Depending on the model and controller, available communication options may include RS232, RS485, TCP/IP and dry contact interfaces.

Can VELAXIZ turnstiles connect to third-party access control systems?

Yes. Selected turnstiles can communicate with compatible third-party controllers and management systems through supported interfaces.

What is dry contact integration?

Dry contact integration allows a third-party access control controller to send a simple opening signal to the turnstile after successful authorization.

Can turnstiles use RS485 communication?

Yes. Selected turnstile controllers can support RS485 for wired communication with compatible systems.

Can turnstiles connect through TCP/IP?

Yes. Selected models can support TCP/IP communication for network-based system integration.

Can you support a custom communication protocol?

Custom protocol requirements can be evaluated based on the project, turnstile controller and technical documentation provided by the customer.

What information should I provide for protocol integration?

It is helpful to provide the required interface, communication protocol documentation, command structure, system architecture and controller information.

Online Message

If You Are interested in Our Products, please Leave Us A Message Below Along With Your Contact information.
We Will Get inTouch With You As Soon As Possible.Thank You!