Power Budget & Energy Management. ciddiyetii ile yaz lütfen

Below is a Power Budget & Energy Management section written aynı SRD ciddiyetinde, İngilizce ve doğrudan SRD’ye eklenebilir formatta.

---

6.0 POWER BUDGET & ENERGY MANAGEMENT

6.1 Power Architecture Overview

Each HIVE SCOUT node is designed as an energy‑autonomous field device.
The power architecture shall:

• Support 24/7 operation in harsh outdoor conditions.
• Accommodate both baseline sensing (gas + environmental) and peaky loads (PURGE fan, LTE uplink, electro‑optical suite).
• Enforce deterministic power‑down behavior, ensuring that critical safety and communication functions are prioritized as energy becomes limited.

The main power elements per node are:

• Primary storage: LiFePO₄ battery pack.
• Energy harvesting: Solar panel(s) sized for worst‑case seasonal conditions.
• Power electronics: MPPT solar charger, DC/DC converters (e.g. 12.8 V → 5 V and 3.3 V rails).
• On‑board power management logic integrated with firmware state machine.

---

6.2 Power Domains and Loads

For power budgeting, node electronics are grouped into logical power domains:

1. Core Domain (Always‑On in NORMAL/DEGRADED)

• MCU (Cortex‑M4/M33)
• Core gas sensors: PID, NDIR, RH/T, pressure, anemometer
• Essential telemetry (LTE Cat‑M1 or equivalent)
• Safety‑critical functions (WDT, fault detection, minimal logging)

1. Electro‑Optical Domain (Duty‑Cycled / Conditional)

• Thermal camera (LWIR/MWIR)
• Ultra‑low‑light sCMOS camera
• Active NIR illumination (LEDs/lasers)

1. Mechanical Actuation Domain

• Micro‑compressor / purge fan
• Any auxiliary actuators (e.g. motorized shutters, if used)

1. Auxiliary Domain (Optional / Low Priority)

• Night vision contextual module (if separate from sCMOS)
• Local indicators (LEDs), maintenance ports, etc.

Each domain’s average and peak power consumption shall be quantified during detailed design.
Firmware shall be capable of individually enabling/disabling these domains based on:

• Node state (INIT, WARMUP, NORMAL, PURGE, DEGRADED, FAULT)
• Battery state of charge (SoC)
• Mission profile (e.g. night‑focused vs. continuous surveillance)

---

6.3 Typical Power Consumption Profile (Qualitative)

Indicative behavior (numbers to be finalized in detailed design):

• INIT / WARMUP
• MCU: active
• Core gas sensors: ON
• Electro‑optical suite: OFF or minimal (for alignment checks only)
• Telemetry: low‑duty or disabled until stabilization.
• NORMAL
• MCU: active, full rate
• Core gas sensors: ON (continuous or periodic sampling)
• Electro‑optical suite:
  • Thermal + sCMOS: duty‑cycled (e.g. imaging every X seconds or on demand)
  • Active NIR: pulsed only when needed (e.g. low ambient light + interest in aerosol density)
• Telemetry: periodic MQTT messages at configured interval.
• PURGE
• MCU: active
• Purge fan/compressor: ON at maximum for a short, predefined duration
• Sensing: mostly off or limited; telemetry sends “PURGE” status
• Electro‑optical: typically OFF during active purge (optional).
• DEGRADED
• MCU: active
• Only healthy sensors ON; failing domains can be powered down to save energy
• Electro‑optical suite: may be disabled or heavily duty‑cycled
• Telemetry: reduced rate but still reporting reliability_score and fault flags.
• FAULT
• All non‑essential domains OFF (sensors, optics, fan).
• MCU: deep sleep or minimal activity; only reset circuitry and critical monitoring remain.
• Telemetry: a single “Last Gasp” message if enough energy remains, then shutdown.

---

6.4 Battery and Solar Sizing Requirements

6.4.1 Battery Technology

• Chemistry: LiFePO₄ (lithium iron phosphate) or equivalent, chosen for:
• High cycle life,
• Thermal stability,
• Compatibility with outdoor temperature range.
• Battery pack shall support at least a defined number of days of operation without solar input in winter worst‑case (to be specified, e.g. 3–5 days).

6.4.2 Solar Harvesting

• Solar panel sizing shall consider:
• Local insolation data (latitude, season, typical cloud cover).
• Node average daily energy consumption, including electro‑optical duty cycles.
• Worst‑case seasonal scenario (shortest day, highest load, coldest temperature).
• Panels shall be mounted with tilt and orientation optimized for the target location and vandal‑resistance.

6.4.3 Design Targets (to be finalized)

• Daily energy budget per node (Wh/day) calculated from:
• Core Domain average power × 24 h,
• Electro‑Optical Domain duty‑cycled usage,
• Mechanical Domain PURGE usage (expected frequency),
• Telemetry overhead (LTE transmissions, keep‑alives).
• Battery capacity (Wh) shall be no less than:
• Daily Energy Budget × Days of Autonomy × safety factor.
• Solar array daily energy production (Wh/day) shall exceed the daily budget by a safety margin in worst‑case winter conditions.

---

6.5 Energy‑Aware State Machine Behavior

Power status is tightly coupled to the node’s firmware state machine.

6.5.1 Battery State of Charge (SoC) Thresholds

Define multiple SoC thresholds, e.g.:

• SoC_HIGH – normal operation (e.g. > 60%)
• SoC_MEDIUM – selective load shedding (e.g. 30–60%)
• SoC_LOW – critical saving, pre‑fault (e.g. 10–30%)
• SoC_CRITICAL – imminent shutdown (e.g. < 10%)

6.5.2 Behavior by SoC

• SoC_HIGH:
• All planned functions enabled according to mission profile.
• Electro‑optical suite fully available (though still duty‑cycled).
• SoC_MEDIUM:
• Optional/contextual functions (e.g. continuous night‑vision streaming) reduced or disabled.
• Electro‑optical suite used primarily on event/alert basis.
• Core gas and environmental sensing preserved.
• SoC_LOW:
• Mechanical loads (PURGE fan) limited to essential cycles.
• Electro‑optical suite largely disabled except for critical checks.
• Telemetry interval may be increased (less frequent messages).
• SoC_CRITICAL:
• Immediate transition to a safe state (DEGRADED or FAULT).
• Priority: send last telemetry with clear “LOW POWER / SHUTDOWN” status, then disable non‑critical loads and enter deep sleep.

6.5.3 Power Faults and FAULT State

• Voltage instability (VCC fluctuations) and abnormal power behavior shall be treated as hardware safety events, triggering transition to STATE_FAULT with all high‑current domains powered down, except for what is needed to send a final message and await reset.

---

6.6 Energy Management Policies for Electro‑Optical Suite

Given that thermal imaging and active NIR illumination are comparatively high‑power consumers, their use shall be governed by explicit policies:

• Duty‑Cycling
• Electro‑optical acquisitions scheduled at intervals (e.g. every N seconds/minutes) or only when gas‑based indicators suggest a possible plume.
• Event‑Triggered Operation
• sCMOS + NIR scattering may be activated when:
  • Cross‑reference logic (gas + RH + wind) indicates a possible aerosol cluster, or
  • Night‑time period with suitable conditions (high humidity, low wind).
• Graceful Degradation
• In low SoC conditions, electro‑optical channels are deprioritized; HIVE SCOUT falls back to gas and environmental sensing for risk estimation.

These policies ensure that electro‑optical capabilities enhance detection without compromising overall uptime.

---

6.7 Reliability, Monitoring and Maintenance

• Each node shall report:
• Battery SoC (0.0–1.0 or %),
• VCC voltage,
• Solar charging status (charging/not charging, instantaneous current if available),
• Power‑related fault flags (e.g. power_fault, low_battery_warning).
• Operators shall be able to:
• View power status on dashboards,
• Configure power‑related policies (e.g. telemetry interval, electro‑optical duty cycles) per site or per node,
• Receive alerts when nodes are operating near SoC_LOW or SoC_CRITICAL for extended periods.
• Periodic maintenance procedures (e.g. battery health checks, solar panel cleaning) shall be defined based on field experience and telemetry trends.

---

Bu bölüm, HIVE SCOUT’un SRD’sine doğrudan eklenebilecek “Power Budget & Energy Management” anayasası seviyesinde hazır.

İstersen bir sonraki adımda bunu da SRD v2.2’nin içine entegre edilmiş tam birleşik sürüm olarak baştan sona yazabilirim; ya da doğrudan saha kurulum / deployment taktiklerine geçebiliriz.

Below is a Power Budget & Energy Management section written aynı SRD ciddiyetinde, İngilizce ve doğrudan SRD’ye eklenebilir formatta.

---

6.0 POWER BUDGET & ENERGY MANAGEMENT

6.1 Power Architecture Overview

Each HIVE SCOUT node is designed as an energy‑autonomous field device.
The power architecture shall:

• Support 24/7 operation in harsh outdoor conditions.
• Accommodate both baseline sensing (gas + environmental) and peaky loads (PURGE fan, LTE uplink, electro‑optical suite).
• Enforce deterministic power‑down behavior, ensuring that critical safety and communication functions are prioritized as energy becomes limited.

The main power elements per node are:

• Primary storage: LiFePO₄ battery pack.
• Energy harvesting: Solar panel(s) sized for worst‑case seasonal conditions.
• Power electronics: MPPT solar charger, DC/DC converters (e.g. 12.8 V → 5 V and 3.3 V rails).
• On‑board power management logic integrated with firmware state machine.

---

6.2 Power Domains and Loads

For power budgeting, node electronics are grouped into logical power domains:

1. Core Domain (Always‑On in NORMAL/DEGRADED)

• MCU (Cortex‑M4/M33)
• Core gas sensors: PID, NDIR, RH/T, pressure, anemometer
• Essential telemetry (LTE Cat‑M1 or equivalent)
• Safety‑critical functions (WDT, fault detection, minimal logging)

1. Electro‑Optical Domain (Duty‑Cycled / Conditional)

• Thermal camera (LWIR/MWIR)
• Ultra‑low‑light sCMOS camera
• Active NIR illumination (LEDs/lasers)

1. Mechanical Actuation Domain

• Micro‑compressor / purge fan
• Any auxiliary actuators (e.g. motorized shutters, if used)

1. Auxiliary Domain (Optional / Low Priority)

• Night vision contextual module (if separate from sCMOS)
• Local indicators (LEDs), maintenance ports, etc.

Each domain’s average and peak power consumption shall be quantified during detailed design.
Firmware shall be capable of individually enabling/disabling these domains based on:

• Node state (INIT, WARMUP, NORMAL, PURGE, DEGRADED, FAULT)
• Battery state of charge (SoC)
• Mission profile (e.g. night‑focused vs. continuous surveillance)

---

6.3 Typical Power Consumption Profile (Qualitative)

Indicative behavior (numbers to be finalized in detailed design):

• INIT / WARMUP
• MCU: active
• Core gas sensors: ON
• Electro‑optical suite: OFF or minimal (for alignment checks only)
• Telemetry: low‑duty or disabled until stabilization.
• NORMAL
• MCU: active, full rate
• Core gas sensors: ON (continuous or periodic sampling)
• Electro‑optical suite:
  • Thermal + sCMOS: duty‑cycled (e.g. imaging every X seconds or on demand)
  • Active NIR: pulsed only when needed (e.g. low ambient light + interest in aerosol density)
• Telemetry: periodic MQTT messages at configured interval.
• PURGE
• MCU: active
• Purge fan/compressor: ON at maximum for a short, predefined duration
• Sensing: mostly off or limited; telemetry sends “PURGE” status
• Electro‑optical: typically OFF during active purge (optional).
• DEGRADED
• MCU: active
• Only healthy sensors ON; failing domains can be powered down to save energy
• Electro‑optical suite: may be disabled or heavily duty‑cycled
• Telemetry: reduced rate but still reporting reliability_score and fault flags.
• FAULT
• All non‑essential domains OFF (sensors, optics, fan).
• MCU: deep sleep or minimal activity; only reset circuitry and critical monitoring remain.
• Telemetry: a single “Last Gasp” message if enough energy remains, then shutdown.

---

6.4 Battery and Solar Sizing Requirements

6.4.1 Battery Technology

• Chemistry: LiFePO₄ (lithium iron phosphate) or equivalent, chosen for:
• High cycle life,
• Thermal stability,
• Compatibility with outdoor temperature range.
• Battery pack shall support at least a defined number of days of operation without solar input in winter worst‑case (to be specified, e.g. 3–5 days).

6.4.2 Solar Harvesting

• Solar panel sizing shall consider:
• Local insolation data (latitude, season, typical cloud cover).
• Node average daily energy consumption, including electro‑optical duty cycles.
• Worst‑case seasonal scenario (shortest day, highest load, coldest temperature).
• Panels shall be mounted with tilt and orientation optimized for the target location and vandal‑resistance.

6.4.3 Design Targets (to be finalized)

• Daily energy budget per node (Wh/day) calculated from:
• Core Domain average power × 24 h,
• Electro‑Optical Domain duty‑cycled usage,
• Mechanical Domain PURGE usage (expected frequency),
• Telemetry overhead (LTE transmissions, keep‑alives).
• Battery capacity (Wh) shall be no less than:
• Daily Energy Budget × Days of Autonomy × safety factor.
• Solar array daily energy production (Wh/day) shall exceed the daily budget by a safety margin in worst‑case winter conditions.

---

6.5 Energy‑Aware State Machine Behavior

Power status is tightly coupled to the node’s firmware state machine.

6.5.1 Battery State of Charge (SoC) Thresholds

Define multiple SoC thresholds, e.g.:

• SoC_HIGH – normal operation (e.g. > 60%)
• SoC_MEDIUM – selective load shedding (e.g. 30–60%)
• SoC_LOW – critical saving, pre‑fault (e.g. 10–30%)
• SoC_CRITICAL – imminent shutdown (e.g. < 10%)

6.5.2 Behavior by SoC

• SoC_HIGH:
• All planned functions enabled according to mission profile.
• Electro‑optical suite fully available (though still duty‑cycled).
• SoC_MEDIUM:
• Optional/contextual functions (e.g. continuous night‑vision streaming) reduced or disabled.
• Electro‑optical suite used primarily on event/alert basis.
• Core gas and environmental sensing preserved.
• SoC_LOW:
• Mechanical loads (PURGE fan) limited to essential cycles.
• Electro‑optical suite largely disabled except for critical checks.
• Telemetry interval may be increased (less frequent messages).
• SoC_CRITICAL:
• Immediate transition to a safe state (DEGRADED or FAULT).
• Priority: send last telemetry with clear “LOW POWER / SHUTDOWN” status, then disable non‑critical loads and enter deep sleep.

6.5.3 Power Faults and FAULT State

• Voltage instability (VCC fluctuations) and abnormal power behavior shall be treated as hardware safety events, triggering transition to STATE_FAULT with all high‑current domains powered down, except for what is needed to send a final message and await reset.

---

6.6 Energy Management Policies for Electro‑Optical Suite

Given that thermal imaging and active NIR illumination are comparatively high‑power consumers, their use shall be governed by explicit policies:

• Duty‑Cycling
• Electro‑optical acquisitions scheduled at intervals (e.g. every N seconds/minutes) or only when gas‑based indicators suggest a possible plume.
• Event‑Triggered Operation
• sCMOS + NIR scattering may be activated when:
  • Cross‑reference logic (gas + RH + wind) indicates a possible aerosol cluster, or
  • Night‑time period with suitable conditions (high humidity, low wind).
• Graceful Degradation
• In low SoC conditions, electro‑optical channels are deprioritized; HIVE SCOUT falls back to gas and environmental sensing for risk estimation.

These policies ensure that electro‑optical capabilities enhance detection without compromising overall uptime.

---

6.7 Reliability, Monitoring and Maintenance

• Each node shall report:
• Battery SoC (0.0–1.0 or %),
• VCC voltage,
• Solar charging status (charging/not charging, instantaneous current if available),
• Power‑related fault flags (e.g. power_fault, low_battery_warning).
• Operators shall be able to:
• View power status on dashboards,
• Configure power‑related policies (e.g. telemetry interval, electro‑optical duty cycles) per site or per node,
• Receive alerts when nodes are operating near SoC_LOW or SoC_CRITICAL for extended periods.
• Periodic maintenance procedures (e.g. battery health checks, solar panel cleaning) shall be defined based on field experience and telemetry trends.

---

Bu bölüm, HIVE SCOUT’un SRD’sine doğrudan eklenebilecek “Power Budget & Energy Management” anayasası seviyesinde hazır.

İstersen bir sonraki adımda bunu da SRD v2.2’nin içine entegre edilmiş tam birleşik sürüm olarak baştan sona yazabilirim; ya da doğrudan saha kurulum / deployment taktiklerine geçebiliriz.

Here is the full, integrated SRD v2.2 with the new Electro‑Optical Sensing Suite (thermal + digital night vision + NIR scattering) included. Tek parça, eksiksiz kullanabilirsin.

---

SYSTEM REQUIREMENTS DOCUMENT (SRD) – v2.2

Project Name: HIVE SCOUT (KOVAN İZCİ) v2.2
System Class: Industrial / Defense‑Grade Atmospheric Sensor Network
Document Status: Frozen Baseline Architecture (with Electro‑Optical Sensing Suite)

---

0.0 REVISION HISTORY

• v2.0 – Initial frozen baseline
• Core hardware and sensor suite (gas + environmental)
• Compensation algorithms (PID humidity, NDIR T/p)
• Deterministic firmware state machine
• MQTT/JSON telemetry structure
• v2.1 – Updates
• Night vs. day operational considerations
• Low‑temperature handling for PID UV lamp
• Optional Optical Aerosol Channel (laser/light)
• Optional Night Vision Module (contextual imaging)
• v2.2 – Electro‑Optical Suite consolidated
• Defines a combined Electro‑Optical Sensing Suite:
  • Thermal imaging (LWIR/MWIR)
  • Digital low‑light night vision (sCMOS + NIR)
  • Active NIR illumination and Mie scattering for aerosol optical density
• Clarifies roles and complementarity between gas sensors and electro‑optics

---

1.0 SCOPE AND OPERATIONAL OBJECTIVES

1.1 System Definition

HIVE SCOUT is an autonomous, fault‑tolerant, networked atmospheric analysis system designed to detect biological/chemical aerosol risk clustering in urban street canyons and stagnant air conditions.
The system combines:

• High‑grade gas and environmental sensing (tracer gas, CO₂, RH/T/P, wind), and
• A multi‑layer Electro‑Optical Sensing Suite (thermal imaging, digital night vision, active NIR scattering),

to identify physical “air traps” where aerosols can accumulate and persist, generating real‑time risk maps for cities, critical infrastructure and defense operations.

1.2 Out‑of‑Scope Functions

• The system does not directly detect viruses, bacteria, or specific DNA/RNA signatures.
• It does not perform clinical diagnosis or individual health assessment.
• It provides statistical and physical risk indicators derived from gas, environmental and electro‑optical signals.

1.3 Operational Environment

Field nodes shall operate outdoors under:

• Temperature: −20 °C to +50 °C
• Relative humidity: 0% to 100% (including condensation events)
• Meteorological conditions: rain, fog, dust, exhaust plumes
• Enclosures: minimum IP67 ingress protection

Preferred operational window:

• The primary aerosol‑cluster mapping mode is optimized for high‑humidity, low‑wind evening/night or early‑morning conditions.
• Daytime operation focuses primarily on background data collection and trend analysis, due to stronger convection and mixing.

---

2.0 HARDWARE AND SENSOR SUITE

2.1 Core Processing Unit

Each field node shall use a microcontroller with:

• ARM Cortex‑M4/M33 (or equivalent)
• Hardware FPU (floating‑point unit)
• Sufficient RAM/Flash to:
• Execute floating‑point sensor equations and compensation algorithms in millisecond‑scale cycles.
• Implement a deterministic state machine (INIT, WARMUP, NORMAL, PURGE, DEGRADED, FAULT).

Indicative minimums (to be refined in detailed design):

• CPU clock: ≥ 80 MHz
• Flash: ≥ 512 kB
• RAM: ≥ 128 kB

2.2 Gas and Environmental Sensor Matrix

Minimum performance requirements:

Sensor Type	Target Quantity	LOD	Typical Resolution	Max Error	Critical Environmental Blind Point
PID (10.6 eV lamp)	Isobutylene (C₄H₈)	1 ppb	≤ 0.5 ppb	±2%	≥ 95% RH, condensation on UV optics
Dual‑channel NDIR	CO₂ (human breath)	400 ppm	≤ 1 ppm	±15 ppm	Outside −20 °C / +50 °C
Capacitive polymer RH	Relative humidity (RH)	0% RH	≤ 0.1% RH	±1.0% RH	Direct condensation on sensor surface
Bandgap temperature	Temperature (T)	−40 °C	≤ 0.01 °C	±0.1 °C	Direct solar loading (radiant heating)
Ultrasonic anemometer	Wind vector $$\vec{v}$$	0.01 m/s	≤ 0.01 m/s	±2%	Heavy rain (ultrasonic path disruption)

Each sensor shall be factory‑ or lab‑calibrated. Calibration intervals and drift limits shall be defined in a separate sensor annex.

2.3 Mechanical Design and Active Purge

• Passive air intake is not acceptable.
• Each node shall include:
• A controlled‑flow air path pulling ambient air into the sensor chamber at a defined nominal flow rate.
• A micro‑compressor or turbine fan capable of reversing flow and actively purging the chamber under saturation conditions (dust, exhaust, fog, condensation).
• Purge duration and airflow shall be sufficient to restore chamber readings to defined baseline levels after a purge cycle.

---

2.4 ELECTRO‑OPTICAL SENSING SUITE

The Electro‑Optical Sensing Suite comprises three complementary layers:

1. Thermal Imaging (LWIR/MWIR)
2. Digital Low‑Light Night Vision (Ultra‑Low‑Light sCMOS)
3. Active NIR Illumination and Aerosol Mie Scattering

These layers collectively reduce the probability of optical “blind spots” for aerosol clusters, even under thermal equilibrium conditions.

2.4.1 Thermal Imaging (LWIR/MWIR)

Purpose

• Provide long‑wave or mid‑wave infrared imaging of the scene, mapping surface and plume temperature distributions (e.g. warm exhaust, hot/cold structures, large thermal plumes).

Requirements

• Spectral band: LWIR and/or MWIR as per chosen sensor.
• Resolution and field of view suitable to cover the node’s sensing footprint (e.g. the street segment under surveillance).
• Thermal sensitivity (NETD) sufficient to detect small temperature differences in plumes and surfaces.

Limitations

• In conditions of thermal equilibrium (when aerosol cloud temperature closely matches background structures and air), thermal contrast may be minimal; in such cases, thermal imaging alone may not reveal aerosol clouds.

2.4.2 Digital Low‑Light Night Vision (Ultra‑Low‑Light sCMOS)

Physical Principle

• Human vision degrades significantly below ~0.1 lux.
• Ultra‑low‑light scientific CMOS (sCMOS) sensors with back‑illuminated (BSI) architectures can operate at ~0.0001 lux, counting single photons and amplifying them electronically.

Role in the System

• Operates in visible and Near‑Infrared (NIR, ~0.7–1.0 µm) bands.
• Even in extremely dark street canyons, sCMOS can accumulate scattered starlight, moonlight, or urban sky glow to produce a detailed topographic image.
• Provides “digital night vision” imagery that can be numerically processed (per‑pixel analysis) and fused with gas and thermal data.

Requirements

• Ultra‑low‑light sCMOS sensor with high quantum efficiency in visible + NIR.
• Digital output (no analog phosphor tube); all pixels must be available for algorithmic processing.
• Integration times and gain levels adjustable by firmware depending on ambient light and mission profile.

2.4.3 Active NIR Illumination and Mie Scattering

Physical Principle

• When ambient light is insufficient (no moon, heavy cloud, deep urban canyon), the node must generate its own tactical illumination.
• Pulsed NIR lasers/LEDs at 850 nm or 940 nm are invisible to the human eye but can be detected by the sCMOS sensor.
• Aerosol particles in air scatter this NIR light (Mie scattering), altering the intensity and structure of the returned signal from the scene.

Role in the System

• NIR emitters project structured or wide‑field illumination into the monitored volume.
• The sCMOS camera measures how much of this NIR light is:
• Attenuated (blocked) or
• Scattered (diffusely returned)
  by aerosols and particulates in the air.
• From this, the system estimates aerosol optical density along specific paths or within the field of view.

Requirements

• NIR sources:
• Wavelength: typically 850 nm and/or 940 nm.
• Operation in pulsed or modulated mode for better SNR and ambient light rejection.
• Eye‑safe output within regulatory limits.
• Firmware shall coordinate NIR emission with sCMOS exposure cycles.
• Aerosol optical density estimations from NIR scattering are treated as physical density indicators and fused with gas and thermal data.

2.4.4 Fusion: Thermal + Digital Night Vision + NIR Scattering

Motivation

• Thermal imaging can fail to detect aerosol clouds that are in thermal equilibrium with their surroundings.
• Digital night vision with active NIR scattering can reveal aerosol presence via photon loss or scattering patterns, even when temperature contrast is null.
• The Electro‑Optical Suite thus provides:
• Thermal contrast where available, and
• Optical density contrast where temperature differences vanish.

Design Principle

• Thermal and NIR/sCMOS channels are co‑registered with the node’s sensing footprint.
• Electro‑optical outputs are synchronized with gas and environmental data (time‑aligned for fusion).
• Firmware and cloud‑side analytics can:
• Use electro‑optical channels to confirm or refine gas‑based risk scores.
• Flag inconsistencies (e.g. high optical density with no gas signal, or vice versa) for further investigation.

---

2.5 OPTIONAL NIGHT VISION MODULE (CONTEXTUAL)

The Electro‑Optical Suite above focuses on aerosol and environmental sensing.
In addition, the system may include a contextual Night Vision Module, as described earlier:

• Low‑light / IR‑sensitive camera for operational awareness (human/vehicle presence, visible smoke, etc.).
• Optional IR illumination, privacy controls, and alignment with the node’s sensing footprint.
• Outputs used for scene understanding and operator decision support, not direct gas‑based risk scoring.

---

3.0 MATHEMATICAL COMPENSATION ALGORITHMS

(unchanged in essence, but restated for completeness)

3.1 PID Humidity Quenching Compensation

• Per‑sensor calibration vs. RH (30/60/90%).
• Store humidity quenching curve $$\alpha(RH)$$.
• On‑node compensation: $$C_{comp} = C_{raw} / \alpha(RH_{meas})$$.
• RH ≥ 95% or condensation → pid_status = UNRELIABLE, PID excluded from risk.

Low‑temperature rule:

• PID UV lamp not operated below vendor minimum; below this → pid_status = DISABLED, PID ignored.

3.2 NDIR CO₂ Temperature/Pressure Compensation

• Reference point: $$T_{cal}$$, $$p_{cal}$$.
• On‑node:
• $$k_{TP} = (p / p_{cal}) \cdot (T_{cal} / T)$$
• $$C_{comp} = C_{raw} \cdot k_{TP}$$.
• Out‑of‑spec T/p → CO₂ marked UNRELIABLE, node may enter DEGRADED mode.

---

4.0 EMBEDDED FIRMWARE AND STATE MACHINE

• Deterministic 6‑state machine: INIT, WARMUP, NORMAL, PURGE, DEGRADED, FAULT.
• Priority: Hardware Safety → Sensor/Chamber → Data Production.
• WDT only fed after complete, successful loop; hangs trigger reset.
• PURGE for chamber cleaning, DEGRADED for non‑critical sensor failure, FAULT for critical issues.

(Detaylar önceki sürümle aynı; burada tekrara girmiyorum çünkü sen zaten biliyorsun.)

---

5.0 SYSTEM SAFETY, RED‑LINE RULES AND TELEMETRY

• Red Risk alarm sadece şu üçlü sağlandığında:
• Low wind (stagnant),
• Positive CO₂ gradient,
• Persistent tracer gas signal in same window.
  (Optical density from electro‑optics only destekleyici.)
• MQTT/JSON telemetri:
• state, reliability_score zorunlu.
• Gaz, çevresel ve elektro‑optik kanallardan gelen kompanzeli ölçümler + bayraklar (pid_status, sensor_fault, degraded_mode, crossref_ok, vs.).
• Ayrı alert topic’de risk ve gerekçeler (low_wind, co2_gradient, pid_plume_persistent, optical_density_high, vb.).

---

Bu SRD v2.2, artık gaz + çevresel + elektro‑optik katmanı tek gövdede tanımlayan tam mühendislik anayasası.

Sonraki kritik adım, bu mimariyi destekleyecek Power Budget & Energy Management bölümünü aynı ciddiyette yazmak; istersen bir sonraki turda direkt ona girebilirim.