Skip to content
This repository was archived by the owner on Oct 2, 2020. It is now read-only.

sub d footprints use pin number 0 for shield (or mounting) connection #1243

Open
poeschlr opened this issue Dec 30, 2018 · 9 comments
Open
Milestone

Comments

@poeschlr
Copy link
Collaborator

This should be fixed to SH or MP

@poeschlr
Copy link
Collaborator Author

The symbols specifically designed for sub-d connectors however also use pin number 0.
This means this can wait till the next major release.

@hildogjr
Copy link
Contributor

Just for clarification:
symbols are using SH pin, but footprint using 0 pin for shield.
screenshot from 2018-12-30 17-09-50

@poeschlr
Copy link
Collaborator Author

@hildogjr this is only true for the generic symbols. The specialized symbols for sub d connectors use 0. Meaning use these symbols and everything should be ok for now.

@poeschlr
Copy link
Collaborator Author

For reference the screenshot of the current db9 connector symbol
screenshot from 2018-12-30 20-17-17

@hildogjr
Copy link
Contributor

But I haven't a Connector_Specialized.lib at my library folder. I am having even an error "/usr/share/kicad/library/Connector_Specialized.lib not found."

My library version (automatically installed by Nightly version) is
201812270847+470a6976ubuntu16.04.1

@poeschlr
Copy link
Collaborator Author

poeschlr commented Dec 30, 2018

The library is called Connector (It holds every connector symbol that does not fit into Connector_Generic)

Is it possible that your local lib is from sometime before the v5 release? (a late nightly perhaps)

@poeschlr
Copy link
Collaborator Author

Updating kicad does not update your library tables. Meaning if you had nighlies before the v5 release then you will have a library table older than v5. (The lib was only declared stable after rc2 of version 5)

@hildogjr
Copy link
Contributor

hildogjr commented Jan 6, 2019

Thx
I replaced my definitions by
https://raw.githubusercontent.com/KiCad/kicad-symbols/master/sym-lib-table
and works fine.
(Yes, even with apt purge kicad* and deleting ~\.kicad\, this configuration was kept).

@tijuca
Copy link

tijuca commented Jan 10, 2019

Basically Offtopic ...

(Yes, even with apt purge kicad* and deleting ~\.kicad\, this configuration was kept).

This is the expected and wanted behavior of apt or respective tools. And if some package is touching anything directly in the users home folder while apt or dpkg is running this is a serious issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants