How to Fix the Printing File (Gcode) Damaged Alert
AnkerMake studio can import STL files (BINARY & ASCII) and OBJ files, and generate Gcode files for the M5 to recognize and print by slicing and planning the printing path.
Cause of Error:
When previewing or printing the workpiece Gcode, if the Gcode is damaged, a pop-up window, as shown in the figure below, will appear. There may be several reasons for this:
Print Gcode file corruption, such as incomplete copy.
The Gcode file is not read completely, such as when printing with a USB flash drive, it is pulled out without entering the printing interface.
Solution:
Re-slice the Workpiece:
If the Gcode file is damaged, re-slice the workpiece and import it again for printing.
Proper Use of USB Flash Drive:
If you use a USB flash drive to print the workpiece, ensure the print job starts before unplugging the USB flash drive.
If the problem still cannot be resolved, please contact us for further assistance.