PrusaSlicer "DRIBBLING VERSION" for MMU2 updated to latest PrusaSlicer 2.1.0-rc
 

PrusaSlicer "DRIBBLING VERSION" for MMU2 updated to latest PrusaSlicer 2.1.0-rc  

Page 2 / 2
  RSS
rmilyard
(@rmilyard)
Active Member

@antimix

Filament is PLA.

 

 

Posted : 25/09/2019 11:09 pm
Antimix
(@antimix)
Estimable Member
Posted by: @rmilyard

@antimix

Filament is PLA.

 

 

 

 

Hi @rmilyard,

try:

Cooling Moves : 3
speed first move  : 2
speed last move :  8
Dribbling moves:  3

they may be not exactly the same, but I remember I used a very similar settings.

Posted : 25/09/2019 11:15 pm
rmilyard
(@rmilyard)
Active Member

@antimix

Tried those settings and changed nothing else.  Load fail on second pass.

Posted : 26/09/2019 12:40 am
michael.k73
(@michael-k73)
New Member

Thanks a ton for your efforts, antimix! I was able to print a 5-color model with 371 tool changes without any interventions. That was with PLA. Different brands, I used the same settings for all of them.

Another print, where I mixed PLA and PETG needed a single intervention with PETG, where the tips don't seem as perfect as with PLA. That was a model with only 17 tool changes though.

Now I am printing with a single cooling move and three dribblings, to speed up printing. Still perfect tips 🙂

 
Posted : 02/10/2019 11:35 am
michael.k73
(@michael-k73)
New Member

To follow up on that: The second print with 371 tool changes was successful as well 😀 This time with only one cooling move.

I have only few mods on my MK2.5+MMU2s: I replaced the MK2.5 heat break with the MK3 heat break from Prusa, as many people here wrote, that this is vital in order to make MK.5+MMU2s work at all. Otherwise I just got rid of the buffer (I hate it! I use self-winding spools now) and installed this: https://www.thingiverse.com/thing:3233579  But I believe that both are not relevant for my success now, the biggest part is the dribbling and the heat break. 

Posted : 03/10/2019 7:06 am
Antimix and nikolai.r liked
volker.jaenisch
(@volker-jaenisch)
Trusted Member

@antimix

Building from your GH code under Debian Buster.

src/build-utils/CMakeLists.txt

looks broken to me.

Cheers,

Volker

This post was modified 9 months ago by volker.jaenisch
Posted : 11/11/2019 4:27 pm
Antimix
(@antimix)
Estimable Member

@volker-jaenisch

I never built it under Linux. I have compiled on Windows 10, with Visual Studio, following the initial Prusa approximate instructions.
I had to integrate all the missing "...you are skilled developer and you should know by yourself how to 😎 " steps not told, with some scripts that created all the folder structures the compiler needs.  I explained how-to in GitHub in some messages, but I have done it ONLY for Windows 10.
Basically also in Linux you need some basic libraries pre-compiled that should be installed in your development computer, and then you need to launch some shell scripts with specific linux settings that prepare the folder structure and dev environment.
Unfortunately at the moment I don't know how to set up a Linux environment. May be I will have a look, and set up a pre-compiled package if I will success.

Posted : 11/11/2019 5:51 pm
nikolai.r
(@nikolai-r)
Noble Member
Posted by: @antimix

Basically also in Linux you need some basic libraries pre-compiled that should be installed in your development computer, and then you need to launch some shell scripts with specific linux settings that prepare the folder structure and dev environment.

There is a dep/ folder where all required deps are being build.

I've tried to build for Mac couple weeks back and even the main branch of PS was failing. Looks like the devs doing some magic in the background in order to compile it. It's definitely not straight forward like described in the how to. 

Often linked posts:
Going small with MMU2
Real Multi Material
My prints on Instagram...
Posted : 11/11/2019 6:13 pm
volker.jaenisch
(@volker-jaenisch)
Trusted Member

@antimix

Dear Antimix!

I have succesfully compiled the original Prusa-slicer 2.1.0 code without any problems on Debian Buster. Doing the same with your fork does not work, because the file  src/build-utils/CMakeLists.txt in your fork see  https://github.com/antimix/PrusaSlicer/blob/master/src/build-utils/CMakeLists.txt is broken:

src/build-utils/CMakeLists.txt:

<<<<<<< HEAD
add_executable(encoding-check encoding-check.cpp)

# A global no-op target which depends on all encodings checks,
# and on which in turn all checked targets depend.
# This is done to make encoding checks the first thing to be
# performed before actually compiling any sources of the checked targets
# to make the check fail as early as possible.
add_custom_target(global-encoding-check
ALL
DEPENDS encoding-check
)
=======

Cheers,

Volker

Posted : 11/11/2019 9:55 pm
Antimix
(@antimix)
Estimable Member

@volker-jaenisch

Interesting. I will check.

May be the original Prusa repository has been changed to allow the Linux build. As you may know, the forked Repositories are not synced with the MAIN original, and they require a periodic check and update.

 

Posted : 11/11/2019 10:32 pm
volker.jaenisch
(@volker-jaenisch)
Trusted Member

Dear @antimix

The Prusa-slic3r has supported Linux builds since the beginning.

I copied the broken file from gh:master and the cmake process comes up with no problem. The build also started and is currently running. I will keep you informed of the outcome.

Cheers,

Volker

Posted : 11/11/2019 11:57 pm
volker.jaenisch
(@volker-jaenisch)
Trusted Member

The build failed.Here the list of broken files:

resources/profiles/PrusaResearch.ini:<<<<<<< HEAD
resources/profiles/PrusaResearch.ini:<<<<<<< HEAD
resources/profiles/PrusaResearch.ini:<<<<<<< HEAD
resources/profiles/PrusaResearch.ini:<<<<<<< HEAD
resources/profiles/PrusaResearch.ini:<<<<<<< HEAD
Übereinstimmungen in Binärdatei resources/fonts/NotoSans-Regular.ttf
src/build-utils/CMakeLists.txt~:<<<<<<< HEAD
src/build-utils/CMakeLists.txt~:<<<<<<< HEAD
src/slic3r/GUI/GUI_App.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.hpp:<<<<<<< HEAD
src/slic3r/GUI/Field.cpp:<<<<<<< HEAD
src/slic3r/GUI/Field.cpp:<<<<<<< HEAD
src/slic3r/GUI/Tab.cpp:<<<<<<< HEAD
src/slic3r/GUI/Tab.cpp:<<<<<<< HEAD
src/slic3r/GUI/Tab.cpp:<<<<<<< HEAD
src/slic3r/GUI/PresetBundle.cpp:<<<<<<< HEAD
src/slic3r/GUI/PresetBundle.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/ConfigManipulation.cpp:<<<<<<< HEAD
src/slic3r/GUI/GUI_ObjectList.cpp:<<<<<<< HEAD
src/slic3r/GUI/GUI_ObjectList.cpp:<<<<<<< HEAD
src/slic3r/GUI/GUI_ObjectList.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/slic3r/GUI/3DScene.cpp:<<<<<<< HEAD
src/libslic3r/Format/3mf.cpp:<<<<<<< HEAD
src/libslic3r/Format/3mf.cpp:<<<<<<< HEAD
src/libslic3r/Format/AMF.cpp:<<<<<<< HEAD
src/libslic3r/Format/AMF.cpp:<<<<<<< HEAD
src/libslic3r/GCode.hpp:<<<<<<< HEAD
src/libslic3r/Model.cpp:<<<<<<< HEAD

Cheers,

Volker

Posted : 12/11/2019 12:37 am
volker.jaenisch
(@volker-jaenisch)
Trusted Member

@antimix

Any news?

I can make a new fork and join in your changes if this helps. I am no C++ hero but capable enough.

I really need your code since my MMU stucks with to big tips and I hope that your algorithm may be a help.

Cheers,

Volker

Posted : 14/11/2019 12:35 am
volker.h3
(@volker-h3)
Active Member

I experiencing the same Problem and I'm not able to compile a Windows version by my own (neither the original one nor the drippling). I succeeded in compiling the dependencies (with a lot of warnings), but failed by compiling the main program.

Volker

Posted : 19/11/2019 5:55 am
Page 2 / 2
Share:

Please Login or Register