Smart Hawk PCB

flux

The conceptual schematic is complete: 83 editable components, 100 named nets, seven functional groups, eight ESC power/signal/telemetry channels, payload interfaces, monitoring, debug, indicators, and test points. Independent verification found zero open ERC, passive, connectivity, or schematic-legibility errors.
Open items before PCB layout
  • Battery voltage and maximum current
  • ESC continuous/peak current and connectors
  • Actual flight controller and companion computer
  • Camera, LiDAR, GPS, and telemetry module interfaces
  • Board dimensions, mounting points, copper weight, and thermal limits
Suggested next steps
  1. Review the Project Specification.
  2. Review the Board Bring-Up Plan.
  3. Supply the missing power and mechanical specifications.
  4. Then proceed with footprint selection, four-layer board setup, and component placement.
B

bilalgg

how to run and show

flux

What would you like to run or display?
  1. View the schematic and follow each functional block
  2. Run ERC to check electrical connections
  3. Simulate a circuit such as the power section
  4. Create and show the PCB layout/3D view
  5. Export a schematic PDF or BOM
Reply with the number.
B

bilalgg

flux

The Smart Hawk project currently contains a verified conceptual schematic with 83 components, 100 nets, and eight ESC channels, but no completed PCB placement or routing. Auto-layout therefore requires both component placement and trace routing.
I could not execute those PCB operations because your ACUs ran out. Before routing, the design also still needs production footprints and the missing battery current, ESC current, connector, board-outline, copper-weight, and thermal specifications; routing the high-current propulsion network without them would be unsafe.
Sign up to send

Files

Schematic

Layout

3D View

Board Bring-Up Plan
Status
This plan is a schematic-checkpoint artifact only. The present design is conceptual and contains explicit placeholder parts and TBD ratings. Do not fabricate or energize propulsion power from this revision.
Release Gates Before Hardware
  • Resolve battery chemistry, cell count, minimum/nominal/maximum voltage, capacity, connector, and fault current.
  • Resolve every ESC voltage/current/transient requirement and connector.
  • Select and verify the main fuse, reverse-polarity protection, switch/contactor, current sensor/shunt, TVS, bulk capacitors, regulators, flight controller, companion computer, sensors, cameras, telemetry module, and CAN implementation.
  • Recalculate the power budget and voltage divider; assign verified values, ratings, footprints, and datasheets.
  • Complete PCB mechanical constraints, stackup, current-density/thermal analysis, placement, routing, DRC, and manufacturing review.
First-Power Sequence After a Production-Verified Revision Exists
  1. Inspect assembly and confirm no battery or ESC loads are connected.
  2. Check resistance from BAT_RAW, VBAT, 5V_LOGIC, and 3V3_LOGIC to GND for unexpected shorts.
  3. Power BAT_RAW from a current-limited bench supply set within the verified input range.
  4. Verify protection-path behavior and measure VBAT at TP1 relative to TP2.
  5. Verify 5V_LOGIC at TP3 and 3V3_LOGIC at TP4 before installing/connecting compute modules.
  6. Verify BAT_V_SENSE at TP5 and BAT_I_SENSE at TP6 against calibrated references.
  7. Connect the flight controller only; verify debug UART at TP7/TP8 and programming/debug access.
  8. Validate GPS, LiDAR, telemetry, CAN, companion, and payload interfaces one at a time.
  9. Connect one unloaded ESC channel at a time; verify signal, telemetry, polarity, and local supply behavior.
  10. Perform propulsion testing only in a restrained safety setup with independently verified current limits, emergency disconnect, thermal monitoring, and approved operating procedures.
Pass Criteria
  • No unexpected current draw, overheating, reverse polarity, or rail collapse.
  • All rails remain within selected component and load tolerances.
  • Battery sensing is calibrated and monotonic across the verified operating range.
  • Each ESC signal maps uniquely to its matching channel and telemetry return.
  • All debug, sensor, communication, and payload interfaces pass their selected protocol tests.

  • Status

  • Release Gates Before Hardware

  • First-Power Sequence After a Production-Verified Revision Exists

  • Pass Criteria