How to disable thermals in localized GND pours?

[senso]

Good evening, so here I am playing around with Altium and I'm sort of starting to understand a little bit more of the Query system, and I can in fact have pours with and without thermals, different sizes and what not, but only if the pour is connect to some net that is NOT ground, here is what I want to do:



I have already tried using InNamedPolygon, InPolygon and some other random things but the GND vias always have the thermals enabled, yes I have tried changing the Priorities, and putting the rule in either the Polygon Connect Style and in the Power Plane Connect Style, is there something I'm missing/failling to understand(it must be me, of course).

Care to enlighten me?

Best regards.

[ajb]

You can get all vias to direct connect by using IsVia, would that work for you?  Simpler than having to name polygons.

[free_electron]

write a rule

if isvia and innamedpolygon 'blabla'  -> directconnect

[senso]

The isVia works, but it would remove thermals in all the vias, maybe not a bad thing and in this situation can work, but I would like to know how to do it using named polygons, its a more powerful/flexible option in my view.

I will try that Free_electron.

[free_electron]

oopsie i made a mistake  you need IsNamedPolygon , not InNamedPolygon.

we are not testing if we belong to the polygon (In...),  we are testing if we connect to (Is)

so :

Make a polygon style Rule :

Where the first object matches - Advanced  - isvia
Where the second object matched , advanced - Isnamedpolygon('blabla')
Connect style - direct connect

don't forget to increase its priority to sit above other rules ( bottom left of window : increase prorities and shove this rule to the the top.

i just tried it . works flawless.

if you have more than one polygon you can alter the 'where the second object matches to

Isnamedpolgon('firsrone') or Isnamedpolgon('secondone')

and so on
or you could make a polygon class and simply test against the class.

[ajb]

Speaking of understanding the query system, as you start to do more advanced queries, you should be aware that operator precedence may not be as you'd expect, and as far as I know is undocumented.  So to be on the safe side, use brackets wherever there may be any ambiguity to ensure that the query is evaluated the way you intend--that can save you a lot of frustration!

[free_electron]

i always use brackets. even in maths. for two reasons :

1) i can never remember what goes first
2) i can't be bothered to try to learn what goes first

has kept me out of trouble all my life.

[senso]

Just tried it, works perfectly, I was also doing it for other nets/polygons and I was doing it a little different, I had All in the second part of the query, it worked, but now I understand the beast a tiny bit better.

Thanks for the help Free_electron and AJB.

[free_electron]

Just tried it, works perfectly, I was also doing it for other nets/polygons and I was doing it a little different, I had All in the second part of the query, it worked, but now I understand the beast a tiny bit better.

Thanks for the help Free_electron and AJB.

i f you really want to unleash the full power of Altium : dig into filter expressions and manipulating the SCH list and PCB list viewers. Then hop into writing scripts. you can make this monster do amazing tricks.

[T3sl4co1l]

Just tried it, works perfectly, I was also doing it for other nets/polygons and I was doing it a little different, I had All in the second part of the query, it worked, but now I understand the beast a tiny bit better.

Thanks for the help Free_electron and AJB.

i f you really want to unleash the full power of Altium : dig into filter expressions and manipulating the SCH list and PCB list viewers. Then hop into writing scripts. you can make this monster do amazing tricks.

I was comparing a new schematic (captured by hand from a customer PDF) to the bill of materials, earlier today.  This involves a combination of filtering, sorting in the List, selecting the components you're checking, and comparing that listing to the spreadsheet -- say by copy+pasting the column into the spreadsheet and comparing the list, element by element, to see that they match up.  Which checks that you know you have the right designators, and the right number of them.  Then, since the listings line up, you can add the attributes wholesale to the components in the schematic with a single paste operation.  A pain to set up, but very powerful.

Also, once you have that part list, filtering it again is easy: make a column beside the designators that formats it as "(Name = '<refdes>') OR", repeat for all <refdes>, copy the column and paste it in the filter box.  After a few seconds of thinking, Altium determines your selection / mask.

...

Afraid I don't have much to contribute to the thread, as it's already been answered...   I will add my preference though: I merely assign all via-in-poly as direct.  As far as I know, the only downside to this approach is making them difficult to solder, if you should ever need to add a jumper/bodge wire to one.  However, I also put accessible test points (which do form thermals) on all nets (near 100% nodal coverage), so I doubt that it's a big deal.

I also like to tent vias-in-poly, since it looks sexier.  However, it is helpful to keep a few open, rather than tenting all of them, in case you need additional "accidental test points" shall we say.

Tim

[74HC04]

oopsie i made a mistake  you need IsNamedPolygon , not InNamedPolygon.

we are not testing if we belong to the polygon (In...),  we are testing if we connect to (Is)

Thank you very much for posting this, free_electron. You just saved me from pulling my hair out!