Correction of heightmap is not really working

ICY_SNAKE

@icy_snake
Frederick are you there??

fcwilt

I made a mistake on the mesh.g file and have edited it to include the call to config_probe.g.

The bed.g file already had it.

Since the Z parameter for G31 is pretty much "set and forget" I don't use any sort of macro to set it.

I do have a macro to set the Z=0 Datum at the center of the bed - which consists of the G1 command to move to the center of the bed and the G30 command to probe and set the Z=0 datum.

At that point you can verify that the Z=0 Datum was set correctly by using the DWC "jog" buttons to move to Z=0.

If you end up touching the bed before reaching Z=0 then the Z parameter in the G31 is too large by the value displayed for Z.

If you reach Z=0 and are not just touching the bed then the Z parameter in the G31 is too small by the size of the gap between the nozzle tip and the bed.

Once I have determined the value needed, I edit the config_probe.g file and run the Z=0 Datum macro again to be sure all is good.

Frederick

fcwilt

@icy_snake

I also forgot to mention that you should include an M98 P"probe_config.g" command in the config.g file just so the probe is configure after a reboot or reset.

Frederick

ICY_SNAKE

@fcwilt said in Correction of heightmap is not really working:

M98 P"probe_config.g"

ok i added it. not problem

ICY_SNAKE

@fcwilt the new z-value is 3.025

fcwilt

@icy_snake said in Correction of heightmap is not really working:

@fcwilt the new z-value is 3.025

That sounds very reasonable.

Frederick

ICY_SNAKE

@fcwilt good so far

fcwilt

@icy_snake

I've got some chores to do so I will have to leave for a while.

I will check back later.

Frederick

ICY_SNAKE

@fcwilt ok thx again, i will wait.

Phaedrux

@fcwilt said in Correction of heightmap is not really working:

The folks at modix don't seem to know what they are doing.

I think it's a case of Modix not having updated their configs for RRF3 yet.

fcwilt

@phaedrux said in Correction of heightmap is not really working:

I think it's a case of Modix not having updated their configs for RRF3 yet.

Maybe so but some of the config file had v3 syntax. I didn't get the impression @ICY_SNAKE did it - but perhaps.

Frederick

ICY_SNAKE

@fcwilt Good morning Frederick,

please can we finish today our files. Let me know when you had breakfast.

Wish you a good day.
Dieter

fcwilt

@icy_snake

Hi,

I'm just about to make breakfast. Give me 30 minutes or so.

Have you had a chance to verify that all is working with:

homeall.g
homex.g
homey.g
homez.g
bed.g
mesh.g

Frederick

ICY_SNAKE

@fcwilt hello frederick,

no problem, take your time.

ICY_SNAKE

@icy_snake All files are fine, i tested them single command.

fcwilt

@icy_snake

Well if those files are all working you are almost done.

What do you want to work on today?

Frederick

ICY_SNAKE

@fcwilt the config_probe.g

which has only the following lines:

; config_probe.g
; config the probe and call the other files.g
;

M950 S0 C"duex.pwm5"
M558 P9 C"zprobe.in" H5 F120 T6000 A5 R0.7
G31 P500 X-18 Y24 Z3.025 ; z value is offset

or i am wrong??

ICY_SNAKE

@icy_snake also a macro to setup the z?

fcwilt

@icy_snake said in Correction of heightmap is not really working:

@fcwilt the config_probe.g

which has only the following lines:

; config_probe.g
; config the probe and call the other files.g
;

M950 S0 C"duex.pwm5"
M558 P9 C"zprobe.in" H5 F120 T6000 A5 R0.7
G31 P500 X-18 Y24 Z3.025 ; z value is offset

or i am wrong??

That is all you need. As mentioned by calling that file with M98 in bed.g, mesh.g, etc. you are sure the probe is configured with the most recent values. No need to reboot or restart to get config.g processed.

Frederick

fcwilt

@icy_snake said in Correction of heightmap is not really working:

@icy_snake also a macro to setup the z?

I was under the impression you had determined a good value for the Z parameter in G31.

As mentioned normal that value is "set and forget" unless your hardware changes.

I suppose I could code a macro to determine that value but as you know it is going to involve setting the physical Z position to some known value to serve as a reference.

Would you like to have such a macro?

Frederick