You need to use EasyEDA editor to create some projects before publishing
Autoroute - Prevent tracks merging
1202 5
DeeEmm 6 years ago
Hi. I am trying to run two small tracks from adjacent pins on a pin header to a device to help load share (rather than one large track - which fails auto routing) but when I run autoroute the two tracks merge at the pins and only one track is run to the device. Each pin has a unique net name, but they run to the common pin on the device (see below) ![net example.png](//image.easyeda.com/pullimage/3k0b97w1jiObKr9d4wnQF60FmYtsjkzUNPvt7fVw.png) Is there any way to force this behaviour when using auto-routing? or does anyone know of a workaround? I appreciate that I can route these manually and then lock them, but that is too labor intensive and is something I would like to avoid if possible. Thanks in advance. /DM
Comments
UserSupport 6 years ago
Hi You can route it manually , and then enable the "Skip routed net" at the auto router config dialog.
Reply
DeeEmm 6 years ago
as I have said, I appreciate that I can route these manually and then skip them, but that is too labor intensive and is something I would like to avoid if possible.
Reply
andyfierman 6 years ago
"...I appreciate that I can route these manually and then skip them, but that is too labor intensive and is something I would like to avoid if possible." At present your only option is to route them manually as advised by UserSupport. The fact that you have attached three different netflags is meaningless in terms of the netlist because electrically it is all the same net so, in the netlist it has only one name.
Reply
DeeEmm 6 years ago
Thanks Andy, so no workarounds then? I did try to update the schematic lib to add in a second joined contact with a different netflag but that resulted in the same behaviour.  As you have said it appears that it only looks to see what nets are electrically joined and then joins them at the most convenient location. Only way I can think to achieve something similar is to use / create a device or terminal adjacent to the destination and route to that instead
Reply
andyfierman 6 years ago
Hmmm. You got me thinking. Not tried this but it might work: 1. create - and save with a unique name - a pcb footprint for a 3 pin device that is just a little pad with 3 pins numbered 1, 2, and 3; 2. create and save with the same name, a schematic symbol for a 3 way connector (with all 3 pins connected together) numbered 1, 2, and 3 and assign the "package" attribute to be the name of the footprint you just created; 3. place the symbol in your schematic then update the pcb from the schematic to pull your footprint into the PCB. You should then be able to place the new footprint where you want and autoroute to each pin separately. * For more info on why adding the pad in the schermatic is a good plan please see (2), (4), (5) and (6) in: [https://easyeda\.com/andyfierman/Welcome\_to\_EasyEDA\-31e1288f882e49e582699b8eb7fe9b1f](https://easyeda.com/andyfierman/Welcome_to_EasyEDA-31e1288f882e49e582699b8eb7fe9b1f)
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