Custom rule won't change space of differential pairs

[aiolus2ZLRU]

The custom rule doesn't work when routing differential pairs.

I'm trying to set the space of differential pair B0_P and B0_N and add a custom rule as below

The general rule was kept as below

After trying different scopes in custom rules, nothing affect the space of differential pair.

where the grid is 1mm, wire width is 0.254mm.

It only shows the violation of space, but the space parameter still follows general rule but not custom rule.

Please help to clarify if I'm missing any setting or how to control the space of differential pairs.

[jorge_garcia]

Hello @aiolus2ZLRU,

I hope you're doing well. Thanks for reporting this, we ran into this shortly before release the developers are already working on this one. 

You are not doing anything wrong it's just not working right now. I'm hopeful that by the next release this will be sorted, can't promise it but I have a good feeling about it.

Best Regards,

[jorge_garcia]

Just to investigate further, did you create the rule after the diff pair was already routed? It won't update the routing automatically.

[aiolus2ZLRU]

No, I always modify the design rule before routing.

I just had a tried, custom rule for differential pairs is working now. Thanks for your quick response. 

[constantin.popescuXD3CL]

Hi @aiolus2ZLRU,

Good to hear the diff-pair routing is now using the custom rule. Do you recall what you did differently this time compared with the last time when it used the general cospper clearance rule? I am asking dbecause I have tested this workflow using the Production Septemebr release and I created a copper clearance rule identical with the one you have created and I can get it to work but there is a catch. You cannot take advantage of the auto-complete that uses the quick-route diff-pair tool because this one can't use the custom clearance rules at the moment. I have assumed that maybe this is what you did the 1st time. If you route manually the diff-pair all the way then the custom clearance will be used otherwise it'll revert to use the general copper clearance. I am looking into fixing this issue as soon as possible.

I hope this helps.

Please let me know if there is anything else I can help you with. 

Kind Regards,

[constantin.popescuXD3CL]

Hi @aiolus2ZLRU,

I have played with the diff-pair router and the custom rules and you can use In Net Classes scope if you have a net-class that contains your diff-pair or all of your diff-pairs for both Object 1 and Object 2 or you can use In Diff Pair scope for both objects. Using In Signal will not work at this time because the quick-route diff-pair engine only uses one signal to get the clearance and the custom rules require 2 scopes (we can't use the same signal on both Object 1 and Object 2 scopes). I am looking into improving this behaviour right now. If you can use any of the above scopes that would help you circumvent this issue. Please see the custom design rules snapshot bellow:

Please let me know if there is anythign else I can help you with.

Kind Regards,

[aiolus2ZLRU]

I always use manual routing, but things are strange now.

Yesterday, custom rule for differential pairs failed on my laptop and desktop, and this morning it seems work as expected on my laptop. But now when I tried same things on my desktop, it still not work. Both computers run latest version of Win10.

I reopen a test project to try the differential pair routing on my desktop. I reload default design rule and add only 1 custom rule for clearance which resualt as below:

Space didn't change, only violation was showed.

Besides, when the design rule is work on my laptop, the meander is not work on differential routing.

Below is the software version on my desktop

If there is further finding, I'll update here.

[aiolus2ZLRU]

Sure, I've tried In Netclass Scope but not work on my desktop as below.

it's really weird, I'll try again on my laptop.

[aiolus2ZLRU]

I just find the point, the custom rule does not work when differential pairs are centralized.

Same custom rule, PairA won't affect by design rule, but PairB does.

[aiolus2ZLRU]

Furthermore, I tried meander on differential pair and resualt as below

For centralized PairA, custom rule not applied, meander length 50mm is worked perfect.

For shift PairB, custom rule applied, but meander only work on single wire.

These are current findings.

[jorge_garcia · Accepted solution]

Hello @aiolus2ZLRU,

Thank you for reporting this. Our developers are already working hard to correct these issues ASAP. None of the custom rules will work currently for diff pairs but this is being addressed.

Let me know if there's anything else I can do for you.

Best Regards,

[aiolus2ZLRU]

That's ok, I can still use general design rule to get work done.

Wait for your update on custom rule, it will be more convenient if works.

Thanks.

[HelenChen-ElectronicsQA]

Hi @aiolus2ZLRU ,

Hope you have a great day.

Today the latest Production build is updated to 2.0.20460 with the fix about the issue you reported. Could you please upgrade to latest version to have a try? Thank you so much for reporting this issue to us.

Thanks,

Helen