Glad it's working properly now. I think the issue was a result of Z0 being set differently than what the G31 trigger height would have given, and the difference was resulting in the huge offset from the Z plane in the heightmap.
@nemesis ah your printer is set up like an ultimaker. i am willing to bet you are fighting a little more friction than the hypercube corexy. do you have to use bushings on the rails that need to rotate?
The entire industry is discovering that stall detect is NOT a reliable way to detect layer shift. Several reasons:
Many possible causes of layer shift have absolutely nothing to do with a motor stalling and/or skipping steps. Belts, pulleys... all the most common causes are not detectable "from the motor". And... most of all... "motor stall" and "motor skip step" are two VERY different things. The driver can detect a true stall, sometimes on the step it occurs, sometimes on the next (or even the next). The driver CANNOT detect all possible "missed step" scenarios.
So... if you expectation was that Triaminic "stall detect" = "never another missed step"... that's just not how those chips/motors work.
There's a much deeper topic here: "Open Loop" (95%+ of all hobbyist 3D printers) vs "closed loop". Only closed loop can detect any/all motor misses (and, even closed loop may not be able to detect a loose grubscrew on a pulley, or a belt jumping teeth). "Stall Detect" is nowhere near "closed loop", and even "closed loop" at the motor is not a panacea.
@dc42 ahhh, that would probably be it! I forgot, my retractions all finish prior to the wipe move, so it's not that.
@Phaedrux I did increase accel and jerk for E and that seems to have helped quite a bit.
@vwegert said in Ideas for more realistic bed temperature control:
@dc42 Now I wish I had a FLIR to see how uniform the temperature really is on the surface and how far in I would have to go to get a realistic measurement... A shame that these things are so expensive...
I looked into buying one of those and from I have been able to deduce the precision of a FLIR is not that good. A spot measuring tool is much cheaper and far more precise. Do that's what I use now. It takes a lot more time to measure the whole bed though...
@JKaechler try M201 X500 Y500. If homing works this way, then you need to set that on homing and create a macro to restore accelerations to their initial values (1000 in your case).
Here's my homex.g (Y is analogous).
M400 ; make sure everything has stopped before we make changes
M915 P0:1 S3 F0 R0 ; configure stall detection
M574 X1 Y1 S3 ; set endstops to use motor stall
M913 X50 Y50 ; reduce motor current to 50% to prevent belts slipping
M201 X500 ; reduce acceleration to avoid false triggering
G91 ; use relative positioning
; X or Y is homed at this point, now home the other axis
G1 S1 X-325 F4000 ; move towards axis minimum
G1 X5 ; move away from home
M400 ; make sure everything has stopped before we reset the motor currents
M913 X100 Y100 ; motor currents back to 100%
G90 ; back to absolute positioning
M574 X1 Y1 S1
M98 Pset_accel.g ; restore acceleration values
set_accel.g restores the acceleration values and has the following contents:
M201 X2000 Y2000 Z100 E9000 ; Accelerations (mm/s^2)
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.