Recalibrating Z on a Delta
-
G31 X0 Y12 Z3.093 P500 ; Set the zprobe height and threshold (put your own values here)
This is config.
G31 T1 P500 X0.0 Y12 Z3.093
G31 T3 P500 X0.0 Y0.0 Z0.00
G31 T4 P500 X0.0 Y0.0 Z0.00This is in config-override.g
-
Something is wrong in the steps above. After an auto calibration the hotend is always above the print surface by the value in G31 Z parameter.
-
For some reason config-override.g has 3 G31 commands -
G31 T1 P500 X0.0 Y0.0 Z0.00
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P500 X0.0 Y0.0 Z0.00??
config.g has -
M558 P1 X0 Z0 H10 ; Z probe is an IR probe and is not used for homing any axes
G31 X0 Y0 Z2.234 P500 ; Starting overMaybe M558 needs Y0 ?
Send G31 X0 Y0 Z2.234 P500 and then M500 to update config-override.g. You probably created the config-override.g file before you put the G31 command in config.g.
You can add Y0 to the M558 command, but it it the default anyway.
-
Send G31 X0 Y0 Z2.234 P500 and then M500 to update config-override.g. You probably created the config-override.g file before you put the G31 command in config.g.
You can add Y0 to the M558 command, but it it the default anyway.
I have always had the G31 command in config.g.
THAT might be the problem. Delete G31 and leave M558.
Delete config-overide.g
Reboot.
THEN calibrate.
Standby….... -
Your R is wrong.
https://d2t1xqejof9utc.cloudfront.net/screenshots/pics/e9555e5af170ca229a9231ded5f2d736/original.JPG
R is the Delta Radius.
You need to home before Auto Calibration, so leave that in there. What they were eluding to is to not have a home command in the beginning of your print file gcode if you want to run a calibration before a print.
Ok, I measure R and it is 97.5mm. Thanks, retesting.
MUCH BETTER!!!!!!!!!!!!!!!!!!!!!!!!!!! Tallness is more inline with the actual. Width is better. Size is better!
It is still smaller than what it should be, but wow what a difference. How to make it print bigger? More R? -
Send G31 X0 Y0 Z2.234 P500 and then M500 to update config-override.g. You probably created the config-override.g file before you put the G31 command in config.g.
You can add Y0 to the M558 command, but it it the default anyway.
I have always had the G31 command in config.g.
THAT might be the problem. Delete G31 and leave M558.
Delete config-overide.g
Reboot.
THEN calibrate.
Standby…....Hmmm…
I changed Z height to 355.000, rebooted..
Followed commissioning IR probe directions.
New G31 command is G31 X0 Y0 Z2.96 P500 ; removed from config.g, rebooted, followed directions on commissioning IR probe.
Added this to config.g but did not reboot. Instead, I pasted this G31 command into the G code console.Auto Delta Calibration #1 -
Calibrated 8 factors using 16 points, deviation before 8.461 after 0.150Auto Delta Calibration #2 -
Calibrated 8 factors using 16 points, deviation before 0.227 after 0.138Home,
Lower hot end 400mmThe result is the hotend stops before reaching the print bed.
It seems to stop immediately when the LED comes on the IR probe.I swear there is a bug with the dive height on first run… The first time through on power up, is different than next runs!!! Can someone please confirm?
Set M558 command to H20 (I use H10) just to be obvious… Reboot, home, Auto Delta Calibration...Powercycle the Duet... Home, Move down 400mm and the result is the hotend stops at the print bed!!!!!!! YES!
Do I NOT run Auto Delta Calibration EVER again?Can we set up a Skype and get this worked out?
-
Trying to do it manually, I am in this endless loop of changing end stop offsets and height settings using the paper technique at the center, X, Y, and Z towers. Center is nice, move to a tower, it is either too tight or too loose, make adjustment using M666, then center gets loose, adjust height, then towers are tight/loose again.
-
Are you using config-override.g at all?
-
Is there any chance that you can get a piece of glass to fit the build plate? Remove all of the tape and clean the residue off. Paint the bottom side of the glass black and tomorrow night, 22 1/2 hours from now, I'll get on Skype and help you. Let me know your user name.
-
Hi,
I am using glass.
Dont want to paint it. -
I swear there is a bug with the dive height on first run… The first time through on power up, is different than next runs!!! Can someone please confirm?
No bug that I know of, but I suspect that the H parameter in the M665 command in your config.g and/or config-override.g file is a long way from the true value.
-
So what is next?
-
If you don't want to paint the bottom side of the glass, do you have a piece of black paper to put under it? Need to get accurate readings from the sensor.
-
If I was to paint the glass, would I paint the top or the bottom? – Sorry I see you said bottom. Hmm.
Are we saying blue masking tape is not the right type of material to use for this probe?
How about white?
How about kapton tape?
How about some other material to use as a test for the probe?One other thing, my kossel is a mini, it uses 2020 extrusions for towers and 3 wheels for the sliders.
Perhaps I should look to replace those with 4 wheel versions? The three wheel has some play in it.But yeah, let's get good reading from the probe, it may help fix my incredibly high H parameter (dive height).
I still say there's a difference between the first run and future runs. -
It isn't the color of the tape, but just the application itself. If you could get the pieces exactly aligned with each other, with no gaps, no humps, it might work. Plain glass painted black on the bottom, or even a black piece of paper under the glass, is what DC42 has recommended. You don't want anything that might let the IR through to distort the reading.
If you don't have a config-override.g file that you are saving the results to, or don't copy the results to the config.g you will have weird results the first time compared to the next. If you get .300 before and .050 after on the first test, save the results to config-override.g with M500. If you don't save the results, I "believe" the results from the first test are still in memory and so the next test may end up like .060 before and .050 after. I am pretty sure they have to be kept somewhere because you can run a bed level test before a print without anything being saved.
So, what do you want to do? I'd like to help, but don't want to chase my own tail. We could even use Teamviewer to allow me to connect to your computer and control your Duet if you'd like.
-
Blue masking tape should work well with the IR sensor. What the IR sensor doesn't like is transparent surfaces with a light surface below, because then it sees two reflections, one from the top of the transparent surfaces and one from underneath.
-
/cry
-
I offered to help.
-
Update here:
I've worked a bit with Number40fan on a few things..
We found we were not getting a consistent reading from the IR probe when calibrating it and wanted to address this before going further. I replaced the IR probe with a newer version.
Both IR probes' LED will tend to flicker when it is at the trigger point if you let it sit there long enough; is this expected?
I've been working on updates to the effector with the creator, added M3 nut holes for rods to attach to, beveled the rod mounts for more range of motion, created IR probe mount in code rather than copy/paste job. Over the last week I've printed about 5 different effectors.
During my experimentation, I discovered that the IR probe will actually go back to a reading of 1 if the probe gets TOO close to the bed. I think my probe may have been too low compared to the location of the hotend, possibly causing false readings inbetween probe points. (is that even possible?) - Taking the leap of faith on this, I've moved the IR probe mount up 2mm from the previous location, it sits about 4mm above the bed now vs 2mm.
I discovered there are some dimensional inperfections on the printer I am using to print the effector on. That is, when adding the M3 nut holes to the rod mounts, the nuts were a very tight fit on the X axis but the Y and Z axis were just fine. I do not now how this would translate into offsets for an effector, not even sure if it is enough to be concerned with, which is why I mention it here, possibly reprint on another printer and see how it works. I can imagine this being a common issue?? Then I can imagine it not being one too..
Ok back to Reprap firmware…
Number40fan and I made changes to bed.g, config.g files, trying to keep track of everything I may have missed something and find that when I go to kick off a bed leveling job, coordinates that 'should' be reachable suddenly send the head flying off the bed and causing issues with crashing pullies, bad. Here is an example -
Homing the printer then sending the command G1 X0 Y75 Z5 moves the hotend toward the Z tower, ok, now, change this to a bed probe -
G30 P0 X0 Y75 Z-9999 (for example)
and the head will go flying off the print area. I have had to cut it down to Y55 to make it fit, only to find the same problem later on down, when Y was -75.. Y-75 .. poor printer.Tonight I plan to confirm all wires and connections are good and firm, no bad readings.
Any words of support or thoughts are greatly appreciated.
-
It's usual for the IR sensor LED to flicker if you position it right at the trigger height. It's also usual for the LED to go off again if you move the sensor is very close to the bed. Neither of these causes a problem when doing normal bed probing, because each probing move starts at the trigger height plus dive height.
What surface are you using with the IR sensor now: the glass or the blue masking tape?
