Prusaslicer: Extend the "filament type" list with PC or allow free form text into the filament type field.

[landrunner22002]

Version

_Version of Slic3r used : 1.41.2

Operating system type + version

Mac OS Sierra

Behavior

After selecting "Polymaker PC-MAX" in "Filament" menu, the exported Gcode file from Slic3r 1.41.2 added "ABS" as filament type instead of "PC-MAX" or "PC" in file name.

[bubnikv]

because it is using the key "Filament type" from the selected filament,
which is set to ABS.

On Thu, Jan 24, 2019 at 10:59 AM landrunner22002 [e-mail]
wrote:

Version

_Version of Slic3r used : 1.41.2
Operating system type + version

Mac OS Sierra
Behavior

After selecting "Polymaker PC-MAX" in "Filament" menu, the exported Gcode
file from Slic3r 1.41.2 added "ABS" as filament type instead of "PC-MAX" or
"PC" in file name.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Slic3r/issues/1704, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFj5Iz0TVwaH4Ih1o60FH6UTZxEBbqVYks5vGYQDgaJpZM4aQhDs
.

[landrunner22002]

because it is using the key "Filament type" from the selected filament, which is set to ABS.
…
On Thu, Jan 24, 2019 at 10:59 AM landrunner22002 @.*> wrote: Version _Version of Slic3r used : 1.41.2 Operating system type + version Mac OS Sierra Behavior After selecting "Polymaker PC-MAX" in "Filament" menu, the exported Gcode file from Slic3r 1.41.2 added "ABS" as filament type instead of "PC-MAX" or "PC" in file name. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1704>, or mute the thread https://github.com/notifications/unsubscribe-auth/AFj5Iz0TVwaH4Ih1o60FH6UTZxEBbqVYks5vGYQDgaJpZM4aQhDs .

And no PC-MAX is available in "Filament Type" menu

[bubnikv]

No. The filament type should be a generic identifier, for PC-MAX a PC would be appropriate.

Originally this field was added to support the Prusa Multi Material upgrade, so that the wipe tower generator would decide the ramming sequences on it. Now we have the ramming sequences parametrized, but there is still some functionality decided internally based on the filament type, namely the print slows down when mixing flex or soluble material with non-flex.

You are right, we shall extend the list of generic polymers, or we should make the list extensible / allow free form texts here.

[jhoblitt]

It is also useful for the filament type to be encoded in the in the gcode filename.

[jhoblitt]

Off the top of my head, here are a few other polymers in use:

• nylon or PA
• polypropylene or PP
• PEI
• PEEK
• PEKK (different from PEEK)
• POM
• PSU
• PVDF

[jhoblitt]

@bubnikv Do additional material types only need to be added to src/libslic3r/PrintConfig.cpp or is there additional work required?

[jhoblitt]

oh, hmm, looks like the ConfigOptionEnum template also needs to be updated.

[jhoblitt]

uh, are two enums for the filament necessary?

[supermerill]

I also had a request for "htpla", i think a free-form field text field (or an extensible list) is needed.

[Photogad]

I also had a request for "htpla", i think a free-form field text field (or an extensible list) is needed.

+1

[Photogad]

It is also useful for the filament type to be encoded in the in the gcode filename.

precisely... it's very useful for those of us that do frequent prints with different materials

[3Dietrich]

also for me as Palette2 user, I'm afraind I need a string to define distinct "filament variable" for post processing the gcode (see /tomvandeneede/p2pp project). Concretely I'm stuck now with BVOH what runs under the type "PLA" in Slic3r but definitly needs a special slicing setting. It seems Slic3r enables me to enter my own string (e.g. "BVOH") but after some other changes it turns out the input was ignored and the string is back to "PLA"..

[bubnikv]

Implemented with https://github.com/prusa3d/PrusaSlicer/commit/c7f6e5436c0215d34ed4ba417288876fcde02df5
Also the freeform editing of the field is now supported with https://github.com/prusa3d/PrusaSlicer/commit/f0acf4f745e65798fc4bd82acaf40bb756937cda
see https://github.com/prusa3d/PrusaSlicer/issues/2232
Closing

[bubnikv]

@jhoblitt thanks for the list, I have added it verbatim.
I sorted them so that the first 5 most commonly used are at the top and the rest is sorted alphabetically.