BL-Touch works for Z home but not for bed leveling?
-
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..
