use of user defined settings in File menu

[GlennM.MCAM]

Hello,

what and how is the use of the user defined settings which you can find under the "File" menu?

I know what user defined settings are but I don't know how to use these as below.

Glenn

[5axes · Accepted solution]

---

what and how is the use of the user defined settings which you can find under the "File" menu?

I know what user defined settings are but I don't know how to use these as below.

---

For any case where you need to store in your project customized information.  Could be for data management, Golbal variable for toolpath calculation like  Gap used for an Electrod : Have a look to the following post.

https://forums.autodesk.com/t5/powermill-forum/electrode-extra-overburn-thickness-in-same-project-ma...

Internal value in a macro to store temporary data , like the last toolpath modified by a value , a general information about the current process , the Filename  you need to use to generate your NC program. A value used by the postprocessor to set up some special function ( The weight of your part to tune the Dynamic setting on a 5 axis machine )

etc. etc

[Anonymous]

I tend to use mine as a way to setup all of my "universal" references that the rest of my macros pull from. This way it keeps a record of what they are for that specific job and I can export them later, add stuff, remove stuff etc.

It's a very, very handy tool.

[GlennM.MCAM]

So the variables (name) that are in this list can be used in a macro like this?

PRINT $variable

[Anonymous]

That's the general usage yes. 

It's basically just user variables you can squirrel away until you need them again or export them to a database.

They're sort of obnoxious to set via macro but you get used to it.

Another thing to note is that they are dynamic. If it is used elsewhere it will change accordingly so play with care if you have them doing calculations. eg ; If you use a value in there to set the RPM/Feed of tools and you change it, the tools will shift accordingly. 

[5axes]

You can use :

PRINT $variable

but I prefer to use :

PRINT $Project.variable

It's on my point of view, much more clear and easy to understand.