¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Problem editing schematic in an existing project ...

 

I have several projects that I created under Kicad v5.1.10 under Win 7 Pro x64.

I need to go back and change some stuff and while I can add new components and change net labels it will not let me place new wires - it draws the wire but it doesn't highlight pins or let me link a wire to them.

What have I done wrong ??

Regards,
Dave


Re: Upgrading from an old version of KICAD

 

For what it's worth, I went to SnapEDA and downloaded the LM555 symbol/footprint in V3 and V4 formats (they don't have V5 or V6 yet) using 5.99 and it worked fine.

On 2021-10-20 10:42 a.m., Charles Steinkuehler wrote:
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Albert
Marsh via groups.io
Sent: Wednesday, October 20, 2021 8:41 AM
To: [email protected]
Subject: Re: [kicad-users] Upgrading from an old version of KICAD

Thanks for the input Craig. I seem to recall a couple years ago that there was a
file format change for the modules and footprints. That was my main concern. I
also recall people mentioning scripts that could be run that would convert one
type to another. I do not relish the idea of redrawing all of the items we have in
our libraries. Luckily, a great number of the parts share the same footprint,
such as 0805, or soic-8.
I've been using nightly versions for production work and have a number of parts I have to use in older library formats (eg: anything downloaded from the 'net is generally still in the older format). The 5.99 version will open these parts, but you will not be able to edit them. You have several options, which is best will depend on how much interoperating you plan to do with the two different versions.

* Keep all libraries in the old format. The 5.99 builds will read these just fine, but you'll have to run 5.x to make any updates. This is the best option if you still need to support earlier versions for a while.

* Write old-version components you need to edit to a new format library. This is what I do since I'm mostly grabbing footprints from online. I am only working with 5.99, so I save the old version part in the new format where I can make any tweaks or changes desired, and I don't care about updating the original source.

* Convert everything to the new formats. You'll probably want to do this eventually, but probably not as a first step!

--
Charles Steinkuehler
cstein@...





Re: Upgrading from an old version of KICAD

 

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Albert
Marsh via groups.io
Sent: Wednesday, October 20, 2021 8:41 AM
To: [email protected]
Subject: Re: [kicad-users] Upgrading from an old version of KICAD

Thanks for the input Craig. I seem to recall a couple years ago that there was a
file format change for the modules and footprints. That was my main concern. I
also recall people mentioning scripts that could be run that would convert one
type to another. I do not relish the idea of redrawing all of the items we have in
our libraries. Luckily, a great number of the parts share the same footprint,
such as 0805, or soic-8.
I've been using nightly versions for production work and have a number of parts I have to use in older library formats (eg: anything downloaded from the 'net is generally still in the older format). The 5.99 version will open these parts, but you will not be able to edit them. You have several options, which is best will depend on how much interoperating you plan to do with the two different versions.

* Keep all libraries in the old format. The 5.99 builds will read these just fine, but you'll have to run 5.x to make any updates. This is the best option if you still need to support earlier versions for a while.

* Write old-version components you need to edit to a new format library. This is what I do since I'm mostly grabbing footprints from online. I am only working with 5.99, so I save the old version part in the new format where I can make any tweaks or changes desired, and I don't care about updating the original source.

* Convert everything to the new formats. You'll probably want to do this eventually, but probably not as a first step!

--
Charles Steinkuehler
cstein@...


Re: Upgrading from an old version of KICAD

 

Thanks for the input Craig. I seem to recall a couple years ago that there was a file format change for the modules and footprints. That was my main concern. I also recall people mentioning scripts that could be run that would convert one type to another. I do not relish the idea of redrawing all of the items we have in our libraries. Luckily, a great number of the parts share the same footprint, such as 0805, or soic-8.

I also was thinking along the same lines as you in regards to an isolated install. I planned on copying our current libraries over to a non-networked laptop and trying it from there.

Thanks again.

-Albert


Re: Upgrading from an old version of KICAD

 

Hey Albert,

I am not certain but fairly sure that it will likely take no work from your end. I did a similar, although less drastic, migration when 5 was released and if I recall correctly there was a tool that popped up on start up that just converted everything completely hands off.?

I am not sure of you VCS solution or just the size of the libraries, but could you isolate a version and just try? Then if all goes well you can attempt it for real??

On a side note, you may want to protect you time and wait until 6 is released since it has breaking file changes. Once you go, you can't come back. Plus there are all sorts of nice fancy new features!

Craig

On Tue, 19 Oct 2021, 18:11 Albert Marsh, <hitekgearhead@...> wrote:
Good morning all,
At work, we have used an old version (2012-01-19 BZR 3256) for a number of years. We have created many libraries and footprints of our own. These libraries and footprints coincide with our company policies, stock management system, and the PCB vendors that we typically use.
We also have some machines on Win7 and some on Win10

I am interested in upgrading to the newest version and am interested in learning about the growing pains that we will encounter when doing so.

I have been following along with this group for years, so I am aware that the formatting of the libraries and footprints has changed, so I know I will have a lot of work in that area, but I am not much of a coder or "software guy" so building, compiling, and editing files by hand will be challenging.

So, what guidance do you all have?

Thanks,
Albert


Upgrading from an old version of KICAD

 

Good morning all,
At work, we have used an old version (2012-01-19 BZR 3256) for a number of years. We have created many libraries and footprints of our own. These libraries and footprints coincide with our company policies, stock management system, and the PCB vendors that we typically use.
We also have some machines on Win7 and some on Win10

I am interested in upgrading to the newest version and am interested in learning about the growing pains that we will encounter when doing so.

I have been following along with this group for years, so I am aware that the formatting of the libraries and footprints has changed, so I know I will have a lot of work in that area, but I am not much of a coder or "software guy" so building, compiling, and editing files by hand will be challenging.

So, what guidance do you all have?

Thanks,
Albert


Re: Nightly build for 5.1.10-1 that still supports Win7 ???

 

If you just don't like to move to Win10, then I can recommend moving to
Linux instead (Ubuntu, SuSE, Debian, Mate, RedHat, ... chose any one) -
it is a bit difficult at first to get used to a new OS, but it'll grow
on you... ;-)
TL;DR - I agree with Konrad.

I have an elderly, low spec (Medion) Windows 7 system. As far as
windows is concerned, it's take it or leave it, and "take" means filling
the entire disk with four partitions. Running Win 7 was (and still is)
monumentally slow, so as a work machine it was quickly retired (and
replaced with a Win 10 PC). But just for kicks, I installed Ubuntu 16
LTS on to a 64GB USB drive plugged into the one and only USB 3 socket.
The Ubuntu installer set up dual booting for me, and mounting the NTFS
hard disk. And what a transformation it was. The machine now runs at
a reasonable speed.

Ubuntu upgraded itself to Ubuntu 20 over the years, and Ubuntu sees by
far and away the most use on that PC, but when I need Win 7 for
something, it's still there. Since all user files go on the NTFS hard
disk, they remain available to me when using Win 7. But I hardly ever
do that, because it's like wading through mud.

After many years, the USB drive died a couple of weeks ago (it now has
as much in common with a USB drive as a grain of sand). Fortunately I
had imaged it with dd (comes with Linux, and very easy to use) before
upgrading to Ubuntu 18, so I just bought a new drive (which cost very
little) and transferred the image across. I'm back on Ubuntu 16, but
that will sort itself out in due course, and I have my favourite Kicad
work environment back.

I also have an ex Win 7 laptop that a friend abandoned because it was
too slow (I traded a bottle of whisky for it). I'm using it right now,
running Ubuntu 20 directly off the original hard disk. It occasionally
bogs down, but mostly it's perfectly usable. Battery aside, It's
lasted way longer than the bottle of Scotch :).

So I second Konrad's comment.

Regards,

Robert.


Re: Nightly build for 5.1.10-1 that still supports Win7 ???

 

Hi,


On 16/10/2021 21:50, David Slipper wrote:

Is there such a beast ???

I have partly fixed the run autorouter script but have run into a problem :-

??? Missing required python API:
??? ??? ??? pcbnew.ExportSpecctraDSN
??? ??? ??? pcbnew.ImportSpecctraSES

It is supposed to be resolved in a nightly build of 5.1.10-1 but all the Win7 nightly's I have tried say they only work on Win8+

Can someone give me a clue where I might find one ??

Moving to Win10 at this time is not possible.
Sorry for not answering your actual question in the affirmative, but: you are aware that support for Windows 7 ended in January LAST year. Right?

Unless you work in a completely isolated environment with some magic unicorns that keep your installation safe, your system is very open to vulnerabilities and other nightmares.

If you just don't like to move to Win10, then I can recommend moving to Linux instead (Ubuntu, SuSE, Debian, Mate, RedHat, ... chose any one) - it is a bit difficult at first to get used to a new OS, but it'll grow on you... ;-)

If some external circumstances force you to use Win7, then I am sorry to inform you that you appear to be affixed by an inclined plane wrapped helically around an axis.

You may be able to compile KiCad nightly yourself, if you are willing to create its rather complex development environment for yourself. But is it worth it?



??? Konrad


Nightly build for 5.1.10-1 that still supports Win7 ???

 

Is there such a beast ???

I have partly fixed the run autorouter script but have run into a problem :-

??? Missing required python API:
??? ??? ??? pcbnew.ExportSpecctraDSN
??? ??? ??? pcbnew.ImportSpecctraSES

It is supposed to be resolved in a nightly build of 5.1.10-1 but all the Win7 nightly's I have tried say they only work on Win8+

Can someone give me a clue where I might find one ??

Moving to Win10 at this time is not possible.

Dave


Re: A footprint for the part of a flex circuit that inserts into the connector?

 

You can also edit the footprint in a text editor to change (for example)
everything on the comments layer to the Edge Cuts layer. I've produced
lots of boards using that technique.

Regards,

Robert.

On 15/10/2021 21:40, Konrad Rosenbaum wrote:
In KiCad 5 you could use the drawings layer to put down the outline and
the Comments layer to explain that this should be aligned with the edge.


Re: A footprint for the part of a flex circuit that inserts into the connector?

 

Hi,

On 15/10/2021 18:25, Doug McKnight wrote:
I'm designing a system that requires a flex to insert into a connector (Molex 5014610491).? The layout of this part of the flex is precisely specified in the documentation and, if I am going to draw it carefully and use it again in the future, it seems natural to make it a "footprint".

However, it doesn't seem like a natural fit... For example, the edge cut layer is not available in the footprint editor.
In KiCad 6 (nightly) the Edge Cut layer is available.

In KiCad 5 you could use the drawings layer to put down the outline and the Comments layer to explain that this should be aligned with the edge.



??? Konrad


Re: A footprint for the part of a flex circuit that inserts into the connector?

 

Reuse generally is available by using 'templates' which may or not be suitable for what you want to do. I use them to capture complex board outlines and connectors with specific alignment that you need to re-use.

I don't know whether a footprint could be used to do something similar.


A footprint for the part of a flex circuit that inserts into the connector?

 

Hello,

I'm designing a system that requires a flex to insert into a connector (Molex 5014610491).? The layout of this part of the flex is precisely specified in the documentation and, if I am going to draw it carefully and use it again in the future, it seems natural to make it a "footprint".

However, it doesn't seem like a natural fit... For example, the edge cut layer is not available in the footprint editor.

How do people do this kind of thing?? Is there another way to draw and reuse a piece of layout?

Thanks
Doug


Re: Mark all pins "not connected" ??

 

The files are text based, so a simple script would set the pins to
whatever state you wanted easily.

SED would do, but it should be doable with a standard code editor and
some sneaky find and replace.

(or go tp perl, python or whatever your fav language is!)

Andy



On Thu, 14 Oct 2021 05:45:14 -0500
"Dale" <rdalek1967@...> wrote:

Hi Dave,

I haven't tried this but could you select, left click and drag over the
pins, and then tell it to put no connect flags on all the pins?? It may
not work but should only take a minute to try it.? Remember to save
first, just in case it fails in a spectacular fashion.?

Dale

:-)? :-)?


David Slipper wrote:

Clever ;-)

Dave


On 14/10/2021 06:00, Craig Burden wrote:
If the pins follow the standard grid spacing you can place a single
no connect at the top of the symbol and use insert to populate the
pins below

On Thu, 14 Oct 2021, 06:44 David Slipper, <softfoot@...
<mailto:softfoot@...>> wrote:

Many thanks all - I hadn't thought of "cut and paste", Ill give
that a try.

I'll also place a feature request.

Dave


On 14/10/2021 03:49, Chris via groups.io <> wrote:
You could file this as a feature request on KiCad's Gitlab
(which you can reach through KiCad's 'Report a bug' feature).
Seems like a reasonable thing to ask for.





Re: Mark all pins "not connected" ??

 

Hi Dave,

I haven't tried this but could you select, left click and drag over the
pins, and then tell it to put no connect flags on all the pins?? It may
not work but should only take a minute to try it.? Remember to save
first, just in case it fails in a spectacular fashion.?

Dale

:-)? :-)?


David Slipper wrote:


Clever ;-)

Dave


On 14/10/2021 06:00, Craig Burden wrote:
If the pins follow the standard grid spacing you can place a single
no connect at the top of the symbol and use insert to populate the
pins below

On Thu, 14 Oct 2021, 06:44 David Slipper, <softfoot@...
<mailto:softfoot@...>> wrote:

Many thanks all - I hadn't thought of "cut and paste", Ill give
that a try.

I'll also place a feature request.

Dave


On 14/10/2021 03:49, Chris via groups.io <> wrote:
You could file this as a feature request on KiCad's Gitlab
(which you can reach through KiCad's 'Report a bug' feature).
Seems like a reasonable thing to ask for.


Re: Mark all pins "not connected" ??

 

¿ªÔÆÌåÓý

Clever ;-)

Dave


On 14/10/2021 06:00, Craig Burden wrote:

If the pins follow the standard grid spacing you can place a single no connect at the top of the symbol and use insert to populate the pins below

On Thu, 14 Oct 2021, 06:44 David Slipper, <softfoot@...> wrote:

Many thanks all - I hadn't thought of "cut and paste", Ill give that a try.

I'll also place a feature request.

Dave


On 14/10/2021 03:49, Chris via wrote:
You could file this as a feature request on KiCad's Gitlab (which you can reach through KiCad's 'Report a bug' feature). Seems like a reasonable thing to ask for.


Re: Mark all pins "not connected" ??

 

If the pins follow the standard grid spacing you can place a single no connect at the top of the symbol and use insert to populate the pins below


On Thu, 14 Oct 2021, 06:44 David Slipper, <softfoot@...> wrote:

Many thanks all - I hadn't thought of "cut and paste", Ill give that a try.

I'll also place a feature request.

Dave


On 14/10/2021 03:49, Chris via wrote:
You could file this as a feature request on KiCad's Gitlab (which you can reach through KiCad's 'Report a bug' feature). Seems like a reasonable thing to ask for.


Re: Mark all pins "not connected" ??

 

¿ªÔÆÌåÓý

Many thanks all - I hadn't thought of "cut and paste", Ill give that a try.

I'll also place a feature request.

Dave


On 14/10/2021 03:49, Chris via groups.io wrote:

You could file this as a feature request on KiCad's Gitlab (which you can reach through KiCad's 'Report a bug' feature). Seems like a reasonable thing to ask for.


Re: Mark all pins "not connected" ??

 

You could file this as a feature request on KiCad's Gitlab (which you can reach through KiCad's 'Report a bug' feature). Seems like a reasonable thing to ask for.


Re: Mark all pins "not connected" ??

 

Usually pins have a certain spacing. I just copy and paste the no connects.

On 2021-10-13 10:46 p.m., David Slipper wrote:

It is rather tedious marking 90 pins of a 100 pin package as "no connection" so I was wondering if there was a way to automatically mark them all as such in one action ??? Perhaps a plug-in ??

I tend to design a basic circuit first (MCU + crystal, psu, etc) and then add functionality in stages, periodically running the ERC.

There doesn't seem to be a way of suppressing the "no connection" warnings in the ERC, so I find it easier mark them all and then to remove "no connection" indicators as I add functionality.

Is there a way to do this ??

Regards,
Dave