Include/exclude component in/from BOM

[silvio3105]

Hi,

Can user somehow have (same) component but somehow place component without footprint.

In my case I have SH1106 1.3" I2C OLED display. I can solder that display on PCB and in that case I want to have that display in BOM.

In other case I want to mount display on enclosure, so in that case I want to place only display in schematic, but not on PCB and exclude component from PCB BOM.

[silvio3105]

Bump!

[jorge_garcia]

Hi @silvio3105,

I hope you're doing well. This sounds like a good use case for variants. If the component is populated then you solder it to the PCB and it's included on the default BOM ulp. If the component is not populated then it will not be included in the BOM.

Best Regards,

[silvio3105]

I'm not sure do I understand what you mean.

[jorge_garcia]

Hi @silvio3105,

I hope you're doing well. Since you could build the board in 2 different ways or "variants" you could use the Assembly Variants feature to create a variation of your board that doesn't have the screen populated. When you generate the bom.ulp you can select what variant to produce the BOM for. If you pick the default('') then the screen will be mounted to the PCB and soldered down. If you pick your other variant then the screen will not be populated on the PCB and the BOM will reflect that.

Let me know if you have any other questions.

Best Regards,

[silvio3105]

But in that case it will be big X over component in schematic.

[CGBenner]

@jorge_garcia 👆

[silvio3105]

Maybe he's on vacation?

[C.Nicks]

In the standard Eagle desktop version you can create a library part with the library attribute _EXTERNAL_ in order to have a schematic symbol and device without a footprint.

That part would have to be a separate version than a footprinted version.

I also use a custom BOM export script that will excluded any component with an BOM->EXCLUDE attribute regardless of the variant populated status.

Things like that might be a bit harder to handle in Fusion since the attributes within libraries are hard to find/modify.

[silvio3105]

I know for _EXTERNAL_ but c'mon, it's 2022, why mix old way with new?

[silvio3105]

Bump!