Changing Footprint

Are you able to attach the project such that I can test it locally?

One possible problem could be that your netlist was not generated or generated under a different name than you expect. This could mean that you try to import an outdated netlist. To avoid this use the update pcb from schematic tool (found in the tool menu and in the top toolbar) as this does not rely on external intermediate files. (the netlist import is not really meant to get a design from eeschema to pcb new but to import from some external tool.)

---

Another source for an error could be that you have the same reference defined multiple times. Run ERC to make sure this is not the case.

Thank you.

By using the "Tools" route from the schematic I have had success.

I had been using the "envelope" NET icons on the top tool bars in both the schematic and PCB NEW. May I point out that these icons seem to be the recommended route in the document "Getting started in KICAD".

Regards

Peter

________________________________
From: <email address hidden> <email address hidden> on behalf of Rene Poeschl <email address hidden>
Sent: 03 October 2019 14:21
To: <email address hidden> <email address hidden>
Subject: [Bug 1846488] Re: Changing Footprint

One possible problem could be that your netlist was not generated or
generated under a different name than you expect. This could mean that
you try to import an outdated netlist. To avoid this use the update pcb
from schematic tool (found in the tool menu and in the top toolbar) as
this does not rely on external intermediate files. (the netlist import
is not really meant to get a design from eeschema to pcb new but to
import from some external tool.)

---

Another source for an error could be that you have the same reference
defined multiple times. Run ERC to make sure this is not the case.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1846488

Title:
  Changing Footprint

Status in KiCad:
  New

Bug description:
  Created design schematic. Moved between schematic and PCB NEW several
  times. Eventually got message that the .NET file could not be used as
  two ICs had footprints could not be used as pins were missing. On
  checking the schematic I found that the two ICs had SOIC 16
  footprints declared (as I expected), however PCBNEW considered that
  SOIC14 had been declared for both.

  In the schematic I re-selected SOIC16 for both. No success. Also I
  deleted the .NET file then re-created it. No success.

  Other ICs were in the schematic but were not affected.

  Previously a schematic with a collection of 14, 16 and 18 pin SOIC
  ICs had all changing to 8 pin SOIC after schematic editing.

  Am I doing something wrong, or is there a fault?

  Peter

  Application: KiCad
  Version: (5.1.4)-1, release build
  Libraries:
      wxWidgets 3.0.4
      libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
  Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.68.0
      OpenCASCADE Community Edition: 6.9.1
      Curl: 7.61.1
      Compiler: GCC 8.2.0 with C++ ABI 1013

  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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_USE_OCC=OFF
      KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1846488/+subscriptions

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2565