You need to use EasyEDA editor to create some projects before publishing
header pins for wemos d1
1797 7
Kevin Greene 3 years ago
Hello. So I'm using the symbol for a wemos D1, on the PCB layout it place the holes correctly. But how do I add the header to the PCB? Kev
Comments
andyfierman 3 years ago
If I understand you issue correctly then unless you can find a footprint for a single piece header like a DIP socket but bigger then I think you will find that this topic covers your particular situation in detail: [https://easyeda.com/forum/topic/How-do-I-leave-the-labels-but-remove-the-parts-53430c692d204cb9be915c4d095988ec](https://easyeda.com/forum/topic/How-do-I-leave-the-labels-but-remove-the-parts-53430c692d204cb9be915c4d095988ec)<br> <br> To properly understand what is going on here, please read (2.2) in (2) in: [https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a](https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a)<br> <br> In particular Appendix A in the document (2.2) explains the use of the Add into BOM  and Convert to PCB  attributes to deal with this sort of situation.
Reply
andyfierman 3 years ago
Here is an example, DRC error-free copy of the OPs project in the topic above (done after reverting the connector names and then all the P1 and P2 connector pins and pads back to simple numbering): [https://oshwlab.com/andyfierman/teensy-grove-breakout-shield](https://oshwlab.com/andyfierman/teensy-grove-breakout-shield)
Reply
Kevin Greene 3 years ago
@andyfierman  thanks
Reply
Kevin Greene 3 years ago
@andyfierman Thanks, but I'm not smart enough to do this. There are loads of WEMOS D1 in the library, Surely someone has already created a model with the pins with the heads?
Reply
andyfierman 3 years ago
@kgreene1983, "Surely someone has already created a model with the pins with the heads?" No, because it is not possible to do this in EasyEDA (or any other EDA tool that I am aware of). This is because a Schematic Symbol and its associated PCB Footprint is assumed to be for a single component or device. The headers for modules like the WEMOS D1 or the Teensy and so on are made up of two separate single row pin header strips and not as a single double row socket like those for say 40 pin DIP devices. At the moment there is no way to make a Schematic Symbol that can call up two separate components in the BOM or indicate that the Footprint requires more than one physical component to be fitted to the board. The process I described in the documentation that I pointed you to deals with this problem. If you are having trouble following the procedure then the simplest option may be to just place the symbol for the WEMOS D1 on the schematic which will pull the associated footprint into the PCB. Then you manually edit the BOM to show that two single row headers must be bought as well as the WEMOS D1 module and that the headers must be fitted to the board and not the module itself.
Reply
Kevin Greene 3 years ago
Thanks.. I understand... I'll try the simple way
Reply
andyfierman 3 years ago
@kgreene1983, I have just added a feature request about this, which includes a third suggestion of how to solve this problem, by adding a second set of supplier information to the symbol. Adding notes in the schematic helps but is not foolproof. :) [https://easyeda.com/forum/topic/Annotate-symbol-to-show-that-the-footprint-requires-placement-of-more-than-one-physical-component-deae7486f93d46028e05313e7874e4c3](https://easyeda.com/forum/topic/Annotate-symbol-to-show-that-the-footprint-requires-placement-of-more-than-one-physical-component-deae7486f93d46028e05313e7874e4c3)
Reply
Login or Register to add a comment
goToTop
你现在访问的是EasyEDA海外版,建议访问速度更快的国内版 https://lceda.cn(需要重新注册)
如果需要转移工程请在个人中心 - 工程 - 工程高级设置 - 下载工程,下载后在https://lceda.cn/editor 打开保存即可。
有问题联系QQ 3001956291 不再提醒
svg-battery svg-battery-wifi svg-books svg-more svg-paste svg-pencil svg-plant svg-ruler svg-share svg-user svg-logo-cn svg-double-arrow -mockplus- -mockplus- -mockplus- -mockplus- -mockplus- -mockplus- -mockplus- -mockplus-@1x -mockplus-

Cookie Notice

Our website uses essential cookies to help us ensure that it is working as expected, and uses optional analytics cookies to offer you a better browsing experience. To find out more, read our Cookie Notice