Hi Prasad,
We are planning on implementing pad stacks during version 8 development.
We currently are not planning back drill support for the initial pad
stack implementation but it's certainly something we would like to
implement.
That being said, pad stacks will require massive internal changes to the
KiCad board code base. I doubt this will be something that a new
developer will be able to manage given the complexity of the KiCad code
base. Once pad stacks are implemented, adding back drill support to
them will be a more manageable task for a new developer. When pad stack
support gets implemented is difficult to say so we might have to wait a
bit longer to get back drill support into KiCad.
I'm sure there will be an announcement once pad stacks are in KiCad. We
can revisit the back drill support that that time. Thank you for your
interest in helping the KiCad project.
Cheers,
Wayne
On 1/12/23 10:10 PM, Prasad Bhat wrote:
> Dear developers at KiCad,
>
> I would like to work on implementing backdrill support in KiCad. In this
> regard, I have thought of 2 possible choices and I need your help in
> choosing what works best.
>
> *Option 1:*
> 1. Update via definition to include another sub-type called 'backdrill'
> 2. Have an additional field in the via definition to have backdrill
> diameter.
> 3. Use layer information to indicate what remains after backdrilling.
> 4. In drill generation, emit one PTH (through hole top to bottom), and
> either one or two backdrops based on layer information.
>
> A backdrill based via would look like following in the s-expression:
> (via
> backdrill
> [(locked)]
> (at X Y)
> (size DIAMETER)
> (drill DIAMETER)
> (backdrill DIAMETER)
> (layers LAYER1 LAYER2)
> [(remove_unused_layers)]
> [(keep_end_layers)]
> [(free)]
> (net NET_NUMBER)
> (tstamp UUID)
> )
>
> *Option 2:*
> Astrome Technologies Pvt Ltd (
www.astrome.co <
http://www.astrome.co>)
>
>
>
> CONFIDENTIALITY NOTICE:
> The contents of this email message and any attachments are intended
> solely for the addressee(s) and may contain confidential and/or
> privileged information and may be legally protected from disclosure. If
> you are not the intended recipient of this message or their agent, or if
> this message has been addressed to you in error, please immediately
> alert the sender by reply email and then delete this message and any
> attachments. If you are not the intended recipient, you are hereby
> notified that any use, dissemination, copying, or storage of this
> message or its attachments isstrictly prohibited.
>
> --
> You received this message because you are subscribed to the Google
> Groups "KiCad Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
devlist+u...@kicad.org
> <mailto:
devlist+u...@kicad.org>.
> To view this discussion on the web visit
>
https://groups.google.com/a/kicad.org/d/msgid/devlist/CAJVLBbevzQKCQgzx3%2BDq1mLsC8QgGRGks_Qc92c0Ukw2T%3DkPWA%40mail.gmail.com <
https://groups.google.com/a/kicad.org/d/msgid/devlist/CAJVLBbevzQKCQgzx3%2BDq1mLsC8QgGRGks_Qc92c0Ukw2T%3DkPWA%40mail.gmail.com?utm_medium=email&utm_source=footer>.