Fusion 360 GCode Post Filename Convention and Discovery

I have sort of standardized my filenames to give me the necessary information to perform a set-up at the machine. For example:

FancySignProfile_12inx15inx1in_FLB_1-4Jenny

ProgramName_StockSize_OriginLocation_BitSize

Sometimes on accident I use a “/” instead of a “-” when designating bit size or material size. After one of the recent Fusion updates this now creates folders! For example:

Folder_Test/0125DN/Actual_filename

Will create two nested folders with the Actual_filename.NC file in the last one.

image

I haven’t decided yet whether this discovery will cause me to change my naming convention. What are your thoughts?

I always use this convension wirth Fusion 360

FancySignProfile_12inx15inx1in_FLB_.25Jenny

Using decimal for the bit size has not caused any trouble.

1 Like