Via Fencing doesn't really work in corners

External Plugins
1

making random vias on top of each other…

Anyone has experience with it? Kicad 9.0, win11

image

image

2

KiCad itself doesn’t have via fencing function. This must be a 3rd part plugin. Please tell more details, change the topic Category to External Plugins if needed, and remember that this forum may not necessarily be the best place to ask a question about some certain plugin. Some plugins are hosted in gitlab or github where they may have discussions and bug reports.

1 Like
3

oh apologize, of course its an external plugin: GitHub - easyw/RF-tools-KiCAD: KiCAD RF tools: footprints wizard and round tracks, mask expander, via fencing

yes, asked in the issues tracker also in github, but not too much life there as I see. Might here some have some experience. Thank you

2 Likes
4

@lowtech
it easier for me to catch the issues here…
Do you have a failing board to test?

2 Likes
5

Sure! Please check out this, Kicad 9.0

via_fencing_issue.zip (8.8 KB)

Thank you very much! :slight_smile:

6

@maui Another simple sample from V9.0.1 on Windows.
Several errors due to two vias in the same location and also placing vias between resistor pads.
Long_test.zip (19.8 KB)

1 Like
7

@maui Another observation. Using the plugin on a single segment of the track in my sample causes a via to be placed directly on the right angled segment of track, shorting it to the B side zone. Looking at the Python code, I don’t see any collision detection.

8

image
image938×412 8.72 KB

9

@HAYDEN
is that a plugin? It is done with the new API?

10

Using the old SWIG API
@maui

image
image714×384 5.63 KB

This plugin does not require the installation of python dependencies

BezierCurveAndVia.zip (10.7 KB)

11

@HAYDEN
thanks for the plugin, but it seems to have similar issues:

image
image1383×1026 49.2 KB

here the testing board
curved_test_fencing.kicad_pcb (66.5 KB)

1 Like
12

This definitely needs to test for too close to another hole and touching another net.
Making this plugin slow is not a problem

13

(Both?) plugin(s) seem to go wrong when the radius of the track is small.

14

a collision detect was working until kv7 IIRC, the instabilities of the swig ‘api’ was a big issue for plugin’s developers.
I think we should move to the new API but it will take time and a new effort.

15

So its time to start a new plugin using the new API. I am not a skilled coder, but seem to have some talent for testing software and tracing bugs.
Is the new API complete enough to do this?

16

The new API examples has some hit testing

17

You can try increasing the chamfer radius, the algorithm for placing vias in the turn section needs to be improved