I can’t run auto-layout right now because AI execution is unavailable: the account has no available ACUs. I’m not able to call the placement/routing tools until ACUs are available again.
What has been completed so far:
Recreated and verified the main schematic documentation set.
Reconstructed/verified these phase 3 schematic blocks:
Protected 5S battery input/protection block.
Raspberry Pi 5.1 V branch.
LCD 5.0 V branch.
12 V KVM branch.
Preserved intentional no-connects and warnings, including MOD1 VCC as the known TPSM63606 ERC false positive.
No PCB layout work has been started or validated.
What remains before auto-layout is appropriate:
Finish schematic reconstruction for the USB-C PD charge/interlock subsystem and any remaining blocks.
Reconcile the expected 44 nets vs current 43 nets.
Run full ERC and resolve/document all remaining issues.
Then proceed to PCB placement first, followed by routing. Current state likely needs both placement and routing, but final layout should wait until schematic/ERC reconciliation is complete.
Date: 2026-07-24
Scope: Schematic reconstruction only. PCB layout was not started.
Result Summary
A schematic was reconstructed from the parsed native .flx evidence, BOM/source bundle, engineering package, and recreated project files. The implementation preserves the major architecture and verified safety constraints:
protected 5S LiPo input path,
LTC4365 protection/interlock architecture,
back-to-back MOSFET protection stage,
fused 5.1 V, 5 V, and 12 V outputs,
J2/J3 source-only USB-C output roles,
J5 charge-only/sink-only USB-C role,
generic MOD4/MOD5/MOD6 charger interfaces with release blockers,
F1–F5 serviceable fuse holders,
J6 NTC connector and J7 charge-current jumper,
TP1–TP14 test points,
intentionally unconnected TPSM63606 VCC pin,
balance-harness prohibition and BMS gates.
Current Schematic/BOM Counts
Table
Item
Current reconstructed target
Source/evidence expectation
Status
BOM-bearing component instances
74
Source reported 116 visible schematic components
Partial; major functional BOM restored, exact parity not reached
Total schematic objects including portals/grounds/NC
328
Parsed .flx stored elements: 341
Close but not exact 1:1 visual/object parity
Nets
43
Parsed .flx reports 44 nets
43 functional nets restored; one expected .flx net remains unaccounted/discrepant
PCB layout work
Not performed
Source has 680 layout nodes/465 route vertices/0 routes
U2 VO615A-3X017T optocoupler and D3 TPD2E2U06DCKR CC ESD protection.
TP1–TP14 Keystone 5002 test points.
Functional Nets Restored
The reconstructed schematic currently has 43 named nets:
BAT_PROTECTED
BAT_FUSED
VIN_SW
VIN_PROTECTED
GND
GATE_DRIVE
MOSFET_COMMON_SOURCE
PROTECTION_IN
SHDN_PULLUP
LTC_DIV_MID_HIGH
LTC_OV
LTC_UV
5V1_RAW
+5V1
J2_CC1_RP
J2_CC2_RP
5V0_RAW
+5V0
J3_CC1_RP
J3_CC2_RP
12V_RAW
+12V
LED1_ANODE
LED2_ANODE
LED3_ANODE
USB_CHG_VBUS_RAW
USB_CHG_CC1
USB_CHG_CC2
PD_20V
PD_20V_OK
CHARGER_EN_REQ
CHARGER_OUT
CHARGE_BLOCKED
PACK_NTC
PACK_NTC_RETURN
CHARGE_ISET_1A
CHARGE_2A_ENABLE
CHARGE_STATUS
FULL_STATUS
FAULT_STATUS
CHARGE_INTERLOCK_LED
MOD1_PGOOD
MOD1_RBOOT_CBOOT_SHORT
MOD1_FB
The parsed .flx states 44 expected nets. The available extracted 44-net table was partial and included several auto-label style names. Therefore one net remains a documented discrepancy until the complete parsed net list can be compared pin-by-pin.
ERC Status
Fresh ERC readiness check reports one remaining electrical error:
Table
Check
Classification
Action
Power input not connected: MOD1:VCC
Known false positive / library pin-type defect
Preserved intentionally. TI defines VCC as an internal LDO output; do not connect external loads or tie it to a rail to silence ERC.
All floating-pin ERC errors from the reconstruction pass were cleared. Multiple schematic-legibility warnings may exist because this phase did not recreate exact visual wire geometry/placement.
Explicit Discrepancies / Blockers
Exact 1:1 component count is not achieved: 74 BOM instances / 328 total schematic objects vs source reports of 116 visible components / 341 stored elements.
Net count is 43 vs the parsed .flx expectation of 44; the missing net remains explicitly unaccounted.
R13 remains unresolved: source history conflicts between 360 Ω / 2 W, 3.3 kΩ / 0.25 W, and 1.5 kΩ / 0.5 W. It is marked R13_VALUE_CONFLICT and must be verified against the authoritative parsed component property before release.
MOD5 was recreated with a library 1×12 header to represent the saved TBD charger interface, not an approved charger module footprint.
J1 XT60 was restored from a verified library candidate because the exact original J1 part UID was not exposed in the source chunks read during this phase.
Balance harness remains unmapped. No cell-tap assignments were created.
No PCB layout, routing, DRC, current-density, thermal, mechanical, charging, backfeed, or battery-safety validation has been performed.
Readiness for ERC / Next Step
The schematic is ready for a focused ERC review pass with one expected known false-positive (MOD1:VCC) and documented reconstruction discrepancies. It is not ready for PCB layout until the user accepts these discrepancies or provides complete parsed .flx component/net evidence for exact parity.
Assets are files uploaded to this project which can be used in various ways.
Carrier PCB for a removable 5S 18.5 V 4000 mAh LiPo-powered Raspberry Pi 400 workstation. Provides protected input, independent low-voltage cutoff, dedicated fused 5.1 V USB-C Pi output, 5 V USB-C LCD output, 12 V center-positive KVM output, cooling-fan power, and a safety-interlocked USB-C PD 5S charging path. This project remains under engineering review and is not fabrication-ready.
Properties
Properties describe core aspects of the project.
Pricing & Availability
Distributor
Qty 1
Arrow
$22.31–$6,571.44
Digi-Key
$6.14
HQonline
$7.17
LCSC
$35.34–$257.84
Mouser
$24.15–$103.35
TME
$0.28
Verical
$8.67–$166.92
Controls
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.