Snapmaker 350 and Cura Problem

Hi,
i use Cura (4.6.2) to create the G-code. I set 190 Celsius for the nozzles and 60 Celsius for the heating bed. I transfer the data via USB. I select the file and the temperature data is NOT transferred by the machine (problem 1).
I adjust the temperature data on the machine (190 Nozzle, 60 heating bed) and start printing. The Nozzle heats up to 190 °C and the heating bed to 60 °C. The bed moves back and forth and Z axis moves down to start printing. During this process, the machine changed the temperature actions to 205 Celsius (nozzle) and 70 Celsius (heating bed) (Problem 2).
Anyone have any ideas?
Greetings
Oliver

Firmware update I have done

That’s odd… Can you open the GCode in a text editor and look which Temperature commands Cura put in? My suspicion is that you set a nozzle temp for the first layer, but overlooked that Cura has different settings for the other layers. You may need to increase the visibility of options. Also, check if the fields are linked or independent (there are symbols in front that allow to change this).
Regarding Problem 1: It may well be that Cura put out GCode that is: Heat the bed to 60, wait for it to reach 60, AND THEN heat the nozzle to 190 and wait for it. That may look like Nozzle not heating up.
In the forum there was someone posting how to change this, but I decided to leave it as it is, since while the bed heats up, the nozzle will just ooze, and the nozzle then heats up very quickly.

1 Like

Thanks.

I’ll check it out. I’ll give you a feedback.

Oliver

Hi Hauke,
whatever I do, no Cura File works with the printer. With Snapmakerjs it works with the temperatures.
Greetings
Oliver

@Tharghor
the default profiles provided by SM have alot of set values that cause problems when trying to change settings. in the link below you will find more info on this as well as the cura profile i use (temp settings seem to work for me) give it a shot and let us know if your still having problems.

thanks,
-Atom

As far as I know, CURA won’t send the Gcode direct to Snapmaker2. What I do is save the Gcode to file and then load it into Luban and send it via WIFI. I also like to examine the code before loading it into LUBAN (using Notepad ++). As someone mentioned it is important to have the right profile in CURA too. Someone posted them on the forum so you can just import them.

Re problem 2, I believe the settings on the touchscreen will be overwritten by Gcode when this is encountered. Again as far as I know the touchscreen does not impose some kind of limit. For instance if you set the touchscreen to 190 temperature it does not mean that it won’t exceed that if it later encounters Gcode that instructs the nozzle to heat up more. I may be wrong and if so would love to understand this better.

Thanks for the help.
I will deal with this in the next days. I will give a feedback afterwards.

@JohnFiott you are correct cura will not send to the SM2 directly, however I do not use luban at all (as it seems like more work then just saving to a flash drive and printing from the touch screen).

Both the original SM profiles are here in the forum as well as my profile in the link above, I posted mine (one you can also just import) after some people seemed to have issues with the SM profiles doing wierd things on temp/material/layer changes.

From my understanding, you are correct. there is an initial temp (that is the one that can be modified from the touch screen) and that lives outside of the normal gcode sequence (in some sort of header from my understanding) but I’m not sure how that works with the temps written in the normal gcode sequence.