Print stops after doing custom GCODE
Hello all,
I'm trying to use PrusaSlicer for the organic supports, but I can't seem to get the print to work. I have been using Simplify3D for a long time without issue, but can't get this print to work through PrusaSlicer. When I start the print, it goes through the entire custom start g-code that I have, but stops when it gets to the point of starting the actual print. I can see in my Octoprint GCODE viewer that it goes through the wipe process at the end of custom script, then it pauses at the command
M109 S212 ; set temperature and wait for it to be reached
You can download the GCODE file HERE. This specific file doesn't have any supports that are needed, but I'm trying this one as a test print using PrusaSlicer. I have another file that needs supports that I will print later after I get this going.
Here is the info on my printer --
Tevo Tornado running Marlin 2.0.9.3
MicroSwiss all metal hotend
Bondtech extruder (Bowden)
BLTouch for auto bed leveling
OctoPrint for print control on a Raspberry Pi
Does anyone have any idea why it would be pausing at this point? The printer is already warmed up to temp before I even start the print, so I'm not sure why it's pausing at the set temp command. The OctoPrint viewer shows the temps are at or above the printing temp when it pauses as well. I have compared the GCODE files from Simplify3D that I know works and the one from PrusaSlicer and the only difference is that M109 command in the PrusaSlicer GCODE.
RE: Print stops after doing custom GCODE
Well, I honestly don't know why, but I added the following GCODE to the filament start script and it's working now.
M109 S212;
Hopefully it keeps working, these new features are super enticing.
RE: Print stops after doing custom GCODE
UPDATE 2
Well, I think I figured it out. The change I made above only worked one time.... and the printer stopped extruding material part way through the print, and I narrowed that down to it having an issue during a bridge (?maybe), and I found other people that had a similar issue and it looked like it had to do with the extruder relative position not being reset so I had to add G92 E0 in the layer start script section. Not sure if that's right or not, but we'll find out with the current print job.
How I fixed the other issue was disabling the option "Emit temperature commands automatically:" since I am doing that in the filament start GCODE section.