File > Fabrication Outputs > Footprint Position (.pos) File…
Each time, I need to edit the files POS , to change the column names to the standard of JLCPCB.
So:
Ref > Designator
PosX > Mid X
PosY > Mid Y
Rot > Rotation
Side > Layer
is there a way to setup PCBNew to get already the JLCPCB nomenclature, instead?
What I did, that, for me, was the simplest approach, was to use LibreOffice’s CalcSpreadsheet and made a Macro to do what I want…
Example below (see top Right Corner my_BOM Icon).
It was pretty simple to do - just took 15 minutes of working through how Libre/Macros work and how to setup the desired fields/etc… I just open the CSV file and click the button.
The POS export has option for CSV…
ADDED: Added screenshot of Panel, indicating Row1 Fields, you can change them to what you want …
Already a macro up there will ok, although I’m not able to program macros under Excel (I did just 2 or 3 times in my whole life for very small stuff copying and paste code )
I would like, to understand if this is something can be done in KiCAD directly.
If not: yes your macro is partial but effective solution
Incredible I was able to create the macro in Excel ok it’s not portable but at lest it works.
I hope that kiCAD Team will provide with something native
It’s not a perfect solution. But, I call several external App related items from a Plugin.
Example shows calling LibreCalc (from a Kicad Plugin at Top-Right). That opens LibeCalc and from there, can open desired CSV/other and do the rest of the needed stuff…
I recommend spending some effort on using KiBot. I use it with the dev docker container.
There is a sample configuration to export the position file, but you can actually automate exporting the gerber package, BOM and positioning file.
Once you get going with KiBot, you’ll appreciate many of the other tasks it automates and the power of selecting components through variants on all production and documentation outputs.
I don’t work with 5.12 I am using v6. It’s at RC1 stage and very stable and has considerable improvements. My BOM script will bridge me through to later this winter if/when KiBot adds v6 support.
That’s right. Although it’s not exactly my intention to install even PERL just for this purpose. I mean: this will be the only one reason for which I do use Perl. Not justified … Conversely, a script that’s running directly into KiCAD environment, will be better (in my case)