BEACON COMPENSATION_MESH higher on POA then PEI and Powder coated
I created 9 Bed compensation meshes;
-3 build plates (Smooth PEI, Powder coated PEI and POA)
-3 temperature ranges
The 3 temperature ranges of the POA-plate are all "higher" then the other 6. Is this normal?
36 Replies
POA
Powder coated
Smooth PEI (whether or not I am going to use it the PEI bed meshes I don't know yet)
That is to be expected it depends on the substrate and how much it affects the induction
However, it would not be visible if you homed with contact before you did the POA mesh.
But regardless, nothing out of the ordinary here and they're all within a similar range.
0.15 - 0.18
You would need to redo that POA mesh after you've run
BEACON_AUTO_CALIBRATE SKIP_MODEL_CREATION=1
If you don't, you're gonna have an additional offset on POA which is undesired, as RatOS homes with contact before starting a print.
@Helge Keck we should probably build that in to the calibration macro, i thought (read: assumed) it did that already?cant follow you
We have a macro to create a contact mesh right?
yes we have
It should run
BEACON_AUTO_CALIBRATE SKIP_MODEL_CREATION=1 before it creates the mesh.
to home with contact, for proper zeroing
Or else the contact mesh is going to be offsetyou can create the contact mesh manually or while doing the calibration, but not automatically before printing
?
and you can use different contact meshes
yes.. The macro to create a contact mesh needs to home Z with contact BEFORE creating the mesh
sorry, are we talking about the scan compensation or the contact medsh
we are talking about the macro that creates the contact mesh
if you want a regulat mesh, but. with contact, then you jsut need to enable the variable
nono
okay nevermind, i'll just show you it's faster 😄
lol
maybe we should talk about names for the different meshes
contact mesh can mean multiple things now
I'm adding this
Without it the mesh will be offset in Z and you'll dig the nozzle into the plate worst case scenario.
hmmm, im sure you have deleted this recently. im sure it was in it
encapsualted in the automation variable
but i can be wrong
I didn't delete any z homing unless it did it multiple times sequentially
but i can check
i remember to have see that you removed one encapsulated z homing, maybe it was another macro
I totally did
GitHub
Beacon: prevent overwriting z-offset and clean up redundancies and ...
…297)
There were an excessive amount of redundant BEACON_AUTO_CALIBRATE commands and move commands, and every one of them was creating new models, effectively causing z_offset to be cleared every ...
That's a major fuck up on my part, that should just have been suffixed with
SKIP_MODEL_CREATION=1
fixing nowgood catch
I'm gonna go over it again and check if i made similar mistakes elsewhere
Ah, i removed it because there's a
G28 Z in _BEACON_HOME_AND_ABL, but that isn't using contact, which it should.ahh
also this
Should probably be followed by a contact home as well
agree
fixing!
Will keep the additional contact home in the scan compensation mesh creation macro, as we're doing heat soaking
GitHub
Beacon: re-zero with contact before creating scan compensation mesh...
Sanity check appreciated @HelgeKeck :D
testing
Merged (and merged into v2.1.x)!
Wow gents,... lots of reading up to do... but the conclusions still stands, @miklschmidt that the POA bed mesh is ok? Not sure when I should do BEACON_AUTO_CALIBRATE SKIP_MODEL_CREATION=1 but as for now I do not have that anywhere incorporated.
I would update RatOS and run at least the POA scan compensation mesh again. The offset will likely cause issues.
Not sure when I should do BEACON_AUTO_CALIBRATE SKIP_MODEL_CREATION=1 but as for now I do not have that anywhere incorporated.You don't need to anymore, it's now properly built into the macro (again, after i accidentally removed it)