Auto Calibration of Nozzle Z offset
-
@nicolas-brejat can you run M98 P"config.g"
Can you also post your full config?
PC5 is the same as zstop. Can you also make sure zstop isn't used in your config -
@fcwilt ok, here is the error it reported
-
@jay_s_uk ok, here is full config for your reference:
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
M669 K1
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes forwards using default driver timings
M569 P1 S0 ; physical drive 1 goes forwards using default driver timings
M569 P2 S1 ; physical drive 2 goes forwards using default driver timings
M569 P3 S1 ; physical drive 3 goes forwards using default driver timings
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E140.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X900 Y900 Z700 E400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X260 Y210 Z200 S0 ; set axis maxima; ---filament sensing---
M591 D0 P1 C"PA13" S1; Endstops
M574 X2 S1 P"!xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"!ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input; Z-Probe
M558 P5 C"probe" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z3 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid
M558 K1 P8 C"PC5" T18000 F180 H2.4 A10 S0.0025 R0
G31 K1 P500 X0 Y0 Z-0.5; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bed" T0 ; create bed heater output on bed and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S350 ; set temperature limit for heater 1 to 350C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0 H1 T50 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
M918 P1 E4 F1000000
M501
M500
M851 -
@nicolas-brejat said in Auto Calibration of Nozzle Z offset:
I tested configuring two probes as you have done but it was under firmware 3.3.0
Perhaps something is different under your firmware.
Did you try including the parameter K0 for the first M558/G31 commands?
Frederick
-
@fcwilt do you mean it's workable under firmware 3.3.0? I'm using RRF 3.0 now, if change K1 to K0 in M558/G31 command, the "K too high" error will disappear, but K0 is for leveling probe, so it'll have below error when auto home:
-
@nicolas-brejat said in Auto Calibration of Nozzle Z offset:
; Z-Probe
M558 P5 C"probe" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z3 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid
M558 K1 P8 C"PC5" T18000 F180 H2.4 A10 S0.0025 R0
G31 K1 P500 X0 Y0 Z-0.5he meant add K0 to the first M558.
can you post the output of M115? we never released a version of RRF3.0 for the Fly-E3 -
@jay_s_uk it was RRF 3.0 before, just now updated to 3.3, but still same issue.
-
@nicolas-brejat ok, thats still not the latest release.
Please find the latest release here https://github.com/gloomyandy/RepRapFirmware/releases/tag/v3.3_2 -
@jay_s_uk after update below firmware, the LCD 12864 screen becomes blank, Wifi fail to connect. does it need to change other settings after update 3.3.2 firmware?
-
@Nicolas-Brejat No. You've loaded the incorrect file. You should be using the ESP8266wifi file and not the SBC file.
-
@jay_s_uk ok, still same error. so it's not related to firmware version?
-
@nicolas-brejat one for @gloomyandy
-
@jay_s_uk We only currently support a single probe.
-
@gloomyandy do you mean RRF firmware doesn't support 2nd probe? if change to duet board, will it work?
-
@nicolas-brejat the STM port currently doesn't support more than one z probe (mainly as a hang over from all the restrictions initially made to the LPC port) but the duet boards do.
It has been added to the to-do list to investigate increasing that limit as part of the next release. -
@jay_s_uk ok, that make sense. hope next release will fix that. thanks