Carbide Create embeds the source file name in the generated gcode.
It seems that when the c2d filename is using UTF characters the embedded string in the g-code is UTF as well.
The file is at that point unusable by Carbide Motion as it fails when parsing the nc file.
I’m afraid that Carbide Create isn’t properly internationalized. It can’t use commas as a decimal separator, and accents in tool or group names cause the same sort of problem you’re seeing here.
Please limit yourself to 7-bit ASCII when naming files, tools, or groups. Even then, don’t use special characters such as apostrophes.
This topic was automatically closed after 30 days. New replies are no longer allowed.