Simplify3d 4.0.1 gcode causing Duet to mess up
-
M190 should be 80 and M109 should be 200. As it is, you start heating the hot end to 200 with M104 but then change it to 80 with M109, and you start heating the bed to 80 with M140 but then change it to 200 with M190.
Edit. Heater 0 is the bed, hence the error when you try to heat it 200 deg C because your confi.fg has probably got a much lower maximum limit defined by M143 (on firmware 1.17 onwards, the default is 125 deg C).
-
@deckingman Thanks. That is one of those, "was I even thinking" moments. The idea is to get both the bed and hotend heating at the same time. After switching the temps, it is working now. These are being set by variables in the script and I just had the wrong ones in the second set. Thanks.
And that first T0 was left in after a test I did and shouldn't have been in there. Didn't make a difference if it was there or not.
-
No worries. We all have those moments
. BTW you can just take out the M104 and M140 commands - there is no point having them if they are immediately followed by M109 and M190. For info, although M104 will work it's been deprecated and we ought to be using G10 and "T" commands. I'd leave the T0 command in there unless you have a T0 in your config.g file. The reason being that if you try to heat the hot end with no tool selected, you'll get an error message.Hope you don't mind me pointing this out but this is little strange:
M106 S255
G4 P500
M106 S0Turn fan on full, wait half a second then turn it off ?
-
@deckingman The reason for the temperature combination is to start both the hotend and bed heating at the same time. So set and return. Then wait for the bed to heat up, slower of the two, then wait for the hotend. I picked this up from the Prusa Slic3r settings. Cuts down on the wait time for heating.
As for the fan blip, yeah, that is strange, but is generated by the slicer and not my code.
-
I think it's to ensure the fan will turn, even when sending a low PWM...
Frédéric
-
@elmoc said in Simplify3d 4.0.1 gcode causing Duet to mess up:
@deckingman The reason for the temperature combination is to start both the hotend and bed heating at the same time. So set and return. Then wait for the bed to heat up, slower of the two, then wait for the hotend. ...........
Ahh yes that's cool. My turn for "one of those moments" as I actually do the same thing, (well almost). I just start the bed heating, then do all the other stuff. The hot end gets heated as part of my home all routine which gets called form the start gcode. So we both achieve the same objective, just by slightly different routes.
-
@fma said in Simplify3d 4.0.1 gcode causing Duet to mess up:
I think it's to ensure the fan will turn, even when sending a low PWM...
Yes, that is what the blipping is for. But in this case, it is to make sure the fan is off so just setting it to 0 wouldn't have that problem. Doesn't really hurt anything so not too concerned about it.
-
@ElmoC, I have this start gcode for Simplify, hope it work for you
T0
M140 S[bed0_temperature] ; set bed temp no wait
M104 S[extruder0_temperature] ; set extruder temp no wait
M106 S0
G28 ; home all axes
M116 ; wait all temps
M98 P/macros/CleanNozzle ; clean the nozzle -
@demonio669 said in Simplify3d 4.0.1 gcode causing Duet to mess up:
@ElmoC, I have this start gcode for Simplify, hope it work for you
T0
M140 S[bed0_temperature] ; set bed temp no wait
M104 S[extruder0_temperature] ; set extruder temp no wait
M106 S0
G28 ; home all axes
M116 ; wait all temps
M98 P/macros/CleanNozzle ; clean the nozzleNot familiar with the M116 command. Will look into that. Thanks.
-
https://duet3d.dozuki.com/Wiki/Gcode#Section_M116_Wait
It will wait to all temps to reach the configured value . when all temps reach the configured temp continues
-
@demonio669 looked it up on the wiki gcode page and see it's not supported in Marlin. But will probably update my Duet scripts to use it.
