Bed levelling/traming odd message - 3.2 Beta 2
-
I'm running 3.2 beta 2 on a mini5+ in SBC mode.
I now get the following messageBed calibration : 2 factor calibration requested but only 0 points provided
while running G32. I did not get this message in beta 1. This is the full output from the console showing that traming did take place.
06/10/2020, 11:55:55 Bed Traming Cycle: 4 - Difference was 0.004mm 06/10/2020, 11:55:55 Leadscrew adjustments made: -0.021 -0.038, points used 2, (mean, deviation) before (-0.029, 0.004) after (-0.000, 0.000) 06/10/2020, 11:55:55 Bed Traming Cycle: 3 - Difference was 0.015mm 06/10/2020, 11:55:55 Leadscrew adjustments made: -0.089 -0.020, points used 2, (mean, deviation) before (-0.058, 0.015) after (-0.000, 0.000) 06/10/2020, 11:55:55 Bed Traming Cycle: 2 - Difference was 0.276mm 06/10/2020, 11:55:55 Error: Bed calibration : 2 factor calibration requested but only 0 points provided 06/10/2020, 11:55:54 Error: Bed calibration : 2 factor calibration requested but only 0 points provided 06/10/2020, 11:55:54 Bed Traming Cycle: 1 - Difference was 0.276mm 06/10/2020, 11:55:54 Leadscrew adjustments made: -0.720 0.553, points used 2, (mean, deviation) before (-0.131, 0.276) after (-0.000, 0.000)
This is the contents of my bed.g
M671 X-130:400 Y150:150 S10 if !move.axes[0].homed || !move.axes[1].homed ; If the printer hasn't been homed, home it G28 XY ; home y and x ; M98 P"0:/sys/homez.g" ; home z ; M561 ; clear any bed transform ;M558 P9 H5 F120 T24000 ; increase dive height M98 P"bed_twoscrews.g" ; perform bed tramming echo "Bed Traming Cycle: 1 - Difference was " ^ move.calibration.initial.deviation ^ "mm" ; while move.calibration.initial.deviation >= 0.01 ; perform additional tramming if previous deviation was over 0.01mm if iterations = 5 abort "Too many auto tramming attempts" M98 P"bed_twoscrews.g" ; perform bed tramming echo "Bed Traming Cycle: " ^ iterations + 2 ^ " - Difference was " ^ move.calibration.initial.deviation ^ "mm" continue ; G28 Z ; home z
and here is the bed_twoscrews.g
G30 P0 X0 Y150 Z-99999 ; Probe near front left leadscrew G30 P1 X230 Y150 Z-99999 S2 ; Probe near front right leadscrew
Any thoughts why?
-
@dc42 @chrishamm I think this is the same problem I described in the email I sent you (but I've seen it on the LPC port). I get the same error messages due to dropped gcode lines/lines executed more than once.
-
@gloomyandy I just replied to your mail. I'll need a debug log from DCS to figure out why this is happening. I haven't had this problem on my test platform yet.