New edge firmware 1.17dev8 (replaces 1.17dev7)
-
Removed Duet WiFi prototype 1 build
Please excuse my ignorance: does this impact the duetwifi beta boards? -
No, prototype 1 was for internal testing and only 2 boards were ever made.
-
I just found a bug in 1.17dev7: after you have printed a file from SD card, you need to reset the printer before you can do any further movement. Will be fixed soon.
-
Maybe I don't know how to use this new feature, but I homed my printer, did an autocalibrate and put the settings in the config file, did a G29 and then reset the controller. I put the G29 S1 into my startup script, but when I went to print, everything was WAY skewed, like not even resembling the part.. So, at this point, I rehomed, autocalibrated, ran a G29, and the print the file without the G29 in the beginning of it, same result. What am I doing wrong? Grid is defined with M557 R70 S20.
Charles
-
Can you post the heightmap.csv file generated by a G29 that giving you bad results?
-
RepRapFirmware height map file v1 generated at 2016-11-08 16:06
xmin,xmax,ymin,ymax,radius,spacing,xnum,ynum
-60.00,60.10,-60.00,60.10,70.00,20.00,7,7
0,0,0.119,0.070,0.194,0,0
0,0.012,0.088,-0.040,0.056,0.037,0
0.044,-0.005,-0.044,0.182,0.068,0.008,0.013
0.037,-0.010,-0.007,0.140,0.025,-0.023,-0.007
-0.018,-0.088,-0.057,0.138,0.036,-0.082,-0.181
0,0.050,-0.087,-0.075,-0.006,-0.038,0
0,0,-0.024,0.025,-0.049,0,0 -
I can't see anything wrong with your height map, although you have a couple of fairly large errors at y=-60 and X= +/- 20mm. What sort of skew are you getting?
-
I haven't let it print more than a couple of perimeters, it's pretty wild and I can't even make out what the part is.
-
Is it just the Z height that is behaving wildly, or X and Y as well?
-
OK, I think I found a problem that could explain what you are seeing. I suggest you roll back to dev6 until I have dev8 ready.
-
Ok, done! Glad I'm not completely crazy. The x and y are really skewed, z axis does some crazy things as well, especially when pausing the print.
-
I have just released 1.17dev8, which fixes the issues I introduced in 1.17. I don't anticipate making any more major changes before 1.17 release, just fixes for any new bugs.
-
Cant seem to get it working
Updated. restarted several times
"No valid grid defined for G29 bed probing" is error
this is in my config.gM557 X20:260 Y0:240 S10 ; define a grid covering the XY area indicated with the specified grid spacing
Sending G29 to activate
-
hmm when i increased Spacing from S10 to S20 it started working.
-
With your original M557 command, you should get an error message saying that there are too many probe points - except if the M557 command is in config.g then you won't see the message.
-
Ok.. What is the max limit of points?
-
DC42, on my delta I don't use any XY offset for your IR probe when running G30 autocalibration and it works fine. When I run G29 grid levelling after, should I have entered an XY offset via G31 first or not? My probe is offset about -40mm in the Y direction.
-
-
I'm glad it's working well for you!
The maximum number of points is currently 121 on the wired Duet and 441 on the Duet WiFi. However, the underlying grid is rectangular so when using a circular probing area the actual max number of points is about pi/4 times these values.
You should configure the probe offset. During auto calibration the probe offset is ignored.
-
I'm glad it's working well for you!
The maximum number of points is currently 121 on the wired Duet and 441 on the Duet WiFi. However, the underlying grid is rectangular so when using a circular probing area the actual max number of points is about pi/4 times these values.
You should configure the probe offset. During auto calibration the probe offset is ignored.
You mean that G29 should have the same X Y Z offsets as G31 in config.g?
If Z probe section in config.g looks like this,
[c]; Z probe section
M558 P1 X0 Y0 Z1 H3 F100 T5000 ; Smart IR Z probe, used for homing Z axis, dive height 3mm, probe speed 100mm/min, travel speed 5000mm/min
G31 P500 X-60.0 Y0.0 Z1.30 ;Set the probe height and threshold
[/c]then bed.g should look like this for Auto bed compensation?
[c]; bed.g
; M561 ; clear any bed transform, otherwise homing may be at the wrong height
G28 ; home the printerM557 X10:275 Y15:190 S25 ; define a grid covering the XY area indicated with 25mm grid spacing
G29 X-60.0 Y0 Z1.30 ;probe levelling grid with prob offsets from config.g
[/c]Edited. Removed .1 from G29