latuernichis there a trivial way to turn a pdf file with a table spanning multiple pages with 672 pin definitions into a kicad symbol, preferably grouped by banks also specified in the table?
xor/a@latuernich so, what you can do is get your pin definitions in a spreadsheet, edit, group... them there and then copy-paste it into the symbol editor pin table.
There are pdf tools helping you to extract tables from PDF, still a PITA.
cpresser
@cccpresser @latuernich very cool!
@xor @latuernich If you use the from-csv-generator, I am very interested in feedback. We haven't used it much our self.
Both functionality and Documentation.
@cccpresser Hi. Finally got around to transfer the PDF into a CSV (was bored in class) but the script doesn't seem to work. If I run it on my CSV file it sets all symbol properties and does nothing else. When running it on the TPS2054D-example.csv it at least generates the outline of the symbol but no pins either. Checked both with kicad-nightly built yesterday and by looking into the generated file.
I am on the master branch of kicad-library-utils.
@latuernich then we broke it during refactoring stuff. Sorry.
Will have a look later. And fix it if its trivial.
Will have a look later. And fix it if its trivial.
@latuernich
It work for me. Not sure what you did wrong (or different) :/
I called `python3 from_csv_generator.py TPS2054D-example.csv`, it creates a file without throwing any error messages.
k-l-u commit 4b58f77 (latest master)
When importing into KiCad 10 I get this dialog. You cannot open them in KiCad9, that will fail since we are in the middle of the migration.
@cccpresser Huh, interesting. I got the same error when trying it with KiCad 9 which is why I built KiCad nightly in the first place.
I don't get any errors either, but the file just doesn't contain any pins. I will play around a bit later, haven't set up a venv for it so I might have some wrong version of a library for example.
@cccpresser Alright, turns out I commented out the lines which are responsible for inserting the pins into the pin list. If I remember correctly I did that because I was on an old commit without realizing it and back then the pins had to be integers. So layer 8 as always.
But thanks for your help anyways.
@cccpresser no wait, pin numbers are still expected to be integers. i think i did that change after pulling the latest commit. will poke around to get it to work, as far as I can tell it is only used necessary for ranges.
@latuernich would you be so kind and open a bug report? Or send patches I'd you feel like it?
I don't have the spoons to work on it right now.
@cccpresser pull request created
@latuernich pong. Will look at it during eh23. At least that's the plan.