You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling the option for Prioritizing GCode Settings, the printer ignores any gcode commands for hotend or bed temps, and instead forces everything to 230C and 30C respectfully.
The printer also ignores its own filament settings as well. You can have set 280C and 100C, and it will still only pre-heat to 230C and 30C.
The work-around is set your filament/bed temps in the printer first. Then, print and during the Pre-Heating (where it shows 230C/30C), press the "X" at the upper-right-hand corner, then press PAUSE print, and then immediately RESUME print. The PreHeating will be fixed, and the Printer's filament settings will be used.
However, the gcode's filament/bed settings was always ignored even after the work-around.
The text was updated successfully, but these errors were encountered:
eduncan911
changed the title
v3.0_R02.12.10 - "Prioritize GCode Settings" forces hotend/bed to 230C/30C at all times
v3.0_R02.12.10 - "Prioritize GCode Settings" Pre-Heats and Prints hotend/bed set to 230C/30C
Oct 24, 2022
When enabling the option for Prioritizing GCode Settings, the printer ignores any gcode commands for hotend or bed temps, and instead forces everything to 230C and 30C respectfully.
The printer also ignores its own filament settings as well. You can have set 280C and 100C, and it will still only pre-heat to 230C and 30C.
The work-around is set your filament/bed temps in the printer first. Then, print and during the Pre-Heating (where it shows 230C/30C), press the "X" at the upper-right-hand corner, then press PAUSE print, and then immediately RESUME print. The PreHeating will be fixed, and the Printer's filament settings will be used.
However, the gcode's filament/bed settings was always ignored even after the work-around.
The text was updated successfully, but these errors were encountered: