adding beacon mesh points?

[static swift]

Running ratOS 202 with beacon revH

Is there an easy way to add a bit to my printer cfg that will allow me to increase the resolution of my beacon bed mesh? It’s not bad as is, but I think more resolution would help. It makes an S shape which looks to me like 3x3 points. I’d like to just up this to like 20x20 or so since it’s so quick. ✌️

[crimson vault]

add a block to you printer.cfg like this. Use values appropriate for you printer this blis from my 500.
zero_reference_position = the center of your bed
probe_count is the value you asked about
mesh, min and max will be extreeme poins of the scan and should be smalled than t your bed
[bed_mesh]
speed: 250
zero_reference_position: 250, 250
horizontal_move_z: 5
probe_count: 25,25
fade_start: 1.0
fade_end: 10.0
mesh_pps: 2,2
algorithm: bicubic
bicubic_tension: .2
mesh_min: 20,30
mesh_max: 480,460

[static swift]

If I already am using the limited mesh macro from ratOS, could I just add a:
[bed_mesh]
Probe_count: 25,25

And it’ll use everything else that’s existing?

[crimson vault]

give it a shot

[static swift]

😊 thanks for the reply. I’ll post results. ✌️

[static swift]

No effect. Still defaults to the 3x3. It’s probably hard coded somewhere in Mikl’s macros.

[crimson vault]

did you put it in user overrides?

[static swift]

Yes.

I’m digging thru his macros now. Looks like it’s in macros.cfg
There’s a section called start print bed mesh. There’s a bunch of perams in there. But where they get defined in somewhere else

Calibrate adaptive mesh.
x0 x1 y0 y1 must be the outer dimensions of your print

Maybe it’s in default profile

[crimson vault]

turns out I put my setting in the [bed_mesh] block in the printer config section after the [stepper_z2] section.

I had to change the mesh_min values because the y_offset was causing move out of range errors

[static swift]

His macros spell it out in variable math based on your print I guess. It’s beyond my knowledge base. @cedar flare ?

There’s a section called calculate mesh point resolution. Probably in there. It must over ride a bed mesh section in your config. Not sure.

Maybe it’s a ratOS 202 thing with beacon that’s not quite compatible. 🤷‍♂️

[cedar flare]

@crimson vault 2.0 configuration is written with EVA in mind, that means the default bed_mesh and z_tilt configs assume a probe offset to the left. When you move it to the back (as in the case of beacon), you'd have to modify the bed_mesh min/max and z_tilt points to fit your particular mount.

I might've tagged the wrong guy, sorry 😂

[cedar flare]

Adaptive bed mesh keeps the resolution, you can read about how it works in the docs.

so if you have a 100mm plate and 4 points you get 1 point each 25mm of print.

If you want more, increase the points.

like you've done here:

[bed_mesh]
Probe_count: 25,25

You prolly want more than that with beacon

You can pretty much go nuts in X for example, only additional y points increase mesh time.

i usually do 100,25

[static swift]

Thanks mikl for the details. I’ll re read the docs on adaptive mesh.

Can you explain why even after putting that code into the overrides area of printer.cfg the movements of the mesh appear the same?

I have a square S shape that to me appears to need more Y detail so the shape changes to more of a snake with many more side to side movements than what appears to be 3 Y coordinate scans.

[cedar flare]

In that case, just increase the Y points. Try 100x100 if you think you need higher resolution.

[static swift]

I have 25,25 in there now to test it and it appears to be 3,3. I only see 3 y passes.

[static swift]

🤦‍♂️ Ok ok. Measure twice. Cut once. I’m sorry for wasting your time when you’re trying to get bigger things out to everyone. My bed mesh was misplaced in the printer.cfg file. I’m re running/testing now. 🙏

🐍✅

[visual haven]

Thank you for marking this question as solved!

Learn more

https://answeroverflow.com