Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> Was the spiral vase mode changed or did I just change a setting?
The spiral vase mode was broken with the relative extruder addressing, which we had enabled by default in our profiles. Now the spiral vase mode is working with the relative extruder addressing mode as well. So what you see is how it always was supposed to work. Enjoy 🙂
To find out what people print single line wall thickness spiral mode, search thingiverse:
http://www.thingiverse.com/search?q=spiral+mode&sa=
I would recommend to use PLA only, maybe to reduce or disable the print cooling fan and maybe to increase the external perimeter line width with spiral mode, so the single line will stick together well enough. I had difficulties to print a spiral mode with ABS as a single line does not provide a good enough bond.
Vojtech
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
@Jo @Vojtech It would be good to see a compiled version of the Windows Slic3r in Future releases. That way we could for example integrate it into Repetier Host. This only works if there's a binary and a path to the profiles.
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
Helmi,
> @Jo @Vojtech It would be good to see a compiled version of the Windows Slic3r in Future releases. That way we could for example integrate it into Repetier Host. This only works if there's a binary and a path to the profiles.
We are providing the Windows binaries as part of the windows drivers and as releases on github.
https://github.com/prusa3d/Slic3r/releases
Frankly, I would love to help, but I don't understand the request. Could you be more specific?
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
Thanks for replying so quickly.
By binary I was talking about an .exe file for windows. The Windows package does also contain the perl files with perl executables and batch files as far as I can see.
But I already digged a bit deeper and it looks like there's another problem why Repetier Host doesn't work with the Prusa Slic3r.
To be more precise here's what I'm looking for:
Repetier Host ( https://www.repetier.com/ ) utilizes Slic3r, Cura or others - to combine slicing with its Host software. Besides the Slic3r they are delivering with the Host you are able to add additional slicers. Therefore a Binary is needed and a directory for profiles. The profiles integration already works, but Slic3r needs to be there as a binary (.exe) so it can call it with options for gui or not (when slicing).
Additionally I found out that the XML::SAX module for perl is missing which is required for parsing AMF files. AMF files are supported by the stock slic3r version and used for positioning of multiple Objects on the print plate.
It would be great to have the Prusa Version of Slic3r compatible here - this would enable us to use and integrate it with Repetier Host.
Get back to me anytime if you need additional information.
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> By binary I was talking about an .exe file for windows. The Windows package does also contain the perl files with perl executables and batch files as far as I can see.
I see. Providing a windows exe is on my list.
The "official" Slic3r contains a Slic3r.exe generated by an installer package cava, which is unmaintained for years and contains GUI libraries, with which Slic3r is unstable. We at Prusa Research invested about two weeks to work around the cava installer and find another way. Due to the cava packager obsolence, are currently the only provider of up to date Slic3r for OSX.
http://www.citrusperl.com/
http://www.cavapackager.com/
So creating an exe for Slic3r on windows (and on other operating systems as well) means to create a perl interpreter wrapper, loading a perl.dll, instantiating the interpreter, delivering some of the command line parametes etc. Basically exactly what the batch does, but compiled as an exe. One reason to do that is that you can then differentiate Slic3r in the list of processes and if you get a core dump, it will be a Slic3r core dump, not perl core dump.
> Repetier Host ( https://www.repetier.com/ ) utilizes Slic3r, Cura or others - to combine slicing with its Host software. Besides the Slic3r they are delivering with the Host you are able to add additional slicers. Therefore a Binary is needed and a directory for profiles. The profiles integration already works, but Slic3r needs to be there as a binary (.exe) so it can call it with options for gui or not (when slicing).
As of today, you can call the perl interpreter instead of the slic3r.exe and to deliver the command line parametes, which are currently stored in the batch file. It should be much easier to do the change on your side than on our side, if you want to provide an immediate solution.
> Additionally I found out that the XML::SAX module for perl is missing which is required for parsing AMF files. AMF files are supported by the stock slic3r version and used for positioning of multiple Objects on the print plate.
That is fixed in the latest Slic3r Prusa Edition builds.
> It would be great to have the Prusa Version of Slic3r compatible here - this would enable us to use and integrate it with Repetier Host.
We fully support and appreciate your initiative.
Thanks, Vojtech
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
>
To find out what people print single line wall thickness spiral mode, search thingiverse:
http://www.thingiverse.com/search?q=spiral+mode&sa=
I would recommend to use PLA only, maybe to reduce or disable the print cooling fan and maybe to increase the external perimeter line width with spiral mode, so the single line will stick together well enough. I had difficulties to print a spiral mode with ABS as a single line does not provide a good enough bond.
Vojtech
I use it to print parts for the trombone I'm printing - I need some very thin walled (about 0.33-0.35mm) tubes as bushings for the slide and an airtight 0.4mm wall thickness tube for the leadpipe. Works great with the new slic3r!
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
Hi Vojtech,
thanks for beeing transparent and open on this. I highly appreciate that.
I see. Providing a windows exe is on my list.
good to hear.
The "official" Slic3r contains a Slic3r.exe generated by an installer package cava, which is unmaintained for years and contains GUI libraries, with which Slic3r is unstable. We at Prusa Research invested about two weeks to work around the cava installer and find another way. Due to the cava packager obsolence, are currently the only provider of up to date Slic3r for OSX.
http://www.citrusperl.com/
http://www.cavapackager.com/
So creating an exe for Slic3r on windows (and on other operating systems as well) means to create a perl interpreter wrapper, loading a perl.dll, instantiating the interpreter, delivering some of the command line parametes etc. Basically exactly what the batch does, but compiled as an exe. One reason to do that is that you can then differentiate Slic3r in the list of processes and if you get a core dump, it will be a Slic3r core dump, not perl core dump.
oh yeah I forgot all that trouble. Thanks for the explanation.
As of today, you can call the perl interpreter instead of the slic3r.exe and to deliver the command line parametes, which are currently stored in the batch file. It should be much easier to do the change on your side than on our side, if you want to provide an immediate solution.
I'm already playing around with that. Think I have to write some own batch to make one batch file start either the gui or the non-gui version instead of using two batches but we'll figure that out.
> Additionally I found out that the XML::SAX module for perl is missing which is required for parsing AMF files. AMF files are supported by the stock slic3r version and used for positioning of multiple Objects on the print plate.
That is fixed in the latest Slic3r Prusa Edition builds.
I will give that a try later today. Thanks.
> It would be great to have the Prusa Version of Slic3r compatible here - this would enable us to use and integrate it with Repetier Host.
We fully support and appreciate your initiative.
😀
Thanks so much,
Frank
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> I use it to print parts for the trombone I'm printing - I need some very thin walled (about 0.33-0.35mm) tubes as bushings for the slide and an airtight 0.4mm wall thickness tube for the leadpipe. Works great with the new slic3r!
Please share the results. I am certainly inclined to print my own trombone. Hope we are talking about a musical instrumens 😉
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
I tried the latest version.
It's getting better but we're still not there. AMF files load through the gui but when trying to load them as RepetierHost does I get this:
"C:\Program Files\Prusa3D\Slic3rPE\slic3r.bat" --load "slic3r_settings.ini" --print-center 145.00,145.00 -o "composition.gcode" "composition.amf"
Can't load 'C:/Program Files/Prusa3D/Slic3rPE/lib/auto/XML/SAX/ExpatXS/ExpatXS.xs.dll' for module XML::SAX::ExpatXS: load_file:The specified module could not be found at C:/Program Files/Prusa3D/Slic3rPE/lib/DynaLoader.pm line 193.
at (eval 89) line 1.
Compilation failed in require at (eval 89) line 1.
This is called from the directory where the file (composition.amf) resides. As I understand it has trouble loading the dll but that also is at the place where it should be.
Any idea what's going on here?
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> This is called from the directory where the file (composition.amf) resides. As I understand it has trouble loading the dll but that also is at the place where it should be.
> Any idea what's going on here?
I think this is the standard dll loading issue on Windows. DLLs are searched in following directories in the following sequence, if I remember correctly.
1) Current directory. This is how the slic3r.bat works. It goes to the directory of the Slic3r binary first, then it starts the perl interpreter there.
2) The directories listed in PATH
3) The standard Windows directories.
For you, you either have to extend PATH, or change the current directory to the directory of Slic3r.
Vojtech
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
Can the Prusa Slic3r be used in Ubuntu?
I'm reluctantly booting into Windows to use it, and Ilike the 0.15mm setting and the cubic infill.
The 0.15mm Optimal setting impots into Slic3r in Ubuntu, but the cubic infill is non-existent.
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> Can the Prusa Slic3r be used in Ubuntu?
It should be possible.
https://github.com/alexrj/Slic3r/wiki/Running-Slic3r-from-git-on-GNU-Linux
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> Can the Prusa Slic3r be used in Ubuntu?
It should be possible.
https://github.com/alexrj/Slic3r/wiki/Running-Slic3r-from-git-on-GNU-Linux
Thank you very much! That looks promising.
I have been using Slic3r with the Prusa custom config bundle in Ubuntu for a while, can't rmember how I installed it but it was a breeze and it runs well.
Where can I get the Prusa customised new version that has the cubic infill?
I assume I have to use the 'Prusa-Slic3r' instead of the 'Stable' or the "Master' version in this step:
$ git clone https://github.com/alexrj/Slic3r.git
$ cd Slic3r
$ git checkout -b origin/master
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
can someone explain why I have to double my live z value when I use slic3r? I have it at -715 when using s3d but now when I want to use slic3r I have to set it around -1430 for it to work. How is that possible?
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> By binary I was talking about an .exe file for windows. The Windows package does also contain the perl files with perl executables and batch files as far as I can see.
I have a prototype. I hope the Windows slic3r.exe will be in the next release.
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
I assume I have to use the 'Prusa-Slic3r' instead of the 'Stable' or the "Master' version in this step:
$ git clone https://github.com/alexrj/Slic3r.git
$ cd Slic3r
$ git checkout -b origin/master
$ git checkout -b version_1.31.5
That should get you the latest release version. then continue as per the instructions.
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
@Vojtech
we finally got it fixed. The problem is the exact path to your slicers root directory needs to be added to the Path variable. Not the path to the lib directory or anything else.
If aynone else wants to have the Prusa Slic3r integrated into the Repetier Host (which i totally recommend) here's what you need to do:
1. Start the Slicer Manager in the Slicer Tab
2. Add a new slicer (after entering a name)
3. add C:\Users\Public\Documents\Prusa3D\Slic3r settings MK2 as the configuration directory and C:\Program Files\Prusa3D\Slic3rPE\slic3r.bat as the path to the Slic3r executable.
4. You don't need to check the plater checkbox as you won't need it.
Hit apply and exit. You now have your new slicer including all the settings/profiles available to select in Repetier Host.
Have fun 🙂
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
>
Please share the results. I am certainly inclined to print my own trombone. Hope we are talking about a musical instrumens 😉
https://www.facebook.com/photo.php?fbid=10155377830029237&set=gm.654840291367122&type=3&theater
http://www.thingiverse.com/thing:1845509
https://github.com/pieterbos/PrintBone
https://soundcloud.com/pieter-bos-2013025/plastic-bell-plastic-slide
There's also soundcloud files on there with just the bell, compared to a brass bell with a metal slide. Bell sounds really good, slide needs some fixes to sound well. But it should sound good soon 🙂
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
I assume I have to use the 'Prusa-Slic3r' instead of the 'Stable' or the "Master' version in this step:
$ git clone https://github.com/alexrj/Slic3r.git
$ cd Slic3r
$ git checkout -b origin/master
$ git checkout -b version_1.31.5
That should get you the latest release version. then continue as per the instructions.
Thank you Marco, I got a lot further this time!
But now even the old version of Slic3r is not working any longer in Ubuntu.... 🙁
I followed the instructions https://github.com/alexrj/Slic3r/wiki/Running-Slic3r-from-git-on-GNU-Linux carefully from the start, and mostly it seemed to run smoothly. It took a while, about an hour to do the entire process.
Problems encountered where:
1) At the "Update Slicer" step I got an error message. I could not figure out what it means or how to resolve it, so I decided to just forget about updating at the moment (it should be relatively up-to-date I figured) and move on along the instructions without updating.
The message received was:
xxxx:~/Slic3r$ git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> version_1.31.5
xxxx:~/Slic3r$
2) The next steps called "Building Slicer" and "Pearlbrew" apparently went well.
But now that the installation is supposedly finished, I don't know how to start Slic3r
I tried to just type slic3r in the terminal, resulting in this (bolding by me):
p@p-ThinkPad-T540p:~/Slic3r$ slic3r
Subroutine setenv redefined at /usr/share/perl5/Slic3r/Config.pm line 195.
Subroutine min_object_distance redefined at /usr/share/perl5/Slic3r/Config.pm line 352.
Subroutine apply_print_config redefined at /usr/share/perl5/Slic3r/GCode.pm line 32.
Subroutine set_extruders redefined at /usr/share/perl5/Slic3r/GCode.pm line 39.
Subroutine set_origin redefined at /usr/share/perl5/Slic3r/GCode.pm line 48.
Subroutine preamble redefined at /usr/share/perl5/Slic3r/GCode.pm line 62.
Subroutine change_layer redefined at /usr/share/perl5/Slic3r/GCode.pm line 76.
Subroutine extrude redefined at /usr/share/perl5/Slic3r/GCode.pm line 107.
Subroutine extrude_loop redefined at /usr/share/perl5/Slic3r/GCode.pm line 115.
Subroutine extrude_path redefined at /usr/share/perl5/Slic3r/GCode.pm line 240.
Subroutine travel_to redefined at /usr/share/perl5/Slic3r/GCode.pm line 352.
Subroutine needs_retraction redefined at /usr/share/perl5/Slic3r/GCode.pm line 389.
Subroutine retract redefined at /usr/share/perl5/Slic3r/GCode.pm line 424.
Subroutine unretract redefined at /usr/share/perl5/Slic3r/GCode.pm line 449.
Subroutine point_to_gcode redefined at /usr/share/perl5/Slic3r/GCode.pm line 459.
Subroutine set_extruder redefined at /usr/share/perl5/Slic3r/GCode.pm line 469.
Subroutine pre_toolchange redefined at /usr/share/perl5/Slic3r/GCode.pm line 514.
Subroutine post_toolchange redefined at /usr/share/perl5/Slic3r/GCode.pm line 542.
Subroutine wipe redefined at /usr/share/perl5/Slic3r/GCode.pm line 565.
Subroutine init_external_mp redefined at /usr/share/perl5/Slic3r/GCode.pm line 630.
Subroutine init_layer_mp redefined at /usr/share/perl5/Slic3r/GCode.pm line 635.
Subroutine travel_to redefined at /usr/share/perl5/Slic3r/GCode.pm line 640.
Unknown constructor for Slic3r::GCode already exists at /usr/share/perl5/Slic3r/GCode.pm line 13.
Compilation failed in require at /usr/share/perl5/Slic3r.pm line 47.
BEGIN failed--compilation aborted at /usr/share/perl5/Slic3r.pm line 47.
Compilation failed in require at /usr/bin/slic3r line 15.
BEGIN failed--compilation aborted at /usr/bin/slic3r line 15.
p@p-ThinkPad-T540p:~/Slic3r$
I'm really just guessing here, but does this mean I have to un-install the old version or something like it?
Next I tried to start the previously working Slic3r version by going to 'Search your computer', typing 's', and clicking on the Slic3r icon that appears magically. The icon still appears, but clicking on it does no longer start Slic3r. No error messages, nothing.
Any further help would be much appreciated....Mik
Re: Drivers 1.7.5 RC2 with Slic3r Prusa Edition (Updated 18 Nov)
> But now even the old version of Slic3r is not working any longer in Ubuntu.... 🙁
You somehow got the new Slic3r installed over the old one, but likely only partially. I suppose you did not configure the perlbrew correctly.
The simplest you can do right now is to use our linux binary package. I have verified it runs on Ubuntu 16.04.1
https://github.com/prusa3d/Slic3r/releases/tag/version_1.31.6
Vojtech