Still having issues with "Probe samples exceed sample_tolerance"
All my belts have good tension according to shaper graphs, and my bed mesh is .116 on my 500. I've also made sure my mag sheet and pei sheet are clean, and the hot end is completely free of filament. I can't tighten my couplers any further. I'm unsure where to go from here.
Am I having issues with missed steps on my Z motors? Often times I will get a poke test where the first and second numbers are very similar on the poke test, or even identical to each other, which seems strange.
Solution:Jump to solution
i nuked all my cfg files and started from scratch, zero mechanical changes, and now ratos calibrate is workign and im at the contact mesh point, been running for about 18 minutes now
53 Replies
Here's another example. This was during a contact test.
Same thing, again.
It's amazing how it manages to make the 2 separate numbers so close to each other on repeated pokes, but doesn't get the actual test correct. no clue where to begin fixing this.
Possible it's PID issues with my hot end? Probe point still goes up while the hot end says it's at temp
Is the Configurator supposed to give me a warnign about the PT1000 sensor? I have the jumper on the ebb42 board as instructed by the build guide
yes
this one
the range keeps going up until it settles and then passes the poke test
unlikely, it would have to fluctuate significantly, what does your temp graph look like?
it seems fine, but the dotted line is all over the place
that's PWM for ya.
Can you show me a pic?
yeah let me heat it up again, doing that right now
I'm also seeing this on the ebb42 board diagram, we don't have to do this?
the "PT Choose"
it seems fine
Starts high and then goes low
Like the poke test starts before the temp is correct
sigh
idk what to do
you're not using the MAX31685
this looks completely normal
i saw that after, but the ebb42 has the same dip switchs, i wast just wondering if it mattered
if not, great
enable performance mode in the hardware configurator
it's enabled
Then it's time to go over every single screw in your toolhead and z assembly
Make sure you've hot tightened your nozzle etc etc
i'm positive i've got them all cranked but i can try again
you can enable this part again, it will improve accuracy:
however i believe i made that the default
ok, i will, i commented it out thinking maybe it was wrong despite advices
Ah i only made it default on the IDEX.
And everything is updated, yeah?
right yes, just did im on the RC3 now
and everythgin else
👍 then it's all about mechanicals at this point
so make sure everything is tight
oh, i'm pretty sure my rear z screw is bent, i can visibly see it wobble when it spins
that could be it?
oh the dip switches arent there lol.
i've got everything as tight as they can be without stripping them
isn't this a ridiculous amount of variance from when it says it's at temp and starts the poke test, and then when it actually passes the poke test? it goes from .069 all the way up to .097 before setting on .095.......
how does this even happen
from .016 to .094 in the span of a few pokes.....
Solution
i nuked all my cfg files and started from scratch, zero mechanical changes, and now ratos calibrate is workign and im at the contact mesh point, been running for about 18 minutes now
no clue
it completed
hooray!
Sorry for all the struggles, but glad you're on the other side of it now 🙂
now hopefully my first layers stick
have to work on that later
Honestly really upset
It looks good except for when it started and the outer wall didn't stick. Never had an issue like this, no clue where to begin
This is beyond crazy, I assume I need to re calibrate my beacon?
@Rewire This looks like a messed up z-axis
This is a big red flag
Obviously your hotend doesn't contract when heated..
Yeah looks like your hotend expansion is delayed quite a bit.
@Rewire add this to
[gcode_macro RatOS]:
variable_hotend_heat_soak_time: 300
Then rerun BEACON_RATOS_CALIBRATEwill do, thanks
just to note, i did manage to sort this out, i think
in another thread
Ah in that case don't mind me 🙂
well im having issues again after a few days lol
switched to PLA and its like it has amnesia so
ill sort it out