Pcbnew: it is impossible to globally increase the size of tracks if they are close to parts while resizing tracks

Bug #1803298 reported by Gabriel Staples on 2018-11-14

This bug report will be marked for expiration in 13 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Undecided
Unassigned

Bug Description

Application: kicad
Version: 6.0.0-rc1-unknown-a5c892d~84~ubuntu14.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Platform: Linux 4.4.0-112-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.54.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.35.0
    Compiler: GCC 4.8.4 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

-------------------------------------

3 Bugs:

1. Lay out a bunch of tracks and parts, using a smaller track size than intended (ex: 0.25mm track clearance, 1mm forced track width, even though your Net Classes rules have 2mm track widtdh). Then, go to Edit --> Edit Track & Via Properties... --> choose the "Set to net class values" option, and click OK. You'll notice that some tracks properly increased in size, but ones that would have entered the keepout region around parts had their size increased did NOT increase in size. (BUG #1) As far as I'm concerned this is a bug.

2. Assuming you still need those skinny (1mm wide) tracks to increase to their correct size of 2mm in this case, you can force it by right-clicking individual tracks one at a time, then pressing the 'e' key to Edit their properties. Check the box for "use net class widths", and click OK. They will increase to their proper size, BUT (BUG #2) NOW THEY ARE OVERLAPPING THE KEEPOUT AREA AROUND PARTS, AND YOU CANNOT USE THE 'D' key (Drag option) to drag the track away! It's as though the track is "stuck" inside the part now! Instead you have to manually delete the track and re-draw it.

3. (BUG #3): Furthermore, if you decide to just redraw over top of the old (too skinny) tracks, with the new, correct track size, in hopes that the old ones will be auto-deleted since you have your interactive router settings set to "Remove redundant tracks", you are out of luck. This feature doesn't work either.

In summary, the above 3 problems make it really hard to "fix up" a board where you mistakenly routed a tight board with the traces a bit too small. You can't resize easily, you can't drag resized traces, and you can't re-draw over top of them. The only thing left to do is just start mass deleting traces everywhere and start over from scratch. Unfortunately, this results in hours of wasted time.

As always, thanks to the devs for hearing my concerns and doing their best to fix them!

description: updated
summary: Pcbnew: it is impossible to globally increase the size of tracks if they
- are close to parts while resizing
+ are close to parts while resizing tracks
Nick Østergaard (nickoe) wrote :

Did you try to disable DRC before doing so?

tags: added: pcbnew
Gabriel Staples (ercaguy) wrote :

I think you mean "Allow DRC violations". See attached image. These are my settings for Route --> Interactive Router Settings...

Even with allowing DRC violations, globally increasing the track size still fails for any track that would be touching a part with its increased size. (Edit --> Edit Track and Via Properties --> "Set to net class values..." --> OK)

I can right-click the track segment and go to Properties (or press E key) --> "Use net class widths" --> OK, and it will forcefully increase the size, as previously described above, but now I can not drag the track.

So...*no change*. The same buggy behavior still exists as before.

Gabriel Staples (ercaguy) wrote :

Note that this bug may be related to this one as well (same project & file): https://bugs.launchpad.net/kicad/+bug/1803485

@Gabriel, do you still have these issues with 5.1? I am confused by your use of the term "keep out" when referring to footprints, as we don't currently allow keep out zones in footprints, see lp:1081846 [1].

Also, please open one bug report per bug, this is required for triaging, bug fix and ease of documentation.

[1] https://bugs.launchpad.net/kicad/+bug/1081846

Changed in kicad:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers