I think the main distinction here is as follows. It invented only to manage a hug amount of data. (Could then later be done with a separate script when eeschema offers a python api) If that script then outputs a copy able table view at the end then it would be possible to use the already existing copy paste feature of the symbol field editor to get the final part selections back to the schematic. This would again fall under the bom export scripts responsibility and would already be possible. ![]() (Assuming database represents your in house stock not everything that is available) The designer would select the part they want at this stage from the list of already known parts or would be able to add a new one to the database if there is no fitting part in it. ![]() what tolerance, …) in the schematic and the export stage would then query the database for parts that fulfill them. I could even imagine that the designer would define minimum viable part requirements (what voltage to i need. From that then either enter the info manually or use copy paste via the symbol field editor in kicad. One can easily imagine having the database search system open in a separate window and checking which part to use that way. I am just not sure that this must be possible from within kicad. (Use symbol fields as a way to finalize the house part number.) Ideally there would still be a way to query the database for available values. ![]() The other way round would right now require a huge library generated from the database.Ī way to reduce the number of symbols needed is the system i suggest above. After all a python tool could simply connect to a database instead of creating a csv file. The direction of KiCad to database should already be doable with the current bom scripting interface. We need a database connector here, a simple single user Sqlite database would meet many users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |