USB-C Sensor Node


Created a project doc

Project Specification

View Document

Project Specification Project Overview
Status: Draft — schematic design in progress.
One universal carrier PCB for a removable LilyGo TTGO T-Beam V1.2 (ESP32, SX1276 915 MHz, GPS). Optional sections are populated as needed for maple-sugar-camp monitoring and control.
Intended Use
Outdoor field nodes in Quebec maple forests. Remote vacuum nodes normally use one solar-charged 18650 and prioritize standby efficiency. Tank-level and relay/control nodes normally use external DC power.
What the Device Should Do
  • Mount the T-Beam on removable 2.54 mm female headers.
  • Accept a 3.0–4.2 V single-cell 18650 supplied by an external CN3065 solar charger.
  • Accept protected center-positive 5–12 V DC barrel input with automatic external-power priority.
I revised the power tree around your deployment split: battery mode gets a low-loss T‑Beam path plus an enableable low-IQ 5 V boost, while barrel mode gets a protected 2 A 5 V buck and automatically takes priority. This avoids forcing the solar node through a continuous 2 A buck-boost; the updated requirements are recorded in the Project Specification.
Thought for 3 mins
Thought for 7 sec
Awaiting 1 background task
"Maple Camp Schematic Design" completed.
I completed the architecture and requirements phase:
  • Renamed the project Maple Camp Universal LoRa Node and updated its description.
  • Created the Project Specification covering the universal PCB, revised split power architecture, optional sensors/relays, and no-routing constraint.
  • Verified the official T‑Beam V1.2 schematic and identified GPIO conflicts:
    • GPIO27, GPIO32, GPIO33: LoRa
    • GPIO34: GPS
  • Recorded the provisional safe mapping:
    • Vacuum ADC: GPIO36
    • Ultrasonic ECHO/TRIG: GPIO39/GPIO25
    • DS18B20: GPIO4
    • Relay 1/2: GPIO13/GPIO14
    • Expansion I²C: GPIO21/GPIO22, shared with the PMU
  • Defined external-priority power paths that prevent barrel-to-battery charging and avoid burdening solar nodes with a continuous 2 A buck-boost stage.
The executor reported completion, but I could not inspect or reconcile its result. The latest confirmed project state still showed 0 components and 0 nets, so I cannot claim that the schematic or ERC is complete.
Execution stopped because your ACUs ran out.

Waiting for input

No schematic yet

Talk to Flux to get started.

No layout yet

When components get added to the schematic, they'll show up here.