New experimental firmware 1.19beta10
-
Hi Lars, I think you are right, I had the corrections in the wrong direction. Please try DuetWiFiFirmware 1.19beta10+4, available at https://dl.dropboxusercontent.com/u/19369680/DuetWiFiFirmware.bin.
[[language]] 07:53:56 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.001 0.008 -0.002, mean 0.002, deviation from mean 0.005 07:53:12 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.003 0.005 -0.001, mean 0.000, deviation from mean 0.003 07:52:38 G32 Leadscrew adjustments made: -0.023 0.025 0.002, points used 3, deviation before 0.012 after 0.000 07:51:53 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.021 -0.006 0.003, mean -0.008, deviation from mean 0.010 07:51:18 G32 Leadscrew adjustments made: 0.325 0.014 -0.374, points used 3, deviation before 0.167 after 0.000 ```I do believe its working! I guess it might offset the center point from Z=0 if it is not on the plane made up of the 3 probings? I included it as a fourth point to minimize this but I guess one could include a rehome of Z in the bed.g…?I'm glad this is working at last. Thanks for your patience!
The algorithm minimises the sum of the squares of the height errors at the probe points. So if the bed centre is not on the plane - either because the bed is not flat or (more usually) because the gantry flexes enough to allow the head to droop a little around the centre, then it will upset Z=0 at the centre. To correct it, you can add a single G30 command in bed.g to probe the bed centre after doing leadscrew compensation. Including probe points near the centre of the bed as you have done will also help.
-
I want to give the bed leveling feature a try.
I remember reading about this in another thread, on how to assign the second Z motor, but I can't find it in search.If memory serves…
I connect the second Z motor to the E1 port of the board. I assign it in config.g with P4. And then the 2nd Z motor would be identified as "U". Is this correct?
Also, would I need to replace the jumper back into the Z2 port on the board when it's empty?If this is a redundant question I apologize. If so, if someone recalls that conversation could they please post a link?
Thanks
-
See https://duet3d.com/wiki/Bed_levelling_using_multiple_independent_Z_motors. You will need firmware 1.19beta10+4. If your board is a Duet WiFi you can get it via the link I posted 4 replies up.
In summary, you don't configure the extra Z drive as U, and you do need to replace the jumpers in the second Z motor socket.
-
Nice! Will give the leveling a try as soon as I have time.
And I have that extra U axis working so well
David, I must say I'm impressed by your development pace and how quickly you respond to our issues!
-
David, I must say I'm impressed by your development pace and how quickly you respond to our issues!
Thanks!
The difference between the Series 2 Duets and other open-source controller boards is that the profits we make on the Duets fund development, support and a generous warranty replacement policy. So I can afford to work almost full time on Duet development and support. Most other open-source boards rely on volunteers.
-
Hello,
How do we download version 1.19beta10 + 4 for Duet Ethernet?
There is only 1.19beta10 + 2
a greeting
-
If you can wait until tomorrow, I will release beta 11.
-
-
Did something change that would affect the Z height of my delta between earlier betas before beta 9?
In beta 9 I tweaked the Z probe offset to get the head right when printing.
Now on beta 10 the same settings now the head crashes into the bed, rips the tape off, no filament comes out because the head is pressing so hard against the bed.Before beta9 -
G31 X0 Y0 Z1.06 P500On beta9 and beyond -
G31 X0 Y0 Z1.28 P500I also had a failed print, maybe it screwed up my z probe..
-
No, nothing has changed in that area.
