Snapmaker 2.0 Doesn't honor initial temp settings

Interesting. Any input @Rainie ?

I checked all printing methods (USB, WiFi transfer and print from Luban) and only with the print via Luban instructions the printer is changing the temperature settings. The other two methods ignore it. The M104 lines are in the gcode

So my conclusion is, that the bug is in the Snapmaker 2 firmware. Maybe something with the priority of the manual setting?

Because the TouchScreen is effectively controlling the flow of code to the controller, perhaps it’s a timing issue for when it shows the temperature change. It sees the future temperature change in the code going to the controller and displays it but the controller hasn’t actually executed that code yet therefore you don’t get to see it display the first temp. I’m just making a guess at what’s going on. I’ve got some experiments in mind to try.

I’ve noticed a related issue. When it detect out-of-filament, the Nozzle temp goes to 200 for the rest of the print.

After further experiments and watching I believe the auto calibrate routine turns off or rather suspends all heating while the routine runs. It could be that the bed heating elements interfere with the proximity sensor, maybe the filament heater too.

I find with mine it ignores an M190 command to wait for temperature and just continues on with homing and probing. This happens if I manually insert an M190 before G28 or if it is present in a sliced file from PrusaSlicer as well. The fact that it ignores the heat commands seems to be problematic because my bed is changing shape when heated or the bed mesh is just not working. First layers are all over the place.

It could be that the TouchScreen (TS) is parsing the file and looking ahead so to speak and taking action. @parachvte? How about telling us what’s going on here?

I made a more detailed check of the our problem:

I set the temperatures for initial layer at 210°C, the print temperature at 200°C and then I modified the temperature from the comment / header in the gcode file (see screen shot below).

Then I loaded it on the Snapmaker and what do we see? 205°C (I forgot to load the filament and he even jumped back to 205°C after the loading) (see pics below)

So the Snapmaker reads the headerinfo and ignores all M104 and M190 orders.

1 Like

The touchscreen allows the temperature adjustment during printing when parsing the gcode, and the priority of the temperature set in the gcode was overwritten.
So the temp value of 70 degrees may be covered by the value of 50 degrees.
This is a touchscreen firmware issue and will be fixed in the next version.

You can adjust the temperature by sliding left in the touchscreen to increase the working temp for the initial layer if the temp is not high enough.

Sorry for the inconvenience.


@SchnabsiX You are very close :wink:. Touchscreen ignores the first M104/M109/M140/M190, instead uses the header info (we will correct the header info to reflect the initial layer temperature).

By doing so, we allow user to modify initial temperatures before printing. And later M104/M109/M140/M190 commands are still executed since we may have different temperatures for different layers. Align with this, if you modify temperature during printing, the temperature will be changed immediately, but later when another M104/M109/M140/M190 command comes it will be overwritten by the command.

There are two kinds of needs to adjust temperature, one is to change temperature immediately and no affect later temperature commands, another is to change temperature and overwrite all later temperature commands. We implemented the first one, we will consider if both methods can be presented in TS, in a proper way.


Sorry to be late to the game on this but I’m also noticing the same issue with my SnapMaker A250 ignoring both initial temp and final layer temp settings I set in Luban and only displays the “default” print temperature on the touchscreen. I’m using the SnapMaker2 Luban 3.5.0 and have firmware: “Snapmaker2_V1.8.0.0_20200507” installed.

Try the last Luban (3.7) and Firmware(1.9) from the forum and check again

Tried with Firmware 1.9.0 and Luban 3.5.0 problem still exists: Set First Printing Temp to 230 and Printing Temp to 225. Printer only heated nozzle to 225 before it started printing. Unable to test with Luban 3.7.0 as experiencing issues after installation (I started a separate topic about that).

please upgrade to 1.10.0 firmware. Snapmaker 2.0 Firmware Updates and Downloads

If the issue still exists, please share your gcode. Thanks

When to add language types to touch screen

We are working on it. We recently just added Japanese to the touchscreen :grinning:

1 Like

I can confirm this issue still exists in the latest firmware 1.10.1

I didn’t notice at first what the issue was for my heat profile tower, but the screen shows the current and target temp always as the highest in the file which also happens to be the last temp it is set to so it is hard to say which it is choosing.

@staff please assist/ resolve

See attached for 2 gcode files. Scratch that. one was too big.
tour_de_chauffe_v2.gcode (756.1 KB)

1 Like

I can also confirm this issue still exists in latest firmware
Sadly I cant upload the gcode being new…

Can you please please fix this @staff

Hi all. I have observed the same issue - latest versions of Luban (3.12.3) AND fimware (1.10.1) are installed. I did a li’l experiment and deleted the line in the header file that sets the initial hot end temp. Hmmm, the machine didn’t seem to like that and I ended up having to cycle the power because it appeared to go unresponsive.

So, I deleted the entire header. All of it. Not commented out. Deleted.

The machine is liking that much better, although you of course don’t get the little picture of the job on the touchscreen, but, meh. Im building a PETG temp tower as I type, so we’re starting at a heady 265c, but it is getting to 265 no issue. When the temps start to fall (and I have manually inserted M109 so it waits) I’m hoping it will behave. I think it should as it parsed the 161,500 lines of code without throwing any errors!

I’ll report back.


1 Like

…Aaaaaaaanndd it followed the G-code perfectly. Makes me a happy chappie.