Hi Charlie,Originally posted in cdnusers.org by andyk
How have you been?
I thought about somthing like this a few months back, but never got the time to investigate this.
I believe you if you say that you can't access symbol level attachements, which in a way is in line with the hierarchy architecure for Allegro platform tools. What I mean is that once the symbol is instantiated, it becomes a different component with unique attributes etc. Kind of like hierarchical block in ConceptHDL.
A solution could be to create an attachement in the board file that tracks all components by refdes and their respective symbol revision. In other words, after you placed a compmonent you go out and find the revision of the symbol (where ever that comes from; i.e File system like ADW or systems like Windchill or Agile ;-)) add update the brd revision attachment list. Similarly you then can write startup routines that check the database symbol revision against the PDM system.
Think about linking padstacks, shapes and all the other good stuff and you have a pretty good solution in place that ensures consistent symbol usage.
I'll investigate this a bit over the next weeks and let you know if their is a way in SKILL to access this type of info. This shouldn't be to hard to do.