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

[BUG] retract_lift_first_layer connection with retract_lift #1783

Closed
qwewer0 opened this issue Nov 3, 2021 · 1 comment
Closed

[BUG] retract_lift_first_layer connection with retract_lift #1783

qwewer0 opened this issue Nov 3, 2021 · 1 comment
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build

Comments

@qwewer0
Copy link

qwewer0 commented Nov 3, 2021

Describe the bug
When retract_lift is set, the retract_lift_first_layer feature seems to be included on the first layer z lifts.
On the following image retract_lift_first_layer is turned off and the retract_lift is set to 1mm, but the travel height on the first layer is 1.6mm (with 0.2mm layer height).
If retract_lift_first_layer is turned on, the outcome is the same.

To Reproduce
Steps to reproduce the behavior:

  1. Turn off retract_lift_first_layer
  2. Set retract_lift to a non zero value, e.g. 1mm
  3. Slice an object, e.g. default box
  4. Turn on travel moves on the gcode view

>> Project File <<

Shape-Box.3mf.txt

Screenshots

image

Desktop (please complete the following information):

@supermerill supermerill added problem bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build and removed problem labels Nov 3, 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
@qwewer0
Copy link
Author

qwewer0 commented Nov 5, 2021

Fixed, Thanks.

@qwewer0 qwewer0 closed this as completed Nov 5, 2021
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
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build
Projects
None yet
Development

No branches or pull requests

2 participants