The Controller card manages the physical board that connects the FAP to your cabin hardware.
Pairing the controller
Power on the controller: on boot it shows a token on its display or Serial port. Paste it into the Token field and press Pair. The device name updates automatically when it sends its first ping.
Once paired you will see its metrics: status (active, pending or revoked), last contact, IP address and firmware version. Remove pairing revokes the device: it will stop working and you will need to pair a new one.
Long-poll timeout
When there is nothing new to report, the controller holds one waiting request open until this limit, in milliseconds, and answers 204 No Content. The default value is 30000 and the range is 5000 to 120000. A higher value reduces the number of requests; a lower value detects changes slightly sooner when reconnecting. For normal use, leave the default.
Ping interval
How often, in seconds, the controller tells the server it is alive. This is an internal Flightdemy setting, only visible to administrators; do not change it unless instructed.
Offline threshold
If the controller sends no ping within this time, in seconds, the server considers it disconnected. The default value is 300 (5 minutes). If your controller shows as disconnected on a good connection, check its internet access before touching this value.
Pulses and blinks
These four parameters, all in milliseconds, adjust the physical behavior of the alerts. The oxygen mask pulse is how long the solenoid stays active: it must be short to avoid forcing the mechanism. The smoke detection, CABIN PRESS and emergency call blinks define the rate of each alert when active.
Cabin lights
The BRT, DIM 1 and DIM 2 levels are the intensity of each lighting level as a percentage, from 0 to 100; the controller converts it to PWM for your LED strips. The transition speed is the time, in milliseconds, the light takes to fade between levels when switching BRT or DIM.
Controller logs
At the bottom you can see the latest received events, with date, IP and payload, and open the full history with date filters. This is the first diagnostic tool when something does not respond.
