348b5fc778
New firmware/esp32p4-sensor-node/ ESP-IDF (C, FreeRTOS) project skeleton per docs/superpowers/specs/2026-07-23-esp32-sensor-node-design.md's Workstream I: - Wi-Fi station-mode connect with exponential-backoff reconnect (wifi_manager.c), credentials from a gitignored main/device_config.h the seeker fills in (template: device_config.h.example). - Telemetry HTTP client (telemetry_client.c) POSTing the spec's exact contract shape to /api/device/telemetry with a Bearer token, via esp_http_client + cJSON. - BME280 I2C driver (bme280.c) with Bosch's public double-precision compensation formulas, using ESP-IDF's newer driver/i2c_master.h API. - LD2410 mmWave presence driver (ld2410.c) over UART, chosen over a plain PIR for its distance/motion data richness — its frame-offset parsing is flagged as the least-certain code in the firmware. - sensor_driver_t registry (sensor_driver.h, sensor_registry.c) so new sensors are a new driver file + one array line, no main-loop changes. - README.md: build steps, manual-config walkthrough, wiring/pinouts, and an explicit "what's verified vs. not" section plus a real hardware caveat (ESP32-P4 has no integrated Wi-Fi radio). UNVERIFIED AGAINST REAL HARDWARE per the spec's honesty-policy note — no ESP-IDF toolchain or physical boards available in this environment. Syntax-checked with gcc against hand-written ESP-IDF API stubs (not committed) as a best-effort substitute for a real idf.py build. Workstream J (RTL-SDR experimental module) is explicitly out of scope here; firmware/esp32p4-sensor-node/components/ is left in place for it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
54 lines
1.7 KiB
C
54 lines
1.7 KiB
C
// HLK-LD2410 mmWave presence/distance sensor driver, over UART.
|
|
//
|
|
// Chosen over a plain PIR for this app's "believable" ethos (per the spec):
|
|
// the LD2410 reports moving-target distance/energy AND stationary-target
|
|
// distance/energy separately, not just a boolean "something moved" — richer
|
|
// signal for the anomaly pipeline (Workstream K) to work with, and it can
|
|
// tell a séance's "someone opened a door" from "the sitter shifted in their
|
|
// chair" in a way a PIR fundamentally cannot. Tradeoff: it's a more complex
|
|
// protocol than a PIR's single GPIO pin, and this driver's frame parser is
|
|
// UNVERIFIED against a real module — see README.md's honesty section and
|
|
// the parsing notes in ld2410.c.
|
|
//
|
|
// Default wiring (3.3V logic — do NOT wire directly to a 5V-logic UART):
|
|
// LD2410 TX -> ESP32 RX (LD2410_UART_RX_GPIO)
|
|
// LD2410 RX -> ESP32 TX (LD2410_UART_TX_GPIO)
|
|
// LD2410 VCC -> 5V (module runs its sensor front-end at 5V; UART logic is
|
|
// 3.3V-tolerant per module datasheet -- double check your
|
|
// specific board revision before wiring)
|
|
// LD2410 GND -> GND
|
|
// Default UART settings: 256000 baud, 8N1 (module factory default).
|
|
|
|
#pragma once
|
|
|
|
#include "esp_err.h"
|
|
#include "sensor_driver.h"
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
#ifndef LD2410_UART_PORT
|
|
#define LD2410_UART_PORT 1
|
|
#endif
|
|
|
|
#ifndef LD2410_UART_RX_GPIO
|
|
#define LD2410_UART_RX_GPIO 17
|
|
#endif
|
|
|
|
#ifndef LD2410_UART_TX_GPIO
|
|
#define LD2410_UART_TX_GPIO 18
|
|
#endif
|
|
|
|
#ifndef LD2410_UART_BAUD
|
|
#define LD2410_UART_BAUD 256000
|
|
#endif
|
|
|
|
// sensor_driver_t-compatible entry points.
|
|
esp_err_t ld2410_init(void);
|
|
esp_err_t ld2410_read(sensor_reading_t *out, size_t max_out, size_t *out_count);
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|