I’ve tried to place my plugins both in the folder:
“C:\Users\username\AppData\Roaming\kicad\scripting\plugins”
and in the folder:
“C:\Users\username\AppData\Roaming\kicad\scripting”
but my “Tools->External plugins” command still does not work (cannot see any plugin listed).
I guess there’s something else missing in my framework…maybe Python packages??
Exactly which plugin are you are trying to install? There are several types of “plugin”, only “Action plugins” are supported on Tools->External Plugins.
By exactly, I mean the name of the script file. There are many files there, I am not going to test all of them.
In the video, there is about one frame showing how to run the script https://youtu.be/av5HwAFl2VI?t=344. I’m not sure why that is quickly skipped over when everything else is explained in excruciating detail.
Anyway, to run the script you need to open the Python console in pcbnew, then type execfile('/path/to/file.py') in the command window. Since you haven’t said which script I can’t be more specific.
Sorry, Bobc.
The exact topic I was going to follow, is this one (that completes the previous one):
In the enclosed video, it is clearly shown that the author uses the function “Tools->External Plugins” for running his scripts (the ones of the GitHub repository “dxf_stuff”).
Certainly some of them are Action plugins, but not all of them.
So final time, which script do want to run?
If you say “all of them”, you will have to learn some scripting and go through each one and figure it out yourself, since the publisher did not provide much in the way of installation instructions.
From what I’ve seen mmccoo’s plugin require additional modules. And as you’ve already figured this out:
you can’t install this packages in python that is packaged with KiCad
you can’t really use pcbnew module with python3
What you might try is install python2.7 and import pcbnew module to this python. Look up on google how to import modules from absolute path. I had some luck with this kind of setup a year ago, but now I am just using KiCad’s python only as it is way more portable.
Thank you all for your answers,
My trouble was thinking that dealing with KiCad 5.0 and the use of scripting was available to anybody…but it is not so.
I guess that not-skilled users should not try to use this kind of devices, and keep using KiCad 4. You have to be able to deal with Python and scripting for managing these powerful tools…otherwise, it’s better to keep using “easy” tools.
Now I’ll try to move to Eagle, for checking if it more suitable for my needs (circular layout).
Scripting always requires background knowledge. In every tool.
In your other thread i pointed you to an explanation how your requirements can be done using the kicad internal array tools. By your answer i guess you never read that.
Regarding scripting: KiCad does not support all scripting tools on all platforms.
You also did not answer some question from the guys trying to help you. (Is it really that hard to clarify which exact script you try to run?) So i would guess you already made up your mind that the golden eagle is better for you and just wanted conformation.
Ok, you are right.
The problem is that, as shown in the picture I uploaded, the author uses several functions for modifying his schematic. Now, if I look at the folder “dxf_stuff” he has uploaded, it contains several plugins, whose names are completely different from the functions he uses in his video; for example:
dxf_plugins.py
dxf_to_graphic.py
dxf_utils.py
So, how can I know exactly which plugin I need for the functions used in the video? Essentially, all the functions listed in my image where used by the author for his work, but I do not know where these functions have been placed in terms of plugins.
Thank you.
If you are that focused on using exactly the workflow shown in the video, maybe try to comment on the video and contact the author that way?
We do not really know more about that particular video than you do. (Form the title i would assume this is not a tutorial but just a showcase of all his plugins. The author also mentioned that they intent to create a more detailed post later on. Maybe you can find that.)
That’s exactly what I did…but I had no answer.
Anyway, watching tutorials like the one I quoted could suggest the idea that using scripts is just a “pick, place, and use” stuff…while it is not so simple, and I think this the important information that the not-skilled user (like me) should keep in mind.
I’ll try to go back and read the other thread you suggested me about “kicad internal array tools”…maybe they could be enough for my needs.
Thank you very much for all your help and suggestions.
Bye
I got it to work in Kicad 5.0.2 on Windows 10 by putting the files in
C:\Users[your user]\AppData\Roaming\kicad\scripting
so the files are in C:\Users[your user]\AppData\Roaming\kicad\scripting\kicad_mmccoo-master
I also tried C:\Users[your user]\AppData\Roaming\kicad\scripts and after doing both the plugins still work after deleting the folders so I think the files are cached somewhere. Some sort of log of files it is accessing would be helpful, or a button to add scripts like in the other places scripts are used now.
Thank you, Ed2!
Currently I am not still working on PCB layouting, but in future I’ll come back to this job, and try to test your hints for managing scripts.
Best regards.
I never did 3rd party tool addition in KiCAD before, Please let me know the steps/procedure to add the below external plugin | 3rd party tool in PCBNEW, KiCAD.
I have gone through web, but could not find resources with clear explanation.
Are you sure this is a plugin and not an alternative fork of kicad itself? I remember the name of the dev. Was that the guy who tried to add teardrop support to kicad?
Edit: yes it is. Man that git history is well lets say not ideal. No wonder the devs rejected the original patches. Well that and the fact that it only works on the legacy canvas as far as i remember.
This means if you want to use this stuff you will need to compile that version of kicad. I noticed that there are absolute paths in the makefiles of that branch. (Introduced for example by the commit simply titled “a”.) This basically means you can only compile it if your setup exactly matches the setup of that particular developer.
It’s a fork and not a plugin. You can compile the whole repo yourself, but the files written by that fork of KiCad will be likely incompatible with the official KiCad.
If you’re looking for teardrops, they will likely happen during the V6 development (see spec here )
I’m afraid using forks made by Heikki or Ben Kempke is currently the only way to achieve rounded corners. We plan to add this feature in the V6 development cycle.