I’m new to KiCad and am in a big crunch and need to get boards sent out today. I downloaded the Sierra Circuits Plugin to expedite the process since I don’t have time for a bunch of back and forth with vendors.
When running the plugin I get the following error:
TypeError: PAD.GetEffectivePolygon() missing 1 required positional argument: ‘aLayer’
I have visual studio and can potentially fix it, but don’t know what it’s asking for. Here’s a snippet of the code file including line 1210 in case it’s helpful:
Well you don’t say what version of KiCad you are using . . . so I am left making some assumptions.
If you are using V9.x.y it may well be that the Author of the Sierra Circuits Plugin hasn’t modified it for V9.x.y yet . . . obviously they will the best people to confirm/deny this, in any case as it not written by the KiCad team the author of that Plugin is the best source of help.
In v9 it requires the layer as an argument, as you can see in the error message. The reason is probably that in v9 you can have a custom padstack which means there can be different “effective polygon” in different layers.
You can fix this in two ways: simple, which can fail depending on the PTH pads in the design. Or complex and foolproof, with which I can’t help so much because I won’t dig into the code to learn what it actually does in the larger picture.
The simple way is to assume that the padstack is the old all-layers-are-the-same style. Then you can simply assume that whatever layer you choose, the result represents any layer. If your designs have only old style THT pads this may be enough for you.
poly = pad.GetEffectivePolygon(pcbnew.F_Cu)
Note that the plugin mines the board to get information for some checks – in this case minimum sizes used in the board. I’m not responsible if this “fix” fails so that the plugin works but gives wrong information for the manufacturer.
Thanks for letting us know the issue you are facing while using the Sierra Circuits Plugin with Kicad Version 9 and I am sorry for the inconvenience caused with you due to the issue.
It’s a Sierra Circuits Plugin version support issue, and we are working to resolve it ASAP.
Our Support Engineer will inform you once the issue is fixed.
Please let us know if you need any further assistance.
