Np_thru_hole

Layout Footprints
1

In a footprint file, from ultralibrarian, which claims to be generated by pcbnew, one of the pads is identified as np_thru_hole.

 (pad """" np_thru_hole circle (at -0.991 0) (size 0.0508 0.0508) (drill 0.4572) (layers *.Cu *.Mask))

)

KiCAD6 complains that it has to be smd or thru_hole and fails to load the footprint.

How to I fix this? (Apart from sending missives to ultralibrarian).

Thank you

2

In a PCB file (not a footprint file!) in KiCad V8 it looks like:

		(pad "" np_thru_hole circle
			(at 0 0)
			(size 3.5 3.5)
			(drill 3.5)
			(layers "*.Cu" "*.Mask")
			(clearance 2.5)
			(uuid "3d23cb67-e9b4-40b6-b374-cef9cc4be791")
		)

I assume there is a version mismatch between what Ultralibrarian delivers, and the KiCad version you are using. A quick way to fix it for you is to create a footprint file with an NPTH in it, open it in a text editor, look at it’s syntax, and modify a copy of the Ultralibrarian file so the syntax matches.

Also, KiCad V6 is getting a bit old now. KiCad V8 has been released a few months ago, and updates are similarly priced to your original KiCad purchase.

3

@Paulvdh Thank you, actually I meant to mod that post, the error is that the file has four double quotes instead of 2 in the number field. Kicad was telling me it wants to see pad designator in position 11, that is where the third quote is. So the error message was a little confusing also. (The extra quotes get disappeared in the post.)

WIll kicad8 accept my kicad6 projects and parts directories?

4

About the double quotes:
I just ignored them. This forum software does some weird auto formatting, and I was not sure what is going on there. It also does not influence my answer: Just parrot the syntax from a working example.

Kicad can open older projects. With a V6 projects I do not expect any problems (Either with a project or a library). With older projects, it depends on the state of the project. (For example, people used to have a very nasty habit of deleting the [Project]-cache.lib file, while it is an essential part of a KiCad V5 project, and it’s needed to convert the project to V6 or newer). A KiCad V4 project depends on the availability of the original libraries the project was created with.

Starting from KiCad V6 all information of the project is defined in the project itself, and upgrading to newer KiCad versions should require very little effort.

5

I removed two quotes - it works fine now, and sent a note to ultralibrarian.

Fedora (that is, my installed version) is at 6.0.11 and stuck there.

Is there a unified repository for KiCad8, or a simple “one clicks adds all”, that works with the dnf/yum architecture?

Thank you

6

According to:

image

7

Do you have a very, very old fedora version?

For the currently supported versions (38-40 and rawhide) there is stable 8.0.1 (perhaps even 8.0.2 by now) and via copr you can get stable earlier as well as testing (that will become the next 8.0.x stable) and nightly development versions (8.99).

8

8.0.2 is available for fedora 38 and 39 via copr as can be seen here:
https://copr.fedorainfracloud.org/coprs/g/kicad/kicad-stable/build/7380775/

9

I think I prefer to push onto 40, which fedora says has Kicad8. But thank you.

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.