New edge firmware 1.17dev8 (replaces 1.17dev7)

dc42 · 8 Dec 2016, 17:16

Can you post the heightmap.csv file generated by a G29 that giving you bad results?

heathmanc · 8 Dec 2016, 17:43

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

dc42 · 8 Dec 2016, 18:52

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?

heathmanc · 8 Dec 2016, 18:53

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.

dc42 · 8 Dec 2016, 19:04

Is it just the Z height that is behaving wildly, or X and Y as well?

dc42 · 8 Dec 2016, 19:12

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.

heathmanc · 8 Dec 2016, 19:22

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.

dc42 · 9 Dec 2016, 14:28

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.

Adamfilip · 11 Dec 2016, 00:00

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.g

M557 X20:260 Y0:240 S10 ; define a grid covering the XY area indicated with the specified grid spacing

Sending G29 to activate

Adamfilip · 11 Dec 2016, 00:02

hmm when i increased Spacing from S10 to S20 it started working.

dc42 · 11 Dec 2016, 00:49

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.

Adamfilip · 11 Dec 2016, 03:47

Ok.. What is the max limit of points?

Firebug24k · 11 Dec 2016, 04:53

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.

Adamfilip · 11 Dec 2016, 05:57

Grid leveling is working incredibly well. Never had such a good first layer over my entire bed.

Thank you DC42

dc42 · 11 Dec 2016, 07:47

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.

32034 · 12 Nov 2016, 11:36

@dc42:

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 printer

M557 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

dc42 · 11 Dec 2016, 17:23

No, I mean set up the XYZ offsets in your G31 command, and G29 will use them.

Adamfilip · 12 Dec 2016, 01:59

is there a way to fade the grid correction after a certain amount of layers. I noticed that its still adjusting Z height even after 50mm of print height.

jnofsinger · 12 Dec 2016, 03:44

Hello,

I am trying to run the new grid correction and running into an issue. I have this in my config.g
G31 X0 Y0 Z19.4 P500

and the bed file

G30 P0 X0 Y0 Z-99999

; Probe the bed and do 6- or 7-factor auto calibration
G30 P0 X-73.6 Y-42.5 Z-99999 ; X tower
G30 P1 X0 Y-85 Z-99999 ; between X and Y towers
G30 P2 X73.6 Y-42.5 Z-99999 ; Y tower
G30 P3 X73.6 Y20 Z-99999 ; between Y and Z towers
G30 P4 X0 Y67 Z-99999 ; Z tower
G30 P5 X-73.6 Y20 Z-99999 ; between Z and X towers
G30 P6 X-36.8 Y-21.25 Z-99999 ; half way to X tower
G30 P7 X36.8 Y-21.25 Z-99999 ; half way to Y tower
G30 P8 X0 Y42.5 Z-99999 ; half way to Z tower
G30 P9 X0 Y0 Z-99999 ; centre, and auto-calibrate 6 factors
G30 P10 X0.00 Y40.00 Z-99999 ; Z tower
G30 P11 X-34.64 Y20.00 Z-99999 ; between Z-X towers
G30 P12 X0 Y0 Z-99999 S6

M557 R90 S20
G29

The auto calibration works fine for my delta. When it runs the G29 command the zprobe doesn't report/trigger properly (it is 19.4mm) above my bed. It pushes my probe out of the way down and gives the message

"Zprobe triggered before probing move started" (if the printer is not homed to top)
OR
"Zprobe was not triggered before probing move" (if the printer is homed before running)

I assume the G31 isn't being read for G29? what option do I need to set for the probe to trigger correctly? Sorry if this has been answered for a delta, haven't found it in the threads.

Thanks,
Jim

dc42 · 12 Dec 2016, 08:19

I think that your very large Z probe trigger height has exposed a bug in the G29 probing, which I will fix in today's release.