Upload 8 files
Browse files- README.md +74 -108
- index.html +65 -133
- style.css +26 -41
README.md
CHANGED
|
@@ -7,7 +7,7 @@ sdk: static
|
|
| 7 |
app_file: index.html
|
| 8 |
pinned: true
|
| 9 |
license: mit
|
| 10 |
-
short_description: "
|
| 11 |
tags:
|
| 12 |
- pcb
|
| 13 |
- eda
|
|
@@ -17,117 +17,83 @@ tags:
|
|
| 17 |
- autorouting
|
| 18 |
---
|
| 19 |
|
| 20 |
-
#
|
| 21 |
|
| 22 |
-
|
| 23 |
-
> PCBEditor is a hosted web application, not a downloadable model. This card
|
| 24 |
-
> documents how the system is built and what it does, because "AI PCB design"
|
| 25 |
-
> is a claim that deserves a precise description. There is nothing here to
|
| 26 |
-
> `from_pretrained()`.
|
| 27 |
|
| 28 |
-
|
| 29 |
|
| 30 |
-
--
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 31 |
|
| 32 |
-
##
|
| 33 |
-
|
| 34 |
-
|
| 35 |
-
|
| 36 |
-
|
| 37 |
-
|
| 38 |
-
|
| 39 |
-
|
| 40 |
-
a
|
| 41 |
-
|
| 42 |
-
|
| 43 |
-
|
| 44 |
-
|
| 45 |
-
|
| 46 |
-
|
| 47 |
-
|
| 48 |
-
|
| 49 |
-
|
| 50 |
-
|
| 51 |
-
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
| 55 |
-
|
| 56 |
-
|
| 57 |
-
|
| 58 |
-
|
| 59 |
-
|
| 60 |
-
|
| 61 |
-
|
| 62 |
-
|
| 63 |
-
|
| 64 |
-
|
| 65 |
-
|
| 66 |
-
this stage — that is the point of the split. No model is fine-tuned, and no
|
| 67 |
-
weights are distributed.
|
| 68 |
-
|
| 69 |
-
### Measurement — deterministic engines
|
| 70 |
-
Component placement, multi-layer autorouting, design-rule checking, and
|
| 71 |
-
fabrication export. A language model has no way to measure whether a trace
|
| 72 |
-
clears a pad by 0.15 mm, so it is never asked to.
|
| 73 |
-
|
| 74 |
-
Routing is performed by **Sadie**, a from-scratch autorouter written in Rust
|
| 75 |
-
(multi-layer A\*, rip-up and reroute, Hammerstad–Jensen impedance modelling,
|
| 76 |
-
graph-based connectivity proof), run as a gRPC worker.
|
| 77 |
-
|
| 78 |
-
## Why the split matters
|
| 79 |
-
|
| 80 |
-
**Reproducibility.** The same design produces the same board. Layout does not
|
| 81 |
-
drift when the upstream model is updated, so a review you did yesterday still
|
| 82 |
-
describes the board you have today. A layout emitted by a language model cannot
|
| 83 |
-
offer that.
|
| 84 |
-
|
| 85 |
-
**Verifiability.** Every routing and clearance result is a calculation you could
|
| 86 |
-
check by hand, and the output is standard fabrication data — so you can re-run
|
| 87 |
-
DRC in KiCad, Altium, or whatever you already trust. An AI result that can only
|
| 88 |
-
be verified inside the vendor's own tool is not a result.
|
| 89 |
-
|
| 90 |
-
**Honest failure.** When a board cannot be fully routed, the system reports the
|
| 91 |
-
**specific nets it could not complete, by name**, rather than a completion
|
| 92 |
-
percentage that hides them. Most unroutable boards are placement problems, and
|
| 93 |
-
naming the stuck nets tells you what to move.
|
| 94 |
-
|
| 95 |
-
## Known limitations
|
| 96 |
-
|
| 97 |
-
- **Dense fine-pitch BGA** is the weakest case. These need escape routing before
|
| 98 |
-
a general router can help, and it is where you are most likely to see unrouted
|
| 99 |
-
nets today. This is under active work.
|
| 100 |
-
- **Not a signal-integrity suite.** Controlled-impedance nets are handled during
|
| 101 |
-
routing, but this is not a substitute for dedicated SI analysis on demanding
|
| 102 |
-
high-speed designs.
|
| 103 |
-
- **AI output is a first draft.** The reliable workflow is AI-drafts,
|
| 104 |
-
human-reviews. Confirm the schematic before it becomes copper, and confirm
|
| 105 |
-
against your fab's capability sheet before a production run.
|
| 106 |
-
- **Library coverage** is smaller than long-established desktop EDA suites.
|
| 107 |
-
|
| 108 |
-
## Intended use
|
| 109 |
-
|
| 110 |
-
Prototyping, learning, and small-to-moderate board designs — particularly where
|
| 111 |
-
no desktop EDA is available (Chromebook, tablet, locked-down machines). Not
|
| 112 |
-
positioned as a replacement for a professional EDA suite on complex production
|
| 113 |
-
hardware, and not a replacement for engineering review.
|
| 114 |
-
|
| 115 |
-
## Data
|
| 116 |
-
|
| 117 |
-
Designs are processed server-side. Prompts and design intent are sent to a
|
| 118 |
-
hosted model provider as part of generation. Footprint and symbol data derive
|
| 119 |
-
from the KiCad libraries, which are licensed CC-BY-SA-4.0 by the KiCad project.
|
| 120 |
-
|
| 121 |
-
## Licence
|
| 122 |
-
|
| 123 |
-
The `mit` licence on this repository applies to the contents of this repository
|
| 124 |
-
(this card). It is **not** a licence to the PCBEditor product or its source,
|
| 125 |
-
which are not distributed here.
|
| 126 |
|
| 127 |
## Links
|
| 128 |
|
| 129 |
-
-
|
| 130 |
-
- Text to PCB
|
| 131 |
-
- How the routing works
|
| 132 |
-
- Why
|
| 133 |
-
-
|
|
|
|
|
|
|
|
|
| 7 |
app_file: index.html
|
| 8 |
pinned: true
|
| 9 |
license: mit
|
| 10 |
+
short_description: "Can you trust an AI-designed PCB? What to check"
|
| 11 |
tags:
|
| 12 |
- pcb
|
| 13 |
- eda
|
|
|
|
| 17 |
- autorouting
|
| 18 |
---
|
| 19 |
|
| 20 |
+
# Can you trust an AI-designed PCB? What to check before you order
|
| 21 |
|
| 22 |
+
An AI tool can hand you a placed and routed board in minutes. The useful question isn't whether it looks right. It's which parts of it were decided by a language model and which were computed, because those two kinds of output fail in different ways and need different checks.
|
|
|
|
|
|
|
|
|
|
|
|
|
| 23 |
|
| 24 |
+
This is the system card for [PCBEditor](https://pcbeditor.com), which turns a plain-English description into a placed, routed, design-rule-checked PCB with standard fabrication files. It explains how the work is split between the model and the deterministic engines, what that means for what you should check, and ends with a checklist to run before you send a board to a fab. PCBEditor is a hosted application, so no model weights come with this card.
|
| 25 |
|
| 26 |
+

|
| 27 |
+
*The 3D view: the board as an assembly, with the parts' 3D models in place.*
|
| 28 |
+
|
| 29 |
+
## 1. Know which decisions came from the language model
|
| 30 |
+
|
| 31 |
+
PCBEditor splits the job in two:
|
| 32 |
+
|
| 33 |
+
- **Judgement, by a language model:** choosing parts, proposing a topology, drafting the netlist. This is reasoning over prior art, which is what language models are good at. The system is model-agnostic and runs on hosted APIs (currently AWS Bedrock); no model is fine-tuned.
|
| 34 |
+
- **Measurement, by deterministic engines:** placement, multi-layer routing, design-rule checks and export. A language model has no way to measure whether a trace clears a pad by 0.15 mm, so it is never asked to. Routing is done by Sadie, an autorouter written in Rust (multi-layer A\*, rip-up and reroute, Hammerstad–Jensen impedance modelling, graph-based connectivity proof).
|
| 35 |
+
|
| 36 |
+
**What this means for your review:** put your attention on the model's decisions, the parts and the connections. Mistakes there look plausible on screen: a wrong pinout or a missing pull-up resistor passes every geometric check. The geometry is computed, so check it with tools rather than by eye.
|
| 37 |
+
|
| 38 |
+
## 2. Expect the same board twice, but only from the same netlist
|
| 39 |
+
|
| 40 |
+
The model stage can return a different draft on a different run, and certainly on a different model version. The layout stage doesn't: the same netlist and the same rules give the same board. A review you did yesterday still describes the board you have today, even if the model behind stage one has been updated.
|
| 41 |
+
|
| 42 |
+
**What this means for your review:** once you have checked a schematic, keep it and build from it. Generating again from the same prompt gives you a new draft, and a new draft needs a new review.
|
| 43 |
+
|
| 44 |
+
## 3. Verify the board outside the tool that made it
|
| 45 |
+
|
| 46 |
+
The output is standard fabrication data: Gerber (RS-274X), Excellon drill, pick-and-place and BOM, plus a native KiCad `.kicad_pcb` file. That means you can check it with software you already trust:
|
| 47 |
+
|
| 48 |
+
- Open the `.kicad_pcb` file in KiCad and run its design-rule check with your fab's rules.
|
| 49 |
+
- Load the Gerbers and drill file into a Gerber viewer and look at every layer, the board outline and the holes.
|
| 50 |
+
|
| 51 |
+
A result you can only verify inside the vendor's own tool isn't verified.
|
| 52 |
+
|
| 53 |
+

|
| 54 |
+
*The routing view: copper on each layer in its own colour, with vias and pads.*
|
| 55 |
|
| 56 |
+
## 4. Read the unrouted list, not a percentage
|
| 57 |
+
|
| 58 |
+
When a board can't be fully routed, PCBEditor names the specific nets it couldn't complete instead of reporting a completion percentage. A figure like "94% routed" hides which connections are missing; a list of net names tells you exactly where to look.
|
| 59 |
+
|
| 60 |
+
**What to do with it:** most unroutable boards are placement problems. Move the parts at the ends of the named nets, give dense parts more room around them, and route again.
|
| 61 |
+
|
| 62 |
+
## 5. Know where it is weakest, and plan around it
|
| 63 |
+
|
| 64 |
+
- **Dense fine-pitch BGAs** are the hardest case. They need escape routing before a general router can help, and this is where you are most likely to see unrouted nets today. Plan for more layers or [via-in-pad](https://pcbeditor.com/via-in-pad) on those parts.
|
| 65 |
+
- **It is not a signal-integrity suite.** Controlled-impedance nets are handled during routing, but demanding high-speed or RF designs still need dedicated signal-integrity analysis.
|
| 66 |
+
- **AI output is a first draft.** The reliable workflow is AI drafts, a human reviews. Confirm the schematic before it becomes copper.
|
| 67 |
+
- **The part library is smaller** than in long-established desktop tools. For unusual parts, check the footprint against the datasheet's land pattern.
|
| 68 |
+
|
| 69 |
+

|
| 70 |
+
*The exploded stackup: layers pulled apart so traces and vias can be inspected layer by layer.*
|
| 71 |
+
|
| 72 |
+
## 6. Use it where it fits
|
| 73 |
+
|
| 74 |
+
PCBEditor is built for prototyping, learning and small-to-moderate board designs, particularly where no desktop CAD is available: a Chromebook, a tablet or a locked-down machine. It is not a replacement for a professional EDA suite on complex production hardware, and it is not a replacement for engineering review.
|
| 75 |
+
|
| 76 |
+
## 7. Know where your design data goes
|
| 77 |
+
|
| 78 |
+
Designs are processed on PCBEditor's servers. Prompts and design intent are sent to a hosted model provider as part of generation. Footprint and symbol data come from the KiCad libraries, which the KiCad project licenses under CC-BY-SA-4.0. The [privacy policy](https://pcbeditor.com/privacy) has the details.
|
| 79 |
+
|
| 80 |
+
## Checklist before you order
|
| 81 |
+
|
| 82 |
+
1. Check every part choice and pinout against its datasheet, especially power, ground, enable and boot pins.
|
| 83 |
+
2. Confirm the schematic before generating copper. Generating again means reviewing again.
|
| 84 |
+
3. Make sure the unrouted list is empty.
|
| 85 |
+
4. Open the `.kicad_pcb` file in KiCad and run the design-rule check with your fab's rules.
|
| 86 |
+
5. Look at the Gerbers and drill file in a viewer: layer count, board outline and holes.
|
| 87 |
+
6. Compare minimum trace width, spacing, drill size and annular ring with your fab's capability sheet.
|
| 88 |
+
7. Give high-speed or RF nets a separate signal-integrity review.
|
| 89 |
+
8. Order a small prototype run before a production run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 90 |
|
| 91 |
## Links
|
| 92 |
|
| 93 |
+
- [PCBEditor](https://pcbeditor.com/?utm_source=huggingface&utm_medium=space&utm_campaign=system_card)
|
| 94 |
+
- [Text to PCB](https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card)
|
| 95 |
+
- [How the routing works](https://pcbeditor.com/free-pcb-autorouter?utm_source=huggingface&utm_medium=space&utm_campaign=system_card)
|
| 96 |
+
- [Why a language model can't apply the physics](https://pcbeditor.com/can-ai-apply-pcb-knowledge?utm_source=huggingface&utm_medium=space&utm_campaign=system_card)
|
| 97 |
+
- [Questions to ask any AI PCB tool](https://pcbeditor.com/evaluate-ai-pcb-software?utm_source=huggingface&utm_medium=space&utm_campaign=system_card)
|
| 98 |
+
|
| 99 |
+
The MIT licence on this Space applies to this card only, not to the PCBEditor product or its source, which are not distributed here. PCBEditor is built by [RoboDIB](https://robodib.com) in Bangalore, India.
|
index.html
CHANGED
|
@@ -3,8 +3,8 @@
|
|
| 3 |
<head>
|
| 4 |
<meta charset="utf-8" />
|
| 5 |
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
| 6 |
-
<title>
|
| 7 |
-
<meta name="description" content="
|
| 8 |
<link rel="icon" href="app-icon.svg" type="image/svg+xml" />
|
| 9 |
<link rel="stylesheet" href="style.css" />
|
| 10 |
</head>
|
|
@@ -16,137 +16,69 @@
|
|
| 16 |
</a>
|
| 17 |
<a class="nav-link" href="https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Try it free →</a>
|
| 18 |
</nav>
|
| 19 |
-
<main>
|
| 20 |
-
<
|
| 21 |
-
|
| 22 |
-
|
| 23 |
-
|
| 24 |
-
|
| 25 |
-
|
| 26 |
-
|
| 27 |
-
|
| 28 |
-
|
| 29 |
-
|
| 30 |
-
|
| 31 |
-
|
| 32 |
-
|
| 33 |
-
|
| 34 |
-
|
| 35 |
-
|
| 36 |
-
|
| 37 |
-
|
| 38 |
-
|
| 39 |
-
|
| 40 |
-
|
| 41 |
-
|
| 42 |
-
|
| 43 |
-
|
| 44 |
-
|
| 45 |
-
|
| 46 |
-
|
| 47 |
-
|
| 48 |
-
|
| 49 |
-
|
| 50 |
-
|
| 51 |
-
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
| 55 |
-
|
| 56 |
-
|
| 57 |
-
|
| 58 |
-
|
| 59 |
-
|
| 60 |
-
|
| 61 |
-
|
| 62 |
-
|
| 63 |
-
|
| 64 |
-
|
| 65 |
-
|
| 66 |
-
|
| 67 |
-
|
| 68 |
-
|
| 69 |
-
|
| 70 |
-
|
| 71 |
-
|
| 72 |
-
|
| 73 |
-
|
| 74 |
-
|
| 75 |
-
|
| 76 |
-
|
| 77 |
-
|
| 78 |
-
|
| 79 |
-
|
| 80 |
-
|
| 81 |
-
|
| 82 |
-
<p>
|
| 83 |
-
The system is <strong>model-agnostic by design</strong> and runs against hosted APIs (currently AWS Bedrock).
|
| 84 |
-
Correctness does not depend on which model is behind this stage — that is the point of the split. No model is
|
| 85 |
-
fine-tuned, and no weights are distributed.
|
| 86 |
-
</p>
|
| 87 |
-
<h3>Measurement — deterministic engines</h3>
|
| 88 |
-
<p>
|
| 89 |
-
Component placement, multi-layer autorouting, design-rule checking, and fabrication export. A language model
|
| 90 |
-
has no way to measure whether a trace clears a pad by 0.15 mm, so it is never asked to.
|
| 91 |
-
</p>
|
| 92 |
-
<p>
|
| 93 |
-
Routing is performed by <strong>Sadie</strong>, a from-scratch autorouter written in Rust (multi-layer A*,
|
| 94 |
-
rip-up and reroute, Hammerstad–Jensen impedance modelling, graph-based connectivity proof), run as a gRPC worker.
|
| 95 |
-
</p>
|
| 96 |
-
</section>
|
| 97 |
-
|
| 98 |
-
<section>
|
| 99 |
-
<h2>Why the split matters</h2>
|
| 100 |
-
<ul>
|
| 101 |
-
<li><strong>Reproducibility.</strong> The same design produces the same board. Layout does not drift when the upstream model is updated, so a review you did yesterday still describes the board you have today.</li>
|
| 102 |
-
<li><strong>Verifiability.</strong> Every routing and clearance result is a calculation you could check by hand, and the output is standard fabrication data — so you can re-run DRC in KiCad, Altium, or whatever you already trust.</li>
|
| 103 |
-
<li><strong>Honest failure.</strong> When a board cannot be fully routed, the system reports the specific nets it could not complete, by name, rather than a completion percentage that hides them.</li>
|
| 104 |
-
</ul>
|
| 105 |
-
</section>
|
| 106 |
-
|
| 107 |
-
<section>
|
| 108 |
-
<h2>Known limitations</h2>
|
| 109 |
-
<ul>
|
| 110 |
-
<li><strong>Dense fine-pitch BGA</strong> is the weakest case. These need escape routing before a general router can help, and it is where you are most likely to see unrouted nets today.</li>
|
| 111 |
-
<li><strong>Not a signal-integrity suite.</strong> Controlled-impedance nets are handled during routing, but this is not a substitute for dedicated SI analysis on demanding high-speed designs.</li>
|
| 112 |
-
<li><strong>AI output is a first draft.</strong> The reliable workflow is AI-drafts, human-reviews. Confirm the schematic before it becomes copper, and confirm against your fab's capability sheet before a production run.</li>
|
| 113 |
-
<li><strong>Library coverage</strong> is smaller than long-established desktop EDA suites.</li>
|
| 114 |
-
</ul>
|
| 115 |
-
</section>
|
| 116 |
-
|
| 117 |
-
<section>
|
| 118 |
-
<h2>Intended use</h2>
|
| 119 |
-
<p>
|
| 120 |
-
Prototyping, learning, and small-to-moderate board designs — particularly where no desktop EDA is available
|
| 121 |
-
(Chromebook, tablet, locked-down machines). Not positioned as a replacement for a professional EDA suite on
|
| 122 |
-
complex production hardware, and not a replacement for engineering review.
|
| 123 |
-
</p>
|
| 124 |
-
</section>
|
| 125 |
-
|
| 126 |
-
<section>
|
| 127 |
-
<h2>Data</h2>
|
| 128 |
-
<p>
|
| 129 |
-
Designs are processed server-side. Prompts and design intent are sent to a hosted model provider as part of
|
| 130 |
-
generation. Footprint and symbol data derive from the KiCad libraries, which are licensed CC-BY-SA-4.0 by the
|
| 131 |
-
KiCad project. See the <a href="https://pcbeditor.com/privacy" target="_blank" rel="noopener">privacy policy</a>.
|
| 132 |
-
</p>
|
| 133 |
-
</section>
|
| 134 |
-
|
| 135 |
-
<section class="links">
|
| 136 |
-
<h2>Links</h2>
|
| 137 |
-
<ul>
|
| 138 |
-
<li><a href="https://pcbeditor.com/?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Product</a></li>
|
| 139 |
-
<li><a href="https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Text to PCB</a></li>
|
| 140 |
-
<li><a href="https://pcbeditor.com/free-pcb-autorouter?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">How the routing works</a></li>
|
| 141 |
-
<li><a href="https://pcbeditor.com/can-ai-apply-pcb-knowledge?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Why an LLM cannot apply the physics</a></li>
|
| 142 |
-
<li><a href="https://pcbeditor.com/evaluate-ai-pcb-software?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Evaluating any AI PCB tool</a></li>
|
| 143 |
-
</ul>
|
| 144 |
-
</section>
|
| 145 |
-
|
| 146 |
-
<footer>
|
| 147 |
-
<p>The MIT licence on this Space applies to this card only. It is not a licence to the PCBEditor product or its source, which are not distributed here.</p>
|
| 148 |
-
<p>PCBEditor is built by <a href="https://robodib.com" target="_blank" rel="noopener">RoboDIB</a>, Bangalore, India.</p>
|
| 149 |
-
</footer>
|
| 150 |
</main>
|
| 151 |
</body>
|
| 152 |
</html>
|
|
|
|
| 3 |
<head>
|
| 4 |
<meta charset="utf-8" />
|
| 5 |
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
| 6 |
+
<title>Can you trust an AI-designed PCB? What to check before you order | PCBEditor system card</title>
|
| 7 |
+
<meta name="description" content="Which parts of an AI-designed PCB came from a language model and which were computed, what that means for your review, and a checklist to run before you order." />
|
| 8 |
<link rel="icon" href="app-icon.svg" type="image/svg+xml" />
|
| 9 |
<link rel="stylesheet" href="style.css" />
|
| 10 |
</head>
|
|
|
|
| 16 |
</a>
|
| 17 |
<a class="nav-link" href="https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Try it free →</a>
|
| 18 |
</nav>
|
| 19 |
+
<main class="content">
|
| 20 |
+
<p class="eyebrow">// PCBEDITOR AI · SYSTEM CARD</p>
|
| 21 |
+
<h1>Can you trust an AI-designed PCB? What to check before you order</h1>
|
| 22 |
+
<p>An AI tool can hand you a placed and routed board in minutes. The useful question isn't whether it looks right. It's which parts of it were decided by a language model and which were computed, because those two kinds of output fail in different ways and need different checks.</p>
|
| 23 |
+
<p>This is the system card for <a href="https://pcbeditor.com" target="_blank" rel="noopener">PCBEditor</a>, which turns a plain-English description into a placed, routed, design-rule-checked PCB with standard fabrication files. It explains how the work is split between the model and the deterministic engines, what that means for what you should check, and ends with a checklist to run before you send a board to a fab. PCBEditor is a hosted application, so no model weights come with this card.</p>
|
| 24 |
+
<p><img src="board-3d.webp" alt="PCBEditor 3D view of an assembled board with a microcontroller, two SOIC chips, two rows of pin headers, a push button and a USB-C receptacle" />
|
| 25 |
+
<em>The 3D view: the board as an assembly, with the parts' 3D models in place.</em></p>
|
| 26 |
+
<p class="actions"><a class="btn" href="https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Open PCBEditor →</a><a class="link" href="https://pcbeditor.com/free-pcb-autorouter?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">How the routing works</a></p>
|
| 27 |
+
<h2>1. Know which decisions came from the language model</h2>
|
| 28 |
+
<p>PCBEditor splits the job in two:</p>
|
| 29 |
+
<ul>
|
| 30 |
+
<li><strong>Judgement, by a language model:</strong> choosing parts, proposing a topology, drafting the netlist. This is reasoning over prior art, which is what language models are good at. The system is model-agnostic and runs on hosted APIs (currently AWS Bedrock); no model is fine-tuned.</li>
|
| 31 |
+
<li><strong>Measurement, by deterministic engines:</strong> placement, multi-layer routing, design-rule checks and export. A language model has no way to measure whether a trace clears a pad by 0.15 mm, so it is never asked to. Routing is done by Sadie, an autorouter written in Rust (multi-layer A*, rip-up and reroute, Hammerstad–Jensen impedance modelling, graph-based connectivity proof).</li>
|
| 32 |
+
</ul>
|
| 33 |
+
<p><strong>What this means for your review:</strong> put your attention on the model's decisions, the parts and the connections. Mistakes there look plausible on screen: a wrong pinout or a missing pull-up resistor passes every geometric check. The geometry is computed, so check it with tools rather than by eye.</p>
|
| 34 |
+
<h2>2. Expect the same board twice, but only from the same netlist</h2>
|
| 35 |
+
<p>The model stage can return a different draft on a different run, and certainly on a different model version. The layout stage doesn't: the same netlist and the same rules give the same board. A review you did yesterday still describes the board you have today, even if the model behind stage one has been updated.</p>
|
| 36 |
+
<p><strong>What this means for your review:</strong> once you have checked a schematic, keep it and build from it. Generating again from the same prompt gives you a new draft, and a new draft needs a new review.</p>
|
| 37 |
+
<h2>3. Verify the board outside the tool that made it</h2>
|
| 38 |
+
<p>The output is standard fabrication data: Gerber (RS-274X), Excellon drill, pick-and-place and BOM, plus a native KiCad <code>.kicad_pcb</code> file. That means you can check it with software you already trust:</p>
|
| 39 |
+
<ul>
|
| 40 |
+
<li>Open the <code>.kicad_pcb</code> file in KiCad and run its design-rule check with your fab's rules.</li>
|
| 41 |
+
<li>Load the Gerbers and drill file into a Gerber viewer and look at every layer, the board outline and the holes.</li>
|
| 42 |
+
</ul>
|
| 43 |
+
<p>A result you can only verify inside the vendor's own tool isn't verified.</p>
|
| 44 |
+
<p><img loading="lazy" src="board-routing.webp" alt="PCBEditor routing view of the board, with copper on each layer in its own colour, vias and pads" />
|
| 45 |
+
<em>The routing view: copper on each layer in its own colour, with vias and pads.</em></p>
|
| 46 |
+
<h2>4. Read the unrouted list, not a percentage</h2>
|
| 47 |
+
<p>When a board can't be fully routed, PCBEditor names the specific nets it couldn't complete instead of reporting a completion percentage. A figure like "94% routed" hides which connections are missing; a list of net names tells you exactly where to look.</p>
|
| 48 |
+
<p><strong>What to do with it:</strong> most unroutable boards are placement problems. Move the parts at the ends of the named nets, give dense parts more room around them, and route again.</p>
|
| 49 |
+
<h2>5. Know where it is weakest, and plan around it</h2>
|
| 50 |
+
<ul>
|
| 51 |
+
<li><strong>Dense fine-pitch BGAs</strong> are the hardest case. They need escape routing before a general router can help, and this is where you are most likely to see unrouted nets today. Plan for more layers or <a href="https://pcbeditor.com/via-in-pad" target="_blank" rel="noopener">via-in-pad</a> on those parts.</li>
|
| 52 |
+
<li><strong>It is not a signal-integrity suite.</strong> Controlled-impedance nets are handled during routing, but demanding high-speed or RF designs still need dedicated signal-integrity analysis.</li>
|
| 53 |
+
<li><strong>AI output is a first draft.</strong> The reliable workflow is AI drafts, a human reviews. Confirm the schematic before it becomes copper.</li>
|
| 54 |
+
<li><strong>The part library is smaller</strong> than in long-established desktop tools. For unusual parts, check the footprint against the datasheet's land pattern.</li>
|
| 55 |
+
</ul>
|
| 56 |
+
<p><img loading="lazy" src="board-stackup.webp" alt="PCBEditor exploded stackup view of the board, with its layers pulled apart and vias running vertically between them" />
|
| 57 |
+
<em>The exploded stackup: layers pulled apart so traces and vias can be inspected layer by layer.</em></p>
|
| 58 |
+
<h2>6. Use it where it fits</h2>
|
| 59 |
+
<p>PCBEditor is built for prototyping, learning and small-to-moderate board designs, particularly where no desktop CAD is available: a Chromebook, a tablet or a locked-down machine. It is not a replacement for a professional EDA suite on complex production hardware, and it is not a replacement for engineering review.</p>
|
| 60 |
+
<h2>7. Know where your design data goes</h2>
|
| 61 |
+
<p>Designs are processed on PCBEditor's servers. Prompts and design intent are sent to a hosted model provider as part of generation. Footprint and symbol data come from the KiCad libraries, which the KiCad project licenses under CC-BY-SA-4.0. The <a href="https://pcbeditor.com/privacy" target="_blank" rel="noopener">privacy policy</a> has the details.</p>
|
| 62 |
+
<h2>Checklist before you order</h2>
|
| 63 |
+
<ol>
|
| 64 |
+
<li>Check every part choice and pinout against its datasheet, especially power, ground, enable and boot pins.</li>
|
| 65 |
+
<li>Confirm the schematic before generating copper. Generating again means reviewing again.</li>
|
| 66 |
+
<li>Make sure the unrouted list is empty.</li>
|
| 67 |
+
<li>Open the <code>.kicad_pcb</code> file in KiCad and run the design-rule check with your fab's rules.</li>
|
| 68 |
+
<li>Look at the Gerbers and drill file in a viewer: layer count, board outline and holes.</li>
|
| 69 |
+
<li>Compare minimum trace width, spacing, drill size and annular ring with your fab's capability sheet.</li>
|
| 70 |
+
<li>Give high-speed or RF nets a separate signal-integrity review.</li>
|
| 71 |
+
<li>Order a small prototype run before a production run.</li>
|
| 72 |
+
</ol>
|
| 73 |
+
<h2>Links</h2>
|
| 74 |
+
<ul>
|
| 75 |
+
<li><a href="https://pcbeditor.com/?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">PCBEditor</a></li>
|
| 76 |
+
<li><a href="https://pcbeditor.com/text-to-pcb?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Text to PCB</a></li>
|
| 77 |
+
<li><a href="https://pcbeditor.com/free-pcb-autorouter?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">How the routing works</a></li>
|
| 78 |
+
<li><a href="https://pcbeditor.com/can-ai-apply-pcb-knowledge?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Why a language model can't apply the physics</a></li>
|
| 79 |
+
<li><a href="https://pcbeditor.com/evaluate-ai-pcb-software?utm_source=huggingface&utm_medium=space&utm_campaign=system_card" target="_blank" rel="noopener">Questions to ask any AI PCB tool</a></li>
|
| 80 |
+
</ul>
|
| 81 |
+
<p>The MIT licence on this Space applies to this card only, not to the PCBEditor product or its source, which are not distributed here. PCBEditor is built by <a href="https://robodib.com" target="_blank" rel="noopener">RoboDIB</a> in Bangalore, India.</p>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 82 |
</main>
|
| 83 |
</body>
|
| 84 |
</html>
|
style.css
CHANGED
|
@@ -6,6 +6,7 @@
|
|
| 6 |
--strong: #ffffff;
|
| 7 |
--muted: rgba(255, 255, 255, 0.55);
|
| 8 |
--accent: #4ade80;
|
|
|
|
| 9 |
}
|
| 10 |
|
| 11 |
* { box-sizing: border-box; }
|
|
@@ -17,54 +18,38 @@ html, body {
|
|
| 17 |
font: 16px/1.65 -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
|
| 18 |
}
|
| 19 |
|
| 20 |
-
main { max-width: 760px; margin: 0 auto; padding: 48px 16px 64px; }
|
| 21 |
-
|
| 22 |
a { color: var(--accent); text-decoration: none; }
|
| 23 |
a:hover { text-decoration: underline; }
|
| 24 |
-
|
| 25 |
-
.eyebrow { font: 11px/1 ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; letter-spacing: 0.15em; color: rgba(74, 222, 128, 0.7); margin: 0 0 12px; }
|
| 26 |
-
h1 { color: var(--strong); font-size: 2.4rem; line-height: 1.15; margin: 0 0 12px; }
|
| 27 |
-
h2 { color: var(--accent); font-size: 1.2rem; margin: 40px 0 10px; }
|
| 28 |
-
h3 { color: var(--strong); font-size: 1rem; margin: 22px 0 6px; }
|
| 29 |
strong { color: var(--strong); }
|
| 30 |
-
.lede { font-size: 1.1rem; margin: 0 0 20px; }
|
| 31 |
-
.note { font-size: 0.85rem; color: var(--muted); border-left: 2px solid var(--line); padding-left: 12px; margin: 20px 0 0; }
|
| 32 |
-
|
| 33 |
-
.actions { display: flex; flex-wrap: wrap; gap: 12px 20px; align-items: center; margin: 0; }
|
| 34 |
-
.btn { display: inline-block; padding: 10px 18px; border: 1px solid var(--accent); color: var(--accent); font: 600 14px/1 ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; letter-spacing: 0.05em; border-radius: 4px; }
|
| 35 |
-
.btn:hover { background: rgba(74, 222, 128, 0.12); text-decoration: none; }
|
| 36 |
-
|
| 37 |
-
.shot { margin: 36px 0 0; }
|
| 38 |
-
.shot img { display: block; width: 100%; height: auto; border: 1px solid var(--line); border-radius: 6px; }
|
| 39 |
-
.shot figcaption { font-size: 0.8rem; color: var(--muted); margin-top: 8px; }
|
| 40 |
-
|
| 41 |
-
.flow { display: flex; flex-direction: column; align-items: stretch; gap: 6px; margin: 18px 0 0; }
|
| 42 |
-
.step { background: var(--panel); border: 1px solid var(--line); border-radius: 6px; padding: 10px 14px; font-size: 0.95rem; }
|
| 43 |
-
.step span { color: var(--muted); font-size: 0.85rem; margin-left: 6px; }
|
| 44 |
-
.step em { display: block; font-style: normal; color: var(--muted); font-size: 0.85rem; }
|
| 45 |
-
.step.prompt { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 0.85rem; }
|
| 46 |
-
.step.out { border-color: rgba(74, 222, 128, 0.4); color: var(--strong); font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; font-size: 0.85rem; }
|
| 47 |
-
.arrow { text-align: center; color: var(--accent); line-height: 1; }
|
| 48 |
-
|
| 49 |
-
ul { padding-left: 20px; margin: 8px 0; }
|
| 50 |
-
li { margin: 6px 0; }
|
| 51 |
-
.links ul { list-style: none; padding: 0; display: flex; flex-wrap: wrap; gap: 8px 20px; }
|
| 52 |
-
|
| 53 |
-
footer { margin-top: 48px; padding-top: 16px; border-top: 1px solid var(--line); font-size: 0.8rem; color: var(--muted); }
|
| 54 |
-
footer p { margin: 6px 0; }
|
| 55 |
-
|
| 56 |
-
@media (max-width: 480px) { h1 { font-size: 1.9rem; } }
|
| 57 |
|
| 58 |
/* Brand bar: the approved Copper Signal mark + wordmark, as on pcbeditor.com */
|
| 59 |
.brand { display: flex; align-items: center; justify-content: space-between; gap: 16px; max-width: 760px; margin: 0 auto; padding: 18px 16px 0; }
|
| 60 |
.brand a { display: inline-flex; align-items: center; gap: 10px; color: var(--strong); text-decoration: none; }
|
| 61 |
.brand img { display: block; width: 36px; height: auto; }
|
| 62 |
-
.wordmark { font: 700 20px/1
|
| 63 |
-
.brand .nav-link { color: var(--accent); font: 600 13px/1
|
| 64 |
.brand .nav-link:hover { text-decoration: underline; }
|
| 65 |
-
main { padding-top: 28px; }
|
| 66 |
|
| 67 |
-
|
| 68 |
-
.
|
| 69 |
-
|
| 70 |
-
.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 6 |
--strong: #ffffff;
|
| 7 |
--muted: rgba(255, 255, 255, 0.55);
|
| 8 |
--accent: #4ade80;
|
| 9 |
+
--mono: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
|
| 10 |
}
|
| 11 |
|
| 12 |
* { box-sizing: border-box; }
|
|
|
|
| 18 |
font: 16px/1.65 -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
|
| 19 |
}
|
| 20 |
|
|
|
|
|
|
|
| 21 |
a { color: var(--accent); text-decoration: none; }
|
| 22 |
a:hover { text-decoration: underline; }
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 23 |
strong { color: var(--strong); }
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 24 |
|
| 25 |
/* Brand bar: the approved Copper Signal mark + wordmark, as on pcbeditor.com */
|
| 26 |
.brand { display: flex; align-items: center; justify-content: space-between; gap: 16px; max-width: 760px; margin: 0 auto; padding: 18px 16px 0; }
|
| 27 |
.brand a { display: inline-flex; align-items: center; gap: 10px; color: var(--strong); text-decoration: none; }
|
| 28 |
.brand img { display: block; width: 36px; height: auto; }
|
| 29 |
+
.wordmark { font: 700 20px/1 var(--mono); letter-spacing: 0.02em; }
|
| 30 |
+
.brand .nav-link { color: var(--accent); font: 600 13px/1 var(--mono); }
|
| 31 |
.brand .nav-link:hover { text-decoration: underline; }
|
|
|
|
| 32 |
|
| 33 |
+
/* The card, rendered from card-body.md */
|
| 34 |
+
.content { max-width: 760px; margin: 0 auto; padding: 28px 16px 64px; }
|
| 35 |
+
.eyebrow { font: 11px/1 var(--mono); letter-spacing: 0.15em; color: rgba(74, 222, 128, 0.7); margin: 0 0 12px; }
|
| 36 |
+
.content h1 { color: var(--strong); font-size: 2.2rem; line-height: 1.2; margin: 0 0 16px; }
|
| 37 |
+
.content h2 { color: var(--accent); font-size: 1.25rem; line-height: 1.35; margin: 44px 0 10px; }
|
| 38 |
+
.content p { margin: 0 0 14px; }
|
| 39 |
+
.content ul, .content ol { padding-left: 22px; margin: 8px 0 16px; }
|
| 40 |
+
.content li { margin: 6px 0; }
|
| 41 |
+
.content code { font-family: var(--mono); font-size: 0.88em; background: var(--panel); border: 1px solid var(--line); border-radius: 4px; padding: 1px 5px; }
|
| 42 |
+
|
| 43 |
+
/* An image paragraph: the picture, then its italic caption underneath */
|
| 44 |
+
.content p:has(> img) { margin: 26px 0; }
|
| 45 |
+
.content img { display: block; width: 100%; height: auto; border: 1px solid var(--line); border-radius: 6px; }
|
| 46 |
+
.content p:has(> img) em { display: block; margin-top: 8px; font-style: normal; font-size: 0.8rem; color: var(--muted); }
|
| 47 |
+
|
| 48 |
+
/* The last paragraph (licence and maker) reads as a footer */
|
| 49 |
+
.content > p:last-child { margin-top: 40px; padding-top: 16px; border-top: 1px solid var(--line); font-size: 0.8rem; color: var(--muted); }
|
| 50 |
+
|
| 51 |
+
.actions { display: flex; flex-wrap: wrap; gap: 12px 20px; align-items: center; margin: 22px 0 0; }
|
| 52 |
+
.btn { display: inline-block; padding: 10px 18px; border: 1px solid var(--accent); color: var(--accent); font: 600 14px/1 var(--mono); letter-spacing: 0.05em; border-radius: 4px; }
|
| 53 |
+
.btn:hover { background: rgba(74, 222, 128, 0.12); text-decoration: none; }
|
| 54 |
+
|
| 55 |
+
@media (max-width: 480px) { .content h1 { font-size: 1.8rem; } }
|