-
Notifications
You must be signed in to change notification settings - Fork 2k
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
G-code flavor "No extrusion" not working like description in tooltip suggests #6023
Comments
I was able to reproduce it. |
This issue is still present in PrusaSlicer 2.3.3 |
Fix of #6023 The fix is partial: No extrusions are shown by the final G-code preview.
The "No extrusion" firmware flavor was never complete. IMHO the "No extrusion" firmware flavor was not a good idea to implement in the first place. What is your use case for it? |
Thank you. If i find the time, i will compile the master branch myself and can give feedback here.
That issue would have been a future feature request of me. Without closer looking at how the code really works, i assume you relay soley on the extrusion moves instead of G1 moves. Which is a pitty in that case. Maybe there could be an exception be made in case there are no extrusion moves found in the gcode. So that there are some sane default values taken into consideration for "virtual" extrusion moves just for the sake of displaying some lines for the movements.
The initial usecase which led to this issue post was, that i was stress testing my klipper firmware and its host-system to find out at which speed the firmware shuts down, creates stutters or generally behaves strange. And i wanted to make those tests as a dry-run. So i had to remove all extrusion moves and knew that PS has this "No extrusion" flavor. Of course that would be possible with a post-processing script too and some regex magic, but yeah. Why not using a function which is inbuilt. In the meantime though, i saw a support question on the klipper discord that someone was asking what's the best way to slice gcode for a plotter. he converted his 3D-printer to a plotting machine basically and only needs x, y and limited z moves. this question dragged me back to this issue, wondering if it got fixed in the meantime. I assume that plotter like machines probably don't want to be targeted by PS but maybe there are some more usecases for a working no extrusion flavor which i overlooked now. |
The original issue should be solved? Can we close this? |
Yes, sorry i totally forgot to report back. |
@th33xitus Thanks. I'll close the issue then. I'm not sure how to deal with the "G-Code Viewer shows no extrusions when there are no extrusions" problem (although I understand there may be valid use cases). If you think it is worth considering, please, open a new issue. |
Version
2.3.0
Operating system type + version
Win10
3D printer brand / version + firmware version (if known)
Firmware: Klipper
Behavior
The g-code flavor "No extrusion" is described as preventing PrusaSlicer from exporting any extrusion value at all.
This at least is the description from the g-code flavor tooltip.
In reality, PrusaSlicer does export something. To be more specific, the generated g-code will look something like this:
This is the part of the g-code where the brim is printed. Instead of exporting values for E, only zeroes are exported. But E is omitted. This causes export of non valid g-code. Not only Klipper will throw an error with such g-code i assume, i am certain any other firmware will do too.
I also observed that in combination with spiral vase, the is NO MOVEMENT generated at all.
After the falsy brim g-code i see something like this:
Only layerchanges will be exported, without any movement in between.
Also the estimated printing time for that particular file with spiral vase and no extrusion combined is estimated at 37 seconds.
The same object sliced with no extrusion but marlin flavor is estimated at 15 minutes.
Here are 3 different g-code files: g-code.zip
Shape-Cylinder_NoExtrusion_Vasemode
This file will show you the faulty g-code export i am referring to in this issue right now. It was sliced with the no extrusion g-code flavor and bein in vasemode aka spiral vase.
Shape-Cylinder_NoExtrusion_NoVasemode
This file is for comparison, showing that slicing the same object without vasemode aka spiral vase but using no extrusion will export the movements, but also exports faulty g-code.
Shape-Cylinder_Marlin_Vasemode
This file is for comparison, showing that slicing the same object using marlin as g-code flavor and vasemode aka spiral vase exports working g-code.
The object which is sliced in this case is a simple shape cylinder, generated within PrusaSlicer itself:
The text was updated successfully, but these errors were encountered: