kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #26566
Re: pcbnew - enable editing of associated net for tracks&vias
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
jp charras <jp.charras@xxxxxxxxxx>
-
Date:
Mon, 10 Oct 2016 15:27:36 +0200
-
In-reply-to:
<trinity-9b76fb79-7ccb-49d1-9293-5bc3bf196dec-1476104340171@3capp-gmx-bs59>
-
User-agent:
Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
Le 10/10/2016 à 14:59, "Torsten Hüter" a écrit :
> Hi Jean-Pierre,
>
> I have done several designs with KiCad and stitch vias. The simplest way for me is to create a
> module with a single through hole pad.
> I've even written a python script to automate the placement of these stitch vias (see the mailing
> list archive). That was never a big problem and works well with the stable KiCad version, no issues
> with zone filling or net calculations.
Yes, I tried it and it works.
>
> I'm guessing that Altium PCB using a special primitive for stitch vias as well.
> See http://techdocs.altium.com/display/ADOH/Via+Stitching
>
> Only blind vias or burried vias are not possible when using a single pad module; Altium uses the
> start and end layer as attribute for these purposes.
It could be worth to also use some attribute to group stitching vias in Kicad.
In fact, as I previously wrote, defining how "stitching vias" are managed is the first work to do.
(the more basic way is to use the time stamp to group vias, but this is a very basic management, but
at least it allows placing/removing a group of vias)
Blind vias or buried vias could be possible when using a single pad module, because pads have a
layer mask to define the copper layers where they live,.
However, pad dialog properties does not handle "buried pads", but most of pad functions should
support them.
>
> --
>
> So maybe having free pads with similar attributes - like Altium is using - is here an alternative
> solution. Also for mounting holes as well (currently you need to create a module for them).
>
> Thanks,
> Torsten
>
> When this entity is defined, netnames will be no more a problem.
>
> So: first, define what is this entity (The best choice is not trivial for me, and deserves to think
> about it), how vias are linked to (or owned by) this entity, how they are taken in account by DRC
> and zone filling algorithms, and only after see if net names issues still exist.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
Jean-Pierre CHARRAS
References