Weird behaviour of the design block function.

[ArguZ]

Hi there,

i wanted to talk about a strange problem i run into every time i use the design blocks.

What happens is that the design block utility complains about double net classes names instead of merging them.
We generally use only "default" "Power"and "GND"in all our designs and it would be great if the nets would just be connected when using a block that has the same net names.

Instead it refuses to paste the block and i first have to rename the class to something else, paste the block, then rename the nets back.

I attached a file that illustrates the problem.

[jorge_garcia · Accepted solution]

Hi ArguZ,

I hope you're doing well. In this particular image the issue is because the Power class shows up in both files but occupies a different slot. The name of a class has no bearing on it's member nets since that would be very limiting (that requirement basically means that a netclass can only apply to one net which somewhat defeats the idea of a netclass).

One thing that can help is to follow the same pattern when making your netclasses and naming them, since that will minimize or eliminate these dialogs popping up.

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

Best Regards,

[ArguZ]

Actually, that makes a lot of sense now...

So the slot number is the important part, and then the name...ok..i get it.
So it is important that we keep the order and name consistent...Eagle is unable to sort the name by name first.

0 default

1 GND 

2 power

will not work with

0 default

1 power

2 GND

for example...

All right, thanks a lot 🙂