Comments (9)
When sending smaller prints it did worked well. However when the print was almost full 350x350 bed, this happened. I agree with the users above. Check that there is no minus values or values over max bed size?
from print_area_bed_mesh.
Is your probe offset configured properly?
from print_area_bed_mesh.
OFFSET
x_offset: 0.0
y_offset: 23.0
So i think, it is.
from print_area_bed_mesh.
If the probe offset is indeed correct then I suspect the "variable_buffer: 20" line may be causing issues.
can you move the model farther away from the side of the bed ? and confirm you do not get negative values anymore.
from print_area_bed_mesh.
I did see this error once, I resliced my model without a skirt and that did the trick.
That being said I should check my probe offset vs mesh min/max, I may have done it wrong, possibly.
Can the macro ommits the buffer in case of model too close?
It is likely not the correct syntax. I think whats happening is the print size is comparing the user mesh limits then if that checks out the generous buffer is too much. The user can lower the buffer or extra macro check?
Below is an exemple of my reasoning, the syntax is likely wrong. I would have tested it but I'm currently printing something.
{% if print_min_y|default(0)|float - buffer % >= mesh_min_y %}
{% set mesh_min_y = print_min_y|default(0)|float - buffer %}
{% else %}
{% set mesh_min_y = print_min_y|default(0)|float %}
{% endif %}
from print_area_bed_mesh.
I have had this issue as well. It IS in fact the buffer, as i have reduced it to 5 and had no issues since.
Check that you part is less than the 20mm buffer from the edge, or reduce the buffer size in the Print_area_bed_mesh.cfg. The file however is not editable directly in mainsail, so I edited it with WinSCP, and now I have a "Dirty" install, which I'm prompted to recover.
from print_area_bed_mesh.
Very rough, there is probably a better syntax to get it done but this works on my end.
It checks if the buffer can be used, if its out of range it will just do the full mesh per our mesh config.
I tried a model of a cube that I enlarge to the max dimensions of my bed, prior to this code it would output values my probe could not get to.
{% if print_min_x|default(0)|float - buffer >= mesh_min_x %}
{% set mesh_min_x = print_min_x|default(0)|float - buffer %}
{% else %}
{% set mesh_min_x = mesh_min_x %}
{% endif %}
{% if print_min_y|default(0)|float - buffer >= mesh_min_y %}
{% set mesh_min_y = print_min_y|default(0)|float - buffer %}
{% else %}
{% set mesh_min_y = mesh_min_y %}
{% endif %}
{% if print_max_x|default(0)|float + buffer <= mesh_max_x %}
{% set mesh_max_x = print_max_x|default(0)|float + buffer %}
{% else %}
{% set mesh_max_x = mesh_max_x %}
{% endif %}
{% if print_max_y|default(0)|float + buffer <= mesh_max_y %}
{% set mesh_max_y = print_max_y|default(0)|float + buffer %}
{% else %}
{% set mesh_max_y = mesh_max_y %}
{% endif %}
from print_area_bed_mesh.
It should be fixed in the latest version.
from print_area_bed_mesh.
@issic Can you please confirm whether you're still having the issue with the latest update?
from print_area_bed_mesh.
Related Issues (20)
- bed_mesh: invalid probe_count option
- Feature Request - relative reference index to use the lowest Z point probed
- Feature Request: Dynamic Bed Mesh Size eg 5x5 vs 3x3
- No longer using old mesh HOT 1
- slicer param print min & max cannot be passed to klipper
- Consider bed temperature when deciding if new mesh should be created or not HOT 1
- Internal error bed mesh calibrate HOT 10
- Can't install the macro through PuTTY HOT 3
- Orca slicer Plate system causes problems. HOT 1
- Unknown command:"PRINT_MIN=109.378,100.38" HOT 1
- how to deinstall?
- Can't get it to work, need a little help HOT 1
- it works but i noticed i still need to adjust my z offset
- How do I iinstall this on my Creality Sonic Pad which runs Klipper HOT 1
- Won't work. But ChipCE code does. HOT 2
- Euclid Stow instead of Deploy
- The reuse function is not working at all
- Feature Request - Add Parameter PROFILE for BED_MESH_CALIBRATE
- Didn't worked in Orca Slicer at first PRINT_MIN > AREA_START
- Bed Mesh ignores BlTouch x&y offset
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from print_area_bed_mesh.