Based on what I can tell from the machine start G-code, the only way you’d be getting different temperatures is if the first layer temperature was set to 250.
Sure, that’s also what I assumed, but it isn’t:
Merci pour ce retour Zoe, en attente d’un correctif pour cela ! Merci a l’equipe Snapmaker pour cela !
1 Like
Merci à l’equipe Snapmaker de résoudre ce petit probleme d’affichage sur l’écran de l’imprimante, pour le reste pour le moment tout fonctionne dans Orca !
Can you post your G-code file? Seeing the heating command in context may help in identifying where in the settings it’s being defined.
ring_2_PLA_0.4_T=200°C_B=60°C_0.2mm.gcode|attachment (571.7 KB)
Here the G-code file. Thank you for having a look 
It is indeed in the Machine G-code
If you need to, just lower 250 which will be the cap for this nozzle flush temp
I’m trying this out and printing this model. https://makerworld.com/en/models/398058, imported the model, added two tabs for adhesion for the wings and adjusted the printing temperature based on the material. However, it seems the hotend started digging into the model since the second layer. I checked the gcode, it seems to be correct Z height: first layer .3, second layer .5, third layer .7 etc.
Not sure what is lowering the Z height
It even get into a point that the head is to low, that right nozzle is dragging on the bed (means the left nozzle has been pressed down). The result could be worse if my kids didn’t tell me.
I tried loading the gcode into luban, and luban stopped after machine start up gcode.
I need more time to troubleshoot this, which I don’t have right now, so reverting back to Cura. However, uploading the gcode here if someone can take a look: https://drive.google.com/file/d/17DOaLKsPItMKounVGzNqkSe07fqm0VWX/view?usp=drive_link
It is for Snampaker 2.0 AT350 with bracing and quick swap
You need to grant public access to that file if you want anyone to read it.
Thanks for letting me know, fixed it.
Can you post the project 3MF file saved from Orca? I want to load it up and compare it to my typical G-code, which correctly sets temperature in the same location where yours is being set to 250.
Here you go. ixpatch_charizard_v3.3mf - Google Drive
As I stated earlier, it is written in the machine start g-code, so it could be you have an older version of the machine definition?
Also that is just set to 250 shortly for the flush, which then quickly set to the correct first layer printing temp
Are you using regular Orca or the Snapmaker Orca beta? There’s a difference in the starting G-code.
My projects (unmodified from the Snapmaker Orca beta):
; flush initial nozzle
T[initial_extruder]
M104 S{nozzle_temperature_initial_layer[(initial_extruder % 2 == 0 ? min(initial_extruder + initial_extruder, 63) : max(initial_extruder - (1-initial_extruder), 0))]}
Your project:
; flush initial nozzle
T[initial_extruder]
M104 S{max(250, min(290, nozzle_temperature_initial_layer[(initial_extruder % 2 == 0 ? min(initial_extruder + initial_extruder, 63) : max(initial_extruder - (1-initial_extruder), 0))] + 15))}; common flush temp
It’s the “max(250, min(290…+15” portion of your starting G-code that’s causing the problem.
machines are different, yours is Artisan and ours are A350
And it is not culprit of the issue I have, it is @makuris 's
I used Snapmaker Orca Slicer on Linux and I have also the max(250 … start G-code. Is this something old that is only in the Linux-Version still present? I will try the code you posted - I assume this will fix my issues. Thank you!
It all boil down to where this gcode comes from which is 3dp-configs/OrcaSlicer/Snapmaker/machine/fdm_a350.json at main · macdylan/3dp-configs · GitHub
where the author wrote in readme:
进行两段不同温度的耗材冲刷，确保喷嘴更加干净。总共大约使用 4-8cm 的耗材，没有太多的浪费，我认为可靠的打印是更重要的。如果你不想有任何浪费，可以在 gcode 中使用
{if 0 == 1}...{endif}来关闭这段逻辑
which means he added it on purpose but not necessary, so if it is causing issue for you, go ahead
Nonetheless, any expression that starts with “max(250” is guaranteed to have a result of 250 or more.
I encountered a weird bug with the orca setup on my Artisan: The nozzle scratches along the clamps of the buildplate. I noticed that there is a boundary check involved in the GCODE startup which is turned off as its not recommended if there are any clamps.
G28
{if 0==1} ; boundary check(for dual/quick swap kit), not recommanded if there are any clamps
G0 X0
G0 Z0.2 F960.0
G0 Y0 F6840.0
G0 X400
G0 Y400
G0 X0
G0 Y0
{endif}
Sadly i noticed the bug too late as both of my nozzles are damaged now. Is this a known issue did anyone else encounter this?
How do I fix this ?
Which printer? The start G-code for my Artisan doesn’t cause this issue. Maybe look at it.
@Snapmaker Support: Please change the initial priming to be more similar to the default Orca priming. At the very least, change the current priming to prime both directions. I find that a single trace doesn’t get the filament all the way to the end of the nozzle.