search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

Autorute fault #2935

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.If you autorute the file "Tarjeta TEG sin rutear" some wires dissapear. I 
copy files before and after("Tarjeta TEG ruteada"), in the SMDs 20pins  some 
wires are missed after autorute.
2. I hope do not loose connectios when autorute.
3.fritzing.0.8.7b.pc

Attach your sketch file and/or custom part files to the bug report.

What is the expected output? What do you see instead?

What version of Fritzing are you using? On what operating system?

Please, let me know any way to go on, any advice will be great to finish, very 
close to do it.

Best regards,

Ramón Villanova.

Please provide any additional information below.

Original issue reported on code.google.com by ramon...@gmail.com on 18 Mar 2014 at 1:50

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by andre.knoerig@gmail.com on 22 Mar 2014 at 5:38

GoogleCodeExporter commented 9 years ago 
probably related to issue 2921

Original comment by andre.knoerig@gmail.com on 23 Apr 2014 at 2:50

GoogleCodeExporter commented 9 years ago

Original comment by andre.knoerig@gmail.com on 23 Apr 2014 at 2:52

GoogleCodeExporter commented 9 years ago 
It is not clear this is a duplicate of 2921--though it might be--so I am 
restoring its independent status.

This is a case in which wiring has been done in only pcb view. When then 
attempting to autoroute in pcb view, the autorouter is unable to complete at 
100 tries, so some of the connections must by definition be lost (since a 
success in this case would mean rerouting what is already there).

Some choices for this particular file are:
-- do the wiring in another view, so that you can see ratsnests if the 
autorouter doesn't complete
-- bump up the number of tries given to the autorouter, in the hope that it 
will succeed (note, it still doesn't do any better at 1000 tries)
-- undo after autorouting to return to the original state

In general, I would call this a UI issue: specifically in cases where all 
wiring was done in a given view, and then the autorouter doesn't complete in 
that view. I believe the user's intent is to use the autorouter to clean up the 
hand-routing, and frankly, our autorouter is not currently up to that task. 
Here are some suggestions:

-- When the autorouter gives up, put up a message to let the user know that 
connections have been lost, since it didn't complete (and there are no 
connections in the other views).

-- When the autorouter gives up, it should automatically return to the original 
state, saying that it failed to complete, and can't improve on the former 
state. 

-- The autorouter should just state at to begin with that it probably can't 
improve on what has already been hand-routed, and should bail out immediately 
without doing anything.

Original comment by irasc...@gmail.com on 7 May 2014 at 7:38

GoogleCodeExporter commented 9 years ago 
Issue has moved to new issue tracker at github. Please continue the discussion 
at https://github.com/fritzing/fritzing-app/issues

Original comment by andre.knoerig@gmail.com on 23 Sep 2014 at 3:44