Correction of heightmap is not really working
-
@fcwilt
</ homeall.g>
M280 P0 S60 I1
G91 ; relative positioning
G1 H2 Z5 F200 ; lift Z relative to current position
G1 H1 X-605 Y605 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y-5 F600 ; go back a few mm
G1 H1 X-605 Y605 F600 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G30 ; home Z by probing the bed
</>< /homex.g>
; homex.g
; called to home the X axis - DUAL ENDSTOPS
G91 ; relative positioning
M913 X50
G1 H1 X-605 F3000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F600 ; go back a few mm
G1 H1 X-605 F600 ; move slowly to X axis endstop once more (second pass)
M913 X100
G1 H2 Z-5 F200 ; lower Z again
G90 ; absolute positioning
</>< homey.g
; homey.g
; called to home the Y axis
G91 ; relative positioning
G1 H2 Z5 F200 ; lift Z relative to current position
G1 H1 Y605 F3000 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F600 ; go back a few mm
G1 H1 Y605 F600 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F3000 ; lower Z again
G90 ; absolute positioning< homez.g
; homez.g
; called to home the Z axis
M280 P0 S60
G91 ; relative positioning
G1 H2 Z5 F200 ; lift Z relative to current position
G90 ; absolute positioning
G30 ; home Z by probing the bed< rehome.g
M280 P0 S60
G91 ; relative positioning
G1 H2 Z5 F200 ; lift Z relative to current position
G1 H1 X-605 Y605 F3000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 Y-5 F600 ; go back a few mm
G1 H1 X-605 Y605 F600 ; move slowly to X and Y axis endstops once more (second pass)
G90thats ok so?
-
Here is an example of a mesh.g file adjusted for your values.
M98 P"config_probe.g" ; insure probe is using most recent configuration values G29 S2 ; cancel mesh bed compensation M290 R0 S0 ; cancel baby stepping G90 ; absolute moves ; --- set Z=0 datum which is needed for creating a heightmap G1 Z5 F99999 ; insure Z starting position is high enough to avoid probing errors G1 Xaaa Ybbb ; move probe to center of bed - set values aaa and bbb as appropriate G30 ; do single probe which sets Z to trigger height of Z probe M557 X20:600 Y20:620 S58 ; define mesh grid 420 points S58 G29 S0 ; probe bed and create height map
-
@fcwilt ok understand
-
When homing the Z axis with a G30 you need to precede it with a G1 command to move to the center of the bed.
I don't know what the M280 P0 S60 is for - I don't have it in my code.
You also have some M913 commands - I have not found it necessary to use those.
You have a file rehome.g - what is that for?
Frederick
-
@fcwilt
I have no idea for what they are using M280, because i have no servo to set any position.Not sure why they change the current for the stepping motors.
I believe they copied many codes together to get it running
-
@icy_snake
@fcwilt ok understandso we have the bed.g and the mesh.g
now we need to finish the config_probe.g to call the others?
I have the following questions.
How will i get the z-offset value in the g31 command?
do we also generate a z_offset.g?
thx
Dieter -
@icy_snake
Frederick are you there?? -
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
-
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
-
@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.