Project Startup


I’ll build the complete schematic in functional blocks, then run connectivity and electrical-consistency checks. Unknown motor current and GPS breakout voltage will remain explicit verification items.
Created a thread
CubeSat ADCS Schematic
Needs input
View Thread
Created the ESP32 CubeSat ADCS Test Platform project name and description, and started the complete schematic build.
Open items:
  • The build could not be completed or verified because no ACUs are currently available.
  • Controller, sensors, GPS, power rails, motor drivers, potentiometers, DIP inputs, and ERC review remain unconfirmed.
  • No PCB layout was started.
Once ACUs are available, resume the schematic build and complete the electrical-consistency/ERC checks.
Received notification from "CubeSat ADCS Schematic" that it finished — picking the work back up.
The executor reports the CubeSat ADCS schematic build completed, but I cannot inspect or independently verify its changes because no ACUs are currently available.
Remaining work:
  • Reconcile the schematic against the full requirements.
  • Run ERC/connectivity checks and resolve violations.
  • Confirm motor stall current is within the DRV8838 limits.
  • Confirm the GPS module supply and logic-voltage requirements.
  • Review pin assignments, power rails, and all three motor channels before starting PCB layout.
Review completed schematic
Check electrical issues
Verify motors and GPS
Prepare layout readiness

Waiting for input


Schematic of ESP32 CubeSat ADCS Test Platform
U3
U5
D1
D2
U8
U7

Schematic is Auto-placed

The schematic has been arranged automatically. Flux can redraw it to be more readable, with components placed in related groups and wires drawn more legibly. This takes about 10-60 mins.

ESP32 CubeSat ADCS Test Platform

ESP32 CubeSat ADCS Test Platform thumbnail