EAGLE 9.1.3 - Bug - routed trace gets lost after moving board

EAGLE 9.1.3 - Bug - routed trace gets lost after moving board

beckeLJCQU
Explorer Explorer
728 Views
4 Replies
Message 1 of 5

EAGLE 9.1.3 - Bug - routed trace gets lost after moving board

beckeLJCQU
Explorer
Explorer

We learned about a bug in the newest EAGLE version the hard way:

For manufacturing purposes we close the schematic and move&copy the board to create multiple boards on one carrier.

In this special example during the first move of all elements one trace gets lost (Group all elements by drawing a group-window around them, than click "move", than CTRL-click anywhere and move - Trace disappears). This behavior is recreatable in V 9.1.3 Premium and 9.1.2 Premium, in V7.7 this does NOT happen.

In the attached Screenshot you can see the affected trace, the example board file is also included.

Any comments?

Thanks,

Andreas

0 Likes
Accepted solutions (1)
729 Views
4 Replies
Replies (4)
Message 2 of 5

jorge_garcia
Autodesk
Autodesk
Hi @beckeLJCQU,

I can reproduce this, this is definitely a big problem. I'll bring this to our developers right now. Thank you for posting the board since it allowed me to reproduce the issue quickly.

Let me know if there's anything else I can do for you.

Best Regards,


Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes
Message 3 of 5

Pieter.Jan.Van.de.Maele
Autodesk
Autodesk

Just want to follow up. We were able to find the root cause of this issue and it will be fixed in the next release. 

Pieter-Jan Van de Maele
Senior Engineering Manager, Fusion Electronics
0 Likes
Message 4 of 5

beckeLJCQU
Explorer
Explorer
Accepted solution

Those are good news! Just out of curiosity and because my colleagues asked: Can you briefly explain the root cause?

thanks!

0 Likes
Message 5 of 5

Pieter.Jan.Van.de.Maele
Autodesk
Autodesk

Sure. The root cause was that the path to the via got optimized by the preserve angles algorithm as it took the shorter route towards the end skipping going back & forth to the via. Obviously it should never optimize connections to vias :).  

Pieter-Jan Van de Maele
Senior Engineering Manager, Fusion Electronics