diff options
| author | Paul Vincent Bezzina <109743463+Vertrex-star@users.noreply.github.com> | 2026-10-14 22:53:06 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-10-14 22:53:06 +0100 |
| commit | 84fb8f025577f083560f7cccc92c5cd097bc8581 (patch) | |
| tree | 4ee0769021e36fb0f4c9dfd8f9b4a2909d3fa932 /README.md | |
| parent | d3a1f90d79215b4381827180a9a02701de7c93d2 (diff) | |
| download | PCB-Challenge-2026-84fb8f025577f083560f7cccc92c5cd097bc8581.zip | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -67,7 +67,7 @@ The keep out zone of the ESP32 antenna does not have to cover any PCB area, it c - Only default KiCad footprints, or footprints explicitly provided as part of the challenge, may be used. - Footprints must not be modified from the library originals (this will be checked via KiCad's "footprint does not match library" DRC warning; note that editing a local copy of the library will not bypass this check, and manual review may also be used). - All footprints must have correctly defined courtyard layers (F.CrtYd / B.CrtYd), and courtyards must not overlap between components. This is enforced via KiCad's built in "courtyard overlap" DRC check. -- Traces and vias may not be routed underneath IC footprints (i.e. within the courtyard area of any IC). +- Traces and vias may not be routed underneath IC footprints (i.e. within the courtyard area of any IC); given there is no shield underneath it. ### Silkscreen - Boards do not need to retain fully legible silkscreen labelling. |