Mapping Silkscreen Outline to Body

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

   You are offering to choose whether to use Max, Min or Nominal body size when mapping silkscreen outline. However, this feature does not work for THD components. For example, you are not asking to enter min and max values of length and width for DIP packages, Headers, PGA packages and TO-220.
Let's compare PGA and BGA packages. For BGA package you ask to enter min and max values for D (length) and E (width), while for PGA you only ask for max values. Hence for PGA packages you can map silkscreen outline to maximum body size, but you are not able to map to minimum or nominal size. This leads to library inconsistency. Can you please explain why it is done the way it is done?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
JJonas Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 21 Apr 2014 Status: Offline Points: 113	Post Options Post Reply Quote JJonas Report Post Thanks(0) Quote Reply Topic: Mapping Silkscreen Outline to Body Posted: 11 Apr 2015 at 10:43pm
	You are offering to choose whether to use Max, Min or Nominal body size when mapping silkscreen outline. However, this feature does not work for THD components. For example, you are not asking to enter min and max values of length and width for DIP packages, Headers, PGA packages and TO-220. Let's compare PGA and BGA packages. For BGA package you ask to enter min and max values for D (length) and E (width), while for PGA you only ask for max values. Hence for PGA packages you can map silkscreen outline to maximum body size, but you are not able to map to minimum or nominal size. This leads to library inconsistency. Can you please explain why it is done the way it is done?



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: 13 Apr 2015 at 12:09pm
	We'll be going over every component family in the next 3 weeks to insure that they all follow the same rules and guidelines. This will be released in V2015.11 the 1st week of May.
	Stay connected - follow us! X - LinkedIn