<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>PCB Libraries Forum : Features &amp; Training</title>
  <link>https://www.PCBLibraries.com/forum/</link>
  <description><![CDATA[This is an XML content feed of; PCB Libraries Forum : Features &amp; Training : Last 10 Posts]]></description>
  <pubDate>Tue, 14 Apr 2026 22:12:44 +0000</pubDate>
  <lastBuildDate>Thu, 18 Sep 2025 00:40:00 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.07</generator>
  <ttl>30</ttl>
  <WebWizForums:feedURL>https://www.PCBLibraries.com/forum/RSS_topic_feed.asp?FID=35</WebWizForums:feedURL>
  <image>
   <title><![CDATA[PCB Libraries Forum]]></title>
   <url>https://www.PCBLibraries.com/forum/forum_images/PCBLForumLogo.gif</url>
   <link>https://www.PCBLibraries.com/forum/</link>
  </image>
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14059.html#14059</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=15739">dramos</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 18 Sep 2025 at 12:40am<br /><br />Dear Tom and Team,<div><br></div><div>Many thanks for your comments. They give me many ideas to conduct the meeting in the desired way.&nbsp;</div><div><br></div><div>After reading the FED-18 document, I could imagine that there could be the problem you described. Something similar happened to me with Tantalum caps. In my opinion, the most interesting thing is to read how other people deal with similar problems you had. To see the same problem from another perspective. But any way, it is an interesting document.</div><div><span style=": rgb251, 251, 253;"><i>"A CAD Librarian would have to know what a good nominal dimension is and a reasonable tolerance." </i>For that purpose we should learn more and more about pcb fabrication and assembly. This is what makes our job so challenging, always you find something new to learn, a new concept or idea for fooprints, a new assembly technics,...</span></div><div><span style=": rgb251, 251, 253;">Thanks again for your interesting comments.</span></div><div><span style=": rgb251, 251, 253;">Regards,</span></div><div><span style=": rgb251, 251, 253;">david</span></div>]]>
   </description>
   <pubDate>Thu, 18 Sep 2025 00:40:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14059.html#14059</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14048.html#14048</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=3">Tom H</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 16 Sep 2025 at 4:08pm<br /><br />When I tried to convince Dieter Bergman to change the zero component orientation back to the original rotation, Dieter just shrugged his shoulders and said "Let the best standard win". Once a standard is published it takes years to undo anything.&nbsp;<div><br></div><div>Jami Smith had a compelling explanation (he sounded like a salesman) and Karen wanted to give the attendees an opportunity to vote on the subject. She forgot that 90% of the people in the conference meeting at APEX were not on the 1-13 committee. People just walked in to find out what was going on and they got a chance to vote on a very important issue. In hindsight, I could have swayed the vote by simply mentioning IPC-SM-782 but I didn't and the industry suffered a major bad decision.&nbsp;</div><div><br></div><div>The FED Proportional Pad Stack feature was recently added to Footprint Expert, but we ran into a problem with calculating pad stack using percentages of package dimensions. Example: The 0805 chip component family has a dozen different heights and to calculate the Toe uses 40% of the package height. This would create 12 different footprints for the same Case Code.&nbsp;</div><div><br></div><div>So we used the IPC J-STD-001 to calculate an acceptable Toe for a 0805 chip component. We then took every component family and every terminal lead and created Toe, Heel and Side goals that would be acceptable to meet J-STD-001 assembly. You can use Footprint Expert Nominal Calculation Mode but you need knowledge of solder joint goals. We did a good job at creating the default solder joint goal values, but they are intended to be adjusted by the end user.&nbsp;</div><div><br></div><div>When you download hundreds of thousands of component datasheets and compare the manufacturer recommended pattern to the Nominal Calculation Mode, you realize the manufacturers do not use Min/Max calculations. They use Nominal Package Dimensions and apply a Toe, Heel and Side (just like the FED Volume 18 concept). Component manufactures don't use the tolerances they publish in their datasheets for their recommended pad stack pattern.&nbsp;</div><div><br></div><div>The IPC-7352 uses Min/Max Calculation Mode which is dependent on the mfr. package tolerances to form the solder joint goals. The major flaw in the Min/Max technology is that component manufacturer tolerances are too robust or not truly accurate and sometimes just composed and unrealistic. The CAD Librarian must be familiar with package tolerances and spot bad tolerance data in the mfr. datasheets.&nbsp;</div><div><br></div><div>Example: for years SOIC manufacturers had an 'L' tolerance of 0.41 mm X 1.27 mm. This tolerance is way too robust and not realistic for today's machine technology. This tolerance makes the pad length way too big. A CAD Librarian would have to know what a good nominal dimension is and a reasonable tolerance. Same concept applies to every component family and terminal lead in the electronics industry. Use reasonable tolerances.&nbsp;</div><div><br></div><div>BTW: it looks as though component manufacturers are finally realizing that their package and terminal tolerances impact the pad stack calculation and they are reducing their tolerances to be closer to reality. It took us long enough to get the component manufacturers to use standard package dimension characters and standard component family name references. It was out of control 20 years ago.&nbsp;</div><div><br></div><div>All the best to the CAD librarians around the world who have to make these decisions everyday. I wish all of you good luck in making the best informed choices for your CAD library.</div><div><br></div>]]>
   </description>
   <pubDate>Tue, 16 Sep 2025 16:08:41 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14048.html#14048</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14047.html#14047</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=15739">dramos</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 16 Sep 2025 at 3:02pm<br /><br />Hi,<div><br></div><div>Many thanks for the explanation, for letting know us why IPC-7351C never existed. I remember that we waited for long for the new "C" version and at the end it was named&nbsp; &nbsp;IPC-7352 and it was downgraded to a "guideline".</div><div>Do you think the IPC will recover in the future the "spirit" of the IPC-SM-782 about pin1 orientation? Perhaps so many time doing the things without knowing "why" in that way, that someone will want to standardize it with any reason...</div><div><br></div><div>After reading your grate explanation about what happened, I have a question about it: Why Ms. K.McConnell accepted the explanation of Mr. J.Smith?</div><div><br></div><div>Thanks to PCBFE I read a very interesting article from Mr.&nbsp;<span style=": rgb251, 251, 253;">Rainer Taube about "New Proportional Land Dimmension" and after that I read the full article in FED-18, do you think this new concept will be more visible in a close future?</span></div><div><span style=": rgb251, 251, 253;">Could it replace the maths of IPC-7352 and the solder joints concepts?</span></div><div><span style=": rgb251, 251, 253;"><br></span></div><div><span style=": rgb251, 251, 253;">Many thanks again for sharing your experiences and knowledge.</span></div><div><span style=": rgb251, 251, 253;"><br></span></div><div><span style=": rgb251, 251, 253;">Best regards,</span></div><div><span style=": rgb251, 251, 253;">david</span></div><div><span style=": rgb251, 251, 253;"><br></span></div><div><span style=": rgb251, 251, 253;"><br></span></div><div><br></div>]]>
   </description>
   <pubDate>Tue, 16 Sep 2025 15:02:24 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14047.html#14047</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14010.html#14010</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=3">Tom H</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 11 Sep 2025 at 9:20am<br /><br />You need to know why IPC-7351 zero component orientation came into existence.&nbsp;<div><br></div><div>I joined the 1-13 IPC Land Pattern Committee in 1999 to help Dieter Bergman with a IPC-SM-782 software calculator to replace the IPC on-line land pattern calculator that was very expensive for IPC to maintain.&nbsp;</div><div><br></div><div>My first goal was in 2000 to transition from using imperial units to designing PCB library parts and PCB layout using the metric measurement system. The first calculator Jeff and I created was an Excel spreadsheet with called LandCalc. It was primarily SMD and only supported metric units. This was to run all tests to ensure the IPC mathematical model for min/max calculations was perfect.&nbsp;</div><div><br></div><div>The first calculators only had one rotation 'Pin 1 Lower Left' which was what the IPC-SM-782 supported since March 1987. After all, it was just an Excel spreadsheet and we didn't have the luxury of multiple rotations.</div><div><br></div><div>It took 2 years to add all the component families and finalize the min/max mathematical model. Then thanks to Philip Restall in the UK, we added a CAD tool translator for Mentor Graphics PADS. PADS was ASCII format so it was easy to figure out and we renamed the Excel spreadsheet to LandWiz. We freely distributed LandWiz on a website <a href="http://www.pcbstandards.com" target="_blank" rel="nofollow">www.pcbstandards.com</a> and had lots of downloads.&nbsp;</div><div><br></div><div>Then in 2003 we started writing code for the first software program which was Land Pattern Wizard. We shortened the name to LP Wizard. It was unique because there was only one footprint rotation 'Pin 1 Lower Left' because user feedback wanted us to fully dimension the resulting footprint to make it easy to QC.&nbsp;</div><div><br></div><div>Then IEC introduced the 3-Teir PCB library solution and we had to change everything to add the Least, Nominal and Most solder joint goals. This took another year to implement into the software tool.&nbsp;</div><div><br></div><div>We completed LP Wizard in 2004 with 3-Teirs, lower left was the zero component orientation and metric units only. We delivered it to IPC to test and replace their on-line calculator.&nbsp;</div><div><br></div><div>IPC was interested in getting volunteers involved in the approval process and were signing up volunteers quickly. We invited industry experts in join the IPC committee. Unfortunately, many of the volunteers turned out to be takers rather than givers. They attended meetings get information rather than provide information.&nbsp;</div><div><br></div><div>IPC had the final 1-13 Land Pattern Committee meeting at the 2004 IPC APEX conference in Anaheim, CA. We invited everyone in the local area to attend, especially members of local IPC Designer Council members. I spoke at the local San Diego chapter meetings regarding this new technology and try to convince everyone to transition to the metric measurement system. One attendee at the meeting was Jami Smith. He liked to attend IPC Designer Council meetings to learn more about standards in the electronics industry. Jami said he was interested in helping with the new land pattern committee, but the committee had already completed their goal of upgrading IPC-SM-782 to IPC-7351. But there was one more meeting at IPC APEX in Anaheim, CA and Jami Smith attended the meeting. He was about 30 minutes late getting to the meeting and when he entered, he recognized me and sat next to me. I was running the projector through my lap top showing the committee the new LP Wizard software program and the IPC-7351 draft.&nbsp;</div><div><br></div><div>80% of the attendees at his final meeting were newbies who never attended a single Land Pattern meeting. They were just people who wanted to learn more about the new standard. Also, this was the first and last IPC Land Pattern Committee meeting that Jami Smith attended. We were all set to finalize the standard when Jami stood up to address the attendees. He claimed to have knowledge of EIA-481 and insisted that the EIA zero component orientation for pick and place machines was Pin 1 'Upper Left'. No one at the APEX meeting knew anything about EIA-481 so they took Jami's word that he was trying to contribute information that we were unaware of.&nbsp;</div><div><br></div><div>Vern Solberg was one of the committee leaders and he suggested a committee vote from everyone in the room. Don't forget that 80% of the attendees had never attended a standards meeting before and they were asked to vote on an important subject. Karen McConnell the committee chairman was there and she agreed with Jami Smith. Then when everyone voted, they sided with Karen and Jami and that was the turning point for the IPC-7351 Zero Component Orientation. Jami Smith left the meeting and no one ever saw him again. But the damage was done.&nbsp;</div><div><br></div><div>It took us 3 - 4 months to change all the footprint rotations in LP Wizard. IPC-7351 was released in 2005. IEC got involved and chastised IPC for changing the footprint rotation based on faulty information and a rash decision at a meeting that no one had the knowledge of what impact they had on the entire electronics industry. So IEC released the IEC 61188-7 which reverted back to IPC-SM-782 zero component orientation.&nbsp;</div><div><br></div><div>Dieter Bergman and I had a conversation in 2008 about changing the zero component orientation for IPC-7351B, but Dieter said that once a standard is released it's very difficult to say you were wrong and here's the correction. Dieter shrugged his shoulders and said "Let the best standard win". However, in 2014 the IEC standard was winning and Dieter agreed to change the zero component orientation in the new IPC-7351C. We had the kick-off meeting at IPC headquarters the week of July 15 - 19. We created the entire framework for the new totally upgraded IPC-7351 standard. I left the meeting and flew back to San Diego, CA and immediately started working that weekend on Chapters 5 for surface mount and 6 for through-hole. The following week on July 23, Dieter Bergman passed away. This was a devasting loss to the electronics industry but I was inspired to carry the torch and spent the next year writing the IPC-7351C with Rainer Taube in Germany. We introduced IPC-7351C to the Land Pattern Committee in 2016 and we worked on refining it for 6 years. Then we found out that Dieter never had the approval by the IPC executive committee for IPC-7351C and they shelved it, never to be released.&nbsp;</div><div><br></div><div>Bottom line is that the Pin 1 in the upper left for xero component orientation should have never been released and Jami Smith will go down in history for changing a standard that he had no business being involved in. Jami disappeared never to be heard from or seen again.</div><div><br></div><div>And now you know - the rest of the story...</div><div><br></div>]]>
   </description>
   <pubDate>Thu, 11 Sep 2025 09:20:34 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14010.html#14010</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14009.html#14009</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=15739">dramos</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 11 Sep 2025 at 7:04am<br /><br /><div>Dear Nick and Team,</div><div><br></div><div>In our company, there is a great discussion about the pin1 orientation. To use IPC-7351 or to use IEC-61188-7.&nbsp;</div><div><br></div><div>I've read the article of the Top, and at the end my conclusions are:</div><div>- IEC-61188-7, is and standard very extended in Europe and some countries in ASIA that over the years has been consistent, has not changed. In other hand IPC-7351 modified the criteria from IPC-SM-781.</div><div><span style="white-space: normal;"><span style="white-space:pre">	</span>In the article is mentioned that it was an error, could you tell me an example? I have not the experience of PCBFE.</span></div><div>- IEC-61188-7, is more close to the IEC-481 from the point of view of the pin1 on reel.</div><div>- JEDEC has pin1 in cuadrant 1.</div><div><br></div><div>Is there anything else that I missed that I could argue to convince to my colleagues to use IEC-61188-7?</div><div><br></div><div>That's true that PCBFE gives us the possibility to configure it, but we would like to use the&nbsp; same&nbsp; .opt file on each site of the company.</div><div><br></div><div>Thanks for your comments.</div><div>david</div><div><br></div>]]>
   </description>
   <pubDate>Thu, 11 Sep 2025 07:04:39 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post14009.html#14009</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : Logical Descriptions in Footprint Expert]]></title>
   <link>https://www.PCBLibraries.com/forum/logical-descriptions-in-footprint-expert_topic3481_post13847.html#13847</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=1">Nick B</a><br /><strong>Subject:</strong> Logical Descriptions in Footprint Expert<br /><strong>Posted:</strong> 07 Apr 2025 at 3:13am<br /><br /><div><div>Logical Descriptions are mostly used by the EE engineer in the schematic symbol. The Logical Description defines the electronic function of the device and is not usually imported into a PCB Footprint. The PCB designer is mostly interested in the Physical Description as it defines the physical attributes of the component package that solders to the PCB.</div><div><br></div><div>The Logical Description is usually in the schematic Bill of Materials (BOM) and that becomes part of the PCB designer's documentation for the CAD library which ties the schematic symbol with the PCB footprint. Logical Descriptions come from several places and there is no standard format that defines them. To achieve the highest level of automation, everything should be standardized. Even the Logical Description.</div><div><br></div><div>Organize the Logical Description by component family. Examples: IC, Transistor, Inductor, Capacitor, Connector, Header, Resistor, Crystal.</div><div><br></div><div>Semiconductor datasheets usually provide the Logical Description on the first page of the component datasheet. Texas Instruments primarily produces semiconductors, and their datasheets are meta data friendly to allow you to copy/paste the Logical Description. Put 'IC' before the description.</div><div><br></div><div>It is important to note that most library PLM systems are ASCII data and "symbols" are not ASCII. Do not copy/paste symbols from a PDF datasheet into your PLM library. Symbols include:<br><img src="uploads/1/_a-25-04-07_Symbols.png" height="56" width="217" border="0" /><br></div><div><br></div><div>Here are sample semiconductor datasheets.&nbsp;</div><div><br></div><div>Note: if the Logical Descriptions contain the word '<b>with</b>', exclude everything after that to keep the Logical Description less than 80 characters.</div><div><br></div><div><b>Texas Instruments:</b></div><div><img src="uploads/1/_a-25-04-07_TI.png" height="81" width="683" border="0" /></div><div><b><font color="#0000ff">IC, USB Type-C DRP Port Controller</font></b></div><div><br></div><div><b>Linear Technology:</b></div><div><img src="uploads/1/_a-25-04-07_LINEAR_TECH.png" height="142" width="541" border="0" /><br></div><div><b><font color="#0000ff">IC, Low IQ, Dual 2 Phase Synchronous Step-Down Controller</font></b></div><div><br></div><div><b>Analog Devices:</b></div><div><img src="uploads/1/_a-25-04-07_ANALOG_DEVICES.png" height="131" width="679" border="0" /><br></div><div><b><font color="#0000ff">IC, Bidirectional, Wide Positive and Negative Sensing Range</font></b></div><div><br></div><div>Discrete components are much more complex than semiconductors because a single datasheet represents multiple devices with different values.</div><div><br></div><div><b>Note:</b> the rule for spaces in the Logical Description</div><div><br></div><div>Single capital letters like V, W, A have no space between the value and the letter.</div><div>Multiple capital letters like VWM, MHz, GHz have a space between the value and the letters.</div><div><br></div><div>Multiple letters that start with a capital letter like ‘Ohm' have a space between the value and the letters.</div><div><br></div><div>Multiple letters that start with a lower-case letter like uH, mOhm, uF, nH have no space between the value and the letters.</div><div><br></div><div><b>Note:</b> the rule for commas in the Logical Description. A space always follows the comma:</div><div><ul><li>Component Family,&nbsp;</li><li>Package,&nbsp;</li><li>Type,&nbsp;</li><li>Value,</li></ul></div><div>The component family always is first, followed by the package style and function and last the values.</div><div><br></div><div><b>Resistor</b>: Resistor, Chip, Thick Film, 196K Ohm, 1%, 1/8W</div><div><b>Capacitor 1</b>: Capacitor, Chip, Multilayer Ceramic, 2.2uF, 10%, 10V, X7R</div><div><b>Capacitor 2</b>: Capacitor, Molded, Tantalum Polymer, 22uF, 10%, 50V, X7R</div><div><b>Inductor</b>: Inductor, Low Profile, IHLP Power, 150nH, 26A, 2.5mOhm</div><div><b>Diode</b>: Diode, TVS, 350 VWM, 564 VC, 64A</div><div><b>Transistor</b>: Transistor, Bipolar NPN, 40V, 200mA, 300 MHz, 625mW</div><div><b>Crystal</b>: Crystal, Mobile Communications, 38.4 MHz</div><div><br></div><div>Connector Logical Descriptions can be organized by these parameters.</div><div><ol><li>Type: Connector, Header, Terminal Block</li><li>Number of Positions: 24 Position&nbsp;</li><li>Pin Pitch: 0.50 mm Pitch</li><li>Function: D-Sub, RJ45, HDMI, USB Type 2, Board-to-Board, FFC, BNC, Audio, Backplane</li><li>Number of Rows: Single Row, Dual Row</li><li>Sex: Male or Plug, Female or Receptacle or Socket</li><li>Rotation: Right Angle or Vertical</li></ol></div><div>Example: <b>Connector, 140 Position, 0.80 mm Pitch, Board-to-Board, Dual Row, Receptacle, Vertical</b></div></div><div><br></div><div><div><br></div><div><div><img src="https://www.pcblibraries.com/Products/FPX/img/FPX_Case1_25podb.png" height="234" width="176" border="0" align="left" /></div><div><div><div><b>PCB Footprint Expert</b></div><div>The Footprint Expert, in conjunction with the online part database, allows you to maintain quality Logical Description data! The Footprint Expert helps you create flawless PCB designs much more efficiently!</div></div><div><br></div><div><div>Get your&nbsp;<i>FREE</i>&nbsp;<b>Footprint Calculator</b>&nbsp;or&nbsp;<b>Footprint Expert</b>&nbsp;Evaluation License:</div><div><a href="https://www.pcblibraries.com/Register" target="_blank" rel="nofollow"><b>https://www.PCBLibraries.com/Register</b></a></div><div>Call:&nbsp;&nbsp;<b>847-557-2300</b></div><div><br></div></div></div></div></div>]]>
   </description>
   <pubDate>Mon, 07 Apr 2025 03:13:15 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/logical-descriptions-in-footprint-expert_topic3481_post13847.html#13847</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCBL Case Codes]]></title>
   <link>https://www.PCBLibraries.com/forum/pcbl-case-codes_topic3480_post13845.html#13845</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=1">Nick B</a><br /><strong>Subject:</strong> PCBL Case Codes<br /><strong>Posted:</strong> 30 Mar 2025 at 4:57pm<br /><br /><div><div>Component manufacturer Case Codes (Package ID's) are in the datasheet on the package dimension page. Every manufacturer has a unique case code for their specific package dimensions. If a Case Code does not exist for non-standard packages, the Part Number is used as a substitute. Sometimes discrete components will have a standard JEDEC or EIA Case Code for SODs, SOTs, Chips and Molded Body packages, but using the JEDEC and EIA Case Code name is misleading as every component manufacturer has slightly different dimensions than the JEDEC specifications. However, when a component manufacturer is acquisitioned by another manufacturer, the Case Codes could be changed.</div><div><br></div><div>Sometimes the manufacturer Part Number includes the Case Code.&nbsp;</div><div><br></div><div>Sample JEDEC Case Codes:</div><div><ul><li>TO-253 – SOT143</li><li>TO-261 – SOT223</li><li>TO-276 – DFN3</li><li>TO-252 – DPAK</li><li>DO-213 – MELF</li><li>DO-214 – Molded Body Diodes, SMA, SMB, SMC</li><li>DO-218 – SOD</li><li>DO-221 - SODFL</li></ul></div><div>Sample EIA Case Codes:</div><div><ul><li>SOT23 – Transistor&nbsp;</li><li>0201, 0402, 0603, 0805, 1206 – Chip</li><li>6032, 7343 – Molded Body</li><li>SOD123, SOD323, SOD523, SOD723 – Diode&nbsp;</li></ul></div><div>All electronic devices today have unique Part Numbers but sometimes share the same Case Code. All connector Part Numbers are the Case Code, as all connector solder patterns are unique.</div><div><br></div><div>Some component manufacturers provide good Case Codes. Here are examples of manufacturers that provide good Case Codes.</div><div><br></div><div><b>NXP Semiconductor</b> Case Codes start with SOD or SOT followed by a number. NXP refers to their Case Codes as 'Outline Version' and it's placed in the upper right corner of the component package dimensions page in the data sheet. <b>Nexperia</b> is a spinoff of NXP and they use the same SOD/SOT prefixes for their Case Codes.</div><div><p ="Ms&#111;normal"><font size="2">Here is the component package datasheet page with the Case Code SOT917-1 in the Upper Right.</font></p></div><div><img src="uploads/3/NXP_SOT917-1_Datasheet.png" height="700" width="569" border="0" /><br></div><div><br></div><div><b>Texas Instruments</b> Case Codes were originally JEDEC descriptors.</div><div><br></div><div>Example: D R-PDSO-G14&nbsp;</div><div><b>D</b> = TI identifier, <b>R</b> = Rectangle, <b>PDSO</b> = Plastic Dual Small Outline, <b>G</b> = Gullwing with 14 leads</div><div><br></div><div>When Texas Instruments acquired <b>National Semiconductor</b>, management preferred the NS Case Codes, so they are in the process of replacing all the JEDEC Case Codes with National Semiconductors.</div><div><br></div><div>The original TI Case Code D R-PDSO-G14 was recently changed to D0014A. The D0014A Case Code is assigned to over 5,000 TI Part Numbers. Over the past 10 years, TI updated Case Codes for over 100,000 Part Numbers. If you're into creating large PCB library databases, you're constantly updating Part Numbers with new Case Codes.&nbsp;</div><div>Here is a footprint and 3D model for TI&nbsp; Code D0014A.&nbsp;</div><div><br></div><div><img src="uploads/1/_a-2025-03-30_CaseCode1.png" height="338" width="500" border="0" /><br></div><div><p ="Ms&#111;normal"><font size="2">Here is the component datasheet page with the Case Code in the Upper Left and package dimensions.&nbsp;</font></p><p ="Ms&#111;normal"><font size="2"><img src="uploads/3/TI_D0014A_Datasheet.png" height="700" width="597" border="0" /><br></font></p></div><div><b>Analog Devices</b> Case Codes start with 05-08-XXXX, but they also use Case Codes from their acquisition of <b>Linear Technologies</b> that begin with CP followed by a hyphen – and a number. Example: CP-10-9</div><div><br></div><div>Analog Devices also acquisitioned <b>Maxim Integrated</b> and took over their Case Codes that start with 21- followed by a 4-character numeric code 21-XXXX.</div><div><br></div><div><b>Diodes, Inc.</b> Case Codes include a variety of JEDEC, EIA and Component Family abbreviations like DFN, QFN, SOP, SOT, DPAK, SOD and DIP. However, be aware that Diodes, Inc. uses the same Case Code, but the packages have various dimensions like SOT23. This is because Diodes acquired <b>ZETEX</b> and their SOT23 used different package dimensions but still uses the same Case Code. The SOT23 Case Code can be spelled in different ways, and each version has different package dimensions. Examples: SOT23, SOT-23, SOT-23-3, SOT23 DN, SOT23F and SOT23R.&nbsp;</div><div><br></div><div><b>On Semiconductor</b> changed its name to <b>onsemi</b>. The Case Codes for onsemi start with the word "CASE" followed by a space and a sequence of alphanumeric characters. Example: CASE 318BA = SOT-23. Onsemi acquisitioned <b>Fairchild Semiconductor</b> which uses JEDEC and component family abbreviations but most of their Case Codes start with the letter M and followed be a string of alphanumeric characters. Example: MA03D = SOT-23.</div><div><br></div><div><b>Infineon Technologies</b> uses various techniques for Case Code names. JEDEC – PG-TO-2522-3, IR followed by numbers, P-TQFP-100-3, PG-DSO- (pin qty), PG- Component Family abbreviation (LGA, SOP, QFP, etc.). Infineon acquisitioned <b>Cypress Semiconductor</b> and added their Case Codes that start with 001- and 51- followed by 5 numeric characters. Example: 001-04468 = QFN and 51-85064 = QFP.</div><div><br></div><div><b>Microchip Technology</b> uses component family abbreviations and the pin quantity for their Case Codes. Examples: 8-SOIC, 64-QFN, 128-QFP, etc. They also use the prefix C04- followed by 3 numeric characters and the letter to represent the revision. Microchip acquisitioned <b>Microsemi</b> and incorporated their Case Codes that have a prefix of CASE followed by a letter. Microchip also acquisitioned <b>Atmel</b> and incorporated their Case Codes which begin with a number that represents the pin quantity followed by a random letter. Example: 86T = 86-pin SOP</div><div><br></div><div><b>Cirrus Logic</b> uses the component pin quantity + package abbreviation. Examples: 32L QFP, 44L PLCC, 48L QFN, 14L SOIC, 10L DFN.</div><div><br></div><div><b>FTDI Chip</b> uses the package abbreviation + pin quantity. Examples: QFP48, QFN32, VQFN48, WQFN28, SOP20, TSSOP20, SSOP20.</div><div><br></div><div><b>Renesas Electronics</b> uses L + pin quantity + overall package dimensions + version letter. Examples: L10 3x3B, L12 3x3D, L16 4x4A, L8 2x2C. They also use an M + pin quantity + .XX + version letter. Examples: M14.173A, M16.15A, M10.118, M28.209. <b>Integrated Device Technology</b> was acquired by Renesas, and they used a P + the Lead Shape G = Gullwing, J + J-Lead, L = PLCC + the package abbreviation. Examples: PG24 = SOP24, PJ28 = SOJ28, PL68 = PLCC68.</div><div><br></div><div><b>Silicon Labs</b> uses package abbreviation + pin quantity. Examples: DFN6, LGA42, QFP100, MSOP10, SOIC8, QFN20. They also use Si as a prefix followed by a random number. Examples: Si53306, SI32261, SI5338B, Si5395J.</div><div><br></div><div><b>Wurth Elektronik</b> uses a 9-character code for their part numbers, and the part number is also used as the Case Code. Examples: 749022011, 750313995, 750032052, etc.&nbsp;</div><div>All the chip manufacturers use EIA Case Codes like 0201, 0402, 0603, 0805, 1206, etc. These manufacturers include AVX, Vishay, Yageo, Panasonic, KEMET, ROHM, KOA, Stackpole, Susumu, Ohmite.</div><div><br></div><div>All connector manufacturers have unique part numbers and no Case Codes, so the Part Number is used as the Case Code. The connector footprint names are <b><i>MfrNameAbreviation_MfrPartNumber</i></b>.</div><div><br></div><div>Non-standard Discrete and Semiconductor packages footprint names are always <b><i>MfrNameAbreviation_CaseCode</i></b>.</div><div><br></div><div>The main issue is that component manufacturers should do a better job at creating unique Case Codes that represent their package dimensions. The package code should be located on the component dimensions page of every datasheet, and it should be obvious to every CAD librarian, PCB designer and EE engineer. The Case Code should be added to every schematic symbol and appear in every Bill of Material (BOM).</div><div><br></div><div>Component manufacturers need to be aware that all PCB design layouts require solder patterns for every component package that they produce. Errors are created when manufacturers do not provide Case Code package IDs for all their package dimensions.&nbsp;</div><div>The upside for assigning Case Codes (package IDs) for every component is that a CAD librarian only needs to spend time creating the Case Code solder pattern and then the EE engineer could assign a Part Number with the correct Case Code.</div><div><br></div><div>Let's use Texas Instruments as an example for this concept. TI has 3,000 Case Codes and each one requires a unique solder pattern. This is what the PCB designer requires for the PCB layout. However, TI produces over 250,000 electronic device part numbers that map to the 3,000 Case Codes and that is a responsibility for the EE engineer. The PCB designer provides the Case Code to the EE engineer and the engineer assigns a part number with the correct manufacturer Case Code in the BOM. This will greatly enhance the productivity of the PCB designer and reduce errors, costs and turnaround time. Case Codes are a very important aspect of every electronic product.&nbsp;</div><div><br></div></div><div><div><br></div><div><div><img src="https://www.pcblibraries.com/Products/FPX/img/FPX_Case1_25podb.png" height="234" width="176" border="0" align="left" /><div><b>PCB Footprint Expert</b></div><div>To get a fully functional Footprint Expert license, complete the Evaluation License request on the Downloads page. Make sure to provide all the requested information, such as your company details and CAD outputs needed.<br><br></div></div><div><div>Get your&nbsp;<i>FREE</i>&nbsp;<b>Footprint Calculator</b>&nbsp;or&nbsp;<b>Footprint Expert</b>&nbsp;Evaluation License:</div><div><a href="https://www.pcblibraries.com/Register" target="_blank" rel="nofollow"><b>https://www.PCBLibraries.com/Register</b></a></div><div>Call:&nbsp;&nbsp;<b>847-557-2300</b></div><div><br></div></div></div></div>]]>
   </description>
   <pubDate>Sun, 30 Mar 2025 16:57:40 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcbl-case-codes_topic3480_post13845.html#13845</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : PCB Pad &amp; Footprint Orientation]]></title>
   <link>https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post13794.html#13794</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=3">Tom H</a><br /><strong>Subject:</strong> PCB Pad &amp; Footprint Orientation<br /><strong>Posted:</strong> 17 Feb 2025 at 4:50pm<br /><br />In PADS Layout, the Bottom (Opposite) Side footprint rotation is clockwise.&nbsp;<div><br></div><div>The Top Side footprints rotate counterclockwise.&nbsp;</div><div><br></div><div>It could be different for each CAD tool.&nbsp;</div><div><br></div>]]>
   </description>
   <pubDate>Mon, 17 Feb 2025 16:50:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/pcb-pad-footprint-orientation_topic3460_post13794.html#13794</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : What&#039;s Wrong with Your Footprint?!]]></title>
   <link>https://www.PCBLibraries.com/forum/whats-wrong-with-your-footprint_topic3404_post13772.html#13772</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=1">Nick B</a><br /><strong>Subject:</strong> What&#039;s Wrong with Your Footprint?!<br /><strong>Posted:</strong> 30 Jan 2025 at 12:13pm<br /><br />The free&nbsp;<b>Footprint Calculator</b>&nbsp;and the&nbsp;<b>Footprint Expert</b>&nbsp;are compared here:<div><div><a href="https://www.pcblibraries.com/products/compare" target="_blank" rel="nofollow"><b>https://www.pcblibraries.com/products/compare</b></a></div><div><br></div><div>To download and use the free&nbsp;<b>Footprint Calculator</b>:</div><div><br></div><div>1. Login at&nbsp;<a href="https://www.pcblibraries.com/downloads" target="_blank" rel="nofollow"><b>https://www.PCBLibraries.com/downloads</b></a><b><br>&nbsp; &nbsp;&nbsp;</b><i>(login with existing account, or register for free)</i></div><div><br></div><div>2.&nbsp;If you see this button, click it:<br><img src="https://www.pcblibraries.com/forum/uploads/1/-a250124b-Calc1.png" height="41" width="168" border="0" /><br><br>3. If you do not see it, you already have a Key. Click this button to download:<br><img src="https://www.pcblibraries.com/forum/uploads/1/-a250124b-Calc2_2025-01-24_22-57-44.png" height="96" width="258" border="0" /><br><br>4. Install and run the Calculator, then use your&nbsp;<b>Email</b>&nbsp;and&nbsp;<b>Key</b>&nbsp;(full key displayed on Download page) to activate the Calculator license.</div><div><br></div></div><div><br></div><div><div><img src="https://www.pcblibraries.com/Products/FPX/img/FPX_Case1_25podb.png" height="234" width="176" border="0" align="left" /><div><b>PCB Footprint Expert</b></div><div>To get a fully functional Footprint Expert license, complete the Evaluation License request on the Downloads page. Make sure to provide all the requested information, such as your company details and CAD outputs needed.<br><br></div></div><div><div>Get your&nbsp;<i>FREE</i>&nbsp;<b>Footprint Calculator</b>&nbsp;or&nbsp;<b>Footprint Expert</b>&nbsp;Evaluation License:</div><div><a href="https://www.pcblibraries.com/Register" target="_blank" rel="nofollow"><b>https://www.PCBLibraries.com/Register</b></a></div><div>Call:&nbsp;&nbsp;<b>847-557-2300</b></div><div><br></div></div></div>]]>
   </description>
   <pubDate>Thu, 30 Jan 2025 12:13:02 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/whats-wrong-with-your-footprint_topic3404_post13772.html#13772</guid>
  </item> 
  <item>
   <title><![CDATA[Features &amp; Training : Free Footprint Calculator or Footprint Expert?]]></title>
   <link>https://www.PCBLibraries.com/forum/free-footprint-calculator-or-footprint-expert_topic3466_post13771.html#13771</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.PCBLibraries.com/forum/member_profile.asp?PF=1">Nick B</a><br /><strong>Subject:</strong> Free Footprint Calculator or Footprint Expert?<br /><strong>Posted:</strong> 30 Jan 2025 at 12:12pm<br /><br /><font size="2"><i>The details below are just some of the differences (yes, there are more!) between the Footprint Expert footprints and the libraries available all over the internet. Most don’t realize how lacking all those footprints online really are, but they can be much worse than lacking when they actually cost you money.</i></font><br><br><t></t><t></t><t></t><t></t><t></t><t></t><t></t><t></t><t></t><t></t><table ="msotablegrid"="" border="0" cellspacing="0" cellpadding="0" style="border-collapse: collapse; border: n&#111;ne;"><t><tr><td width="319" valign="top" style="width: 239.5pt; padding: 0in 5.4pt;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><b><font size="4">Footprint Expert</font></b></p></td><td width="320" valign="top" style="width: 239.7pt; padding: 0in 5.4pt;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><b><span style="font-size: 12pt;">Source 1</span></b><span style="font-size: 12pt;"><o:p></o:p></span></p></td><td width="320" valign="top" style="width: 240.3pt; padding: 0in 5.4pt;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><b><span style="font-size: 12pt;">Source 2</span></b><span style="font-size: 12pt;"><o:p></o:p></span></p></td></tr><tr style="height: 0.85in;"><td width="319" valign="bottom" style="border-top: n&#111;ne; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 0.85in;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><o:p>&nbsp;<img src="https://www.pcblibraries.com/forum/uploads/1/image003.png" height="129" width="304" border="0" /></o:p></p></td><td width="320" valign="bottom" style="border-right: n&#111;ne; border-left: n&#111;ne; width: 239.7pt; padding: 0in 5.4pt; height: 0.85in;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><img src="https://www.pcblibraries.com/forum/uploads/1/image004.png" height="141" width="300" border="0" /></p></td><td width="320" valign="bottom" style="border-right: n&#111;ne; border-left: n&#111;ne; width: 240.3pt; padding: 0in 5.4pt; height: 0.85in;"><p ="ms&#111;normal"="" align="center" style="margin-bottom: 0in; text-align: center; line-height: normal;"><o:p><img src="https://www.pcblibraries.com/forum/uploads/1/image005_2024-07-31_04-01-30.jpg" height="129" width="305" border="0" />&nbsp;</o:p></p></td></tr><tr style="height: 15.6pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.6pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb21, 96, 130;">AUTO-GENERATED</span></b><span style="font-size: 10pt;">&nbsp;library parts use predefined or user-modified rules – share across your organization;<br><b>RULES-based, auto-generated part library</b><o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.6pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb21, 96, 130;">MANUALLY CREATED</span></b><span style="font-size: 10pt;">&nbsp;by many different people, using&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">countless rules</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">– results in a board with inconsistently built parts,&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">far more prone to introduction of costly errors</span></b><span style="font-size: 10pt;">; massive variations in parts inconducive to standardized rule-based library</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.6pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.6pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Built to exact datasheet specification</span></b><span style="font-size: 10pt;">, either Metric or Mils<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.6pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Units vary based on source</span></b><span style="font-size: 10pt;">, and Metric often converted from Mils with rounded-off measurements;&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">converting pin pitch often results in leads not fully centered on pads</span></b><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">User-defined consistency</span></b><span style="font-size: 10pt;">&nbsp;of line widths for all parts<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Many different line widths</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">used across different footprints due to&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">lack of standard rules</span></b><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Accurate contour courtyards</span></b><span style="font-size: 10pt;">&nbsp;are auto generated<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Sloppy or non-existing contour courtyards</span></b><b><span style="font-size: 10pt;"><o:p></o:p></span></b></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Relevant data</span></b><span style="font-size: 10pt;">: Footprint Name, Physical and Logical Descriptions, datasheet link, and more<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Nothing, or inconsistent random data</span></b><b><span style="font-size: 10pt;"><o:p></o:p></span></b></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Auto-generated keep outs</span></b><span style="font-size: 10pt;">&nbsp;on all non-plated holes for copper poly shapes, traces and vias<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Missing keep-out will cause DRC errors</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">at the manufacturer if copper, traces, and vias are placed within 0.25 mm of the non-plated hole</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Pin 1 polarity markers for silkscreen and assembly<o:p></o:p></span></b></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Pin 1 markings missing or vary</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">in shape and in size</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Footprint Origin at center</span></b><span style="font-size: 10pt;">&nbsp;of gravity<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Footprint Origins randomly placed</span></b><b><span style="font-size: 10pt;"><o:p></o:p></span></b></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Uniform, silkscreen outlines are whole objects</span></b><span style="font-size: 10pt;">&nbsp;mapped to the maximum package dimensions<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Silkscreen is fragmented</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">and mapped to the nominal package dimensions</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><span style="font-size: 10pt;">Clear, consistent, intelligently placed markings to&nbsp;<b>minimizes use of board space</b><o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><span style="font-size: 10pt;">Inconsistent and extra markings and excessive courtyards&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">requires more placement space</span></b><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Consistent silkscreen trimming</span></b><span style="font-size: 10pt;">&nbsp;around all pads<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Inconsistent and random silkscreen trimming</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">around pads</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt;">Solder Mask swell auto-applied</span></b><span style="font-size: 10pt;">&nbsp;and configurable<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Inconsistent solder mask swell</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">from one footprint to another</span><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-top: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><span style="font-size: 10pt;">Through-hole&nbsp;<b>pad stack hole sizes automatically defined</b>&nbsp;by maximum terminal lead diameter, and&nbsp;<b>pad size auto-calculated</b>&nbsp;by 1.5 x hole diameter<o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-top: n&#111;ne; border-right: n&#111;ne; border-bottom: 1pt dashed rgb191, 191, 191; border-left: n&#111;ne; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><b><span style="font-size: 10pt; color: rgb192, 0, 0;">Lack of published, consistent rules&nbsp;</span></b><span style="font-size: 10pt;">to define through-hole pad stacks make it impossible for proper quality control of resulting footprint,&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">results in capriciously calculated footprints</span></b><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr><tr style="height: 15.4pt;"><td width="319" valign="top" style="border-width: initial; border-style: n&#111;ne; border-color: initial; width: 239.5pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><span style="font-size: 10pt;">Non-plated holes have smaller pad sizes to&nbsp;<b>prevent copper slivers after drilling process</b><o:p></o:p></span></p></td><td width="640" colspan="2" valign="top" style="border-width: initial; border-style: n&#111;ne; border-color: initial; width: 480pt; padding: 0in 5.4pt; height: 15.4pt;"><p ="ms&#111;normal"="" style="margin-bottom: 0in; line-height: normal;"><span style="font-size: 10pt;">Non-plated holes have a pad size equal to the hole size create&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">risk of copper slivers</span></b><span style="font-size: 10pt; color: rgb192, 0, 0;">&nbsp;</span><span style="font-size: 10pt;">after the drilling process; the&nbsp;</span><b><span style="font-size: 10pt; color: rgb192, 0, 0;">plane antipad is randomly defined with no obvious rules</span></b><span style="font-size: 10pt;"><o:p></o:p></span></p></td></tr></t></table><br><div><img src="https://www.pcblibraries.com/Products/FPX/img/FPX_Case1_26pod.png" height="234" width="176" border="0" align="left" /></div><div><i><font size="3"><span style="font-weight: bold; line-height: 17.12px; font-family: Aptos, sans-serif;">The Footprint Expert automates footprints to perfection.</span><span style="line-height: 17.12px; font-family: Aptos, sans-serif;">&nbsp;Professional, detailed, and accurate parts – all built consistently with identical rules, regardless of how many people are involved in your library development.</span></font></i></div><div><div><br><span style="font-size: 12pt;">Get your FREE&nbsp;<b>Footprint Calculator</b>&nbsp;or&nbsp;<b>Footprint Expert</b>&nbsp;Evaluation License:<br></span><a href="https://www.pcblibraries.com/Register" target="_blank" rel="nofollow"><b>https://www.PCBLibraries.com/Register</b></a></div><p ="ms&#111;normal"=""><span style="line-height: 14.98px;"><font size="2">Call us -&nbsp;<b>847-557-2300</b></font></span></p></div>]]>
   </description>
   <pubDate>Thu, 30 Jan 2025 12:12:42 +0000</pubDate>
   <guid isPermaLink="true">https://www.PCBLibraries.com/forum/free-footprint-calculator-or-footprint-expert_topic3466_post13771.html#13771</guid>
  </item> 
 </channel>
</rss>