kicad-developers team mailing list archive

[Thiadmer Riemersma <thiadmer.riemersma@xxxxxxxxx>]

Hello Clemens,

Why not have one _database_ in between schematic and layout and
> manufacturing, assembly (and ERP and ...) and the tools just pick what they
> need?


I agree that this is the better option. But it is also an ambitious
project. For example, for machine assembly, the global database must also
hold feeder details (tape/tube/tray, step size, reel size), orientation in
the packaging, component height, best nozzle to use to pick it up, and
probably other parameters that I am forgetting right now.

On Tue, Feb 14, 2017 at 2:52 PM, Clemens Koller <cko@xxxxxxxxx> wrote:

> Hi, Thiadmer!
>
> On 2017-02-14 12:21, Thiadmer Riemersma wrote:
> > And as others have already observed: a BOM tools sits in the middle of
> workflow.
>
> I agree here!
>
> > The software to prepare our pick & place machine has a BOM editor.
> > Our ordering/inventory system has a BOM editor too.
> > So what I think is important is flexible export /and/ flexible import.
>
> ... but import/exporting data in between the tools is IMO still not the
> best solution I can imagine.
> I/Os are off course still necessary, but using a lot of spreadsheet glue
> the processes seem more error-prone and are harder to verify for
> correctness when data is kept and needs to be synced in different places.
>
> I wish/tend to centralize all my data in an (open / from different tools
> accessible) database storage as much as possible and keep only the relevant
> data in the different tools.
> This approach seems also the trend in advanced commercial tools, however
> they use their own proprietary databases for customer-lock-in and sell it
> as best way for performance.
>
> > So that changes made to the BOM can be imported into KiCad and
> back-annotated in the schematic.
>
> Why not have one _database_ in between schematic and layout and
> manufacturing, assembly (and ERP and ...) and the tools just pick what they
> need?
>
> Regards,
>
> Clemens
>
> >
> > On Tue, Feb 14, 2017 at 11:47 AM, Clemens Koller <cko@xxxxxxxxx <mailto:
> cko@xxxxxxxxx>> wrote:
> >
> >     Hello, Martin!
> >
> >     Your work looks very promising.
> >     I am running very similar stuff "manually" (by executing .sql
> scripts) around my commercial tool.
> >
> >     Is there an ODBC in between your frontend code and the Firebird
> database you use?
> >     I am asking because the data here sits in a MariaDB storage.
> >
> >     Regards,
> >
> >     Clemens
> >
> >     On 2017-02-14 08:55, Martin Schreiber wrote:
> >     > On Tuesday 14 February 2017 07:20:23 Oliver Walters wrote:
> >     >> Hi all,
> >     >>
> >     >> I have been working on a BOM exporter built into KiCad (in
> addition to the
> >     >> external BOM script functionality that already exists).
> >     >>
> >     >> It's not ready yet to be merged but I am showing the progress
> here to get
> >     >> any input and in case anyone else is working on a similar feature.
> >     >>
> >     > I am working on a standalone tool which extracts component field
> values from
> >     > schematics
> >     > and looks-up the component, footprints and BOM-values in a
> database:
> >     > http://mseide-msegui.sourceforge.net/pics/msekicadbom.png <
> http://mseide-msegui.sourceforge.net/pics/msekicadbom.png>
> >     > Component fields can be composed by macros:
> >     > http://mseide-msegui.sourceforge.net/pics/component.png <
> http://mseide-msegui.sourceforge.net/pics/component.png>
> >     > and be based on a component-kind-template:
> >     > http://mseide-msegui.sourceforge.net/pics/componentkind.png <
> http://mseide-msegui.sourceforge.net/pics/componentkind.png>
> >     >
> >     > MSEkicadBOM can be used to produce the various production and
> documentation
> >     > files:
> >     > http://mseide-msegui.sourceforge.net/pics/production.png <
> http://mseide-msegui.sourceforge.net/pics/production.png>
> >     > http://mseide-msegui.sourceforge.net/pics/docuset.png <
> http://mseide-msegui.sourceforge.net/pics/docuset.png>
> >     >
> >     > The code is here:
> >     > https://gitlab.com/mseide-msegui/mseuniverse/tree/
> master/tools/kicad/bom <https://gitlab.com/mseide-msegui/mseuniverse/tree/
> master/tools/kicad/bom>
> >     >
> >     > Martin
> >     >
> >     > _______________________________________________
> >     > 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>
> >
> >
> >
> >
> > _______________________________________________
> > 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
> >
>
> _______________________________________________
> 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
>