search

fritzing / fritzing-app

Fritzing desktop application
http://fritzing.org
Other
3.97k stars 826 forks source link

Fritzing is generating double routes between some parts in PCB View #2944

Open davidperrenoud opened 10 years ago

davidperrenoud commented 10 years ago

From fernaand...@gmail.com on April 18, 2014 02:12:03

What steps will reproduce the problem? 1.in schematic view place 3 resistor and 1 generic female header 4 pines 2.connect ping 1 from each resistor to the 2-4 pines in the header 3.connect the other resistor pines (number 2 of each resistor) together in the pin 1 of the header What is the expected output? What do you see instead? Fritzing creates double routes when it makes the autoroute task What version of Fritzing are you using? On what operating system? Version 0.8.7 (b1bf5 2014-01-24) Cocoa [Qt 4.8.5] Please provide any additional information below. This is only an example about how to place the parts, the original file is an array pf leds with its own resitor of 220ohms and a connector to another PCB

Original issue: http://code.google.com/p/fritzing/issues/detail?id=2946

allam-a commented 9 years ago

I can reproduce this issue on Version 0.9.0 (bda4e 2014-06-11) 64 [Qt 5.2.1] using the example Arduino->Light->Display->Liquid Crystal Display 1) In the PCB view delete All traces 2) Select the PCB and change it to single sided 3) Autoroute Notice double routes between pin 3 of the LCD and middle pin of the potentiometer and also between arduino UNO pin1 and R2

failiz commented 3 years ago

Still reproducible in 0.9.4

failiz commented 3 years ago

Remove imported label

vanepp commented 2 years ago

Still reproducible in 0.9.9. See

https://forum.fritzing.org/t/on-my-first-project-routing-gives-double-traces/14920/

for an example case. I expect this is low priority, but is still present.

Peter

KjellMorgenstern commented 2 years ago

I tested the Arduino->Light->Display->Liquid Crystal Display example.

  1. Load the example

  2. Export to XML Netlist

  3. Check the xml for "wiper". It is only present in one net, with four connectors (two THT donuts on two sides)

  4. Now, convert the PCB to single sided

  5. Again, export the XML Netlist

  6. Check the new xml for "wiper". It is now present in two nets, each again with four connectors.

So, it seems the issue is that duplicate nets get created when changing to single sided PCB. The autorouter then correctly connects all connectors for each net.