Won't HOME after capacitive sensor installed
-
@phaedrux Not sure what you mean by " Is your mesh compensation accurate? ". Do I have to run the mesh comp tool once again after I find the correct height?
I was able to get the negative offset to work in the Z axis but I had to add a G30 P1 Z-.160 comand after G31 command. Should I not have to do that?
; Z-Probe
M574 Z5 S2 ; Set Z probe
M558 P5 H5 F240 T6000 I1 ; Set Z probe type to switch and the dive height + speeds
G31 P1000 X-75 Y-45 Z0 ; Set Z probe trigger value, offset and trigger height
G30 P1 Z-.160
M557 X-8:172 Y0:220 S20 ; Define mesh grid -
@excelon said in Won't HOME after capacitive sensor installed:
Do I have to run the mesh comp tool once again after I find the correct height?
I'm not really clear on that actually. I don't think so. As long as the probe is getting a repeatable result I think the mesh should be valid and the height offset would apply to all points.
But what I mean by is your your height map accurate is that if you have mesh compensation active and you move to z1 and then jog the nozzle in X and Y does it actively adjust the z axis to keep the nozzle a steady 1mm away from the bed, or does it seem to get closer or farther as it moves?
A good test of that is to print a bed level test STL that prints some lines across the surface of the bed. If the mesh is accurate it should give a consistent first layer. If it's not some areas might be too squished and others too far away.
Maybe you can post an image of your mesh compensation result. It can be easier to judge a good map just from looking at it sometimes.
Your g31 doesn't look right. The z value shouldn't be zero. Once you've used that trigger height process using g30 s-1 to measure it you should put that value there.
I'm not sure what that g30 p1 is for but it probably shouldn't be there in config.g. your problem should be resolved once you have a measured value entered in the g31 z in the line above.
Can you post your config.g and homing files as they are now as well? I think you're pretty close to getting everything in place.
-
OK. So, the mesh comp tool/map is active and working 100%. I know this because my bed is pretty messed up from pile driving the nozzle into the corner trying to figure out a few things ( my fault ). Not to mention that I didn't know how to code in the mesh mapping into my gcode and used to have to do it manually, but not anymore, thank you.
As for the G30 P1 in the config.g.... I entered it there because no matter the value I entered in the G31 line, it would make no difference. I know you have said before that I should be able to enter a Z offset in the G31 line, but it doesn't work.
NOTE: I removed the Z neg offset becuase I manually changed it but I would still like to be able to offset Z in the future in case I changed nozzles or the like.Most recent files.....
3_1545799253017_homez (1).g 2_1545799253017_homey.g 1_1545799253017_homex.g 0_1545799253016_homeall (1).g
-
Thank god for auto bed leveling
-
Your home all is a little weird since it does a fast home of x and y, then moves back a little bit and homes z, and then moves some more in x and y.
You should finish all the x and y moves first and then move the probe to the center of the bed and g30 there to get a good center point z height. Use the same coordinates for the homez for consistency.
-
Now just missing config.g
-
@phaedrux 0_1545804443527_config.g
Sorry, I missed that somehow...
-
How exactly would I clean up homeall? I have X and Y going out after the fast moves like you're talking about because of the Z probe hanging off the side of the bed. Please help to make this better if it can. This is only the 3rd day or so ive been on this so I have a lot to learn.
-
@excelon said in Won't HOME after capacitive sensor installed:
@phaedrux 0_1545804443527_config.g
Sorry, I missed that somehow...
Your max speeds and acceleration for X and Y are a little low. Fine for testing but you may want to raise them up for actual prints so you're not capping the slicer. Add a zero to the ends of the current values and you're set.
For home all I'm not sure what you mean by the probe hanging off the edge. I had posted a fixed homeall above I think.
When I get back to my computer later tonight I can post a better example. In the mean time, check the setting up a Cartesian guide in the wiki, specifically the homing files section and compare what's there to what you have to see what I mean.
-
This is what I would use for homeall.g
G91 ; relative positioning G1 Z5 F6000 S2 ; lift Z relative to current position G1 S1 X-235 Y-235 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 S1 X-100 Y-100 F300 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X190 Y160 F6000 ; put probe over the centre of the bed G30 ; probe the bed for z height G1 X0 Y0 ; return to home positionRemove the G30 P# from config.g
Then use this to find the probe trigger height
G90 ; absolute positioning G1 X115 Y115 F6000 ; move nozzle to center of bed ; Jog the nozzle down until it touches the bed ; if it gets to Z0 but still doesn't touch, send G92 Z10 to trick it to think it's at 10mm, and then slowly jog it down until it is touching. ; When it's touching, send G92 Z0 G30 S-1 ; do a trigger height measurement probe The result of the trigger height will be shown in the console. Use that value in G31 Z in config.g Now when you homez it should give you an accurate Z position. Z0 should touch the bed. -
@phaedrux said in Won't HOME after capacitive sensor installed:
G90 ; absolute positioning
G1 X115 Y115 F6000 ; move nozzle to center of bed
; Jog the nozzle down until it touches the bed
; if it gets to Z0 but still doesn't touch, send G92 Z10 to trick it to think it's at 10mm, and then slowly jog it down until it is touching.
; When it's touching, send G92 Z0
G30 S-1 ; do a trigger height measurement probe
The result of the trigger height will be shown- list itemin the console. Use that value in G31 Z in config.g
Thank you for the homeall.g!!! It's so much cleaner and a lot less movements. I am understanding the code more and more, and then it even helps more to get your version and see it in action and what I could have done.
As for the config.g code. Am I replacing the Z-probe section altogether? Current z-probe is as follows...
; Z-Probe
G29 S1
M574 Z5 S2 ; Set Z probe
M558 P5 H5 F240 T6000 I1 ; Set Z probe type to switch and the dive height + speeds
G31 P1000 X-75 Y-45 ; Set Z probe trigger value, offset and trigger height
M557 X-8:172 Y0:220 S20 ; Define mesh grid
-
The way you have the zprobe section right now is fine, you g31 just needs a Z parameter. You et that from measuring the trigger height as described.
-
@phaedrux Thats the problem, though. entering a Z height in the G31 line like you mentioned doesn't have an effect.
-
What value do you get when you measure it with g30 s-1?
-
@phaedrux
Ok, Sorry. I think I get it now. Lowering the nozzle to the bed and tricking the software to think its higher, AND THEN registering zero when it’s at its lowest point and touching the bed. Now, when entering a negative Z value on line G31 will allow it to go beyond the -0- threshold and to the squish zone where I have been killing myself to get to? -
Well the measured value will likely be positive because the probe is above the nozzle and should trigger before the nozzle actually touches the bed. But then it should make z0 equal z0 and 0.2 equal 0.2.
-
@phaedrux I get it and it should work but I must have something off somewhere because it works and the nozzle is close to the bed and where I would want it for printing but as soon as I start the print its too high again.
These are the steps I'm taking and the results:
- Homeall which is great now thanks to you.
- Home Z ; which brings the probe over the center of the bed (same as homeall) but doesn't bring it back.
- Once over the middle of the bed and the 5mm dive height specified I run the G30 S-1 and it bring the nozzle all the way down to the bed and Z is reading -0.37 in the Duet webserver status.
BUT.... - When I intioniate a print the lowest Z goes down to in the webserver status is 0.20 which is too high.0_1545932907319_config (3).g [0_1545932923234_homeall (2).g]
-
@excelon said in Won't HOME after capacitive sensor installed:
Home Z ; which brings the probe over the center of the bed (same as homeall) but doesn't bring it back.
You mean you are doing home all, and then homez?
Once over the middle of the bed and the 5mm dive height specified
You mean you are sending G30 S-1 while it is 5mm above the bed, or when it's touching the bed?
When you do G30 S-1 there should be a result shown in the Gcode console. What does it say?
-
@phaedrux I think I got it figured out, but I am not able to change the Z height in config.g on command 31 like you said.
Yes, I am doing homeall and then homez. When I hit homez there is no return, only dive height return. Homez jogs out over the middle of the bed and lowers the nozzle until the sensor goes off and then returns +5mm Z height and stays there. From there I try and send G30 S-1 command but the sensor is still active and I get an error message stating that the probe is already active or sensing ( sorry, not by the printer at the moment ) so it wont lower the nozzle lower without manually raising it first. Then I tried what you recommended in your post about tricking Duet (G92 Z10) and I can finally lower the nozzle all the way to the bed like you mentioned. Once on the bed I run G92 Z0 and that zeros out the Z status and I raise the nozzle to the correct printing postion and note the positive number in Z status and added that to command G31 in config.g BUT..... when I go to print the nozzle is not all the way down on the bed and I now have to use babystep +/- 0.05 to raise the nozzle. If i go back into config.g and add "1mm" to command G31.... still nothing. I was under the impression that the number specified in the G31 command in config.g, whether is be -/+, is supposed to offset the Z height.
To answer your question. Yes, I was sending G30 S-1 after homez and couldn't until I manually raised the nozzle because the sensor is closed at that time ( or open, depending on type of sensor ). After I do everything you advised me of... tricking Duet to be 10mm higher and moved the nozzle to the bed, run G92 Z0, raise the nozzle to printing height, gcode console read 0.48 and that's what I entered in command G31 in config.g, but again.... still nothing. Only difference is now the nozzle in slap on the bed surface.
-
Ok, follow these steps exactly. It sounds like you're doing extra things that aren't needed.
Home all. Don't hit home z after. This will home all the axis and return to 0,0.
Use the axis jog buttons to move the probe to the center of the bed, and lower the z axis as low as it will go.
If the nozzle touches the bed, send G92 Z0.
If it doesn't quite touch the bed, send G92 Z10 and then jog it down until it does touch the bed, and then send G92 Z0.
Now send G30 S-1. The probe should raise up on its own and then lower again until the probe triggers.
The g-code console should give you a z probe trigger height. That number will be used in G31 Z in config.g
Do you still get 0.48?
If you repeat the steps to move the nozzle to touch the bed, send G92 Z0, and then G30 S-1 a few times in a row, do you get pretty close to the same result each time?
Are you running a G29 after this to map out the bed?
