Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The silkscreen of unused components is not removed for .brd files #475

Closed
PrzemekBarczyk opened this issue Oct 28, 2024 · 3 comments
Closed

Comments

@PrzemekBarczyk
Copy link

PrzemekBarczyk commented Oct 28, 2024

I'm using your project to generate interactive BOMs for the EAGLE program. I've noticed discrepancies in the output file depending on whether the input file is a .brd file or a .json file (generated with brd2json.ulp).

If a project has a variant with hidden components, the BOM generated from the .json file does not include these components in either the table or the schematic. In contrast, for .brd files, the hidden components are only excluded from the table but remain visible on the schematic.

Below, I’ve attached screenshots to illustrate these differences.

Are the described differences intentional design decisions? Does the project allow for variant configuration using .brd files so that hidden components are also excluded from the schematic?

Thank you!

bom .json
BOM obtained using .json

bom .brd
BOM obtained using .brd

image
.brd in EAGLE

@PrzemekBarczyk PrzemekBarczyk changed the title Unused elements' silkscreen isn't removed The silkscreen of unused components is not removed for .brd files Oct 28, 2024
@qu1ck
Copy link
Member

qu1ck commented Oct 28, 2024

Silkscreen is expected to not be removed because it does not magically disappear from the board if you don't solder the component. The rendering is supposed to represent how the actual board looks, including pads and silk markings.

Not sure why using the json method shows that behavior but that method ulp is not maintained afaik, use native .brd support.

@PrzemekBarczyk
Copy link
Author

Thanks for the quick response!

@Funkenjaeger
Copy link
Contributor

I've added an issue to the brd2json repo regarding the incorrect behavior with the ULP (footprints missing for unpopulated components) - just for posterity, as I'm not inclined to fix it presently. As @qu1ck said, the ULP is essentially OBE at this point due to native .brd/.fbrd support in ibom which has been in place for just shy of 2 years now, so I've gone ahead and archived that repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants