Deep dive ④ · Design

Electrical architecture

The power and signal architecture authored natively in Siemens Capital — the functional architecture in Systems Architect, then carried into a detailed schematic where every function becomes a wired device. A projection of the same model, not a hand-drawn diagram.

Tool: Capital 2512 Redundant E/E · dual FC + dual battery Systems Architect → schematic

Authored in-tool

Functional architecture → wired schematic

The E/E design was carried through Capital in two native stages — both projections of the one model, nothing hand-drawn. First the functional architecture in Capital Systems Architect: the QX-250's functions (F1–F10, FA–FE) with the signal nets that connect them — DShot M1–M4, VBAT / current sense, and the CRSF command link. Then the platform was carried into a Capital schematic, where every function lands on a real device and the harness is wired end to end.

Capital Systems Architect — QX-250 functional architecture
Capital Systems Architect — functional architecture. The QX-250 functions laid out with their signal connectivity: F7 Stabilize & Control driving F3 Drive Motor (ESC) over DShot M1–M4, with VBAT / current sense and the CRSF command link feeding back. A live diagram generated from the model — not a drawing.
Capital schematic — QX-250 wired E/E design
Capital schematic — the wired design. Every function is now a device: U1 flight controller (F7), the A1 PDB + 4-in-1 ESC, four 2306 motors, the video TX, ELRS receiver and LED/buzzer — with the reliability-driven redundancy visible in copper: a U2 redundant flight controller (DShot fail-over to the ESC), a dual 4S battery with an OR-ing block (PWR1) feeding VBAT, and BEC 5 V rails to the FC and receiver.
The schematic is where the reliability analysis shows up as copper. MADe's finding — that every single fault dropped the aircraft (24 order-1 cut sets) — is answered right here: the second flight controller, the second battery and the OR-ing block are not decoration, they are those cut sets designed out. The early simulation set the architecture; Capital realized it.
How it crossed from Teamcenter to Capital. The same neutral Logical-BOM model that populated Teamcenter was rendered to a Capital project.dtd XML and imported through Project Manager — creating the QX-250 project with its functional design and platform. Nothing was hand-redrawn; the schematic is a projection of the one model.