In the symbol editor, how do I change the pin number of a specific pad stack. For example, I have a connector footprint (converted from an old 16.2 library) that has a row of pins 1 thru 10. There are two additional pins numbered 16 and 17, but I want them to be 11 and 12. I can not find a way to edit the pin number.
Further, suppose I wanted to make those two pins "mechanical" instead of electrical. How can this be done without deleting and adding the pin again?
Suppose I have to delete and re-add these two pins as mechanicals. How can I specify the coordinates where I want them located? I have tried typing the coordinates onto the command line using the "x ## ##" method, but it does not work.
You can display package Geometry/Pin number and go to edit/text and change the number.
For changing the pads to mechanical, I believe you have to delete and place them again. I may be wrong though.
In reply to Mstrghettorigg:
To make it a mechanical pin just delete the pin text (Edot - Delete)
In reply to steve:
Thanks guys, two very easy solutions.
What about the placing by coordinates issue? If I have a padstack attached to my cursor, if I enter the coordinates on the commandline (preceeded by "x") I get no result. In calls we pressed the tab key and a box came up to enter the coordinates. I don't seem to be able to get that working either.
Any "easy" solutions for this?
In reply to TH Designs:
I don't have any problem with the x # # in command line method of placing the pads.
You don't happen to have capital letter for "X" do you?
Have you tried placing it first and try it in the move command?
If you have the part on your cursor (floating), try the command line "pick xxx.xx yyy.yy" with the x/y coordinates. Equivalent to the LMB click to place the component.
In reply to Roger BFS:
BTW - if you are in the process of a "move" command, the "x 123" or "y 123" commands achieve relative delta coordinate moves/places.
Oops - sorry I mispoke. I meant to say "ix 123" and "iy 123" command lines for the relative move/place.
I had no problem doing this in class last week either..............
No capital "X".
I'm wondering........... I set the "x" key as a "funckey" to perform the "swap ends" command when routing (ala 16.2). This may be my problem. I'll remove it from the env file and try it again.