Default User Settings Export

Default User Settings Export

jodyF8L9L
Enthusiast Enthusiast
335 Views
7 Replies
Message 1 of 8

Default User Settings Export

jodyF8L9L
Enthusiast
Enthusiast

Hello,

 

I read the following post regarding exporting default settings and it was helpful knowing that my defaults can be exported into an editable xml file and then reimported.

 

https://forums.autodesk.com/t5/fusion-manufacture-forum/user-default-settings-dosen-t-update-between...

 

However, when I exported my settings, the file seemed very...lacking. It contained only 200 something lines of xml code and only about 8 strategy combinations. Attached is the file.

 

My question: is it possible to export EVERYTHING, and if not, what would be the syntax for differentiating between...for example..."turingProfileFinish" for face, inside, and/or outside profiles? Are there any guides for such a thing?

 

jodyF8L9L_0-1767899112861.png

 

 

0 Likes
336 Views
7 Replies
Replies (7)
Message 2 of 8

a.laasW8M6T
Mentor
Mentor

It used to export every parameter, but now it only exports things that were set as user defaults it seems.

 

 

 

 

Andrew Laas
Senior Machinist, Scott Automation


EESignature

0 Likes
Message 3 of 8

jodyF8L9L
Enthusiast
Enthusiast

@a.laasW8M6T that is what I was thinking, but there are also combinations of strategies that are not being exported either, such as the one I listed. For example, I probably want a 90 deg lead in/lead out on outside profile finishing, but a 0 deg lead in/lead out on a face profile finishing would probably be better. That may not be the best example because lead-in/lead-out may not be combination dependent parameter, but there are definitely combination dependent parameters such as Clearance, which I do have set as combination dependent defaults.  I would just like to be able to set those as defaults as well as be able to deploy those defaults or have a back-up of sorts programmatically with an xml file instead of having to rely on remembering which combinations of strategies I have set user defaults for.

0 Likes
Message 4 of 8

a.laasW8M6T
Mentor
Mentor

Im not really following why you want to edit the XML file. 

 

The purpose of the export is to make a backup of defaults or to transfer them to another account for example.

 

if you want different logic applied to inside or outside turning  for example then you would use expressions and save them as a user default (I have done this in quite a few cases for various aspects of toolpaths to automate stuff.)

 

https://help.autodesk.com/view/fusion360/ENU/?guid=MFG-REF-EXPRESS 

 

Andrew Laas
Senior Machinist, Scott Automation


EESignature

0 Likes
Message 5 of 8

jodyF8L9L
Enthusiast
Enthusiast

I am working on standardizing operation parameters (Fusion implementation baseline kinda stuff) and I want the xml file so I can programmatically set user defaults for operations outside of working on going through the operation itself. Just easier to mass update things like stock to leave or leads parameters. This will also serve as a new user to import (or Fusion reset) and be all set...user can just have a quick an easier way to get back up and running with all of the settings needed.

0 Likes
Message 6 of 8

a.laasW8M6T
Mentor
Mentor

Ahh yep

I get where you're going there.

 

@seth.madore any insight as to why this changed? or if it is possible to somehow export the full parameters 

Andrew Laas
Senior Machinist, Scott Automation


EESignature

0 Likes
Message 7 of 8

seth.madore
Community Manager
Community Manager

No, I don't have any insight into that. I'm not even sure who's area that might be, but I'll ask around

 

 

One option; create a toolpath, right click on the toolpath in the browser and select "save all as default". That may be enough to send everything to the XML file


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 8 of 8

jodyF8L9L
Enthusiast
Enthusiast

@seth.madore yes that's what it's looking like now...set user defaults manually, operation by operation, and export. Was just looking for that "easy" button...and more complete button I guess too. 

0 Likes