Skip to content

Connecting the hardware

How Protequ reaches it

Protequ talks to each Suprema BioStation 3 terminal over your IP network. Each terminal is reached at its IP address on TCP port 51211 (the Suprema default). You give Protequ the terminal's address, and that is the whole link — there is nothing else to install or set up between them.

Before you start

  • The BioStation 3 is mounted, powered (mains or PoE), and finished booting. It takes about 30 seconds after power-up before the idle screen appears.
  • The terminal has an IP address on the same network the Protequ server can reach. Use a fixed address or a DHCP reservation so it does not change later.
  • You know that IP address. There is no network scan in Protequ; you must enter the address yourself.
  • TCP port 51211 is open between the Protequ server and the terminal. Any firewall in between must allow it.
  • No login for the terminal is needed in Protequ. The connection carries no username or password and no certificate.

On the equipment

  1. On the BioStation 3, open the network settings from the on-device menu.
  2. Give the terminal a reachable IP address. Either turn on DHCP and reserve the address on your DHCP server, or set a fixed IP, subnet mask, and gateway by hand.
  3. Leave the connection so the terminal waits for the server to reach it (server-to-device mode). This is the terminal's normal setting.
  4. Keep the terminal's port at 51211 unless your site requires a different one. If you change it, note the new number for the next step.
  5. Confirm the terminal shows it is on the network before leaving it.

In Protequ

Add one BioStar Suprema 3 Access Device in Protequ and fill in these fields on the configuration page:

Value you set above Field in Protequ Notes
Terminal IP address ip_address The address of this one BioStation 3 unit
Terminal port port Default 51211; change only if you changed it

Each device entry connects to exactly one physical BioStation 3.

Confirm it works

This adapter supports discovery. After the device entry saves and shows Connected, run discovery on it. The terminal's doors and their reader sides are read back and appear as child items in Protequ automatically. You do not add doors by hand first.

To check the link itself:

  • The device's connection status shows Connected within about 30 seconds of saving.
  • A connect event appears in the Protequ event log.
  • Present an enrolled face or card at the terminal; an access event appears in the log and the door strike fires.

If it does not connect

  • Status stays disconnected, connecting repeats. Ping the terminal from the Protequ server to confirm the IP is right and reachable. Check that no firewall blocks TCP 51211 between the server and the terminal. If you just powered the terminal, wait for its idle screen before retrying.
  • Wrong or changed IP address. A DHCP address can move if it was not reserved. Correct the ip_address field, or pin the terminal to a fixed address, then save again.
  • Port mismatch. If someone changed the terminal's port, the port field in Protequ must match it exactly. Set both to the same number.
  • Doors do not appear after discovery. Confirm the device shows Connected first, then run discovery again. Discovery reads the door layout from the terminal, so the link must be up.