openscopeproject / openscopeproject/InteractiveHtmlBom

Rule areas in footprints generate excessively large outlines

Open
#570 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.6k
Forks
578
Avg merge
5h 24m
Merged PRs (30d)
2

Description

My footprints with rule areas (keep outs) cause the BOM to generate with extremely large footprint outlines.

Image Image

Removing the rule area from each footprint will remove all errors with the BOM, but this is not ideal for my design.

Interestingly, this error will sometimes be fixed when I remove the rule area and place it back. The first time I generate a BOM after, the outline occasionally generates correctly. However, I am not able to find a pattern with this behaviour (half of them will have correct outlines, half will not).

Placing the footprints on a new board by itself does not generate issues.

Placing the same footprints on a different project, or adding rule areas to footprints on an existing project will replicate this issue on that project.

This seems to be a common error and is independent of generating a BOM file when opening a KiCAD project the first time, or generating multiple times through a single session. The rule areas placed in the PCB Editor do not seem to affect the generation of the BOM.

I am running KiCAD 10.0.6, Plugin 2.12.0, and the latest version of MacOS.

Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the oversized footprint outlines during BOM generation with KiCad rule areas, then compare affected footprints with those on a standalone board. Check whether repeated generations and moving rule areas change the result. Done means rule areas no longer produce incorrect large outlines consistently across projects and sessions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.