New experimental firmware 1.19beta10
-
Can this new independent Z motor leveling be used for dual Z Cartesian printers like the Prusa, OrdBot, clones, etc, or is this a Delta only feature? Seems like it could be used to automatically get the X-axis of the bed mechanically leveled, only requiring the Z motors to track Y-axis movement…
-
Do you have a config-override.g file, and a M501 command near the end of config.g?
No. I took the post-calibration M665 and M666 numbers from config-override.g, put them in config.g, and deleted config-override.g. No M501 command at the end of config.g. (I tried the M501 / config-override.g methodology in the past but ultimately prefer to have it all in config.g).
Those numbers look good to me.
Good to hear!
-
Lars, I found the problem: I missed a minus sign when transposing a formula from Maxima to the source code. So in the 3 leadscrews case it was computing the second leadscrew correction with the wrong sign.
Please try 1.19beta10+2 which I have just released.
Works now!
-
I have another oddity to report with 1.19beta10:
Sometimes when a (successful) print ends, I get a "Can't delete file 0:/sys/resurrect.g" error. It's not surprising it can't delete it (because I don't have a resurrect.g file), but I never saw that error until recently (I'm pretty sure coincident with going from beta8 to beta10). I also don't know where the [c]G10 P1 S0[/c] came from - it's not in my gcode, and the only [c]G10[/c]s I have in my Duet config files are [c]G10 P0 R0 S0[/c] and [c]G10 P1 R0 S0[/c] in my config.g file when I set up my tools. Here's the console output from a print I ran last night:
11:12:00 PM G10 P1 S0 Can't delete file 0:/sys/resurrect.g Done printing file 11:11:56 PM Can't delete file 0:/sys/resurrect.g Done printing fileHere are the last lines of gcode from that print:```
G1 X0.053 Y9.146 F540
G1 E-8.0000 F6000
; layer end
T0 ; Select Extruder 0 if not already selected
G90 ; Switch to absolute mode
G1 X0 Y0 Z250 E-10 F6000 ; Retract filament and raise printhead
M104 S0 ; Turn off heater
M84 S10 ; turn off motors after 10 secondsBTW, do you prefer feedback like this in this forum or as an issue in github? -
Thanks, Yonkiman. I prefer issues reported here, especially for betas.
Regarding G1 P1 S0, do you have a stop.g file, and if so, is it in that?
I'll suppress the "Can't delete" message in the next beta.
-
Chrishamm has released DWC 1.17+2 which includes the changes needed to work with the new height map. So will those of you running firmware 1.19beta10 please upgrade it to 1.19beta10+2 if you haven't already, and upgrade DWC to 1.17+2. The mesh bed compensation height map should then display correctly.
-
Regarding G1 P1 S0, do you have a stop.g file, and if so, is it in that
Yes, I have the file; no it is not in that file. File only has the default 2 comment lines. I actually did a search for the word "G10" on my entire SD card, and it only appeared in the tool setup in config.g (as reported above) and one or two binary files.
Speaking of which…once we successfully flash the firmware, is it safe to remove all the non-text (i.e. .bin/.zip/.rar) files from our sys directory?
-
Speaking of which…once we successfully flash the firmware, is it safe to remove all the non-text (i.e. .bin/.zip/.rar) files from our sys directory?
Yes, although the only binary files that should be in there are the two extra .bin files for the Duet WiFi.
-
Hey David, did you see my question nested up a few posts about dual-Z motor cartesian printers?
-
Can this new independent Z motor leveling be used for dual Z Cartesian printers like the Prusa, OrdBot, clones, etc, or is this a Delta only feature? Seems like it could be used to automatically get the X-axis of the bed mechanically leveled, only requiring the Z motors to track Y-axis movement…
Yes, it's for Cartesian and CoreXY printers, not deltas.. See https://duet3d.com/wiki/Bed_levelling_using_multiple_independent_Z_motors.
It can also be used to tell you what adjustments to make to manual bed levelling screws, but I haven't documented how to do that yet.
-
Did some more testing for the leveling. There might be some other bug. Feels like its still adjusting in the wrong direction…
I changed the probe order to match the reporting of G32 and moved the points a bit.16:55:14 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.136 -0.441 -0.471, mean -0.349, deviation from mean 0.151 16:54:26 G32 Error: some computed corrections exceed configured limit of 0.50mm: -0.007 0.505 0.553 16:52:50 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.138 -0.439 -0.461, mean -0.346, deviation from mean 0.147 16:52:09 G32 Leadscrew adjustments made: -0.294 0.260 0.269, points used 3, deviation before 0.170 after 0.000 16:51:36 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: 0.186 -0.203 -0.174, mean -0.064, deviation from mean 0.177Front left lead screw (-60,-10) is connected to Z (drive 2)
Front right lead screw (560,-10) is connected to Y (drive 1)
Back centre lead screw (250,560) is connected to X (Drive 0)Macro "4 - Leveling Check Probe":
T0 M401 G30 P0 X250 Y420 Z-99999 ; probe near a leadscrew G30 P1 X420 Y80 Z-99999 ; probe near a leadscrew and calibrate 3 motors G30 P2 X80 Y80 Z-99999 S-1 ; probe near a leadscrew M402 G90 G1 X250 Y250 T-1 ```bed.g:T0
M401
G30 P0 X250 Y420 Z-99999 ; probe near a leadscrew
G30 P1 X420 Y80 Z-99999 ; probe near a leadscrew and calibrate 3 motors
G30 P2 X80 Y80 Z-99999 S3 ; probe near a leadscrew
M402
G90
G1 Y250
T-1M584 Y5 X7 U8 V6 E3:4 Z0:1:2 ; Set up steppers for x, y, u, v, z and e, use P4 once it works to hide V
M671 X250:560:-60 Y560:-10:-10 S0.5 ; Set up lead screw positions for bed leveling -
Lars, thanks for that. The corrections it wants to make now look correct - they are similar to the height errors but with opposite sign and somewhat larger magnitude - which is expected because you are probing well inside the leadscrew positions.
As you say, it looks like the corrections may be getting applied with the wrong sign, at least for the 2nd and 3rd screws. I'll simulate your figures on my Cartesian printer (which has only 1 Z motor) and see whether there is a problem with positive corrections.
EDIT: I found the problem. When it is setting the motor direction, it sets the directions of all Z motors together instead of individually. I will fix this shortly as I am keen to get this feature working properly.
-
Lars, please try DuetWiFiFirmware 1.19beta10+3, available here https://dl.dropboxusercontent.com/u/19369680/DuetWiFiFirmware.bin.
-
21:45:43 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.275 -0.663 0.068, mean -0.290, deviation from mean 0.299 21:45:15 G32 Error: some computed corrections exceed configured limit of 0.50mm: 0.260 0.969 -0.344 21:44:34 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.274 -0.659 0.049, mean -0.295, deviation from mean 0.289 21:43:43 G32 Leadscrew adjustments made: 0.136 0.486 -0.174, points used 3, deviation before 0.210 after 0.000 21:42:42 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.148 -0.339 0.041, mean -0.149, deviation from mean 0.155 21:41:57 G32 Leadscrew adjustments made: 0.043 0.230 -0.082, points used 3, deviation before 0.094 after 0.000 21:41:19 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.010 -0.112 0.054, mean -0.023, deviation from mean 0.069Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.19beta10+3 (2017-07-21)
WiFi Server Version: 1.19beta9
Web Interface Version: 1.17+2 -
Just in case they got lost in all the back-and forth, here are the two issues I'm still seeing with 1.19beta10+2 & DWC 1.17+2:
-
M666 in config.g doesn't execute/"stick" - after a reboot M666 is always reset to [c]Endstop adjustments X0.00 Y0.00 Z0.00, tilt X0.00% Y0.00%[/c]. I don't have a config-override.g file or an M501 command in my config.g. M665 in config.g works as expected.
-
My prints are now ending with a "Can't delete file 0:/sys/resurrect.g" error, and the final lines in my gcode are not executed:
G1 X0.053 Y9.146 F540 G1 E-8.0000 F6000 ; layer end T0 ; Select Extruder 0 if not already selected G90 ; Switch to absolute mode G1 X0 Y0 Z250 E-10 F6000 ; Retract filament and raise printhead M104 S0 ; Turn off heater M84 S10 ; turn off motors after 10 seconds ```I'm guessing it might have to do with the [c]T0[/c], because the print completes, but the printhead doesn't move up and the heater doesn't turn off. I'll try a print without the [c]T0[/c] tomorrow and see if the problem goes away. -
-
David, any chance you could add the probe point data in the output together with the adjustment for the leveling?
-
21:45:43 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.275 -0.663 0.068, mean -0.290, deviation from mean 0.299 21:45:15 G32 Error: some computed corrections exceed configured limit of 0.50mm: 0.260 0.969 -0.344 21:44:34 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.274 -0.659 0.049, mean -0.295, deviation from mean 0.289 21:43:43 G32 Leadscrew adjustments made: 0.136 0.486 -0.174, points used 3, deviation before 0.210 after 0.000 21:42:42 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.148 -0.339 0.041, mean -0.149, deviation from mean 0.155 21:41:57 G32 Leadscrew adjustments made: 0.043 0.230 -0.082, points used 3, deviation before 0.094 after 0.000 21:41:19 M98 P0:/macros/4 - Leveling Check Probe Bed probe heights: -0.010 -0.112 0.054, mean -0.023, deviation from mean 0.069Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.19beta10+3 (2017-07-21)
WiFi Server Version: 1.19beta9
Web Interface Version: 1.17+2This is strange. I set up my bench system, configured as a CoreXY with your leadscrew positions and motor assignments:
M584 Y5 X7 U8 V6 E3:4 Z0:1:2 ; Set up steppers for x, y, u, v, z and e, use P4 once it works to hide V M671 X250:560:-60 Y560:-10:-10 S0.5 ; Set up lead screw positions for bed levelingI created a bed.g file like yours, except that I put the initial probe height errors that you reported in it:
G30 P0 X250 Y420 Z-0.010 G30 P1 X420 Y80 Z-0.112 G30 P2 X80 Y80 Z0.054 S3I set my Z steps/mm to 3200 so that 1mm movement is 1 revolution of the motor. I have flags on the motor shafts so that I can see the movement. I loaded firmware 1.19beta10+3. I sent G92 X0 Y0 Z10 as I don't have any means of homing this setup.
When I run G31, I get this:
Leadscrew adjustments made: 0.002 0.185 -0.117, points used 3, deviation before 0.072 after 0.000I can see the X motor moving clockwise very slightly, the Y motor moving clockwise a little less than 1/5 of a turn, and the Z motor moving anticlockwise a little less than 1/8 of a turn. I checked that when I command +Z movement, the rotation is clockwise. So it all looks correct.
Please can you check a few things:
1. Is the maximum Z speed in your M201 command in config.g achievable?
2. Are you certain that you have the motors connected to the driver outputs in the order listed? Bear in mind that the order of driver outputs along the edge of the Duet is 2 1 0 3 4 (i.e. Z Y X E0 E1) not 0 1 2 3 4.
3. Can you see the leadscrews moving by about the correct amount, in the correct direction?
-
Just in case they got lost in all the back-and forth, here are the two issues I'm still seeing with 1.19beta10+2 & DWC 1.17+2:
-
M666 in config.g doesn't execute/"stick" - after a reboot M666 is always reset to [c]Endstop adjustments X0.00 Y0.00 Z0.00, tilt X0.00% Y0.00%[/c]. I don't have a config-override.g file or an M501 command in my config.g. M665 in config.g works as expected.
-
My prints are now ending with a "Can't delete file 0:/sys/resurrect.g" error, and the final lines in my gcode are not executed:
G1 X0.053 Y9.146 F540 G1 E-8.0000 F6000 ; layer end T0 ; Select Extruder 0 if not already selected G90 ; Switch to absolute mode G1 X0 Y0 Z250 E-10 F6000 ; Retract filament and raise printhead M104 S0 ; Turn off heater M84 S10 ; turn off motors after 10 seconds ```I'm guessing it might have to do with the [c]T0[/c], because the print completes, but the printhead doesn't move up and the heater doesn't turn off. I'll try a print without the [c]T0[/c] tomorrow and see if the problem goes away.Thanks for your report.
I can't reproduce the M666 problem, it works on my delta. Please share your config.g file. If you run M98 Pconfig.g subsequently, does it pick up the correct M666 settings?
I don't know why the last few lines of gcode are not being executed. Is tool 0 active at the end, or is some other tool active? Do you have anything in the tool change files for tool 0?
The "Can't delete" message will be fixed in the next beta.
-
-
-
My M666 command wasn't "taking" because I put it before my original block of mechanical configuration commands, one of which was [c]M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them[/c]. So the first M666 was just getting clobbered (PEBCAK).
-
I was also wrong about the issue at the end of a print. I'd switched printing profiles to one that (I didn't notice this at the time) didn't have an ending script with a Z raise. Then when the print finished without moving the head off the print, I looked at the gcode console and saw the "Can't delete" error, so I assumed they were related, and then I managed to look at the wrong gcode when I was "confirming".
Dave, one of these days I swear I'm going to stop wasting your time and actually be helpful… I really appreciate your patience.
-
-
No problem!
