#PAM does not work with Beacon3D

1 messages · Page 1 of 1 (latest)

icy dust
#

the reason is that the beacon module havent implemented the mesh min and mesh max feature

#

you can file a issue on the beacon github repo

novel sorrel
#

At the speed of the beacon... why does PAM matter? you could up the bed mesh to like 50x50 without issue correct? EG: doesn't the mesh still just adjust where you are printing?

icy dust
#

and imagein, with pam you can mesh a benchie in less than a second

novel sorrel
#

oh...right.... you're talking still limiting the mesh to the PAM desfined area...but AT beacon speed to boot dooohl!

icy dust
#

even if you move super fast, the beacon measures only a small line on the bed, means if you wish a high resolutiuon you ened to wait as well

novel sorrel
#

As with the Super Pinda, when you change between beds (flex metal sheet based, garolite, and/or a carbon fiber sheet) that zero space changes. So i still feel my reversion to my BLTouch was the simplest. with PAM as you state, I get the resolution needed...WHERE I'm printing.

icy dust
#

beacon is still cool

novel sorrel
#

most definitely.

#

...would love to use one if I could figure a way to 'properly and accurately' save a bed thickness offset

icy dust
#

you can easily save and reuse variables in a gcode macro

novel sorrel
#

oh yes. but how would you prove to yourself the Beacon was reading variations in say a CF or garolite plate compared to the metal it was sensing under the plate

#

ha...those 'sanding ' videos

icy dust
#

thats already possible

novel sorrel
#

yes

icy dust
#

there are two ways

#

a dedicated plugin, or just using the mainsail presets

#

but dont let us hijack this thread

novel sorrel
#

but again... the Beacon is seeing the bed...not those non-ferrous surfaces

icy dust
#

so this still works

#

PEI is also a non-ferrous surfaces btw

#

all print surfaces are

novel sorrel
#

agreed.

novel sorrel
#

link(s) come up 404 not found!