Pad Stack Always X Exceed Y

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   When building a Oscillator Corner Concave.
In the generated padstack the Y width exceeds the X width and has a 270 degree rotation.

The pad could better be generated with a 0 degrees rotation and a X width exceeding the Y width.

This keeps the Pad Stack Library cleaner with less entries.

Regards,

Wim.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
PLTcbv Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 21 Aug 2012 Location: the Netherlands Status: Offline Points: 134	Post Options Post Reply Quote PLTcbv Report Post Thanks(0) Quote Reply Topic: Pad Stack Always X Exceed Y Posted: 25 Sep 2014 at 4:58am
	When building a Oscillator Corner Concave. In the generated padstack the Y width exceeds the X width and has a 270 degree rotation. The pad could better be generated with a 0 degrees rotation and a X width exceeding the Y width. This keeps the Pad Stack Library cleaner with less entries. Regards, Wim.



Tom H Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 05 Jan 2012 Location: San Diego, CA Status: Offline Points: 5716	Post Options Post Reply Quote Tom H Report Post Thanks(0) Quote Reply Posted: 25 Sep 2014 at 10:39am
	In our tool it doesn’t matter. Pin orientations will change with part re-orientation. Things like this are cleaned up when converted to the target CAD tool format.
	Stay connected - follow us! X - LinkedIn

PLTcbv Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 21 Aug 2012 Location: the Netherlands Status: Offline Points: 134	Post Options Post Reply Quote PLTcbv Report Post Thanks(0) Quote Reply Posted: 26 Sep 2014 at 12:13am
	This is the default view when making a part. The pad orientation is "270" and should be "0". If you use the Padstack Designer you can't create an offset in the Padstack when Y exceeds X. So i.m.o. always let X exceed Y. If you convert to Expedition ASCII out rotations are not cleaned up. So we have one pad with orientation "0" and one pad with "180"