Running tracks between pads/pins hack. OpenGL won’t allow but DRC is OK with it coming from Default canvas.
How do I get OpenGL to allow me to run the track between pads when the pads are on it’s opposite layer.
Note: this is a hack I use and these are the conditions as to why
1- Hobbyist, so I make my own board and the minimum I can do is 0.5mm track 0.5mm clearance. I can do 0.2 but shorts are a plenty.
2- I use IC sockets which have parallel pins through out its length so on a 0.5mm track between pads/pins I have at least 0.6mm clearance either side to the IC sockets pin, obviously the pad is not shown for that side.
OpenGL, I’ve tried disabling rules check as well the interactive browser to allow violations but nothing.
Can you disable interactive browser, if so how, or how do I actually run tracks between non existent pads on its layer. If you think about it, the clearance is from the hole edge/centre so with no pad there, just hole, it should allow the track to run as long as its > than the minimum track clearance as does the Default canvas. I’m assuming I can do it in Default canvas for it may take the clearance from the hole edge/centre. OpenGL or Interactive browser must be different.
Any ideas?
Disable DRC check should work.
But the interactive router only updates its settings when you open this tool.
So if you are in interactive router do the following:
- press e and activate allow drc violations (and press ok)
- press esc to leave the interactive router
- press x to get back to the interactive router.
(now drc violations should be allowed.)
Another way would be to edit the router settings before you enter the interactive router.
- got to preferences->interactive routing
- activate allow drc violations (and press ok)
- Enter interactive router (press x)
If this doesn’t work report back with you kicad version. (Maybe there is a bug somewhere.)
By the way could you share the footprint you made, so that we can play around with it?
Sorry there is something i didn’t know until now.
If you read the tool tip of allow drc violation it tells you that this mode only works in highlight collision mode. (not in shove or walk around mode.)
Thanks but I’ll have to take that as a NO. It’s too dangerous, I can place a track anywhere and in conflict with a lot of things, pads tracks, anything. The function of the Default canvas is far better and safer, I can only place the track as long as the clearance is good as I can also see the clearance…
Maybe sometime in another version.
Why not edit the pads you want to connect and specify that they are part of Net-(P15-Pad1) ? Then the DRC should not complain anymore. If those pads are part of a footprint and are electrically connected to another pad, you can give the pads the same ID.
He does not want to connect to this pads. He wants to put a track in between two pads where he normally can not put a trace.
To get enough space on this one copper layer he removed the copper of the offending pads on this layer.
(Done by Setting pad properties as Copper on F.Cu or B.Cu instead of all cooper layers)
But DRC does not take into account that this pad has no copper on this layer.
(I think this is a bug.)
Sounds like it’s PTH/via stack related… as that stuff also acts the same on all layers, no matter what.
If the description in the OP is right, the Legacy canvas could do this though. Interesting. For openGL this must be a bug.
I just spent too many hours trying to find a screen video capture to hopefully show what I mean that gave a decent video. It’s heavily compressed and shrunk so I could upload it. Haven’t had much success with it. Hopefully the vid works.
In any case, for me this subject is closed and thanks for the help.
1 Like
definitely a bug and needs to be reported @pauls969
By the way you still have F.Silk and F.Mask enabled in your pads that have copper only on the bottom.
Thanks, If you’re referring to the video, that’s just two IC’s together to simplifying showing the problem.
Yes i was referring to that.
