Force Duet calibration heightmap?

dc42

The height map is both activated and saved to the SD card when you run G20 S0 or just G29, but it is not loaded automatically when you restart the Duet. So include G29 S1 in your homing sequence or your slicer start gcode if you always want to use bed compensation.

peirof

One question…

Compensation works only when start a 3d print?

or

Does Duet also use it in the movements that are made with DWI? (Without any file to print)

I mention it because it would be interesting to be able to try the Heightmap without having to send a piece to print

peirof

I think this is already answered … but I can not find it.

When I start a compensation ... the gcode M557 is executed, and depending on the parameters it has, it does so ...

but ... you can (I think so), adjust what goes up in Z before trying each point, and the speed of displacement between points.

I would like to reduce a little the amount that goes up in Z, and increase some speed (this I have less interest), so that the autocalibration is faster, since with a bed of 340 mm in diameter, if I take samples every 15mm. ... well ... it takes a while ...

peirof

another question…

i have edited, text editor [c]heightmap.csv[/c]

and the contents are:

[[language]]
RepRapFirmware height map file v2 generated at 2018-01-03 09:21, mean error 1.903, deviation 0.574
xmin,		xmax,		ymin,		ymax,		radius,		xspacing,	yspacing,	xnum,	ynum
-105.00,	105.10,		-105.00,	105.10,		140.00,		35.00,		35.00,		7,		7
      0,  	2.872,	  	2.759,  	2.600,  	2.434,  	2.297,          0
  2.892,  	2.740, 	 	2.602,  	2.416,  	2.227,  	2.040,  	1.880
  2.636,  	2.548, 	 	2.414,  	2.265, 	 	2.027,  	1.861,  	1.686
  2.412,  	2.398,  	2.201,  	2.009,  	1.838,  	1.623,  	1.425
  2.086,  	2.035,  	1.872,  	1.688,  	1.460,  	1.372,  	1.149
  1.749,  	1.651,  	1.500,  	1.350,  	1.188,  	1.038,  	0.961
      0,  	1.311,  	1.260,  	1.125,  	0.960,  	0.799,          0

What is the meaning of colums? What represent?[c]xmin, xmax, ymin, ymax, radius, xspacing, yspacing, xnum, ynum[/c]

dc42

When bed compensation his enabled, all XY movements except homing moves and G1 S2 moves are subject to bed compensation.

You can adjust the probing speed and height parameters in the M558 command. See the GCodes wiki page.

dc42

The labels near the top of the height map file refer to the numbers in the line that follows. That line holds the M558 parameters that were used when the height map was generated, followed by the numbers of points along the X and Y directions.

peirof

@dc42:

When bed compensation his enabled, all XY movements except homing moves and G1 S2 moves are subject to bed compensation.

You can adjust the probing speed and height parameters in the M558 command. See the GCodes wiki page.

For a Delta…. What is a recommend speed?

dc42

The recommended speed depends on the type of Z probe. The IR probe should be ok at 1000mm/sec, and probably quite a lot higher before repeatability starts to suffer.

peirof

I am triying things… and

1- First calibrate
2- In config.g adjust Zoffset of G21
3- Run Compensation, with few points, for test pourposes

and...

How can see, the graphic is far from 0…. what i have to do, for graphic will be near of grid z=0?

dc42

That suggests to me that your Z homing was not accurate before you ran G29.