kicad-developers team mailing list archive
Mailing list archive
Re: Dealing with addition to kicad_pcb files
Thoughts on the comments here?
I also expect when porting to a new fab, modifying the stackup, then running DRC onthe 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/26Because 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 formatissues and always be available as long as the project is open. Thisfalls apart when the board is loaded outside of a project so that couldbe an issue.My preference is saving the stack up in the board file with animport/export option.
On Thursday, August 31, 2017, 3:45:19 PM CDT, Bastian Neumannn <neumann.bastian@xxxxxxxxx> wrote:
Having the design rules imported from eagle via a python script is the way to go IMHO. I don't see the benefit of adapting to a proprietary file format.
Having a warning shown is a better way than not starting up at all.
I might have a look at it tomorrow.
Am 31.08.2017 10:18 nachm. schrieb "Tomasz Wlostowski" <tomasz.wlostowski@xxxxxxx>:
On 31.08.2017 19:59, Simon Küppers wrote:
> Does it make sense to maybe use something like the EAGLE DRU Format?
> Maybe make it fully compatible to it? Some fabs give you the EAGLE DRU File.
IMHO a warning on unrecognized token while parsing files is a must - in
many cases users run nightlies to benefit from the latest features, but
board manufacturers or companies run the stable release (due to IT
restrictions or just worries about stability). Current situation makes
this difficult (see complaints on the forum...)
As for the DRU format - I wouldn't standardize on anything proprietary.
Also Eagle's design rules are somewhat simpler than what we're aiming at
Mailing list: https://launchpad.net/~kicad- developers
Post to : kicad-developers@lists. launchpad.net
Unsubscribe : https://launchpad.net/~kicad- developers
More help : 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