Re: [Kicad-developers] DRC rules panel

Neat, that'll be super useful On Mon, Jul 20, 2020, 9:56 AM Jeff Young wrote: > To do syntax highlighting and code completion. > > > On 20 Jul 2020, at 14:41, Ben Ellis wrote: > > > > Why are the DRC rules parsed w/ s-exprs as they're being typed instead > of after? I just fixed a bug where

Re: [Kicad-developers] DRC rules panel

To do syntax highlighting and code completion. > On 20 Jul 2020, at 14:41, Ben Ellis wrote: > > Why are the DRC rules parsed w/ s-exprs as they're being typed instead of > after? I just fixed a bug where typing ) without ( crashed the entire program >

Re: [Kicad-developers] DRC rules

Hello Jeff, I just checked and that doesn't seem to be the case here. R1 /a0cec481-6d12-448f-86cc-c28b78945760 R2 /2b22cd25-9b07-4b44-9454-a447c5deb022 R3 /5728510b-9b66-4b52-a87f-214fd4df2e61 R4 /305018a5-34e0-410a-bff5-1eb7a79bc504 R5 /36178733-2e55-42eb-8e00-ab3976b16d92 R6

Re: [Kicad-developers] DRC rules

Hi Mark, We’ve seen something like that DRC error before. I think it was because the two items (the reported item and the correct item) had the same UUID. Can you check to see if that’s the case here? Thanks, Jeff. > On 4 Jun 2020, at 13:59, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I

Re: [Kicad-developers] DRC rules

Erhm, ooh yeah, I sorta nuked the jenkins instance that performed the mirroring... so I will need to fix that one of these days.. On Thu, 4 Jun 2020 at 14:59, wrote: > > Hello Jeff, > > I was using github instead of gitlab, this lags gitlab by a day it seems. > The problem fixed with

Re: [Kicad-developers] DRC rules

Hello Jeff, I was using github instead of gitlab, this lags gitlab by a day it seems. The problem fixed with ae852e17f987b77e2acf141285edbbbdaf27548f. I am not able to reproduce the overflow, but it seems it might be something else. The attached project does contain a DRC error, but the wrong

Re: [Kicad-developers] DRC rules

Hi Mark, That’s 6 change-lists too early for the fix. You need at least d2cd4de280353b02ab66dab8e22e8da88415dc13. Cheers, Jeff. > On 4 Jun 2020, at 10:13, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I just tried version 9ff09aa784551264e89350368f61ed6b35266f7a, but > it still fails. I

Re: [Kicad-developers] DRC rules

Hello Jeff, I just tried version 9ff09aa784551264e89350368f61ed6b35266f7a, but it still fails. I tells me that it requires 1.3mm clearance, but both the hole and the track are in the "Net-(C1-Pad1)" netclass, which should only require 0.25mm. The plane clearances are as expected. With this

Re: [Kicad-developers] DRC rules

Hi Mark, The hole clearance logic never got updated to pass both items (the track and the hole). It should work now. Cheers, Jeff. > On 2 Jun 2020, at 22:27, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I've tried my big board and the clearances seem to work OK for planes. > I still have

Re: [Kicad-developers] DRC rules

Hello Jeff, I've tried my big board and the clearances seem to work OK for planes. I still have to compare the gerbers and check if they are exactly as expected. However I get a lot of clearance error on holes in the board, and am unable to solve this. I've attached an example project. There is

Re: [Kicad-developers] DRC rules

Mark, Yes, last selector. Order of rules (at present) doesn’t matter. No, we were not planning on keeping the separation, although we did discuss supporting named conditions. Cheers, Jeff. > On 2 Jun 2020, at 13:00, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I assume in that case the

Re: [Kicad-developers] DRC rules

Hello Jeff, I assume in that case the last selector is applied and not the last rule, correct? To be honest I prefer the selector/rule seperation, is that going to stay? regards, Mark. Jeff Young wrote: Hi Mark, The condition syntax was just a preview. It???s not

Re: [Kicad-developers] DRC rules

Hi Mark, The condition syntax was just a preview. It’s not implemented yet. You’ll need to use the selector syntax for now. So, for instance: (selector (match_netclass "Net-(C1-Pad1)") (match_netclass "Net-(C1-Pad1)”) (rule “Min_Net-(C1-Pad1)") Cheers, Jeff. > On 2 Jun 2020, at 11:05,

Re: [Kicad-developers] DRC rules

I just tested the old simple testcase, the new rule file is: (rule "Max_Net-(C1-Pad1)" (constraint clearance (min 1.3mm)) (condition "A.netclass == Net-(C1-Pad1)")) (rule "Min_Net-(C1-Pad1)"

Re: [Kicad-developers] DRC rules

Hi Mark, Rules are now evaluated in order: last one which matches wins. Most of the time you won’t need priority, but if you do have two rules that match the same things, put the higher priority one later in the rules file. Cheers, Jeff. > On 2 Jun 2020, at 09:41, mdoes...@xs4all.nl wrote: >

Re: [Kicad-developers] DRC rules

Hello Jeff, I tried to give the big board a new attempt, previously a lot of strange things happened which I quite couldn't figure out. I noticed the priority was no longer accepted. Can you give a quick update on the intended way the rules are supposed to be used? regards, Mark.

Re: [Kicad-developers] DRC rules

Hello Jeff, It works correctly with 4f14769ce1ca587f72b51024a71e12a97d9d42f8. I will have to update the rules before I can check the big board. This will take some time, I'll let you know the result. regards, Mark. Jeff Young wrote: Hi Mark, There are 4 or 5 bug

Re: [Kicad-developers] DRC rules

Hi Mark, There are 4 or 5 bug fixes after the hash you’re using. The one I just pushed is most likely to address your pad-to-pad DRC issue. Cheers, Jeff. > On 21 May 2020, at 20:53, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > That works fine on the plane, but when I do a DRC check if

Re: [Kicad-developers] DRC rules

Hello Jeff, That works fine on the plane, but when I do a DRC check if fails on the pads of C1 and C2. I'm using cec857c0f49d4fd984a4095896306ff5d3a5930e, not sure if you changed anything after that. To me the syntax is just fine, as long as these things can be specified correcly. regards,

Re: [Kicad-developers] DRC rules

Hi Mark, That’s expected. The effective clearance is the largest specified in all rules that match. Since both selectors match in the same-net case, the effective clearance is 1.3mm. There is a “relaxed” token to address this, which allows a higher-priority rule to relax a constraint. So

Re: [Kicad-developers] DRC rules

Hello Jeff, I've tried to get the big board working, but I'm unable to set a default clearance on a netclass. What I want to achieve is that a certain netclass has a small clearance (0.2mm) with itself, but a large clearance to other netclasses, for example 5.5mm. For some netclasses I would like

Re: [Kicad-developers] DRC rules

Jeff, A definite +1 for that from over here! Thanks for the clarification. Yours, James. On Thu, May 21, 2020 at 1:33 PM Jeff Young wrote: > While the prototype is selector-based the “real” implementation is likely > to be expression-based, so you’ll be able to say something like: > > (rule

Re: [Kicad-developers] DRC rules

While the prototype is selector-based the “real” implementation is likely to be expression-based, so you’ll be able to say something like: (rule “my special rule” … (condition “A.net == B.net ”)) Cheers, Jeff. > On 21 May 2020, at 12:19, James Jackson wrote: >

Re: [Kicad-developers] DRC rules

Hi Jeff, The background is that I'm looking at a ruleset which has different rules depending on whether two neighbouring vias are in the same, or different, nets. Running the risk of 'feature creep', of course, I think the constraints can indeed be met by what is there, but I suppose my question

Re: [Kicad-developers] DRC rules

Hi James, It sounds like you’re looking for hole-to-hole min. That’s in the existing constraints system in 5.99; you don’t need rules for that. Or does your hole-to-hole min depend on the specific via, specific netclass, or something else? (The current hole-to-hole min is board-wide.)

Re: [Kicad-developers] DRC rules

Hi Jeff, Many thanks for this - looks very powerful, and when it gets hooked in to the PNS router will be killer. An issue I'm currently grappling with a variety of rules considering placements around vias. Some rules require a distance measured from the outside of the annular ring to a track (or

Re: [Kicad-developers] DRC rules

If the Inspect > Design Rules Checker dialog is going to be re-done, I'll wait for that to happen and provide feedback if and when. Thanks. On Wed, 20 May 2020, 20:28 Jon Evans, wrote: > Copying and pasting Jeff's text from the forum since it wasn't in his > original email to this list: > >

Re: [Kicad-developers] DRC rules

Copying and pasting Jeff's text from the forum since it wasn't in his original email to this list: "First the small text: the rule syntax WILL CHANGE. What’s there today is a PROTOTYPE. There will be NO TOOLS for migrating today’s rules to later rules. Think of it as a sandbox, not a

Re: [Kicad-developers] DRC rules

You can file this as an issue if you'd like, but it's already planned to completely re-do this UI at some point once we know what the actual DRC implementation will be. We're not doing that yet because the new system is still very much in flux. On Wed, May 20, 2020 at 3:22 PM Diego Herranz

Re: [Kicad-developers] DRC rules

Hi, It's nice getting a powerful rules system. Thank you for all the work. Just because it is slightly related to this. I find misleading that opening Inspect > Design Rules Checker, you get access to modify Minimum Track Width, Minimum via size and minimum uVia size. That is a subset of the

Re: [Kicad-developers] DRC rules

Awesome! Thanks Jeff! I'm just starting to look at this and I have something quick to mention regarding the UI: At Design Rules > Constraints in the 'Zone fill strategy' section, the options are two checkboxes but they appear to be mutually-exclusive. Should they be radio buttons instead? On

Re: [Kicad-developers] DRC rules

Excellent, now it works :-) I'll test the big board tomorrow. For me this was the most important feature missing from kicad, thanks for making it work. regards, Mark. Jeff Young wrote: Congrats on the first bug! Actually 4 separate ones: the caching mechanism was

Re: [Kicad-developers] DRC rules

Congrats on the first bug! Actually 4 separate ones: the caching mechanism was causing the rules to not be loaded when the board was read, the zone cutout stuff wasn’t fully hooked up to the new rules engine, there’s no "Net-(C1-Pad2)" netclass in the document (only "Net-(C1-Pad1)”), and the

Re: [Kicad-developers] DRC rules

Sorry, forgot to attach the project. <> ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] DRC rules

Hello Jeff, Seems easy to reproduce, so here is a test project. There are just two netclasses and three nets. I expected the cutout in the zone to create a 1.3mm clearance for Net-(R1-Pad2). regards, Mark. ___ Mailing list:

Re: [Kicad-developers] DRC rules

Hi Mark, Clearances are in mm, so your clearances are *really* big. At a guess I’d say all the clearances are overflow when we multiply them by mm-to-nm, but I’d think that would give random results not no results. You shouldn’t need to set a priority unless you’re authoring a “relaxed”

Re: [Kicad-developers] DRC rules

I've just tested this on a design and the drc-rules is read, which I know because if I don't add "(version 1)" at the first line I get an error message. Other than that I doesn't seem to do anything. I tried to add "(priority 100)" to the rules, but that is refused when reading the drc file. It's

Re: [Kicad-developers] DRC rules

I got tired of my text editor not highlighting matching parens so there’s now a basic rule editor in Board Setup > Design Rules > Rules. > On 16 May 2020, at 17:02, Jon Evans wrote: > > Thanks Jeff, this is awesome. I look forward to trying it out. > > On Sat, May 16, 2020 at 12:00 PM Jeff

Re: [Kicad-developers] DRC rules

Thanks Jeff, this is awesome. I look forward to trying it out. On Sat, May 16, 2020 at 12:00 PM Jeff Young wrote: > Here’s a really dumb test file just so you can get an idea of what it > looks like: > > (version 1) > (selector (match_netclass "Default") (rule "Big Gap")) > (selector

Re: [Kicad-developers] DRC rules

Here’s a really dumb test file just so you can get an idea of what it looks like: (version 1) (selector (match_netclass "Default") (rule "Big Gap")) (selector (match_type track) (rule "Big Gap")) (rule "Big Gap" (clearance 1.5)) (selector (match_type blind_via) (rule "Big Hole")) (rule "Big