Author Topic: Visibly applying paramters to components  (Read 3630 times)

0 Members and 1 Guest are viewing this topic.

Online ajbTopic starter

  • Super Contributor
  • ***
  • Posts: 2607
  • Country: us
Visibly applying paramters to components
« on: February 15, 2015, 09:31:20 pm »
I'm trying to apply a ClassName parameter on a set of components so that I can target them with a specific design rule in the PCB.  I can define a ClassName in each component's individual parameters, which works fine, but I'd really rather this be done in a visible way on the schematic (I'm also not sure how durable this approach is when synchronizing with libraries later on).  Using a blanket with a Parameter Set directive would seem to be the way to go, but this applies the ClassName parameter to the enclosed nets, not the enclosed components.  Is there some other way to make this work?
 

Offline free_electron

  • Super Contributor
  • ***
  • Posts: 8517
  • Country: us
    • SiliconValleyGarage
Re: Visibly applying paramters to components
« Reply #1 on: February 15, 2015, 11:26:23 pm »
what is the pcb rule you are trying to apply for the components ?
Professional Electron Wrangler.
Any comments, or points of view expressed, are my own and not endorsed , induced or compensated by my employer(s).
 

Online ajbTopic starter

  • Super Contributor
  • ***
  • Posts: 2607
  • Country: us
Re: Visibly applying paramters to components
« Reply #2 on: February 15, 2015, 11:47:47 pm »
At the moment it's a component clearance rule, but I'd like to know as a general question if there's a way to do this.  The rule in this particular case works exactly as intended with the ClassName applied in the component properties, no problems on the rule side of things. 

For the record, I also tried using a PCB Rule directive on the blanket covering the components in question, but I just wind up with a bunch of rules that target all of the nets contained in the blanket, and nothing targeting the components.
 

Offline free_electron

  • Super Contributor
  • ***
  • Posts: 8517
  • Country: us
    • SiliconValleyGarage
Re: Visibly applying paramters to components
« Reply #3 on: February 16, 2015, 04:27:01 am »
Yes there is a way to do this ,but you have to be VERY specific in the definition of the rule. If you just define it as clearance it will show up everywhere.
- draw your blanket.
- add parameter set
- make the parameter set touch the blanket.
- double click the parameter set symbol
- click 'add as a rule' button
- click 'edit rule values'
- under 'Placement':  pick 'Component Clearance Constrain't : The wizard will open. Set it up. click OK

done.



Professional Electron Wrangler.
Any comments, or points of view expressed, are my own and not endorsed , induced or compensated by my employer(s).
 

Online ajbTopic starter

  • Super Contributor
  • ***
  • Posts: 2607
  • Country: us
Re: Visibly applying paramters to components
« Reply #4 on: February 16, 2015, 05:12:43 am »
That was one of the first things I tried.  When I do that I get a component clearance rule between InNet() and All for each enclosed net, but those rules don't have any effect on the components (which makes sense, because components don't have a Net property).  Even if those rules did the trick, having 12 rules where only one is required is pretty ugly.
 

Offline free_electron

  • Super Contributor
  • ***
  • Posts: 8517
  • Country: us
    • SiliconValleyGarage
Re: Visibly applying paramters to components
« Reply #5 on: February 16, 2015, 05:23:02 am »
yep. you're right. for some reason it does 'innet'.. that's a bug.

report it.
Professional Electron Wrangler.
Any comments, or points of view expressed, are my own and not endorsed , induced or compensated by my employer(s).
 

Online ajbTopic starter

  • Super Contributor
  • ***
  • Posts: 2607
  • Country: us
Re: Visibly applying paramters to components
« Reply #6 on: February 16, 2015, 04:12:22 pm »
Okay.  It's frustrating how often I find myself wondering if I've run into a bug or if I'm just not going about it right.

Is this actually a bug, though?  Now that I check, I find three separate entries for this as a new feature request on Altium Live, but no indication there that it's worked previously (ie, that it's a bug).
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf