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

Incorrect settings extracted from Prusa (2.8.1) Sliced gcode #22

Open
infinisean opened this issue Nov 1, 2024 · 1 comment
Open

Incorrect settings extracted from Prusa (2.8.1) Sliced gcode #22

infinisean opened this issue Nov 1, 2024 · 1 comment

Comments

@infinisean
Copy link

When I slice an export the model, and then load it in the web-interface, it has many incorrect settings.... for example, I am using the PrusaXL 2-tool and it picks up my Tool-0 diameter, even though I have sliced for Tool-1... likewise the temperature is neither the first layer or other layer temp from the sliced output, the speeds are all wrong, the filament overrides like retract length are incorrect, etc.

Two suggestions:

  1. I like how you explain how (some of) the settings are chosen from the sliced/exported file.... I would suggest expanding on that to included the full configuration line in question that the script is pulling the value from. That will aid in debugging...
  2. It would be very helpful to have the values that are pulled from the sliced/exported file auto-populate text-input boxes in a large form, with the ability to override those "learned" values if they are erroneous (or advanced users just want a quick way to make an adjustment without going through the whole slice/export/import/review process each time a change is needed).
@garethky
Copy link
Owner

garethky commented Nov 2, 2024

Ok, I can dig into that, I have an XL and I'm on 2.8.1 locally. Would you mind providing the gcode file that you used?

Looks like the tool number is pulled from the perimeter_extruder setting. But maybe that's not right for the XL.

    • Maybe, I'll have to see how much work that is to implement. Ideally you get the line, along with a line number in the file to find it.
    • I don't want to add the text boxes, its just so overwhelming. The concept here is that Prusa Slicer has all those text boxes. E.g. If you really think you should print the test faster, you can change that in Prusa Slicer. We do have some issues open about specific choices that are hard to make: specifically what the print temp should be, see Use printing temperature instead of first layer temperature for test #19.

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

2 participants