Light desk

Two tents, two clocks: photoperiod windows, Got vs Want hours, the SF1000 twin lamp, sunrise and sunset, manual light hold, catch-up, the DLI estimate and the PPFD map.

• 2×4 MISSING IN WINDOW — the lamp is off inside its lit window.
• CATCH-UP ACTIVE — the hub is making up missed lit hours.
• MANUAL HOLD ON — the lamp is frozen by a hold.
• LIT WINDOW BUYING HEAT — the lamp is on while heat is being bought or dumped; see Climate.

• Got / Want h: lit hours today against the schedule; Deviation today in minutes.
• Lights on, hours, Sunrise min, Sunset min, Min dark h: the schedule. Editors show saving… → saved on hub, and say where the same hub setting is edited elsewhere.
• Schedule source explains itself: 4×8 clock, Schedule follows 4×8 for the 2×4, or a lamp plug task.
• DLI estimate · maker map: running and projected mol/m²/day from the bound fixture's PPFD layers × canopy distance × dim % × hours, with a generic stage band verdict. Canopy distance is yours to set (Settings › Integrations › CannaLib › 4×8 canopy distance (cm) and 2×4 canopy distance (cm)); left empty, the estimate reads at the maker's recommended hang height for the stage and says so. In flower the band follows CO₂ supplemented (Settings › Light): off, 30–40 mol (40–50 in late flower); on, 35–55. When the estimate is under or over its band, a line says what would reach it: a dim level, a canopy distance (only once you set one) or hours of light (never in flower). It is advice only. Labelled maker map everywhere because it is an estimate, not a PAR meter.
• Light control path: what DSC drives and what overrides it (the SF1000's own dimming knob, for example).

The 2×4 lamp is on a hub PWM output (Twin SF1000). You get Auto photoperiod (the schedule runs), a brightness target, sunrise and sunset ramps, and a 24 h lamp history. Manual light hold freezes the lamp at its current on/off and brightness and stops the schedule (and any active catch-up) from moving it until you clear the hold. A lamp toggle first shows the roll-on it will cause (the hold or the auto photoperiod it re-enables), then asks you to confirm, and journals the change. Manual lamp control during the dark period can stress clones; confirm only if you mean it.

Read this first

Releasing a hold during catch-up turns the lamp ON. Catch-up is the hub's, and today it cannot be cancelled from the dashboard (a Cancel catch-up button exists but needs a newer hub firmware to act). If you do not want the lamp on, leave the hold on until the window is over. The same pattern applies to Full Auto and the mister.

The hub has no output for the 4×8 lamp and cannot see it. The photoperiod is a clock only; the lit clock shows the schedule, not a measured lamp. Options: bind a smart plug as Lamp plug · 4×8 so the brain follows the hub's window (on/off only, leave an off-only schedule on the plug); Got then counts the plug's reported on-time (Got · Lamp plug: power at the socket, not a light reading). Or bind a lux sensor to confirm lit state. Black camera frames are not proof of a dark tent.

Match each lamp to a DSC-KitLib fixture (Settings › Light › Devices). With two lamps in a tent, the DLI estimate adds both. The PPFD map card shows the maker's map with Map / 3D / Spectrum / Bands views at the chosen canopy distance, with a dimmer slider that scales the map, and not transcribed where the library has the fixture but not its map yet. Nameplate watts feed the energy estimate and tariff cost.

Shifting a schedule or flipping to 12/12 is an explicit, confirmed action (a shift plan without confirm is refused). Learning surfaces a suggestion when timing outliers become the norm; it does not act on a single day.

Guide contents  ·  Using the dashboard  ·  Troubleshooting  ·  Digital Stealth Care

DSC-Brain user guide · Light desk · this page is edited on the site; the Notion original was retired after the mirror