G.code analysis

Scanning the .gcode file is a feature built into the printer that allows you to check the print file before the print job starts. This analysis is used to identify potential problems or errors in the gcode file in advance, which could cause difficulties when printing.

The outcome of the .gcode analysis can be of two types:

  • SUCCESS: This means that no writing errors or problems were detected in the gcode file, and printing can start automatically without further hindrance.
  • FAILURE: If it fails, the printer detects errors in the gcode file and communicates it. In this situation, the printer will not start printing until the problem is resolved.

If this is not the case, there are several checks and actions to take:

SAVE THE GCODE AGAIN: First of all, try saving the gcode file to your computer’s memory again. After that, copy it to the external disk or to the printer’s memory (if possible the connection remotely via Octoprint).

SAFE DISK REMOVAL: Be sure to perform a “safe disk removal” before disconnecting the SD card or USB stick from your PC. This prevents damage to your data and storage device.

CHECKING THE OPERATION OF THE EXTERNAL DISK: Make sure that the SD card or USB stick is functional. Check that there are no hardware issues that could affect the reading of the gcode file.

EXTERNAL DRIVE FORMATTING: Check that your SD card or USB stick is formatted as FAT-32 or ExFAT, as these formats are commonly supported by most 3D printers. Make sure you don’t use non-standard formatting or NTFS.

VERIFYING GCODE START AND END SCRIPTS: Take a look at the “start gcode” and “end script” scripts in your configuration file. There may be issues or errors within these scripts that affect the parsing of the gcode file.