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

wipe tower first layer grid fill far too fast #940

Closed
ghost opened this issue May 31, 2018 · 3 comments
Closed

wipe tower first layer grid fill far too fast #940

ghost opened this issue May 31, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented May 31, 2018

Version

1.40.1 beta

Operating system type + version

Mac OS

Behavior

There is a reset of the speed in gcode between wipe tower brim and wipe tower first layer grid fill.

Generated gcode looks like this..

G1 X157.302 Y71.599 F7000
G1 X97.302 Y71.599
G1 X157.302 Y71.599
; CP WIPE TOWER FIRST LAYER BRIM END
;-----------------------------------
G1 X97.802 Y57.699 F7200 <--- bad?
;--------------------
; CP EMPTY GRID START
; layer #1
G1 X97.302
G1 Y57.199
G1 X157.302 Y57.199 E3.2600

This causes the first layer to get print very fast - the first layer get ripples and get ripped off on the next layer.

In the code this is cause by line WipeTowerPrusaMM.cpp:1178 - there the speed is hard coded.
So as a user i have no chance to change this on generating the gcode file.

Please make it adjustable or slower... maybe it can be calculated from another setting.

@lukasmatena
Copy link
Collaborator

Thanks for the report. This issue is already fixed by e4aff5b, which is already in the current master and will be part of the next release (you can also compile it yourself before that). The speed was significantly decreased - the F7200 is a travel feedrate, which was not changed before printing of the fill.

@spiff123
Copy link

Great! (sorry posting with other account)
I will try that!

@bubnikv
Copy link
Collaborator

bubnikv commented Jun 4, 2018

Will be fixed in the release. Closing.

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

3 participants