A320 FAP Trainer - Kiosk mode and hardware

Guide for physical simulator installations: how to open the FAP in kiosk mode, how the Hardware add-on works, how to pair the screen controller and the controller, and how to solve the most common problems.

Updated: 18/11/2026

Hardware integration and kiosk mode

What hardware integration is

Hardware integration connects the A320 FAP Trainer to a real cabin simulator or mock-up. The FAP is shown on a screen installed in the cabin, in kiosk mode, and a controller board links it to your hardware: the physical seat belts switch changes the FAP instantly, annunciators and lights turn on in your panel, and the instructor can trigger smoke machines or oxygen masks. It requires the Hardware add-on on your license.

Connection diagram: screen controller, controller and hardware

The pieces of a hardware installation.

This guide covers kiosk mode, the add-on, pairing the screen controller and the controller, and how to solve common problems. For using the app itself, see the A320 FAP Trainer user guide.

Kiosk mode

Kiosk mode opens the FAP full screen and without signing in, for the computer installed in your simulator or mock-up. It does not show the sidebar: the scenario is controlled from the app, the instructor station or the hardware.

Where to find the link

Each license has a personal link like flightdemy.com/fap/…. You will find it in the Configurator, Hardware tab, as the Screen controller URL. Use Copiar (Copy) to take it to the simulator computer and set it as the browser home page or shortcut.

The first-device rule

For security, the link is paired with the first device that opens it. From then on only that device can use it; any other will see a notice that the code is already paired. To change device, press Desvincular (Unpair) in the Hardware tab and open the link on the right device. If you think someone else knows your link, use Regenerar (Regenerate) to create a new one and invalidate the old one.

Start-up

With the start overlay enabled, the kiosk starts with the FAP Screen screen: tap Comenzar (Start) to enable audio and, if configured, full screen. Browsers require this first tap, so it cannot be skipped entirely.

Kiosk mode start screen

The kiosk start screen: one tap enables audio and full screen.

If your license includes the hardware add-on, the kiosk tries to reach the controller at start-up. If it cannot, it shows ConexiĂłn perdida (Connection lost): Reconectar tries again and Continuar offline opens the FAP without hardware.

Connection lost notice

The connection lost notice appears when the kiosk cannot find the controller.

The Hardware add-on

The Hardware add-on extends your FAP Trainer license to connect the trainer to a physical cabin. Without it, the FAP works fully on screen; with it, the FAP reads your switches and drives real lights and mechanisms.

The two pieces

  • Screen controller: the browser on the computer that shows the FAP in kiosk mode. It is paired by opening the Screen controller URL.
  • Controller: a board (Arduino or compatible) wired to your hardware, with inputs for switches such as seat belts or doors, outputs for LEDs and annunciators, PWM outputs for cabin lights and commands for accessories such as smoke machines. It is paired with the token it shows at start-up.

What it adds in practice

The physical seat belts switch changes the FAP state instantly, emergency lights and annunciators light up on your panel, doors with sensors show on Doors/Slides, and the FAP or the instructor station can trigger the smoke machines, the electrical failure or the oxygen masks.

Network requirements

The controller and the screen controller computer must be on the same local network (the same router). The controller also needs internet access to validate the license and send its pings. Pairing each piece is explained in the next two articles.

Hardware: Screen controller

The Screen controller card in the Hardware tab defines how the computer that shows the FAP in kiosk mode behaves.

Hardware tab of the Configurator

The Hardware tab: Screen controller on the left and Controller on the right.

Screen controller URL

This is the kiosk mode link. Copiar (Copy) puts it on the clipboard and Abrir (Open) opens it in a new tab. Below it you will see the paired device and the pairing date:

  • Desvincular (Unpair) releases the link: it stays valid, but will pair with the next device that opens it.
  • Regenerar (Regenerate) creates a new link and invalidates the old one and the paired device. Use it only if you think someone else knows your link.
Screen controller settings

Screen controller settings: full screen, start overlay, logs, timeout and grace period.

Settings

  • Automatic full screen: the browser goes full screen on the first tap. It cannot happen without that tap: it is a browser restriction.
  • Start overlay: shows the FAP Screen with the Comenzar (Start) button, which enables audio and full screen. If you disable it, the system tries to start on its own; test it on your computer, since some browsers block audio without that gesture.
  • Logs de debug (debug logs): the controller sends diagnostic messages to the server and to its Serial port. Enable it if support asks you to.
  • Initial connection timeout: maximum time, in milliseconds, the kiosk waits for the controller’s first reply before showing Connection lost. Default 1500; raise it to 3000–5000 on a slow network.
  • License grace period: extra time, in seconds, the controller keeps working if the license or the add-on stop being active, for example during a renewal.

Hardware: Controller

The Controller card in the Hardware tab manages the board that connects the FAP to your physical cabin.

Pairing the controller

Power on the controller: at start-up it shows a token on its screen or Serial port. Type it or paste it with Pegar (Paste) into the Token field and press Vincular (Pair). The device name updates automatically when it sends its first ping.

Once paired you will see its status (active, pending or revoked), last contact, IP address and firmware version. Removing the pairing revokes the device: it stops working and you will need to pair a new one.

Communication settings

  • Long-poll timeout: how long, in milliseconds, the controller keeps a waiting request open. Default 30000 (range 5000–120000). Leave it as is for normal use.
  • Offline threshold: if the controller does not ping within this time, in seconds, it is considered disconnected. Default 300. If it shows as disconnected on a good connection, check its internet access before changing this value.

Pulses, blinks and lights

  • Oxygen mask pulse: time, in milliseconds, the solenoid stays active. Keep it short so the mechanism is not strained.
  • Blink rates for smoke detection, CABIN PRESS and emergency call, in milliseconds.
  • Cabin lights: BRT, DIM 1 and DIM 2 intensity as a percentage (0–100), which the controller converts to PWM for your LED strips, and the transition speed between levels.

Controller logs

At the bottom of the card you will see the latest events received, with date, IP and content, and you can open the full history with date filters. It is the first diagnostic tool when something does not respond.

Troubleshooting

"This code does not belong to your account"

You are opening another license’s kiosk link, or you are not signed in with the account that owns the license. Always use the URL from your own Configurator, Hardware tab.

The link opened on the wrong device

It paired with the first device that opened it. In the Hardware tab, press Desvincular (Unpair) and open the link on the right device. If someone else may have seen it, use Regenerar (Regenerate).

"ConexiĂłn perdida" (Connection lost) when the kiosk starts

The kiosk did not hear from the controller in time. Check that the controller is powered, paired and on the same local network as the FAP computer, then press Reconectar. On a slow network, raise the initial connection timeout. To practice without hardware, press Continuar offline.

The controller shows as disconnected

Check the controller’s power and internet connection. Open its logs: if there are no recent pings, restart it. Also check that it has not been revoked.

Commands do not reach the hardware

Enable Logs de debug and repeat the action. If the event appears in the logs, the problem is the wiring or the controller pin; if it does not, it is communication between the FAP and the controller: check that both are on the same router.

The kiosk does not show my changes

Press Save configuration and hard-refresh the kiosk: the computer’s browser may keep the previous version in cache.

There is no sound in the kiosk

Tap Comenzar on the start screen: browsers require that first gesture to enable audio. If you disabled the start overlay, tap anywhere on the screen.

Didn't find what you were looking for?

Our team is ready to help. Reach out via our contact page and we'll get back to you as soon as possible.

Contact us