kicad-developers team mailing list archive

[Greg Smith <ecomputerd@xxxxxxxxx>]

I also expect when porting to a new fab, modifying the stackup, then running DRC on the result without changing layout should be possible.
I would expect importing from DRU file would (optionally) overwrite stackup, DRC, Netclasses, and/or Via/Drill sizes. Saving to DRU file directly might be possible, but may not be "roundtrip accurate" in cases where KiCad is more flexible.
For more detail see my "Design Rules File load/save" thread here:
https://forum.kicad.info/t/design-rules-file-load-save/7044/21

I also have DRC and listings of drills/holes by standard drill sizes in KiPadCheck with selectable drill set. The intention is to also be able to import the drill set from a manufacturer file:
https://forum.kicad.info/t/kipadcheck-works-with-nightly-seeking-feedback/7294/26

Because the KiCad "manufacturer file" could include a lot more information than a DRU file, my thought was that there might be a new file format. Maybe call it "KMF" for KiCad Manufacturing File as a superset of what is included in a DRU file.

On Thursday, August 31, 2017, 1:02:09 PM CDT, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:

The project file is always an option.  This would prevent file format
issues and always be available as long as the project is open.  This
falls apart when the board is loaded outside of a project so that could
be an issue.

My preference is saving the stack up in the board file with an
import/export option.

On 8/31/2017 1:56 PM, José Ignacio wrote:
> I don't see why you couldn't have both, an embedded version of the
> actual setup and the ability to import/export from/to an external file.
> 
> On Thu, Aug 31, 2017 at 12:54 PM, Neal Hollingsworth
> <nealanthony@xxxxxxxxx <mailto:nealanthony@xxxxxxxxx>> wrote:
> 
>    Hi all,
>      I've mostly been lurking on the list, but thought I would make a
>    suggestion regarding the via stack configuration. It might be nice
>    to store the actual configuration/stack-up/DRC settings in an
>    external file. The idea is that these are processes paraders that
>    are deaigned to in most cases. This would make it possible have have
>    e.g. A configuration file for a specific board house and price
>    point. The board file would then only need to store a reference to
>    the configuration file. Just a thought, take it for whatever it's worth!
>           Neal Hollingsworth 
> 
>    On Thu, Aug 31, 2017 at 12:44 PM Wayne Stambaugh
>    <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>> wrote:
> 
>        On 8/31/2017 1:21 PM, Bastian Neumannn wrote:
>        > Hi,
>        >
>        > I am currently building a feature that lets you input a via stack
>        > configuration.
>        > This information needs to be saved with the pcb data. So I
>        tried putting
>        > it into
>        > the kicad_pcb file. 
>        >
>        > Now older versions will not load the file because it has
>        additional
>        > values that
>        > it did not expect.
>        >
>        > How do you deal with that problem?
> 
>        The official policy is that file format changes must be backwards
>        compatible not forwards compatible.  In other words, the user
>        will have
>        to download the version KiCad where the change was made.
> 
>        If you make any changes to any of the file formats, you must
>        increment
>        the file format rev number.  This will cause the appropriate
>        exception
>        to be raised which will warn the user the file version is newer
>        than the
>        file version supported by the version of KiCad they are using.
> 
>        Since this is all very new and has not been planned for the stable 5
>        release, I would most likely merge this into the master branch
>        after the
>        stable 5 branch is created.
> 
>        Cheers,
> 
>        Wayne
> 
>        >
>        > Cheers,
>        > Basti
>        >
>        >
>        > _______________________________________________
>        > Mailing list: https://launchpad.net/~kicad-developers
>        <https://launchpad.net/~kicad-developers>
>        > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>        <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>        > Unsubscribe : https://launchpad.net/~kicad-developers
>        <https://launchpad.net/~kicad-developers>
>        > More help   : https://help.launchpad.net/ListHelp
>        <https://help.launchpad.net/ListHelp>
>        >
> 
>        _______________________________________________
>        Mailing list: https://launchpad.net/~kicad-developers
>        <https://launchpad.net/~kicad-developers>
>        Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>        <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>        Unsubscribe : https://launchpad.net/~kicad-developers
>        <https://launchpad.net/~kicad-developers>
>        More help   : https://help.launchpad.net/ListHelp
>        <https://help.launchpad.net/ListHelp>
> 
>    -- 
>                                                               Neal
> 
>    _______________________________________________
>    Mailing list: https://launchpad.net/~kicad-developers
>    <https://launchpad.net/~kicad-developers>
>    Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>    <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>    Unsubscribe : https://launchpad.net/~kicad-developers
>    <https://launchpad.net/~kicad-developers>
>    More help   : https://help.launchpad.net/ListHelp
>    <https://help.launchpad.net/ListHelp>
> 
> 

_______________________________________________
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