LeadAssimilator
commented
5 years ago Slic3r is exporting .gcode files as utf-8 but PrusaControl is not correctly specifying the encoding when reading them back in gcode.py's copy_file_with_progress_and_color_changes. This leads to an unhandled exception which breaks the saving process and the UI entirely if the original file contains utf-8 characters.
The default usage of Slic3r will insert utf-8 characters towards the end of the file as ; filament_notes = "List of materials tested with standart PLA print settings for MK2:\n\nDas Filament\nEsun PLA\nEUMAKERS PLA\nFiberlogy HD-PLA\nFillamentum PLA\nFloreon3D\nHatchbox PLA\nPlasty Mladeč PLA\nPrimavalue PLA\nProto pasta Matte Fiber\nVerbatim PLA\nVerbatim BVOH" which comes from the Notes tab of the selected filament profile in Filament Settings and is saved in PrusaResearch.ini.
Workaround Options
- Use https://www.prusaprinters.org/color-print/ instead because PrusaControl appears to be dead.
- Remove/clear the Notes from the selected filament profile in Slic3r prior to gcode export (may come back when profiles get updated).
- Add a Slic3r Post-Processing Script to remove the filament_notes comment.
- Use https://manual.slic3r.org/advanced/filament-swaps (tedious - Slic3r needs to offer a simple layer height color change feature like PrusaControl did).
- Add the M600 command manually with your favorite text editor.
The ColorPrint plugin at the generate/save state hang (or take very long) on 44%. The file is almost finished in the hdd, just missing the end (flush()?) I tried with big file, and a short one the same result.