Axess Gatekeepers terminal | Web interface guide

The Axess Gatekeeper web interface is your central operational dashboard for on-site setup and deployment. Through this browser-based tool, you can link the turnstile to Palisis, adjust gate closure timings, manage security credentials, and review diagnostic logs.

This step-by-step guide walks you through connecting to the web portal, applying necessary configurations, and verifying communication with your Palisis BackOffice.

What does it mean?

Every Axess gate terminal hosts an internal embedded web server. Accessing this interface allows your technical or operations team to:

• Establish secure communication between the physical gate controller and Palisis API servers.
• Customise passage timings (such as the flap closure delay) to suit your venue's visitor flow.
• Download system logs for diagnostic review and troubleshooting.
• Ensure each gate is accurately mapped to its physical lane and entry point.

What should I do?

Follow the chronological stages below to log in, configure core parameters, and bring your turnstile online.

1. Connecting & logging in

Opening the web interface

1. Connect your configuration laptop to the same local area network (LAN) or subnet as the Axess turnstile (via an Ethernet patch cable or local facility Wi-Fi).
2. Open a standard web browser (Chrome, Edge, or Firefox).
3. Type the terminal's IP address into the address bar (e.g. http://192.168.1.12/) and press Enter.
4. The Axess system login screen will appear.

Initial login credentials

Use the default setup credentials provided for initial access:

Changing the default password

1. Navigate to Configuration > Change Password.
2. Enter a robust new password and confirm the entry.
3. Store the new password securely in accordance with your organisation’s password management policy (e.g. via 1Password).

2. Configuring system & lane identifiers

Navigate to Configuration > System to set up the core identity of the gate:

• poe_name: Enter a name for the terminal, f.e. Palisis.
• poe_project_nr: Enter the project number assigned to your venue (typically 0 for single-project sites).

• Operating mode: Select OEM mode.

  (⚠️ Important: The mode selection field is only visible during the initial setup session. Once saved, it locks in and is no longer displayed on the screen.)

• Lane & entry numbers: Verify that lane1_active is set to true, and confirm the Entry number and Lane number assigned to the gate.

3. API communication parameters

To ensure the terminal can authenticate tickets against Palisis in real time, scroll down to the axoem_api section under Configuration > system:

• axoem_api_url:
  • Production: https://office.palisis.com/pit/axess
  • UAT: https://uat.palisis.com/pit/axess
• axoem_api_authurl:
  • Production: https://office.palisis.com/pit/axess/api/v1
  • UAT: https://uat.palisis.com/pit/axess/api/v1
• axoem_api_clientid: Enter your unattended user username (e.g. unattended+[OwnerID]@palisis.com), provided by your Customer Success Manager or Project Manager.

• axoem_api_tout (Timeout): Set this value to 10000 (10,000 ms / 10 seconds).

  Increasing the timeout threshold ensures multi-ticket redemptions, group passes, and third-party OTA vouchers have sufficient network round-trip time to validate without timing out at the flap.

4. Device parameters: Adjusting the "Close gate delay"

Device-specific mechanics are managed under Devices > Parameter, with sub-tabs for turnstiles (TST) and flap gates (FLP).

While motor speeds, sensor thresholds, and obstacle resistance should remain at factory defaults, you may adjust the Close gate delay to optimise visitor pacing:

How the "Close gate delay" works

The Close gate delay defines how long the glass flaps remain open after a successful scan before closing behind the guest.

• Dual-flap rule: The flap gate consists of two independent motorised flaps. You must configure the exact same value on both flaps, as the system will evaluate either the minimum or maximum value depending on the operational cycle.
• Unit of measurement: Values are entered in units of 100 ms (0.1 seconds), within a range of 0 to 100:

Step-by-step adjustment:

1. Go to Devices → Parameter.
2. Open the FLP subsection (🔴 1).
3. Locate the parameter Close Gate Delay.
4. Enter the desired value.
5. Click the checkmark at the bottom right to confirm the settings (🔴 3).
6. Repeat steps 1-5 for the second flap with the same value.

5. Update

The Update menu allows certified configuration packages and firmware builds to be uploaded to the terminal controller:

• Terminals arrive pre-configured with approved production templates. You do not need to upload new configuration files unless explicitly instructed by a Palisis specialist.
• Archived update records and historical installation logs can be reviewed here if required.

6. Logfiles & system diagnostics

The Logfiles area provides real-time visibility into local controller events:

• Track network calls, sensor trips, and validation requests in files such as guest1.log, lane1.log, and syslog.
• When contacting Palisis Support regarding scan rejections or communication anomalies, download the relevant timestamped log file from this screen to attach to your support ticket.

7. Verifying settings & rebooting

Once all parameters have been entered and saved:

1. Perform a controlled hardware reboot to commit all changes to the non-volatile memory.
2. After the system reboots (approx. 60–90 seconds), perform a test scan with any standard QR code or barcode to trigger device registration. For more information, please visit the article Axess Gatekeepers terminals | How to set up the terminal.

Good to know

Network Isolation: In venues with dedicated guest Wi-Fi and segmented staff VLANs, ensure your management computer is assigned to the operational VLAN. If the gate's IP does not respond to a ping, check your switch port profile or subnet routing.

FAQs