Hi to group ,
As i checked and confirmed in forums push and shove stops working with drc violations . I tried many ways to find a solution but no luck . This is a major asset in manual pcb routing It’s difficult to reroute bus lines or dense digtal circuits one by one every time. There is line no spreading to fix violations. Is it true that it is planned for version 10 ?.
Sorry, it’s not clear what feature you’re asking for?
Let me gve an example
Let’s say you have a board routed with clearance 8 mils .In many places you have 5-8 tracks running in parallel with that clerance .Let’s say you decide to change clearance as a rule to 9 mils . There are everywhere violations .If you try to drag a segment or try to reroute ,Kicad shows the violation in intense green color and returns track to original state . At that point you have to erase tracks and start again .Push and shove is not working .Its crusial that there is an easy way out of this condition. In the past i had some pcb’s made with easypc-pro and it handled this condition . Possibly it’s a difficult task so my question if you plan to have it in KICAD 10 .
Ah I see. I don’t think that’s planned, but you could lodge a feature request on GitLab.
Please add cross links if you make a feature request for this. It is a very common problem. Also when for example moving or rotating a section which already has a partial layout, it is very common to create DRC violations, and those violations are difficult to clean up.
KiCad does support a [Ctrl + Click] to commit a new position even if it has DRC violations. That does help, but a better solution would be nice. Maybe it would work if DRC violations with tracks and pads that were already existent before the drag would be excluded when determining the new position.
Sometimes the Push 'n Shove does move tracks to a new location that does not have a DRC violation, but that is not often.
Hi,
I did a feature request in Gitlab . That’s the number one topic to address in my opinion . The whole idea is being productive so routing is the most important topic.But anyhow who can complain for the price of this program,Frankly i think these people have done more than enough
.
If there was a track DRC violation, previous versions of KiCad would try to Shove/Walkaround the track. So it sounds more like a regression actually.
Something is wrong in routing engine as far as i understand . Another headache is V9 can;t even export to V8 or V7 .That’t another big question . Or at least make a pcad, pads or altium ascii export .
Hi,
Three weeks ago I routed a pretty complex 8-layer board using V9. My only complaint was about the jankiness of the diff pair router… So either I don’t know how to use the router in a way that exposes the issues you see or I’m not aware of a particular case where the shove algo stops working. I would be happy to fix it if you’d provide me with a design that demonstrates your particular issue.
Best,
Tom
If you hold Ctrl and click, it will apply the changes.
Hi,
Sorry i was misunderstood. Kicad finishes the job fine. The point is how much time it takes to finish
the board . Routing and autorouting is actually the holly grail of pcb design .It’s the center point about pcb design . It’s impossible after a violation is detected not to be able to use push and shove to solve the violations ,if possible ,and proceed.It’s not productive to try to move bus routed tracks tightly spaced and use only Ctrl +click to fix lines.Push and shove should fix that . I’ll give you an example in the picture attached .The bus routed lines are tightly placed with 6 mils spacing , 10 mils track width . i changed the highlighted track to 12 mils . After that i tried moving NET2 up .No operation was possible. What solution do i have ?.Move all lines over NET1 .Move NET1 , Check that no viloation exists and operate push and shove again . This is a simple test case i present . In reality you get much more complex situations that make this point far time consuming . Overall though Kicad is a quite productive tool .If i can be of any assistance or you want me to send you test cases to help i would do it gladly . I can sedn you of course this test case file if it helps .
Why not just attach it here if it’s not confidential. It never hurts to give an example project right away, with an explanation and instructions how to trigger the problem there. Often it would save several rounds of questions+answers.
