Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Board has many small unconnected traces under pads #283

Open
jsiddall opened this issue Mar 19, 2024 · 7 comments
Open

Board has many small unconnected traces under pads #283

jsiddall opened this issue Mar 19, 2024 · 7 comments
Assignees
Labels
Milestone

Comments

@jsiddall
Copy link

jsiddall commented Mar 19, 2024

Please provide as many details as you can

  • What version of freerouting are you using?

v1.9.0 2023-10-30

  • On what platform did you run it? Windows, Linux, MacOS? 32-bit or 64-bit?

Linux 64 bit

  • What EDA do you use? KiCad, KiCad with freerouting plugin, EAGLE, EasyEDA, other? What is its exact version?

KiCad 6.0.10

  • What types of files are you working with? Can you attach the project files (.pro, .kicad_pcb, etc) or the exported DSN file?

Exported DSN file, can attach if it would help

  • Did you use any command line arguments?

No

  • Can you post a screenshot of the problem?

Yes:
image

image

  • Can you include the latest, related log entries from the .log file?

Not sure it is relevant, but there were several messages on the console including:

2024-03-19 11:52:03.519 [Thread-153] WARN  FloatLine: Parameter is null
2024-03-19 11:52:12.137 [Thread-153] WARN  CalcFromSide: start corner was not found
2024-03-19 12:16:13.453 [Thread-153] WARN  RoutingBoard.insert_forced_trace_polyline: shove trace failed
  • Please list the detailed steps to reproduce the problem

Generate DSN in KiCad, autoroute, export SES, re-import into KiCad

  • What would you expect freerouting to do in this situation?

Generate the layout as it did but don't leave tracks with unconnected ends (flagged as DRC warnings)

  • Is fixing this issue critical for your work?

No, freerouting is great even with this inconvenience. Keep up the great work!

@andrasfuchs andrasfuchs self-assigned this Mar 19, 2024
@andrasfuchs andrasfuchs added this to To do in Freerouting Project Board via automation Mar 19, 2024
@andrasfuchs andrasfuchs added this to the 2.0 milestone Mar 19, 2024
@andrasfuchs
Copy link
Collaborator

Thanks @jsiddall for the report!

Could you attach the KiCad project files so that I can reproduce the whole workflow?

@jsiddall
Copy link
Author

jsiddall commented Mar 19, 2024

Update: having looked at these spurious tracks, they all seem to be on power and ground pads. This may be relevant since there were a small amount of power and ground traces done in KiCad before sending the DSN to freerouting

@jsiddall
Copy link
Author

Thanks @jsiddall for the report!

Could you attach the KiCad project files so that I can reproduce the whole workflow?

I would have to cleanup the project first. It has the traces added by freerouting but the folder also has a lot of other older versions in it. I can do that if it would help, though the DSN would be a lot easier.

Also, could I email the files to you directly? Would rather not post publicly.

@andrasfuchs
Copy link
Collaborator

We could start with the DSN if that's easier for you, I might be able to find the bug that way.

Please send it to info@freerouting.app. Would it be alright with you if I uploaded the DSN into this repo for testing purposes just like the others?

Thank you!

@jsiddall
Copy link
Author

I emailed the cleaned up KiCad project, DSN and SES files. Let me know if you need anything else.

Thanks!

Copy link

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!

@jsiddall
Copy link
Author

I see the bot is getting impatient! Any progress on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants