The perimeter LED assembly is documented as a status and interaction layer. It is not treated as a calibrated horticultural light source.
Purpose
The perimeter lighting communicates operating state, warnings, service conditions and user interactions without changing the central cultivation-light recipe. Colour assignments are interface states and are versioned in the software configuration.
| Function | Required behaviour | Research relevance |
|---|---|---|
| Normal operation | stable, low-glare indication | must not alter a declared dark period |
| Warning | visible, distinct state | event is written to the operating record |
| Critical fault | unambiguous alert | associated actuator state and timestamp are preserved |
| Service mode | local identification of the active module | prevents maintenance events from being hidden in a trial |
Engineering requirements
- exact LED family and revision recorded in the bill of materials;
- maximum and typical channel current measured on the installed assembly;
- voltage drop measured at the first, middle and final segment;
- surface and enclosure temperature recorded at worst-case command;
- power-supply headroom, connector rating and conductor cross-section documented;
- brightness limited for night operation and camera acquisition;
- status meanings remain accessible through text or the dashboard and do not rely on colour alone.
Validation plan
Bench validation records current, voltage, temperature and command latency for representative patterns. Optical validation records spectrum and PPFD at plant positions with the central lamp off and on. Trial protocols state whether perimeter lighting was disabled, constant or included in the measured recipe.
Permitted claims
The website may state that the v2.0 architecture includes addressable perimeter status lighting. It may not state that the subsystem supplements photosynthesis, improves flowering or delivers a defined wavelength until a component-specific spectrum and plant-position photon map are published.