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

[Request]G-code on per filament setting #319

Closed
sarf2k4 opened this issue May 26, 2017 · 7 comments
Closed

[Request]G-code on per filament setting #319

sarf2k4 opened this issue May 26, 2017 · 7 comments

Comments

@sarf2k4
Copy link

sarf2k4 commented May 26, 2017

Would like to ask some validation whether or not this is feasible because on the recent slic3r release, the linear advanced has been removed in the printer section.

I read several topics regarding the linear advanced where you would adjust the K values to maintain constant pressure inside the hot end.

To my knowledge from reading those topics, it is different from material type and even if both abs material also might have different K values.

What's more is that printing with different material also gives a possibilities that the user has to adjust the z-offset while printing. With this, hopefully enables the user to add a z-offset change g-code without to fiddle from the lcd panel anymore, provided that the user knows the correct settings for a good layer height.

@Sebastianv650
Copy link

I don't believe two ABS materials will have different K values. If both are realy ABS and not some alloy, the spring constant (and K is nothing else in the end) will be the same.
Nevertheless, you are right when you say seperate start gcode sections linked to the selected filament would be helpful to set LIN_ADVANCE K and simmilar. I also made the experience that PLA needs another z offset than PETG, which I guess comes frome the different printing temperatures and therefore different expansion of the hot end and bed due to heat.

@sarf2k4
Copy link
Author

sarf2k4 commented May 26, 2017 via email

@sarf2k4
Copy link
Author

sarf2k4 commented May 26, 2017 via email

@tcm0116
Copy link
Contributor

tcm0116 commented May 26, 2017

I submitted a similar request in #265, but there's been no discussion on it.

@sarf2k4
Copy link
Author

sarf2k4 commented May 26, 2017

@tcm0116 , maybe your description not catchy enough? ;P

I guess another workaround is to use the post processor but not all of us know how to use it including me nor the right software to use it either

@fiveangle
Copy link

I agree with this - if only so we can set a different Z offset: PETG indeed requires very different offset that PLA, and it is tedious to try and guestimate the amount required in the livestepping.

bubnikv added a commit that referenced this issue Jun 5, 2017
@bubnikv
Copy link
Collaborator

bubnikv commented Jun 5, 2017

Implemented with ad3be1a

Based on the implementation by @lordofhyphens
slic3r/Slic3r@19eea19

@bubnikv bubnikv closed this as completed Jun 5, 2017
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

5 participants