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

Command line slicing bad gcode #5029

Closed
StefanRaatz opened this issue Oct 30, 2020 · 7 comments
Closed

Command line slicing bad gcode #5029

StefanRaatz opened this issue Oct 30, 2020 · 7 comments

Comments

@StefanRaatz
Copy link

Version

_Version 2.3.0-alpha2+win64

Operating system type + version

Windows 10 Pro Version 10.0.19041 Build 19041

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

Creality Ender 3

Behavior

Corrupt GCODE after slicing via command line

Command for sclicing:

.\prusa-slicer-console.exe -s --loglevel 5 "~\rough_stone_wallinchAfullopenforgeopenlocksidepegs.stl"

The log shows no error.

SlicingLog.txt

GCODE:
image

When I slice the same model via GUI everything works fine.

Thanks and best regards
Stefan

@bubnikv
Copy link
Collaborator

bubnikv commented Oct 30, 2020 via email

@StefanRaatz
Copy link
Author

StefanRaatz commented Oct 30, 2020

Why this is a ZIP file? Just because I entered ~ to shortenup the path?

Added the --gcode to the cmd line and added the ini file I exported from Prusa slicer to get the exact same settings like on the GUI.

.\prusa-slicer-console.exe -s --gcode --repair --loglevel 5 --load "C:\Users\Stefan\Downloads\PrusaSlicer_config_bundleEnder3.ini" "C:\Users\Stefan\Downloads\rough_stone_wallinchAfullopenforgeopenlocksidepegs.stl"

Now I'm getting an error which is fine:

Object name: rough_stone_wallinchAfullopenforgeopenlocksidepegs.stl
Print z: 6.350000

This is usually caused by negligibly small extrusions or by a faulty model. Try to repair the model or change its orientation on the bed.
Flow::mm3_per_mm() produced negative flow. Did you set some extrusion width too small?

When the same error would appear within the GUI, but there the object is sliced without any errors or repairing.

Br
Stefan

@StefanRaatz
Copy link
Author

Tried different things now and couldn't get it to work

What works:
Open stl file in GUI export as amf and then slice it via cmd line to GCODE.

What's not working:
Export to AMF via CMD line and then slicing to GCODE.

I don't know what the GUI is doing to create a working file vs what the cmd ling args are doing.

@lukasmatena
Copy link
Collaborator

lukasmatena commented Oct 30, 2020

I reproduced the problem. What is happening is that it slices in SLA mode and names the output file as gcode instead od sl1. It is definitely a bug.

Likely cause is that it formats the output filename according to input_filename_format using its default value, which is [input_filename_base].gcode. It seems to happen in SLAPrint::output_filename. It should be fixed. Someone should fix it.

@StefanRaatz
Copy link
Author

@lukasmatena is that fix already comitted to the master? If so I would like to compile and test if that fix worked.

@lukasmatena
Copy link
Collaborator

@StefanRaatz I'm sorry, my statement that "It should be fixed" was ambiguous. What I meant is that "Someone should fix it". It is not fixed yet. Thanks for the offer though.

bubnikv added a commit that referenced this issue Dec 7, 2020
SL1 file was exported with a .gcode suffix if the user did not provide
output file name for SLA command line slicing.
@bubnikv
Copy link
Collaborator

Fixed with c7586e5

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