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

Filament Settings/Advanced/Print speed override does not seem to work #350

Closed
kursatu opened this issue Jul 17, 2020 · 3 comments
Closed
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@kursatu
Copy link

kursatu commented Jul 17, 2020

Version

Version of SupserSlicer used goes here
2.2.52
Use About->About SuperSlicer for release versions

For -dev versions, use git describe --tag or get the hash value for the version you downloaded or git rev-parse HEAD

Operating system type + version

What OS are you using, and state any version #s
Windows 10
In case of 3D rendering issues, please attach the content of menu Help -> System Info dialog

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

What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s
Printer: Custom corexy, Vking derivative
Firmware: Marling bugfix-2.0.x

Behavior

  • Describe the problem
    The Filament Settings/Advanced/Print speed override setting does not seem to produce anything different.

  • Steps needed to reproduce the problem
    In the Filament/Advanced/Print speed override box enter a value, say 75
    Slice
    Observe that there is no gcode change in the file. The only change is in the metadata at the very end of the file.
    Please see the meld diff attached.

    • If this is a command-line slicing issue, include the options used
  • Expected Results
    Per the tooltip description, I've expected that M200 is generated for that filament wipe in between
    ; CP TOOLCHANGE WIPE
    ; CP TOOLCHANGE END

  • Actual Results

    • Screenshots from SuperSlicer preview are preferred

Is this a new feature request?

Project File (.3MF) where problem occurs

Upload a SuperSlicer Project File (.3MF) (Plater -> Export plate as 3MF for Slic3r PE 1.41.2 and older, File -> Save / Save Project for SuperSlicer, Slic3r PE 1.42.0-alpha and newer)
Meld1

Mmu_test1.zip

@supermerill supermerill added the bug Something isn't working as intended label Jul 17, 2020
@kursatu kursatu changed the title Filament/Advanced/Print speed override does not seem to work Filament Settings/Advanced/Print speed override does not seem to work Jul 17, 2020
@kursatu
Copy link
Author

kursatu commented Jul 17, 2020

It is again super useful feature.
There should a usable, very good speed control/settings for the wipe tower.
Currently, it seems to be fixed , depending on the filament type.
For me, it would decrease the filament switch time significantly.
I recall others complaining the petg not printing because the wipe speed it too high.

Print_speed_override

@supermerill
Copy link
Owner

supermerill commented Sep 9, 2020

Okay, I axed my code when I merged with the new prusa wipe tower (new files, and I forgot to find a way to re-implement it, as the previous hooks doesn't exist anymore).

I'm trying things to re-create it.

Also, the previous behavior of default slower print with flex filament seems also axed.

@kursatu
Copy link
Author

kursatu commented Sep 9, 2020

Keep up the good work.
Just a feedback, not sure what the behavior should be preferred.
Prusa has chosen a fixed speed and slowing down via M220 for the wipe tower.
I believe it does obey the volumetric speed limit though.

My speed preference would be
1- The print speed/vol speed limit defined in the print/filament settings
2- Optionally a speed percentage via "Print speed override"
3- The same print speed/vol speed limit/print speed override should also apply to the empty grid
Currently , I am doing this (item 3 and fixed speed up from current feedrate) via a post processor.
The time wasted at the wipe tower is pretty significant, especially when printing small one-off , single copy models.
My post processor cuts it down a bit, quite worthwhile if I recall correctly.
Though , it is the slicer that should do it in the first place.

@supermerill supermerill added fixed for the next version That means that you should be able to test it in the latest nightly build and removed working on labels Sep 19, 2020
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Oct 5, 2020
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 fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

2 participants