Find your answer.
Planer — building projects, luminaire placement and AirBUS connectivity
Load floor plans, draw walls, select catalogue luminaires and estimate 868 MHz radio connectivity.
Standard and Gessler LED indication — reading luminaire faults
Distinguish the status LED from the main light. Function test, readout after complete power removal and an animated single-luminaire simulator.
Connecting EZF — interactive connector guide
Select a number on the drawing or choose a connector below. Enlarge the drawing to read printed labels.
Controller — language settings
MENU → second page → Settings → Language. PL, DE and EN flags, saving on exit and a display image for each step.
Controller — set the clock, date and NTP
RTC clock: set time and date manually or use NTP synchronization, correction and Summer time mode. Separate procedures with display screens.
Controller — device name
MENU → Settings → Ctrl name. Keyboard editing, saving with OK and checking the name in Information, with display screens.
Network — controller Access Point mode
Enable the controller’s own Wi‑Fi network and read connection details in INFO.
AirBUS — delete one luminaire
Remove one specified address, including the confirmation screen.
Import a luminaire list from CSV
Prepare and validate a list for AirBUS, BUS1 or BUS2, then import it over USB.
Web Master — setting up the integration
Connect Web Master to an EZF controller, synchronise luminaires and read their status.
Modbus IP — configuration and status monitoring
Enable Modbus TCP, check the register map and test AirBus luminaires.
EZF API — JSON, TSV and error handling
HTTP request examples, luminaire IDs, NVG diagnostics and error codes.
USB drives for the controller: FAT32 and exFAT
Prepare a USB drive, check format compatibility and resolve errors.
Meet the EZF control unit
Your starting point for luminaires, tests and system documentation.
BUS and AirBUS. Find your luminaire
The address, channel and location help identify a device unambiguously.
Function test and duration test
How the tests differ and why the configured duration matters.
Results, reports and the event log
Keep the test context and prepare a clear service request.