pcbnew copper pours does not close

Bug #1823863 reported by Martin Thomas on 2019-04-09
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Undecided
Unassigned

Bug Description

I have a board with an inner copper pour. I marked it with the signal name (U_Half) but it did not contact with the vias.
I use the the following version:
***
Application: kicad
Version: (5.1.0-201-gd93008030), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 GnuTLS/3.5.8 zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.19.27-mt 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.62.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

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

I attached the board, the problem is the copper pour in Layer In1.Cu on Zone priority Level 1 within the big zone. I want it to be "/U_Half" which does not work.

With an older Version I didn't have this problem. The version without problems is:

***
Application: kicad
Version: (5.0.0-rc2-dev-107-g49486b83b), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

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_SPICE=ON
***

Martin Thomas (mtlaunchpad) wrote :
summary: - pcbnew copper pours do not close
+ pcbnew copper pours dos not close
summary: - pcbnew copper pours dos not close
+ pcbnew copper pours does not close
Martin Thomas (mtlaunchpad) wrote :

The commit "97063440bbf871a5aa8da9f8c5532199240f366e" was the last which had no problem with the filled zones.

Martin Thomas (mtlaunchpad) wrote :

By the way the STEP Export and 3D Viewer is also working better with the Version from 97063440b...

Seth Hillbrand (sethh) wrote :

I think that this is fixed by JP today in 37ae0bf809

Can you try tomorrow's nightly and see if it is better?

Wayne Stambaugh (stambaughw) wrote :

@Martin, none of the zones in the provided board are tied to net U_Half. I believe there was a bug that was recently fixed in the zone properties dialog that caused zone nets to be changed when changing the zone priority or something along those lines. Would you please try resetting the zone net and confirm the zone filling is broken or it was due to the net being changed?

Seth Hillbrand (sethh) on 2019-04-09
Changed in kicad:
status: New → Incomplete
Martin Thomas (mtlaunchpad) wrote :

I tested it with 37ae0bf809 yesterday and the problem was still there. Also the STEP Export does not work.

Seth Hillbrand (sethh) wrote :

@Jeff- Do you have time to look at this? It appears maybe to be related to the netname escaping.

Seth Hillbrand (sethh) wrote :
Changed in kicad:
milestone: none → 6.0.0-rc1
status: Incomplete → Fix Committed
Martin Thomas (mtlaunchpad) wrote :

Yes I tested it and the copper pour works fine now.
And I figured out than I can export a STEP file without any issues if I open the board with an older version of pcbnew (in my case Application: pcbnew Version: 5.0.0-rc2-dev-107-g49486b83b) and save it.
If I open this file with the most recent version I could export a step file. This works until I save it again with the current version.

Jeff Young (jeyjey) wrote :

@Martin, were you doing the STEP test in a recent nightly? That one was tracked under a different bug report, but I thought it was fixed too. (On the Kicad side, anyway. Maui is doing the work on the StepUp side, but I'm not sure what the timeline there is.)

https://forum.kicad.info/t/bad-layer-data-error-when-exporting-step/16322/3

Martin Thomas (mtlaunchpad) wrote :

I compiled the last version just and the STEP Export seams to be working here. Thank you.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers