3.2beta2 inconsistent G32
First time it tapped the 1st point, then 2d point twice.
Then twice good.
Last it tapped the 1st point, then 3d point twice.
2020-10-17 21:33:07 G32 Error: Bed calibration : 3 factor calibration requested but only 1 points provided Error: Bed calibration : 3 factor calibration requested but only 0 points provided Error: M950: Pin 'io3.in' is not free 2020-10-17 21:32:46 G32 Leadscrew adjustments made: 0.005 0.009 -0.003, points used 3, (mean, deviation) before (0.004, 0.004) after (-0.000, 0.000) 2020-10-17 21:32:21 G32 Leadscrew adjustments made: 0.030 0.009 0.010, points used 3, (mean, deviation) before (0.016, 0.008) after (-0.000, 0.000) 2020-10-17 21:27:01 G32 Error: M950: Pin 'io3.in' is not free 2020-10-17 21:22:49
; bed.g ; called to perform automatic bed compensation via G32 ; T-1 P0 ; deselect all tools but don't run any tool change macro files M98 P"homeu.g" ; Home U, drop any mounted tool so the endstop reaches bed. M950 J4 C"nil" ; Use the input pin on io3 on the main board Z M558 P8 C"0.io3.in" F250 A2 T24000 S0.02 ; Set the pin of Z probe G31 Z-1 ; Set the trigger height as -1 so that 0 is not touching the switch. G30 P0 X5 Y264.5 Z-99999 ; probe near left leadscrew G30 P1 X495 Y495 Z-99999 ; probe near back leadscrew G30 P2 X495 Y5 Z-99999 S3 ; probe near front leadscrew and calibrate 3 motors M558 P8 C"nil" ; Set the pin of Z probe M950 J4 C"0.io3.in" ; Use the input pin on io3 on the main board Z
Veti last edited by
why are you reassigning pins in the bed.g?
Using the z switch as emergency stop when not using it as probe. Sits under the toolcarriage.
My toolchange macros are also inconsistent.
Makes moves in wrong order.
jay_s_uk last edited by
What firmware version are you running?
I can't say I have any issues with anything running out of order on my toolchanger
3.2 beta 2 as stated in title.
But I downgraded to 3.1.1 now.
Nuramori last edited by Nuramori
Same/similar problem I had, so I can confirm this behavior. Duet3 + sbc + toolboard 0.6 and toolboard 1.0
I also fixed it by going back to 3.1.1. I did try beta 1, which worked fine. Beta 2 is where things went haywire.
Thanks for your reports. There are known problems with commands sometimes being executed out-of-order when using macros on Duet + SBC. These will be resolved in beta 3.
Nuramori last edited by
Is there a chance that the bandwidth/processing speed differential between the main board controlling movements and the processor/driver on the toolboard can create a situation where the extrusion is out is time/lagging behind the movements of the head? I have had in the back of my mind that the axis movements, if too high would outpace the tool head pushing plastic.