Correction of heightmap is not really working
-
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
-
@fcwilt said in Correction of heightmap is not really working:
M98 P"probe_config.g"
ok i added it. not problem
-
@fcwilt the new z-value is 3.025
DO IT OR DON'T
-
@icy_snake said in Correction of heightmap is not really working:
@fcwilt the new z-value is 3.025
That sounds very reasonable.
Frederick
-
@fcwilt good so far
-
I've got some chores to do so I will have to leave for a while.
I will check back later.
Frederick
-
@fcwilt ok thx again, i will wait.
-
@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.
-
@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
-
@fcwilt Good morning Frederick,
please can we finish today our files. Let me know when you had breakfast.
Wish you a good day.
Dieter -
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
-
@fcwilt hello frederick,
no problem, take your time.
-
@icy_snake All files are fine, i tested them single command.
-
Well if those files are all working you are almost done.
What do you want to work on today?
Frederick
-
@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 offsetor i am wrong??
DO IT OR DON'T
-
@icy_snake also a macro to setup the z?
DO IT OR DON'T
-
@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 offsetor 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
-
@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
-
@fcwilt yes lets do a macro. so whenever i change my bed from glass to aluminium i can run a new setup
-
@icy_snake said in Correction of heightmap is not really working:
@fcwilt yes lets do a macro. so whenever i change my bed from glass to aluminium i can run a new setup
Is there are reason to think the correct value for each would be different every time you changed the bed material?
Frederick
