I usually preheat the nozzle and bed before I print. I'm guessing that you don't preheat your nozzle and let the gcode do it for you. The printer will wait for the bed to heat up to 60 with M190 S60. But the G10 S205 after that won't be waited for. You can edit the gcode and add M116 after G10 S205 and it should wait for 205C to be reached before it continues. I'm sure there's a better way around it.
Latest posts made by GeoffVR6
-
RE: Help Orca slicer : doesn't set extruder temperature
-
RE: BLTouch Configuration
I'm not sure your endstop setting is correct.
I checked your wiring and pins and they look good to me for your board.
I'm running a Maestro board that had 3.4.6 and now 3.5RC1.
It has A moving bed with an optical endstop at the bottom of the printer and I use a BL-touch for Z0 when the bed is up top twords the nozzle.
My endstops are:M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop WAS S1 Changed for Promega with mechanical X endstop 4-11-22 M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop. This is an optical sensor. M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop. This is an optical sensor.
So if you have a mechanical switch at the other end I'd try
M574 Z1 S1 P"zstop"
Hope this helps.
-
RE: Probe Already Triggered at Start of Probing Move Error
I've had some issues with this on one of my printers. Make sure the pin is straight like Phaedrux said. Also, sometimes very fine strings of filament can get into where the pin slides and make it stick. If you pull the pin in and out, you shouldn't feel any restriction. On my problem printer I also added a M558 R delay to the probe and that seemed to help a bit.
M558 P9 C"^zprobe.in" H5 F120 T6000 R1 B0
With R1 I have a 1 second delay.
Of course, this isn't official advice, just some things I have tried. -
RE: did I f*ck up?
@Phaedrux Amazon USA. Shipping label from 3DMakerWorld. Edit: Last week.
-
RE: did I f*ck up?
I just picked up a Duet 3 Mini 5+ last week. It had the macro on it and of course I clicked it by accident. I had to redo all my setup from the previous day.
I commented out the macro after it bit me once. I got through all that and am running my first test print now.```
;test completed macro for mini 5+ v1.0 testing
;M30 "0:/sys/config.g"
;M30 "0:/sys/config.g.bak"
;M471 S"0:/sys/config_default.g" T"0:/sys/config.g" D1
;M30 "0:/macros/SETNETWORK14"
;M30 "0:/macros/SETNETWORK24"
;echo "Test macros deleted - restart"