Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use AM settings #19

Open
natdan opened this issue Jul 10, 2017 · 5 comments
Open

Use AM settings #19

natdan opened this issue Jul 10, 2017 · 5 comments

Comments

@natdan
Copy link
Collaborator

natdan commented Jul 10, 2017

... to start with when using known slicers (i.e. Slic3r). It would need an controller which would be invoked before invoking a slicer and it will in turn read AM details (from wherever they are stored - probably Cura's format and transfer them to target slicer's config file.

For example: before Slic3r is invoked, read ~/CEL Robox/PrintJobs//.roboxprofile and produce slic3r.ini file and then pass that as command line parameter when invoking Slic3r. That way some of the presets from AM would be preserved when Slic3r is inovked. Most importantly material details (what's the point of smart reels if that info is lost in translation).

@nebbian
Copy link
Owner

nebbian commented Jul 10, 2017

@natdan, just a point of order, the material details ARE preserved (at least the temperatures are, I haven't tested the extrusion multiplier, but I think it would be preserved). That's part of the magic of using the Robox postprocessor. It sets the temperatures to whatever is on the smartreel.

I totally agree that we should parse the .roboxprofile and put as much as possible into the command line string for the slicer. For example, the brim width, layer height, and whether to use support would be prime candidates to get started.

@natdan
Copy link
Collaborator Author

natdan commented Jul 10, 2017

Actually you are right regarding temperature - it is set in gcode pre and post scripts added to the sliced gcode. Unless temperature (and head speeds!) do have any influence to resulted gcode from selected slicer.

@24c
Copy link

24c commented Jul 10, 2017

Guys, just out of curiosity, I looked at one of my PrintJob files, and there is a .gcode, .slicer.gcode & a .robox.gcode. I take it the .robox.gcode is the version that AM is using in the end? I only ask because my AM temperatures for my filaments are different to the Slic3r ones I imported into Slic3r when I first installed using the config bundle. AM is reporting the AM temperatures not the Slic3r ones in the window bottom left of AM.
am-temps
am-filament-temps
slicing-temps

@nebbian
Copy link
Owner

nebbian commented Jul 10, 2017

@24c, as I mentioned above, the temperatures that get used for printing are the ones that you set in AutoMaker, not Slic3r. This is done by the postprocessor.

@24c
Copy link

24c commented Jul 10, 2017

@nebbian, OK, I just looked anyway :) ...but this is a good thing isn't it?, as you can't damage things.

I've already seen so far that the support, solid layers etc and infills are all driven by the Slic3r settings, which is pretty cool, as when you Preview the layer, you see how it is going to be made, and these things being implemented. There are a lot of check boxes in Slic3r PE, and I don't know if they all work, as maybe the post processor strips them out, but the infill patterns and support settings are doing fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants