Hello everybody,
I am trying to define a new part in Part Developer within Allegro PCB Librarian XL and I have two questions. I really appreciate any help and guidance you could provide!
I'm defining different symbols for my part, so that either manually or through scripts (scr) a specific symbol can be chosen. This is how the Symbols tree structure looks like (please refer to screenshot below) - let's assume I'd like to define four symbols in total. The question is: if I try to rename them, the environment returns the following error: "The symbol cannot be renamed because the specified name is invalid. Reenter the name in the format sym_n, where n is a non-zero positive integer.". Is there any way to make a successful renaming? I have seen screenshots of tutorials online for Part Developer with symbols actually having names different than just sym_n.
QUESTION 2:
For another component I am defining, I would like the component's general structure to look like the following:
Basically, a very simple port consisting of a single symbol pin (with a name "B" and a Text "A") and a property which is a text (this wil act as a netlist, labeled as "C" in the picture above).
The question is the following: is it possible to define such component in a way that its properties can be modified as follows during the insertion in a cpm project (done either manually through "Add Component" or through a *.scr file execution)?
- The "A" label can be changed (that is, the Text associated to the symbol pin)
- "C" can be changed --> this is working for me, I can simply define it either if I add the component manually in a cpm project or if I add it through a script file;
- The orientation (rotation) of the whole structure can be changed. For example, mirrored or rotated, implying that the whole symbol adapts to the rotation. In the two screens below I mentioned to examples of this.
- So far I achieved all of this by defining different symbols of the same component, while I'd like to have just one symbol and change the properties I just mentioned "on the file" when the component needs to be added into the schematics.
Thank you!
Paolo