PrusaSlicer 2.2.0 faulty GCode
Has anyone else tried exporting a PLA GCode, only for the printer to set the extruder nozzle temperature at 170C? I have tried setting the temperature manually under Filament Settings, but it makes no difference. The GCode still tells the printer to extrude at 170C, which obviously will not work for PLA. Old GCodes on the same card still work, so it is the GCode itself that is not correct, and not how the printer is reading the GCode. I currently have the PLA set as Prusament PLA, but that should not make any difference, especially if the Filament settings specify 215C.
RE: PrusaSlicer 2.2.0 faulty GCode
Do you have a mini ? Or are you using start gcode by Bob ? It’s now becoming more common for a 2 stage start, where the extruder heats to 170 as that’s soft enough for filament not to damage the bed but not hot enough to ooze, and then waits , does the mesh levelling at the intermediate temperature and then when levelled it then proceeds to warm to the full temperature.
We have seen several people complain that the temp doesn’t go to set value so they stop the print thinking somethings wrong when it’s actually what the printer has been told to do.
RE: PrusaSlicer 2.2.0 faulty GCode
Oops - i3MK3S. I'll leave it to run next time, and see if it works. Must admit, I have stopped the print, rather than risk damaging the printer. Thanks!
RE: PrusaSlicer 2.2.0 faulty GCode
Oops - i3MK3S. I'll leave it to run next time, and see if it works. Must admit, I have stopped the print, rather than risk damaging the printer. Thanks!
The PINDA warmup can take a bit of time on the 1st print on a cold morning. Give it a few minutes and observe. If the nozzle moves down close to the bed and pauses, it's probably doing the warmup. You can monitor the PINDA temp from the front menu by selecting Support->Temperatures. It's most likely waiting for the PINDA to hit 35C. Unfortunately, the current Prusa Mk3 firmware doesn't allow updating the display with helpful messages mid-print, so there's no way to notify the user of what's going on.
RE: PrusaSlicer 2.2.0 faulty GCode
Turns out I made a bad assumption. I am used to upgraded software retaining my preferences. Turns out that the software had reset the printer to the Mini.
Suggestion for the software team - if you are going to reset the preferences, then have the newly issued software insist on the set-up wizard!