Rename wires

Well, I'm going to show my Unix bias here, but there are a *lot* of tools available to do things like this built in to Linux and OS X and available for Windows.  It depends how deep you want to go down the rabbit hole!

My first reaction would be to use "sed" the stream editor.  (Do a search for "sed for windows".)  Sed is used at the command line, and takes some input, modifies it, and sends it to some output.  For example,

sed 's/W500/W512' schematic.sch > newschematic.sch

which would change occurrences of W500 to W512 and create a new file called newschematic.sch without changing the original schematic.sch.  To make sure things look good, you could use the "diff" command on the two files to see exactly what was changed.  Of course, you wouldn't want to have to change that command line and re-run it for every substitution you want to make, so it's better to create a sed script file with all the commands you want (somewhat analogous to that CSV file in the referenced article), and then run the command:

sed -f script.file schematic.sch > newschematic.sch

Sed is a great tool and can be used over and over again without having to modify and recompile.  Now, if you want to learn something a little more sophisticated, there is a simple, yet amazing text processing language called AWK.  AWK knows how to read in a text file line by line, split the line into words and do things to those words.  You can do more testing and manipulating than you can in sed.  AWK is very much like the C programming language, so you can do things like printf to create new output.  Then, if you want to really go down the rabbit hole and get into more powerful scripting languages, the big three in my book are PERL, Python and Ruby.  Each has strengths and weaknesses and each has devout followers and detractors.  Let me know if you're interested or do a search to learn more...

BTW, if you don't want to download and install any of these unix tools, you might consider using Windows PowerShell too...

Thank you for your help.

after some tests I found out that Win doesn't like the following command:

sed 's/W500/W5000' 30c.sch 30d.sch

But the following seems to work so far (thank you google):

sed "s/W500/W5000/" 30c.sch 30d.sch

Well, first everything seems to work fine, it reads and schows all data in the 30c file, but after everything has finished, the 30d.sch is still empty. Any idea what I am doing wrong? Sorry I have to admit that I'm not the shell-guy...

As for the advice with the inconsistent board: Thank you for your advice, but there is no board, only the schematic. It is the shematic of my newly build camper. I know, eagle may not be the best solution for doing that, but works so far ok for me...

Thanks a lot for your help. So far everything seems to work verry nice. Just one thing: With oldname = N.name; we look for all net names. If possible I'd like to change only a range of names, because for example W300/xx-W900/xx are already in the correct order and should not be changed anymore.

The simplest would probably be to look for all wires starting with W1xx (W100 up to W199). I tried to use wildcards like * and ?? (I changed the N.name command to something like W1* or W1?? or W1##) but that doesn't seem to work...I think there is a trivial solution for that?

Even beter would be if i could chose a range of numbers to change (only if it doesn't gets to complex!): For example from W100/xxxx up to W299/xxxx, or W100-W199 plus some unnamed wires (N$1 to N$150 for example)

strxstr? Will that be ULP for beginners lesson 2?

^[ \t]+|[ \t]+$...hmm that looks for me like: You have a roof, you spent time repairing it + you spend more time on repairing it and that costs you more $...am I right?

thanks and good night

Ursicin Caminada wrote:

The simplest would probably be to look for all wires starting with W1xx (W100 up to W199). I tried to use wildcards like * and ?? (I changed the N.name command to something like W1* or W1?? or W1##) but that doesn't seem to work...I think there is a trivial solution for that?

One (simple) way is to add this as a test after oldname = N.name;:

string startpart = "W1";

int position = strstr(oldname, startpart);

if (pos >= 0)

  // It starts with W1 and it should be renamed...

Even beter would be if i could chose a range of numbers to change (only if it doesn't gets to complex!): For example from W100/xxxx up to W299/xxxx, or W100-W199 plus some unnamed wires (N$1 to N$150 for example)

 

strxstr? Will that be ULP for beginners lesson 2?

Yes, strxstr might be a good answer for this because you could write a regular expression that would match the W, then the number, then the slash, or the N$ and the number.

^[ \t]+|[ \t]+$...hmm that looks for me like: You have a roof, you spent time repairing it + you spend more time on repairing it and that costs you more $...am I right?

LOL!  In a regular expression, "^" means the beginning of a line, and "$" means the end of a line.  (They even use "$" as a command in the vim editor to move the cursor to the end of the line.)  The square brackets [] are used for specifying a group, in this case a space and a "\t" which means a tab character.  A regular expression matches anything in the group, so it can be either a space or a tab.  The "+" means one or more of what is right before it.  ("?" is zero or one of the previous thing, and "*" is zero or more of the previous thing.  This is different from the ? and * wildcards.)  The "|" is used to mean the test "or".  So,

^[ \t]+ means one or more spaces or tabs at the beginning of a line

|  or

[ \t]+$ means one or more spaces at the end of the line

Simple, yes? 

So, to match your wire name, the regular expression would be W\d+ which means a "W" followed by one or more digits.  If you wanted to get all W1xx and W2xx numbers, you could use W[12]\d+ which means one or more digits after either W1 or W2.  You can keep trying to modify the regular expression to test for the range of numbers you want to use, or you might want to just use oldname, get rid of the "W" and use strtol() to convert the digits to a number that you can test with some combination of =, < or >.  It would be easy to put a couple variables at the top of your script instead of trying to modify a regular expression every time:

int minimum = 100;

int maximum = 299;

char c = '/';

int position = strchr(oldname, c);

string number = strsub(oldname, 1, position);

int test = strtol(number);

if ( (test >= minimum) && (test <= maximum) )

// in range, do something

Hi,

I tried to put that new code to the old one. Not sure if it could work like that. That is what I tried:

int minimum = 100;

int maximum = 199;

string sheetname;

string message;

string oldname;

string newname;

string lastpart;

char c = '/';

//int number = 100;

//int position;

schematic(S){

  S.sheets(SH){

       sprintf(sheetname, "Sheet: %d\n", SH.number);

       message += sheetname;

       SH.nets(N){

            oldname = N.name;

                 int position = strchr(oldname, c);

                 string number = strsub(oldname, 1, position);

                 int test = strtol(number);

                 if ( (test >= minimum) && (test <= maximum) )

                 // in range, do something

                 // position = strchr(oldname, c);

                 // lastpart = strsub(oldname, position);

                 // sprintf(newname, "W%d", number);

                 // newname += lastpart;

                 // number += 1;

            message += "Rename old: ";

            message += oldname;

            message += " to new: ";

            message += newname;

            message += "\n";

            }

       }

}

dlgMessageBox(message);

Now the Message-Box shows me all nets like it did with the old code, but now only the nets matching the test criteria have the "Rename old:" at the beginning...and none of them have a new name after "to new:" somehow hard to explain...It looks like that:

(...)

Sheet: 4

N$96 to new:

N$97 to new:

(...)

Rename old: W190/50RD to new:

Rename old: W191/50BK to new:

(...)

So I think something is wrong, but I have no Idea what.

As for the regular expressions...thank you for your explanations, but I think I'll put that on hold until I have learned lesson 1 for beginners ;-)

Well, something I didn't tell you before...  "//" means that anything after this on a line is a comment.  A comment is something only for humans to read.  The computer (EAGLE) ignores everything in the comment.  There is another kind of comment too, a multi-line comment that starts with "/*" and ends with "*/".  For example:

/*

this is a comment and EAGLE will ignore everything in it

*/

// this is also a comment, but it only lasts until the end of this one line.

I'm going to try to use the Github Gist function for the ULP code.  I will do that in the next message...

Well, the gist looks very nice on the Element14 site, but it doesn't get through to NNTP. 

You can see what I posted at: https://gist.github.com/AnalogNotes/9377478

At the top right of the code display is a button with "<>" on it.  That will let you view the "raw" code in a form that is very easy to copy and paste.  Let me know if that works for you...

Your code works perfectly, I'll check what is different and try to figure Out what didn't work with my code, unfortunately I'didnd have time to do that yet.

As for the // I found out myself that they are used for comments...could have deleted these lines, but you know, because I don't really know what I am doing on a such script, I just start somewhere and try if it works or not. I then comment out one line, have a look what changed, comment out the next line, try again....
Because of that I just comment out these lines, so if I need them again it is much faster to delete the // than to find and

copy/paste the needed line.

The commented out lines are basically your "old" script in what I copied the new part. I then commented these lines out because I tought they would basically do the same as the new ones...

Gist GitHub: Because I use the Element14 Website instead of newsgroups, I didnt notice a problem with the code missing. What I noticed was that the code is not shown in the notification email, but this isn't a big problem for me. Copy and paste from the element14  website works peerfectly.
Is there any concerns if I post the code directly on to the element14 website? Or why du you use GitHub?

Thanks

Ursicin Caminada wrote:

Your code works perfectly, I'll check what is different and try to figure Out what didn't work with my code, unfortunately I'didnd have time to do that yet.

 

As for the // I found out myself that they are used for comments...could have deleted these lines, but you know, because I don't really know what I am doing on a such script,

I'm impressed, you are doing well!

I just start somewhere and try if it works or not. I then comment out one line, have a look what changed, comment out the next line, try again....

I think that's the best way to learn...

Because of that I just comment out these lines, so if I need them again it is much faster to delete the // than to find and copy/paste the needed line.

This is what "real" programmers do all the time. 

Gist GitHub: Because I use the Element14 Website instead of newsgroups, I didnt notice a problem with the code missing. What I noticed was that the code is not shown in the notification email, but this isn't a big problem for me. Copy and paste from the element14  website works peerfectly.
Is there any concerns if I post the code directly on to the element14 website? Or why du you use GitHub?

It was mostly an experiment.  When I paste code into a post on Element14, every line gets the same indentation, so I make a lot of changes in the editor here.  The Github Gist is nice because the indentation stays the way I created it, and the code is displayed with line numbers.  I could then explain things by line number.

This forum is connected to the NNTP system and all of the posts are stored at the Eagle Central web site too.  Code doesn't transfer very well between them.  I think I will only post code directly here at Element14 in the future.

I use Github and Bitbucket to store all of my programs and my EAGLE files.  That way I have a backup that is not on my own computer and they keep track of all of the changes I make to my files.

OK, I did some testing on a schematic that I have here.  At first, I only had failures.  When I ran the script with the commands "name oldname newname", I got an error message "Unknown part".  I tried several different things, and finally sent a question to Cadsoft tech support.  Jorge pointed out that in the documentation for the name command, it says that "only parts, elements, pads, smds, pins and gates can be selected by their name using the old_name new_name syntax.  Nets, busses and signals have to be clicked first."  Oh no, that means we *have* to use a mouse click!

Luckily, I had just learned something new that I could try.  You can read about it in another thread here on Element14: Re: How do I move/rotate values on a schematic?  I tested a couple commands using "name newname coordinates" by typing them on the command line in the schematic editor, and they worked!  So, then I just had to figure out where in the ULP to find the coordinates for the mouse click.  I looked in the help file, and found that nets have a segments() loop member and that segments have a wires() loop member and each wire has a start point (x1, y1).  Perfect!

So here is the script:

int minimum = 100;

int maximum = 199;

int newnumber = 100;

string script = "grid inch;\n";

string line;

string oldname;

string oldnumber;

string newname;

string lastpart;

char c = '/';

int position;

int test;

schematic(S){

  S.sheets(SH){

    sprintf(line, "edit .s%d;\n", SH.number);

    script += line;

    SH.nets(N){

      oldname = N.name;

      position = strchr(oldname, c);

      oldnumber = strsub(oldname, 1, position);

      test = strtol(oldnumber);

      if ( (test >= minimum) && (test <= maximum) ) {

        lastpart = strsub(oldname, position);

        sprintf(newname, "W%d", newnumber);

        newname += lastpart;

        N.segments(SEG)

          SEG.wires(W) {

            sprintf(line, " (%f %f);\n", u2inch(W.x1), u2inch(W.y1));

          }

        script += "name ";

        script += newname;

        script += line;

        newnumber += 1;

      }

    }

  }

  script += "edit .s1;\n";

  script += "grid last;\n";

  dlgMessageBox(script);

}

exit(script);

I used the "grid inch" command to make sure I was working with the correct units to match the "u2inch" commands.  The "grid last" command near the bottom returns the grid setting to what it was before the script ran.  At the start of each schematic page loop, I add the command to the script to edit that page so that the mouse clicks match the parts on the correct page.  At the end, I put in the command "edit .s1" to return to the first page of the schematic.  The dlgMessageBox command shows you the script before it runs, and the very last line, "exit(script);" is what actually runs the script and makes the changes.  If you want to see what will run without making changes, comment out the exit line.  If you don't want the dialog box to show, you can comment out the dlgMessageBox line.

Hopefully that works for you!  Let me know if you have any questions...

Wow, thank you very much for your huge work.

When I was reading about clicking, I was a bit concerned...clicking on every net...I wasn't aware that the ULP script can click as well. Anyway, you as a "unix-guy" wouldn't click on every wire, would you? ;-)

I was trying your script and it looks very nice. As far I can say right now everything works like it should. Great. Thank you very much, you made it very easy to chenge all my wire-names.

Do you know what name will be given after all W1xx are used, will it go from W199/xx to W200/xx, W201/xx?

I tried to figure out what you are doing exactly, but especially for the following lines It would be nice if you cold give a short explanation (only if you have the time for it!):

sprintf(line, "edit .s%d;\n", SH.number);

sprintf(line, " (%f %f);\n", u2inch(W.x1), u2inch(W.y1));

position = strchr(oldname, c);

      oldnumber = strsub(oldname, 1, position);

I think the first 2 lines are some of these regular expressions? But what are they exactly doing?

And what are the last 2 lines doing?

Can this script simply be changed, so it would rename a part (or all) of the N$xxx named wires to W1xx or W2xx or something like that? I was trying some things but right now I wasn't able to get that working... But please don't put to much work into that! If it is a simple thing ok, if not it's not that important!

...but while I am writing, I should maybe try sed for that again... Let's see if I find some time to try a few things on that during the weekend.

Thank you very much and have a nice weekend.

Wow, thank you very much for your huge work.

When I was reading about clicking, I was a bit concerned...clicking on every net...I wasn't aware that the ULP script can click as well. Anyway, you as a "unix-guy" wouldn't click on every wire, would you? ;-)

I was trying your script and it looks very nice. As far I can say right now everything works like it should. Great. Thank you very much, you made it very easy to chenge all my wire-names.

Do you know what name will be given after all W1xx are used, will it go from W199/xx to W200/xx, W201/xx?

I tried to figure out what you are doing exactly, but especially for the following lines It would be nice if you cold give a short explanation (only if you have the time for it!):

sprintf(line, "edit .s%d;\n", SH.number);

sprintf(line, " (%f %f);\n", u2inch(W.x1), u2inch(W.y1));

position = strchr(oldname, c);

      oldnumber = strsub(oldname, 1, position);

I think the first 2 lines are some of these regular expressions? But what are they exactly doing?

And what are the last 2 lines doing?

Can this script simply be changed, so it would rename a part (or all) of the N$xxx named wires to W1xx or W2xx or something like that? I was trying some things but right now I wasn't able to get that working... But please don't put to much work into that! If it is a simple thing ok, if not it's not that important!

...but while I am writing, I should maybe try sed for that again... Let's see if I find some time to try a few things on that during the weekend.

Thank you very much and have a nice weekend.

Ursicin Caminada wrote:

Wow, thank you very much for your huge work.

 

When I was reading about clicking, I was a bit concerned...clicking on every net...I wasn't aware that the ULP script can click as well. Anyway, you as a "unix-guy" wouldn't click on every wire, would you? ;-)

You are welcome!  It was fun to figure out how to do it.  As a Unix guy, I believe in being lazy and making the computer do all the work!

Do you know what name will be given after all W1xx are used, will it go from W199/xx to W200/xx, W201/xx?

Yes, the name will count up as far as it needs to for all the names.  It will go from 199, 200, 201,...,299, 300,...

I tried to figure out what you are doing exactly, but especially for the following lines It would be nice if you cold give a short explanation (only if you have the time for it!):

 

sprintf(line, "edit .s%d;\n", SH.number);

sprintf(line, " (%f %f);\n", u2inch(W.x1), u2inch(W.y1));

position = strchr(oldname, c);

oldnumber = strsub(oldname, 1, position);

 

I think the first 2 lines are some of these regular expressions? But what are they exactly doing?

And what are the last 2 lines doing?

In languages like "C", there is a command to print formatted output, "printf".  Instead of regular expressions, printf uses what is called a template language.  You create the format string that you want to print and put in format specifiers.  Sometimes we don't use any format specifiers at all, for example many C programming books start with the "Hello world" program, which says something like:

printf("hello, world");

Format specifiers are used to display variables.  If you want to display a decimal, like the number of the schematic page, you would need to use the specifier "%d", and then list the name of the variable after a comma.  So, with the format string "%d" and the variable SH.number, the command would be:

printf("%d", SH.number);

In the first line above, I wanted to create a string for the script that says "edit .s1;" or "edit .s2;" for each page of the schematic, so I used the %d in place of the number in the format string and the value of SH.number was substituted into that part of the output.  To put that string on its own line in the script, I put "\n" at the end of the format screen.  That gets replaced by the newline (return) character.

You can see that there is an "s" in front of the printf, it is a different version of the command and it prints formatted output into a string.  In this case, the output is put into the "line" string variable.  I used the line variable as a temporary place to make the command, and then I added that to the end of "script" with the "script += line;" part.  If I had used sprintf to write directly to the script, everything already there would have been erased.

The second line is very similar, but I used "%f" for a floating point number instead of a decimal.  The nice thing about printf and sprintf is that you can use commands instead of just variables, so the first %f is substituted with the output from the command "u2inch(W.x1)" and the second %f is substituted with the output from the command "u2inch(W.y1)".  These convert from the EAGLE internal units to inches.  I could have used other units, but I was lazy and since I'm in the US, I stayed with inches.  The important thing is to match the unit conversion with the grid specification so that the mouse clicks are put in the correct location.

The last two lines are string functions.  The first one uses the "strchr" command to look for a character in a string.  In this case, we look for the contents of "c" which is a slash ("/") in the string "oldname".  The location is put into the variable "position".  The interesting/weird thing about ULP and other languages like C is that everything starts with zero as the first number.  So, if the slash was the first character of oldname, position would be 0.  If the slash was the second character, position would be 1...

The last line uses the "strsub" command to pull a substring (part of a string) out of another string.  In this case, I am pulling a substring starting at 1 and going to "position".  I cheated a little here because I was planning that the first character in "oldname" is a "W", so I didn't want to start at 0 which would have included the "W", instead I started at 1, which is the next place after the W.  If oldname was "W128/1.5OR", this substr command would pull out "128" and put it into "oldnumber".  After that, I used the command "strtol" to convert that string of characters into a number that I could use in the range test.  (The string "100" is different from the number 100.)

Can this script simply be changed, so it would rename a part (or all) of the N$xxx named wires to W1xx or W2xx or something like that? I was trying some things but right now I wasn't able to get that working... But please don't put to much work into that! If it is a simple thing ok, if not it's not that important!

...but while I am writing, I should maybe try sed for that again... Let's see if I find some time to try a few things on that during the weekend.

 

Thank you very much and have a nice weekend.

The script can definitely be changed for that.  I would use the strstr() function to look for the N$ in "oldname".  Something like:

string prefix = "N$";

position = strstr(oldname, prefix);

if (pos >= 0) {

// starts with N$, do the rename here...

}

If I have time this weekend, I will modify the script to do that.  It will probably take less than ten minutes...

While trying on in the original schematic I found an iussue:

As long no wires start on one page and continue on another everything works great, but as soon the wires go to another page I get problems.

As soon the Wires are continuing over more than one page, the script reserves a number for each section on each page. If I then chose to change name on all pages, I get a gap in numbering...hard to describe...

Lets say the I'd like to get the new numbers as following:

W100 on page 1

W101 on page 1, continuing on page 3

W102 on page 2, continuing on page 3

W103 on page 2, continuing on page 3

W104 on page 4

W105 on page 4

...

Now I get:

W100 on page 1

W101 on page 1, continuing on page 3 (on page 3 it asks me if I want to change W101 again, now to W104)

W102 on page 2, continuing on page 3 (on page 3 it asks me if I want to change W102 again, now to W105)

W103 on page 2, continuing on page 3 (on page 3 it asks me if I want to change W103 again, now to W107)

W107 on page 4

W108 on page 4

...

(W101-103 are not used anymore)

Is there any chance to correct this without to much work?

Thanks

Ursicin Caminada wrote:

As long no wires start on one page and continue on another everything works great, but as soon the wires go to another page I get problems.

[...]

Is there any chance to correct this without to much work?

I was afraid something like that might happen.  I think the answer will be to add each name to a list of the old names that we are going to change.  If we find the name again on a later page, we should ignore it.  This will apply to the N$xx nets as well...

Hi Doug,

Sorry, I was a bit busy with other projects during the last 2 Weeks. This weekend I finally tried a little bit around on that again.

As said before, I don't really know much about programming scripts, so if something works it is more or less accidentally ;-) Anyway, so far I have renamed all N$xx, and all WXXX in the higher range (W5xx-W9xx) with a combination of sed, your script and the c++ programm mentioned earlier in this thread (to export, rename manually and reimport).
So far I am a big step further.

Unfortunately I still don't get how to change the W1xx so they will start with W100 and continue one after the other, especially the problem that it renames the wire again if it is on more than one page is the biggest concern I have.

 

I was afraid something like that might happen.  I think the answer will be to add each name to a list of the old names that we are going to change.  If we find the name again on a later page, we should ignore it.

Do you have any piece of script doing that?

Thx a lot

Ursicin

I have been busy with other things too.  My son competed in a track meet and then he was home from college for spring break.  (He was third place in discus and hammer and fourth place in shotput.  It was only the second time he has competed at the college level.  I'm very proud!)

I should have time in the next days to look at that script again.  I will let you know what I come up with...