font size in Rich Auto pad

[irishwoodworker]

Is there any way to change this so I can see more letters of the file names?

Thanks

[uzumati]

That is a little annoying, I stated naming my tool paths so I can tell what they are in the first 5 letters.

[irishwoodworker]

in a $7,000 tool, this is pretty disappointing. Looks like 90s technology.

[stevem]

It's not hard to simply name your your tool path's, so it hasn't bothered me that much.
The Rich Auto controller is used in many machine applications. If it was a big problem, the manufacturer would have probable mads some changes to the screen. I do agree that it is very cryptic in it's design.

[lynkspyder]

My tool paths are generally tied to a specific tool. I put them in a folder on a thumb drive that relates to the name of the project. The following is an example of the naming structure:
EM250 = 1/4" End Mill
BM500 = 1/2" Ball Nose
TB125 = 1/8" Tapered Ball Nose
OM188 = 3/16" Spiral O Flute

You get the point.

[irishwoodworker]

Thanks, all. I think lynkspyder's model will work for me.
The interface takes me back to the DOS days!!

[dickdelmi]

It seems to me we are talking about a Vectric problem and not a machine problem.  
On the tool paths screen I put the tool paths in the order I want to use them and then print out a job sheet which lists the bits and operating parameters in the order of usage.  The machine then stops and raises after each tool path is complete and it is then a simple matter to change bits and continue with the job.  Don't forget to re-zero the Z axis.
For continuous operation with different tools you need a tool changer machine.

[grg]

May 24, 2018 21:21:19 GMT -5 lynkspyder said:

My tool paths are generally tied to a specific tool. I put them in a folder on a thumb drive that relates to the name of the project. The following is an example of the naming structure:
EM250 = 1/4" End Mill
BM500 = 1/2" Ball Nose
TB125 = 1/8" Tapered Ball Nose
OM188 = 3/16" Spiral O Flute

You get the point

I do the same but add a letter designation to the front so I get the right program order on the controller and it's clear without looking at the job sheet

AFEM250
BBEM125

...and so on.

[Deleted]

I use a number prefix to get my files ordered and all my tool and path descriptions are in comments in the G-code file because I've made my own post processors for several machines so they have lots of useful information that I can read right within the file. Details include: filename, creation date, what post processor I used as a sanity check, material size and origin in relative and absolute terms, home position, safe Z, project notes, toolpath names and notes, each bit name and notes, and each tool path has a header that details the path, notes, tool and notes again.

I also have made a Notepad++ language definition configuration to interpret the G-code and highlight various language features as well as invalid G and M codes for a particular machine.

Since I do a lot of feedthrough work that is horizontally oriented I also make a post processor that rotates the orientation of the machine so instead of 0,0 being in the near left corner and feedthrough in Y, it makes it "look" the same but from the perspective of standing on the right side of the machine and facing it. That is, in this new orientation and facing, 0,0 is still on your near left but you then feedthrough in X. This allows me to take advantage of the computer monitor being wider than taller and being able to see the output how it will be viewed.

I also use a job sheet, the primary reason I upgraded to Pro.