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

1.9.1.67 - Layer Pause Bug Gcode on the wrong layer with Scarf Seam enabled. #4132

Closed
1 of 2 tasks
TinyMito opened this issue May 21, 2024 · 9 comments
Closed
1 of 2 tasks
Assignees
Labels
bug Something isn't working

Comments

@TinyMito
Copy link

TinyMito commented May 21, 2024

Bambu Studio Version

1.9.1.67

Where is the application from?

Bambu Lab github releases

OS version

macOS

Additional system information

MacBook Pro 14

Printer

P1S Combo

How to reproduce

I found out the gcode is pausing at 2 layers offset.

  1. 0.20mm layer height
  2. Add pause to any layers ie. Layer 57 in the screenshot.
  3. Printer actually delayed paused by two layers.
  4. I have gone in to investigate the gcode.
  5. It actually paused at layer 59 instead.

Actual results

20240521_002218

Expected results

Should pause on the correct layer.

Project file & Debug log uploads

not available.

Checklist of files to include

  • Log file
  • Project file
@TinyMito TinyMito added the bug Something isn't working label May 21, 2024
@TinyMito
Copy link
Author

TinyMito commented May 21, 2024

For 0.16mm layer height, same problem, but now it is offset by 3 layers. The printer missed the intent pause layer physically. I had to cancel the print.

20240521_002219

@TinyMito
Copy link
Author

Additional updates, it seems like it only affect model with a base raft or with support. I can provide the project file in private only. Please let me know where to share it.

@TinyMito TinyMito changed the title 1.9.1.67 - Showstop: Layer Pause Bug Gcode on the wrong layer. 1.9.1.67 - Layer Pause Bug Gcode on the wrong layer. May 21, 2024
@LiZ-Li-BBL
Copy link
Contributor

Hi,
You could share the file to liz.li@bambulab.com, we will check the problem.

@moop2000
Copy link

moop2000 commented Jun 2, 2024

I am experiencing the same issue. I've narrowed it down to the scarf joint seam feature being enabled. It doesn't matter if it's enabled per model or globally, once it is enabled in the file, the pauses will be offset. The number of layers in error appear to be affected by the layer height. In my testing, .16 layer height causes the pause to be adjusted by three layers, while .2 layer height is adjusted by 2 layers.

Layer Bug.zip
I've attached an example file. It is a standard setup with all default settings. Plate 1 is just a cube, with a pause at 10mm, which is offset. Plate 2 has a cube with scarf joint enabled just for that one object, not globally, and it is also offset. Removing that second object, plate 1 will show the proper pause location.

@nigeljohnson73
Copy link

I have just bumped into this. Also narrowed it down to scarf joins (as this is the only thing I added in my project) I'm using 0.2mm layer height, and using 20mm scarf length, the offset for me is 4 layers - requested start of layer 14
image

and it happens the start of layer 18
image

How is that even linked :D

@nigeljohnson73
Copy link

Oh, interesting proof, and if you need scarf seams... Set the pause at the place with the standard profile. Then enable scarf seems with the settings you need, and the pause will "move", but will still occur at the right place in printing.

@TinyMito
Copy link
Author

TinyMito commented Jun 3, 2024

Hi, You could share the file to liz.li@bambulab.com, we will check the problem.

The file, I sent, has scarf seam enabled. Maybe that's why the issue like many others are facing the same problem.

@TinyMito TinyMito changed the title 1.9.1.67 - Layer Pause Bug Gcode on the wrong layer. 1.9.1.67 - Layer Pause Bug Gcode on the wrong layer with Scarf Seam enabled. Jun 3, 2024
@QingZhangBambu QingZhangBambu self-assigned this Jun 3, 2024
@QingZhangBambu
Copy link
Collaborator

i will fix it as fast as possible

@TinyMito
Copy link
Author

20240611_002276

Looks good and thank you for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants