BL-Touch works for Z home but not for bed leveling?
-
So I've upgraded my CR-10S with a Duet 2 WiFi, 24V power supply, BL Touch, etc. Over the last week I've been working on the config; finally got it to home with the BL Touch (no z switch) and complete a decent calibration cube print. BUT...
When I try to perform either a G29 "Run mesh compensation" or G32 "True bed leveling"
I get "error : Z probe was not triggered during probing move"Any Ideas? it does deploy with the m280 p0 s10, and retract with m280 p0 s90.
If any other G code files are needed let me know ill post them quickly.
Thanks!
; bed.g
; called to perform automatic bed compensation via G32
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation; config-override.g file generated in response to M500 at 2021-05-31 18:36
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A204.9 C265.4 D1.1 S1.00 V24.1 B0
M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700 (Mountain Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Miller-Spec Printer" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
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 X450 Y450 Z350 E2000 ;Jerk
M203 X12000 Y12000 Z1500 E5000 ; max speed
M201 X900 Y900 Z300 E5000 ;Acceleration
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X-4 Y-6 Z0 S1 ; set axis minima
M208 X302 Y302 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H0 F120 T9000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-43 Y-7 Z3.67 ; set Z probe trigger value, offset and trigger height
M557 X20:282 Y20:282 S16.375 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4983 C1.647829e-7 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat 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 S300 ; set temperature limit for heater 0 to 300C
M308 S1 P"e0temp" Y"thermistor" T100000 B4983 C1.647829e-7 ; 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 S300 ; set temperature limit for heater 1 to 300C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.5 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.5 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S0.5 H1 T45 ; set fan 2 value. Thermostatic control is turned on; Tools
M563 P0 S"Extruder 1" D0 H1 F0 ; define tool 0
G10 P0 X-4 Y-6 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
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700 (Mountain Standard Time)
M280 P0 S10 ; deploy BLTouch; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700 (Mountain Standard Time)
M280 P0 S90 ; retract BLTouch -
Post your homeall/homez as well.
Does M401 and M402 work to deploy/retract the pin?
Please also post the results of M122 and M98 P"config.g"
-
Thank you for taking the time to check this out! I really appreciate it.
When sending M401 it does deploy; and retract with M402
Home all and Home Z is posted under these results.
Result of M98 P"config.g"
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
6/1/2021, 1:15:17 PM m122Results of M122 - "response too long" but in console I get...
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S4-6J9F6-3S46T-1U0AL
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93992 of which 24 recycled
Exception stack ram used: 496
Never used ram: 8580
Tasks: NETWORK(ready,316) HEAT(blocked,1224) MAIN(running,1896) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:23:54 ago, cause: power up
Last software reset at 2021-05-31 18:02, reason: User, spinning module GCodes, available RAM 8556 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 26.4, current 37.2, max 37.5
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 121/419
Driver 1: standstill, SG min/max 105/268
Driver 2: standstill, SG min/max 0/554
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-06-01 13:14:56
Cache data hit count 2524443450
Slowest loop: 9.40ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.2ms, write time 2.1ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 1204431ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 8, completed moves: 8, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 29.95ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address e0:98:06:22:e6:14
WiFi Vcc 3.34, reset reason Unknown
WiFi flash size 4194304, free heap 20408
WiFi IP address 192.168.1.14
WiFi signal strength -54dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700
G91 ; relative positioning
G1 H2 Z5 F9000 ; lift Z relative to current position
G1 H1 X-311 Y-313 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F9000 ; go back a few mm
G1 H1 X-311 Y-313 F600 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X63 Y27 F9000 ; go to first bed probe point and home Z
M558 A1 F100
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F150 ; lift Z relative to current position
G90 ; absolute positioning; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700
G91 ; relative positioning
G1 H2 Z5 F900 ; lift Z relative to current position
G90 ; absolute positioning
G1 X63 Y27 F900 ; go to first probe point
M558 A1 F100
G30 ; home Z by probing the bed
;M558 A10 F120
;G30
; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F150 ; lift Z relative to current position
G90 ; absolute positioning - WiFi -
-
@miller-spec said in BL-Touch works for Z home but not for bed leveling?:
M558 P9 C"^zprobe.in" H0
Why do you have your dive height as 0? It should be at least slightly higher than your trigger height. So try H5.
You should also update your firmware. Upload this zip file to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
-
@miller-spec said in BL-Touch works for Z home but not for bed leveling?:
; bed.g
; called to perform automatic bed compensation via G32
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 30 2021 22:04:22 GMT-0700
M561 ; clear any bed transform
G29 ; probe the bed and enable compensationTo run G32 you have to define probing points in bed.g
And the layout of the z-axis
M671is missing in config.g
(UTC+1)
-
Thanks, I Changed my dive height to 5 and updated the firmware. Now I'm able to run mesh compensation and see my height map.
-
I'm guessing I cant use G32 because I have my motors wired in series. G32 would allow the controller to adjust the bed right? which isn't possible wired like that. So that's my bad didn't do any research on that command. Thank you though, I appreciate the response.
-
You can use G32 to level the bed by adjusting the level screw by hand.
G32 reports the deviations for each point, so it is much easier to do that....
I have used that for a long time before switching to double Z....(UTC+1)
-
@miller-spec you have a spare motor driver, so you could split the Z motors and connect each to their own driver, for auto bed levelling (though just left/right). See https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
True, Ill try that. I've been using my digi caliper to probe the gantry to the bed on its extreme ends and twisting the lead screws till they're close, then releveling haha. Thanks, gonna see what G32 does now.
-
Once I figure out a way to neatly enclose all this new hardware I'll definitely do that. Right now its all bolted to the old CR-10 enclosure skeleton haha..
