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

Empty G1 before starting bridging perimeter #7714

Closed
WizardUli opened this issue Jan 9, 2022 · 4 comments
Closed

Empty G1 before starting bridging perimeter #7714

WizardUli opened this issue Jan 9, 2022 · 4 comments

Comments

@WizardUli
Copy link

Version

Version 2.4.0

Operating system type + version

NixOS, nixpkgs#ff377a78794d412a35245e05428c8f95fef3951f

3D printer brand / version + firmware version (if known)

MK2.5S 3.10.0-142

Behavior

'Empty' (i.e. without parameters) G1 command is emitted before starting some of bridging perimeter.

slicer

Project File (.3MF) where problem occurs

bridge.zip

@WizardUli
Copy link
Author

This may be related to or even causing #1284 (comment) !
Perhaps the G1 commands should be there and contain some crucial step preventing beginnings of bridging perimeters becoming too thin or outright starting in mid-air whole millimeters after edge.

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 10, 2022

From https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.4.0-beta2 change log:

Empty G1 commands were sometimes present in the G-Code due to the cooling slow down logic. This is an old bug present in 2.1.0 already #3058 #5176

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 10, 2022

The previous occurence of empty G1 was fixed with 4e9f906

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 10, 2022

This one was fixed with 07d0484

@bubnikv bubnikv closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants