Revert net name back to default

On 16/02/2017 9:02 p.m., Marco Trapanese wrote:

Hi,

I'm using EAGLE v6.6 on Windows 7 64-bit.

 

Is there a way to tell EAGLE to generate again a random name for a net

previously named?

 

I mean:

 

1. say you have a net called N$4

2. using the NAME command you change it to FOO

3. now I want to revert back to a default name, like N$*

 

I looked in the docs about NET command and NAME pages without find an

answer.

 

Marco

Hi Marco

The ULP I wrote can do that for you

rename_net.ulp

http://eagle.autodesk.com/eagle/ulp?utf8=%E2%9C%93&q%5Btitle_or_author_or_description_cont%5D=rename_net.ulp&button=

HTH

Warren

--

... use NNTP://news.cadsoft.de and a functional news reader like

Thunderbird!

... or http://www.eaglecentral.ca browser access to CadSoft EAGLE

support forums.

On 2/16/2017 3:02 AM, Marco Trapanese wrote:

Hi,

I'm using EAGLE v6.6 on Windows 7 64-bit.

 

Is there a way to tell EAGLE to generate again a random name for a net

previously named?

 

I mean:

 

1. say you have a net called N$4

2. using the NAME command you change it to FOO

3. now I want to revert back to a default name, like N$*

 

I looked in the docs about NET command and NAME pages without find an

answer.

 

Marco

Hello Marco,

I hope you're having a good day. That's an unusual use case, thanks for

bringing it up.

If there are multiple nets named FOO in your design, then they are all

interconnected.

The easiest and safest thing to do is to delete the net and just redraw

it, EAGLE will assign it an N$ name.

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

Best Regards,

Jorge Garcia

--

We have a new forum here <http://forums.autodesk.com>

Hi Jorge,

 

 

The easiest and safest thing to do is to delete the net and just redraw

it, EAGLE will assign it an N$ name.

 

hm. this can be a little bit complicated if there more than two connections , e.g. bus connections or a lot of nodes.

I suggest two actions.

1) exporting the netlist - e.g. netlist(1).txt and check where the N$1...x are.

If here is a numbering hole then you can fill this by inserting as e.g. N$[33] (33 is just space holder) or find the lastest N$xxx

2) then renaming with [NAME] the complete wire (not the segment only) in the sch with this found N$xxx name.

done.

Best Regards,

Gerald

---

No, the easiest thing to do is run the ULP I mentioned earlier.

One of the options within the ULP is to use the lowest unused N$xx name.

Just as Eagle would do if you drew a new net.

HTH

Warren

--

EAGLE support forums at http://www.eaglecentral.ca :: Where the EAGLE community meets.

Il 16/02/2017 19:53, warrenbrayshaw ha scritto:

Hi Marco

The ULP I wrote can do that for you

 

rename_net.ulp

Thanks!

I'm going to try it and then I will write a feedback here.

Best

Marco

Il 16/02/2017 19:58, Jorge Garcia ha scritto:

I hope you're having a good day. That's an unusual use case, thanks for

bringing it up.

To me, it happens when I have to insert a component in the middle of an

existing net. I delete one segment, place the new component and

reconnect both sides (I'm talking of two pins components, like R, C, L,

D....).

If I had previously named the net, it keep its own name, at least at one

side. If I need to have the other side to the given name, I need to

revert back to an "un-meaningful" name the first and set again the

desired name to the second.

If there are multiple nets named FOO in your design, then they are all

interconnected.

For my (personal?) use case, it should apply only to that segment.

Because is there I broke the net to place a new component.

I'll try the ulp of warrenbrayshaw and see if it fits!

Thanks

Marco

Il 17/02/2017 08:05, Marco Trapanese ha scritto:

I'm going to try it and then I will write a feedback here.

Yeah! It's great! Thank you

Hi Warren,

Yes, I saw your ulp, forgot to mention it.
The point: Your ulp is not supplied with the Eagle.
It is a privately written tool.

But it makes fine exactly what I had described yesterday with the manual procedure.

By manual you have to read the netlist, your ulp makes this for you.

Yes of course, you can make a little more with it.

But for me, I'm not a friend for overall automatism because may be i have to repair somewhat after that action.

For that action - you have also two steps: loading the ulp and using it.

But you have not a list in your background -> you don't know how many nets you have also you don't know all net names.

For me, i have a list in background and can look for every time during development.

Best Regards,

Gerald

---

Hi,

aha, ok, that's easy i think.

After that if you merges two segments together to one segment, the menu

will ask you, e.g.: "you are connecting two segments;;; the result name will: "...this name, or this name..";; is this ok?"" or similar.

Well, that is easy for N$xx wires. -> just connect it and the suggested name N$xx appears.

This will normally the latest wire number, or the first unused N$xx; e.g. N$1 ( or if N$1 is used, N$2 will come).

Other think about is if you have power wires. Here you have priority usage of this wires.

E.g.

VSS -> GND => GND; GND -> VSS => VSS;

// because you have supply pins on mostly components, you needs to check it manually.

Here in this example: AGND (analogGND) or VSS; but GND (some other have VSS as GND) are power pins of the ICs.

What i want to say: "The wire with that you're going, this wire likes merging to the other and this (other) will you get, or what you want, ... normally."

Best Regards,

Gerald

---