More unintended ripup bugs (7.5.1)

On 07.03.2016 21:29, Jorge Garcia wrote:

Anyway, Im still seing unintended ripup bugs like described in the

thread "7.2.0 unintended ripup bug" . Do I really have to leave the

hierarcy design to get it like I need? This is a rather serious issue to

me.

 

Ok, I verified that the module I had in there caused this effect. This

basically means I have to ditch modules until it gets fixed. Too bad, I

really have a lot of same-stuff instances here and I was really up to

finish the ulp I was writing to copy placement and routing from a

master, but this feature is important to me to even make my new

16 layer design routable at all.

 

I hope the issue will get addressed in the near future.

 

Hi Morten,

 

Bob Starr had started a ULP to handle copying placement and routing from

a master, so don't reinvent the wheel you can use his as a starting

point. His ULP can't replicate the power and gnd nets though. It's

called mod-duplicate you can find it on www.cadsoftusa.com > Downloads.

 

I'll talk to the devs about this issue and see what happened there.

Thanks Jorge. I will look at Bob Starr's ULP, but I am already convinced

I need a better one Yes I have indentified the challenge of detecting

global nets in a module instance. I believe I can add a region polygon

on some suitable layer and modify the module to get these nets too.

In fact, the placement part is already written, so I should be close to

finish my "reinvented but improved wheel", but I don't want to spend

more time on it until I have use for it.

In the future sometime, I expect this ulp to get redundant, and Eagle to

handle this stuff, possibly by using a design as a sub-part.

Regards

Anyway, Im still seing unintended ripup bugs like described in the

thread "7.2.0 unintended ripup bug" . Do I really have to leave the

hierarcy design to get it like I need? This is a rather serious issue to

me.

 

Ok, I verified that the module I had in there caused this effect. This

basically means I have to ditch modules until it gets fixed. Too bad, I

really have a lot of same-stuff instances here and I was really up to

finish the ulp I was writing to copy placement and routing from a

master, but this feature is important to me to even make my new

16 layer design routable at all.

 

I hope the issue will get addressed in the near future.

 

Hi Morten,

Bob Starr had started a ULP to handle copying placement and routing from

a master, so don't reinvent the wheel you can use his as a starting

point. His ULP can't replicate the power and gnd nets though. It's

called mod-duplicate you can find it on www.cadsoftusa.com > Downloads.

I'll talk to the devs about this issue and see what happened there.

Best Regards,

Jorge Garcia

On 03.03.2016 12:31, Morten Leikvoll wrote:

In the 7.4.2 beta release notes you had:

 

"- Restored V6 behavior for designs w/o hierarchy if combining or

renaming net segments, which could cause unnecessary ripups."

 

Now that I started to use hierarcy, does this mean this fix is lost? The

stuff I try to work with is not even part of the hierarcy.

(did the developers take a shortcut on this?)

 

Anyway, Im still seing unintended ripup bugs like described in the

thread "7.2.0 unintended ripup bug" . Do I really have to leave the

hierarcy design to get it like I need? This is a rather serious issue to

me.

Ok, I verified that the module I had in there caused this effect. This

basically means I have to ditch modules until it gets fixed. Too bad, I

really have a lot of same-stuff instances here and I was really up to

finish the ulp I was writing to copy placement and routing from a

master, but this feature is important to me to even make my new

16 layer design routable at all.

I hope the issue will get addressed in the near future.