![]() ![]() I combine D (diode) and DS (led) parts into one table, J (jack) and P (plug/socket) into another, and the occasional T (transformer) will get tucked into L (inductor). Easy-peasy.Īfter much farting around with the spreadsheet, I saved separate csv files for each table I wanted (Capacitors…) leaving the first line in the csv with the field names for db import. To view a datasheet I open the symbol properties and click the little icon. ![]() ![]() Besides using the db to select parts, I want to generate a custom Assembly-BOM, a Cost/Availability-BOM, and maybe a custom placement file that can optionally adjust rotation with TapeCorrection, and perhaps add Height. Most of these fields will get pulled into kicad (via. I will jam the Description field full of detail for the selection dialog. I like the idea someone suggested about adding a little box symbol so it is treated like a part and shows in the bom.ĭisplayed on the schematic will ONLY be Value and ExtValue (optional extra value info). Status is for filtering, such as ‘N’ to not-display (eg: an old part), ‘1’ for current favorite parts, simply null for more parts… So a database view for fav parts displays only the parts flagged with 1, a view for more parts can be everything but N, a view for all parts ignores Status.īuildLevel can be set to something like pcb2nd to flag an after-reflow operation like manually adding a lightpipe or plugging in a socketed module. It’s a simple pattern that I like, but you can use any unique number system that works for you, and the key can be integer or text afaik. I use 003-xxxxx for C=caps (third letter of alphabet), 004-xxxxx for D=diodes,Ġ18-xxxxx for R=resistors, 026-xxxxx for Z=modules. PartNumID is my company part number and will be the database unique key field. JlcpcbPN, JlcpcbMfgPN, JlcpcbQty, JlcpcbEach, LabStock, Note, Temp Vendor, VendorPN, VendorQty, VendorEach, VendorAvail,ĪltVendor, AltVendorPN, AltVendorQty, AltVendorEach, AltVendorAvail, Symbol, Footprint, TapeCorrection, Datasheet, Manufacturer, ManufacturerPN, PartNumID, Substitute, Status, BuildLevel, Description, Value, ExtValue, Package, Height, I rearraged/added to the spreadsheet to get all the columns (fields) I wanted: Up to date, and also pulling all the current datasheets. I started with my years-old master parts spreadsheet, updating/adding/deleting parts to get it I have been building the symbol/fp/3dmodel parts over the last year with v6, and now adding database (and also datasheets) with v7. …/kicad/gil-lib/database/… (gil-db.sqlite and gil-db-xxx.kicad_dbl files) …/kicad/gil-lib/3dsymbols/… (xxx.step files) …/kicad/gil-lib/gil-fp/… (xxx.kicad_mod files) …/kicad/gil-lib/symbols/gil-lib.kicad_sym ![]() My kicad library is comprised of five folders: pull part info together in a big-o spreadsheet.A great big thanks to (and any other devs involved) for adding this major feature. This post documents an adventure creating my first database, which is not likely the best way to do it, but fwiw here is my little case study. I got very excited finding that v7 will have database functionality, and took it as an opportunity to drag my small shop into a more automated workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |