Component class case examples

[sugenganthos]

Hello,
I want to ask about example case we can use component class as mentioned in

Post-V8 New Features and Development News

It is now possible to set component classes on symbols in eeschema. Directive labels attached to a rule area can now take a ‘Component Class’ field - any symbols within the rule area will be assigned that component class. The ‘Component Class’ field can be set directly on symbols too: [image] [image] Symbols can have more than one component class, taking on any that are defined directly on the symbol (or any of its sub-units), or from any directive labels attached to any rule areas which co…

[jmk]

Hi,
I doubt you will get many replies as this feature was only released five days ago into the Nightlies 8.99.
This means it has only been available for a day or two, so few have had a chance to test this.

[sugenganthos]

I just hope the developer who post this gives the example. I also wants to test this feature, but don’t know what usage.

[craftyjon]

It is primarily for use with custom design rules right now. It allows you to make custom rules that apply to certain components defined at the schematic level.

[JamesJ]

As @craftyjon says, these are for DRC rules currently. For example, you might have a set of components that are very noise-sensitive, in a Component Class called ‘FrontEnd’. You could place a rule area on the PCB also called ‘FrontEnd’, and have the following DRC rule to ensure all the components are in an area you keep electrically clean:

(rule FrontEnd
   (condition "A.hasComponentClass('FrontEnd') && !A.insideArea('FontEnd')")
   (constraint disallow footprint)
)

There are some other use-cases to come, but these depend on features that haven’t yet been released.

[sugenganthos]

It’s worth to try. But not now, since I’m not good creating DRC rules