Auto Calibration Confusion

brisksleeper

Hi all! I'm trying to re-setup my Rostock Max V2 after sending my Duetwifi to the shop for some minor repairs, but my auto-calibration routine seems to be going haywire. I have FSR's under the bed. This is what's happening:

1. When it runs through the calibration routine, in between each peripheral point it makes this sweeping motion by the Z tower and goes down in between the X and Z Towers as if to make contact, but never does.

2. When it makes contact at the points I can see that it is indeed sensing the bed and pulls up at all of my points.

3. When the routine is over, I'm getting no results (no error messages either); no deviation factor, I run M665 and M666, but getting my original results.

I do have S6 at the end of my bed.g code, so I don't even know where to start. I was hoping someone might recognize the symptoms and could offer an explanation. The guy who repaired my Duetwifi updated my WiFi Server firmware and Duet Web Control, I'm wondering if that has anything to do with my issue.

Here's my bed.g:

[[language]]
; Auto calibration routine for SeeMeCNC Rostock MAX V2
;
; About the G30 S parameter
; Used to specify what calibration computation to perform.
;
; S=-1 Don't adjust anything, just print the height error at each probe point
; S=0 Equivalent to S= <number_of_points_probed>; S=3 Adjust homing switch corrections only
; S=4 Adjust homing switch corrections and delta radius
; S=6 Adjust homing switch corrections, delta radius, and X and Y tower position offsets
; S=7 Adjust homing switch corrections, delta radius, X and Y tower position offsets, and diagonal rod length

M561                  ; clear any bed transform, otherwise homing may be at the wrong height
G31 X0 Y0               ; don't want any probe offset for this
M558 P3                  ; drive mod pin on Probe Z connector LOW
G28                  ; home the printer

;*** Remove the following line if your Z probe does not need to be deployed
;M98 Pdeployprobe.g    ; deploy the mechanical Z probe

; The first time the mechanical probe is used after deployment, it gives slightly different results.
; So do an extra dummy probe here. The value stored gets overwritten later. You can remove this if you use an IR probe.

G30 P0 X0.00 Y100.00 Z-99999 H0
G30 P1 X50.00 Y86.60 Z-99999 H0
G30 P2 X86.60 Y50.00 Z-99999 H0
G30 P3 X100.00 Y0.00 Z-99999 H0
G30 P4 X86.60 Y-50.00 Z-99999 H0
G30 P5 X50.00 Y-86.60 Z-99999 H0
G30 P6 X0.00 Y-100.00 Z-99999 H0
G30 P7 X-50.00 Y-86.60 Z-99999 H0
G30 P8 X-86.60 Y-50.00 Z-99999 H0
G30 P9 X-100.00 Y-0.00 Z-99999 H0
G30 P10 X-86.60 Y50.00 Z-99999 H0
G30 P11 X-50.00 Y86.60 Z-99999 H0
G30 P12 X0 Y0 Z-99999 S6

;*** Remove the following line if your Z probe does not need to be retracted
;M98 Pretractprobe.g   ; retract the mechanical Z probe

G1 X0 Y0 Z150 F10000   ; get the head out of the way of the bed</number_of_points_probed> 
```and my config.g

[[language]]
; Configuration file for SeeMeCNC Rostock MAX V2

; Communication and general
M111 S0 ; Debug off
M550 PRandy MaxV2 ; Machine name and Netbios name (can be anything you like)
M551 Preprap ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xEA ; MAC Address
;*** Wifi Networking
M552 S1 ; Enable WiFi
;M554 P192.168.1.201
;M553 P255.255.255.0

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

G21 ; Work in millimeters
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 R141.047 L300.15 B145.0 H355.0 X0 Y0 Z0 ; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 Z16 E16 I1 ; Set 16x microstepping with interpolation
M92 X80 Y80 Z80 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E800 I60 ; Set motor currents (mA) and increase idle current to 60%
M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
M566 X800 Y800 Z800 E1200 ; Maximum instant speed changes mm/minute

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4388 R4700 H30 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
;M305 P2 T100000 B4388 R4700 H30 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M301 H1 P25.8 I0.116 D72.3 T1.0 S1.0
M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
M106 P1 T45 H1 ; disable thermostatic mode for fan 1
M106 P2 H-1
M106 P3 H-1

; Tool definitions
M563 P0 D0 H1 F1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
;*** If you have a single-nozzle build, comment the next 2 lines
;M563 P1 D1 H2 ; Define tool 1
;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E1025:1025 ; Set extruder steps per mm

; Z probe and compensation definition
;*** If you have an IR zprobe instead of a switch, change P4 to P1 in the following M558 command
M558 P5 X0 Y0 Z0 ; Z probe is a switch and is not used for homing any axes
G31 X0 Y0 Z-.08 P500 ; Set the zprobe height and threshold (put your own values here, Set the zprobe offset and threshold (determine your printer's Z offset value). For a delta, use zero X and Y offset.

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

T0 ; select first hot end

dc42

Regarding #1, see #3 at https://duet3d.com/wiki/Common_problems_and_their_solutions.

When you have fixed that, if you are still not getting autocalibration results, check the GCode Console page for error messages.

brisksleeper

That did it dc42, thank you! Had to put M401 before my first G30 and M402 after my last G30.

Concrete Head

For all those who spent hours of frustration trying to use the auto calibration with FSR sensor DELETE THE PROBE FILES from the SYS directory!! I just spent all day yesterday trying to figure out why everything was working except would not save any corrections.
Then came across this post.
You have to scroll down to see the release dc42 refers to because 1.20 is out now as well.

dc42 thank you for all you do! You are Amazing!