-
-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotend on at the start of printing even without being configured for it #736
Comments
I sliced your project and looked at the output gcode and there arent any extra heating commands in there that I can find. In fact theres only a single bed heating M190 command for first layer temp and I cant find one for your bed at printing temps for the other layers so I'm not sure whats going on there. One thing to investigate is the Duet Reprap implementation webpage states that the M command aer deprecated and that it should be using G10 followed by M116 to get the same effect. |
The only test I did was slicing using Prusa Slicer 2.2 and Simplify3d 4.0, and I didn't have this problem. The scripts are exactly the same, changing only the names of the hotend and bed variables. |
Super Slicer iirc has been updated to be in line with the current reprap firmware standard so theres a G10 that's been inserted at the top of the output gcode file. I think that is what is actually heating up your extruder. Basically if you dont add in suitable start gcode for your flavour then it will auto insert it. As reprap no longer uses the M109 command that you inserted in your start gcode SuSie is adding in a G10 for you. Then Susie wont add one in for you at the top and it should work like you want. Edit - just had a go with that and it doesnt remove the one at the top of the output gcode. Looks like its being added as a standby temp |
The only work around I can come up with is to add another at the top that immediate sets the extruder temps to zero before starting to heat the bed and then heating the extruder like so - G10 P0 S0 R0 ; to counter the one inserted at the start of gcode generation for some reason. M190 S[first_layer_bed_temperature] ; wait for bed temperature G10 P0 S[first_layer_temperature] R[first_layer_temperature] G1 X0 Y0 Z0 F1000.0 ; move out of print volume |
Maybe I have to remove the SXX part on these lines. |
Your suggestion does, until the problem is resolved. Thank you for your attention to the matter! |
I understand that as "yes that's the fix i requested" and will push it in the next release |
That's right, thank you very much! |
It is better not to include any if there is one "G10 P" in the start G-Code. Also for a toolchanger the code below works better as you would want to set the temperature on the extruder actually used and not just the first one. |
Version
Version: 2.3.55.2
Build: SuperSlicer_2.3.55.2
Operating system type + version
Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 18363), 64-bit edition
Total RAM size [MB]: 8,458MB
3D printer brand / version + firmware version (if known)
Duet 2 wifi 1.04 - RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
Behavior
This is my start gcode script:
M190 S{first_layer_bed_temperature[0]} ; wait for bed temperature
G28
G1 X0 Y0 Z2 F1000
M400
M109 S[first_layer_temperature] ; wait for nozzle temperature
G1 X0 Y0 Z0 F1000.0 ; move out of print volume
G1 Y10 E9 F500.0 ; start purge
G1 Y50 E9 F500.0 ; finish purge line
I don't know what's going on, but the hotend has been warming up since the beginning, along with the table. I don't know if there is any option that I enabled wrong. The hotend should only heat up after the table is hot and after the G28.
Project File (.3MF) where problem occurs
AnevoMGN9H2.zip
The text was updated successfully, but these errors were encountered: