Solved Duet3 6HC not deploying BL touch for mesh bed leveling
-
I agree.
With what?
How can it use the buttons on the dashboard with no issues but combining them with home all not trigger it?
Not sure what you mean.
Frederick
-
@fcwilt What I mean by that is how can the probe be recognized for a single G30 and work as intended. The probe goes to the right location, deploys, gets triggered at the right height, reports that data as my new z height, and retract. Yet for any command other than that the probe will not deploy.
-
@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:
@fcwilt What I mean by that is how can the probe be recognized for a single G30 and work as intended.
That's good.
Yet for any command other than that the probe will not deploy.
That's bad.
The other commands that I use that need to probe are G29 and G32.
I assume you are using those. What exactly happens when you try to execute them?
Sometimes it helps to execute them from the DWC Console to make it easier to see the response.
Frederick
-
@fcwilt the toolhead moves to the correct X and Y location and the BLTouch does not deploy. The bed moves up and I have to hit the estop in order to avoid a collision.
I get an error message stating "z probe not triggered during probe move"
-
@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:
@fcwilt the toolhead moves to the correct X and Y location and the BLTouch does not deploy. The bed moves up and I have to hit the estop in order to avoid a collision.
I get an error message stating "z probe not triggered during probe move"
Are we talking about G29?
Did you verify that you DO NOT have a mesh.g file?
Does homeZ.g work?
Thanks.
Frederick
-
@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:
M584 X0.1 Y0.2:0.3 Z0.4:0.5 C0.0 E1.0:1.1 ; set drive mapping M350 X16 Y16 Z16 E16:16:16:16:16 I1
That would be the source of the array too long error. You have two E drivers assigned, but then in M350 you list five values for E microsteps. Remove three of those 16s.
The Can timeouts are another problem that might explain what's going on. Can you now send M122 B1 to get the disagnostics report for the expansion board?
Also, can you try adding a
G4 S2
command to the start of your config.g to cause a couple seconds to pass before any commands are sent to the canbus expansions to allow time for the boards to initialize.And finally, your tool definitions are a bit weird.
; Tools M563 P1 S"FDM1" D0 H1 F0:2 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"FDM2" D1 H2 F0:3 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C G10 P0 X-9 Y39 Z-5 ; T0 G10 P1 X-9 Y39 Z-5 ; T1 G10 P2 X-9 Y39 Z-5 ; T2 G10 P3 X-9 Y39 Z-5 ; T3
You start at tool 1 instead of tool 0.
And then you have G10 tool offsets for tool 0 to 3, two of which don't currently exist. -
@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:
@dc42 So if I understand correctly, I need a mesh.g file? I don't currently have one under /sys
@fcwilt correct no mesh.g file
-
@Phaedrux can do! I removed the extra microstep values. After initial configuration I had to remap a few things. The configuration tool doesnt account for 2 Z motors or Y motors so in the tool I just made them extra drivers so I could get all my drivers accounted for. Then after the config.g was generated I went in and manually mapped them. It was an oversight on my part not to delete the extra M350 values.
So the reason I have no tool 0 or tool 3 yet is those tools havent been picked out yet by me team. I was thinking a sharpie to mark important locations (tool 0) and the fly cutter thing from E3D for tool 3.
M122 B1
Diagnostics for board 1:
Board EXP3HC firmware 3.0RC1 2019-12-16b1
Never used RAM 163.1Kb, max stack 344b
HEAT 1228 CanAsync 1452 CanRecv 940 TMC 168 AIN 532 MAIN 2216
Driver 0: standstill, reads 53889, writes 11 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 53891, writes 11 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 53894, writes 11 timeouts 0, SG min/max 0/0
Moves scheduled 0, completed 0, hiccups 0
VIN: 24.1V, V12: 12.3V
MCU temperature: min 42.2C, current 42.5C, max 42.5C
Ticks since heat task active 51, ADC conversions started 398294, completed 398294, timed out 0
NVM user row de9a9239 aeecffb1 ffffffff ffffffff -
This post is deleted! -
The expansion bird firmware is out of step with the mainboard. Send M997 B1 to flash the expansion. Make sure you have all the files from the 3.2.2 release in the system folder first. If in doubt just upload the full zip file again from the 3.2.2 release. That might actually get it to update on its own.
-
@Phaedrux M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.2.2 (2021-02-12)
Bootloader ID: not available
Never used RAM 154896, free system stack 200 words
HEAT 92 CanAsync 94 CanRecv 87 TMC 64 MAIN 299 AIN 259
Last reset 00:00:50 ago, cause: software
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm, standstill, reads 48988, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, 80.0 steps/mm, standstill, reads 48990, writes 11 timeouts 0, SG min/max 0/0
Driver 2: position 0, 80.0 steps/mm, standstill, reads 48993, writes 11 timeouts 0, SG min/max 0/0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V, V12: 12.3V
MCU temperature: min 42.2C, current 42.5C, max 42.5C
Ticks since heat task active 97, ADC conversions started 50088, completed 50088, timed out 0
Last sensors broadcast 0x00000000 found 0 100 ticks ago, loop time 0
CAN messages queued 18, send timeouts 0, received 462, lost 0, free buffers 36successful update
-
Ok now that those things were changed what happens when you send M98 P"config.g"? Still getting any errors?
Just to confirm, bltouch and z motors are both on the mainboard right?
-
![0_1615578697731_Screenshot 2021-03-12 135015.jpg](Uploading 100%)
after the update I updated the config file with a new fan definition (I accidentally had too many assigned to each tool) and restarted the board. I retried G29 and let it play out. it did not deploy the probe, but this time it stopped at a z height of 0.50 and just gave me an error message instead of crashing. I consider this progress lol
-
Good news: M98 P"config.g" now only returns a blue message about HTTP, FTP, and TELNET. no errors. confirmed. the only drivers being used on the expansion are D0 for extruder 0 and D1 for extruder 1. The BL touch is on io.7 on the mainboard
-
What was the error? Your screen shot didn't upload.
-
Only other suggestion I have at this point is to try using io_5 instead of 7.
-
G29
Error: Z probe was not triggered during probing move
-
@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:
;deselect tools T-1
Do you happen to have anything in your tool change files?
-
So I just switched it from io.7 to io.5 and edited my config to match
; Axis Limits M208 X50 Y0 Z0 C0 S1 ; set axis minima M208 X550 Y550 Z550 C260 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!io1.in" ; configure active-high endstop for low end on X via pin !io1.in M574 Y1 S1 P"!io0.in" ; configure active-high endstop for low end on Y via pin !io0.in ;M574 Z1 S2 P"!io7.in" ; configure Z-probe endstop for low end on Z ; Stall detection for tool coupler M915 C S5 F0 H200 ; Z-Probe M950 S0 C"io5.out" M558 P9 C"io5.in" H2 F120 T6000 R0.2 A1 S0.01 ; 1 reading ;M950 S0 C"io7.out" ; create servo pin 0 for BLTouch ;M558 P9 C"^io7.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds M557 X100:400 Y100:400 S25:25 ; define mesh grid G31 P50 X-63 Y-61 Z2.5 ; set Z probe trigger value, offset and trigger height
Good news: it still works a z endstop. the probe deploys and retracts at the appropriate times.
Bad news: G29 still doesn't deploy the probe -
Is there something about the position of the first probe point for G29 that is causing stress on the servo wiring and making a poor intermittent connection?
Can you try manually placing the print head at the same place it would be when doing G29 and then sending a manual G30? Does it work there?