Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add options for z-hop function #429

Closed
belm0 opened this issue Aug 29, 2020 · 2 comments
Closed

add options for z-hop function #429

belm0 opened this issue Aug 29, 2020 · 2 comments

Comments

@belm0
Copy link

belm0 commented Aug 29, 2020

Behavior

  • Describe the problem
    z-hop of slicer is not flexible (vertical hop only). There are conflicting requirements (reduce blobbing, avoid hitting existing extrusions) which cannot be addressed by this simple function.
  • Expected Results
    add control over z-hop function (raise it during wipe according to non-linear function, etc.)

promising results here: prusa3d#2507 (comment)

Is this a new feature request?
yes

@supermerill
Copy link
Owner

supermerill commented Aug 29, 2020

please explain more.
"etc" is not enough for me to implement it.

Also, did you try the "extra wipe for external perimeters", do you think this should be used before every z-hop?

@supermerill supermerill added the awaiting response Further information is requested label Aug 29, 2020
@n8bot
Copy link

n8bot commented Aug 29, 2020

I just added a comment to that PS issue, talking about how IceSL handles their zhop/travel moves. They do it diagonally, which has the beneficial side-effect of slowing down nozzle speed just before "unlifting," which helps to alleviate ringing that can sometimes occur in the pritn move that directly follows a fast travel move.

@supermerill supermerill added also in prusaslicer and removed awaiting response Further information is requested labels Jun 4, 2021
supermerill added a commit that referenced this issue Nov 4, 2021
 * At the first move, merge Z-move and don't split the travel, so the printer won't "dance", whatever where the nozzle is.
Note:it's a hack, please redo it properly when reworking gcode-writer.
 * retract_lift_first_layer is gone back to the old simple behavior (revert b16ecbf)
 * removed auto extra lift for first layer, now that lift_min exists.
 * with complete object, don't unlift at object/first layer change, to avoid Z-dance
 * lift_min will be used between brims, skirts, objects but not between object-skirt, object-brim and their object
#1783
#1775
#1575
#599
#429
#395
#241
supermerill added a commit that referenced this issue Nov 6, 2021
 * At the first move don't split the travel
 * At the first move, if start_gcode_manual and no layer_gcode, don't lift the nozzle so the printer won't "z-dance", whatever where the nozzle is.
Note:it's a hack, please redo it properly when reworking gcode-writer.
 * retract_lift_first_layer is gone back to the old simple behavior (revert b16ecbf)
 * removed auto extra lift for first layer, now that lift_min exists.
 * with complete_object, don't unlift at object/first layer change, to avoid Z-dance
 * lift_min will be used between brims, skirts, objects but not between object-skirt, object-brim and their object
#1783
#1775
#1575
#599
#429
#395
#241
supermerill added a commit that referenced this issue Nov 6, 2021
Also change other behaviors to be compliant:
 * At the first move don't split the travel
 * At the first move, if start_gcode_manual and no layer_gcode, don't lift the nozzle so the printer won't "z-dance", whatever where the nozzle is.
Note:it's a hack, please redo it properly when reworking gcode-writer.
 * retract_lift_first_layer is gone back to the old simple behavior (revert b16ecbf)
 * removed auto extra lift for first layer, now that lift_min exists.
 * with complete_object, don't unlift at object/first layer change, to avoid Z-dance
 * lift_min will be used between brims, skirts, objects but not between object-skirt, object-brim and their object
#1783
#1775
#1575
#599
#429
#395
#241
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants