Suggestion: "Bend Cost" to aid in autorouting for single sided fabrication.

[sleemanj]

When routing a board for single-sided fabrication, especially DIY boards it is useful to have what will in reality be the non-copper side only have purely straight line routes which are implemented during fabrication by a simple straight solid wire, or for short ones by an SMD 0-ohm link on the copper side.

It is almost possible to do it already in Freerouting by setting the cost for "against preferred direction" on layer 2 to a very very high number (10000.0) and then it will make basically all routes on layer 2 straight and in the preferred direction. However that will mean that layer 2 ONLY has all auto routes vertical, or all auto routes horizontal. Ideally it should allow to have both horizontal and vertical auto routes on that layer, as long as each route individually is a straight line.

I propose the idea that would I think be able to accomplish this and more is to add a "bend cost" parameter for the "Trace costs on layer" autoroute parameters, such that if a route bends that increases the cost.

[github-actions]

This issue is stale because it has been inactive for 60 days. Remove stale label or comment or this will be closed in 7 days.

[sleemanj]

Comment.

[github-actions]

This issue is stale because it has been inactive for 60 days. Remove stale label or comment or this will be closed in 7 days.

[sleemanj]

Comment ---- On Tue,05 Dec 2023 14:45:43 +1300 ***@***.*** wrote ---- This issue is stale because it has been inactive for 60 days. Remove stale label or comment or this will be closed in 7 days. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[github-actions]

Hey there!👋 This issue is stale because it has been inactive for 60 days. If this matter is still relevant, feel free to remove the stale label or add a comment. Otherwise, it will be closed in 7 days. But remember, with thousands of monthly active users, someone might just have the solution you need. This is a community-driven project, and your active participation is crucial. If the issue is critical for your work, consider contributing a fix yourself or hiring someone to help. I'm here to support your efforts and will review and merge pull requests as quickly as I can. Let's collaborate to keep improving our project! 🚀 Your involvement is invaluable, and together, we can ensure the continuous growth and success of our community. Thank you for being an integral part of this journey. Your engagement is what drives our project forward!

[sleemanj]

comment

[andrasfuchs]

@sleemanj Thanks for the suggestion. Is it similar to issue #278?

If not, could you explain it the difference through an example?

Thank you!

[sleemanj]

In general my idea is simply "changing direction could have a configurable cost".It sounds like the other ticket is the more or less the same but is making the trace after the direction change more expensive rather than the direction change itself.  I imagine either approach would probably have the same effect.Message ID: ***@***.***>

[github-actions]

Hey there!👋 This issue is stale because it has been inactive for 60 days. If this matter is still relevant, feel free to remove the stale label or add a comment. Otherwise, it will be closed in 7 days. But remember, with thousands of monthly active users, someone might just have the solution you need. This is a community-driven project, and your active participation is crucial. If the issue is critical for your work, consider contributing a fix yourself or hiring someone to help. I'm here to support your efforts and will review and merge pull requests as quickly as I can. Let's collaborate to keep improving our project! 🚀 Your involvement is invaluable, and together, we can ensure the continuous growth and success of our community. Thank you for being an integral part of this journey. Your engagement is what drives our project forward!

[sleemanj]

comment