![]() ![]() Make sure you have all required Mono libraries installed. ![]() Move it to where you want your files and unpack its contents and run the post installation script: tar -xzf repetierHostLinux_1_03.tgzĪfter that you have a link in /usr/bin to the installation, so you can start it with repetierHost. ![]() The linux version comes as gzipped tar file. You can omit /relregistry if you want to keep the registry settings. \setupRepetierHost_2_3_1.exe /COMPONENTS="Components=app,slicer,slicer\curaengine,slicer\slic3r,slicer\slic3rpe,assoc,assoc\stl,assoc\ast,assoc\3mf,assoc\obj,assoc\amf,assoc\gcode,assoc\gco,assoc\g" /MERGETASKS="desktopicon" /VERYSILENT /SUPPRESSMSGBOXES /CLOSEAPPLICATIONS Silent uninstallįor a silent uninstall call uninst000.exe with this parameter: "C:\Program Files\Repetier-Host\unins000.exe" /VERYSILENT /delregistry With the following command line you can run a typical silent install. Silent installįor a automated silent install you need to skip Repetier-Server installation and suppress message boxes. The installer already contains Slic3r, Prusa-Slicer and CuraEngine. After downloading run the installer and you are done. The windows version comes with a installer. Go to the download page and fetch the latest version for your os. With lower versions you may have speed issues with live preview. For a good rendering performance OpenGL 1.5 or higher is needed. The only other requirement is a graphic card with OpenGL. NET framework 4.0 or a recent Mono installation, if you are running Linux. If you have a Macintosh computer, check for the Repetier-Host Mac on this site. The Host works on Windows XP and later and on Linux. If you have an old computer running Windows XP you may have difficulties. Currently available computers should have no problems at all. įor me, PrusaControl has been far closer at print time esitmates than Astroprint/Octoprint have been.Before you start with the installation, you should check if your computer meets the requirements. Are you using the 2.0 drivers? Try slicing in Slic3r and see what that gcode produces on. gcode estimates is full speed motor movements. Its usually the acceleration/deceleration of the motors that add up over time where the. 24 hour prints are usually off by an hour or 2 for me. That's weird that its off so much on a relatively short print. A big factor in print time estimation being wrong is on longer prints than that. Somewhat within an hour would be good enough i guess ?Īny ideas or experience with print time estimates that might help me? I just want to have some sort of guess how long a print will take. my whole desk is shaking violently becaus it is moving so fast (Stone plate and Enclosure incoming soon ? ) I am not realy complaining about the speed of the printer. is there any way to make a better guess? is it possible that firmware on my mk3 has like "wrong" or old setting throwing the estimate of? (See picture) EDIT: It took 7:05 in total. Running the print on my mk3 is running close to 7 hours. I just printed the stock gcode Adalinda that came on the sd card. I mostly got the same print time estimates using as i got of prusa control. so it took for example 3 hours instead of 2. I noticed that the estimate print time in Prusa Control was off. ![]()
0 Comments
Leave a Reply. |