› ›

Integration with PrusaSlicer 2.9.3 (flatpak)

HUBHUB
in Linux
RepetierHost 2.3.2 successfully works with PrusaSlicer 2.6.1 which is distributed as a set of files to be unpacked in some directory.
But PrusaSlicer 2.9.3 is only distributed as flatpak. This flatpak app may be run with flatpak run com.prusa3d.PrusaSlicer but RepetierHost requires a path to binary when configuring external slicer. I've tried to create a shell script with this to have this executable:

#!/bin/bash

Configured executor path as /home/user/.var/app/com.prusa3d.PrusaSlicer/config/PrusaSlicer/ and pointed to the above script as PrusaSlicer executable (+x permission set). I'm able to see configurations in drop-down, able to run the slicer for configuration with "Configuration" button in RepetierHost but can't run slicing, getting the following in log:

18:58:18.967 : PrusaSlicer command:/home/user/3D/prusa_flatpak.sh --load "slic3r_settings.ini" --dont-arrange --export-gcode --output "composition.gcode" "composition.amf"
18:58:18.974 : Preferred name from Cube_20x20x20mm to Cube_20x20x20mm
18:58:19.170 : <PrusaSlicer> --------------------------------------------------------------------------
18:58:19.171 : <PrusaSlicer> Message: 18:58:19: Starting PrusaSlicer flatpak with entrypoint script
18:58:19.171 : <PrusaSlicer> --------------------------------------------------------------------------

Running the command manually gives No such file: slic3r_settings.ini but I suggest RepetierHost generates some temporary slic3r_settings.ini for that and don't know how to get the sample for further testing.

So does RepetierHost support PrusaSlicer 2.9.3? How to set these two to work together?

Comments

  • HUBHUB
    By accident found the sample files from previous run of slicer through RepetierHost.
    Tried to manually run the script described above /home/user/3D/prusa_flatpak.sh --load ~/.local/share/RepetierHost/slic3r_settings.ini --dont-arrange --export-gcode --output composition.gcode ~/.local/share/RepetierHost/composition.amf and... successfully got the resulting .gcode file. So the question is now how to make it work with a click of a button in RepetierHost.
  • RepetierRepetier
    That should work, but you need to be aware of 3 issues to make it work:
    1. We call it from workingdirectory so output composition.gcode is ~/.local/share/RepetierHost/composition.gcode - you might tweak the path if slicer does not find it.
    2. For slicing we call the console variant, so no gui should appear. Actually the same executeable just different parameter I think if it is not named prusa-console or so.
    3. We only understand ascii gcode, so with prusa printers disable output format binary.
Sign In or Register to comment.