Multi-board products
One project, a PCB per board, one assembly that checks every connection between them pin by pin.
A HAT on a Raspberry Pi, a cape on a BeagleBone, a front panel cabled to a main board: a product of several boards is one WireFrame project, with a PCB per board drawn from its own root sheet, a board stack for the tower, and an assembly (.asmxml) that names every board — including the ones you buy — and every connection. What no single board can show is checked here: 5 V on a 3.3 V pin, SDA on SCL, a cable turned round, signals crossing without a ground.
What it does
One project, several PCBs
Each board drawn from its own root sheet; the design graph follows the board you work on.
Bought boards, pin by pin
Raspberry Pi 40-pin, BeagleBone P8/P9, HC-SR04, GY-521, hobby servo, Pololu A4988 — from their published pinouts.
Connections checked
Rails joined, supply on a signal, pins traded or reversed, a pin open on one side, a direct pair that cannot mate.
The tower in 3D
Assembly 3D builds the stack in its case; explode it to see between the boards.
Split with the Copilot
/topology measures 2–4 ways to split a design and writes the one you choose into the project.
Faults no single board can show
A 5 V pin meeting a 3.3 V pin, SDA wired to SCL, a cable turned round, fast signals crossing with no ground beside them: each board can be correct on its own and the product still dead. The assembly checks every connection between boards pin by pin and reads "N boards, N connections — N blockers, N warnings". On the hexapod example, turning the HC-SR04 lead round and crossing the GY-521's SDA and SCL gives two blockers and both crossings.
Bought boards are checked like your own
A Raspberry Pi, a BeagleBone or a sensor module comes from its published pinout: which pins are rails and grounds, which take a signal, which take a supply in a range, which are spare. A host pin named for where it is (GPIO17, PA5) meeting what the plugged-in board uses it for is what a header is for, not a naming conflict, and a shield's one-part header block is connected one header at a time.
From one design to several boards
/topology reads the design's blocks and the nets a cut between them would carry, proposes two to four genuinely different splits and measures each the same way — parts against room, connector pins crossing between boards, the tower against its ceiling. It applies one only with your words, with connectors from real families, and writes a PCB per board and the project's assembly.
The details
| Files | A .pcbxml per board, each from its own root sheet, and one .asmxml |
|---|---|
| Connections | Direct (stacking headers) · cable (JST, FFC, with length) · wire |
| Bought boards | rpi-40 · beaglebone / beaglebone-92 · hc-sr04 · servo · gy-521 · pololu-a4988 |
| Checks | Rails joined · supply or ground on a signal · pins traded or reversed · a pin open on one side · signals with no ground · shorts through two connectors · a pair that cannot mate |
| Views | Boards · System view · Assembly 3D with explode |
How to start
- File › New › New Assembly (.asmxml) for the active project.
- Add a board (project) for each PCB, and Add a board not designed here for a Pi or a sensor module.
- Connect two boards for each header or cable, then read the findings in View › Assembly View.
Questions
Does it check logic levels between boards?
Not yet: pins have no logic level, so a 3.3 V host driving the input of a 5 V-supplied part is not caught. The guide lists this among today's limits.
Does it check the boards against the case?
Assembly 3D shows the tower in its case, but no interference check reports a collision yet.
Can a board from another project be part of the product?
Yes — Add a board (project) takes a PCB of this project or another, such as an open-source shield.