Topics created by GaRv3

Also, what type of extruder is it? 4mm of retraction may be too much. It really looks like retraction under runs.

The easiest way of getting warning that I can think of is to put the commands you want to test in a GCode file and print it. However, when I was testing stall detection endstops, I didn't find any need to do this. If the stall detection is working then the homing move stops when the tower or axis reaches the hard stop. If it tries to keep going, then stall detection isn't working. You should use reduced current when homing with stall detection anyway, to make sure that the motor does stall instead of the belt jumping on the pulley.

I just upgraded to 1.21 and the issue appears to be resolved now. ☺

@AlexLin:

for the interested this is the phone mount. I doesn't include the 3030 mount but that is easy to fix
https://www.thingiverse.com/thing:2194278

Great! Thank you!

I have just tried the same on mine and after a rest boot post Config.g upload mine also stays disconnected

Currently on 1.21RC1 for FW and WiFi Server and 1.20 for DWC.

HTH

+1 for an option to be able to pause or halt on a warning message. I'd use this if delta calibration generated a value over x mm deviation.

Sounds great. Thanks!
Do you already know the board you are going to use or would you like some suggestions?

I have lowered the fan duct even more and put a silicone sock over the heater block. Now I at least do not get errors any more.
Seems to be ok now.

@whosrdaddy:

No, if you map more drivers to the same axis, they automatically get the same current as the original driver.
You can specify a different current values per driver if you wish though…

Currently all drivers used by an axis have to use the same current.

Ok, great. I deleted them.

Thx!

The D numbers are the same ones you use in the M563 tool definition command.

Ok, I had a typo in the deployprobe.g filename.

But this is not gonna work anyway because of the following reasons.

M140 (without parameters) does NOT reactivate the heater. This probably is a bug.

The scripts are called at the very beginning and end of the mesh calibration. This is not what is needed for sensors of this type because the leveling will take a while and bed temperature drops quite a lot which will result in completely different offsets at the start and end. The heaters have to be turned off when the probe moves down (until it triggers) and back on, when the probe starts moving up again (right after triggering). So the bed heater would be shut off several times (at each probe position) for a second or so when the probe moves down and stay on for the rest of the time. This would keep the bed temperature relatively stable and allow precise mesh compensation.

The hotend still cannot be turned off and on again.

I followed your instructions and it is working perfectly fine. I used a three pin molex, one of the side pins is connected from the 24V pin to the buck converter VIN, the middle pin pin goes from the Vfan to the VCC output of the buck. Unfortunately this jumper is not protected against reverse polarity, so I will have to label it very carefully. Worst case (reversed polarity), I would power the buck converter with 5V and nothing serious will happen.
You saved my Noctua and my radial fan!. I love my Duet more and more, it has plenty of possibilities for any configuration. Very versatile.
Thanks again for you great help.