Print from SD card using Polygonhell's firmware

[dth2m5]

I have upgraded to Poly's .82.2 firmware.

The printer does not recognize any of my *.gcode files, but it recognizes my *.stl files; this proves that the soldering/wiring works as intended.

I have tried many different naming conventions and slicers.

I have not modified the firmware settings in anyway, except for calibration. I believe the issue to reside within the firmware calibration, but I do not know how to fix it.

Any thoughts?

[Eaglezsoar]

I have upgraded to Poly's .82.2 firmware.

The printer does not recognize any of my *.gcode files, but it recognizes my *.stl files; this proves that the soldering/wiring works as intended.

I have tried many different naming conventions and slicers.

I have not modified the firmware settings in anyway, except for calibration. I believe the issue to reside within the firmware calibration, but I do not know how to fix it.

Any thoughts?

I'm confused. The only thing that can recognize the .stl files is the slicer. The slicer simply creates the gcode for the printer to use. How can you say that the printer
can recognize .stl files? The computer driving the printer or the SD card interface processes the gcode generated by the slicer and then controls the printer. Your statement
that the printer recognizes .stl files thus proving that the soldering/wiring works as intended makes no sense to me. You need to better understand that the .stl files have nothing
the printer can use until they are sliced and converted to gcode. If your printer does not recognize gcode files then the interface between the computer or SD card to the printer has
major problems. Perhaps you can rewrite what you are actually experiencing. We can help you but you need to better express what the actual problems are. Think about what I have
said then try to reword your statement of problems and then send us another report on what is happening.

[lordbinky]

When you say the printer does not recognize any of your *.gcode, you are remembering to change the filename to *.gco and NOT leaving it as *.gcode correct?

[dth2m5]

Thanks, Blinky.

I was not modifying the filename to *.gco. Bah. I'm an idiot.

[Eaglezsoar]

I apologize dth2m5, I did not understand what you meant.
Just an error in communication. Thank you lordbinky for understanding what he meant.

[lordbinky]

It was all a guess lol. When he said he could see a .stl but then spoke of gcode without stating .gco , I just thought that the 3 letter filetype limit was being overlooked.

[dsnettleton]

I always use the file extension to specify what type of plastic I've sliced the object for. So instead of *.gco, I have *.PLA and *.ABS. Really handy if you like to work with multiple types of filament.

[krak]

I always use the file extension to specify what type of plastic I've sliced the object for. So instead of *.gco, I have *.PLA and *.ABS. Really handy if you like to work with multiple types of filament.

Are you saying that you have setup your printer to accept .PLA and .ABS file extensions as well as .GCO?

[dsnettleton]

Most operating systems do not accept the file extensions as canonical. Windows is the exception rather than the rule. In other words, the firmware doesn't care whether the file extension is .GCO or .PLA or .MP3. It's smart enough to take a file with gcode in it and run the gcode, whatever I want to call the file. So there's no extra actual required. You can just change your filenames.