mini ir probe - G33 fails
i got one of these IR probes and it works fine with my bed
when i run G33 i get a fail when its 75% done, but it does not say why :-/
my config is here: https://pastebin.com/7PwY7yQs
i have manuel tested that my probe can reach the points i have defined
using the latest DEV downloaded today - the machine is NOT an delta, i just use G33 so i can store my beds disortion in eeprom and only do an G33 every other week
what could be wrong?
when i run G33 i get a fail when its 75% done, but it does not say why :-/
my config is here: https://pastebin.com/7PwY7yQs
i have manuel tested that my probe can reach the points i have defined
using the latest DEV downloaded today - the machine is NOT an delta, i just use G33 so i can store my beds disortion in eeprom and only do an G33 every other week
what could be wrong?
Comments
that is why i attached my config just in case i screwed up the config
it has a mat black surface like recommended for these ir probes... only in the corner there are some white logos to prevent stupid people from getting burned... on top i have a PEI sheet
i have tried to use a black permanent marker to cover those logos to see if it makes a difference..
it does about 75% of the 22x22 probe points and then fails
You have a Y min= 23.5
You have probe Y offset=28
You min P1 P2 Y =28-23.5 = 4.5
Allso, looks like you have coma's instead of fullstop in the bed dimension settings (not sure if this may cause errors).
it fails arround those positions anyway
when homed the nozzle is at Y-23.5 and the probe is then at Y4.5
since this is an IR probe it can be picky about things and give false signals... just as a test i have placed some black duct tape arround the board as to give it tunnel vission downards and to minimize ir light going direct to the board
22x22 points take a long time but so far it looks good
i tried to replace them with periods in the online config tool but it seems to replace them back to comma's
if my current test runs good i will try and replace the comma's back to periods once more
and from there slowly enlarge my probe field so i get as close to the border i can
current settings are: https://pastebin.com/WT3G7ytj
but it still fails near the end.... it could have been nice that the error box in repetier host told why it failed
was it because it could not reach the next point or was it something with the probe trigger
or would it in fact start to probe and fail when it tries to go to the pos?
then its strange as the fail happen only when it goes in the x direction... never when it goes from one y pos to the next... i could understand if the fail happen at the last point on X before it goes to next line on Y and starts over...
hope that made sense
i lowered number of points pr axis to 11 and it worked, will repreat 2 mor times to see if it is a success each time
after that i will try and expand the area so i get closer to edge
it did home but it then it tried to home again without respecting the endstop... what a loud noise
i do have a few older versions of the dev firmware but i doubt it will change anything
now i have enlarged the area just a bit and it had one fail... on the 2nd attempt now
is there any setting i can use to make it a bit more imune or forgiving to false triggers? like more probe repeats ??
I know on the reprap forums, ppl have tried painting the underside of their glass bed with black paint.
As a side note,maybe 22x22 probe points is too much for the memory available in eeprom, i would try 6x6 and work up from there if successful.
right now testing with 11x11 points but will lower it and try again
its just a pain to use since i have to remove the hotend while i use it (takes up to much space) and the downside to that probe is that i cant get close to the edges...
the ir can get alsmost to the edge and i have checked with manual moves that i can to the points i have in the config.
more laters
there are one corner where it triggers early for some reason... its the same every attempt so i would rule out false triggers
sadly that corner is the first point for the last row so i dont know if the rest of that row is ok
there is about 12mm difference on that corner and the only numbers i can think of is that it goes up 10mm between probe points and i have set it to go up 2mm to untrigger the probe
the 10mm is also time consuming so i will try and lower that to like 1 as it would allready go up 2mm to untrigger and 1 extra is plenty in my case
also placed a kitchen towel arround the bed at that corner to rule out that the surrounding machine parts reflects ir
i checked that if the probe stays under 6 or 7 mm it will not trigger false in that corner
will try with sandpaper on the pei in that corner.... i bet if those stupid white logos was not there it would not have been a problem
Also a 22x22 grid is a bit overkill even though it fits, so regarding your success rate I would go with 11x11 or 10x10 you you have a realistic chance to finish.
Height map in host is tricky if it failed. It is counting responses so you need to restart host if measuring fails.
Remember that z probe bed distance is also set in eeprom overriding your config.
and every time i flash firmware i do a M502 followed by M500
probe cant be adjusted :-(
some info from the serial line:
i reduced to 5x5 just to make it happen faster
is there somewhere i can force it to use a ref of say 10 or less? just to test if that is what determines how far it goes up
in disortion.cpp
float z = RMath::max(EEPROM::zProbeBedDistance() + (EEPROM::zProbeHeight() > 0 ? EEPROM::zProbeHeight() : 0), static_cast<float>(ZHOME_HEAT_HEIGHT)); //EEPROM::zProbeBedDistance() + (EEPROM::zProbeHeight() > 0 ? EEPROM::zProbeHeight() : 0);
only one of them could give an result of more than 5 and that is ZHOME_HEAT_HEIGHT, funny enough in configuration.h that is set to 20, but on the online config tool i searched all pages for "ZHOME_HEAT_HEIGHT" but it was no where to be found... is this a static set number or is it just called something else on the config web page?
will try and reduce it to 6 just to see if it makes a difference
now i will push my luck and try and get to extreme edge of board and see what happens
where are the homing options with preheat? and do it require that i have a delta?
for some reason the probe at some few spots report a bigger difference and that makes it fail.
i have tried to shrink the probe area and change the amount of probe points pr axis
what would it take for me to change the code to ignore these cases and replace the value it got with something that is between what it got at the point before and the one after?
so something is wrong and i bet if there was an ignore parameter it would work