Return to Answer

###Avoid naming .gcode files with non-ASCII characters ####(this includes EASCII) I know of no firmware on a printer that can handle files that have characters not present in the set of 95 non-control American Standard Code for Information Interchange characters by default. Marlin, for example, can't process the characters ä ö ü & € as these all are missing in the ASCII.

###Avoid having more than one . Nowadays the . is no longer a fully reserved character in file names, so a file can be named 0.5mm Gauge Block.stl on Windows without problems.

Ultimaker Cura will cut the name at the . before the extension when generating the .gcode. This is mainly done to prevent tons of errors that could crop up in firmware that might not be able to deal with it. Remember that this behavior can lead to overwriting files - our 0.5mm Gauge Block.stl would generate 0.gcode, as would 0.1.5 Penholder.stl (that follows a version naming convention).

###Avoid reserved characters Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.

Avoid naming .gcode files with non-ASCII characters

(this includes EASCII)

I know of no firmware on a printer that can handle files that have characters not present in the set of 95 non-control American Standard Code for Information Interchange characters by default. Marlin, for example, can't process the characters ä ö ü & € as these all are missing in the ASCII.

Avoid having more than one .

Nowadays the . is no longer a fully reserved character in file names, so a file can be named 0.5mm Gauge Block.stl on Windows without problems.

Ultimaker Cura will cut the name at the . before the extension when generating the .gcode. This is mainly done to prevent tons of errors that could crop up in firmware that might not be able to deal with it. Remember that this behavior can lead to overwriting files - our 0.5mm Gauge Block.stl would generate 0.gcode, as would 0.1.5 Penholder.stl (that follows a version naming convention).

Avoid reserved characters

Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.

Avoid naming .gcode files with non-ASCII characters (this includes EASCII) and reserved characters

Nowadays the . is no longer a reserved character in file names, so a file can be named 0.5mm Gauge Block.stl on windows without problems, but Ultimaker Cura will cut the name if there is a . earlier to the end .gcode, preventing tons of errors that could crop up in the firmware but remember that this also can lead to overwriting files - our Gauge Block would generate 0.gcode.

However, only few firmware on the printer can handle files that have characters not present in the 95 American Standard Code for Information Interchange characters. Marlin, for example, can't process ä ö ü & € as these all are missing in the ASCII.

Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.

###Avoid naming .gcode files with non-ASCII characters ####(this includes EASCII) I know of no firmware on a printer that can handle files that have characters not present in the set of 95 non-control American Standard Code for Information Interchange characters by default. Marlin, for example, can't process the characters ä ö ü & € as these all are missing in the ASCII.

###Avoid having more than one . Nowadays the . is no longer a fully reserved character in file names, so a file can be named 0.5mm Gauge Block.stl on Windows without problems.

Ultimaker Cura will cut the name at the . before the extension when generating the .gcode. This is mainly done to prevent tons of errors that could crop up in firmware that might not be able to deal with it. Remember that this behavior can lead to overwriting files - our 0.5mm Gauge Block.stl would generate 0.gcode, as would 0.1.5 Penholder.stl (that follows a version naming convention).

###Avoid reserved characters Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.

Avoid naming .gcode files with non-ASCII characters (this includesExtended ASCII Codes)

Ultimaker Cura manages to cut the name if there is a dot earlier to the end .gcode, preventing tons of errors but also can lead to overwriting files.

However, only few firmware on the printer can handle files that have characters not present in the 95 American Standard Code for Information Interchange characters. Marlin, for example, can't process ä ö ü & € as these all are missing in the ASCII.

Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.

Avoid naming .gcode files with non-ASCII characters (this includes EASCII) and reserved characters

Nowadays the . is no longer a reserved character in file names, so a file can be named 0.5mm Gauge Block.stl on windows without problems, but Ultimaker Cura will cut the name if there is a . earlier to the end .gcode, preventing tons of errors that could crop up in the firmware but remember that this also can lead to overwriting files - our Gauge Block would generate 0.gcode.

However, only few firmware on the printer can handle files that have characters not present in the 95 American Standard Code for Information Interchange characters. Marlin, for example, can't process ä ö ü & € as these all are missing in the ASCII.

Also note that some characters are reserved in file naming and will lead to other errors (mainly when trying to create the files in the first place), including, but not limited to, / \ : ? *.