You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I have tall prints that needs z-hop because sometimes a corner will curl up or something and the print would get knocked over without zhop.
However, because of zhop, it leaves tiny wisps of stringing. If I disable z-hop, there is no stringing at all. I think is is because the printer pauses, goes straight up, and then travels.
I would love for there to be a feature that does the z travel at the same time as the travel. There would of course need to be some considerations. The vertical move would need to start just after it leaves the print, and it would need to be at max height before it crosses anything on th
e layer or 2 below the current layer.
Not only would something like this create cleaner prints, it should shave off a few minutes on prints using z-hop. The second or so it takes to do the zhop would pretty much be cut down to 0.
I've attached a picture of what I'm trying to say here.
The text was updated successfully, but these errors were encountered:
So I have tall prints that needs z-hop because sometimes a corner will curl up or something and the print would get knocked over without zhop.
However, because of zhop, it leaves tiny wisps of stringing. If I disable z-hop, there is no stringing at all. I think is is because the printer pauses, goes straight up, and then travels.
I would love for there to be a feature that does the z travel at the same time as the travel. There would of course need to be some considerations. The vertical move would need to start just after it leaves the print, and it would need to be at max height before it crosses anything on th
e layer or 2 below the current layer.
Not only would something like this create cleaner prints, it should shave off a few minutes on prints using z-hop. The second or so it takes to do the zhop would pretty much be cut down to 0.
I've attached a picture of what I'm trying to say here.
The text was updated successfully, but these errors were encountered: