Notifications
Clear all

PrusaControl - official thread  

Page 2 / 4
  RSS
PJR
 PJR
(@pjr)
Moderator
Re: PrusaControl - official thread


How accurate is Craftware in terms of time estimation? I've tried gcode.ws and Simplify3D and they both give estimates that are usually way off (more than an hour on a 5h print). With PrusaControl, the estimates are usually within a minute or two, even on bigger prints.

My current workflow is to use Slic3r and then load the gcode in PrusaControl for time estimate. It's a bit annoying, but it works.

Well, PrusaControl will always be the most accurate; it's the only slicer written specifically for the Mk2.

Peter

Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…

Posted : 24/07/2017 2:07 pm
3d-gussner
(@3d-gussner)
Reputable Member Prusa-Translations
Re: PrusaControl - official thread

To use the newest Slic3r PE standalone and in Prusa Control i just copy it to '<drive>:\Program Files (x86)\PrusaControl\tools\Slic3r-Lite' and modify the shortcut to that path for Slic3r PE.

So i am sure that generating gcode with Slic3r PE and Prusa Control are using the same version of Slic3r with all the new fixes and features.

Posted : 26/07/2017 9:34 pm
3d-gussner
(@3d-gussner)
Reputable Member Prusa-Translations
Re: PrusaControl - official thread

QUESTION:

I try to compile the Prusa Control on my Win 10 64-bit workstation but it looks like the build folder isn't complete and the exe doesn't start.

Any advise how to get it working?

Posted : 26/07/2017 9:39 pm
robert.b26
(@robert-b26)
Estimable Member
Re: PrusaControl - official thread


I'm quite happy with PrusaControl so far, especially since the time estimates are within a minute or two, which is awsome! No other slicer that I've used came even close.

I completely agree, I couldn't believe how much having a accurate time estimate has changed how I set up my personal print queue. Being able to start a 5 hour print at 7am, and know I can come home at lunch at noon to start the next one sounds simple, but is amazing.

I thought I'd just try prusacontrol for fun, because I was used to tweaking all the knobs in Slic3r, but after a dozen beautiful prints, I think I'm sold.

Robert B.

Posted : 26/07/2017 11:27 pm
Hobby Hoarder
(@hobby-hoarder-2)
Trusted Member
Re: PrusaControl - official thread

Until now, I was using Slic3r for generating gcode and then I would just import that into PrusaControl to get an accurate time estimate. Today I tried doing the same thing with Simplify3D, but PrusaControl won't calculate the time (I just get "nan"). Am I doing something wrong? The generated gcode prints great of course.

Posted : 08/08/2017 9:01 pm
Jason Foss
(@jason-foss)
Eminent Member
Re: PrusaControl - official thread

I really enjoy using PrusaControl, and I really appreciate the ease of use (I opened Slic3r PE and it was just a lot...) but I feel like I'm outgrowing PrusaControl in a number of instances

(1) I'd like to be able to modify the start and end gcode (mainly to get rid of ooze during heat up, and to put the printer in a better ending position)
(2) I'm using materials (or brands of materials) there aren't profiles for
(3) I'd like to be able to calibrate my extrusion multipliers for all the different filament types I print

Is it "safe" for me to just modify the associated printers / materials_i3_mk2 JSON files (assuming I don't screw up the files, of course)

Posted : 14/08/2017 9:14 pm
Rob Nance
(@rob-nance)
Eminent Member
Re: PrusaControl - official thread

I kind of assumed when this got announced we'd see a streak of updates in short order, but it seems to have been quiet. I want to use it more, but it needs a few key things first the community has been vocal about (like custom profiles, and perhaps an advanced section).

I think some great additional presets would be wise, since that's kind of the purpose of this. Ideally it will auto analyze your STL, and suggest the right presets. For example, the .10 detail preset is great, BUT why not have a ".10 DETAL (complex)" and then a ".10 DETAIL (simple)". The complex could slow speeds down. Tying speed to detail doesn't make a lot of sense, and printing slow for something where stringing wouldn't be an issue doesn't make sense either. I feel like this is the age of software for FDM, that we are entering. You all, and many others like you, have gotten the hardware to a point where at the very least we know what works, and it's just cost issues driving decisions. I really think we need some logic that is using all we have learned, rather than just a one size fits all preset.

Posted : 18/08/2017 9:27 pm
olivier.l6
(@olivier-l6)
Active Member
Re: PrusaControl - official thread

Hi,

I open a stl file in Prusacontrol, and i thought that it didn't work because no object appeared. But at the end i did a zoom. My part is very very small. How is it possible to set the % to have the right size ? In Cura it's easy, you can give a value and keep the ratio for the other axes.

best regards

Posted : 19/08/2017 2:01 pm
Hobby Hoarder
(@hobby-hoarder-2)
Trusted Member
Re: PrusaControl - official thread


Hi,

I open a stl file in Prusacontrol, and i thought that it didn't work because no object appeared. But at the end i did a zoom. My part is very very small. How is it possible to set the % to have the right size ? In Cura it's easy, you can give a value and keep the ratio for the other axes.

best regards

It's easy, just click on the object and you should get the option on the right side. You can then enter the % or switch to mm and enter the exact size. You can also see the lock that keeps the ratio for other axes.

Posted : 20/08/2017 1:34 pm
Mark Fortune
(@mark-fortune)
Active Member
Re: PrusaControl - official thread

Hey team,

I just thought I'd add my two cents and add a feature request. I have been using Prusa Control, and have been pleasantly surprised at the results; everything that I have thrown at it has printed really well. I have a few suggestions that would improve the slicer, and should take very minimal effort to implement.

  • I have all of my other slicers set up so that they heat the nozzle to 170, then run calibration, then home and heat up the rest of the way. This is to reduce the possibility of filament dripping onto the print bed while calibrating. This is a tried and proven method that many, many users have used and tested, and is even baked into the KISS slicer! As the Prusa Research team is the group behind the Prusa Control application, and Prusa Control is based on being a 1-click system for printing, I would think that adding this to the default starting gcode would immensly help users. Thanks for the consideration.
  • Add the controls for rotation of other axis through mouse manipulation. I know this is most likely a feature that you all have coming up, but I thought I'd say it anyway.
  • Brim or Raft. I don't use rafts for anything besides ABS (occasionally), but it's still useful to have.
  • Again, I get that Prusa Control is aimed at beginners and people just want an easy slicer solution. In my opinion (which very well may be irrelevant) these additions would be hugely beneficial to newcomers. I'll add anything if I come across it. So far, awesome job Prusa Team!
    Sidenote: This has also been sent to the feedback page.

    Original Prusa i3 MK2S

    Posted : 03/09/2017 2:46 am
    rob.l6
    (@rob-l6)
    Honorable Member
    Re: PrusaControl - official thread

    Version 9.3_390

    Another thing I just noticed. Saving a project does NOT save the printer settings 😯 Unless I have missed something this is a very basic feature of the software that isn't working. It is therefore pretty useless IMO. 🙄

    Posted : 25/09/2017 5:59 am
    ppaukstelis
    (@ppaukstelis)
    Eminent Member
    Re: PrusaControl - official thread

    I ran into a bit of an issue using the AppImage in a multiuser Linux environment. It seems like writing files to /tmp (printer.json, etc.) causes trouble because the permissions then don't allow other users to read those files.

    Posted : 21/10/2017 1:27 am
    chris.p8
    (@chris-p8)
    Trusted Member
    Big problem with Slic3r integration...

    After some experimentation it would seem that there is a big problem with Slic3r integration - I have used PrusaControl to slice an STL file and generate the gcode and it is useless.

    The resulting print has lost the first 2mm of the model - I used the external (standalone) version of Slic3r on the same STL file and this gcode printed perfectly - so the gcode generation in PrusaControl is broken - the model appears complete in the display but going up through the model layer by layer
    does not display the starting layers either.

    Makes it pretty well unusable - pity as I have had several models that did print ok, might try an earlier release with the same model and see if this is a recent problem - I am using 9.3_390_beta

    Chris

    Posted : 21/10/2017 6:57 pm
    ppaukstelis
    (@ppaukstelis)
    Eminent Member
    Re: PrusaControl - official thread


    I ran into a bit of an issue using the AppImage in a multiuser Linux environment. It seems like writing files to /tmp (printer.json, etc.) causes trouble because the permissions then don't allow other users to read those files.

    Is there a way to change the temporary directory where files get written (commandline option?) This problem has begun to get very annoying for users.

    Posted : 06/11/2017 1:58 pm
    walter.v4
    (@walter-v4)
    Active Member
    Re: PrusaControl - official thread

    I just installed version 0.9.4_415_beta on win7; wanted to try printing in different colors on my MK2S.
    Basically, it just adds command M600 at the right place. Nothing else.

    All in one, nice tool, very simple to use. A few comments:
    I keep getting a warning message "Object blabla...is out of printable area" while modifying the scale.
    This message is not correct. The object is not out of printable area. I eventually managed to get rid of it by clicking everywhere...

    What's the purpose of the project file .prusa? It's a zip that contains the stl model and an xml file. Just a few parameters are saved in the xml.
    Would that be feasible to include the printer settings?

    Thanks

    Posted : 16/11/2017 3:23 pm
    marco
    (@marco-9)
    Eminent Member
    Re: PrusaControl - official thread

    I really love PrusaControl...but in Ubuntu 16.04 you cannot load saved projects...already opened an issue for this in GitHub...

    Posted : 18/11/2017 1:11 pm
    ToTo
     ToTo
    (@toto)
    New Member
    Re: PrusaControl - official thread

    Guys, Is it possible to allow customisation of some of the most common settings? Like Cura has hide/show feature.
    I really like the user interface and I would love to use it permanently.

    Posted : 28/11/2017 10:49 am
    chris.p8
    (@chris-p8)
    Trusted Member
    Re: PrusaControl - official thread

    When you open an STL file and generate the gcode, is it possible when you save it, to point to the same location the file was opened from?

    I frequently click the save button and then have to go hunting around for the gcode which is saved in what often appears to be a random
    target directory? I realise that you can re-navigate back to where you came from but it is a bit annoying?

    Thanks

    Chris

    Posted : 08/12/2017 10:00 am
    Donovan
    (@donovan)
    Re: PrusaControl - official thread

    I have been using Prusa Control for a couple months and it has been great, but I just upgraded to the new version 0.9.4_415, and now it takes forever to slice, 5-10 minutes where it used to take 30 seconds... I am using it on a Mac running High Sierra 10.13.1.. I have tried deleting the app and reinstalling, any ideas?

    Posted : 13/12/2017 12:58 am
    JoshFink
    (@joshfink)
    Active Member
    Re: PrusaControl - official thread

    Similar issue. I had to go in and delete the app AND delete ~\Library\Application Support\PrusaControl and then reinstall. I still find it slower than the previous version but not as painfully slow as without the delete.

    Posted : 13/12/2017 3:27 pm
    Page 2 / 4
    Share: