slic3r wrong config for pronterface?
Posted by lucindrea
|
slic3r wrong config for pronterface? August 04, 2013 09:28PM |
Registered: 12 years ago Posts: 16 |
so i have 2 versions of slic3r inside the pronterface folder - one is slic3r v 9.9 the other is ver 9.10 (10 fixed some memory issues for me) and i have changed the path inside the proterface options to point to the slic3r v9.10 .. when i click slicer options in proterface it does bring up the correct slic3r and i am able to change the options , then save them (printer-opts , feedf-ops etc) .. every time from that point on when i open slic3r by it's self or from inside proterface (via the slicer options menu command) the panel screen shows all my configs loaded up and all the settings are fine
The issue happens when i drag a stl into pronterface and it runs scli3r - the gcode it creates is compleatly wrong - it puts the head at 200C (i use pla and thats too hot ) and never turns on the heated bead , because if this i'm certin that speed and feed rates for bridging allong with other settings are not getting put into the gcode.
Now if i open slic3r by it's self and load a stl then export the gcode , it's all good (temp at 185 , bed turns on etc) .. i kind of like that pronterface is a all in one soultion but of course it loads gcode files as easly as it loads stl files , i just need to create them beforehand.
This is failry minor and just an extra step for me so no worries if no one knows why it does this , but any help would be appreacated - and fyi - if this should go into another forum (a pronterface one? ) then please let me know
thanks.
EDIT:
after poking around a large amount of googles results , i found some stuff in the github faq ......
If you're feeling more adventurous, you can have Pronterface call the command-line Slic3r automatically when opening an STL file. To get this to work, you must first export the configuration, you wish to use with Pronterface, from Slic3r using Export Config... from the File menu. Next open Options from the Settings menu in Pronterface, and put the following under slicecommand:
slic3r.pl $s --load config.ini --output $o
and the following under sliceoptscommand:
slic3r.pl --load config.ini --ignore-nonexistent-config
Replace slic3r.pl with the full path to the Slic3r executable and config.ini with the full path of your previously exported configuration file. On OS X, the executable has a path like this:
/Applications/Slic3r.app/Contents/MacOS/slic3r
Whenever you edit your Slic3r configuration from within Pronterface, remember to re-export it using the Export Config... from the File menu.
Edited 1 time(s). Last edit at 08/04/2013 11:07PM by lucindrea.
The issue happens when i drag a stl into pronterface and it runs scli3r - the gcode it creates is compleatly wrong - it puts the head at 200C (i use pla and thats too hot ) and never turns on the heated bead , because if this i'm certin that speed and feed rates for bridging allong with other settings are not getting put into the gcode.
Now if i open slic3r by it's self and load a stl then export the gcode , it's all good (temp at 185 , bed turns on etc) .. i kind of like that pronterface is a all in one soultion but of course it loads gcode files as easly as it loads stl files , i just need to create them beforehand.
This is failry minor and just an extra step for me so no worries if no one knows why it does this , but any help would be appreacated - and fyi - if this should go into another forum (a pronterface one? ) then please let me know
thanks.
EDIT:
after poking around a large amount of googles results , i found some stuff in the github faq ......
If you're feeling more adventurous, you can have Pronterface call the command-line Slic3r automatically when opening an STL file. To get this to work, you must first export the configuration, you wish to use with Pronterface, from Slic3r using Export Config... from the File menu. Next open Options from the Settings menu in Pronterface, and put the following under slicecommand:
slic3r.pl $s --load config.ini --output $o
and the following under sliceoptscommand:
slic3r.pl --load config.ini --ignore-nonexistent-config
Replace slic3r.pl with the full path to the Slic3r executable and config.ini with the full path of your previously exported configuration file. On OS X, the executable has a path like this:
/Applications/Slic3r.app/Contents/MacOS/slic3r
Whenever you edit your Slic3r configuration from within Pronterface, remember to re-export it using the Export Config... from the File menu.
Edited 1 time(s). Last edit at 08/04/2013 11:07PM by lucindrea.
|
Re: slic3r wrong config for pronterface? August 07, 2013 12:17PM |
Registered: 12 years ago Posts: 6 |
I wasn't sure if by editing your post you were saying you were okay now or not, apologies if I'm about to tell you stuff you've already worked out.
I hit the same problem, and yes, the solution is to tell slic3r to "export" the configuration, and then change the pronterface options to point to that file. In the latest pronterface version that would be under Settings/Options/External Commands/Slice Command.
When you export the settings from slic3r you can call the file anything you want, and you can put it anywhere you want.
When you tell pronterface where it is and what it's called I think it's safer to use the fully qualified path name; for example mine is: -
./Slic3r/slic3r.exe $s --load /Pronterface/Slic3r_config.ini --output $o
I hit the same problem, and yes, the solution is to tell slic3r to "export" the configuration, and then change the pronterface options to point to that file. In the latest pronterface version that would be under Settings/Options/External Commands/Slice Command.
When you export the settings from slic3r you can call the file anything you want, and you can put it anywhere you want.
When you tell pronterface where it is and what it's called I think it's safer to use the fully qualified path name; for example mine is: -
./Slic3r/slic3r.exe $s --load /Pronterface/Slic3r_config.ini --output $o
Sorry, only registered users may post in this forum.