Yet another Python teardrop script. Adds and deletes teardrops to a PCB. V0.3.3

[Niluje]

Thanks a lot for your answer.

I will add a method in script to fix the saved file.

I am using :
Application: kicad
Version: 4.0.2+e4-6225~38~ubuntu14.04.1-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.8.4,wx containers,compatible with 2.8)
Platform: Linux 3.13.0-91-generic x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.54.0
_ USE_WX_GRAPHICS_CONTEXT=OFF_
_ USE_WX_OVERLAY=OFF_
_ KICAD_SCRIPTING=ON_
_ KICAD_SCRIPTING_MODULES=ON_
_ KICAD_SCRIPTING_WXPYTHON=ON_
_ USE_FP_LIB_TABLE=HARD_CODED_ON_
_ BUILD_GITHUB_PLUGIN=ON_

[maui]

you could also add a function to add teardrops only on selected vias (selection is available in GAL mode)

.IsSelected()

ps please post the updated script

[PCB_Wiz]

@Niluje

These parameters follow the Altium way as defined here (for via to track only): http://techdocs.altium.com/sites/default/files/wiki_attachments/235632/TeardropsDlg.png

Teardrops are a great idea, but I’ve found arc geometry teardrops give the best results, for clearance to nearby PADS, and allowing larger teardrops.
Not sure if you can support ARC as an option ?

[nicholas]

its an issue for the manufacturer

if they feels it necessary they ask for permission to add it.

post-processing carried out at fab, as is balance patterns etc

IMHO

[Niluje]

@maui

you could also add a function to add teardrops only on selected vias (selection is available in GAL mode)

.IsSelected()

I am actually working on it right now. It is a bit complex but I think I will be able to get something quite quickly.

@PCB_Wiz

Teardrops are a great idea, but I’ve found arc geometry teardrops give the best results, for clearance to nearby PADS, and allowing larger teardrops.Not sure if you can support ARC as an option ?

This is clearly possible. The only drawback is that it will generate complex zones for each teardrop. Nevertheless, can you (or anyone) give some references about the arc radius ? I am not able to find anything.

@nicholas

its an issue for the manufacturer

For sure, that’s why I want it !

[maui]

@Niluje

I am actually working on it right now. It is a bit complex but I think I will be able to get something quite quickly.

have a look here …

Does anyone know how to set all the selected line widths in one go?

and this script is useful to change Layer of selected lines import pcbnew board = pcbnew.GetBoard() Dwgs_User=40 for drw in board.GetDrawings(): if drw.IsSelected(): drw.SetLayer(Dwgs_User) where Layers nbrs are: (0 F.Cu signal) (31 B.Cu signal) (32 B.Adhes user) (33 F.Adhes user) (34 B.Paste user) (35 F.Paste user) (36 B.SilkS user) (37 F.SilkS user) (38 B.Mask user) (39 F.Mask user) (40 Dwgs.User user) (41 Cmts.User user) (42 Eco1.User user hide) (43 Eco2.User user) …

and this is a function for annular checking

Annular checking: How do I check if all my pads diameter is drill diameter +0.3 (or so)?

Hi again, EDIT: I corrected annular calculation, which has to be 1/2 the previous calculation value I’ve added a checking also for via annulars and added an extra on drill tool as here the script @ github

[PCB_Wiz]

[quote=“Niluje, post:7, topic:3388”]
This is clearly possible. The only drawback is that it will generate complex zones for each teardrop. Nevertheless, can you (or anyone) give some references about the arc radius ? I am not able to find anything. [/quote]
This is how PADS layout sets ARC teardrops.
I think that ratio is a % of PAD diameter, and the teardrop polyline can match the trace width
You can see how much closer other pads/vias/corners can be placed, with curved teardrops.
It does not need a lot of segments to approximate the arc, maybe 5 or 7 a side ?

I wonder if KiCad scripts can trawl the DRC error reports/tags, as then a 2 pass could be possible, where offending teardrops are removed or adjusted.

PADS can also generate teardrops on angled entry into oval pads.
There are no teardrops on trace T junctions, they apply to “last-segment intersecting pad-outline”

[Joan_Sparky]

@PCB_Wiz

It does not need a lot of segments to approximate the arc, maybe 5 or 7 a side ?

I think there is arc support for tracks coming. Someone who does RF circuitry has got code working that does arc tracks… but I have no idea about how far away that is from implementation into the official branch.
@cbernardo, @keruseykaryu, @madworm or @caer will probably know more about the status - if there is any.

That’s the relevant thread:

Microwave Toolbar - shape description file experiences or documentation?

I’m trying to write a script to generate traces for microstrip filters for import into KiCad. It looks like the “polynomial shape for microwave applications” tool in the microwave toolbar may make this possible. However, I haven’t found any documentation on the syntax of polynomial shape tool shape description files. Do any of y’all know of any documentation on the microwave toolbar, or of any examples of shape description files?

[PCB_Wiz]

@Joan_Sparky

I think there is arc support for tracks coming. Someone who does RF circuitry has got code working that does arc tracks… but I have no idea about how far away that is from implementation into the official branch.
That’s the relevant thread:

Interesting, but that’s a ways-off, and a simple polyline segmented ARC approx will work now.
If course if full ARC entity support arrives, it will be easy to add.
Meanwhile, best to keep entities DRC and Shove understand,

Note that other CAD pgms have only modest ARC support, - for example, shove with ARC preserve is missing in Mentor.

Edit: I see road map info here, about DRC/ARC and complex Pad shapes

http://ci.kicad.org/job/kicad-doxygen/ws/Documentation/doxygen/html/v5_road_map.html

[maui]

Hi @Niluje
any news from your side about the script?
thank you
Maurice

[Niluje]

Hi @maui,

I have implemented all the requested features: (but the curved teardrops (but I am planning to code it soon)):

• add teardrops only on selected via/pads if some are selected
• add a method to fix the missing polygon parenthesis (this actually also solves the artefacts issue in GAL mode)
• improve performances
• Fixed some bugs in teardrops file

I only have to make it readable and clear before releasing it. This might be done by the end of the week.

It took me much more time than I initially though because I became father ten days ago which did not let me much brain time available.

I am now struggling with github to import my personal ssh-only hosted git repos. This will be much more efficient to share it here.

[maui]

@Niluje

It took me much more time than I initially though because I became father ten days ago which did not let me much brain time available.

Hi @Niluje
CONGRATS!!! I can understand your happiness and brain storm!!!
I became father 2 years ago and I’m still feeling like that

Maurice

[Niluje]

@maui: Thank you very much! This is all new to me and I really enjoy it!

I managed to get the script done this evening. I created a github account for the occasion: https://github.com/NilujePerchut/kicad_scripts/tree/master and uploaded the script on it.

The readme gives some explanations about how to use the script.

I hope this will can be useful (and not too much buggy).
Thank for all the advices on this thread.

Next step: curved teardrops.

[PCB_Wiz]

@Niluje

I hope this will can be useful (and not too much buggy).Thank for all the advices on this thread.

Next step: curved teardrops.

Sounds cool, looking forward to curved teardrops !

@Niluje

• add a method to fix the missing polygon parenthesis (this actually also solves the artefacts issue in GAL mode)-

If the corrupted file error is solved, you could edit the thread title - maybe add a version number there ?
I expect this to be generally useful, and referred to often.

[davidsrsb]

@PCB_Wiz

If the corrupted file error is solved, you could edit the thread title - maybe add a version number there ?

I have edited it to something more sensible

Congrats Maurice on the baby

[Niluje]

Thanks for the modification, this looks better now.

As suggested by @PCB_Wiz, I also added the current revision and will keep it synced with the github version.

[Niluje]

Curved teardrops are now available.
The script is still available on my github page:

NilujePerchut/kicad_scripts

The script behaviour is identical to the previous version (0.2.0).
Curved style is used by default. The number of segments per curved is controlled by the parameter “segs” of the setTearDrops function (default is 10).
If segs is set to 2, straight lines are used.

I hope this will help.

Notice: I am not very good in geometry and the only solution I found is to use a bezier curve in order to keep the teardrop tangent to the track and the via. It works but it is quite expensive in processing time. If someone has a better method, please let me know.

The script version is now 0.3.0 (the thread title is now modified)

[yangjinhua1990]

HI
thankyou for your help, I get one error:
File “C:\Program Files\KiCad\lib\python2.7\site-packages\pcbnew.py”, line 31, in
import _pcbnew
ImportError: DLL load failed: %1 不是有效的 Win32 应用程序。

Win10 64bit
python2.7.4 64bit

[mmccoo]

@Niluje

The reason you’re getting corrupt output files is because you need to call z.CloseLastContour() after z.AppendCorner§

I see this as a bug in kicad; AppendCorner should call it for you. (I’ll suggest it on the developer maillist)

Sadly, the only way to know this is to step through the c code in the debugger.

Miles

[Niluje]

Thank you very much!

I will correct it as soon as possible. This will be a huge enhancement!