High pincount schematic symbols

External Plugins
3

Oh, I didn’t know that!

Good idea. I’ll make the change.

4

It’s one of KiCad’s silliest “features”. It’s used to implement power ports, but also the ghastly hidden pins on ICs (like in the 7400 lib) that are implicitly connected…

5

I made the change, tested it (seems to work), updated the repo and bumped the version number on pypi. Thanks for the tip!

6

There have been issues in the past with things set to zero size not rendering properly in eeschema - but I use that so often that if there are any more issues with it, I’ll just fix them myself in eeschema…

7

If that becomes a problem, I can always bump the “invisible” pin number size up to 1 mil. That’s still a better solution than having to redo a board spin.

8

Or just report a bug on the tracker and I’ll pounce on it :wink:

9

Does Kipart need any specific version of the Python installed? I just tried it with Python 3.4 on Win7 64bit, install via pip went ok, but any call to kipart.exe results in this:

10

I developed it with Python 2.7.6. That print statement would have to be turned into a print function call for it to run on Python 3.

11

Thanks! Works fine with 2.7.6. Perhaps adding that info somewhere on the page would help to avoid confusion among less experienced users.

12

Considering that the function call syntax is equally valid in 2.7 as long as you’re not using the optional features (omitting EOL or printing to a different file), perhaps you should consider using that syntax. There are a lot of simple Python scripts that would be both 2- and 3-compatible if the developers would just put parens in their print statements.

–In fact, I tend to define something like this at the top of my scripts so I can use the rest of the features too

def Print(text, end='\n', file=sys.stdout):
    """Python 2+3-compatible Print"""
    file.write(text)
    file.write(end)
    file.flush()

As a companion to print, if you use it:

try:
    raw_input
except NameError:
    raw_input = input

Or, if you prefer to call it input:

try:
    raw_input
except NameError:
    pass
else:
    input = raw_input
13

I’m working on the port to Python 3. I’ve used ‘futurize’ to do the conversion. It’s mostly working, but there are a few issues that aren’t as simple as converting the print built-in to a function.

14

I got it ported over to Python 3 in case you want to dump Python 2.7 from your system.

15

Would it be possible to add support for pin coordinates in mils (e.g. “X” and “Y” columns in CSV)?

16

Sorry, I don’t understand what these pin coordinates would be for.

17

I’m talking about symbol pin coordinates as they defined in the KiCad symbol format. That would allow to define gaps between pin groups (for more complex symbols) in the CSV itself instead of rearranging pins in the symbol editor afterwards.

18

So you don’t really want (X,Y) coordinates. You want something like a “gap” pin that’s listed in the CSV file but doesn’t turn into an actual pin in the symbol and leaves a space instead. Possibly this could be specified by placing an asterisk in the pin number column.

19

That would do the trick too, thank!

20

OK, I added the ability to insert “gap” pins. Just insert a row with a pin number that is a ‘*’ (or starts with one) and that will create a non-existent pin that inserts a gap in the sequence of pins on the symbol.

This only works if you’re using KiPart with the -s row option. (Using the -s name or -s num options will sort the pins by their names or pin numbers and that makes it impossible to tell where the gap pins should be placed.)

If you’re building a multi-unit symbol or using multiple sides of the symbol, remember to also specify the unit and side for the gap pin.

1 Like
21

Many thanks, I’ll give it a try.

22

I have been fighting with multi part symbols.

i afetr some time managed to get outlines to be diffrent byt for the ref des text it always ends up same place in all symbols,

albeit the tutorials bring forward the 7400 example for multi symbols its for a professional designer not very interesting…
multi symbols are crucial for bigger chips and you should preferably be able to name the something clever and not a,b,c,d rather _power _input etc something to reflect the parts functionality.

kicad need IMHO a part concept where you can tie togheter arbitraryt symbols wit any footprint and make a part.
this is where you check that all pins are used and not over-used.

today you can go into layout and need to manually check that all symbols been correctly mapped.
huge source for hunan.errors.