There is no way to make distinguish between clearance track to track, pin to pin, via to track etc…
This is no good when routing a circuit.
If pins are at 6 mills and you set a clerance of 16, it seems it does not route, or i am wrong?
Enzo
There is no way to make distinguish between clearance track to track, pin to pin, via to track etc…
This is no good when routing a circuit.
If pins are at 6 mills and you set a clerance of 16, it seems it does not route, or i am wrong?
Enzo
What part number do you have that has 6mill spacing on it’s pins?
Spacing is 8 mils, but i want 16 mills from track to track and vias…
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Mail
priva di virus. www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Oh, easy, only use half the pins on the device; skipping every other one.
Sprig i do not understand.
What do you mean in using only half of the pins?
Enzo
I don’t understand what Sprig is saying above.
About different clearances - why do you need them? The minimum clearance is dictated by the manufacturing process, i.e. the manufacturer’s capabilities. The process doesn’t know about pads, tracks or vias, they are only copper areas. Nets are distinct areas and the minimum clearance is the minimum space between areas. If they can do 6 mil space between pads they can do 6 mil spacing between tracks etc.
However, you can set different clearance for certain pads using the footprint editor (Pad properties -> Local clearance or Footprint Properties). The interactive router then follows the global values for track/track, track/via etc. but the DRC may complain.
I now realized that the interactive router may refuse to connect tracks to pads if pad clearance is smaller. In case you use the OpenGL canvas and the interactive router you can change the mode to “Highlight collisions” and check “Allow DRC violations”. Change the mode back to Shove when your’e done with those tracks&pads.
Thanks eelik, it seems to work.
I have to make some practice.
Enzo
The KiPadCheck plugin checks some things that KiCad does not. You might have a look at that to see if it provides what you want.
There is still another option.
As @eelik said, you can set clearances by footprint or by individual pads.
But you can also set clearances for net classes under the Design Rules menu.
You can keep the 16 mils clearance for all nets except for those that arrive to the footprint you need 8 mils clearance.
Thanks for your help
Enzo