Beep after G32 completion

  • It started just today, I'm running 1.16 beta 10 and the steppers seem to emit a loud beep once I send any command after G32 completes. The controls are then unresponsive until I reset the board. Could it be a mathematical error following the bed correction matrix? G30 by itself runs fine. The problem seems to be tied to G32 only. I can only see one thing I changed today, and that would be the z probe offset. I actually set it to 1.89, does it support this format?

    Any advice?
    Here are my config.g and bed.g

    ; FT 2020 i3 config file for dc42 Duet firmware

    ; Prologue and comms section
    M111 S0 ; Debug off
    ;*** ;*** Wifi Networking
    M552 S1 ; Enable WiFi

    M555 P2 ; Set output to look like Marlin
    M575 P1 B57600 S1 ; Comms parameters for PanelDue

    ; Movement section
    M569 P0 S1 ; Drive 0 goes forwards (change to S0 to reverse it)
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M569 P4 S1 ; Drive 4 goes forwards
    M574 X1 Y1 Z0 S0 ; set endstop configuration (X, Y and Z endstops, at low end, active high)
    M906 X1360 Y1360 Z300 E300 ; Set motor currents (mA)
    M201 X1000 Y1000 Z15 E1000 ; Accelerations (mm/s^2)
    M203 X15000 Y15000 Z250 E3600 ; Maximum speeds (mm/min)
    M566 X1200 Y1200 Z30 E60 ; Minimum speeds mm/minute
    M208 X200 Y200 Z140 ; set axis maxima (adjust to suit your machine)
    M208 X0 Y0 Z0 S1 ; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed)
    M350 X32 Y32 Z16 E32 I0 ; Set 16x microstepping without interpolation
    ;M350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping with interpolation
    M92 X320 Y320 Z1600 ; Set axis steps/mm
    ;M92 X160 Y160 Z1600 ; Set axis steps/mm
    M92 E185.2:185.2 ; Set extruder steps per mm
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves

    ; Z probe section
    ;M558 P0 ; No Z probe
    ;G31 X-11.0 Y0 Z1 P500 ; Set the probe height and threshold (put your own values here)
    M558 P1 X0 Y0 Z1 H6 F150 T3000 ; smart IR Z probe, used for homing Z axis only, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
    G31 P500 X0 Y0 Z1.89 ; set threshold and offsets

    ; Heater and thermistor section
    ;*** If you have a Duet board with 1K thermistor series resistors, change R4700 to R1000 to the following M305 commands
    M305 P0 T100000 B4036 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
    M305 P1 T6858834 B5425 R4700 H0 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
    ;M305 P1 T6808015 B5422 R4700 H-10 L0
    ;M305 P2 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
    M301 H1 P22.0 I0.2 D180 T0.2 S1 W180 B30 ; NEW PID settings extruder 0
    M307 H0 A 387.9 C304.5 D6.5 B0 S0.8 ;Heater 0 model: gain 387.9, time constant 304.5, dead time 6.5, max PWM 0.80, in use: yes, mode: PID
    Heater 0 model: gain 387.9, time constant 304.5, dead time 6.5, max PWM 0.80, in use: yes, mode: PID

    ;M301 H1 P9.5 I0.75 D30.15 T0.50 S1.0 ; OLD PID settings for extruder 0
    ;M301 H2 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 1
    M570 H1 P30 T30 S120 ; Increase to allow extra heating time if needed
    M143 S493 ; Set max hot end temp 493°C

    ; Tool definition section
    M563 P0 D0 H1 ; Define tool 0 to use extruder drive 0 and heater 1
    G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
    ;*** If you have a dual-nozzle build, un-comment the following 2 lines
    ;M563 P1 D1 H2 ; Define tool 1
    ;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures

    ; Bed probe section (not needed if you use a bed.g file)
    ;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of your Z probe
    ;M557 P0 X40 Y40 ; Four...
    ;M557 P1 X160 Y40 ; ...for bed...
    ;M557 P2 X160 Y160 ; ...probe points...
    ;M557 P3 X40 Y160 ; ...levelling
    ;M557 P4 X121 Y100 ; 5th probe point for levelling (un-comment this to get a 5th point at the centre of the bed)

    ; Epilogue
    ;*** If you are using axis compensation, put the figures in the following command
    M556 S78 X0 Y0 Z0 ; Axis compensation here
    ; select first hot end

    ; macro /sys/bed.g Auto calibration routine for a Cartesian printer: 1 to 5 probe points
    M561 ; clear any bed transform, otherwise homing may be at the wrong height
    G1 Z6 F200
    G1 X40 Y40 F2000 ; move head
    G30 P0 Z-100000 ; probe
    G1 Z5 F200 ; rise head
    G1 X160 Y40 F2000
    G30 P1 Z-100000
    G1 Z5 F200
    G1 X160 Y160 F2000
    G30 P2 Z-100000
    G1 Z5 F200
    G1 X40 Y160 F2000
    G30 P3 S Z-100000 ; probe and calibrate with 4 parameters (as there is 4 points)
    G4 P1500 ;Leave the probe there to give the web interface time to report the plane points
    G1 Z10 F200

  • @dcaron:

    G30 P3 S Z-100000 ; probe and calibrate with 4 parameters (as there is 4 points)

    This is highly suspicious - you should have S followed by a number, in this case presumably 4 since the comment suggests you want to calibrate four parameters.

  • Peridot,
    I did add 4 after the S parameter, it still doesn't work. It seems to hang on the next move (10 mm z lift). It beeps just after the 1500 ms delay. It seems like a stepper beep and then it hangs. It doesn't accept new commands or report temperatures. The web interface is still functional and a software reset brings it back to normal.

  • I fountd the culprit: the right formulation was S0 to end the calibration routine. I changed my file to the form in the Wiki:

    M561 ; clear any existing bed transform
    G30 P0 X10 Y10 Z-99999 ; define 4 points in a clockwise direction around the bed, starting near (0,0)
    G30 P1 X10 Y190 Z-99999
    G30 P2 X190 Y190 Z-99999
    G30 P3 X190 Y10 Z-99999
    G30 P4 X100 Y100 Z-99999 S0 ; finally probe bed centre, and calculate compensation
    G1 X0 Y0 F5000 ; move the head to the corner (optional)


Looks like your connection to Duet3D was lost, please wait while we try to reconnect.