How to fix DRC incomplete connection when using jumpers and headers to connect nets
117 4
Lorenzo Stanco 1 week ago
Hi. I'm designing a PCB which consists of **two boards separated with a v-cut**. They will be stacked on top of each other using a couple of header strips, that will also carry signals from one board to the other. This means that some nets exist on both boards, and they will be fully connected **only when the boards will be assembled**. Now I get DRC errors (incomplete connection) because in the PCB design these nets are not physically connected. How to fix that? Do I have to use two different net names also if the net is practically the same? I guess this is the exact same problem of connecting a net by soldering jumpers, how do you do that? Thanks.
Comments
andyfierman 1 week ago
EasyEDA does not currently support any way of splitting a net into more than a single route of continuous copper without generating an Incomplete Net warning. If you have a net on one part of a PCB that has the same name as a net on another part of the PCB but the two parts of the are not connected together by copper then you will get an Incomlete Net warning. As long as you understand the reason for that warning to occur and can be **absolutely** sure by manual inspection that the intended gap is the **only** cause of the warning, then you can ignore it. Otherwise you have no other choice but to give the nets different names. I would suggest adding an alphanumeric suffix. That is a much less error prone and therefore the recommended solution.
Reply
andyfierman 1 week ago
Note therefore that your schematic should show the separate nets and their associated header connections and so should be given differentiated net names anyway.
Reply
Lorenzo Stanco 1 week ago
@andyfierman Thanks very much for the reply. > As long as you understand the reason for that warning to occur and can be **absolutely** sure by manual inspection that the intended gap is the only cause of the warning, then you can ignore it. I am sure, but I think I will use different names anyway, so that I can continue to use the automatic checks reliably. If I start ignoring specific warnings, there will be the time where I'll miss the "legit" one. > Note therefore that your schematic should show the separate nets and their associated header connections This is very inconvenient, but not a problem right now: I'm currently using EadyEDA to draw to PCB directly, I'm not using for schematics yet.
Reply
andyfierman 1 week ago
This explains why we recommend always starting with a Schematic: [https://easyeda\.com/forum/topic/The\_best\_way\_to\_design\_a\_PCB\_in\_EasyEDA\-ThR3pwqIC](https://easyeda.com/forum/topic/The_best_way_to_design_a_PCB_in_EasyEDA-ThR3pwqIC)<br> <br> :)
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
We use cookies to offer you a better experience. Detailed information on the use of cookies on this website is provided in our Privacy Policy. By using this site, you consent to the use of our cookies.