Hi,
I'm experiencing a very weird issue I'm unable to debug. I have a relatively small print I'm trying to print to test if the alignment of the nozzles on my dual extruder is correct, and whenever I try to print it (from the sd card reader), the printer just restarts itself without any visible errors. I sliced it with Slic3r PE, and then I tried to slice it with Prusa Slicer, both versions do the same even though the gcode is definitely not the same. The print always seems to stop around the same layer (layer 15 or so, but I don't know what exact layer it is).
I also tried printing while plugged in to the computer, as I thought the logs might spit out something helpful, but it didn't show any errors before stopping the print. Instead of just restarting the machine, this caused the temperature to drop ridiculously while the computer kept trying to send gcode commands to the printer though.
I thought this might be an issue with Marlin (was running 1.1.9) but I updated to the latest bugfix-2.0 branch and it's still happening, so that doesn't seem to be it.
Any clues how I might be able to debug this?
Here is the gcode, in case anyone can spot anything weird that I can't (it won't let me attach it): [www.dropbox.com]
I'm experiencing a very weird issue I'm unable to debug. I have a relatively small print I'm trying to print to test if the alignment of the nozzles on my dual extruder is correct, and whenever I try to print it (from the sd card reader), the printer just restarts itself without any visible errors. I sliced it with Slic3r PE, and then I tried to slice it with Prusa Slicer, both versions do the same even though the gcode is definitely not the same. The print always seems to stop around the same layer (layer 15 or so, but I don't know what exact layer it is).
I also tried printing while plugged in to the computer, as I thought the logs might spit out something helpful, but it didn't show any errors before stopping the print. Instead of just restarting the machine, this caused the temperature to drop ridiculously while the computer kept trying to send gcode commands to the printer though.
I thought this might be an issue with Marlin (was running 1.1.9) but I updated to the latest bugfix-2.0 branch and it's still happening, so that doesn't seem to be it.
Any clues how I might be able to debug this?
Here is the gcode, in case anyone can spot anything weird that I can't (it won't let me attach it): [www.dropbox.com]