New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SKiDL BUG] generate_pcb() #127
Comments
I'm wanting to try to keep the PCB design process in Python. I saw this exchange and thought generate_pcb() might be a way to create a pcbnew board object by running pcbnew.LoadBoard() on the .kicad_pcb. Is this sound, or is there another way I should be doing this? |
The I would be interested in hearing more about your efforts to do a Python-only PCB design. Maybe the forum is a better place for that. |
Hmm, fp_libs (loaded from LibURIs()) seems to be an empty dictionary....I added a print to verify at line 135, right before the backtrace occurs. Could I be missing a package or something I wonder? Yes, I'm already modelling a custom keyboard in just Python using cadquery and would like to extend that to the PCB design rather than learning a GUI, if possible. I'm a little surprised it's not a common workflow yet, maybe in the not-so-distant future? I'm wanting to create a little single-switch PCB I can use many of, like this one - in fact, I'm trying to open that amoeba's .kicad_pcb file and just edit the dimensions to fit my 3d model. |
If I add
generate_pcb()
to the end of the SKIDL example to try to something I can feed into the pcbnew module, I get the following. Seems to be kinet2pcb....is fp_libs supposed to contain the full names of the Part footprints?The text was updated successfully, but these errors were encountered: