Probing issues
-
@medicusdkfz said in Probing issues:
For me the G30 S-3 before a mesh bed leveling seems more logical than a simple G30
G30 S-3 assumes the current Z position value is correct and can be used to determine how far the probe moved when it was triggered.
You want to use G30 to set the Z=0 datum - which assumes the Z trigger height value in G31 is correct.
Frederick
-
@fcwilt But this doesn't solve, that the trigger signal isn't shown in the right way... And the G30 S-3 have to have the same distance all over the bed after a mesh or at the gantry level probing points. But that isn't so...
-
@medicusdkfz said in Probing issues:
But this doesn't solve, that the trigger signal isn't shown in the right way
I don't know what you mean.
And the G30 S-3 have to have the same distance all over the bed after a mesh or at the gantry level probing points. But that isn't so...
Again I don't know what you mean.
Using G30 to set the Z=0 datum is only done at one XY position and always at the same position.
I use the center of the bed as that position.
You need to set the Z=0 datum before...
- creating the height map for mesh compensation using G29
- loading an existing height map previously created using G29
You need to set the Z=0 datum after...
- using the manual bed leveling assistant (if you do that)
- using the auto bed leveling feature (if you do that)
-
@fcwilt I also do this. You can see it in my code snippets above...But sometimes you can see a trigger value of P=1000 in the web gui (with a red background) or on the display and sometimes not. And for my opinion it has to sense always - of course with a small difference, but it has to sense... That's my problem. I don't trust the hardware... And I've tried it with different z-values in the G31 from -0.1 up to 2 mm...
-
@medicusdkfz said in Probing issues:
@fcwilt I also do this. You can see it in my code snippets above...But sometimes you can see a trigger value of P=1000 in the web gui (with a red background) or on the display and sometimes not. And for my opinion it has to sense always - of course with a small difference, but it has to sense... That's my problem. I don't trust the hardware... And I've tried it with different z-values in the G31 from -0.1 up to 2 mm...
But using that G30 S-3 changes the Z trigger height setting in G31 meaning the result of the subsequent G30 will be wrong.
Also I'm not sure why you find you have to run have that conditional code in your bed.g file. My bed.g simply probes the bed near the locations of each of the three Z steppers and I invoke bed.g twice with two G32. That always obtains accurate leveling.
-
I suppose I still have a thinking error when calibrating the Z height in G31. So far I have followed the instructions in the wiki. I have done a homing of all axes, then a quad gantry levelling and a G28 Z again.
All this at 110 degrees bed temperature and heated the nozzle to 260 degrees. Then I moved the nozzle to the center of the bed and lowered it to the paper surface so that the paper could still be moved with some resistance. Then followed a G92 Z0 and several G1 Z5 and G30 S-1 commands.
The determined value was then entered in config.g as Z-value at G31.
But actually, after G92 Z0, I should have moved the inductive sensor over the former nozzle position in the middle of the bed, right? I have an offset Y-position from nozzle to sensor of 25 mm....
Of course, it would be best if the sensor position would match the nozzle position. This would mean that I get reliable values only from Y > 25, because I can drive with my nozzle only to Y=0 but not into the minus... -
... and now I get the error again and again: "Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh."
To fix the mesh bed levelling is getting me me mad...The papertest with G28 Z (z microswitch) is ok!
-
You seem to be on the right track.
Yes you want to probe the spot where you touched the nozzle to the bed.
I always use the center of the bed for both of those operations.
Of course after you determine the correct value for the Z trigger height parameter for the G31 you have to be sure that the G31 command gets executed.
The probe X and/or Y offsets will limit where you can move the probe to as you near the edges of the bed - that's perfectly normal.
Frederick
-
@medicusdkfz said in Probing issues:
... and now I get the error again and again: "Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh."
To fix the mesh bed levelling is getting me me mad...The papertest with G28 Z (z microswitch) is ok!
So you do the equivalent of...
- move to Z=5
- move the nozzle to the center of the bed
- jog Z so to just touch the nozzle to the bed
- execute G92 Z0 to establish the Z=0 position
- move to Z=5
- move the probe to the center of the bed
- execute G30 S-1 to determine the probe trigger height
- enter that value into G31 as the Z trigger height parameter
- execute the G31 command with the new parameter (however you do that)
Now at that point to verify that all is working as it should be I...
- move to Z=5
- execute G30 to set the Z=0 datum using the new G31 Z trigger height parameter
- move to Z=5
- move the nozzle to the center of the bed
- move to Z=1 and use a 1mm thickness gauge to verify the gap (or move to Z=0 and use paper)
All should be good.
Now to make all that easier I have created a few macros to save time and keystrokes.
Frederick
-
That all is logic and clear to me and is working right now. But when I perform the G30 and perform a mesh bed levelling (G29 S0) I get this warning...
-
@medicusdkfz said in Probing issues:
That all is logic and clear to me and is working right now. But when I perform the G30 and perform a mesh bed levelling (G29 S0) I get this warning...
You need to go back and do the G30 with G29 to create a new height map.
Then the G30 with G29 S0 should load the height map without issue.
Frederick
-
Sorry, that is exactly what I have done (line 32 in my mesh.g)... And than I get this warning!
But thank you for your help!
-
@medicusdkfz said in Probing issues:
Sorry, that is exactly what I have done (line 32 in my mesh.g)... And than I get this warning!
I cannot find where you execute G30 after leveling the gantry but before creating the height map.
In the bed.g file I see where you execute G28 Z but in the homez.g file I see that you are homing to an end stop switch but I don't see G30.
Frederick
-
In my mesh macro you will find in line 15 a G32 command and after that before the G29 S0 the G30...
-
@medicusdkfz said in Probing issues:
In my mesh macro you will find in line 15 a G32 command and after that before the G29 S0 the G30...
Yes I see that but you also have to do a G30 BEFORE creating the height map as well as before loading a height map.
Also remember that you don't need to load the height map after just creating it - the height map remains loaded after creation until something else unloads it.
Frederick
-
I have done all this, but this doesn't explain the warning... I go a step further and perform with every print a mesh. I know, that's an overkill, but I suppose, that the thermal expansion is not consistent. But again: I don't understand the warning...
@medicusdkfz said in Probing issues:
... and now I get the error again and again: "Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh."
To fix the mesh bed levelling is getting me me mad...The papertest with G28 Z (z microswitch) is ok!
-
Is there any perspective of help here? If it has a professional service, I would also pay for it... The issue is important to me and I would like to get it solved!
-
@medicusdkfz said in Probing issues:
Is there any perspective of help here? If it has a professional service, I would also pay for it... The issue is important to me and I would like to get it solved!
Can you show us where you perform the G30 before creating the height map?
Frederick
-
@medicusdkfz shall we start a fresh?
Post your latest files.
Your original comments around the value not always showing in DWC when probing, the DWC doesn't update quick enough to show the change in value, but don't worry, its being recorded at the correct trigger height -
Ok, thank you for your help... I will deliver this evening the necessary information.
