#Inconsistent first layer on the extremities on a vcore pro with newest ratos

26 messages · Page 1 of 1 (latest)

cyan elk
#

Hello everyone, so i rebuilt my vcore pro and then tried with the ratos defaults to print a large 300x300 grid finity tray on the 315x310 build area, but the corners were not consistent
I thought maybe the issue were the conservative edge coordinates of the beacon, so i spent more time today fine tuning the max stepper x,y size and maxing out the z_tilt/bed mesh coordinates

i redid the compensation mesh and installed a 2504AC instead of my old ratrig generic steppers

brave lynxBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

cyan elk
#

those are 60x60 squares on all edges

#

thats my height map, nothing out of the ordinary if you ask me

#

and im using

[z_tilt]
z_positions = 
    0,0
    150,315
    315,0
points = 
    15,0
    158,285
    300,0

[bed_mesh]
mesh_min = 15,25
mesh_max = 300,305
probe_count = 11,11

[stepper_z]
microsteps: 16

[stepper_z1]
microsteps: 16

[stepper_z2]
microsteps: 16

[printer]
max_z_velocity: 15
max_z_accel: 60
#

thats what i tried

earnest moss
#
  1. What toolhead are you using? Please share a few photos, notably showing the beacon and nozzle relationship,.
  2. Does the configured beacon offset match the physical reality?
  3. What is your gantry made of (alu?)? Please share a few photos of the printer overall.
  4. What heatsoaking are you performing?
cyan elk
#

i thought i had nailed down the issue to a wobbly z axis/instable

#

thats why i modded the original xy joiners to add some spring loaded nuts into a 420mm extrusion for extra stiffness

#

which did lower my score on the poke test from 7 or so to 3

#

its a vcore pro frame, with longer z rails for a roughly 300x300x400 size

#

that was before my fix

#

its the ratrig toolhead 1.0 with a rapido uhf, so it should be all good?

#

i played around/asked gemini for some thoughts/ideas, it tweaked my beacon/ztilt values for some other probing points
thats a cold mesh

#

and thats the ratos mesh from the last square test with a fresh comp mehs

#

for the heatsoak im doing

[gcode_macro RatOS]
variable_beacon_adaptive_heat_soak: True
variable_bed_heat_soak_time: 300
cyan elk
#

im trying again now without any of my custom z_tilt, bed_mesh positions 🤔

cyan elk
#

I guess my y extrusions are not parallel?
Or bowed/twisted idk

#

That's with vcore pro defaults

#

Left middle and left top

cyan elk
#

Seems to me that the issue was a too low heatsoak time